Fleet 77 / 55 Services Applications Reference

Inmarsat Confidential F77 & F55 Services and Applications Reference Manual

Fleet F77 & F55

Services and Applications

Reference Manual

Version 2.5

March 2006

Disclaimer

This document is for the exclusive use of the recipient to whom it is addressed and the recipient shall not permit this document to be distributed to any third party at any time. Recipients are responsible for making their own decision as to the completeness, fairness or accuracy of the information and any opinions contained in this document and must rely on their own judgement in relation thereto. So far as

Inmarsat is aware, the information contained in this document is true and accurate. However, no representation or warranty, express or implied, is or will be made by Inmarsat and no responsibility is or will be accepted by Inmarsat as to the accuracy or completeness of the document.

For further information or clarification please contact Chris Insall on:

[email protected]

Contributor: Ian C Lewis

[email protected]

Copyright © Inmarsat 2006 Page 1 of 98 Version 2.5


1. INTRODUCTION TO THE INMARSAT FLEET F77 & F55........................... 4

1.1 4.8

KBPS

V

OICE

................................................................................................. 5

1.2 64

KBPS

UDI...................................................................................................... 5

1.3 64

KBPS

S

PEECH

................................................................................................ 5

1.4 64

KBPS

3.1

K

H

Z

A

UDIO

..................................................................................... 5

1.5 56

KBPS

D

ATA

................................................................................................... 5

1.6 M

OBILE

P

ACKET

D

ATA

S

ERVICE

(MPDS) ......................................................... 5

1.7 2.4

KBPS

G

ROUP

3 F

AX

...................................................................................... 6

1.8 9.6

KBPS

G

ROUP

3 F

AX

...................................................................................... 6

1.9 F

LEET

F77

AND

F55

TECHNICAL SYSTEM ENHANCEMENTS

................................ 6

1.10 F

LEET

F77

AND

F55 M

ARITIME

E

QUIPMENT

.................................................. 7

2. THE INMARSAT FLEET (F77 / F55) MARKET............................................. 11

2.1 P

OSITIONING OF

I

NMARSAT

F77 / F55 ............................................................ 11

2.2 F77 / F55

VS

.

VSAT ....................................................................................... 12

2.3 I

NMARSAT

M

OBILE

ISDN................................................................................ 13

2.4 I

NMARSAT

M

OBILE

P

ACKET

D

ATA

S

ERVICE

(MPDS) ...................................... 14

2.5 I

NMARSAT

F77 / F55

APPLICATIONS OVERVIEW

.............................................. 15

2.5.1 Navigation .............................................................................................. 15

2.5.2 DGPS corrections ................................................................................... 15

2.5.3 Navigational chart updates ..................................................................... 15

2.5.4 Obtaining weather reports ...................................................................... 15

2.5.5 Safety, distress, MRCC and Coast Guard communications (F77 Only) .. 15

2.5.6 Interfacing with general analogue equipment.......................................... 16

2.5.7 Secure communications .......................................................................... 16

2.5.8 Fleet Management & the corporate WAN............................................... 16

2.5.9 World-Wide-Web (WWW) access......................................................... 16

2.5.10 Email ...................................................................................................... 16

2.5.11 Ship-to-ship communications.................................................................. 16

2.5.12 Cargo / vessel telemetry ......................................................................... 17

2.5.13 Crew calling (welfare) ........................................................................... 17

2.5.14 Videoconferencing.................................................................................. 17

2.5.15 Using Microsoft



NetMeeting............................................................... 17

2.5.16 Universal Messaging .............................................................................. 17

2.5.17 Voice and data multiplexing ................................................................... 17

2.5.18 File transfer ............................................................................................ 18

2.5.19 128kbps channel ‘bonding’..................................................................... 18

2.5.20 Group 4 facsimile ................................................................................... 18

2.5.21 Telex....................................................................................................... 18

2.5.22 Tele-presence ......................................................................................... 18

2.5.23 Tele-medicine......................................................................................... 18

2.5.24 Tele-education........................................................................................ 18

3. OVERVIEW OF THE INMARSAT SYSTEM.................................................. 19

3.1 F77 / F55 C

OVERAGE MAP

.............................................................................. 19

3.2 I

NMARSAT

4 C

OVERAGE EXTENSION

............................................................... 20

3.3 N

ETWORK

O

PERATIONS

C

ENTRE

(NOC)

AND

LES

S

........................................ 20

3.4 H

OW

F77

AND

F55

CALLS ARE ROUTED

&

BILLED

........................................... 21

4. INMARSAT F77 / F55 TECHNICAL SOLUTIONS ........................................ 24



4.1 M

OBILE

ISDN BRI

INTERFACE

........................................................................ 24

4.2 I

NMARSAT

M

OBILE

ISDN

VERSUS

M

OBILE

P

ACKET

D

ATA

S

ERVICE

................. 25

4.3 N

AVIGATIONAL CHART UPDATES

..................................................................... 27

4.4 O

BTAINING WEATHER REPORTS

....................................................................... 28

4.5 D

ISTRESS

/ S

AFETY

/ MRCC / C

OAST

G

UARD

(F77

ONLY

) .............................. 29

4.6 A

NALOGUE SYSTEMS

– G

ROUP

3

FAX

,

MODEMS AND

DECT............................ 32

4.7 S

ECURE COMMUNICATIONS

– STU

AND

STE .................................................. 33

4.8 F

LEET

M

ANAGEMENT

&

ACCESS TO THE CORPORATE

WAN ............................ 35

4.9 W

ORLD

-W

IDE

-W

EB

(WWW)

ACCESS

............................................................. 37

4.9.1 How to set up Win2000 MPDS dial-up networking ............................... 37

4.9.2 Optimising TCP/IP settings for MPDS ................................................... 43

4.9.3 Typical F77 / F55 WEB applications ..................................................... 44

4.10 E

MAIL VIA

F77 / F55................................................................................... 44

4.10.1 Optimising Outlook Express for F77 / F55............................................. 46

4.10.2 Optimising Eudora 5.1 for F77 / F55...................................................... 50

4.11 C

ARGO

/

VESSEL TELEMETRY VIA

MPDS...................................................... 53

4.12 C

REW CALLING

(

WELFARE

)

VIA

F77 / F55 ................................................... 54

4.13 V

IDEO CONFERENCING

................................................................................ 56

4.14 U

SING

M

ICROSOFT



N

ET

M

EETING VIA

F77

OR

F55................................... 59

4.15 U

NIVERSAL

M

ESSAGING VIA

F77 & F55...................................................... 69

4.16 V

OICE AND DATA MULTIPLEXING VIA

F77 / F55........................................... 71

4.17 F

ILE TRANSFER WITH

F77 & F55 ................................................................. 72

4.18 128

KBPS CHANNEL

‘

BONDING

’ ................................................................... 74

4.19 F

ACSIMILE VIA

F55 / F77 ............................................................................ 75

5. CUSTOMER SUPPORT PROCESSES ............................................................ 77

5.1 S

ERVICE

A

CTIVATION AND

MES

REQUIREMENTS

............................................ 77

5.1.1 Financial - Accounting Authorities & ISPs............................................. 77

5.1.2 Legal....................................................................................................... 77

5.1.3 Contractual / Technical........................................................................... 78

5.2 S

ERVICE

A

CTIVATION

P

ROCESS

...................................................................... 78

5.3 I

NMARSAT

F77 / F55 MES N

UMBERING

.......................................................... 79

5.4 U

SER FAMILIARISATION

................................................................................... 79

5.5 P

OST

-

SALES SUPPORT

..................................................................................... 79

6. ISDN..................................................................................................................... 81

6.1 F

LEET

F77 128K

BIT

/

S

M

OBILE

ISDN .............................................................. 84

7. MPDS & IP INTERNET PROTOCOLS........................................................... 86

8. NETWORK SECURITY ISSUES ...................................................................... 90

8.1 R

EMOTE USER SECURITY

................................................................................. 90

8.2 V

IRUSES

.......................................................................................................... 91

8.3 F

IREWALLS

..................................................................................................... 92

9. TROUBLE-SHOOTING TOOLS AND TECHNIQUES................................. 95



Purpose

The aim of this reference manual is to increase the level of awareness in the Inmarsat Fleet market and in particular to promote and thus share the benefits of the many Inmarsat Fleet applications amongst existing Inmarsat agents, system integrators, distributors, service providers and manufacturers. It will also be of use to end users looking for technical reference information when integrating Fleet F77 or

F55 within their corporate networks.

1. Introduction to the Inmarsat Fleet F77 & F55

In response to the ever-increasing need for data-driven, cost-effective and secure communications at sea, Inmarsat has developed the unique new service family called Fleet, which provides fully integrated satellite communications services incorporating voice and data applications. The first of the Fleet systems to be launched was the 77-cm maritime antenna hence Fleet F77. The newest member is the

Fleet F55. For many of the application descriptions that follow, the terminals are interchangeable but there are some important differences and these are highlighted in the table below.

As well as the global 4.8kbps voice service - Advanced Multi-Band Excitation (AMBE) - and new

(optional) 9.6kbps fax and async data services, F77 & F55 both offer the Mobile ISDN circuit-switched

56/64kbps channel as well as the Mobile Packet Data Service (MPDS), which is mandatory on both

F77 & F55. All the principal F77 / F55 services are summarised below:

Fleet 77 Service

(-4dB/k antenna)

Global 4.8kbps AMBE voice /

DTMF (mandatory)

Distress calling, AMBE voice

(mandatory)

Global 64kbps UDI

(mandatory) for G4 fax etc.

Global 56kbps Data (via V110 rate adaptation)

Global 64kbps/3.1kHz Audio –

G3 fax & analogue services etc.

Global 64kbps Speech

Global MPDS (mandatory)

Global 2.4kbps G-3 facsimile

(optional)

Global 9.6kbps G-3 facsimile

(optional)

Global 9.6kbps async data

(optional)

Fleet 55 Service

(-7dB/k antenna)

Global 4.8kbps AMBE voice /

DTMF (mandatory)

No Distress service

Spot beam 64kbps UDI

(mandatory) for G4 fax etc.

Spot beam 56kbps Data (via V110 rate adaptation)

Spot beam 64kbps/3.1kHz Audio

– G3 fax & analogue services etc.

Spot beam 64kbps Speech

Spot beam MPDS (mandatory)

No

Mobile Physical Port

Via ISDN handset(s) & RJ-11 analogue, 2-wire

Via ISDN handset(s) and dedicated alarm button(s)

RJ-45 ISDN S/T bus (and USB port)

RJ-45 ISDN S/T bus

Via ISDN TA (and via 2-wire analogue)

Via ISDN handset(s)

RS-232 (also RS-422 and USB port)

RJ-11, via FIU two wire analogue

Spot beam 9.6kbps G-3 facsimile

(optional)

Spot beam 9.6kbps async data

(optional)

RJ-11, via FIU two wire analogue

RS-232 serial port

Additional ports may also be available such as supplementary ports for user-supplied handsets, USB for data and local user MES configuration via PC and L-band receive ports for DGPS and chart updates etc.

NOTE: Other than mandatory services, the extent to which these services are implemented by

Land Earth Station Operators (LESOs) and equipment manufacturers may vary.



1.1 4.8kbps Voice

F77 / F55 4.8kbps voice is the default voice telephony service. The service is often referred to as

AMBE voice where AMBE or Advanced Multi-Band Excitation is the technique used to compress the human speech waveform. The service is typically available through the system handset but is also available through additional user-provided handsets (connected to an analogue RJ-11 port on the MES).

This service is the lowest cost telephony service available on F77 / F55 and is equivalent to a global

Mini-M telephony service.

1.2 64kbps UDI

The 64kbps UDI (Unrestricted Digital Information) service supports data applications at 64kbps between Integrated Services Digital network (ISDN) terminals using ISDN protocols such as V.120,

X.75 and PPP (Point-to-Point Protocol). It supports any 64kbps data stream and is the service used for implementing ISDN applications such as Group4 fax, video-conferencing, LAN-routing, File Transfer, and secure telephony.

The service is accessed primarily through an RJ-45 connector on the MES although on some F77 / F55 models can also be accessed via the USB port. On the ISDN S/T bus, multiple ISDN devices (up to 8) may be attached to the MES (see Using MSN with the Inmarsat F77 / F55). Also on some F55 models two 64kbps channels can be ‘bonded’ for a 128kbps aggregate channel.

1.3 64kbps Speech

The 64kbps Speech service supports high quality telephony primarily between ISDN telephones. It may also be used to support an analogue telephone connected to the MES using an ISDN Terminal Adaptor or a corded handset supplied with the MES. This service is typically used where high-quality audio is required for broadcast purposes and is not normally the default maritime voice service.

1.4 64kbps 3.1kHz Audio

The 64kbps 3.1kHz Audio service supports connections between analogue devices commonly used over the Public Switched Telephone Network (PSTN). Such devices may include voice-band data modems such as V.34 operating at speeds up to 33.6kbps with V.42 and V.42bis, Group 3 fax machines at speeds up to 14.4kbps and secure telephone systems such as STU-III, STU-IIB and STE.

The service is normally accessed by attaching the analogue device to the MES via an ISDN Terminal

Adaptor. On some terminals, this is also available via a configurable analogue telephony port on the

MES. Again, this service can be used when high-quality audio is required but is not normally the default maritime voice service.

1.5 56kbps Data

The 56 kbps service supports connections to terminals in Switched 56 networks, which are found primarily in North America. This service is supported by V.110 rate adaptation from 64kbps to 56kbps.

The service is accessed through the RJ-45 connector on the MES.

1.6 Mobile Packet Data Service (MPDS)

The Mobile Packet Data Service offers an ‘always on’ packet-switched, 64kbps shared access channel.

The service is suitable for a wide range of IP-based applications such as corporate LAN access, WWW

Internet browsing, on-line navigational chart updates, on-line weather reports and email. It is accessed via the RS-232 port on the MES (and on some models via the USB port).



1.7 2.4kbps Group 3 Fax

An F77 MES may, as an option, support the 2.4kbps mini-M fax service. However, F77 also supports other fax services as described below which provide a far more cost-effective means of sending and receiving faxes and which would probably be used in preference to the 2.4kbps service. The service, if available, is provided via the ITU Group 3 Fax Interface Unit (FIU) though an RJ-11 connector on the

MES.

1.8 9.6kbps Group 3 Fax

An F77 and F55 MES can, as an option, now also support the 9.6kbps Inm-B fax service. This represents one of the most cost-effective means of sending fax via Fleet F77 or F55. Again, if it is available, the service is provided via the ITU Group 3 Fax Interface Unit (FIU) though an RJ-11 connector on the MES.

1.9 Fleet F77 and F55 technical system enhancements

The F77 / F55 utilises primary channels originally provided for Inmarsat’s Global Area Network (GAN) which itself was a development of mini-M. F77 & F55 use the enhanced New Generation (NG) signalling system to ensure compatibility with the multiple spot-beams of the Inmarsat 4 th

generation spacecraft (I4). F77 has a new call prioritisation and pre-emption scheme to offer improved distress call-handling capabilities. In addition to this, F77 & F55 use improved satellite link margins and more advanced EIRP control and spot beam selection for added communications security and efficiency in a maritime environment.



1.10 Fleet F77 and F55 Maritime Equipment

Some examples of Inmarsat-approved F77 terminal equipment are shown below. The F77 systems available from Nera, Thrane & Thrane, JRC and KVH are illustrated but others may enter the market at a later date.

Nera

The F77 Below Decks Equipment (BDE) from Nera is shown below left. The two designs of

F77 Above Decks Equipment (ADE) from Nera, deck–mounted (A) and mast-mounted (B) are shown below right:

Thrane & Thrane

The F77 BDE & ADE from Thrane & Thrane / Sailor is shown below:



JRC

The F77 BDE & ADE from JRC is shown below:

KVH

The F77 BDE & ADE from KVH are shown below:



Fleet 55 Maritime Equipment

Some examples of Inmarsat-approved F55 equipment are shown below. The systems available from the manufacturers Nera, Thrane & Thrane, EMS and KVH are illustrated but, once again, others may enter the market at a later date.

Nera

The F55 BDE & ADE from Nera are shown below:

Thrane & Thrane

The F55 BDE & ADE from Thrane & Thrane / Sailor are shown below:



EMS

The F55 BDE and ADE from EMS is shown below:

This F55 terminal also supports integrated 128kbps channel bonding.

KVH

The F55 BDE & ADE from KVH are shown below:



2. The Inmarsat Fleet (F77 / F55) Market

2.1 Positioning of Inmarsat F77 / F55

Inmarsat F77 / F55 will be of greatest benefit to maritime users who either have a need to use ISDNtype applications or who have large volumes of data to transmit back to their shore-side head office / fleet management centre. Visit http://fleet.inmarsat.com/ for the Fleet home site.

The Figure below shows how the Inmarsat Fleet services are positioned against the different maritime markets:

F33

F55

Government

Vessel demand for Data,

Global

Voice

Fishing

Leisure

F77

Merchant

Vessel Size

Positioning of Fleet services

The key features of the Inmarsat F77 / F55 service that currently make it unique amongst other satellite communications systems are:

•

Global coverage for F77 (F55 provides global voice and spot beam MPDS and Mobile ISDN)

•

On-demand direct-dialled access to the ubiquitous PSTN and ISDN networks

•

True ‘always-on’ packet-data network to access the Internet

•

Full maritime safety services with pre-emption (Fleet F77 only)

•

Inmarsat does not charge a monthly fee. Demand-assigned services are ‘pay as you use’

If the customer needs a system that has to fulfil all of these requirements then the Inmarsat F77 or F55 services are the perfect choice.

However, in some circumstances, the decision will not be so clear-cut and it may be necessary to consider whether the customers needs will be best addressed by Inmarsat F77 / F55, Inmarsat B or by a maritime VSAT solution. Several factors need to be considered in making this choice as follows:



2.2 F77 / F55 vs. VSAT

Satellite traffic charging

VSAT services are generally arranged and charged on a leased monthly basis with a minimum 6-month contract basis as opposed to the Inmarsat on-demand, per-minute charge. Frequently, VSAT backhaul charges may also be added. On this basis, the VSAT charge per minute can look attractive if the link is to be used on an almost continuous basis, (for example, the transmission of bulk geophysical data from a seismic survey ship or cruise line passenger calling from within selected zones). However, if the link is to be used on a less than full time basis (for example, on-demand routing, www access, navigation & weather forecasts or intermittent company WAN access) the Fleet 77 solution is more likely to be the most cost-effective for the maritime user.

F77 / F55 vs. VSAT - Equipment costs

Inmarsat F77 / F55 maritime terminals will cost in the region of $15-23K USD excluding installation. A typical maritime VSAT system (Ku-band or C-band) costs, excluding installation, from $100K to

$120K USD, although this depends upon the type of system (C-band or Ku-band). Often VSAT networks require additional multiplexers such as Frame Relay Access Devices (FRADs) to interface to customers’ systems. Obviously these equipment costs need to be taken into account in carrying out the break-even analysis as discussed above.

F77 / F55 vs. VSAT – Installation / convenience

Important factors in the maritime market are the size of the satellite communications system, ease of installation, coverage and reliability. Inmarsat F77 / F55 above deck equipment (ADE) systems weigh typically 18 – 65 kilos with a max radome diameter of about 1.3m. Maritime VSAT systems (Ku-band or C-band) typically weigh from 350 to 770 kilos with antenna sizes ranging from 1-3 metres. Although both installations (F77 / F55 and VSAT) need to take account of wind forces on mountings, the physical size of the VSAT equipment requires that special deck mounting and crane arrangements need to be made. In both cases installation has to be carried out by specialist technicians but for F77 / F55 this should take just 1-2 days. VSAT installation often requires highly skilled technicians and expensive test equipment such as 20GHz spectrum analysers.

F77 / F55 vs. VSAT – Coverage & availability

