These are the actual figures from R&D as per June 6th 2006:

Note:

• Assumption for all the above are all-in-one configuration

• For split mode (USB, BT) standby times will be reduced down to 20hrs

The outdoor part of the WorldPro1000 (and even the whole unit when connected all-in-one and using the wireless interfaces) satisfies the tough requirements for the IP-44, making it a capable product suitable for the roughest outdoor conditions.     You may even achieve the IP grading of IP-42 when connecting the Worldset to the WorldPro1000/1010 using the specially developed IP protected ISDN cable (Part No 106499.)  

BGAN LaunchPad is available in two different editions;  

Personal Edition – this edition is for the personal user and has the following properties: 

• It is installed on a user’s machine via the standard installation CD and is customisable during installation and in-life.

• The end user can always personalise all of Launch Pad’s functions and features

• Only a single default user profile is available

• As only one profile exists, the user is not asked to select from a number of user profiles to log in, the BGAN LaunchPad simply opens. 

Corporate Edition – this edition is for the corporate end user and has the following properties:  

• The basic BGAN LaunchPad software is installed on the user’s machine via the installation CD but the user profile which defines certain features of the functionality of the BGAN LaunchPad is created by the corporate IT manager, or similar, using the ‘BGAN LaunchPad Corporate Profile Manager’. 

• Functionality of the user profile can be restricted by the corporate IT manager

• The number of profiles in the user profile library is unrestricted.

• Profiles are identified and selected via a user name and password.  Most customers are probably meant to use the Personal Edition. If you are unsure about which version you should use, please contact your service provider.

Yes, the numbers for the 4kbps BGAN voice service will be from the range 87077xxxxxxx.   

• 1xxxxxxxx   Inmarsat A           
• 3xxxxxxxx   Inmarsat B 
• 39xxxxxxx   Inmarsat B - 64 kbps        
• 4xxxxxxxx   Inmarsat C 
• 5xxxxxxxx   Aero                  
• 6xxxxxxxx   Inmarsat M          
• 60xxxxxxx   Fleet/GAN/Swift - 64 kbps  
• 76xxxxxxx   mini-M/GAN/Fleet
• 77xxxxxxx   BGAN                 