Where Inmarsat wins again over maritime VSAT is that typically VSAT systems use regional spot or hemi beams and once you sail out of coverage, your service and connectivity is lost. Space segment and backhauls need to be negotiated in each spot or VSAT beam to ensure continuous coverage. The

Inmarsat F77 / F55 service achieves very high levels of reliability and availability through the use of fully redundant components at Land Earth Stations, backup Network Co-ordination Stations (NCSs) and a fully backed-up Operational satellite constellation. The fade characteristics of L-band, for example during high precipitation, are superior to C or Ku-band. In addition to this, interference from other maritime C-band radar systems is much reduced.

F77 / F55 vs. VSAT - Data rates

Inmarsat F77 & F55 support packet data rates of up to 64kbps and circuit-switched rates of 56/64kbps

(and 128kbps for dual terminal ‘bonded’ channels). VSAT systems typically support data rates up to

2Mbps depending upon antenna size and satellite capacity.

F77 / F55 vs. VSAT - Regulations & licensing

It is always important to understand the regulations for VSAT, as any equipment installed on a vessel must comply with ship radio licensing requirements. It is necessary, for example, to check your flag state requirements for C and Ku-band.



2.3 Inmarsat Mobile ISDN

The Inmarsat Mobile ISDN service on F77 provides a global (and in the case of F55 a spot-beam), satellite-based extension of the terrestrial ISDN network to maritime users who would otherwise be unable to access ISDN. As urban-based organisations become more familiar to the features and capabilities of ISDN they will come to expect the same communications features and capabilities aboard their vessels. Many maritime Inmarsat customers already use Inmarsat systems for transferring data to and from their shore-side offices. As ISDN is made available by their terrestrial telephone service providers they too will wish to take advantage of the higher speeds and lower costs of the F77 / F55 mobile ISDN service for their maritime data communications needs.

It follows that demand for the Inmarsat Mobile ISDN service is clearly linked to the availability and growth of ISDN applications and services.

Because of the global growth of ISDN a whole range of telecommunications applications that were once the domain of large corporations have now become cost-effectively available to even the smallest of businesses. Dial-up networking using ISDN enables any number of Local Area Networks (LANs) to be quickly and easily linked. Using the Mobile ISDN technology maritime users can transform their shipboard communications environment into an ‘office that floats’.

Anyone who uses modems over traditional analogue telephone circuits will be familiar with the sound of two modems ‘handshaking’ and trying to connect, which can take 15-30 seconds of chargeable telephone time. An ISDN call typically takes less than 5 seconds to connect - a factor, which becomes even more significant when one is making a call over a satellite communications system.

While the use of Mobile ISDN to implement ISDN applications on board a vessel is a major benefit, it should not be forgotten that the Mobile ISDN service is also the most cost-effective means of transferring data over Inmarsat. While there may be additional equipment required to implement Mobile

ISDN - if no terrestrial ISDN line & Terminal Adaptor already exists - and line rental charges, the reduced call charges per kilobit will normally cover this cost many times over the life span of the terminal. In many cases, users will have covered the additional equipment cost within a matter of months.

With the introduction of the Mobile ISDN service there are no longer any reasons why those working in a maritime environment should not enjoy any of the sophisticated IT solutions that are taken for granted in today’s modern office.

The protocol implemented by Mobile ISDN on F77 and F55 is in fact Euro ISDN compatible and hence up to 10% more efficient that B-HSD.



2.4 Inmarsat Mobile Packet Data Service (MPDS)

Imagine one of your existing maritime customers is using the Inmarsat F77 / F55 terminal to access the

Internet. They are trying to find a local chandler for a particular piece of equipment, and so are using an

Internet search engine to find a supplier at a local port. Because they know that they are charged for every second they are connected, they hurry through the information, picking out the first couple of suppliers that they discover. If these suppliers cannot help them, they then need to reconnect to the

Internet and repeat the search.

However, the nature of the Internet means that, for the majority of the time for which they are connected, there is very little information being passed via the satellite. There is a flurry of activity when they first display each page, but there is ‘dead time’ while they are reading through the information on the screen, no more information is being sent or received.

Now imagine an alternative situation where, rather than being charged for the time for which they are connected, they are charged for the amount of information that they send and receive via the satellite.

They can now take their time, reading through the information, knowing that, however long it takes them to read the information on a screen, it is costing them nothing.

This alternative situation can now be achieved, using the Inmarsat Mobile Packet Data service

(MPDS). As this example demonstrates, the new service can provide significant cost savings to F77 /

F55 users when accessing information interactively.

With Mobile ISDN, the customer uses a dedicated line or channel between their mobile equipment and the satellite. This channel provides up to 64kbps of bandwidth. The customer is charged for the total length of time for which this dedicated channel is allocated.

MPDS works by allowing mobile users, covered by the same satellite spot beam, to share the channels available in that spot beam. As more users connect, they too are shared amongst the available channels.

Given that the bandwidth of each channel is fixed at 64 kbps, this means that the bandwidth available to each user is reduced when further users connect. Therefore, the mobile users may be aware that the speed of the service is slowing down.

However, Inmarsat systems monitor the MPDS channels to ensure they operate at optimum loading, adding further channels to the spot beam to maintain a service that is fit for purpose. During quiet periods, e.g. when a user is reading a web page or typing an email, the channels are free to be used by other mobiles. This is because only short maintenance bursts are sent to keep the network informed of the mobile’s status. (The cost of these maintenance bursts is considered an overhead and is not charged to the end user terminal.)

Currently the MPDS service is operated on a ‘best efforts’ or undefined bit rate (UBR) basis. This means the bandwidth available to an individual mobile may vary depending on the activity of other mobiles, but could be as much as 64kbps. In addition Inmarsat will add more channels as the traffic grows.

Given the variety of applications that can be used on the Inmarsat Fleet, there is a quick way of deciding whether the Mobile ISDN or MPDS is more appropriate for a particular application. As a general rule, if the application uses the Internet or involves human interaction (such as reading information on the screen, or inputting data via the keyboard), it is likely to show substantial savings by using packet data.



2.5 Inmarsat F77 / F55 applications overview

Inmarsat Fleet F77 and F55 are designed to accommodate the needs of a wide range of maritime users with large amounts of data to receive and transmit such as cargo & container shipping, oil & gas production & transportation, naval communications, fishing, passenger and cruise lines. The rest of this section includes a non-exhaustive list of some key applications that can be used over Inmarsat F77 and

F55. Where necessary these ‘technical solutions’ are explained in more detail in Section 4.

2.5.1 Navigation

Navigation is a general area that comprises location finding, using the most up to date charts, weather forecasting, tide and current predictions, route planning and route optimisation.

2.5.2 DGPS corrections

The optional Differential Global Positioning System (DGPS) service provides enhanced location determination for GPS. The standard GPS output is made more accurate with differential corrections received via an F77 / F55 terminal tracking an Operational Inmarsat satellite. Reception is made possible using a DGPS receiver tuned to the narrow-band 1200bps broadcast channel transmitted on all four Operational satellites. This is a subscribed service and a special receiver is required which is installed with the F77 / F55 terminal. The service providers continuously calculate corrections for the appropriate ocean regions and transmit these uni-directionally in real-time. Some F77 / F55 terminals have a convenient dedicated L-band receive output port specifically for this equipment, for others, a simple diplexer module can be used.

2.5.3 Navigational chart updates

In a similar way to the DGPS facility, application providers exist that provide continuous broadcast information including navigational charts. These are also broadcast at 1200bps on at least 3 Operational

Inmarsat satellites to provide global coverage. Once again a small L-band tuner and receiver unit are attached to the F77 / F55 terminal. The chart update package includes route planning and route optimisation software. More detail about the system is in section 4.

2.5.4 Obtaining weather reports

Detailed weather reports including precipitation, sea surface temperature, swell, wind speed & direction, ice pack, currents and tides can also be received either via the subscribed broadcast service described above or by FTP downloads for the specific area you are sailing. The other most obvious way to receive weather forecast and report information is via a typical Internet WWW session, which would normally be most efficient via MPDS. In this case all that is required is a PC with WEB-browsing software such as Microsoft’s Internet Explorer or Netscape Navigator. An example of this is shown in more detail in section 4.

2.5.5 Safety, distress, MRCC and Coast Guard communications (F77 Only)

The Fleet 77 distress service provides a multi-layered priority system allowing Distress, Urgency and

Safety calls to pre-empt lower-priority and routine calls. The pre-emption allows both the mobile and other shared resources such as Land Earth Station (LES) channel units and occupied satellite channels to be pre-empted and made available for the higher priority call if necessary (i.e. they are busy on lower priority calls). This applies to shore-to-ship calls as well as ship–originated. When installed correctly,

F77 (but not F55) can form part of a GMDSS safety system. For further detail on GMDSS and F77 call pre-emption see Distress / Safety / MRCC / Coast Guard (F77 only).



2.5.6 Interfacing with general analogue equipment

Using devices with analogue interfaces via an F77 / F55 MES (such as additional handsets, Group 3 facsimile, V-series voice-band data modems, STU-IIb/III secure phones and DECT handsets etc.) is possible via the AMBE voice service and the 64kbps 3.1kHz audio service. See Analogue systems –

Group 3 fax, modems and DECT for more details on how these services can be configured.

2.5.7 Secure communications

A STU-III SECTEL (Secure Telephone) can be attached to an F77 / F55 MES via the two-wire RJ-11 interface in exactly the same way as the V-series modem and G3 fax machine. Some F77 / F55 terminals and LESs will support STU – demodulation meaning that the STU call can be connected via the lower-cost ABME voice service at 2.4kbps rather than the more expensive 64kbps 3.1kHz audio service. Secure speech tested over a 64kbps 3.1kHz audio link has been found to be ‘highly intelligible’ and the voice quality rated ‘synthesised’. See Secure communications – STU and STE for more detail.

2.5.8 Fleet Management & the corporate WAN

Operators of Local Area Networks on board ship increasingly require connections with other LANs. It is possible to interconnect different networks transparently via F77 or F55, using, for example, TCP/IPbased protocols. More detail on corporate WAN access options is given below in Fleet Management &

access to the corporate WAN.

2.5.9 World-Wide-Web (WWW) access

Perhaps one of the most popular applications of F77 and F55 users is access to the Internet. A vast quantity of information useful to mariners is available via the World-Wide Web. This is readable with standard browser software either bundled with all popular operating systems (Internet Explorer- IE) or other vendors (Netscape Navigator). The principal way Internet access will be arranged through an F77

/ F55 terminal will be using a specially configured dial-up-networking session via MPDS. It is also possible via a Mobile ISDN call to an ISP or via a corporate intranet. It is worth noting that Internet access restrictions can easily be applied by an administrator, using content control software such as

NetNanny



from http://www.netnanny.com/ . More detail on access to the Internet via MPDS is provided below in World-Wide-Web (WWW) access. Remember that on F55, MPDS and Mobile

ISDN work in the spot beams only.

2.5.10 Email

Electronic mail is becoming one of the most popular mechanisms for communicating at sea. Because of the different time zones and 24-hour nature of Global maritime operations, ‘office hours’ may not coincide so detailed messages must be left for later retrieval and action. An email composed off-line and sent via an F77 / F55 terminal into the corporate mail system can be ideal for this purpose. To achieve the most cost-effective maritime email service, however, may require not just a PC with email client software and shore-side email or Internet accounts, but a correctly configured dial-up networking connection, email compression software and ensuring that your mail client/server settings have been optimised for satellite networks. Several solutions and techniques exist to achieve this and they are further below in Email via F77 / F55.

2.5.11 Ship-to-ship communications

Ship-to-ship communications via F77 / F55 will typically be via the 4.8kbps AMBE voice service, dialled as a mobile-to-mobile call. Useful directory information is available on-line directly from the

Inmarsat website on vessel identities and contact numbers.

Visit http://www.inmarsat.com/ship_directory.cfm

for this unique service.



2.5.12 Cargo / vessel telemetry

The principle of telemetry is ‘measurement at a distance’. It allows the essential parameters of either a ship’s cargo or even measurements of the vessels operational systems on board to be transmitted to a remote centre where the appropriate expertise can be focussed and fleet or cargo management decisions taken. These may require maintenance to be undertaken or some corrective action relating to the ship’s cargo or even vessel re-routing. Sensors or transducers around the vessel will typically be producing small quantities of data at regular intervals. Applications relating to telemetry are frequently tailor-made as the specific nature of the systems being monitored varies so widely between companies. More detail and an example using MPDS via F77 / F55 is given below in Cargo / vessel telemetry via MPDS.

2.5.13 Crew calling (welfare)

Ship owners and managers are fast realising that a convenient voice service, provided for the shipboard staff, can make a happier, safer and more productive crew. It is now easy to provide some remote telephones, installed in private areas, which accept money or cards to pay for calls home. Several

LESOs provide pre-paid calling card services, which are also ideal for this purpose. See Crew calling

(welfare) via F77 / F55 below for more detail.

2.5.14 Videoconferencing

Users can enjoy full videoconferencing facilities from virtually anywhere on the ocean. International standards exist which are widely implemented and which are ideal for use over F77 / F55 allowing simultaneous video and audio. More detail is provided in Video conferencing.

2.5.15 Using Microsoft

 NetMeeting

With NetMeeting on F77 / F55, maritime users can not only undertake a low-resolution videoconference but also enjoy advanced application sharing facilities such as a shared ‘virtual’ desktop and creative ‘white boarding’. More detail is provided on installing and configuring MSN Messenger

Service and NetMeeting below in Using Microsoft

 NetMeeting via F77 or F55.

2.5.16 Universal Messaging

Universal messaging is the ability to send messages via practically any medium or communications system to a group of individuals simultaneously. It has been implemented by some companies via websites, which allow messages to be created and dispatched to a target group using a large variety of media including synthesized text-to-speech voice calls. More information is given in Universal

Messaging via F77 & F55.

2.5.17 Voice and data multiplexing

A 64 kbps data channel may be used to carry up to eight multiplexed (or combined) telephone, fax and medium-speed data circuits. This capability may interest Fleet users where multiple telephone lines are required for example with passenger calling in the cruise industry or for simultaneous welfare calling by ship’s personnel. Alternatively it will provide the capability to have a data connection to the corporate

WAN and simultaneously support several compressed voice channels. Sophisticated multiplexing equipment is available for this application (for example the V100 from Vocality International Ltd), which can efficiently multiplex 4 to 8 voice/fax/data (V.32) channels plus a LAN connection onto a

64kbps F77 or F55 Mobile ISDN call. Any unused voice call capacity (including speech interpolation on active calls) is dynamically allocated back to the LAN connection. More detail on multiplexing is provided in Voice and data multiplexing via F77 / F55.



2.5.18 File transfer

This application is the transmission of large files to or from shore. An example could be image files or seismic recording data. Several options exist for such transfers and some equipment and protocols can be recommended which have been optimised for Inmarsat F77 & F55. Unless the session is interactive it is expected that Mobile ISDN would be the preferred communications mechanism for File Transfer rather than MPDS. More detail on file transfer is provided below in File transfer with F77 & F55.

2.5.19 128kbps channel ‘bonding’

If an enhanced data rate is required, two F77 or F55 terminals can be installed on a single vessel and have their two channels ‘bonded’ - through the use of external equipment such as Livewire’s ISDN

Integration Unit (IIU) - whereby two 64kbps UDI channels can be aggregated together to produce a single 128kbps aggregate channel. Some F55 terminals even support a dual channel bonding mechanism internally. See 128kbps channel ‘bonding’ below for details.

2.5.20 Group 4 facsimile

Group 4 fax machines are designed for use over ISDN, offering faster transmission speeds, higher quality and improved transmission reliability. The main benefit of Group 4 is that it uses a digital network throughout and so does not convert the scanned information into an analogue format before transmission. With ISDN, it typically takes only six seconds to transmit an A4 page rather than about 45 seconds for Group 3 machines. More detail on fax delivery / retrieval options is provided in Facsimile

via F55 / F77.

2.5.21 Telex

Although a direct connection to the Telex network (such as the Inm-B service) is not supported on F77 or F55, users who wish, can send and receive Telex messages via a Telex interworking agent. Service providers exist who can offer an email or Internet interface to a private ‘virtual’ Telex account.

Messages can be created as a mail document and forwarded via a ‘send Telex’ mailbox and telex number to an interworking server. The messages are then automatically forwarded by Telex-net and distributed to the correct Telex addresses. Confirmation of the message status is then returned to the sender. Using these providers, other features are available such as multi-addressing, conversational telex, message routing, desk top printing, message notification, search requests, ‘legal document’ and message status reporting.

2.5.22 Tele -presence

Tele-presence can bring remote expert assistance directly to the ship, such as in cargo or vessel damage

& insurance assessments or advice on the repair of ship engines for example, avoiding the expense and delays of transporting and co-ordinating a ship visit by a specialist.

2.5.23 Tele -medicine

Inmarsat F77 / F55 can provide rapid access to remote medical expertise, using interactive audio-visual and data communications measuring a patient’s vital signs. Systems such as Vital Link



1200 from http://www.telemedicsystems.com/ have been specifically designed for just this purpose. Use of such equipment can assist medical professionals to take decisions that can save lives or avoid costly ship diversions if unnecessary.

2.5.24 Tele -education

Inmarsat F77 / F55 can support tele-education applications such as the training of staff whilst embarked, on installation, maintenance and emergency procedures. The resulting savings in expenses and travel can be significant.



3. Overview of the Inmarsat system

3.1 F77 / F55 Coverage map



The previous coverage map shows the areas of F77 / F55 global and spot beam coverage of each of the four satellite regions. Each of the four ocean regions operates as a separate network. In areas where regions overlap, as shown on the map, the separate networks are defined by either mobile antenna discrimination (for Inm-A, Inm-B, mini-M and F77 / F55) or by frequency (for Inm-C, Inm-D+).

Mobile antenna discrimination means that antennas with sufficient size (and hence gain) can receive and transmit to one satellite without causing interference to or receiving interference from another satellite.

The user of a mobile earth station with a small antenna, however, must determine which satellite to use by its frequency (in such cases, of course, frequencies cannot re-used between overlapping regions).

F77 and F55 operate within the full global beam coverage area of the Inmarsat satellites and like

Inmarsat-B, take advantage of the added power of spot beams when in coverage.

3.2 Inmarsat 4 Coverage extension

An extension is now being implemented for all existing spot-beam services, to include the following:

•

Fleet F55 MPDS, 9.6Kbit/s Fax option, 64K Mobile ISDN and 3.1Khz Audio

•

Fleet F77 128Kbit/s Mobile ISDN

Following the implementation of the Inmarsat 4 satellites, coverage for these services is planned to be extended to include the full IOR and AOR-W areas served by Inmarsat 4 satellites (N.B. at the time of writing, IOR coverage has not as yet been extended – for the latest status, please visit www.inmarsat.com/coverage ).

The spot-beam service coverage extension planned via the Inmarsat 4 satellites is represented by the shaded area above.

3.3 Network Operations Centre (NOC) and LESs

In each ocean region there is a Network Co-ordination Station (NCS), which manages and co-ordinates the telecommunications traffic in that region. The NCS assigns available communication channels to the

Mobile Earth Stations (MESs). When a channel is no longer required, it is released to be allocated later to another MES when required. Typically, the NCS function is performed at a particular Land Earth

Station (LES) under contract to Inmarsat. Of all the Inmarsat systems, Inm-M, Inm-B, mini-M, F77 and F55 actually all use the same NCS in each Ocean Region. The Network Operations Centre (NOC) at Inmarsat’s headquarters in London, England performs co-ordination of the network 24 hours a day,


Inmarsat Confidential F77 & F55 Services and Applications Reference Manual every day. The NOC maintains contact via dedicated satellite and terrestrial links with the NCSs and

LESs in all Ocean Regions.

Land Earth Stations (LESs)