As can be seen from the list (taken from http://www.wtng.info), “870 77” is unique to BGAN and makes it possible to distinguish BGAN numbers from the other Inmarsat services. 

a. First, compile and send the message to recipient #1  (“write message” menu) 

b. When the message is sent, go to the menu folder “sent messages”. 

c. Select the message you just sent, then select “Read”

d. When the message is displayed, you select “Options” and then “Forward”

e. Now the message is displayed again, and when selecting “send” you can now specify recipient #2. 

f. Repeat b through e for as many recipients as you like

This will save you from compiling the same message over and over again.   In the current version Launchpad (v2.6.0), it is not possible to specify multiple recipients, nor is it possible to forward from the “Sent messages” folder. However, one workaround is copying the text (by CTRL-C) before sending it the first time and then pasting (by CTRL-V) it into each of the messages to the other recipients. 

Note: There will be sent one SMS for each recipient, and you will be charged accordingly.   

The WorldPro and the BGAN system supports a range of supplementary services, known from ISDN and 3GPP. 

The following supplementary services are already supported by Worldpro1000;

• CLIP – Calling Line ID Presentation

• CLIR -  Calling Line ID Restriction

• COLP – Connected Line Presentation

• COLR - Calling Line ID Restriction

• Call Forwarding services incl. CFU(unconditional), CFB(busy), CFNRy(no reply) and CFNRc (not reachable) 

• Barring services incl. BAOC, BOIC, BOIC-exHC, BIC-Roam   

• CUG – Closed User Group 

The following services will be available in 3Q2006:   

• HOLD – Call hold

• CW – Call waiting

As part of the BGAN program, Inmarsat has developed a TCP Performance Enhancing Proxy, also known as TCP-PEP. This is an application running on the PC connected to a BGAN terminal. Upon execution the TCP-PEP application modifies the PC’s TCP-IP stack to make the data transfer more efficient over BGAN.    

Inmarsat have carried out an extensive test campaign which has demonstrated a clear performance improvment in using TCP-PEP, in some cases up to [50-100%]. However, the improvements heavily depend on a number of factors e.g. type of traffic, file sizes etc.    

The verification testing of the TCP PEP is not yet completely finalised, but it is now undergoing Beta testing, and is expected to be launched to end-users 3Q2006. 

In BGAN, the terminal is typically referred to as UT(=User Terminal) or UE(=User Equipment). Connected to the terminal at the user side we have the TE (Terminal Equipment), which typically would be a handset or a laptop.

The BGAN network consists of RNS(= Radio Network System) and CN(=Core Network), delivered by Thrane&Thrane and Ericsson respectively.  Another term is SAS(=Satellite Access Station), this  encompasses all the BGAN equipment at the each gateway site (incl. RF and antenna). 

The old terminology referring to “Ocean Regions” has a maritime flavour which has not been considered appropriate to BGAN, which is a product family targeting land based customers initially.     

The two I-4 satellites used in BGAN are being referred to as F1, which is located at 64°E  (IOR position) and F2, which is located at 54°W (AORW position).  Assuming there will be a 3rd I-4 satellite in the future, it will be named F3 and most likely be position around 178°E (POR position).

Having done it once, this is a very straight-forward process.  Nera have made a diagram which explains the process step by step.

Please refer to  ftp://ftp.nera.no/mesbbs/Software/Nera_WorldPro/Software_upgrade_WorldPro.pdf, but you will also find it in the manual and the SW release notes.  It is also reproduced below for convenience.

1. Attach the terminal to the MAC via USB and power up in Mass storage mode.
2. The volume name of the WorldPro "disk" will be "untitled", open this to show the content.
3. Delete the current SW file present, on the MAC OS this is achieved by moving it to "Trash"
4. MAC OS does not delete the file, it makes a local non visible copy of it on the Flash device. Notice that the disk free space is unchanged despite the file being deleted. Important: To really delete the file it is now necessary to "Empty Trash".
5. Ensure that the Flash free space is now over 19MB
6. Copy the new CSW to the Flash device
7. When complete press the activation button and the burn sequence will start.
8. MAC OS does not refresh the disk contents, so when the burn is complete detach the USB cable, wait 2 seconds and reattach.
9. The status of the operation will now be shown in the "Status" file

First of all, there exist a number of scenarios where Launchpad loses contact with the WorldPro without there being any problem with USB link. For example when the WorldPro loses synch with BGAN network for a prolonged period (>10sec), it will do a silent deregistration and go back to Global beam search before trying to register again (automatically). In this case Launchpad will indicate “Connection lost to terminal” and you will need do select “search for terminal” within Launchpad before you get reconnected. Also, it may happen that Launchpad loses touch with which COM ports it should use. In this case, you should be able to correct the inconsistency by going to the “Current PC- Terminal interface” and request a automatic scan for the COM ports (alternatively, manually respecify them). In other cases, exiting and restarting the Launchpad application is required.

Assuming that you have determined that Launchpad is not the problem, here is a list of suggested actions for

recovering your USB connecvity:

1)     Exit all applications on your PC that may interfere; Have a look through your active programs and exit all that you suspect may interfere with the COM ports assigned to NeraWorldPro. For example, you should deactivate all modem application on your PC. (check under Modems in Device manager). To see if this helped, verify your USB connectivity again by “Query” under “Diagnostics” in Windows’ Device Manager. See also separate FAQ below for handling “interfering” applications.

2)     Remove cradles that may be connected to your PC; If your laptop is connected to a cradle, you should remove it and connect the USB directly to the PC. Verify USB connectivity again.

3)     Remove USB HUBs that may be connected to your PC; The same goes if you are connected to the WorldPro through a USB HUB. Remove it and connect the World Pro directly to your PC.Verify USB connectivity again.

4)     Unplug and replug the USB cable; observe that the “Nera dualport#1” and “Nera dualport#2”modems devices disappear (from Windows Device manager) as soon as you have unplugged. If this does not happen, remove these two entries manually. Observe that the Nera modem devices reappear when you replug the USB. Verify USB connectivity again.

5)     Reboot your PC; Some times USB COM ports may get stuck in the lower layers of your PCsOperating System. In this case, there is no way out other than rebooting your PC. When your PC up and running again, verify USB connectivity again.

6)     Reboot your WorldPro. Although it is extremely rare, the USB may be get stuck on the WorldPro’s part as well. In this case a restart of the WorldPro will resolve the problem.

7)     Reinstall the USB drivers on your WorldPro. In very rare cases, the USB drivers may have got corrupted in your PCs OS. If this is the case, a reinstallation of the drivers will resolve the problem.