As shown below, the Land Earth Stations (LESs) are the gateways, which provide the link between the satellites and public terrestrial telecommunications networks. Each LES communicates with just one of the four Inmarsat satellites and is thus said to serve a particular Ocean Region. Often single LESs are situated within the footprint of more then one Ocean Region and thus are able to offer multiple Ocean

Region coverage from a single location. LESs are owned and operated by national telecommunications operators and other authorised private telecommunications organisations. LES operators compete alongside AA’s and ISP’s with each other for Inmarsat customers’ traffic. Thus, customers will find it beneficial to ‘shop around’ to determine which LES offers the best services and most economic traffic charges for their particular communications needs.

3.4 How F77 and F55 calls are routed & billed

Telephone calls over the Inmarsat satellites can be made from either the mobile satellite terminal

(mobile-to-fixed calling) or from a normal terrestrial telephone line (fixed-to-mobile calling). The point of origination of the call (i.e. from the satellite terminal or from a terrestrial line) determines the manner in which the call is routed and billed.

Mobile-to-fixed call routing

The Mobile Earth Station (MES) operator makes the selection of the LES by either using the default

LES programmed into the MES for each ocean region or by entering the LES code in the dialling string for a particular call in accordance with the MES manufacturers’ instructions. The LES operator using its own national or international routing arrangements carries out terrestrial routing of the call to its final destination.

Fixed-to-mobile call routing

When a land-based fixed subscriber wishes to make a call to an F77 or F55 terminal, the terrestrial network needs to be able to recognise the dialled Inmarsat Mobile Number (IMN), route the call and bill the call at the correct tariff. The subscriber’s telecoms provider therefore needs to have put into place appropriate routing arrangements with one or more LES operators in order to handle Inmarsat fixed to mobile calls. Some telecoms providers have their own LES. However, they will still have to make routing arrangements with LES operators in other ocean regions as only the large LESOs can ‘see’ more than two Inmarsat satellites.



These routing arrangements require that the telephone service provider’s exchange recognises not only the ocean region dialled but also the type of Inmarsat call to be made (as determined by the T or type digits just after the country code) so that the call can be routed to an LES offering the desired service in the correct ocean region. This information is also required so that the call can be charged at the correct tariff.

In 1996 a new ITU Single Network Access country Code (SNAC) of 870 was allocated to Inmarsat which allows a caller to a digital Inmarsat mobile (such as F77 / F55) to dial the same number irrespective of which Ocean Region the mobile is located. This was part of the Inmarsat Mobility

Management (MOBMAN) initiative, which also enabled GSM-like value-added services such as automatic voice, fax mailboxes and call forwarding to be provided by LESs. SNAC (870) has now been implemented by a number of national PTTs.

In summary then, the fixed subscriber cannot determine the routing of calls made in the fixed-to-mobile direction but is dependent upon the routing arrangements made by the telephone service provider. Most

PTTs and private telecom operators have the appropriate routing arrangements in place for standard

Inmarsat services including F77 & F55. However there are some PTTs in less developed countries or smaller private operators that do not provide these routing arrangements. There are also some PTTs that while able to route voice services are unable to route data services fixed to mobile. If the customer is based in one of these countries they can still be provided with a fixed to mobile solution operated by a number of service providers and LESs.

Mobile-to-mobile calling

Mobile-to-Mobile calling is supported for F77 / F55 services. There is of course twice the end-to-end delay because of the double satellite hop, which is likely to reduce the throughput and performance of many user applications.



Mobile-fixed and mobile-to-mobile billing

When a call is made from an F77 or F55 terminal the call charge is composed of two elements; the satellite portion comprising the call from the MES to the LES via one of the Inmarsat satellites and the terrestrial portion (or back-haul)

1

, which is the delivery of the call from the LES to the final PSTN or

ISDN destination. An MES user can make a call using any LES within the ocean region of operation that supports the Inmarsat service required.

However, different LESs will have different tariffs, usually structured as charge-bands based on the destination called, and it makes good business sense to ask your AA or ISP for the most relevant tariff system for your vessel.

The Accounting Authority (AA) or ISP usually bills F77 / F55 calls made in the mobile-fixed and mobile-to-mobile direction in the same manner as other Inmarsat maritime services are billed. See

Service Activation and MES requirements for more detail.

Fixed-to-mobile billing

Call charges for fixed subscriber originated calls are set by the telephone service provider or PTT and cannot be influenced by the subscriber and in some cases can be rather high. However, in countries where the telecommunications service has been deregulated there will normally be a choice of telephone service providers thus enabling a fixed subscriber to have a choice of tariffs. Many LESs and service providers have also introduced two-stage dialling methods to by-pass the default national PTT routing agreements, and will have separate billing arrangements (and often more cost effective call charges) for the Inmarsat portion of the call. Otherwise the telephone service provider bills calls made in the fixedmobile direction.

1

The terrestrial delivery or back-haul should always be via a terrestrial cable network to avoid the issues associated with double-hops. Special call markers within the PSTN and ISDN signalling systems indicate that a satellite hop has already been included (‘SAI’) so subsequent routes should only be cable. Occasionally, however, a second hop may be unavoidable, on, for example, an F77 / F55 call to a PSTN number within an undeveloped national network where only satellite is available.



4. Inmarsat F77 / F55 Technical Solutions

4.1 Mobile ISDN BRI interface

Because the Inmarsat F77 / F55 MES is fitted with an ISDN Basic Rate Interface (BRI), the use of any

ISDN device is greatly simplified when compared to the systems integration and additional router equipment that had to be procured to run an ISDN device over an Inmarsat –B HSD terminal.

Inmarsat F77 & F55 support all the ISDN protocols that can run over a B channel found on an ISDN line. These include all the popular ISDN protocols such as X.75, PPP, HDLC, V.120 and V.110. Also, if new protocols are developed these will also run over a Mobile ISDN link. (Note: V.110 is only supported at 56 kbps).

However, Inmarsat F77 / F55 does not actually implement any of these protocols. The implementation of the protocols is found in the Terminal Adapter or in the software on the PC. The Inmarsat F77 / F55 is merely a pipe that supports a 64kbps data stream.

Because Mobile ISDN provides a pipe in the form of a B channel just like ISDN, it can benefit from new developments in ISDN that send data more efficiently or with extra features such as compression or encryption. For example, many Terminal Adapter vendors now provide V.42bis compression as standard in X.75 and V.120. These have been developed many years after end-users have installed their ISDN lines but they can run these new protocols without changing their ISDN line. The same applies to Mobile ISDN. For the first time in the mobile satellite world, satellite end-users will be able to tap into a much larger data communications world in the form of ISDN and benefit from the huge amount of ongoing investment in new ISDN technologies.

All Inmarsat F77 / F55 MESs are compatible with Euro ISDN and so the ISDN device to be used with

F77 / F55 must also support this ISDN standard, which is often configurable either by software or replacement of a chip within the device.

In the event an ISDN device is not fitted with an ISDN BRI then it can usually be used with an

Inmarsat F77 / F55 MES in conjunction with an ISDN Terminal Adaptor.

Some ISDN applications requiring 2 B-channels (such as 128kbps video conferencing) can now be supported using the channel ‘bonding’ technique described in 128kbps channel ‘bonding’. Such applications may need some specific configuration. Advise on these applications can be provided by an experienced integration provider.

This document describes most of the more commonly used F77 / F55 applications (both ISDN and non-ISDN) together with any specific configuration issues that may need to be addressed when they are used with the Inmarsat F77 / F55.

N.B. A new, dedicated channel 128Kbps service option will now be provided on Fleet F77

(planned from Q1 2005). See section 6.1 for further details.



4.2 Inmarsat Mobile ISDN versus Mobile Packet Data Service

The Inmarsat Mobile Packet Data Service (MPDS) has been developed to provide a way of delivering mobile packet data over satellite, which is more efficient and flexible than anything that can be achieved by satellite at the moment.

With the Mobile ISDN service, the customer is charged for the time for which they remain connected, regardless of how much data they transfer. The key advantage of the new Inmarsat Mobile Packet Data is that the customer will only pay for the amount of information that is sent over the network. This allows the customers to work in a similar way regardless of whether they are in the office or onboard ship.

This is achieved by allowing channels from the ships to the satellites to be shared by several users, and makes more efficient use of the satellite network.

As already mentioned, there are still situations in which Mobile ISDN is more appropriate.

There are a small number of software applications that make up the majority of all shipboard data use.

•

Internet access

•

Email

•

Document or File transfer

•

Accessing a local area network or corporate intranet

At any point in time, each of these applications uses different amounts of bandwidth on the network, depending on what it is doing. Most applications use less than half of the available bandwidth at any given time. Therefore it follows that on a circuit switched service such as Mobile ISDN, the user would be paying for, but not using, 100% of the channel. Using Inmarsat MPDS the customer will pay for just the data that is transmitted or received over the network.



The chart below shows cost curves for a typical Inmarsat Mobile Packet Data application like web browsing where data transmission is sporadic rather than continuous. The chart compares the cost of running such an application over Mobile ISDN, which is shown as a steadily increasing line reflecting the per minute charges associated with a switched circuit, and the cost of running such an application over Inmarsat Mobile Packet Data, which is shown as a flat line which increases only when data is being transferred. Clearly then, for data transfers of a sporadic nature, the Inmarsat MPDS service will be more cost effective than the Mobile ISDN service.

Inmarsat Mobile ISDN vs. MPDS cost comparison

It follows also that if the application is transferring data continuously then the Inmarsat Mobile Packet

Data charge curve will go above the circuit switched charge curve and it would be appropriate to advise the use of the Mobile ISDN service for that particular application.

As a general rule, if the application uses the Internet or involves human interaction (such as reading information on the screen, or inputting data via the keyboard), it is likely to show substantial savings by using packet data. The following chart summarises the appropriate use of either Mobile ISDN or

Inmarsat Mobile Packet Data for various popular applications.

Choosing Inmarsat Mobile ISDN .v. MPDS for popular applications.



4.3 Navigational chart updates

Most ECDIS (Electronic Chart Display Information System) manufacturers and electronic chart suppliers now provide a chart correction or download capability, for example Transas