Please also refer of the application note “NeraWorldPro: Connecting to PC via USB”, which contains a

troubleshooting section which is expected to be expanded in future revisions. ( Link

ftp://ftp.nera.no/mesbbs/Manuals/Nera WorldPro/Applications Guides/WorldPro_Conn_to_PC_USB.pdf ).

refer to the application note “NeraWorldPro: Setting up a DUN”, which you will find at download.nera.no or directly from ftp://ftp.nera.no/mesbbs/Manuals/NeraWorldPro/ApplicationsGuides/WorldPro_DUN.pdf

In Hyper terminal setup, you must specify one of the COM ports assigned to the WorldPro. (Refer to separate FAQ for how to determine which 2 COM ports are used by theWorldPro. Note: Do NOT select “Nera Dualport1” or Nera Dualport2”) You may use either one , the higher COM port (here COM4) or the lower COM port, but be aware that ;

-         if you connect to the lower COM port, you will block Launchpad (or any other application) to do control command communication with WorldPro.

-         if you connect to the higher COM port, you will block Launchpad (or any other application) to do establish data sessions with WorldPro.

To avoid confusion and potential COM port conflicts, the safest recommendation is to exit Launchpad and not run any data connection while you have your hyperterminal session active.

There is a huge amount of AT commands supported in the WorldPro. Some of them are 3GPP specified, some are BGAN specific and some are specific to WorldPro product. The control communication between WorldPro and Launchpad is based on using a subset of these AT commands, but there is nothing preventing you from entering the same AT commands manually.

A prerequisite is of course having an application capable of sending AT commands over a serial port connection running, let us assume HyperTerminal for simplicity.  

If you type “at*” or “at=/h” in HyperTerminal window, the WorldPro will output a list of available commands, and give a short indication on what the command does.

By typing “at<command>=/h” (e.g. “at_isig=/h”) you will get the detailed syntax for the specified command and how it is used in the Nera WorldPro.

Hint: Most AT commands and responses sent to and from the WorldPro are logged in the terminal sys trace. This is useful if you want to analyse a particular command sequence between Launchpad and WorldPro.

You must open the battery compartment with a flat-headed screwdriver (or coin) and you will find both the SIM card and battery in there. The battery needs to be removed before the SIM card can be inserted or taken out. This is explained in detail in the “Installing SIM card and battery” in the “Operations” section in the User manual. URL Link:   ftp://ftp.nera.no/mesbbs/Manuals/NeraWorldPro/

For convenience, a picture from the user manual has been included below: 

08-06-2006 - Partners and end-users are being advised of a quick and easy way to increase the speed of BGAN's standard IP data traffic in the "send" direction.

The throughput speed of BGAN traffic in the "send" direction (i.e. data sent from the terminal) will be enhanced if the window size on the receiving PC or server is correctly set.

And Inmarsat has prepared a small software file, available for download here, which automatically configures the client computer or server.

The window size on an IP connection effectively sets the number of packets ¿in flight¿ between origin and destination, at any given time.

Setting an optimum window size is particularly relevant for channel Partners undertaking customer demonstrations, and for end-users

users who frequently access the same servers with applications such as FTP (e.g. media customers, or corporate customers accessing intranet sites).

The optimum window size for BGAN is 128k (default setting on many systems is 64k).

Disclaimer: Modifying the computer registry may cause problems that may require you to reinstall the operating system. We cannot guarantee that problems resulting from modifications to the registry can be solved. Use the information provided at your own risk. Inmarsat will not be liable for any issues or problems that may arise in using this software.

To set the window size for systems running Windows XP or Windows 2003, follow the instructions below:

How to use automatic registry key entry to manage a client computer's or server's TCP parameters:

1. Inmarsat supplies two .reg files that will automatically configure the client computer or server to use the recommended TCP parameters. Choose the appropriate file to match your operating system.

2. The two files are:

• WinNT.reg (for use with Windows NT)
• WinXP_Win2k_Win2ksvr_and_Win2k3svr.reg (for use with Windows XP, 2000 Professional, 2000 Server and 2003)

3. Save the relevant .zip to your desktop and uncompress.

4. Double click the .reg file to change parameters. When the following screen appears click "yes" to continue:

5. When the following screen appears click "OK" to finish.

6. Re-boot your PC for the changes to take effect.

Note: Windows NT does not support windows scaling and therefore only supports a 64k window size. Hence running Windows NT over BGAN will give a lower performance than other operating systems.

How to configure TCP parameters manually

Use the following settings when configuring the TCP parameters. Please ensure you re-boot after the settings have been entered.

Registry Settings
System Key: [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters]

Value Name: TcpWindowSize
Data Type: REG_DWORD (DWORD Value)
Value: HEX: 1FFFF or Decimal: 131071

Value Name: Tcp1323Opts
Data Type: REG_DWORD (DWORD Value)
Value: HEX: 1 or Decimal: 1

08-06-2006 - Partners and end-users are being advised of a quick and easy way to increase the speed of BGAN's standard IP data traffic in the "send" direction.

The throughput speed of BGAN traffic in the "send" direction (i.e. data sent from the terminal) will be enhanced if the window size on the receiving PC or server is correctly set.

And Inmarsat has prepared a small software file, available for download here, which automatically configures the client computer or server.

The window size on an IP connection effectively sets the number of packets ¿in flight¿ between origin and destination, at any given time.

Setting an optimum window size is particularly relevant for channel Partners undertaking customer demonstrations, and for end-users

users who frequently access the same servers with applications such as FTP (e.g. media customers, or corporate customers accessing intranet sites).

The optimum window size for BGAN is 128k (default setting on many systems is 64k).

Disclaimer: Modifying the computer registry may cause problems that may require you to reinstall the operating system. We cannot guarantee that problems resulting from modifications to the registry can be solved. Use the information provided at your own risk. Inmarsat will not be liable for any issues or problems that may arise in using this software.

To set the window size for systems running Windows XP or Windows 2003, follow the instructions below:

How to use automatic registry key entry to manage a client computer's or server's TCP parameters:

1. Inmarsat supplies two .reg files that will automatically configure the client computer or server to use the recommended TCP parameters. Choose the appropriate file to match your operating system.

2. The two files are:

• WinNT.reg (for use with Windows NT)
• WinXP_Win2k_Win2ksvr_and_Win2k3svr.reg (for use with Windows XP, 2000 Professional, 2000 Server and 2003)

3. Save the relevant .zip to your desktop and uncompress.

4. Double click the .reg file to change parameters. When the following screen appears click "yes" to continue:

Additional comments to the discussion dBm and dBHz. The term log means logarithm with base 10. The acronym dB stands for deciBel. By Bel means the logarithm of a quantity. By deciBel means 10 times Bel. dBm is a logarithmic expression for power measured in milliwatt. Example: P=1 Watt is 1000 mW, or  P=10*log(1000) dBm=30 dBm.

dBHz is a logaritmic expression for bandwidth. Example: If a communication system has a bandwidth of B=3.5 MHz (like UMTS) then this is 10*log(B)=10*log(3500000)=65.44 dBHz

A conversion between dBHz and dBm is not meaningful and I am not able to answer the question of conversion between dBHz and dBm

White Gaussian noise is often expressed as noise spectral densitydensity in watt/Hz. For example termal noise has a spectral density of N0=k*T W/Hz where k is the Bolzmanns constant k=1.38*10^-23 Ws/degK, and T is the temperature in deg. Kelvin. This could be expressed in a logaritmic scale in dBm/Hz. Thus at room temperature N0=1.38*10^-23 * 300 W/Hz or -174 dBm/Hz. If for instance the the bandwidth is 3.5 MHz, the noise level N0*B measured in dBm is -174dBm +65.44 dBHz=-108.5 dBm . In the latter example dBHz is used to find the nois power in a given bandwidth when the noise density is known.

• Press [Menu] [4] [9]
• You will receive a message  " Handset reset will set all values to Factory setings and deletes last calls
• Press [Yes] Handset will appear to freeze, but will eventually shut down. 

DO NOT REMOVE THE HANDSET FROM THE SATELLITE PHONE TERMINAL.

You may need to then power cycle the satellite phone terminal.

Next, if you plan on using the terminal for incoming calls, you may want to reset the Mobile Subscriber Number (MSN) to match the terminal you are using.

• Press [Menu] [4] [8]
• If you have nothing listed press [options]
• If you have something listed, scroll to the one you want to edit then press [options]
• Scroll to either Edit number or Add number. Press [Select]
• For HNS Standard Voice for Number enter 1
• For Label enter something you will remember.
• Press [Save]