(see http://www.transas.com/ ) and C-Map



(see http://www.c-map.com/ ). Another example is the

ChartManager



paper chart correction and MetManager



weather service from ChartCo



(see http://www.chartco.com/ ). Charts and specific updates can be obtained directly by a subscribed customer connecting with the service provider’s specialized websites via MPDS or Mobile ISDN.

Services such as these (with dedicated software) can process and display chart updates published by the

UK Hydrographic Office (UKHO), Digital Notices To Mariners (DNTMs), maritime news such as the

Lloyds List Broadcast and weather updates. Charts and updates are also broadcast at 1200bps on at least 3 Operational Inmarsat satellites to provide global coverage. With this system a small L-band tuner and receiver unit are attached to the F77 / F55 terminal (non-intrusively and receive-only) and dedicated software processes and displays chart updates published by the UK Hydrographic Office

(UKHO), Digital Notices To Mariners (DNTMs), maritime news such as the Lloyds List Broadcast and weather updates. Chart update packages often also include route planning and route optimisation software.

An example digital chart is shown below:

The UK Maritime & Coastguard Agency (MCA) accepts these for the purposes of complying with the carriage requirement for Notices to Mariners under Regulation 20 of the Safety of Life at Sea (SOLAS)

Convention and the Merchant Shipping (Carriage of Nautical Publications) Regulations 1998.



4.4 Obtaining weather reports

Like electronic charts, weather information can also be obtained for your specific sailing area or region by email or FTP. Numerous Internet WEB sites also exist for this purpose such as NowCasting



(see http://www.nowcasting.ie/ ), Transas



(see http://www.transas.com/ ), ChartCo



(see http://www.chartco.com/ ) and C-Map



(see http://www.c-map.com/ ) and WNI OceanRoutes



(see http://www.oceanroutes.com/ ), and can be viewed and saved as described in the section on general

WWW access via F77 / F55. Alternate services also exist which provide continuous broadcast data on

Operational satellites to passive demodulators and receivers. These are driven by custom software and produce weather charts similar to that shown below.

Reception of these signals as well as DGPS corrections and navigational chart updates is made possible using a dedicated receiver unit tuned to the narrow-band 1200bps broadcast channel transmitted on the

Operational satellites. This is a subscribed service and a special L-band tuner and receiver is required which are installed with the F77 / F55 terminal. Some F77 / F55 terminals have a dedicated L-band receive output port specifically for this type of equipment. If this is not available a simple diplexer module can be used.



4.5 Distress / Safety / MRCC / Coast Guard (F77 only)

The Global Maritime Distress and Safety System (GMDSS) makes certain mandatory requirements on vessels over 300 gross registered tonnes and all passenger ships on international voyages. They require the vessel to have two independent means of achieving the following (for the sea areas in which the vessel operates):

•

Transmitting ship-to-shore distress alerts

•

Receiving shore-to-ship distress alerts

•

Transmitting and receiving ship-to-ship distress alerts

•

Transmitting and receiving search and rescue co-ordinating communications

•

Transmitting and receiving on-scene communications

•

Transmitting and (as required) receiving signals for locating

•

Transmitting and receiving maritime safety information

•

Transmitting and receiving general radio-communications to and from shore-based radio systems or networks

•

Transmitting and receiving bridge-to-bridge communications

‘Independent means’ also requires separate power supplies – as there should be no single point of failure affecting both communications systems.

The four sea areas are defined thus;

Area A1

is within range of VHF coast stations with continuous DSC alerting available (about 20-30 miles).

Area A2

is beyond area Al, but within range of MF coastal stations with continuous DSC alerting available (about l50 miles).

Area A3

is beyond the first two areas, but within coverage of geostationary maritime communication satellites. This covers the area between roughly 76º North and 76º South. In practice this means

Inmarsat.

Area A4

is the remaining sea area. The most important of these is the sea around the North Pole (the area around the South Pole is mostly land). Geostationary satellites, which are positioned above the equator, cannot reach this far.

This chart shows an example of sea areas

A2 and A3 around Northern Europe.

For example, within areas covered by A3,

Inmarsat–C will frequently be used in conjunction with F77.



The International Maritime Organisation (IMO) Resolution A.888 (21) states that any system being designed for use in the GMDSS after 1 February 1999 should be able to recognize the four levels of priority:

Distress; Inmarsat Priority 3 (P3)

Urgency;

Safety;

Other (general/routine)

Inmarsat Priority 2 (P2)



With prioritisation and pre-emption, the rescue authorities will always get a call through to a ship, even if the voice or data channel is already in use at a lower priority. Pre-emption works in a hierarchical way:

•

A distress (P3) call will pre-empt all other communications.

•

An urgency (P2) call will pre-empt both safety (P1) and routine (P0) calls.

•

A safety (P1) call will pre-empt a routine (P0) call.

The IMO resolution also requires that new systems should give appropriate access for communications in both ship-to-shore direction and shore-to-ship direction for distress, urgency and safety traffic originated by Maritime Rescue Co-ordination Centres (MRCCs) or other search and rescue authorities.

In other words, all new systems must provide prioritised pre-emption. Inmarsat Fleet F77 meets these requirements with carefully designed call prioritisation - as standard - in the F77 specification allowing both from and to-mobile calls to be given priority resources to complete the call. Provision of preemption in both directions places a requirement upon Inmarsat land earth stations (LESs) and NCSs to offer this safety functionality. Inmarsat Fleet F77 is the first and only satellite communications product to enter GMDSS that is capable of meeting the latest criteria stipulated by the IMO for new systems.

Satellite system availability is also stipulated in the same IMO resolution: better than 99.9% for shipshore distress alerts. Inmarsat consistently exceeds this figure. See http://www.inmarsat.com/safety/.

Special Access Codes

The following table shows two-digit codes (“SACs”) designated for P1/P2 calls, as recommended by

Inmarsat Safety services. Please contact your LESO for further information:

32 Medical Advice Use this code to obtain medical advice. Some LESOs have direct connections with local hospitals for use with this code.

38 Medical assistance This code should be used if the condition of an ill or injured person on board the vessel requires urgent evacuation ashore or the services of a doctor aboard the vessel. This code will ensure that the call is routed to the appropriate agency or authority ashore to deal with the situation.

39 Maritime assistance This code should be used to obtain maritime assistance if the vessel requires assistance or a tow or has encountered oil pollution etc.

41 Meteorological reports

This code should be used by weather-observing vessels to send their observations. In most cases where this service is available the service is free of charge to the vessel, the national weather authority paying the relevant charges

42 Navigational Hazards and warnings

This code provides a connection to a navigational office for transmission of information from the vessel about any hazards which could endanger the safety of navigation (e.g. wrecks, derelicts, floating obstructions, defective radio beacons or light vessels, icebergs, floating mines etc.)

43 Ship position reports This code provides a connection to an appropriate national or international centre collecting ship movement information for search and rescue (or other) purposes e.g. AMVER or AUSREP etc.



The F77 Distress Button

The distress function on an F77 is initiated via dedicated button(s) attached to the BDE (the Nera F77 example is shown right). The button must have a protection mechanism against accidental activation. As an additional precaution, the distress button must be held down for at least 6 seconds before the distress voice call is activated.

Marine Equipment Directive ‘Wheelmark’

The new IEC International standard (IEC 61097-13) has been published which covers the requirements for maritime communications equipment

Ship Earth Stations (SES).

In Europe, Fleet F77 equipment approved in accordance with the above

IEC standard will be eligible to be endorsed with the ‘wheelmark’* approval symbol, shown right:

* Fleet F77 is currently referenced in the EU Marine Equipment Directive (MED) Annex 2, and must be moved to Annex 1 before a Wheelmark can be issued. At time of writing this has been requested.

Please check with the EU website for the latest status: http://www.mared.org/



4.6 Analogue systems – Group 3 fax, modems and DECT

The F77 and F55 analogue services

The 64kbps 3.1kHz audio service enables an F77 / F55 MES to be used to establish high quality circuitswitched analogue connections for communications with other analogue devices via the PSTN. The

Speech service can be used for high quality voice connections via an ISDN handset and the 3.1kHz

Audio service enables the attachment of analogue communications devices such as G-3 fax machines, modems, STU secure phones and DECT base stations. The F77 / F55 analogue RJ-11 port emulates local exchange line conditions such as 600-ohm impedance, ‘battery voltage’ of approx 40 VDC, dial tone and ring current. Remember when dialling from-mobile via an analogue port on the F77 / F55 to always terminate the dialling string with a ‘#’ symbol.

Group 3 facsimile

Virtually any Group 3 fax machine can be attached to an F77 / F55 MES via the RJ-11 analogue port assigned to the 64kbps 3.1kHz audio service. Alternatively this can also be achieved by using an ISDN

Terminal Adaptor (TA) connected to the MES via the BRI interface and the G3 fax machine connected to the TA using the two-wire RJ-11 interface. In both cases to make an incoming fixed-to-mobile call reach a particular device, an MSN number and valid terminal ID for the 3.1kHz data service must be programmed into the MES. The same MSN would then have to be programmed into the TA. Both of these operations will be described in the manufacturers instructions. Tests have shown that the modems of modern G3 fax machines will train up to 33.6kbps via the 3.1kHz audio channel.

An F77 and F55 MES can now (optionally) also support the 9.6kbps Inm-B fax service. This is a highly cost-effective means of sending Group 3 fax via both Fleet F77 and F55. This service is also provided via the F77 / F55 Fax Interface Unit (FIU) though an (appropriately configured) RJ-11 connector on the

MES.

Analogue modems

Virtually any voice-band-data V-series modem can be attached to an F77 / F55 MES via the two-wire

RJ-11 interface in exactly the same way as the G3 fax machine. Remember to configure the ATDT

Hayes dialling string with a terminating ‘#’ pound sign. Tests have shown that most V.90 modems cannot support the delays inherent in a satellite link and that connections will normally back down to

V.34 at 28.8kbps.

Digital Enhanced Cordless Tele-comms (DECT)

DECT is likely to provide limited range in metal-walled ships such as tankers or carriers but should give good performance in fibreglass vessels such as yachts. Any Inmarsat F77 / F55 MES may be used with a DECT telephone system but it will require a DECT base station on one of the RJ-11 voice ports on the BDE. This port should be configured for the telephony service required, (AMBE voice or 64kbps

3.1kHz audio).

Handsets and base stations complying with the popular DECT standard improve the performance of cordless phones in three important areas - speech quality, security against eavesdropping, and immunity from radio interference between nearby cordless phones. Since 1993, DECT has been a mandatory standard throughout the EU. Member countries have set aside radio frequencies in the 1.88-1.9GHz for

DECT. Worldwide the DECT standard has been adopted in 26 countries.

The key benefits of DECT are:

•

High capacity.

•

High speech quality (32 kbps ADPCM)

•

DECT uses encryption so that radio eavesdropping is virtually impossible.

•

Standby of 45 hours and talk times of nine hours are commonly available.



4.7 Secure communications – STU and STE

A secure telephone (SECTEL) is a device that connects to a telephone line and provides a variety of security services to the conversation or information that is being transmitted. Most secure telephone devices also have data ports for the connection of a computer or fax machine.

The most widely available types of secure telephones are the Secure Telephone Unit (STU) - III (USA) and the Speakeasy (Aus). The STU-III is by far the most widely used and has become in effect the de

facto global standard in secure communications. The STU-III looks like a typical telephone but provides end-to-end security between any two STU-III devices, even those manufactured by different vendors. STU uses a form of V.26 & V.32 modulation but with a heavily modified training pattern. The

STU-III was developed in 1983 for use over an analogue telephone line. The STU-IIB is a variant of the STU-III in use by NATO and some non-NATO countries such as Australia and New Zealand.

Three vendors are licensed by the US Government to manufacture the STU-III - Motorola, GE and

AT&T. About 400,000 STU-III SECTELs are in use and Motorola dominates the market with about

50% market share. Although the STU-III is no longer manufactured AT&T still provides spares and support for all models.

Four classes of STU-III exist as follows: -

Class

Type 1

Type 2

Usage

Classified US Govt only

Non-classified

Type 3

Type 4

Commercial – US only

Commercial – exportable

Classes of STU-III SECTEL

Types 1 and 2 must be compatible between manufacturers whereas Types 3 and 4 are usually manufacturer-specific. Types 1 and 2 are no longer manufactured and have been superseded by the

Secure Terminal Equipment (STE).

Secure Terminal Equipment (STE) is the next generation STU-III. STE offers backwards compatibility with STU-III while taking advantage of digital communications protocols like ISDN and ATM. The cryptographic key for STE is held on a removable PCMCIA card for additional security. STE is currently available as an ISDN Terminal Adaptor and supports both encrypted voice and data.

Inmarsat F77 / F55 supports STU-III, STU-IIB and STE. The configurations for STU-III and STU-

IIB, both of which are analogue devices, are the same and are different to that of STE, which is a digital device. An STE telephone is normally capable of emulating a STU-III telephone.



STU & STE configuration

The STU-III and STU-IIB are analogue devices and so should be connected to the MES as described above for general analogue devices. The STE is an ISDN device and is supplied with an ISDN BRI interface. The STE should be connected to the MES, as shown below, using the RJ-45 BRI interface on the MES and the port configured with an MSN appropriate to the 64kbps UDI or 56kbps data service as required.

STU/STE configuration

Some LESOs working with certain F77 MES manufacturers provide a STU-IIb / III service via the

4.8kbps AMBE voice channel. This is supported through a STU modem demodulation technique and is significantly more cost-effective than using a 3.1kHz analogue (64kbps) channel.



4.8 Fleet Management & access to the corporate WAN

The concept of linking or networking computers within a single site thus creating a Local Area Network or LAN is familiar to most of us and these LANs are becoming increasingly common aboard vessels.

There is also an increasing demand for these remote LANs and individual remote users to access a central or headquarters LAN to deposit or retrieve data such as email thus creating a Wide Area

Network or WAN.

Remote access of this nature is normally and most effectively implemented using LAN routers or bridges. Routers and bridges manage the transfer of data between LANs and are manufactured as individual units or as combined bridge/routers. Though routers and bridges differ in mode of operation, the implementation of each is similar and so the term router is used below to refer to either a bridge or router or hybrid.

Remote LAN Access via F77 / F55

When the amount of data to be transferred between two LANs or a central LAN and a remote user is large then a dedicated or leased circuit, whether terrestrial or satellite, will provide the most economically attractive communications solution. However, in many instances the amount of traffic is insufficient to economically justify a leased circuit. The use of an ISDN dial up connection, either Basic

Rate or Primary Rate, can be an attractive solution to provide the telecommunications link required.

With a dial-up connection the router has no dedicated connection to the central LAN. Instead, the router automatically connects to the other router when there is data to be transmitted. Once a connection has been established it will be held open for traffic. When there has been no traffic for a pre-determined length of time, selected by the user, the router will automatically clear the call. Some routers will take a fixed minimum time to disconnect, in which case it is recommended that there is a

‘guarding’ function in the application.

However, unless the vessel is alongside she will not have access to terrestrial ISDN. The Inmarsat F77 /

F55 service is ideally suited to this application, even – in some cases - while the vessel is in port. Using an Inmarsat F77 terminal, a user can connect a remote user or LAN from anywhere within the Inmarsat global coverage area (spot beams for F55). Any router with an ISDN BRI interface can be connected to an Inmarsat F77 / F55 terminal to provide remote LAN access.



At the fixed site no special modifications are required for use with Inmarsat although it is generally good practice to use the same routers at each end of the link or at least routers from the same manufacturer in order to take maximum advantage of any special features they possess.

Router optimisation

The most common protocol developed to interconnect various networks is called the Internet Protocol

(IP). Two transport layer protocols were developed with IP - TCP and UDP. TCP (Transmission

Control Protocol) provides a reliable end-to-end service by using error recovery and re-ordering. UDP

(User Datagram Protocol) makes no attempt at error recovery. TCP/IP is very suitable for use over a satellite link. Inmarsat does not encourage the use of proprietary protocols but realises that the business application might require these in order to work with legacy applications or networks.

Since both terrestrial ISDN and the Mobile ISDN service charge by connect time it is important to not only connect when there is useful data to send but also to minimise the connect time and maximise the data throughput once connected. LAN protocols like TCP/IP were developed for a local environment where bandwidth is free and are therefore potentially very ‘chatty’ i.e. if they were used as is across an

ISDN or Mobile ISDN network they would probably keep the link alive for most of the time resulting in high traffic charges - particularly when used on a satellite circuit. Routers to be used with an ISDN or

Mobile ISDN network must be optimised not only to perform the connections to the network to route the data but also to minimise the connection charges.

Data filters

There may be many workstations or servers connected to a remote network and it can be very easy for a user to forget that the router is automatically configured to make a Mobile ISDN call whenever it sees any data destined for the central LAN. Filters can be used to eliminate most of the traffic generated by these users from initiating a Mobile ISDN call so that only authorised users can generate the remote connection.

Router data compression

Once a connection has been established it is important that the application maximises the use of the available bandwidth. A router with data compression can transport up to twice as much data across a

Mobile ISDN link. There are several different compression services available to the customer. Some are provided by LESs and are therefore dependent on using the LES concerned or alternatively there are also a few independent service providers that offer specialist satellite compression systems.

IPX spoofing

Some network protocols (such as Novell IPX) are very ‘chatty’ with the central server sending messages to each remote user every few minutes - even when there is no data to send. In a network using Mobile ISDN or terrestrial ISDN these ‘keep alive’ messages can significantly increase the traffic charges. The routers should be configured to implement a ‘spoofing’ protocol whereby the router responds to the ‘keep alive’ messages from the network without actually bringing up the communications link.

Remote LAN access - cables and interfaces

For the Mobile ISDN Service, the router should be connected to the RJ-45 BRI interface on the MES and an MSN assigned appropriate to the 64kbsp UDI or 56kbps service as required. When using

MPDS the router must be specified with an RS-232 serial interface and connected to the RS-232 port on the Inmarsat F77 / F55 MES. Note that the configuration of a customers router or firewall is not advised without appropriate training and in a real-life situation the customers’ IT specialists would normally insist on carrying out this task as well as managing their IP address allocations for reasons of network security.



4.9 World-Wide-Web (WWW) access

4.9.1 How to set up Win2000 MPDS dial-up networking

MPDS enables a PC running a standard operating system such as Windows 2000 to connect to the

Internet via an F77 / F55 terminal. At the Land Earth Station (LES) side there is a direct connection to the public Internet as shown in the overview diagram below:

World-Wide Web (WWW) access via F77 / F55

Although the diagram above shows access via a LAN and router, it is equally possible to use the RS-

232 asynchronous data port (9-pin D-type female) on the F77 / F55 terminal directly. The example below is based upon using the RS-232 interface (COM 1).

Firstly, to setup your F77 / F55 mobile consult the appropriate user manual. The transceiver should be configured for the right ocean region and LES operator that provides the MPDS service. The F77 / F55

RS-232 configuration should be (using the handset user interface):

Baud rate: 115200 baud, Flow control: Hardware

PC / Windows 2000 configuration for MPDS:

Following the instructions given below, you can set up a new dial-up networking connection to work with MPDS via F77 / F55 on a shipboard Win2000 PC. First of all the F77 / F55 terminal needs to be made known to the PC/Win2000 as a new standard modem. Go to the Control Panel

(Start/Setting/Control Panel) and select ‘Phone and Modem Options’. The following window appears.



Highlight Modem Tab and Click Add to proceed, then select ‘Don’t detect my modem…’, Select Next.

Select ‘(Standard Modem Types)’ and select ‘Standard 28800 bps Modem’. Select Next then the

Communications Port that is used for your F77 / F55 connection - Select Next.

Select ‘Finish’. The PC/Win2000 will now treat the F77 / F55 terminal as a standard modem. Select

Modem tab then Standard 28800 bps modem and then select Properties.



The figure shows the ‘Maximum speed’ value that must be selected from the list. Select the ‘Advanced’ button Enter AT+WS45=4 in the ‘Extra Initialization Command’, then click OK.

Click on ‘Dialing Rules’ tab then click on ‘New’ to create new dialing location. Type the name of the

Location, Country then click on Apply and OK repeatedly to come out of Phone & Modem Options.

Now click on ‘Start’ menu\ ‘Programs’\ ‘Accessories’\ Communications and then Select ‘Network and

Dial-Up connection’.

Double click on ‘Make New Connection’. Click Next to proceed.



Select ‘Dial-up to the Internet’, click on Next. Select the last option and then click on Next.

Select ‘I connect through a phone line and a modem’, then from the drop down menu select ‘Standard

28800 bps Modem

Enter a phone number. Any number will do, e.g. ‘1234’. Before you proceed take the tick off from

‘Use area code and dialing rules’ then select next. Enter User name and Password.



Select a name for your connection (e.g. Inmarsat MPDS), select ‘No’ then ‘Next’.

Select ‘Finish’. In the ‘Dial-Up Networking’ window the new MPDS connection will appear as a new icon within a few seconds. Use the right button on the mouse to access the ‘Properties’ of the new

MPDS Connection ‘Inmarsat MPDS’.

The figures above show which options need to be ticked and enabled.

Highlight your ‘Standard 28800 Modem’ & click ‘Configure’. Click ‘OK’ repeatedly until the ‘Dial-Up

Networking’ window appears. Congratulations, your new MPDS dial-up connection is now configured and an MPDS session can now be set up.



Running an MPDS session

Following these steps starts an MPDS session.

1. Ensure the F77 / F55 terminal is on, is fully enabled, is tracking an operational satellite and has logged on (spot beam selection etc. completed).

2. Ensure the PC – F77 / F55 cable connections are in place. Go to the PC ‘Dial-Up Networking’.

Select the MPDS connection. The following window will appear:

Select the button ‘Dial’.

3.

Wait for the F77 / F55 to establish an MPDS connection. When the MPDS connection is established the F77 / F55 should indicate this on the display / handset.

4. Wait for the PC to negotiate an IP address and validate the user name and password. The following window appears while the IP address is negotiated .

5. When the above window disappears the Internet access is available. This is indicated on the PC with a ‘Dial-Up Networking’ icon in the task bar icon tray.

Now Internet applications can be started on your PC using MPDS, e.g. FTP or Web browsing.

Closing an MPDS session

Following these steps stops an MPDS session.

Select the ‘Dial-Up Networking’ icon in the task bar icon tray:

A window appears showing the connection time and the number of bytes transmitted and received.

Double click on Inmarsat MPDS icon and click Disconnect.

Select the button ‘Disconnect’. Wait for the window to disappear.

The F77 / F55 MPDS session is now disconnected and is back in normal idle mode.



4.9.2 Optimising TCP/IP settings for MPDS

The operation of TCP/IP is degraded significantly when used over a long delayed link. In order to improve the operation, it is required to ‘tweak’ the TCP/IP settings slightly. By expanding the TCP

‘receive window’, more data is allowed to be outstanding in the receive window before a return acknowledgment is required. The default setting is around 8Kbytes, which is far too small. By following the instructions below it can be increased to around 32Kbytes, which is recommended. A competent person should undertake the changes suggested here, to the system Registry, as incorrect settings may damage system files. The following example is running under Windows



200 Pro.

Click start on the task bar then click on Run and type regedit and OK. Following window will appear.

Double click on the ‘HKEY_LOCAL_MACHINE’ directory. Double click on ‘System’ directory to expand the folder. Double click on ‘Current control set’ to expand the folder. Then double click on

Services to expand the folder then scroll down for TCP IP folder. Double click on ‘TCP IP’ to expand the folder. Right click on ‘Parameters’ folder select ‘new’ and then ‘DWORD value’. You should see

New Value #1 in the right hand window appear.

Right click on it and change its name to TcpWindowSize (Note the case changes). Right click again and select modify. The following window will appear.

Click hexadecimal and add the value 7FFF (32767 decimal) then OK. Now click on Registry in top tool bar and exit regedit and restart the pc, the change should now be active.

Further MPDS optimisation

Through upgrading your PCs operating system Performance varies between the various Microsoft operating systems. The following table describes MPDS standard performance and some quick steps that can be taken to improve performance.

O/S

Windows



2000

Windows



NT

Windows



95

Windows



98

Performance

Best performer

Close to 2000

Better than 98 when optimised

Worst performer

Recommendations

Install Service Pack 2 /3

Install Service Pack 6a

Use optimisation tool

Use optimisation tool

Improvement (MPDS)

2-10%

2-5%

5-11%

0-12%

Note: These optimisations can also result in improvements when using the Mobile ISDN service. Tests show anywhere up to 40% improvements can be achieved.



4.9.3 Typical F77 / F55 WEB applications

The most popular WEB applications on F77 / F55 are likely to be straightforward Internet access for information retrieval, communications with ports and ships supplies, news & current affairs, chart updates, weather forecasts, WEBmail and online banking. Several WEB sites are tailored to maritime users for example http://www.missiontoseafarers.org/ and http://www.merchantnavy.com/ . They offer

‘fast site’ options with reduced graphical content to speed up the access via satellite and reduce the cost of a WEB access session. WEBmail is a service offered by many Internet ISPs in addition to the usual email server supporting the standard POP3 protocols. Several LESOs also provide WEBmail and specialized email services via Inmarsat, such as StratosNet (see http://www.stratosglobal.com/ ),

Telenor’s Eik Mail (see http://www.internet.eik.com/ ), Xantic’s Amos Mail service (see http://www.xantic.net/ ) and Rydex (see http://www.rydex.com/ ).

WEBmail allows email customers to receive, read, compose and send emails with their usual SMTP address when they only have access to a WEB browser and an Internet connection. Some WEBmail services support attachments others do not. Another classic application of on-line Internet access is to update your ship’s PC virus protection software. As discussed elsewhere, for most of these applications, MPDS via F77 / F55 will be the communications medium of choice.

For a complete guide to web access at sea, visit the Digital Ship Webguide, sponsored by Inmarsat, at http://www.thedigitalship.com/webguide .

4.10 Email via F77 / F55

Existing Inmarsat users have found e-mail useful not just for inter-personal communication, but as the perfect way to transfer any type of data from place to place. Any F77 / F55 user can connect to the

Internet and use an e-mail service provided by an ISP. Mobile ISDN users can connect to any service provider that allows ISDN access to their service. MPDS users can connect to the Internet and access

ISP’s e-mail services that do not require dial-in authentication (as the user is connected directly to the

Internet, and does not dial directly into an ISPs server). As ISPs do not specifically tailor their services to satellite users, F77 / F55 users may experience problems with these services, or find that they lack options and features which are available using service providers specific to the satellite environment.

Typical ISP services allow users to have one or more mailboxes, all with e-mail addresses using the

ISP’s domain name. Some may offer users the option of having their own domain name for their mailboxes. E-mail is accessed using three main protocols: POP3 (Post Office Protocol v3), IMAP4

(Interim Mail Access Protocol v4), or via WEBmail, using HTTP (HyperText Transport Protocol).

POP3 is the most common e-mail access method used by ISPs. It allows messages to be stored on the

ISPs server, and downloaded periodically. It is a fairly simple protocol, and only allows the direct download of all (unread) messages in a mobile users mailbox.

IMAP4 is available on some ISP servers, and offers greater functionality than POP3. Rather than simply downloading all e-mail to the client, IMAP4 allows a user to maintain a structure of folders on the server, and manage the headers of messages. This enables the user to only download the headers of messages, and then choose which messages they wish to download. In addition, messages may be moved between folders by moving the headers, and never downloading the messages themselves.

WEBmail is commonly available as an alternative to POP3 services. As described above under WWWaccess, it allows an F77 / F55 user to access their mailbox through a web page.

SMTP (Simple Mail Transfer Protocol) is the protocol that a client uses to send messages over the

Internet. When using an ISP service with POP3 or IMAP4, these protocols are used to download messages, but SMTP is used to upload messages to the ISPs mail server, for delivery over the Internet.

Some LESOs provide dedicated email facilities, which will improve on those offered by an ISP because

LESOs have the knowledge and ability to configure their service to work more effectively over a satellite link. This may include changes to the TCP/IP stack and application time-outs for the service.

Also, as the service is hosted by the LESO, the traffic does not pass over the Internet (Mobile Packet



Data users) or via the public ISDN network (Mobile ISDN users) that provides a certain amount of extra resilience and perhaps performance improvements.

The performance of the email service can be further improved by employing specialised ‘middleware’ software that is available for the satellite industry. These offer some of the following potential benefits:

Extra resilience: If a data link is broken during the transmission of messages, standard software will start the transmission again, from the beginning. Specialised software is able to continue this transmission from where it stopped.

Message filtering: Services can provide the ability for users to screen mail, before it is downloaded.

This may be simply by preventing large messages from being downloaded, or by providing the ability to check who is sending messages and only allowing messages through from known originators.

Least-cost access: Some services provide the ability to connect to the service by automatically selecting the cheapest network. For example, ships close to shore could use GSM to access the service, whilst switching to F77 / F55 when out of GSM range.

Batching and compression: Service may provide automated batching and compression, ensuring that messages are transmitted in the most cost effective way.

Specialised email message hubs

There are a number of specialist companies that provide e-mail services specifically for the Inmarsat community. Many of these companies have their roots in the industries that they serve, having had much experience of using standard e-mail packages over satellite systems, which led to developing better solutions for themselves, and others. The features and benefits of these solutions match those of the LESO value added services. In fact, many of the LESO services are based on specialised messaging hubs brought in from these companies. It is also possible to purchase specialist hubs that can be sited at corporate headquarters, in order to provide access for remote users directly into corporate systems, rather than routing through a third party.

Email middleware

Middleware is a term used for software that provides a link, or bridge, between two applications or environments. Rather than develop complete messaging hub solutions for satellite systems, some specialist companies have developed components that integrate with the popular corporate systems.

These solutions therefore allow closer integration with existing corporate messaging systems, whilst still providing features that benefit the remote user.

Email via MPDS vs. email via Mobile ISDN

E-mail works effectively over both Mobile Packet Data and Mobile ISDN. However, one service is charged by connection time, and the other by amount of data transferred, so there are subtly different ways in which e-mail should be used over each service.

Email via MPDS

The following section details some hints and tips for using popular mail clients over the MPDS and F77

/ F55. As the service is charged by the amount of data transmitted, it is ideally suited for sending and receiving small urgent messages, or using mail clients which support the IMAP protocol, which enables message headers to be downloaded, studied, and then only the required messages downloaded. In addition, keeping the data to a minimum, by not sending attachments or ensuring that they are compressed will lessen the amount of data sent over the link.



Email via Mobile ISDN

Mobile ISDN is charged by on-line time. Thus, it is better suited to sending large amounts of mail, compressed and batched. Each batch can be sent at intervals throughout the day, or perhaps just once each night.

Outlook Express and Eudora

Outlook Express and Eudora are two of the most popular e-mail clients in use today. It is possible to use them straight from the box on an F77 / F55. However, there are certain settings that can be modified to improve their performance.

4.10.1 Optimising Outlook Express for F77 / F55

POP3 and IMAP4 systems do not provide any compression of data over the communications link. In order to reduce the amount of data sent and received, use the following guide:

Outlook Express supports both the ubiquitous POP3 and the less well used IMAP4. Neither of these protocols have any compression components but the IMAP4 option allows the retrieval of headers only.

This can save bandwidth if the mailbox is susceptible to Junk and Spam mail, as these messages can be deleted without downloading.

Switch off ‘Check for mail every x minutes’ and do this manually or set the value to several hours.

The action of only checking for e-mail when necessary can reduce costs. To disable automatic checking go to: Tools/Options/General also on the same page Send and Receive messages at start-up should be disabled, again to allow queuing of e-mail.



Disable ‘Automatically download message when in the viewing panel’ when in preview pane. This will stop messages being downloaded as you browse the headers. This can be found in Tools/options/

Read as shown below.



Send plain text messages only. If you use bold, underline and non-standard fonts more data is used than plain text. To switch on plain text in Outlook Express go to: Tools/options/send mail /sending

format /plain text radio button. It is also advisable to deselect the Send messages immediately option, as this will allow the use of the Send Recv button on the main toolbar, which will queue messages enabling them to be sent all at once rather than initiate a connection for each message.

Also, signatures impose an extra overhead; they can be disabled in Tools/options/Signatures



Read receipts are designed to allow the sender of the message to be notified when the recipient has opened the message. As this generates extra traffic it is advisable, to switch them off. Go to

Tools/options/send mail.

When sending an Attachment; before attaching a file to an email, compress it with a file compression utility such as Winzip (www.winzip.com), which is shareware, or Powerarchiver

( http://www.powerarchiver.com/ ) , which is freeware.

Note that the recipient must have a similar utility to de-compress the documents.



4.10.2 Optimising Eudora 5.1 for F77 / F55

Eudora also supports both the ubiquitous POP3 and the less well-used IMAP4. Neither of these protocols have any compression components but the IMAP4 option allows the retrieval of headers only.

Having downloaded the headers, individual e-mails can be retrieved or discarded. This can save bandwidth if the mailbox is susceptible to Junk and Spam e-mail or if there is a requirement to retrieve specific messages. The ISP must support the use of IMAP.

Eudora POP3 has the option to download only part of the message. This gives the effect of only downloading the headers if this setting is set small enough, and has the secondary benefit that should a message contain a virus, it can be deleted without downloading all of it. Although the dialog says skip, it only skips the part over 3K (in this case). To change this option select: Tools/Options/Incoming Mail.

Leaving e-mail on the server has advantages and disadvantages. The advantage is that you can retrieve it later if you need it, or lose the copy that you have downloaded, the disadvantage is that it is possible to download it again and incur more data charges. A better strategy would be to download what is required and delete what is not from the server.



If you disable ‘Immediate send’ this will allow e-mail to queue which will reduce the number of

SMTP connections needed to send messages. Found in: Tools/options/Sending Mail:

Send plain text messages using bold, or using underlining or text in complex fonts uses more bytes than plain text. Text mode is set by default but can be edited in Edit/Text from the main menu. Signatures impose an extra overhead; they may be disabled on the tool bar.



Attachments – as for Outlook, try to compress any attachments with the utilities suggested.

Switch off ‘Check for mail every x minutes’ and do this manually or set the value to several hours.

The action of only checking for e-mails when necessary can reduce costs. This is done from

Tools/Options/Checking Mail. On the same page, checking ‘Don’t check without a network

connection’, will stop Eudora forcing a new network connection.

Read receipts are designed to allow the sender of the message to be notified when the recipient has opened the message. This generates extra traffic, read receipts are turned off in Eudora by default but can be toggled on the new message toolbar as shown below.



4.11 Cargo / vessel telemetry via MPDS

The diagram below shows an overview of a telemetry network. Sensors or transducers around the vessel either detecting cargo status such as temperature, pressure, humidity etc. at different locations in the hold or operational measurements of ship-board systems such as engine performance are connected to a central processor which in turn is on the ship’s LAN. An application (typically in these cases of a bespoke and customised nature) can establish an MPDS connection via the Internet and a firewall to the corporate WAN. Over this link the essential telemetry data can be reported to a peer application running at headquarters. This reporting can be according to a schedule or alternatively passed upon a trigger value such as a pre-set alarm or limit. Using MPDS, only the telemetry data transmitted is actually charged for, making the system highly cost-effective.

Cargo or onboard systems telemetry network



4.12 Crew calling (welfare) via F77 / F55

A pre-paid voice service, provided for the shipboard staff, can be installed relatively easily. Having such a facility available can, as mentioned before, lead to improved morale and a safer and more productive crew.

Crew calling is made easy with F77 / F55

The typical network configuration for crew-calling, will be a pre-paid payphone or dialler, positioned in a private area, which is cabled either into the ships PBX or directly into one of the analogue RJ-11 ports on the F77 / F55 which is set up for the 4.8kbps AMBE voice service. It is certainly not necessary, for example, to use the high-quality 64kbps 3.1kHz audio or 64kbps Speech services for crew calls. Calls can either be pre-set to route to a LESs or Inmarsat Service Provider’s pre-paid card service or alternatively have the pre-payment accounts managed on board through the use of a programmable payphone.



Pre-paid card services via LESOs or Inmarsat Service Providers

Several pre-paid card services are available. Typically these are accessed via a pre-arranged and advertised short code, which is free (not charged) to the calling terminal ID. This dialling can be restricted through the use of a dialler or payphone, which only allows calls to be made to the pre-paid platform. Once the short code is called the pre-paid platform answers and prompts the user to enter a

PIN or account number. This is usually provided on a scratch card or pre-paid satellite phone card. The user then dials the destination PSTN number and is connected. Cards are usually supplied in 10 or 20minute values. The caller is usually only charged for the actual time spent on an effective call through the pre-paid service. Some services allow the caller to top-up their remaining call time (with a credit card) through a call to the service administrator.

A simple installed solution is the Inmarsat Crew Phone, a one-box device that takes social calling away from the bridge - allowing crew to call home with more privacy and giving masters the freedom to run their vessel efficiently.

The Inmarsat Crew Phone can be used via Fleet and all existing Inmarsat shipboard terminals (except Inmarsat A) using pre-paid calling cards.

Crew can also enjoy cheaper phone calls thanks to Inmarsat’s 'Super Quiet Time' prepaid card* tariffs. For further details see: www.inmarsat.com/crewcalling

Typical programmable payphone

It is now also easy to provide payphones, which are able to account individually for crewmembers’ call allowances purchased in advance and programmed into the phone or onto a card. Some of these prepaid card phones also accept coins. As would be expected they are ruggedised and contain anti-fraud measures such as PIN number protection for ‘owner’ accounts etc. A typical crew calling payphone, the PUBLISAT from http://www.gs4.fr/ is shown below:

From a PC connected directly to the payphone or via a dial-in modem the following management controls are available:

•

Password and PIN protection for payphone manager or ‘owner’ account.

•

Individual management of pre-paid accounts in ‘call units’.

•

Pre-paid accounts can either be stored on smart cards or stored in phone as a PIN account.

•

Programmable number / digit insertion to work with any PBX, LES or F77 / F55 terminal.

•

Programmable cost in seconds per unit – settable on voice service used or time of day etc.

•

Programmable cost of calls to different destinations e.g. PSTN country codes.



•

Settable overall limit on call duration.

•

Programmable cost of incoming calls – free, fixed value or time – dependent.

•

Print logs of calls made / from which card accounts or with specific PIN codes etc.

•

Reload fresh cards with set number of unused call units.

N.B. It is advisable to check with your service provider if the hardware provided gives full access to special commercial offers available specifically for Crew Calling.

4.13 Video conferencing

Two principal International Telecommunications Union (ITU) standards exist for the provision of video-conferencing. H.320 is a suite of specifications that define how video-conferencing systems communicate with each other over narrow-band, circuit-switched media. Narrow-band bit rates include the 64Kbps Mobile ISDN rate. H.323 is an umbrella recommendation from the ITU that sets standards for the provision of video-conferencing over IP networks (such as LANs and WANs) that do not provide a guaranteed Quality of Service (QoS). These networks dominate today’s corporate desktops and include packet-switched TCP/IP and IPX over Ethernet, Fast Ethernet and Token Ring networks.

It is not recommended to use video-conferencing over the Inmarsat Mobile Packet Data service, as it will result in higher call charges than using the Mobile ISDN service. Videoconferencing and application sharing using NetMeeting, for example, is suitable for MPDS and this is also described in detail elsewhere in this section.

Circuit-switched video-conferencing

The international standard for video conferencing over circuit-switched media such as ISDN and

Mobile ISDN is the ITU-T recommendation H.320. Most video conferencing systems in general use worldwide, are compliant with this standard. Other proprietary standards are equally capable of being used over an Inmarsat F77 / F55 channel and the same principles will apply for their use as discussed below.

H.320 video conferencing solutions are normally supplied either as dedicated systems specifically designed for installation in a dedicated video conferencing room or as PC hardware and software kits intended for installation in a desk top PC. Both implementations are suitable for use with the Inmarsat

F77 / F55 service.

Copyright © Inmarsat 2006

Video conferencing with F77 / F55

Page 56 of 98 Version 2.5


The H.320 video & G.728 audio conferencing standards

H.320 is a suite of specifications that define how video conferencing systems communicate over circuit switched media such as ISDN, including the H.261 video compression algorithm. On an Inmarsat F77 /

F55 64Kbps channel this system should achieve 10-15 frames/second. The H.261 algorithm includes a mechanism that optimises bandwidth usage by trading picture quality against motion so that a quickly changing picture will have a lower quality than a relatively static picture. With regard to audio compression it is important when using F77 / F55 for video-conferencing to use the G.728 algorithm, which only consumes 16Kbps of bandwidth. An H.320 compatible video conferencing system using

Inmarsat F77 / F55 will therefore use 16Kbps (G.728) for audio and 1.6Kbps for H.221 framing leaving 46.4Kbps for video. This applies to both the terrestrial and remote F77 / F55 systems.

Video-conferencing over IP networks

H.323 is an umbrella recommendation from the International Telecommunications Union (ITU) that sets standards for multimedia communications over IP networks that do not provide a guaranteed

Quality of Service (QoS). The H.323 standards are important building blocks for a broad new range of collaborative, LAN-based applications for multimedia communications. H.323 products offer the following benefits to users:

•

Products and services developed by multiple manufacturers under the H.323 standard can interoperate without platform limitations.

•

H.323 provides multiple audio and video codecs that format data according to the requirements of various networks, using different bit rates, delays, and quality options. Users can choose the codecs that best support their computer and network selections.

Mobile ISDN for videoconferencing

Most PC-based video conferencing systems are supplied with an integral ISDN BRI, which can be connected directly to the F77 or F55 MES.

The video-conferencing system must support the audio coding standards as described above to function over the Inmarsat F77 / F55 service. While most modern systems do support these standards some older systems only have G.711 or G.722, which will not permit the use of the video conferencing system over the Inmarsat F77 & F55 services.

Application sharing should be disabled if it is not required, as it will otherwise reduce the already limited bandwidth available for the video.

Once the call is connected it typically takes 5 - 10 seconds for each of the video conferencing systems to synchronise and connect.

If the call is established with an audio connection but no video is present then it is highly likely that one or both of the video conferencing systems is in G.711 or G.722 audio mode. In this case clear the call down, reconfigure one or both of the terminals and re-dial the call.

If H.323 is to be used then the host PC should be connected to the Internet or private network if used as described elsewhere in this section and the video-conferencing run as an application once the IP connection is made.



4.14 Using Microsoft

 NetMeeting via F77 or F55

NetMeeting can provide an efficient way to allow ship owners, staff and/or crew to communicate simultaneously via an online conference. When used via MPDS this can be a highly cost-effective way to co-ordinate resources without the need for face-to-face meetings. An example would be the resolving ship-borne technical or logistical problems with staff simultaneously on board and ashore with video, audio, file sharing and white boarding. Alternately it can solve the problems brought about by the closure of Telex networks.

Here we describe how to install and use Microsoft NetMeeting. The purpose is only to help the user to get started with the basic functions in NetMeeting, not to show how all the functions work in

NetMeeting. With NetMeeting the user can:

•

Make video and audio call.

•

Chat

•

Create, load, update and save the graphic information with the ‘whiteboard’ function.

•

Transfer files to the other conferees.

•

Share programs and share a remote desktop.

Minimum hardware requirements are, any PC or laptop with Pentium II 400 MHz (at least 90 MHz required), 64 MB of RAM for Windows 95/98 (at least 16 MB), 4 MB of free hard disk space (an additional 10 MB is needed during installation only to accommodate the initial set-up files). An ISDN connection, so an F77 / F55 64kbps UDI connection is therefore ideal for the purpose. A sound card with microphone and speakers is also required for both audio and video support. A video capture card or camera that provides a Video for Windows capture driver is required for video support. Most of the new PCs and laptops have built-in soundcards. (In this example, the Quick Cam Pro web camera produced by Logitech was used and a microphone.)

As a Mobile ISDN connection is required for the F77 / F55 terminal to run NetMeeting, the PC must also have an ISDN card or an ISDN PCMCIA card (for a laptop) and the Microsoft Dial-Up

Networking must be configured. This is described elsewhere in this section.

Microsoft NetMeeting is a standard program provided in all Windows platforms. However, the latest version is recommended. In this example version 3.01 was used. It can be downloaded from http://www.microsoft.com/windows/netmeeting

In order to start a NetMeeting session over the Internet, you must know the IP-addresses of the other parties. Unfortunately this is very difficult to know, because most Internet users do not have a permanent IP address, but a IP address that changes every time they log on, and they are not always on line either. Therefore NetMeeting uses a Microsoft Network MSN Messenger Service 2.0 Others can be used but this is described here because it is free of charge and easy to use. Use of MSN messenger

Service 2.0 requires a so-called ‘passport’ or a hotmail account. Setting up such an account is also free of charge. The user can go to the following web sites to get MSN messenger Service 2.0 and a hotmail account:

For MSN messenger Service 2.0

: http://msn.co.uk/page/11-141.asp

For Hotmail account: http://www.hotmail.com

NetMeeting requires Internet Explorer IE 4.01 or better, the user can download the latest IE from: http://www.microsoft.com/windows/IE/



Installation and configuring of MSN messenger Service 2.0

When you have downloaded the program MSN Messenger Service 2.0 mmssetup.exe it is straightforward to install. After the licence agreement, you will see the following figure:

When installing MSN messenger, we use in this example the hotmail account [email protected]

.

Hence ‘m4gan1’ is the sign-in name in the figure below:

Click Next and you can finish the installation.



The next step after installation of Messenger service 2.0 is to create a contact list, which contains the people you want to contact. You must first log on MSN messenger Service by clicking the symbol

in the taskbar near the clock (or go to Start, Program, choose and click MSN Messenger

Service). On the first use, you will see the following figure.

In order to make a contact list, you click the Add. Since we have a hotmail account as shown earlier, we must check the box ‘By e-mail address’:

Click Next.



The person we want to put in the contact list has also a hotmail account [email protected]

. We type in this E-mail address and click Next. Follow the instructions then finish making the contact list as follows:



The account m4gan2 gets a message from Messenger Service that he/she is put in m4gan1’s contact list. This happens only if m4gan2 is already an MSN Messenger Service user.

Installing NetMeeting 3.01 on Windows 98

When you have downloaded the self-extracted file NM30.exe it is also straightforward to install. Follow the instructions on the screen.

Using MSN Messenger Service 2.0 to make NetMeeting call

After you have logged on MSN messenger Service by clicking the symbol in the taskbar near the clock (or go to Start, Program, choose and click MSN Messenger Service), you will see the status of the people in your contact list, i.e. if they are on-line or off-line. See below.



If they are on-line, you can use Messenger Service to send an instant message to them. In order to send an instant message, click Tools, then Send and Instant Message. Choose the people to whom you wish to message, from the list.

After you have chosen gan-2 (the first name chosen in this example when registering the hotmail account with MSN), you will get a new window that allows you to write a message and send it to gan-

2. Right after you click Send, gan-2 will get a similar window, you and gan-2 may then exchange messages in real time. The results are shown below.



When you start a NetMeeting session, you can use voice, video and data communication etc. simultaneously. Click Tools, Send an Invitation, To Start NetMeeting 3.01 and choose for example gan-

2, then you will get the figures below:



The figure above shows that MSN Messenger Service has sent you a status message telling you what to do. At the same time, the person you invite to the NetMeeting session gets a message from MSN

Messenger Service and he or she has the chance to accept or decline the invitation.

Click Accept in the figure above when prompted and you - the calling party - will get a new message from the MSN Messenger Service as shown in the figure on the right, the called party will also receive a new message from the Messenger Service as shown. At the same time, both the calling party and the called party will see that NetMeeting 3.01 is automatically running with the status ‘not in a call’ (see below). Also at this time, the called party will get a prompt showing the IP-address of the calling party.

The advantage of using MSN Messenger Service for starting NetMeeting is therefore obvious. One need not find the IP-address of the called party; you can simply allow Messenger Service to do that.

The Messenger Service registers the IP-address of the calling party and prompts this to the called party.



At this time, the calling side will get the prompt below; you must click Accept because the called party is still waiting for your response.

When the calling side has clicked Accept, both the calling and the called party are in connection, see below:

The small picture-in-picture on the bottom right is the video image from the your (calling) side. In order to see and to be seen on the NetMeeting screen, you must go to Tools, Video and check Send/Receive.

You can change the video window size by going to Tools, Window Size and choose the window size you want to have.

Sharing applications, Chat, Whiteboard, File Transfer etc.



Under the Tools menu, you can find Sharing, Chat, Whiteboard, and File Transfer etc.

Sharing is a powerful feature that allows you to remotely share an application, for example a Word document, between you and the other party. If you want to allow the other party to revise the document, you must allow them to take control. You must be cautious sharing programs (applications) with people you do not know well, especially when you want to share your desktop with the other party. This is simply because you are potentially giving full access to your PC and file system.

NetMeeting Chat, Whiteboard and File Transfer allow you to exchange messages, drawings and files of any type while you and the other party are in a videoconference.

NetMeeting interworking with H.323

The example given used MSN Messenger Service 2.0 to initiate NetMeeting, but not all Internet users have an MSN hotmail account or ‘passport’. Besides, NetMeeting is mostly compliant with H.323. This means that the called party may use another application than Microsoft NetMeeting to communicate with the calling party, as long as that application is also H.323 compliant. The called party may also use another browser like Netscape or Opera, or even using a different operating system than Windows. In such situations, however, MSN Messenger Service 2.0 is no longer helpful, and we must have another way to get the IP-address of the called party before we can initiate NetMeeting. This is not trivial as the

IP-address is likely to be different every time the user logs on to the Internet for an ‘ordinary’ user (one that does not connect to a LAN). Fortunately, there are services available that can make it easier for you to make a NetMeeting call in these circumstances, some are free of charge and some are not. Since most PCs today use Windows as the operating system and Internet Explorer as their default browser, we have not described the use of these alternate services, also because MSN Messenger Service 2.0 is free and very easy to use.

Finding your IP address whilst online

If you know that the party you want to connect with is online at the same time (for example by prior arrangement) and that they have Windows as the operating system, the called party can follow these steps to determine their current IP addresses:

For Windows 95/98: Go to Start, Run, and type winipcfg and then press ENTER. This will show their current IP-address. They can then tell you their IP-address, and you can start running NetMeeting. In the menu do Call, New Call, To, the IP-address got from the other party can be keyed in and then press ENTER or click on Call.

For Windows NT: Go to Start, Command Prompt. When you are in the DOS window, type ipconfig and then press ENTER. This will show your current IP-address. To make a NetMeeting call from

WinNT, the same procedure can be used as in Win95/98. Note that typically Windows NT users will be behind a firewall, so they may need to contact the system administrator to open some TCP/IP ports.

For Windows 2000 Pro : Double click on the dial-up networking icon in the system tray and select the details tab. The client and server IP addresses are shown.



4.15 Universal Messaging via F77 & F55

An example of a universal messaging service is TeleMessage at the website http://www.telemessage.com

. This allows an F55 or F77 user to create one message and have it delivered to almost any device (SMS, mobile phone, e-mail, pager, phone, instant messaging e.g. the ICQ service at http://www.icq.com/ , or fax) for any number of recipients simultaneously and immediately. A useful application of this, for example, is that messages can be sent to a phone, which allows messaging to the large population of people that are not connected to the Internet. The screen capture below shows how a short text message can be composed along with the recipients name and all of the delivery options you wish to use to enable the message to get through to them:

Your regular contacts can also be saved in an on-line address book:

Messages can be delivered straight away or at a designated time, giving the sender the reassurance that everybody is automatically informed at the right time, which can be very useful in a maritime satellite scenario where the sender and recipient(s) are likely to be in different time-zones.



4.16 Voice and data multiplexing via F77 / F55

Multiplexing is defined as the simultaneous transmission of two or more channels within a single communications circuit. The component channels can be the same, as in a multi-channel telephony multiplexer, or from a variety of different sources such as phone, fax and data. The number of channels, which can be multiplexed onto a single communications circuit, depends upon the capacity of the communications circuit and the bandwidth requirements of the individual channels to be multiplexed.

Multiplexing with F77 / F55

Early multiplexers allocated fixed bandwidth slots within the communications circuit for each multiplexed signal. However, modern statistical multiplexing techniques permit the dynamic allocation of bandwidth on an as needed basis. For example, a device such as a network router may be attached to a data port on a multiplexer and assigned the full bandwidth of the communications link. When a phone or fax, also attached to the multiplexer, goes off-hook the multiplexer will automatically reduce the bandwidth available to the router in order to assign bandwidth to the phone or fax. When the phone or fax call is complete and goes on-hook the bandwidth is automatically re-assigned to the router on the data port.

Obviously statistical multiplexing techniques make much more efficient use of a fixed-bandwidth channel and should be the preferred multiplexing technique in Inmarsat F77 / F55 applications.



Multiplexing is generally defined as the simultaneous transmission of two or more signals within a single communication channel. The basic methods of multiplexing involve the separation of signals by the allocation of individual time slots within the communications channel, known as Time Division Multiple

Access (TDMA), the allocation of different frequencies for each signal within the channel, known as

Frequency Division Multiple Access (FDMA), or the individual and unique coding of the data associated with each signal within the communications channel, known as Code Division Multiple

Access (CDMA).

Multiplexers can have a range of inputs such as telephony, fax, and data (synchronous and asynchronous) and any combination of these devices can be used simultaneously. Alternatively the multiplexer may be configured for one particular type of traffic e.g. voice telephony. However, consideration has to be given to the fact that the Inmarsat F77 / F55 channel has a 64Kbps bandwidth.

If too many devices are attached and operated at the same time there will be contention for capacity on the link and the multiplexer will allocate bandwidth in order to serve as many users as possible.

Some advanced bridge/routers incorporate multiplexing features. These routers offer the capability to

‘piggy-back’ voice, fax and data traffic with LAN traffic whenever the Inmarsat F77 or F55 MES link is connected.

Multiplexer configuration

Multiplexers to be used with an Inmarsat F77 or F55 should be ordered with an ISDN BRI for use with the Mobile ISDN service and an RS-232 serial port for use with the Inmarsat Mobile Packet Data service. For use with Mobile ISDN the router is connected to the RJ-45 interface on the MES and an

MSN assigned appropriate to the 64kbsp UDI or 56kbps service as required. As with remote LAN access, the configuration of a hybrid router/multiplexer is not advised without appropriate training.



4.17 File transfer with F77 & F55

The use of bridge/routers with the Inmarsat F77 or F55 services provide a means of using widely available, off-the-shelf equipment, with a familiar user interface for transparently and automatically connecting two or more LANs. The diagram below shows a typical configuration using Mobile ISDN.

File Transfer with F77 / F55

In some circumstances an alternative solution for the transfer of data over the Inmarsat F77 / F55 service can be more attractive than a LAN connection using TCP/IP. While TCP/IP is a robust protocol and very suitable for satellite communication, there is some overhead associated with network protocols such as TCP/IP. Actual data throughputs can be quite variable between 30-60Kbps. This means that if large data file transfer is the primary requirement of the Inmarsat F77 / F55 service (for example, geophysical applications) then the bridge/router solution with associated network overhead may not be the most economic means of transmitting data back to base.

Popular FTP software commonly used for FTP via satellite includes:

CuteFTP pro

 - from http://www.globalscape.com/

Bulletproof FTP – from http://www.bpftp.com/

Go!Zilla

 - from http://gozilla.com/

GetRight

 - from http://www.getright.com/

And probably the most widely used file transfer is that supplied within Microsoft



Internet Explorer.

These packages have the great advantage of re-starting from where a previous transfer was broken by a loss of connection. They also ensure the error-free transfer of files.



However, conventional file transfer software packages designed for terrestrial ISDN circuits may not adapt very well to the delays of a satellite communications channel which are typically of the order of

250ms thus giving a total round trip delay of about 500ms depending on the LES used and terrestrial portion of the link. A mobile-to-mobile call can see a round trip delay of up to two seconds.

To address this requirement several specialist manufacturers have produced file transfer solutions specifically designed for the fastest possible data throughput on an Inmarsat F77 / F55 satellite link.

Systems are available which share some common features such as proprietary s/w and h/w required at each end of the link (so usually no interoperability between systems), PC-based, synchronous communications, full duplex data transfer capability, very robust file transfer protocols with error correction, data recovery following link failure and high data throughput - typically averaging 60Kbps on a 64Kbps link. They typically do not, however, offer interactive operation. The specialist hardware file transfer solutions vary; with options of internal PC cards, PCMCIA cards and in-line devices.



4.18 128kbps channel ‘bonding’

Some F55 terminals provide a dual 64kbps channel bonding mechanism whereby two 64kbps UDI channels can be aggregated together to support higher rate 128kbps services. This is achieved through dedicated interfaces on the F55 BDE as shown below:

128kbps channel bonding

The example above illustrates the multiplexing application enhanced with the 128kbps-bonding feature.

As shown above, two F55 MES terminals are required equipped with the bonding interface and appropriate cabling. The call charges are exactly double that of a 64kbps UDI Mobile ISDN call but the data throughput is also double and for some applications this can be a critical requirement. Particular applications where high data throughputs are required are for example where the delay in sending very large files has to be minimised and where software applications will only operate at these data rates.

Other applications such as LAN access, multiplexing, videoconferencing etc. will all benefit proportionately from the improved bandwidth available.

The same effect can also be achieved using two F77 terminals with the addition of extra external terminal adaptors and multiplexers, but this is not an integrated feature as it is with some F55 terminals.



4.19 Facsimile via F55 / F77

As mentioned in the overview above, Group 4 fax is faster than Group 3. This is mainly due to the higher transmission speed of 64kbps as the image-coding scheme is still the Modified Huffman runlength coding of Group 3 specified by ITU T.30 (within T.4). Group 4, however, also uses an even better compression algorithm (T.6) as the network layers provide an error-free link. Several options exist to send and receive faxes via F77 / F55 and these are discussed below.

Group 3 & 4 Fax and fax emulation software

This is possible by creating a document in Word, Excel, Power Point etc. and using software on the mobile PC to convert to a fax format directly. It can then be sent to standard Group 3 / Group 4 fax destinations using fax modems or Terminal Adaptors (TAs) that operate either via the optional F77 /

F55 analogue fax port (for up to 9.6kbps Group 3 fax) or the 3.1kHz service for 14.4kbps fax or via the

BRI interface for 64kbps Group 4 fax. Paper documents can also be scanned and transmitted digitally in this way if digital originals do not exist. An example of such a package is RVS-COM Lite, which works with the DIVA TA from http://www.eicon.com/ .

Fax via a Website

An alternative service on the same system means that mobile maritime F77 or F55 fax users can even use their regular web browser to access the Electronic Fax providers web fax feature and send a fax directly from the browser.

Fax over IP

It is also possible to use a fax bridging service (e.g. Jfax etc.) where the original document is held electronically on your PC, and then emailed to a specialist server, which checks the destination fax # and delivers the document to the appropriate (nearest) point of presence (PoP) and converts the document format in order to deliver to a Group 4 or Group 3 fax machine via the local PSTN/ISDN. In this service, the MPDS connection could be used, or Mobile ISDN to access the email service in the normal way, the document being sent as an attachment. Delivery confirmation and notification of each fax sent is delivered back to you, the sender, by e-mail.

Faxes with IP built-in

New fax machines recently available, possess options that have much of this messaging and IP connectivity built in. With their scanning capability, these fax machines are able to replicate the messaging process directly without additional hardware or software (i.e. a dedicated fax PC). This solution does require subscription to an email and Internet service however.

Solutions using the Internet this way means you can use the Internet to send faxes from the ship to any fax machine connected to the PSTN or ISDN or vice versa. It can also be more efficient than using a traditional circuit-switched fax services, and brings fax into line with e-mail.



Commissioning F77 & F55 Group 4 fax ISDN IMNs

In order to successfully interface, configure and use a true Group 4 fax machine with an F77 / F55 terminal, it is important that the terminal is commissioned properly. In most cases you will be interfacing 2 ISDN devices – a data terminal adapter and a Group 4 fax machine. For this you will only need to commission one ISDN IMN. ISDN circuits possess a capability to route calls to selected devices on their own. If the group 4 fax machine supports Group 3 transmissions as well and you wish to be able to use this functionality, then you must also obtain one 3.1Khz audio IMN commissioned as well. These ‘virtual’ ports (ISDN and 3.1kHz audio IMNs) must now be programmed through the F77

/ F55 handset and enabled for outgoing & incoming calls as well as for correct call routing. This is described in your manufacturer user manual.

Interfacing a Group 4 fax to the F77 / F55

The Fleet F77 / F55 below-decks unit (BDU) provides a number of interfaces. The Group 4 fax machine needs to be connected to the ISDN BRI RJ-45 port. In case the BDU possesses only one physical RJ-45 port, an ISDN splitter can be used to allow multiple ISDN devices to connect to the F77

/ F55. Correct configuring of the routing inwards of calls will allow automatic forwarding of data calls to one device (i.e. ISDN TA) while fax calls will be diverted to the Group 4 fax machines by the IMN

(MSN) identifier.

Configuring your Group 4 fax machine

The Group 4 fax machine is connected directly to the ISDN RJ-45 interface on the F77 / F55 BDE.

Depending upon the make of the fax machine, you will usually be required to program your fax machines with the MSN numbers - see Using MSN with the Inmarsat F77 / F55. The MSN feature enables the assignment of multiple numbers to a single ISDN BRI channel. This is useful for mapping to multiple devices on a single physical channel. On some F77 / F55 terminals a sub-address is automatically assigned. For specific configuration commands see your F77 or F55 terminal manufacturer guide.

Group 4 fax image quality

Group 4 fax machines support a resolution of 400 - 600 dpi, which is as good as most laser printers

(Group 3 supports up to 200 x 200 dpi). In addition, Group 4 typically features 64 levels of grey (with

Colour options as well), so text is easier to read and illustration and photo fidelity is preserved. Higher scanning resolutions means higher amounts of digitised data and thus requiring higher bandwidths to transmit economically. If a Group 4 machine transmits to a Group 3 machine (or vice versa), the Group

4 machine falls back to a Group 3-compatibility mode, so the fax quality is the same as that for Group

3. Using a Group 4 machine at the source, however, may provide better results, although the printing and resolution capability of the receiving machine will determine the final quality.

Fax-to-email via F77 / F55

A growing number of commercial messaging services support this facility. They provide a message switch on a special number, which automatically answers an incoming fax call, detects what kind of message it is receiving, and converts it to an appropriate digital format. In the case of fax, this is usually a TIFF image file, which can be viewed using standard PC imaging software. The digital file is then emailed, as an attachment, to the recipient’s normal SMTP email address via the Internet. This can then be downloaded in the normal way or viewed over the Web from your F77 or F55 MES.



5. Customer Support Processes

5.1 Service Activation and MES requirements

Service Activation is the term used by Inmarsat to define the process of formal registration, which must be carried out before bringing each new or modified Mobile Earth Station (MES) into service. In the past the most important part of Service Activation was the technical testing of the equipment. However, with the increased reliability of MESs and greater number and variety of users, Service Activation has moved from being a technical process to being a largely administrative procedure centred on the customer. Like an application for a telephone or email service, it consists mainly of setting up an account for the user.

The first stage in Service Activation is the administrative registration of customers and their equipment - as soon as the MES is registered and the details transmitted to the Land Earth Stations (LESs) it can be used.

All operational MESs must satisfy the following basic requirements:

5.1.1 Financial - Accounting Authorities & ISPs

All maritime customers must register their ships licence with a particular country or ‘Flag’. The vessel owner must then select, and register with, an Accounting Authority or ISP (if permissible) that is recognised by that country. (If a vessel is already registered with an AA they will be able to provide the facilities for F77 / F55 accounting – provided the ship has not changed Flags.) The Accounting

Authority, will liase with the relevant Routing Organisation (RO) and Inmarsat to register the terminal.

Inmarsat can provide customers with an up to date list of AA’s and ISP’s recognized by each country.

It should be noted at this point that there is a difference between registering with an AA and ISP.

Traditionally maritime users have had to register with an Accounting Authority as part of the IMO regulations for the purposes of GMDSS. This allows the user to access any LES within the Inmarsat network in both the mobile to fixed and fixed to mobile routing. The AA in turn receives all the airtime traffic on a monthly basis from all the LESs on behalf of the user and in turn on-bills to the F77 / F55 user on a cost plus basis.

An ISP on the other hand will have a reseller airtime agreement with one or more LES, and it is only these LESs that the user will be able to use. The service will be barred through all other LESs in the mobile to fixed direction. Though the fixed to mobile will continue in the usual manner. This then restricts the user to the contracted LESs that the ISP has relationships with. The ISP will collect the traffic from their contracted LESs, and again on-bill, but at the rates that the ISP has contracted with the user rather then the cost plus basis of an AA.

Service activation forms can be downloaded from http://www.inmarsat.com/support.cfm

.

5.1.2 Legal

The MES must meet all national licensing requirements. The Routing Organisation (RO) is responsible for the enforcement of the national licensing requirements. Each Country’s RO follows recognised procedures and in a limited number of cases includes a fee for registering the terminal. This can be on a per registration basis $100-$500 each time or an annual fee of approx $150 a year. RO’s application forms, procedures and fees can be obtained from your current AA. Alternatively the RO’s contact numbers can be obtained from Inmarsat who can provide you with the relevant forms and details of their approved AA’s or ISP’s.



5.1.3 Contractual / Technical

The MES operator or owner must agree to the Inmarsat Terms and Conditions for the Utilisation of the

Space Segment, and realise that any violation of these terms and conditions could result in the suspension of or permanent withdrawal of access to the space segment. A technical requirement is that the Fleet MES must be a model that is Type Approved by Inmarsat.

5.2 Service Activation Process

The owner of an MES or anyone who is acting on behalf of the owner can initiate Service Activation, however, an applicant who is not the owner (for example, an agent) must pass the Service Activation

Registration form to the owner for signature. RO’s will refuse to activate a terminal where these terms have not been accepted and signed by the MES owner.

The applicant selects the Accounting Authority or ISP who will be responsible for processing the traffic charges associated with the terminal. The details of the owner, MES and billing arrangements are recorded on the Service Activation Registration Form which is then signed by the owner of the MES and forwarded to the chosen Routing Organisation (RO) or in some countries, for example the UK, a

Point of Service Activation (PSA) for approval and commissioning with the allocation of a set of

Inmarsat Mobile Numbers (IMNs).

After processing and approving the application the RO (or PSA) forwards the information electronically to the Inmarsat Customer Activation Group at Inmarsat headquarters in London, England who ensure that the details of the MES are transmitted to all Land Earth Stations so that access may be granted.

The Inmarsat F77 / F55 Service Activation process is automated and normally takes about 24 hours

(though often much sooner) providing there are no queries related to the application.

Inmarsat F77 / F55 Service Activation follows the process specifically for maritime terminals. Also because of the Multi Subscriber Numbering (MSN) facility in F77 / F55


Inmarsat Confidential F77 & F55 Services and Applications Reference Manual it will be necessary at the time of Service Activation to request sufficient IMNs for the number of devices that are to be attached to the F77 or F55 MES. There is no limit to the number of IMNs that can be assigned to a particular MES but the number of devices that can be attached to a particular service will be limited by the specification of the MES and is normally eight.

5.3 Inmarsat F77 / F55 MES Numbering

Inmarsat Serial Number (ISN)

The Inmarsat Serial Number (ISN) is a unique number assigned by an MES manufacturer to each newly manufactured MES. The Inmarsat Serial Number (ISN) and the SIM card Serial Number (SSN) are used to identify the MES or SIM card respectively and should be displayed prominently on the

MES or SIM card. The SIM card for an F77 / F55 MES is similar to that of mini-M The Inmarsat

Serial Number (ISN) for an Inmarsat F77 / F55 MES takes the following form

T

1

T

2

AA NN xxxxxx where:

T

1

T

2

ISN Type-digits: 66

AA Manufacturers ID code

EB

TT

Nera

Thrane & Thrane

AE

JR

STN Atlas/ECI

JRC

ES EMS

NN MES type ID code xxxxxx Forward ID of MES (6-digit Hexadecimal)

Inmarsat Mobile Number (IMN)

The Inmarsat Mobile Number (IMN) is the subscribers’ number, which is used for calling a Mobile

Earth Station (MES). It performs exactly the same function as a PSTN or ISDN number. The exact form of the IMN varies from one Inmarsat service to another and so can be used to verify the type of service associated with the number.

The Inmarsat Mobile Number (IMN) for an Inmarsat F77 / F55 terminal takes the following form

T

1

T

2

X

1

X

2

X

3

X

4

X

5

X

6

X

7 where: -

T

1

T

2

= Double T-digit - 76 for F77 / F55 AMBE voice & 9.6kb/s fax & data service and 60 for

56/64/128kbps, and X

1

-X

7

= Freeform decimal number

F77 & F55 IMNs are assigned by Inmarsat and are distributed in batches to Routing Organisations

(ROs) / Points of Service Activation (PSAs) for allocation to their maritime customers.

5.4 User familiarisation

The main objective of an Inmarsat F77 / F55 system provider should be to provide an application that is as simple to use as its ISDN equivalent

In practice certain applications may require some configuration changes to optimise performance over the Inmarsat F77 / F55 but once this has been carried out the operation of the application should be no different to using the application in an ISDN terrestrial environment.

The actual operation of the equipment should be done whenever possible using an ISDN line in the first instance so that the user can become familiar with the operation of the equipment without running up an unnecessary satellite traffic bill.

5.5 Post-sales support

Once installed it would be reasonable to expect the equipment to function reliably for its working life.

Modern IT equipment has a high degree of reliability and equipment failures are decreasingly likely to be the cause of application failures. More likely causes of application failure are likely to be:



•

Operator error (new crew/shift)

•

ISDN unavailability (equipment disconnected or ISDN line allocated for something else)

•

Calling Line ID screening

•

ISDN features not supported by Inmarsat network

In the ideal world, the F77 / F55 system provider would have a duplicate system in the office so that test calls can be made in the event of problems to determine if the problem lies at the remote location or in the office. See Trouble-shooting tools and techniques below.

It is often the case that users become at least as familiar and often more familiar with the day-to-day performance of the F77 / F55 application than the equipment supplier. On this basis it makes good sense to review the performance and use of the equipment from time to time with the customer so that strengths and weaknesses can be identified and possible improvements made for future systems. Your equipment supplier will for example register you on their bulletin board or keep you informed of all the latest updates and any necessary fixes or upgrades to the equipment. The latest software application packages also need to be reviewed regularly in terms of their compatibility to the Fleet equipment and

Inmarsat network. This is equally important when advising customers of the most appropriate software packages.



6. ISDN

Overview of ISDN

ISDN or Integrated Services Digital Network is the ITU-T (formerly CCITT) term for the digital public telecommunications network. It is offered in two packages - Basic Rate and Primary Rate.

Basic Rate, also known as 2B+D, provides two 64Kbps (B) data channels and one 16Kbps (D) signalling channel. It is intended to provide service for individual users and business applications such as

LAN data links or high quality audio feeds for broadcast media applications. It is provided as a dial-up service by the local telephone service provider and is charged for, like a normal telephone service, on the basis of a standing (monthly or quarterly) charge and a usage charge per minute. The usage charge per channel is similar to normal telephony rates.

Primary Rate provides up to 30 x 64Kbps (B) data channels and 1 x 64 Kbps (D) signalling channel. It is aimed at high bandwidth business applications such as video-conferencing and high capacity ondemand LAN bridge/router links.

Because the Inmarsat F77 / F55 service operates at only 64Kbps it is normally used with the Basic Rate

ISDN service but can be used on Primary Rate with applications that can operate on a single B-channel.

For example, a remote video-conferencing user is able to dial into a high capacity group videoconferencing system using just a single Inmarsat F77 / F55 channel, albeit with reduced video quality.

At an ISDN subscriber’s premises the point at which the ISDN telephone line terminates is known as the U-interface. The ISDN connection is terminated at the U-interface by a Network Termination device known as NT1. This is normally permanently wall mounted. In the US the customer is responsible for providing the NT1, in the rest of the world it is provided by the ISDN service provider as part of the ISDN service.

ISDN Physical Line Configurations

The ISDN subscriber interface at the NT1 is known as the T point or T-Interface. If a second network termination device such as an ISDN switchboard is connected to the NT1 at the T-interface this is designated the NT2 and the ISDN subscriber interface is then the S point or S-interface. The physical and electrical characteristics of the S-Interface and T-Interface are identical and they are usually referred to as the S/T-interface or S/T bus (also S0 interface and S0 bus). Physically the S/T interface is an RJ-45 connector. It is to the S/T-interface that the subscriber equipment is connected.



Interface conversion between the S/T bus and the serial communications interface on the subscriber

Data Terminal Equipment (DTE) is carried out using an ISDN Terminal Adapter (TA). Nowadays most equipment capable of being used with ISDN can be supplied with an integral ISDN Basic Rate Interface

(BRI). The DTE can be any type of data equipment such as a video-conferencing system, bridge/router or audio codec. The TA is also known as the Data Communications Equipment or DCE.

Stand-alone TA’s can be ordered with either a dual channel 2B+D BRI or a simple single channel B+D

BRI. As an Inmarsat F77 / F55 channel is equivalent to a single B-channel consideration may be given to using a single channel TA for use with Inmarsat F77 or F55 applications, as the single channel TA will normally be less expensive than a 2B+D unit. However, a dual channel TA will permit communication with two separate Inmarsat F77 / F55 applications in different locations simultaneously and will also facilitate testing and fault finding (see Trouble-shooting tools and techniques).

There are several differing implementations of ISDN worldwide. Protocol conversion between differing

ISDN standards is carried out transparently by the national telephone service providers. However,

ISDN BRIs differ with the different ISDN standards and so care should be taken to specify the correct country of use, and hence ISDN BRI, for the base station equipment. If the DTE to be used with the

Inmarsat F77 / F55 terminal uses a serial communications port (normally either X.21 or RS-232) it will be independent of any ISDN standard.

ISDN User Interfaces

ISDN is normally implemented using existing two-wire, twisted-pair conductors from the local telephone exchange to the customer premises up to a maximum distance of 5.5km from the exchange.

At the customer premises the point of termination of the incoming ISDN telephone line is known as the

U-interface. The incoming ISDN line is terminated at the U-interface by a Network Termination device known as an NT1.

In North America it is the responsibility of the customer to provide the NT1 but in most of the rest of the world the NT1 is provided and installed by the telephone company. Physically the NT1 is like an oversized telephone line-box and is normally wall-mounted.

The customer interface of the NT1 is known as the S/T-bus or S0 interface and utilises an eight-wire

RJ-45 interface. In point-to-point applications, the S/T bus can connect equipment up to 1000 metres apart. When used in a passive bus configuration (i.e. connecting up to eight terminals) it can span a distance of up to 500 metres. The name S/T-bus comes from the letters used in the ISDN specifications used to refer to two reference points, S and T. Point T refers to the connection between the NT1 device and the customer supplied equipment (e.g. data terminal, telephone, fax machine). Customer equipment can connect directly to the NT1 at point T, or there may be a PBX (Private Branch

Exchange, i.e. customer owned telephone exchange). When there is a PBX present, point S refers to the connection between the PBX and customer terminal equipment. The specification for the T interface is identical to the specification for the S interface. In ISDN terminology ‘terminal’ can mean any sort of end-user ISDN device, such as data terminal, telephone or fax machine.

Interface conversion between the terminal equipment and S/T-bus is carried out using a Terminal

Adapter (TA). The Terminal Adapter is typically packaged in a similar fashion to modems i.e. either as a stand-alone unit or as a built-in PC-card or module for various types of communications equipment

(such as bridge/routers or PBX’s). Stand-alone TA’s are supplied configured with a standard serial communications interface such as RS-232, V.35 or X.21. The customer according to the application normally specifies the interface. Nowadays most equipment capable of being used with ISDN is supplied with a built-in ISDN Basic Rate Interface (BRI) as standard or may be ordered with a BRI as an option.



ISDN Dialling and numbering

As the ISDN numbering system follows the same pattern as the normal telephone system dialling is carried out in exactly the same manner as making a normal telephone call. The subscriber number is used with the same area codes as the telephone network and international codes are also the same and used in the same way as for the telephone network.

International access codes (i.e. the prefix used to obtain an international line) are also the same with the exception of the UK, which uses the prefix 00+, but in locations served by older switches, the older prefix of 000+ is still used.

Fixed-to-Mobile Dialling

Calls to an Inmarsat F77 / F55 terminal, are made in exactly the same manner as a normal international

ISDN call. Dial the international access code, followed by the Ocean Region code and finally the

Inmarsat Mobile Number of the Inmarsat F77 / F55 MES.

Note that in most countries the ISDN network will route automatically to a predefined LES. In some cases the LES will not support the F77 / F55 service required. The fixed caller must check with their tele-comms provider.

The general format is: -

International access code + Ocean Region code + Inmarsat Mobile Number (IMN)

Where

The Inmarsat Global Ocean Region Code (SNAC) is 870, however, there may be some LESs where the Ocean Region Code has to be manually selected as follows: -

Atlantic Ocean Region-East

Pacific Ocean Region

871

872

Indian Ocean Region 873

Atlantic Ocean Region-West 874

The remaining Inmarsat Mobile Number (IMN) dialled is of the form:

7 6 X

1

X

2

X

3

X

4

X

5

X

6

X

7 or 6 0 X

1

X

2

X

3

X

4

X

5

X

6

X

7

Mobile-to-Fixed dialling

Prior to dialling the destination ISDN number the following parameters on the Inmarsat F77 / F55 MES need to be set: - a. F77 / F55 channel speed - 56 or 64kbps b. LES to be used - ensure that the selected LES is capable of handling Inmarsat F77 / F55 c. MES mode

The procedures for checking and setting these parameters are given in the manufacturers Operating

Guide for each MES.

Once these parameters have been set the call is dialled as follows:

00 + Destination Country Code + ISDN subscriber number + #

Some F77 / F55 applications, such as LAN bridge/routers and File Transfer Systems, are capable of automatic dialling in which case the above dialling string can be programmed into the equipment in accordance with the manufacturers instructions.



Terrestrial ISDN Multi Subscriber Numbering (MSN)

ISDN supports Multi Subscriber Numbering or MSN. MSN is a facility whereby more than one telephone number can be allocated to an ISDN line. Each incoming number on the same ISDN line (up to a maximum of two simultaneous calls as there are only two channels per line) can be routed to a different piece of equipment depending on the phone number called. For instance one number might route straight through to a fax machine on an analogue port, whilst another number might go to a telephone and yet another number might go to the serial port on a terminal adaptor.

MSN allows you have up to 10 directory numbers associated with an ISDN line. Each device connected to the ISDN line will need to be configured with its MSN number so that it can recognise and respond to incoming calls. Typically, the numbers will be the same apart from the last digit, which will be assigned the digits 0-9 thus giving 10 individually assigned numbers.

Using MSN with the Inmarsat F77 / F55

In the same way that an incoming ISDN call can be routed to a specific ISDN device, an Inmarsat F77

/ F55 MES can be programmed to route calls to specific devices attached to it. So, for example, a

64kbps data call could be connected to a router, a 64kbps video call could be connected to a video conferencing system or video phone and an incoming G-3 fax call could be connected to a G-3 fax machine connected to the 64kbps 3.1kHz audio service.

At the time that the Service Activation form is completed an IMN should be requested for each device that will be attached to the MES. Remember there is no limit to the number of IMNs that can be assigned to a particular MES although the number of devices that can be attached to a particular service will be limited by the specification of the MES and is normally eight.

To assign an IMN to a particular device an MSN number and the Terminal ID corresponding to the

IMN must be programmed into the MES. This procedure will vary between MESs and should be carried out in accordance with the manufacturers instructions. The ISDN device must also then be programmed with the same MSN in accordance with the ISDN device manufacturers’ instructions.

Once this procedure has been successfully carried out any calls coming in on that particular IMN will be automatically routed to the ISDN device corresponding to that IMN.

6.1 Fleet F77 128Kbit/s Mobile ISDN

Introduction

In March 2005, Inmarsat announced the operational availability of a new service: 128K Mobile ISDN, operating via a new, dedicated high-speed channel. A separate technical guide to the F77 128K is available from Inmarsat

(see http://fleet.inmarsat.com/support ).

Benefits of 128kbit/s ISDN

High-end users of mobile ISDN have traditionally met their bandwidth requirements by “bonding” two

64kbit/s channels. This has required the operation of two Fleet F77 terminals, together with specialist multiplexing hardware; additional overhead is associated with bonding two channels. The new 128kbit/s

Fleet service represents a more cost-effective and efficient HSD option which requires only a single

Fleet F77 terminal and standard approved antenna.



Typical applications for F77 128K Mobile ISDN include:

•

Video conferencing (e.g. H320, H264)

•

Data intensive applications (e.g. government / mission critical applications)

•

Faster I.P. access via Dialup Networking

•

Effective transfer of large files

Users of automated data transfer software can potentially experience an immediate benefit in terms of improved cost savings and terminal availability, given the same email volume requirement.

Implementation

Owners of existing Fleet F77 terminals wishing to access the 128Kbit/s service will require a software or software/hardware upgrade from their terminal supplier, who should be consulted to provide the terms of supply. New Fleet F77 terminals from participating manufacturers will be provided with embedded firmware that automatically enables a 128kbit/s service. Users should also confirm with their airtime provider and Land Earth Station Operator (LESO) that they support the 128kbit/s service.

N.B. IMN Numbering for this service is unchanged from the 64Kbit/s format. See section 5.3.

Coverage

F77 128kbit/s ISDN is delivered to the Inmarsat 3 spot beam coverage areas. Spot beam services, including F77 128Kbit/s ISDN, are due to be extended with the availability of Inmarsat 4 coverage areas (NB all other Fleet F77 services are available in the full global beam areas into four ocean regions). For the latest coverage status, visit www.inmarsat.com/coverage .

Operation

§ Prior to making the call a user selects the required ISDN speed and dials the appropriate number.

§ For ship-to-shore initiated calls the mobile user selects a 128kbit/s service (by dialling prefix

“906”- refer to manufacturer’s user instructions) and a connection is made from the Fleet terminal, across the Inmarsat network and on to the terrestrial user. This initial connection utilises only half (64kbit/s) the available bandwidth.

§ If a 128kbit/s channel is available on the satellite link and the terrestrial user is able to accept the call at this connection speed then the remaining 64kbit/s is assigned.

§ If no high-speed satellite channels are available, or the terrestrial user is unable to accept the call or the connection speed is compromised mid-call, the mobile user is notified and the connection is terminated. The user then has the option of redialling and trying to connect over

64kbit/s.



§ For shore-to-ship initiated connections the shore user dials an Inmarsat Mobile Number (IMN) associated with the 128kbit/s service. An initial connection is opened to the MES using half the

128kbit/s channel capacity and a request made for a 128kbit/s satellite connection to the mobile user. If a 128kbit/s channel is available and the mobile user is able to accept the call the remaining 64kbit/s available within the channel is allocated and a true 128kbit/s connection is established.

In both ship-to-shore and shore-to-ship connections the call will be closed if either the sender or receiver clears either of the 64kbit/s channels.

128K Applications

Your terminal hardware provider should first be consulted to provide specific advice on the compatibility of applications such as Videoconferencing and dialup networking access to Internet

Providers (N.B. variability may be experienced in the performance of different applications at

128Kbit/s). See also the F77 128K guide for further details: http://fleet.inmarsat.com/support

N.B. for simple, direct access to Internet connectivity using the 128K service, please consult your service provider for details of Special Access Code services (“SAC” codes - e.g. 28#, 67#); this enables the user to connect directly to the LESO’s own Internet POP (Point of Presence), and no separate

Internet Service Provider account is required by the end user.

7. MPDS & IP Internet protocols

Internet Protocol is the protocol by which data is sent from one computer to another on the Internet.

Every computer on the Internet has at least one address (IP address) that uniquely identifies it from all other computers on the Internet. The Internet protocols are the world's most popular open-system

(non-proprietary) protocol suite because they can be used to communicate across any set of interconnected networks and are equally well suited for LAN and WAN communications. The Internet protocols consist of a suite of communication protocols, of which the two best known are the

Transmission Control Protocol (TCP) and the Internet Protocol (IP). The Internet protocol suite not only includes protocols such as TCP and IP, but it also specifies common applications such as electronic mail, terminal emulation, and file transfer. Because IP is the protocol of the Internet it has become the choice for many corporate and private networks. Inmarsat MPDS via F77 & F55 supports the same protocol and so is highly compatible with these networks.

IP packet data

A packet is a block of data with a header attached that indicates what the packet contains, its destination and other information about the data. A packet can be considered to be a data envelope with the header acting as an address. Generally packetisation of data creates an overhead of 5-10% in addition to the original data although the exact level of overhead will vary depending upon the application and protocol used.



Internet Protocol is the most commonly used packet data communication mechanism and contains several types of information, as illustrated below:

IP Packet structure

The IP packet fields are described as follows: -

Version

Indicates the version of IP currently used.

IP Header Length (IHL) Indicates the datagram header length in 32-bit words.

Type-of-Service Specifies how an upper-layer protocol would like a current datagram to be handled, and assigns datagrams various levels of importance.

Total Length

Identification

Flags

Specifies the length, in bytes, of the entire IP packet, incl. the data and header.

Contains an integer that identifies the current datagram.

This field is used to help piece together datagram fragments.

Consists of a 3-bit field of which the two low-order (least-significant) bits

Fragment Offset

Time-to-Live control fragmentation. The low-order bit specifies whether the packet can be fragmented. The middle bit specifies whether the packet is the last fragment in a series of fragmented packets. The third or high-order bit is not used.

Indicates the position of the fragment's data relative to the beginning of the data in the original datagram, which allows the destination IP process to properly reconstruct the original datagram.

Maintains a counter that gradually decrements down to zero, at which point the datagram is discarded. This keeps packets from looping endlessly.

Protocol

Header Checksum

Source Address

Destination Address

Options

Data

Indicates which upper-layer protocol receives incoming packets after IP processing is complete.

Helps ensure IP header integrity.

Specifies the sending node.

Specifies the receiving node.

Allows IP to support various options, such as security.

Contains data information.

IP V4 addressing

Every computer on a TCP/IP network is identified by a unique 32-bit IP address, which also specifies routing information inter-network. An IP (version 4) address uses dotted decimal notation, with each eight bits of an IP address (called an octet) separated from the next eight bits by a period. An IP address is a single value that looks like this:

102.54.94.97. This contains two important pieces of information:

•

The network ID, which is the portion of the IP address that identifies a group of computers and other devices that are all located on the same logical network.



•

The host ID, which identifies a particular computer within a particular network ID. A host, or node, is any device that is attached to the network and uses TCP/IP.

Each host on the network uses the network ID and host ID to determine which packets it should receive or ignore, and to determine the scope of its transmissions (only hosts with the same network ID accept each other’s IP-level broadcasts). The network number identifies a network and must be assigned by the Internet Network Information Centre (InterNIC) if the network is to be part of the

Internet. An Internet Service Provider (ISP) can obtain blocks of network addresses from the InterNIC and can itself assign address space as necessary. The host number identifies a host on a network and is assigned by the local network administrator.

The Internet uses address classes to differentiate networks of various sizes. IP addressing supports five different address classes: A, B, C, D, and E. Only classes A, B, and C are available for commercial use.

The network class can be determined from the first octet of its IP address. The following table summarizes the relationship between the first octet of an IP address and its network ID and host ID.

The table also identifies the total number of network IDs and host IDs for each address class that participates in the Internet addressing scheme. This sample uses w.x.y.z to designate the four octets of the IP address.

Class w values

1

Network ID

A 1–126

w

B 128–191

w.x

C 192–223

w.x.y

Host ID

x.y.z y.z z

Available networks Available hosts per net

126 16,777,214

16,384 65,534

2,097,151 254

1

Inclusive range for the first octet in the IP address. The address 127 is reserved for loop-back testing and inter-process communication on the local computer; it is not a valid network address. Addresses 224 and above are reserved for special protocols and cannot be used as host addresses.

Because the sender’s IP address is included in every outgoing IP packet, the receiving computer can derive the originating network ID and host ID from the IP address field.



IP address assignments

IP addresses are assigned to devices as either static IP addresses or dynamic IP addresses. Generally, any device that is permanently connected to a network, such as the Internet, is assigned a static address that will not change. Devices that are not permanently connected to a network, again using the Internet as the most common example, such as dial-up Internet users, are assigned dynamic IP addresses. The

DHCP server assigns these for the duration of the network connection only. When the session is terminated (or times out) the IP address is returned to the ‘pool’ and reassigned to the next user requiring one. Every time a dial-up user connects to the network a different IP address can be assigned.

Private IP address ranges

The following address ranges are set as private and cannot be routed on the Internet. If they do appear on the Internet they are ignored and discarded.

10.0.0.0 to 10.255.255.255 172.16.0.0 to 172.31.255.255 192.168.0.0 to 192.168.255.255

Network and broadcast addresses

By convention, if an IP address contains all zeros after the NET ID, then the packet is treated as ‘this network’ or the network address. If an IP address contains all ones after the NET ID, then the packet is treated as a broadcast and will be received by all the hosts.

For example: 192.168.10.0 = Network address, 192.168.10.255 = Broadcast address.

Sub-nets

The use of sub-nets is very widespread due to the shortage of available IP address space and the fact that although many computers operate on closed (private) LAN networks, they are rarely occur in a convenient multiple of 2 to efficiently fill one Class. A subnet takes some bits from the host portion of the address by the use of a subnet mask, which tells the network which part of the address is the host range. In this way you can create multiple subnets, which can serve separate sites. For example, a subnet can be configured which supports four sites from the class C address 192.168.10.0, each being properly addressed with a useful host range (of 62 hosts per site) and network and broadcast addresses:

Site: A B C D

Host range: 192.168.10.1-62 192.168.10.65-126 192.168.10.129-190 192.168.10.193-254

Broadcast: 192.168.10.63

Network: 192.168.10.0

192.168.10.127

192.168.10.64

192.168.10.191

192.168.10.128

192.168.10.255

192.168.10.192

The net mask in this case will be 255.255.255.192 or FF.FF.FF.C0

h

TCP and UDP

Transmission Control Protocol (TCP) is connection-oriented; meaning is a controlled end-to-end dialogue keeping track of the arrival and acknowledgement of datagrams. User Datagram Protocol

(UDP) is usually used by transaction – oriented applications, which keep track of responses. E.g. the datagram or request will be re-sent if the expected response is not received. Connectionless UDP is also applicable for broadcast signals (no point in acknowledging those) and Voice over IP (VoIP) applications since non-receipt and re-sending is not appropriate for a voice service.

Port assignments

In addition to the IP address, a ‘port’ number is associated with each virtual connection. For the purposes of setting firewalls etc, IP port numbers and their assignments, can be looked up at: http://www.iana.org/ .



8. Network security issues

Any computing device that is capable of connection to a public network (for example, the Internet or

PSTN) is potentially vulnerable to unauthorised access by third parties – commonly known as

‘hacking’. This is not a satellite-specific issue and the many individuals and organisations that have a permanent network connection to the Internet or dial-up network access for remote users will already be very familiar with the protection of their networks through the use of firewall technology. ‘Alwayson’ access to the Internet via MPDS will be subject to exactly the same controlled access as a ‘normal’ remote user - the use of MPDS on F77 or F55 neither enhances nor degrades the security of the network.

The section below on Network Security, discusses some of the elements of firewall technology. This is highly recommended for use by MPDS customers. The section on Remote User Security, discusses some of the security issues faced by users with permanent Internet access, using for example cable,

MPDS or ADSL, and how these issues can also be applicable to Inmarsat MPDS users.

Network security

Firewalls are software or hardware-based security components that divide computer networks into two logical segments: an unsecured side that remains exposed to computer users from the outside world, typically to provide access to Web servers or other such public parts of a network; and a second, secure side that’s off-limits to intruders but remains accessible to authorised users.

Firewalls give authorised LAN users the freedom to connect into or out of a network – to use email, to access the Internet, or to make remote-access connections into a central LAN from a remote computer or network. They enable system managers to provide the far-reaching flexible access that ‘customers’

(both internal and external to a network) demand, while at the same time limiting a network’s exposure to interlopers – either malicious or accidental.

A firewall helps to implement a security policy that defines the services and access permitted; it guards the site at its front door. A firewall can be a router, a personal computer, a host or a collection of hosts, set up specially to shield a site or subnet from protocols and services that can be abused from hosts outside the company. A firewall possesses the following properties:

•

All traffic from inside to outside, and vice-versa, must pass through it.

•

Only authorised traffic, as defined by the local security policy, is permitted through it.

•

The firewall system itself is immune to penetration.

Helpful and detailed advice on PC privacy protection and security can be found online from http://www.theguardianangel.com/ .

8.1 Remote user security

Regular Internet user will be familiar with the threat posed by hackers breaking into on-line computer systems. These illegal attacks are carried for various reasons and personal computers or small office networks are just as likely targets as large computer systems. So how does a hacker identify a potential target? Frequently it starts with a port probe. Internet networking software (using TCP/IP) uses ports

(sometimes called ‘sockets’) to communicate. These software ports are the logical way that data is routed around the network (for example a web host will use port 80 initially).

A hacker will scan a list of Internet addresses making a blind connection attempt to various port numbers. If any response is received – even an error or access-denied message – then the hacker knows that a service is running on that machine. On an unprotected machine the rest of the process (i.e. gaining access to your files) is easy to an experienced hacker.



There are two principal modes of connection to the Internet:

•

Circuit-switched dial-up such as Mobile ISDN or the 9.6kb/s async data service.

•

Permanent always-on network access such as that provided by ADSL, LAN or MPDS.

A dial-up user will typically dial into a local PoP. Once a connection is made the user is assigned an IP address (dynamic IP address) and is connected to the Internet for the duration of the dial-in session, which may be anything between a few minutes and a few hours. When the call is terminated the

Internet connection is closed and the dynamically assigned IP address reallocated to another user. A subscriber to cable or ADSL enjoys a permanent connection (24hrs/day) to the Internet and is assigned either a permanent (static) IP address or a temporary one that is assigned for weeks or even months at a time.

From a hacker’s point of view a dial-up connection provides less of a window of opportunity to probe a users machine compared to a permanent connection because of the normally relatively short connection time. In addition, because a dial-up user is invariably assigned a dynamic IP address it is highly likely that the address will have been reassigned by the time the hacker has figured out how to break into the target machine.

Therefore any always-on Internet connection, such as MPDS, is a potential target for computer hackers. This is not a satellite-specific issue but a problem that exists for any computer or network that is permanently connected to the Internet.

8.2 Viruses

There is a variety of malicious software available, which can perform attacks such as: denial of service, system disruption, unauthorised access to computer systems, misuse of telecommunications facilities and even computer-based fraud. This poses a significant threat to all connected computer systems anywhere on the Internet. The cost of recovering from a security breach can be substantial whereas tracking down a potential intruder can pose a real challenge. The main categories of such programmes are: a) A virus is a self-replicating programme that can infect other programmes. When an infected program is executed, this will cause viral code within the programme to be run as well. b) A worm is a programme, which attacks computers that are connected by a network and spreads by sending a copy of itself through the network to infect another machines. The main difference between a worm and a virus is that worms are separate entities whereas viruses are attached to programmes. The effects can be similar, however. c) A Trojan horse is a programme that pretends to be something it is not. Often it has the same name as a legitimate file, but only to deceive, and when executed, may perform an unexpected behaviour.

You can check your PC against potential vulnerability to Trojans online at http://www.antitrojan.net/ . d) A Trojan mule - this term most often refers to the fictitious login screen. Then user treats this simulation as a genuine login screen and enters his confidential ID and password. The Trojan mule intercepts these data and terminates. This effectively reveals a user's ID and password.

The basic rule of protection against viruses is to use multi-layered protection, including anti-virus software and check every programme before it is actually used. KEEP THE ANTIVIRUS

SOFTWARE UP TO DATE.



8.3 Firewalls

The obvious solution then is to equip your computer or network with some sort of firewall. A shipborne network will typically use a scaled-down version of the type of firewall that large corporate networks use whereas a software firewall is ideal for a smaller vessel where space and convenience may be paramount.

All firewall software gives at least the most basic protection. It blocks unauthorised inbound access to the PC, on various port numbers, from the Internet. The PC shouldn’t respond at all (e.g. ‘stealth mode’) and it should appear invisible. All unsolicited inbound access attempts are blocked regardless of source. Outbound traffic is monitored and only responses from contacted hosts are permitted back in.

Firewalls can also filter outbound connections (from the PC to the Internet). Some viruses and Trojans

(see Viruses section below) try to make surreptitious outbound connections – sometimes to transfer information like passwords or credit-card data and sometimes to allow someone else to connect to the

PC through the ‘back door’. The effective use of anti-virus software will minimise the need for outbound filtering.

Software firewalls

Below is an example of a software firewall showing all the logical protocol connections running under

Windows 2000 Pro



.

Agnitum

 Outpost

This firewall example can be downloaded from http://agnitum.com/ .

Built-in firewall profiles are pre-set to model the safe behaviour of download managers (e.g. FTP),

WEB browsers (HTTP), standard Microsoft Office



products etc. All NetBIOS activity can be blocked. Additional add-ins support the blocking of content such as WEB site adverts, Active X controls, Java scripts, pop-up windows, cookies and potentially malicious email attachments. An optional DNS server is also provided. There is also an attack detector, which monitors and logs any connection requests to your PC from unauthorised sources. This software firewall also offers a full

‘stealth-mode’ as described above.



Whenever a new IP or NetBIOS connection is requested the firewall prompts the user whether the connection type, port number and application is authorised. See below:

As can be seen from the software firewall’s ‘Allowed’ list (below) – every parameter of the connection can be set up in the customised rules wizard to be allowed or blocked – according to protocol, direction,

IP address, local port number, remote port and application name.

These can be modified and updated at will as more knowledge is gained of the behaviour of your applications.

If you are in doubt about the protection your firewall offers there is a WEB-based utility available at http://www.pcflank.com/ , which tests firewalls (benignly fortunately). Connect to the site and check your protection on-line!



Zone Alarm



This can be downloaded from http://www.zonelabs.com/ and is similar to Outpost



:

Each known application can be permitted access to the Internet or the ‘trusted’ intranet. The firewall

‘learns’ the users profile of common applications and has profiles built-in for easy initial set-up.

Programs’ access can thereafter be added and deleted under user control and unknown connections are flagged to the user, who has the opportunity to add them to the permitted applications or block them.

Unexpected connections or ‘attacks’, which are clearly not genuine applications, are reported to the user via an alert window as shown above right.

McAfee



Other popular firewall and virus software is available from http://www.mcafee-at-home.com/ .



9. Trouble-shooting tools and techniques

Installation and testing

It is good practice to check any Inmarsat F77 / F55 ISDN application first on a terrestrial ISDN line.

This can be done on a single Basic Rate line as only one 64Kbps (B) channel is used for the application.

Calls can therefore be made from one B channel to the other. An ISDN to ISDN test will verify that the application works in the office environment. The next test should include the satellite delay. Many off the shelf applications will not have been tested with a round-trip delay on the order that can be expected with the Inmarsat F77 / F55 Service (i.e. ~500ms).

Each end of the application can be connected to the ISDN BRI either directly, if the equipment is fitted with a BRI, or through the ISDN Terminal Adapter (TA) if only the serial interface is available using interface converters as necessary (see Trouble-shooting tools and techniques below). If required both ends of the application can be connected to the dual channel TA and calls made from one DTE to the other. If the DTE equipment does not have dialling features calls can be initiated from the TA either via the front panel or from a PC connected to the control port on the TA.

A typical pre-installation checklist may comprise the following checks:

•

Has the MES been activated?

•

What is the MES F77 or F55 IMN? (Leave a note of this at the ISDN equipment for fixed-mobile dialling).

•

Does the chosen LES support F77 or F55? (Check for all Ocean Regions). If registered with an ISP, have the correct LES/s been defaulted into the MES?

•

Is the ISDN number valid and functioning and not being used for another application (This is a common installation problem. Always check the ISDN number using a terrestrial link first)

•

Does the ISDN number have international access if connected to a PABX (for fixed-mobile dialling)?

•

Is the application configured, if required, for satellite propagation delay?

Basic test tools

•

ISDN Basic Rate line.

•

Dual channel ISDN Basic Rate Terminal Adapter (TA) with front panel or control port dialling.

•

Cables as required

•

Loop-back connectors - see below



Using Microsoft Windows

 98 System Monitor

Microsoft Windows 98 contains, as standard, a very simple but useful application called System

Monitor, which can be configured to monitor the data throughput of any of the COM ports. The output can be graphically displayed on the PC screen and will show quite clearly the nature of the data communications. The display can also be used to demonstrate to a customer the nature of the data in support of a recommendation to use either Inmarsat Mobile Packet Data or Mobile ISDN for a particular PC-based application.

System Monitor is accessed from the Start button on Windows 98 through Programs, Accessories,

System Tools, System Monitor. Configuration is as follows: -

Click on Edit, Remove Item – Remove any default settings.

Click on Edit, Add Item – Click on Dial-Up Adaptor,

Click on Total Bytes Transmitted – OK.

Click on Edit, Add Item – Click on Dial-Up Adaptor

Click on Total Bytes Received - OK.

Click on Options, Line Charts.

The resulting display (shown above whilst downloading a weather page from a Web site) will clearly show the data flow through the COM port.



Using Windows 2000

 Pro system performance monitor

Microsoft Windows 2000



Pro contains an even more useful application called System Performance monitor, which can be configured to show the data throughput of your TCP/IP connections. Again, the output can be graphically displayed in a window.

The System Performance monitor is accessed from the Start button, then Programs, Administrative tools, Performance. If it is not found here it will need to be enabled by clicking Start, Settings, Taskbar

& Start Menu, Advanced and tick on Display Administrative Tools. Configuration is as follows: -

Right-click in the chart window and select Add counters. Under Performance Object select the appropriate dial-up-networking or network interface Then select bytes received or sent per second, or whichever set of parameters you wish to log. Set the scale to 0 to 20,000 to show a convenient range:

The resulting display shows packets sent and received through the relevant connection – and for MPDS or Mobile ISDN will give a good indication of the volume of data a particular application requires.



DU Meter



There is another very useful application called DU Meter



from Hagel Technologies, which provides an accurate account of the data, which is flowing through your network connection at any given moment. This readout is presented in both numerical and graphical format, in real time. DU Meter includes a logging and alerting facility, which can be triggered by data volume related events. It supports

Windows



95/98/NT4/2000 and XP. DU Meter works with most types of network connections including MPDS.

An example of continuous and stable data transfer as displayed by DU Meter is shown below:

A screenshot of the alerts and reports page is shown below:

As DU Meter can keep a log of the total volume of data sent and received it may be of use (on a packet network such as MPDS), in verifying the billable data volume sent over your MPDS connection. Note that in relation to data errors anywhere in the Internet or MPDS network, which result in TCP/IP datagram re-transmissions, the re-sent data is also billable.

A trial version can be downloaded from http://www.dumeter.com/ .



Data flow measurement freeware tools

It is strongly suggested that for detailed data flow measurement and analysis of MPDS or Mobile ISDN sessions that you download and install the IP-Consultant freeware tool developed by Inmarsat and Klas from http://www.klasonline.com/ . There is also a very useful cost-compare tool from http://www.imhotek.com

.

Loop-back calls

Loop-back connectors are a useful diagnostic tool for use with audio codecs, video conferencing, file transfer and hence store-and-forward video applications. They cannot be used with multiplexers or bridge/routers because of the nature of the communications.

Pin-out instructions for loop-back connectors for commonly serial interfaces are shown below:

Interface Type

RS-232

RS.449

Connector Type

Male Sub-D 25 pin

Male Sub-D 37 pin

Pin Connections

Connect pins 2 & 3

Connect pins 4 & 6 and 22 & 24

X.21

V.35

Male Sub-D 15 pin

Male Standard V.35 34 pin

Connect pins 2 & 4 and 9 & 11

Connect pins P & R and S & T

Loop-back connector pin connections

Loop-back connectors are used in conjunction with a TA and connected to one of the serial ports of the

TA. If the unattended TA is then left connected to the ISDN BRI back at the workshop or office, calls can be made to the TA from the remote location. The sent signal, be it audio, video, data or even the test output from a Fireberd



bit-error-rate (BER) test set, will be returned to the remote location on the return channel thus demonstrating the functioning of the link without having to have a second communications line open for confirmation from the destination that the communication is successfully being received.

LES assistance

In order to ascertain if an F77 or F55 channel is being assigned to the call, Short Code 33 can be dialled from the Inmarsat F77 / F55 MES for connection to the LES and the call monitored by LES staff. The call is free but the degree of assistance will depend upon the availability of staff at the LES.


Fleet 77 / 55 Services Applications Reference

Fleet F77 & F55

Services and Applications

Reference Manual

Version 2.5

March 2006

1. INTRODUCTION TO THE INMARSAT FLEET F77 & F55........................... 4

2. THE INMARSAT FLEET (F77 / F55) MARKET............................................. 11

3. OVERVIEW OF THE INMARSAT SYSTEM.................................................. 19

4. INMARSAT F77 / F55 TECHNICAL SOLUTIONS ........................................ 24

5. CUSTOMER SUPPORT PROCESSES ............................................................ 77

6. ISDN..................................................................................................................... 81

7. MPDS & IP INTERNET PROTOCOLS........................................................... 86

8. NETWORK SECURITY ISSUES ...................................................................... 90

9. TROUBLE-SHOOTING TOOLS AND TECHNIQUES................................. 95

Purpose

1. Introduction to the Inmarsat Fleet F77 & F55

1.1 4.8kbps Voice

1.2 64kbps UDI

1.3 64kbps Speech

1.4 64kbps 3.1kHz Audio

1.5 56kbps Data

1.6 Mobile Packet Data Service (MPDS)

1.7 2.4kbps Group 3 Fax

1.8 9.6kbps Group 3 Fax

1.9 Fleet F77 and F55 technical system enhancements

1.10 Fleet F77 and F55 Maritime Equipment

Nera

Thrane & Thrane

JRC

KVH

Fleet 55 Maritime Equipment

Nera

Thrane & Thrane

EMS

KVH

2. The Inmarsat Fleet (F77 / F55) Market

2.1 Positioning of Inmarsat F77 / F55

Government

Fishing

Leisure

Merchant

2.2 F77 / F55 vs. VSAT

2.3 Inmarsat Mobile ISDN

2.4 Inmarsat Mobile Packet Data Service (MPDS)

2.5 Inmarsat F77 / F55 applications overview

2.5.1 Navigation

2.5.2 DGPS corrections

2.5.3 Navigational chart updates

2.5.4 Obtaining weather reports

2.5.5 Safety, distress, MRCC and Coast Guard communications (F77 Only)

2.5.6 Interfacing with general analogue equipment

2.5.7 Secure communications

2.5.8 Fleet Management & the corporate WAN

2.5.9 World-Wide-Web (WWW) access

2.5.10 Email

2.5.11 Ship-to-ship communications

2.5.12 Cargo / vessel telemetry

2.5.13 Crew calling (welfare)

2.5.14 Videoconferencing

2.5.15 Using Microsoft

 NetMeeting

2.5.16 Universal Messaging

2.5.17 Voice and data multiplexing

2.5.18 File transfer

2.5.19 128kbps channel ‘bonding’

2.5.20 Group 4 facsimile

2.5.21 Telex

2.5.22 Tele -presence

2.5.23 Tele -medicine

2.5.24 Tele -education

3. Overview of the Inmarsat system

3.1 F77 / F55 Coverage map

3.2 Inmarsat 4 Coverage extension

3.3 Network Operations Centre (NOC) and LESs

3.4 How F77 and F55 calls are routed & billed

4. Inmarsat F77 / F55 Technical Solutions

4.1 Mobile ISDN BRI interface

4.2 Inmarsat Mobile ISDN versus Mobile Packet Data Service

4.3 Navigational chart updates