BGAN XL Radio Module Integrators manual Confidential RMIntegratorsManualCover.
BGAN XL Radio Module Integrators Manual Document number: 99-137719-D Release date: 9 December 2019
Disclaimer Any responsibility or liability for loss or damage in connection with the use of this product and the accompanying documentation is disclaimed by Thrane & Thrane A/S. The information in this manual is provided for information purposes only, is subject to change without notice and may contain errors or inaccuracies. Manuals issued by Thrane & Thrane A/S are periodically revised and updated. Anyone relying on this information should acquire the most current version e.g. from www.cobham.
Record of Revisions Rev. Description Release Date Initials A Original document 14 August 2014 UFO B The following sections have been added: 6.4.13, 7.5.14, 7.6.7, 10.2.1.2 15 January 2015 UFO 28 June 2016 UFO 9 December 2019 UFO The following sections have been edited: 5.6.5, 6.2.4, 6.4.3, 6.4.5, 6.4.6, 6.4.7, 6.5.1, 6.6.8, 6.7.5, 6.7.6, 6.8.3, 6.9.1, 6.10.4, 7.5.7, 7.7.1, 7.7.1.2.5, 8.5.4.2, 8.5.5, 10.1, 10.2.1.3, 10.2.2.1, 10.3.3, 10.4.1, 11.3.4, 11.5, 11.13, 12, 14.2, 14.3.15, 14.3.
Table of contents Chapter 1 About this manual 1.1 Purpose ............................................................................................. 1-1 1.2 Chapter overview ............................................................................... 1-1 1.3 Manual variants (FOR INTERNAL USE) ............................................... 1-2 1.4 Recommended terminology (FOR INTERNAL USE) .............................. 1-3 1.5 Intended readers ...............................................
Table of contents 3.8 TT-3752A Integrators Kit ..................................................................3-10 3.8.1 What’s included .............................................................................3-10 3.9 Approvals and certifications .............................................................3-11 3.9.1 Shortest way to a type approval ......................................................3-11 3.10 Ordering information ...................................................................
Table of contents Chapter 6 5.6 5.6.1 5.6.2 5.6.3 5.6.4 5.6.5 5.6.6 Electrical characteristics ..................................................................5-14 Power supply interface ...................................................................5-14 Digital interfaces ............................................................................5-14 Rx1 coaxial interface ...................................................................... 5-16 Rx2 coaxial IF interface .........................
Table of contents 6.4 System .............................................................................................6-12 6.4.1 BGAN XL Radio Module status .......................................................6-12 6.4.2 Software versions ..........................................................................6-13 6.4.3 BGAN XL Radio Module temperature .............................................6-15 6.4.4 Software updated ..........................................................................
Table of contents 6.6 Functionality ...................................................................................6-28 6.6.1 Radio silence ................................................................................6-28 6.6.2 Satellite selection ..........................................................................6-28 6.6.3 Doppler correction ........................................................................6-29 6.6.4 Fast signal-to-noise reports ........................................
Table of contents 6.8 Control ........................................................................................... 6-46 6.8.1 BGAN Class ................................................................................... 6-46 6.8.2 Product Type ................................................................................. 6-47 6.8.3 BGAN IMEI Number ...................................................................... 6-47 6.8.4 BGAN capabilities .................................................
Table of contents 7.5 Circuit switched services ..................................................................7-6 7.5.1 Voice and CS data calls ...................................................................7-6 7.5.2 SIP registering and authentication ..................................................7-6 7.5.3 BGAN call type signalling ................................................................ 7-7 7.5.4 BGAN call priority signalling ...........................................................
Table of contents 7.9 TSI/PCM interface ........................................................................... 7-42 7.9.1 Configuring the TSI/PCM interface for normal operation ............... 7-42 7.9.2 Data formats ................................................................................. 7-43 7.9.3 Configuring the TSI/PCM interface for test mode operation ........... 7-43 Chapter 8 Control interface 8.1 Terminology ..........................................................................
Table of contents 9.2 9.2.1 9.2.2 9.2.3 9.2.4 9.2.5 9.2.6 9.2.7 9.2.8 Chapter 10 RF control interface ..........................................................................9-12 Tx control signal (B2B_Tx_Ctrl) .......................................................9-12 Rx control signal (B2B_Rx_Ctrl) ......................................................9-13 Tx synchronization signal (B2B_Tx_Sync) ........................................9-13 Tx acknowledge signal (B2B_Tx_Ack) .........................
Table of contents 11.2 11.2.1 11.2.2 11.2.3 11.2.4 11.2.5 Software update ...............................................................................11-3 Introduction ....................................................................................11-3 Update procedure ...........................................................................11-3 Platform update procedure (FOR INTERNAL USE) ............................11-4 Software fallback / recovery ..............................................
Table of contents 11.11 BGAN reception .............................................................................. 11-30 11.11.1 Integrator’s interface .................................................................... 11-30 11.11.2 Python .......................................................................................... 11-31 11.12 Spectrum analyzer ......................................................................... 11-32 11.12.1 Basic operation .........................................
Table of contents 12.6 Services .......................................................................................... 12-11 12.6.1 Spectrum analyzer (spectrum measurement) ................................ 12-11 12.6.2 Spectrum analyzer (spurious search) ............................................12-12 12.6.3 Spectrum analyzer (phase noise measurement) ............................12-13 12.6.4 Changing satellite table ................................................................12-15 12.6.
14.3 Physical layer ..................................................................................14-7 14.3.1 MTR 6 Receiver Tuning Range ....................................................... 14-8 14.3.2 MTR 7 QPSK frame acquisition ...................................................... 14-8 14.3.3 MTR 8 QPSK packet error rate ........................................................14-9 14.3.4 MTR 9 QAM Frame Acquisition ..................................................... 14-10 14.3.
-xviii Confidential - For internal use 99-137719-D
1111 About this manual 1.1 1 Purpose This document is the Integrators Manual for the TT-3750 BGAN XL Radio Module from Cobham SATCOM. The manual describes the general principles for integrating the BGAN XL Radio Module (RM) in a product to provide access to the Inmarsat BGAN network. The manual is also intended as a reference manual for looking up details regarding protocols, parameters, commands, troubleshooting etc. This manual covers software version 1.07 or higher. 1.
Manual variants (FOR INTERNAL USE) Chapter 10, Test & diagnostics, provides information about available tests and monitoring capabilities. Chapter 11, Terminal support, describes the available functions to support integration, operation and troubleshooting of a complete terminal with a BGAN XL Radio Module. Chapter 12, Use cases, presents use cases which can provide inspiration when integrating the BGAN XL Radio Module into a product. Chapter 13, Applications, shows some applications.
1111 1.4 Recommended terminology (FOR INTERNAL USE) The purpose of the following writing guidelines is to ensure consistency in the naming of the different terms through out the entire manual. Term to use Other terms used for the same thing Terminal A terminal may in other documents be called UE (User equipment) or UT (User Terminal). Board processor Control processor or master processor Application processor Data processor Reference clock Master oscillator, reference oscillator or ref.
Typography (FOR INTERNAL USE) 1.6 Typography (FOR INTERNAL USE) In this manual, typography is used as indicated below: Bold is used for the following purposes: To emphasize words or parameter names. Example: Example: “The sys.status.mode parameter reflects ...Do not touch the antenna”. Italic is used to emphasize the paragraph title in cross-references. Example: “For further information, see Connecting Cables on page...”.
1111 1.7 Precautions 1.7.1 Warnings, Cautions and Notes About this manual Precautions Text marked with “Warning”, “Caution”, “Note” or “Important” show the following type of data: • Warning: A Warning is an operation or maintenance procedure that, if not obeyed, can cause injury or death, or jeopardize the safety. • Caution: A Caution is an operation or maintenance procedure that, if not obeyed, can cause damage to the equipment. • Note: A Note gives information to help the reader.
Precautions 1-6 Confidential - For internal use 99-137719-D
2222 Chapter 2 Introduction to BGAN 2 Introduction to BGAN This chapter has the following sections: 2.1 About the BGAN network .................................................................. 2-2 2.1.1 IAI-2 Layering ................................................................................. 2-3 2.1.2 Physical layer ................................................................................. 2-4 2.2 99-137719-D User terminal classes ........................................................
About the BGAN network 2.1 About the BGAN network The BGAN system was developed to provide 3GPP (3rd Generation Partnership Project) services to portable mobile terminals via the Inmarsat-4 (I-4) satellites, offering up to 858 kbps to the highest capability mobile terminals. BGAN delivers 'always-on' Internet Protocol (IP) services, telephony and ISDN.
2222 About the BGAN network Traffic is currently routed via two BGAN Satellite Access Stations (SASs) - one at Burum in the Netherlands and the one in Paumalu in Hawaii. Each SAS maintains a separate Radio Network Controller (RNC) for access to each satellite, and Core Network (CN) switching elements. The RNC manages the radio traffic to and from the satellite, whereas the CN provides the terrestrial telecommunications infrastructure and switching.
About the BGAN network 2.1.
2222 About the BGAN network 2.1.2.1 Bearer type identification 1DPLQJ &RQYHQWLRQ 'LUHFWLRQ %XUVW GXUDWLRQ 7\SH 6\PEROUDWH 0RGXODWLRQ )(& EORFNV SHU IUDPH 6\QWD[ 'HVFULSWLRQ ) 5 )5 )RUZDUG FRQWLQXRXV WUDQVPLVVLRQ 5HWXUQ EXUVW WUDQVPLVVLRQ )RUZDUG 5HWXUQ FRQWLQXRXV WUDQVPLVVLRQ PV EXUVW RQO\ UHWXUQ GLUHFWLRQ PV EXUVW RQO\ UHWXUQ GLUHFWLRQ PV IUDPH EXUVW IRUZDUG DQG UHWXUQ GLUHFWLRQ 7 7\SH 6\PERO UDWH VSHFLILHG LQ V\PEROV SHU VHFRQG )RU
User terminal classes 2.2 User terminal classes The BGAN system supports a number of different terminal classes in order to serve differing communication needs and thus enable a variety of terminals available to the end-user. The various terminal classes are grouped in families having similar specification targeted for a given market segment. Table 3-4 on page 3-7 shows an overview of the different classes and how they are mapped into groups.
3333 Chapter 3 This chapter has the following sections: 3.1 Key features ..................................................................................... 3-2 3.2 Functional description ...................................................................... 3-2 3.3 Interfaces ......................................................................................... 3-4 3.4 Mechanical outline ........................................................................... 3-4 3.
Key features 3.1 Key features • Modem compatible L-band radio. • Flexible design based on software-defined radio principles. • Compact form factor and low weight for portable and tracking devices. • Low power consumption and power-saving mode for battery-powered operation. • Single input supply and power-cycle resilient on all interfaces • Easy to type-approve with all currently defined Inmarsat BGAN and BGAN-XL services including LDR/HDR and BGAN classes. 3.
33 Functional description 3.2.1 Integration options The architecture of the BGAN XL Radio Module has been designed with flexibility in mind to enable easy integration into all different kind of terminal architectures. Apart from the various user interfaces defining a given terminal the integrator will only have to implement an antenna system (incl. HPA/LNA) and a SIM card interface.
Interfaces 3.3 Interfaces The BGAN XL Radio Module provides a number of interfaces for integration into a terminal. The various interfaces are listed below with a short description of the functionality: Name Description Data Interfaces Data IF Used for payload data, management, event detection, software upload etc. TSI IF Used for ISDN data (optional). Control Interfaces Control IF Used for configuration and control of the BGAN XL Radio Module.
3333 Product overview Environmental Specifications Figure 3-3: Mechanical outline 3.5 Environmental Specifications The BGAN XL Radio Module is designed and tested for use in harsh environments found in e.g. maritime and aeronautical segments. The following sections state the extreme values which the BGAN XL Radio Module meets with regards to temperature, humidity, shock and vibration. 3.5.
Power consumption 3.5.2 Vibration and shock The BGAN XL Radio Module is designed and tested to the specifications listed in the following table using the on-board reference clock on the BGAN XL Radio Module. Property Value Vibrationa 5 to 20 Hz 0.02 g2/Hz Vibrationa 20 to 150 Hz -3 dB/octave Vehicle/Vessel Motions: Shock (Survival) 20 g Vehicle/Vessel Motions: Induced acceleration 0.5 g Table 3-3: Technical data for vibration and shock a. Random vibration of 1.
3333 Protocols 3.7 Protocols Three of the interfaces illustrated in Figure 3-2 on page 3-3 support higher layer protocols: • BGAN air interface • BGAN XL Radio Module control interface • BGAN XL Radio Module data interface 3.7.1 No higher layer protocols are implemented on the TSI (Time Slot Interchange) interface which implements a standard PCM bus protocol.
Protocols Market segment BGAN class Terminal type Maximum data bit rates (published by Inmarsat) [Download/Upload] Maritime Class 8 High Gain Antenna 432 kbps / 432 kbps Class 9 Intermediate Gain Antenna 284 kbps / 284 kbps Class 14a Low Gain Antenna 150 kbps / 150 kbps Class 10 High Gain Antenna 492 kbps / 492 kbps Class 11 Intermediate Gain Antenna 464 kbps / 448 kbps Vehiculara Table 3-4: Supported BGAN classes (Continued) a. Available in future firmware release. 3.7.
3333 Protocol layer Reference Comments Network Layer IPv4 [IETF RFC791] The IP network layer provides access to local services and to the CS service, which is accessed via SIP. Circuit Switched Services SIP [IETF RFC3261] RTP [IETF RFC3550] The CS services of the BGAN network are provided by the RM via the SIP and RTP protocols. SIP is used for call control (session control in SIP terminology) and RTP is used for user plane data.
TT-3752A Integrators Kit 3.8 TT-3752A Integrators Kit An Integrators Kit is available to assist smooth integration of the BGAN XL Radio Module in a new terminal. The kit is based on a carrier board specifically designed to hold a BGAN XL Radio Module and provide the basic functionality required to operate the BGAN XL Radio Module.
3333 Approvals and certifications 3.9 Approvals and certifications The BGAN-XL Radio Module is designed for application in CE and FCC approved products and fully complies with the RoHS and WEEE directives of the European Union. Product overview Figure 3-6: Prepared for CE and FCC approval Figure 3-7: RoHS and WEEE compliant 3.9.1 Shortest way to a type approval Mandatory test requirements (MTRs) for a BGAN UT are written and provided to the terminal manufacturers by Inmarsat.
Ordering information 3-12 Confidential - For internal use 99-137719-D
4444 Chapter 4 System description This chapter has the following sections: Introduction to the BGAN XL Radio Module ....................................... 4-2 4.2 BGAN XL Radio Module interface overview ...................................... 4-3 4.3 Integrating the BGAN XL Radio Module ............................................ 4-4 4.4 High-level terminal system design .................................................... 4-8 System description 4.
Introduction to the BGAN XL Radio Module 4.1 Introduction to the BGAN XL Radio Module The BGAN XL Radio Module is designed to be a versatile building block for easy integration of BGAN functionality into a variety of different terminal architectures targeting all applicable market segments. Basically the module presents a data interface towards the user side and an L-band RF input/output towards the BGAN system.
4444 BGAN XL Radio Module interface overview 4.2 BGAN XL Radio Module interface overview The BGAN XL Radio Module provides a number of interfaces for integration into a terminal. The various interfaces are listed below with a short description of the functionality: Description Type Data Interfaces Data IF Used for payload data, management, event detection, software upload etc. USB 2.0 (OTG) TSI IF Used for ISDN data (optional).
Integrating the BGAN XL Radio Module 4.3 Integrating the BGAN XL Radio Module The BGAN XL Radio Module is not designed for stand-alone operation. It requires to be controlled by an external processing unit. In all aspects the external processing unit will be the master. This applies during startup, configuration and operation of the BGAN XL Radio Module.
4444 Integrating the BGAN XL Radio Module 4.3.2 Configuration system The configuration system is a vital part of the BGAN XL Radio Module and is used to exchange configuration settings and system information between the surrounding platform and the BGAN XL Radio Module. The integrator can access the configuration system via both the control interface and the data interface as illustrated in the figure below.
Integrating the BGAN XL Radio Module this state will be referred to as SDM sleep further on. If activated by the integrator in the configuration system the BGAN XL Radio Module will enter this power management state when it is in operating iai2 mode and is registered to the BGAN network if no PS or CS connection is established. For further details on SDM sleep operation see section 11.5 on page 11-12.
4444 Integrating the BGAN XL Radio Module • Mechanical pointed antennas without power detector. • Phased array antennas. • Omnidirectional antennas. It is the responsibility of the integrator of the BGAN XL Radio Module to design an antenna pointing algorithm which matches the antenna and can accommodate requirements such as reliable pointing, fast channel acquisition and meaningful GUI information. See section 8.5.5 on page 8-36 for more information. 4.3.
High-level terminal system design 4.4 High-level terminal system design As mentioned earlier the BGAN XL Radio Module requires to be controlled by an external processing unit designed and implemented by the integrator. Also, all product specific software functionality related to a given terminal must be implemented outside the BGAN XL Radio Module.
4444 High-level terminal system design • Software upload of ADU • ARINC interface (aero only) 4.4.2 Application Processor The Application Processor is meant to be the flexible part of the architecture differentiating the various terminals towards the user. The BGAN XL Radio Module does not put up any constraints on the implementation of the Application Processor, hence its size and type can be chosen freely with respect to the user/network applications implemented for a given terminal.
High-level terminal system design • System error logging and reporting. • PPPoE connections to the BGAN XL Radio Module. • SIP client. 4.4.3 High-level System Architecture Block Diagram The following figure shows a conceptual high-level block diagram of the BGAN XL Radio Module-based system architecture. For more block diagrams of various terminal types see chapter 13.
5555 Chapter 5 Product specifications This chapter has the following sections: General precautions ......................................................................... 5-2 5.2 Physical specifications ...................................................................... 5-2 5.3 Mounting considerations .................................................................. 5-4 5.4 Environmental specifications ............................................................ 5-6 5.
General precautions 5.1 General precautions CAUTION! The BGAN XL Radio Module is designed for mounting on a PCB, implementing appropriate external interfaces designed to meet overall regulatory specifications of the unit. The electrical interfaces of the RM are thus not designed to be directly accessible for the user of the end product. It is therefore important to handle the RM with care as it does not have ESD protection on all I/Os.
55 Physical specifications Product specifications The following figure shows the outline drawings and dimensions of the BGAN XL Radio Module. Figure 5-2: Outline drawing with dimensions in mm Tolerances are in accordance with DS/ISO 2768-1 F.
Mounting considerations 5.3 Mounting considerations The BGAN XL Radio Module shall be mounted to the carrier board and/or terminal mechanics using five non-threaded through-holes; for details see Figure 5-3 below. Optionally two threaded blind-holes in the bottom can be used as well if required by the application. Figure 5-3: Mounting possibilities Mount the BGAN XL Radio Module on a carrier board implementing appropriate external interfaces designed to meet overall regulatory specifications of the unit.
5555 Mounting considerations 5.3.1 Recommended footprint Product specifications The following figure shows the recommended footprint for mounting of the BGAN XL Radio Module. Building height underneath the BGAN XL Radio Module is specified in Figure 5-2 on page 3. Figure 5-4: Recommended RM footprint 5.3.2 Cooling requirements It is essential that the maximum allowed case temperature for the BGAN XL Radio Module is not exceeded. The maximum case temperature is shown in Table 5-2 on page 5-6.
Environmental specifications 5.4 Environmental specifications The following sections state the extreme values which the BGAN XL Radio Module meets with regards to temperature, humidity, shock and vibration. 5.4.1 Temperature and humidity The BGAN XL Radio Module is designed and tested to meet the temperature and humidity specifications listed in the table below.
5555 Environmental specifications 5.4.1.1 Temperature capabilities (FOR INTERNAL USE) The BGAN XL Radio Module is designed for case temperatures from -40°C to +75°C but has been qualified from -55°C to +85°C with external reference clock. This means that operation outside -40°C to +75°C cannot be guaranteed by design and should thus be verified by the integrator at terminal level. WARNING! Operation below -40°C requires an external master clock as the internal master oscillator will not work here. 5.4.
Environmental specifications • Higher red graph shows survival operation. Figure 5-5: Cobham vibration spectrum 5.4.2.3 Vibration capabilities (FOR INTERNAL USE) The BGAN XL Radio Module is designed for and tested with a vibration spectrum with twice the amplitudes stated in sections 5.4.2 and 5.4.2.2. The BGAN XL Radio Module is designed for and tested with a vibration spectrum with three times the amplitudes stated in section 5.4.2.1 The following figure shows the direction of worst case G-sensitivity.
5555 Connector specifications 5.5 Connector specifications This section specifies the various connectors on the BGAN XL Radio Module with respect to type, placement and pin allocation. 5.5.1 Connector overview Figure 5-7 below shows the connectors of the BGAN XL Radio Module. RM bottom view Ref CLK B2B Connector 1B 1A 30B 30A Tx Rx2 (IF) 60 Product specifications Rx1 90 Figure 5-7: Connectors of the BGAN XL Radio Module 5.5.
Connector specifications Connector classification Optional RF connectors Reference Description Rx2 One Tyco spring-loaded B2B coaxial connector Tyco part number: 619135-1 Ref CLK One Tyco spring-loaded B2B coaxial connector Tyco part number: 619135-1 Connector for Debug Connector BGAN XL Radio Module development only (for internal use) One 40-pin Samtec LSHM series B2B connector Samtec part number: LSHM-120-04.0-x-DV-A-N Table 5-4: Connector types and specifications (Continued) 5.5.
5555 Connector specifications Signal Description I/O Electrical Pin # Rx_Ctrl Rx Chain Active Out 3.3V TTL 22B Tx_Ctrl Tx Chain Active Out 3.3V TTL 20B Power Supply Interface 5V_In 4x DC input power PWR 5.2 VDC 1A, 1B, 2A, 2B GND 17x GND PWR GND 3A, 3B, 6A, 6B, 9A, 12A, 14A, 16B, 17A, 18B, 20A, 23A, 23B, 26A, 28B, 30A, 30B Data Interface USB_DP Serial Data + I/O USB2.0 4A USB_DM Serial Data - I/O USB2.0 5A USB_ID Host/device Identification In USB2.0 4B PWR USB2.
Connector specifications 5.5.4 Debug connector (FOR INTERNAL USE) The pin numbers listed in the table below are defined by the figure below. Electrical characteristics for the signal types are listed in Table 5-10 on page 5-15. RM bottom view Debug Connector Ref CLK 20A 20B 1A 1B Tx B2B Connector 1B 1A 30B 30A Rx2 (IF) 60 Rx1 90 Figure 5-8: Pin allocation of debug connector Signal Description I/O Electrical Pin # Debug_[1..20] FPGA Debug I/O 1.8V LVCMOS [20B..
5555 Connector specifications 5.5.5 RF coaxial connectors The product using the BGAN XL Radio Module can connect to the RM via four RF connection points using spring loaded coaxial connectors. Signal Description I/O Specification RF Interface Rx1 Receiver input In Refer to 5.6.3 on page 5-16 Rx2 Secondary IF receiver input In Refer to 5.6.4 on page 5-17 Tx Transmitter output Out Refer to 5.6.5 on page 5-18 Ref CLK Reference Clock input/output In/Out Refer to 5.6.
Electrical characteristics 5.6 Electrical characteristics This section specifies the electrical characteristics of the various interfaces to the BGAN XL Radio Module. 5.6.1 Power supply interface Electrical characteristics for the supply pins in Table 5-5 are shown in the table below. Refer to section 4.3.3 on page 4-5 for a definition of the various use cases for which the power consumption is given. Electrical characteristics Min. Typical Max. Unit 4.95 5.2 5.
5555 Electrical characteristics Electrical characteristics Min. IO Max. Unit ±4 mA 3.3V Open Drain VOH Ext. VDD Ext. VDD V VOL -0.3 0.4 V 4 mA IO USB 2.0 See USB 2.0 [16] and USB 2.0 OTG [17] for electrical specifications except for the following deviation: It is only permitted to use VBUS for signalling purposes, i.e. do not use VBUS to power external equipment.
Electrical characteristics 5.6.3 Rx1 coaxial interface The electrical specifications related to the Rx1 coaxial interface are shown in the table below. Property Value Unit Receiver Specifications (Rx1) Tuning Range 1518.0 – 1559.0 MHz Channel step size 1.25 kHz Input Signal Level -100 to -60 dBm Noise Figure (see Figure 5-9 on page 17, normal mode).
5555 The figure below shows the typical noise figure versus temperature. Figure 5-9: NF versus temperature (typical) Note The BGAN XL Radio Module meets the requirements to Packet Error Rate (PER) stated in the SDM (see [18]) with a 0.2 dB degradation of C/N0 compared to the C/N0 points stated in the SDM in order to allow for implementation losses like e.g. HPA noise, in-band frequency ripple etc. 5.6.
Electrical characteristics 5.6.5 Tx coaxial interface The electrical specifications related to the Tx1 coaxial interface are shown in the table below. Property Value Unit 1626.5 – 1660.5 MHz Transmitter specifications (Tx) Tuning rangea 1668.0 – 1675.0 Channel step size 1.25 kHz -10 to -40 dBm Output signal level, absolute precision +/-1 dB Output signal level, relative precision +/-0.
5555 Electrical characteristics 5.6.6 Reference Clock I/O Property Value Unit 57.
Interface descriptions 5.7 Interface descriptions The following sections describes the physical-layer behaviour for the various interfaces on the BGAN XL Radio Module. 5.7.1 Control interface The control interface is used for low-level control of the BGAN XL Radio Module. It consists of a UART with hardware flow control, an outgoing and an incoming interrupt, and a reset signal.
5555 Interface descriptions 5.7.2 Digital reference clock output The 57.85 MHz reference clock of the BGAN XL Radio Module is output at 3.3V TTL levels and can be used for external synchronization. See section 6.5.4 for information on how to enable the reference clock output. Note The digital reference clock output will by default be disabled when the BGAN XL Radio Module enters sleep mode in order to save power.
Interface descriptions 5.7.3.2 RF Control SPI Timing Timing of the SPI bus is shown in the figure below. The specifications are valid at the interface of the BGAN XL Radio Module (i.e. at the B2B connector). /( ƚĐLJĐůĞ ƚůĞ &/. ƚŵŽƐŝͺƐĞƚƵƉ ƚŵŽƐŝͺŚŽůĚ 026, ƚŵŝƐŽͺƐĞƚƵƉ ƚŵŝƐŽͺŚŽůĚ 0,62 Figure 5-11: SPI timing diagram. The timing parameters shown in the table below are specified with respect to the 50% edge of CLK/LE and the 10/90% edges of the data signals (MOSI/MISO). Characteristic Min. Typ. Max.
5555 Interface descriptions 5.7.5 Data interface The data interface of the BGAN XL Radio Module is electrically compliant to the USB 2.0 OTG standard. Signal Description USB_DP Serial Data + USB_DM Serial Data - USB_ID Host/device Identification USB_VBUS USB Bus Voltage Table 5-20: USB interface signal description Product specifications The VBUS power output has a current-limiting function and is tolerant of short term short circuit.
Interface descriptions 5-24 Confidential - For internal use 99-137719-D
6666 Chapter 6 Startup & configuration This chapter has the following sections: 6.1 Start-up ............................................................................................ 6-2 6.2 General use ...................................................................................... 6-7 6.3 Parameter overview .........................................................................6-11 6.4 System .............................................................................................
Start-up 6.1 Start-up This section describes in detail the various modes of operation supported by the BGAN XL Radio Module and describes the procedure for bringing the BGAN XL Radio Module into operational mode. 6.1.1 Overview As introduced in section 4.3.1 on page 4-4 the BGAN XL Radio Module always operates within a predefined set of modes, each supporting its own well-defined set of functions.
6666 the start-up sequence are designated with t1..t4 in Figure 6-1 above and are described in detail in section 6.2.4 on page 6-8. 6.1.1.1 BGAN XL Radio Module actions (FOR INTERNAL USE) The following figure is only for internal use and summarises the actions done by the BGAN XL Radio Module during the start up procedure. .
Start-up 6.1.2.1 Step #1 - Starting (booting) Each time the BGAN XL Radio Module is started (see 5.7.1 on page 5-20) it will enter the initial mode. In this mode the software modules and service functionality for the physical layer will be loaded. The state of the BGAN XL Radio Module is reflected by the sys.status.mode parameter which is located in the configuration system (see section 6.4.1 on page 6-12 for more information). 6.1.2.
6666 6.1.2.4 Step #4 - Service mode When the BGAN XL Radio Module is ready to receive service related instructions on the control interface an acknowledge message is returned (see section 8.5.2.9.1 on page 8-26): MSG_ACK Now the BGAN XL Radio Module has entered service mode and the integrator has access to a special designed service API which among other things offers the capability to: • Execute additional connectivity tests (see step #5a in section 6.1.2.5).
Start-up 6.1.2.7 Step #6 -Configuration (dynamic) Finally the integrator must provide more configurations to specify dynamic information (such as Tx power level(s), reference clock, ATC activation etc.) that is needed by the BGAN modem to operate properly depending on the specific configuration. After dynamic configuration has been completed the BGAN XL Radio Module can be put into operating mode, requesting load of a specific waveform, by sending the following message (see section 8.5.2.4.
6666 6.2 General use 6.2.1 Introduction to the configuration system The BGAN XL Radio Module has a configuration system which is used for sharing configuration information. All public parameters in the database are accessible from all tasks in both the protocol processor and the modem and for the integrator as well using the control and data interface. The configuration system supports 3 different storage types: 1. Volatile memory (RAM), 2. Non-volatile (Flash file-system) 3.
General use 6.2.4 Syntax description for parameters All parameters described in this section are presented in a table similar to the one illustrated below. Parameter name External access Type / Domain Values Comment .param.name [r|w|r/w] [t1|t2|t3|t4] [§1|§2|§3|§4|§5] [int|string|bytearray] [min..
6666 6.2.4.1 Parameter restrictions The parameters in the configuration system are classified into the following five restriction groups: • §1 Mandatory parameters which must be specified by the integrator. These parameters are only read once during activation and cannot be modified later in the startup process. If these parameters are not specified when activated the BGAN XL Radio Module will enter its ERROR state and cannot proceed to normal operation before the errors are corrected.
General use Restrictions The RM will not operate The RM will operate (error mode) (but in error mode) The RM will operate §4 x §5 x Table 6-2: Severity of unconfigured parameters. (Continued) Note To ease configuration and assist the integrator during initial troubleshooting the BGAN XL Radio Module generates syslog entries (severity level 5) about missing configuration parameters which are mandatory (§1, §2 and §3). Examples: Sys log entries (severity level 5): 0: Err. 'protocols.bgan.
6666 Parameter overview 6.3 Parameter overview 6.3.1 Configuration tree (Top-level) Root level Description sys System parameters like serial number, software version etc. post POST test definitions and results protocols Protocol specific parameters. Subdivision based on the software module structure, e.g. protocols.bgan, protocols.sip and protocols.umts services Service specific parameters, e.g. spectrum analyzer and transmission time plan configuration parameters.
System 6.4 System The sections below describe the parameters that are related to the overall system. sys errorlog mainboard powermanagement terminal bus pcm status unit sw cpu dsp flash ver release active archive Figure 6-4: Parameter hierarchy for system parameters. 6.4.1 BGAN XL Radio Module status The status of the BGAN XL Radio Module is reflected by the sys.status.mode parameter listed in the table below. Furthermore the current state of each sub-unit is exposed in the parameters sys.status.unit.
6666 System Parameter name sys.status External access Type / Domain .unit.1.name r string / ram n.a. Name: modem .unit.cnt r int / ram n.a. Number of units who report status .uptime r int / ram n.a. BGAN XL Radio Module uptime specified in seconds Comment Table 6-4: Configuration parameter: BGAN XL Radio Module status (Continued) 6.4.1.1 BGAN-XL User Terminal Test Setup (BUTTS) status (FOR INTERNAL USE) The BGAN XL Radio Module BUTTS functionality can be enabled or disabled.
System 6.4.2.2 Versions of active software units (FOR INTERNAL USE) The BGAN XL Radio Module discloses the following information about the active units: Parameter name External sys.sw. access Type / Domain Values [min;max] .cpu.version r string / ram n.a. Version number of the active cpu build .cpu.buildid r string / ram n.a. Build ID of the active cpu build (format “-”) .cpu.builddate r string / ram n.a. Build date of the active cpu build .dsp.
6666 System 6.4.3 BGAN XL Radio Module temperature The internal temperature of the BGAN XL Radio Module is stored in the configuration system. The parameter is updated every time the temperature changes 1°C. Parameter name External Type / Values Comment sys access Domain [min;max] .mainboard.tem r perature int / ram [-55.. +125] Temperature in degrees Celsius (°C). Values correspond to the working area of the sensor. .overheat_protec r/w t4 §4 int / ram [0..1] tion.
System 6.4.5 Power management / SDM sleep The BGAN XL Radio Module SDM sleep mode can be enabled and disabled. For more information on SDM sleep see 11.5 on page 11-12 and 11.5.2 on page 11-13 for limitations in using SDM sleep and suspend mode together. Parameter name External Type / Values Comment sys.powermanagement access Domain [min;max] .enabled r/w t4 §4 int / ram [0..1] 0: Disable (default) 1: Enable Table 6-11: Enable / disable BGAN XL Radio Module power management 6.4.
6666 System Note that the parameters .rxslots, .txslots, .rxdatdly, .txdatdly, must be configured before the parameter .enabled is activated as they are only read once. 6.4.7 Terminal serial number (FOR INTERNAL USE) The integrator must, upon startup, write the serial number of the terminal into the configuration parameter sys.terminal.serial Parameter name sys External Type / Values Comment access Domain [min;max] .terminal.serial r/w t1 §1 string/ ram n.a. Max.
System 6.4.9 MAC address The MAC address which is pre-programmed during manufacturing of the BGAN XL Radio Module can be read in the following parameter. Parameter name External Type / Values Comment sys access Domain [min;max] .macaddr r byte array/ factory n.a. A 6 character ASCII string. Table 6-15: Radio Module MAC address 6.4.10 BOM versions The BOM versions which are pre-programmed during manufacturing of the BGAN XL Radio Module can be read in the following parameters.
6666 6.4.12 Platform type (FOR INTERNAL USE) This parameter holds the value corresponding to the product id described on the internal wiki (http://wiki.ttnet/bin/view/Products/CoreSwPlatformProductId) Parameter name External Type / sys access Domain Values Comment [min;max] .platform_type [0x0d, 0x15] r byte array / factory Product ID for BGAN XL Radio Module (TT3750A) is 0x0d. Product ID for the BGAN XL Radio Module for Aero (TT3750A-AER) is 0x15. Table 6-18: Value for platform_type parameter 6.4.
System Parameter name sys.sw.http External Type / access Domain .update_port r/w Values Comment [min;max] int / ram n.a Writing to this parameter will change the port used for software update (overriding the default 8080 port). Subsequent updates to the parameter (without restarting the BGAN XL Radio Module) are ignored. .notification.keepalive r/w t4 §4 int / ram [60..3600] Default: 120 seconds, This setting will override .keepalive.
6666 Interface 6.5 Interface The sections below describe the parameters that are related to the USIM, RF and RF control interfaces. platform usim protocols bgan interface rf delay rx2 clk rx rfctrl tx ctrl burst rx ctrl receiver Startup & configuration atc Figure 6-5: Parameter hierarchy for interface parameters. 6.5.1 USIM The following parameters are related to the BGAN XL Radio Module USIM configuration. Parameter name External Type / platform.usim access Domain Values [min;max] .status [0..
Interface Parameter name External Type / platform.usim access Domain Values [min;max] Comment .airtime_provider r string / ram n.a. EFDP_NAME .iccid r string / ram n.a. EFICCID .imsi r string / ram n.a. EFIMSI .pin.status r string / ram Absent, Invalid, Needed, Blocked, USIM PIN status PUK Blocked, SIM Lock Blocked, Valid .m2m r int / ram [0..
6666 6.5.2 Tx and rx delay The table below shows the parameters related to the RF signal timing. The following delay parameters are at disposal for the external platform to achieve correct burst timing (see 9.1.1). Parameter name protocols.bgan.interface External Type / Values Comment access Domain [min;max] .rf.delay.tx.external r/w t1 §1 int / ram [0..4095] Specified in 57.85 MHz clock cycles. .rf.delay.rx1.external r/w t1 §2 int / ram [0..4095] Specified in 57.85 MHz clock cycles. .rf.delay.rx2.
Interface 6.5.4 Reference clock The source of the reference clock must be specified via the .clk.rx.ref_clk_sel parameter specified in the table below. Values [min;m Comment ax] Parameter name protocols.bgan.interface External access Type / Domain .clk.rx.ref_clk_sel r/w t1 §5 int / flash [0..1] 0=internal (factory default) 1=external .clk.rx.ref_clk_coax_out r/w t1 §4 int / ram [0..1] 0=off (default) 1=on Only allowed to be enabled when ref_clk_sel is set to internal .clk.rx.
6666 Interface Parameter name protocols.bgan.interface External Type / Values Comment access Domain [min;max] .rfctrl.tx.ctrl.spi_en r/w t1 §4 int / ram [0..1] SPI Tx messages 0=disable(default) 1=enable r/w t1 §4 int / ram [0..1] Tx control (B2B_Tx_Ctrl) 0=disable(default) 1=enable .rfctrl.tx.ctrl.tx_ack_en r/w t1 §3 int / ram [0..1] Tx acknowledgement (B2B_Tx_Ack) 0=disable 1=enable(default) .rfctrl.rx.pin.rx_ctrl_en r/w t1 §4 int / ram [0..
Interface Parameter name protocols.bgan.interface External Type / access Domain Values [min;max] .rfctrl.tx.burst.init r/w t1 §3 int / ram [0..10413] Specified in 57.85 MHz clock cycles.(10413) .rfctrl.tx.burst.start r/w t1 §3 int / ram [0..10413] Specified in 57.85 MHz clock cycles.(2582) .rfctrl.tx.burst.down r/w t1 §3 int / ram [28925..57850] Specified in 57.85 MHz clock cycles.(28925) Comment Table 6-26: Transmitter timing (Continued) 6.5.5.
6666 Interface 6.5.6 Intermodulation test frequencies (aeronautical only) These values contain the channel numbers to be used for testing the performance of the receive band intermodulation. The channel numbers are defined as described in the SDM v2c4 [18] where the most significant bit determines the offset and the remaining 15 bits are used to calculate the frequency. These values are received from the RAN and require the BGAN XL Radio Module to operate in IAI2 mode, but they are reset on reboot.
Functionality 6.6 Functionality The sections below describe the parameters that are related to different functionality offered by the BGAN XL Radio Module. protocols bplt bgan functionality ambe cs radio_silence clk drift csfifo Figure 6-6: Parameter hierarchy for functionality parameters 6.6.1 Radio silence During normal run time operation the BGAN XL Radio Module offers the possibility to achieve radio silence. When it operates in radio silence mode all burst transmissions are discarded.
6666 Parameter name protocols.bgan.functionality External access Type / Domain Values [min;max] .satellite_selection r/w t4 §4 string / flash n.a. Comment APAC, EMEA, AMER, MEAS, AUTO (Default is AUTO) Table 6-31: Satellite selection If set to e.g. APAC the satellite search algorithm will only search for the APAC (AsiaPacific) satellite. Note If antenna pointing (see 8.5.5 on page 8-36) is running the integrator must first stop it, before changing .satellite_selection.
Functionality 6.6.4 Fast signal-to-noise reports During normal run time operation the BGAN XL Radio Module can deliver fast signalto-noise reports at an interval of 10 ms. This service is controlled via the parameter .fast_snr_reporting and is per default deactivated. Parameter name protocols.bgan.functionality External Type / Values Comment access Domain [min;max] .fast_snr_reporting r/w t4 §4 int / ram [0..1] 0=disable (default), 1=enable Table 6-33: Special service: fast signal-to-noise reports 6.
6666 Functionality The .ambe.cni parameter specifies if the internal comfort noise handling shall be enabled. Changes to that parameter takes effect for new CS calls. Parameter name protocols.bgan.functionality External access Type / Domain .ambe.enable r/w t3 §4 int / ram Values [min;max] Comment [0..1] 0=disable, 1=enable (default) .ambe.cni r/w t4 §4 int / ram [0..1] 0=disable (default), 1=enable Table 6-35: Configuration parameters for AMBE encoding. 6.6.7 Call waiting The .cs.
Functionality 6.6.9 BPLT parameters The configuration parameters below are only used when the BPLT waveform is operational on the BGAN XL Radio Module. Some scripts require special handling which can be controlled through the values below. Usually there is no need to use values beside 0 or 1. Any other values specifies the amount of FEC blocks to average CNo calculations over. A maximum of 1700 is defined. Parameter name protocols.bplt External access Type / Domain Values [min;max] .
6666 Functionality Three configuration parameters are used to detach/attach and control the suspend mode. They are shown in the table below. Parameter name External Type / access Domain protocols.umts.cs.attach w t4 §4 Values Comment [min;max] int / ram [0..1] 0=CS detach 1=CS attach protocols.umts.ps.attach w t4 §4 int / ram [0..1] 0=PS detach 1=PS attach sys.suspend.enable w t4 §4 int /ram [0..1] 0=leave Suspend Mode 1=enter Suspend Mode Table 6-40: Suspend mode configuration. 6.6.
Functionality The disadvantage of using the faster bit rate ramp up is a higher power consumption, especially if the HDR connection is primarily used in the forward direction. This must be taken into consideration by integrators when making a battery-powered product. Parameter name protocols.bgan.functionality External access Type / Domain Values [min;max] .hdr.rate_ramp_up r/w t4 §4 int / ram [0..1] Comment 0=disable (default), 1=enable. Table 6-42: HDR bit rate ramp up 6.6.
6666 Changes in the satellite table is persistent, but can be overwritten by data received from the BGAN RAN. Parameter name External protocols.bgan.functionality. access satellite_table Type / Domain Values [min;max] Comment .change.locked r/w t3 §4 int / ram [0..1] Lock mechanism .change.satellite_id r/w t3 §4 int / ram [0..15] Satellite ID .change.position r/w t3 §4 int / ram [-1800..1800] Longitude of satellite in 1/10th degrees. Positive values for East. .change.channel.
Functionality Parameter name protocols.net.static_route External access Type / Domain Values [min;max] ..netmask r/w t4 §4 string / ram Netmask ..gateway r/w t4 §4 string / ram Gateway IP address. Comment Table 6-45: Static route . is in the range [0..
6666 6.7 Status The following subsections describe the parameters that are entirely controlled by the BGAN XL Radio Module and are seen as 'read-only' from external integrators. protocols umts bgan sat status interface rf gain rx functionality clk pcm Figure 6-7: Parameter hierarchy for status parameters. 6.7.1 Receiver AGC level The receiver AGC level is stored in non-volatile flash memory.
Status The .clk.mode parameter shows the condition (invalid, coarse or fine) of the clock offset estimate. The clock offset estimate is only safe to use when the condition is fine. Coarse condition indicates that the estimation is ongoing but has not been settled yet. Parameter name External Type / protocols.bgan.functionality access Domain Values [min;max] Comment .clk.aging_frequency r t4 int / ram [-10000..10000] Frequency offset (Hz) related to a clock offset compared to 1538.5 MHz .clk.
6666 Status The fields described below contains information regarding the satellite table used by the IAI-2 stack. Parameter name External Type / protocols.bgan.status.sat access Domain ellite_table Values [min;max] .count [0..8] r t4 int / ram Comment Number of entries in the satellite table. Only valid if waveform has been loaded. Will have the value 0 otherwise. 0: Satellite table is not valid (waveform has not been loaded) ..satelite_id r t4 int / ram [0..
Status 6.7.4 IAI-2 status information Various information regarding the current status of the forward bearer currently in use by the IAI-2 stack. Parameter name External Type / protocols.bgan.status access Domain .state r Values [min;max] string / ram n.a. Comment Describes the overall state of the IAI-2 stack. N/A (initial) Satellite search Receive system information Registering Registered Deregistered .channel r int / ram [0..
6666 6.7.5 Satellite coverage The status field below can be used to detect if the terminal leaves the coverage area of the spot beams on the satellite. Parameter name External Type / protocols.bgan.status access Domain Values [min;max] .out_of_coverage [0..1] r int / ram Comment 0: (Initial value). Either the spot beam coverage is undetermined (e.g. if protocols.bgan.status.state is ‘Satellite search’) or the terminal is within a spot beam.
Status 6.7.7 Connection status The configuration parameters below contain information about the current state of the PLMN search and the status of the packet switched and circuit switched connections. Parameter name External Type / protocols.umts access Domain Values Comment [min;max] .cs.status r string / ram n.a. n/a (initial) Idle Attaching Attached Attached rejected Detaching Blocked .ps.status r string / ram n.a. n/a (initial) Idle Attaching Attached Attached rejected Detaching Blocked .
6666 The RM has an array of 11 entries with PDP context information. ‘’ is 1..11. Parameter name protocols.umts.ps External Type / Values Comment access Domain [min;max] .pdp..cid r int / ram [0..255] CID (PDP Context Identifier) for the PDP context entry x. CID is used to define PDP context in AT+CGDCONT (3GPP TS27.007 [15]). If 0 there is no valid entry. .pdp..pppoe_session r int / ram [0..2^16-1] PPPoE session id for the PPPoE session that created the PDP context. Only valid if .pdp.
Status .pdp..rab should normally not be used. It is intended for aeronautical terminals with SwiftBroadband Oceanic Safety Service implemented. In this case it can be used to detect if radio resources on the PDP context are lost, and if so re-establish the PDP context. 6.7.8 Navigational information (aeronautical) (FOR INTERNAL USE) The BGAN XL Radio Module supports an aeronautical receive path equalizer as defined in the SDM.
6666 Status segregation hardware / data arbitrator in front of the RM to ensure that data from Aircraft Information Services Domain does not flood the RM. Parameter name protocols.bgan.status External Type / access Domain Values Comment [min;max] .queue_size.high_prio r int / ram [0..2^31-1] Bytes in queue in the priority pool (specified as described above). .queue_size.low_prio r int / ram [0..2^31-1] Bytes in queue in the normal data pool. Table 6-56: Data segregation (IAI pool status). 6.7.
Control 6.8 Control The following subsections describe the parameters that can be modified by the integrator to control behaviour of the BGAN XL Radio Module. The integrator must configure the control parameters before activation. sys imei protocols bgan bcn-bct interface rf gain tx functionality nav skyscan pwr waveform Figure 6-8: Parameter hierarchy for control parameters. 6.8.1 BGAN Class The integrator of the BGAN XL Radio Module must configure the BGAN class. For supported classes see 3.7.
6666 6.8.2 Product Type The integrator must configure the product type. This setting is used by the USIM driver of the BGAN XL Radio Module to enforce the Market Sector Restrictions described in the SDM v5c1 [18]. Parameter name sys External Type / access Domain Values Comment [min;max] .product_type r/w t1 §3 int / ram [0..5] 0: Land / Land-mobile. 1: Maritime 2: Aeronautical 3: M2M 4: Fleet One 5: S-Band Table 6-59: Product type Important This setting must be written before platform.usim.
Control Note The IMEI checksum (check_digit) is calculated as: 1. Starting from the right, double every 2nd digit (e.g. 5 -> 10). 2. Add the digits (e.g. 10 -> 1+0) and check if the sum is divisible by 10. 3. If not, the IMEI can be calculated by choosing the check digit that would give a sum divisible by 10. Example: IMEI: 35145120840121 1: (5x2, 4x2, 1x2, 0x2, 4x2, 1x2, 1x2) = (10, 8, 2, 0, 8, 2, 2) 2: (1+0+8+2+0+8+2+2) + (3+1+5+2+8+0+2) = 44 3: Luhn Digit = 6 IMEI: 351451-20-840121-6 6.8.
6666 choose between full support (in both the forward and return direction) or half support in either the forward or the return direction. The .ldr.enable parameter must be activated if the integrator wants a terminal that supports the use of low data rate (LDR) capabilities. If none of the capabilities are activated the RM will operate as a standard BGAN modem A new product will normally have to support extended L-band to get Type Approval from Inmarsat.
Control 6.8.5 Receiver input power (FOR INTERNAL USE) 6.8.5.1 Gain variation The BGAN XL Radio Module has a mechanism that can compensate for gain variations over the frequency range of the received signal. The RM uses pairs of frequencies and gain corrections together with an interpolation algorithm to compensate for variations. Only linear interpolation is supported. The RM offers up to 15 pairs to cover the entire transmitter frequency range as indicated in the table below.
6666 Control Parameter name protocols.bgan.interface External access Type / Values Domain [min;max] Comment .rf.gain.tx.nominal_power r/w t1 §2 int / ram [-1000..4000] Nominal transmitter output power in dBm x100 Table 6-64: Nominal transmitter output level Note The integrator must ensure that the combination of the nominal power and gain variations in any situation is within: – 40dBm P nom + G comp – 10dBm 6.8.6.
Control Note Note that external gain variations over temperature must be handled by replacing the compensation parameters (or the nominal power) according to the drift of the temperature. 6.8.7 ATC activation The parameter .atc.activation is used (by the integrator) to signal if an interferer is present or not. How this information is used by the RM is described in section 9.1.5.1 on page 9-9. The parameter is per default deactivated which indicates that no ATC interferers are present.
6666 6.8.9 Sky-scan (Check waveform) The following parameter specifies the time-out values for the waveform validation (see section 8.5.5.11 on page 8-48). This time-out value is only used during sky-scan operation. Parameter name protocols.bgan.functionality External Type / access Domain Values Comment [min;max] .skyscan.check.waveform.timeout r/w t3 §4 int / ram [0..2] 0=360ms (default), 1=440ms, 2=520ms Table 6-69: Sky-scan (Check waveform) time-out. 6.8.
Control The .sband parameter will internally in the DSP add 353.4 MHz and 651.86 MHz to the Tx and Rx target frequencies instructed by CPU to shift operation from L-band to Sband. Parameter name protocols.bgan.interface.rf External Type / access Domain Values Comment [min;max] .freq_offset.rx.external r/w t3 §3 int / ram [0..2^32-1] Rx frequency conversion in kHz external to RM. default: 0 .freq_offset.tx.external r/w t3 §3 int /ram [0..2^32-1] Tx frequency conversion in kHz external to RM.
6666 Control controlled with below configuration parameters. Further description of the Synchronous Serial Link is not provided in this document. Parameter name protocols.bgan.interface External Type / access Domain Values Comment [min;max] .serial_link.control r/w t1 §3 int / ram [0..1] 0: Disable (default) 1: Enable .serial_link.data r/w t1 §3 int / ram [0..
Connection types 6.9 Connection types The following subsections describe the parameters that can be modified by the integrator to control the behaviour of the different connection types. protocols sip pcm Figure 6-9: Parameter hierarchy for connection parameters. 6.9.1 Circuit switched parameters The following parameters are defined for the circuit switched services described in section 7.5 on page 7-6: Parameter name External protocols.sip access Type / Domain Values [min;max] Comment .auth.
6666 Connection types Parameter name External protocols.sip access Type / Domain Values [min;max] Comment .pcm.slotrx r/w t3 §4 int / flash [0..31] TSI/PCM Rx slot to use. .pcm.slottx r/w t3 §4 int / flash [0..31] TSI/PCM Tx slot to use. .pcm.calltypes r/w t3 §4 int / flash [0..3] Bit field specifying for which call types the TSI/PCM bus shall be used. Bit 0: ISDN UDI/RDI (default), Bit 1: 3.
Support 6.10 Support The sections below describe the parameters that are related to the different services offered by the BGAN XL Radio Module. services sa timeplan syslog cm data Figure 6-10: Parameter hierarchy for support parameters. 6.10.1 Configuration of the spectrum analyzer The tables below show the parameters related to configuration of the internal spectrum analyzer which is available in service mode (see section 11.12 on page 11-32). Parameter name services.
6666 Parameter name services.intif External Type / access Domain Values [min;max] .sa.spur_bw r/w t2 §4 int / ram [1..999999] .sa.rx_auto_gain_adjus r/w t2 §4 int / ram [-10000 .. t 3200] Comment Spurious search bandwidth in Hz Receiver gain in 0.01 dB Table 6-76: Spectrum analyzer configuration (Continued) • Spectrum analyzer bandwidth (span): 4 different bandwidths are available in the range from 2 kHz to 2 MHz.
Support Parameter name services.intif External Type / access Domain Values [min;max] .timeplan.bt_[0..15] r/w t4 §4 string / ram n.a. R5T1X, R5T1XD, R5T2X, R5T2XD, R5T45X, R5T45XD, R20T1X, R20T1XD, R20T2X, R20T2XD, R20T45X, R20T45XD, R5T2Q, R5T2QD, R5T45Q, R5T45QD, R20T05Q, R20T05QD, R20T1Q, R20T1QD, R20T2Q, R20T2QD, R20T45Q, R20T45QD, R80T05Q, R80T1Q, FR80T25X4, FR80T25X16, FR80T25X32, FR80T25X64, FR80T5X4, FR80T5X16, FR80T5X32, FR80T5X64,NA .timeplan.cr_[0..15] r/w t4 §4 string / ram n.a.
6666 6.10.3 Syslog The syslog client can be configured using the following settings: Parameter name External Type / services access Domain Values Comment [min;max] .syslog.relay_ip r/w t4 §4 string / flash 16 chars IP of the Syslog collector (Application Processor) Default: “192.168.1.2” .syslog.severity r/w t4 §4 int / flash [0..7] Severity level 0: Emergency 1: Alert 2: Critical 3: Error 4: Warning 5: Notice 6: Informational (default) 7: Debug Table 6-78: Syslog configuration settings 6.10.
Support Parameter name services.syslog.cm External Type / Values Comment access Domain [min;max] .data.evm r/w t4 §4 int / ram [0..1] Enable/disable of squared Error Vector Magnitude data logging of the forward bearer. 0: Disable (default) 1: Enable .value.evm r The last reported Error Vector Magnitude value in parts-permillion. .rate.evm r/w t4 §4 int / ram 50 Reporting rate specified in 80 ms units. Default: 50 (4 sec.) .data.clk_drift r/w t4 §4 int / ram [0..
6666 Parameter name services.syslog.cm External Type / Values Comment access Domain [min;max] .rate.multipath_delay r .data.demod r/w t4 §4 int/ram [0..1] int/ram 50 Reporting rate specified in 80 ms units. Default: 50 (4 sec.) Enable/disable of demodulator related data logging. 0: Disable (default) 1: Enable .value.demod_state r int/ram [0..4] The last reported state of the demodulator (0: idle, 1: tune, 2: search, 3: track, 4: blocking). .value.demod_reacq r int/ram [0..
Support Parameter name services.syslog.cm External Type / Values Comment access Domain [min;max] .data.per r/w t4 §4 int/ram [0..1] Enable/disable of packet error rate data logging. 0: Disable (default) 1: Enable .value.per r int/ram [0.. 1000000] The last reported packet error rate of the turbo decoder (in 10E-06 units). Packet error rate is measured on all packets on the received bearer possibly including packets for other terminals. .rate.per r/w t4 §4 int/ram [0..
6666 Support Parameter name services.syslog.cm External Type / Values Comment access Domain [min;max] .value.fec_on_dec_err r int/ram [-1..12] The last reported FEC number (within frame) on error. Default -1 (no decoding error). .value.seq_on_dec_err r int/ram [-1..4095] The last reported sequence number on error. Default -1 (no decoding error).
Factory (FOR INTERNAL USE) 6.11 Factory (FOR INTERNAL USE) The sections below describe the factory parameters that are specified during BGAN XL Radio Module manufacturing and related to the modem. These calibration parameters are all stored in the configuration system and are organized in the hierarchy shown in the figure below. sys bgan cal tx gain freq temp delay att rx clk delay gain ctrl freq Figure 6-11: Parameter hierarchy for factory parameters. 6.11.
6666 6.11.1.2 Tx gain versus temperature The following shows the parameters used for Tx gain calibration versus temperature. Parameter name sys.bgan.cal External Type / access Domain Values Comment [min;max] .tx.gain.temp.locked r/w t1 §1 int / ram [0..1] .tx.gain.temp.thres[1..10] r/w t1 §1 int / factory [-100..150] Temp [°C] threshold .tx.gain.temp.pwr_correction[1..10] r/w t1 §1 int / factory [-500..500] Power corr. 0.01 dB .tx.gain.temp.pwr_pairs [0..
Factory (FOR INTERNAL USE) 6.11.1.4 Tx step attenuator The following shows the parameters used for calibration of the Tx step attenuator. Parameter name sys.bgan.cal External access Type / Domain Values [min;max] Comment .tx.att.locked r/w t1 §1 .tx.att.step_[00..31] r/w t1 §1 int / ram [0..1] Lock mechanism int / factory [100..-3500] Att. setting in dB x100 Table 6-83: Tx attenuator step calibrations To get a successful result the following must apply: step 31 step 30 step 0 6.11.
6666 Parameter name sys.bgan.cal External Values Type / Domain access [min;max] .rx.gain.ctrl.vga2_ref r/w t1 §1 int / flash [0..127] Temporary, used for manufacturing .rx.gain.ctrl.atc_ref r/w t1 §1 int / flash [0..1] Temporary, used for manufacturing .rx.gain.ctrl.freq_ref r/w t1 §1 int / flash [1500000000.. 1700000000] Temporary, used for manufacturing [Hz] .rx.gain.ctrl.rx1_ref r/w t1 §1 int / flash [0..10000] Temporary, used for manufacturing .rx.gain.ctrl.
Factory (FOR INTERNAL USE) 6.11.3 Reference oscillator calibration The following parameters are used for the calibration of the reference oscillator: Parameter name External Type / sys.bgan.cal access Domain Values [min;max] Comment .rx.clk.dac_setting r/w t1 §1 int / factory [0..4095] Clk DAC setting .rx.clk.dac_offset r/w t1 §1 int /cached [-4095..4095] Clk offset from factory setting (i.e. aging offset). .rx.clk.dac_slope r/w t1 §1 int / factory [-10000..
6666 Factory (FOR INTERNAL USE) 6.11.4 RF signal delay The following parameters hold the BGAN XL Radio Module’s internal RF delays which are used in combination with the external reported delays to achieve correct Tx timing as explained in 9.1.1 on page 9-2. Parameter name sys.bgan.cal External Type / access Domain Values Comment [min;max] .tx.delay.tx.internal r/w t1 §1 int / factory [0..4095] Specified in 57.85 MHz clock cycles .rx.delay.rx1.internal r/w t1 §1 int / factory [0..
Settings (FOR INTERNAL USE) 6.12 Settings (FOR INTERNAL USE) 6.12.1 Flash parameters related to modem operation The sections below describe the flash parameters that are specified during BGAN XL Radio Module development and related to modem operation. These settings are all stored in the configuration system and are organized in the hierarchy shown in the figure below.
6666 Settings (FOR INTERNAL USE) description of each of these parameters can be found in the internal design documentation. Parameter name protocols.bgan.set.tx External Type / access Domain .burst_ctrl.seq_len_ch0 r Values [min;max] Comment int / ram [28925..433875] Sequence length of channel 0 ('Setup 1') (default=404950) int / ram [28925..173550] Sequence length of channel 1 ('Setup 2').(default=173550) .burst_ctrl.seq_len_ch2 r int / ram [28925..173550] Sequence length of channel 2 ('Reset').
Settings (FOR INTERNAL USE) 6.12.1.2 Intermediate receiver frequency The table below shows the parameter for the intermediate frequency in the receiver chain. Parameter name protocols.bgan.set.rx External Type / access Domain .if.freq r Values [min;max] int / flash [100000000.. 200000000] Comment [Hz]. (default=130400000) Table 6-89: Configuration parameter: intermediate Rx frequency in the receiver chain 6.12.1.
6666 Settings (FOR INTERNAL USE) 6.12.1.5 Modem state This parameter specifies the mode of operation for the modem and is solely used during debugging of the physical layer. Parameter name External protocols.bgan.set.modem access Type / Domain Values [min;max] Comment .mode int / ram [0..3] 0=normal (default) r/w t4 §4 1=manufacturing 2=debug 3=BPLT Table 6-92: Modem mode • Normal mode is default. • In manufacturing mode, alive surveillance is deactivated.
Settings (FOR INTERNAL USE) Parameter name protocols.bgan.set.rx.gain External Type / access Domain Values Comment [min;max] .backoff.f80t2.5x16 r/w t3 §4 int / flash [-8700..0] Backoff from full scale in 0.01 dB.(default=-2850) .backoff.f80t2.5x16m r/w t3 §4 int / flash [-8700..0] Backoff from full scale in 0.01 dB.(default=-2850) .backoff.f80t2.5x32 r/w t3 §4 int / flash [-8700..0] Backoff from full scale in 0.01 dB.(default=-2950) .backoff.f80t2.5x64 r/w t3 §4 int / flash [-8700..
6666 6.12.1.7 Reference clock The table below shows the parameters related to the clock offset estimation (see 6.7.2). The .mov_avg_nframe parameter indicates how many frames (80 ms) needed before a clock offset estimate is calculated. If the receiver is in tracking mode a value of 50 gives an update rate of 4 seconds. The .mov_avg_m parameter tells how many "nframe values" are used to estimate the clock offset. Parameter name protocols.bgan.set.
Settings (FOR INTERNAL USE) 6.12.1.9 FPGA debug mux The table below shows the parameters for setting of the platform specific signal routing used for internal debugging in the modem. Parameter name protocols.bgan.set External Type / access Domain Values [min;max] .fpga.debug_mux r/w t4 §4 int / ram [0..15] Comment 0=disable (default), 15=TDP, 14=Extended-POST, 13=BUTTS Table 6-96: Configuration parameter: FPGA debug mux 6.12.1.
6666 Parameter name protocols.bgan.set External access Type / Domain Values [min;max] .butts.ref_clk.cal_request r/w t4 §4 int / ram [0, 1] Comment 0=ready/finished 1=ongoing calibration .butts.ref_clk.cal_status r int / ram [0..2] 0=ready/finished 1=ongoing 2=timeout Table 6-97: Configuration parameter: BUTTS settings Note If .butts.ref_clk.cal_status returns the value timeout, it is usually a consequence of either a wrong setting of fpga.
Settings (FOR INTERNAL USE) 6.12.2 Parameters related to extended POST (FOR INTERNAL USE) 6.12.2.1 RF control interface The table below shows the parameters related to perform extended POST for the RF control interface. The SPI clock and SPI word length can be configured on the RF control interface. This feature is only available during extended POST. Parameter name External Type / protocols.bgan.set.extended_post access Domain .
7777 Chapter 7 Data interfaces 7 This chapter has the following sections: Protocol overview for the data interface ........................................... 7-2 7.2 Physical layer ................................................................................... 7-4 7.3 Network layer .................................................................................. 7-5 7.4 IP addressing scheme ....................................................................... 7-5 7.
Protocol overview for the data interface 7.1 Protocol overview for the data interface The data interface of the BGAN XL Radio Module provides access to a wide range of services. First and foremost it provides access to the services of the BGAN network both the Circuit Switched (CS) and Packet Switched (PS) services. Secondly, it provides access to a number of local services for management and test of the RM itself.
7777 Protocol overview for the data interface Protocol layer Reference Comments Packet Switched Services PPPoE [IETF RFC 2516] PPP [IETF RFC 1661] [Section 7.6] The PS services of the BGAN network are provided by the RM via the PPPoE protocol. Each PPPoE sessions maps directly to a PDP context in the PDCP protocol. Management Services HTTP [Section 7.7.1] Syslog [Section 7.7.2] AT-shell [Section 7.7.3] Telnet [Section 7.7.4] Data Tunnel [Section 7.7.
Physical layer 7.2 Physical layer The connection between the Application Processor and the BGAN XL Radio Module is done by using a USB 2.0 interface in device mode, so that the RM acts as a USB device, and the Application Processor acts as a USB host. The RM can run USB 2.0, and will do so if the Application Processor side also offers this, but will fall back to 1.1 if needed.
7777 7.3 Network layer An IPv4 network runs on top of the Ethernet network. This network is used for a number of things, among those: • Circuit Switched services such as SIP, RTP and PCM. • Telnet access to the RM debug shell. • Configuration system read/write access. 7.4 IP addressing scheme The IP addresses and netmask for the two-node network between the AP and the BGAN XL Radio Module are determined as follows: The network mask must be a 255.255.255.252 (a /30 network).
Circuit switched services 7.5 Circuit switched services This section describes the interfaces for accessing the Circuit Switched (CS) BGAN services including: • Voice calls (Speech and 3.1 kHz Audio) • CS data calls (ISDN UDI/RDI) • Supplementary Services (SS) • Short Message Service (SMS) The Session Initiating Protocol (SIP) is used for call control of voice and ISDN calls. User plane data (i.e. voice frames or ISDN data frames) are supported via the Real Time Protocol (RTP).
7777 Circuit switched services Registering is mandatory. If authentication is enabled all transactions with the SIP server will require HTTP Digest authentication as described in RFC 2617 [3] using the specified user name and password. User name, password and whether or not to use authentication may be configured via the configuration parameters presented in section 6.9.1. 7.5.3 BGAN call type signalling The BGAN network supports the following four call types: • Speech (AMBE+2) • 3.
Circuit switched services 7.5.4 BGAN call priority signalling The BGAN network supports the following call priorities: • Normal / no priority • 3GPP eMLPP priority 0-4,A,B1 • Emergency call If none of the header fields described below are included in the INVITE a normal/no priority call is established. If the BGAN XL Radio Module receives an INVITE having both header fields present, it will treat the call as a 3GPP eMLPP priority call. 7.5.4.
7777 7.5.4.2 Emergency calls For emergency calls (defined by emergency destination numbers such as 112 or 911 configured in the BGAN XL Radio Module and on the USIM) the header field Priority is used (RFC3261 [5]). To setup a mobile originated emergency call the following header field must be present: Priority: emergency Example: Emergency INVITE sip:112@radio-module.local SIP/2.0 … To: 112 Priority: emergency 7.5.
Circuit switched services 7.5.6.3 Calling Line Identification Restriction Calling Line Identification Restriction (CLIR) may be suppressed or invoked on a per call basis. This is signalled to the RM by using the header field Privacy defined in RFC 3323 [7].
7777 Circuit switched services DTMF For BGAN speech calls transcoded to PCM A-law or L16 the RM supports in-band DTMF detection and generation. 7.5.7.2 AMBE+2 RTP definitions AMBE+2 has not been assigned an official encoding name and static payload type by IANA so a proprietary name has been defined that may be used with dynamic payload type number assignment.
Circuit switched services The RX and Tx PCM slot numbers to use are determined by the configuration parameters protocols.sip.pcm.slotrx and protocols.sip.pcm.slottx (see section 6.9.1 on page 6-56). 7.5.10 ISDN data via RTP If configured to use RTP for ISDN RDI/UDI calls (protocols.sip.pcm.enabled set to 0) the RM will send and accept for these call types the SDP session parameters shown in the example below. Only payload CLEARMODE is supported for ISDN RDI/UDI calls.
7777 Circuit switched services 7.5.12 Short Message Service (SMS) AT command Description Reference [2] +CSMS Select Message Service Section 3.2.1 +CPMS Preferred Message Storage Section 3.2.2 +CMGF Message format Section 3.2.3 +CSCA Service Centre Address Section 3.3.1 +CSMP Set Text Mode Parameters Section 3.3.2 +CSDH Show Text Mode Parameters Only : 1 supported Section 3.3.3 +CSAS Save Settings Section 3.3.5 +CRES Restore Settings Section 3.3.
Circuit switched services 7.5.13 Supported SIP RFCs The BGAN XL Radio Module SIP implementation supports the functionality defined by the RFCs listed in Table 7-10 below. RFC Description 2617 HTTP Auth Basic and Digest 3261 Core SIP functionality 3262 Making 1xx responses reliable; defines the PRACK method 3264 An Offer-Answer model with SDP 3323 A Privacy Mechanism for SIP 3326 The Reason header field for SIP.
7777 Cause code Description 18 No user responding 19 User alerting, no answer 21 Call rejected 22 Number changed 25 Pre-emption 26 Core Network failure 27 Core Network failure 28 Invalid number 31 Normal, unspecified 34 Call Rejected, no channel/circuit 44 Call Rejected, requested channel/circuit not available 102 Network timeout (no answer) Table 7-11: List of circuit-switched cause codes (UMTS Call Control) (Continued) For other cause codes < 256 refer to ‘UMTS Specific cause val
Circuit switched services Cause code Description 0x00034107 Reject, no cell or Radio Network 0x00034108 Reject, authentication failure active conn.
7777 Cause code Description 0x0008641b Deregister, decryption error 0x0008641c Deregister, user specified position not permitted 0x0008641d Deregister, Radio Network initiated Deregistration 0x0008641f Deregister, tracked SAT below minimum 0x00086420 Deregister, Lease Group not available 0x00086421 Deregister, Lease Mode handover failed 0x00086422 Deregister, Radio Failure 0x00086423 Deregister, Unsupported UE subclass 0x00086424 Deregister, Elevation too low 0x00086425 Deregister, Pro
Circuit switched services Cause code Description 0x00034020 Service option rejected, not supported 0x00034022 Service option rejected, temporarily out of order 0x00034026 Network failure, call cannot be identified 0x00034030 Network failure, retry upon entry to new cell 0x0003405f Network error, detached 0x00034060 Network error, invalid mandatory info 0x00034061 Network error, message invalid 0x00034062 Network error, protocol state error 0x00034064 Network error, invalid conditional in
7777 Packet switched services 7.6 Packet switched services The following subsections introduces the packet switched services supported by the BGAN XL Radio Module and describes how they are controlled. 7.6.1 Brief introduction to PDP contexts and Traffic Flow Templates A PDP context is a data pipe towards the Internet through the BGAN network. PDP contexts come in two types; primary and secondary, and are grouped in families.
Packet switched services The first establishes a PDP context with cid (Connection ID) 2, then requests a Quality of Service for cid 2 with traffic class 3, which is a background connection. (This particular example is, in result, identical to the “XBB:BACKGROUND” service name string.) $SSOLFDWLRQ SURFHVVRU 5DGLR 0RGXOH 333R( 3ULPDU\ 3'3 &RQWH[W 6HFRQGDU\ 3'3 &RQWH[W V 333R( 3ULPDU\ 3'3 &RQWH[W 6HFRQGDU\ 3'3 &RQWH[W V 333R( 3ULPDU\ 3'3 &RQWH[W 6HFRQGDU\ 3'3 &RQWH[W V [ \
7777 Packet switched services 7.6.3.1 Service parameter for data segregation (aeronautical) (FOR INTERNAL USE) ARINC-781 requires that IP data from Aircraft Control Domain and Aircraft Information Services Domain is segregated. This is described in detail in 6.7.9 on page 6-44. The separation of the data pools can be achieved by appending a proprietary AT command to the PPPoE service command string.
Packet switched services 7.6.5 List of AT commands for manipulating PDP family QoS This subsection lists the subset of 3GPP AT commands used to manipulate QoS and other parameters for a given PDP context. • AT+CGDCONT - defines a PDP context. • AT+CGDSCONT - defines a secondary PDP context. • AT+CGEQREQ - requests a QoS for a given PDP context. • AT+CGEQMIN - requests a minimum QoS for a given PDP context. • AT+CGTFT - defines (TFTs) Traffic Flow Templates for given PDP context family.
7777 Packet switched services The figures for data rates exclude the data rate used for voice or ISDN. The maximum data rate depends on the current air link quality and current voice or ISDN connections (these will reduce the maximum data rate). 7.6.
Packet switched services Cause code Description 45 Syntactical errors in packet filter(s) 46 PDP context without TFT already activated Table 7-17: List of packet-switched cause codes (GPRS specific) (Continued) For other cause codes < 256 refer to ‘GPRS specific cause values for session management’ in 3GPP TS24.
7777 Cause code Description 0x00086300 Establish Reject, normal 0x00086301 Establish Reject, Radio Network failure 0x00086302 Establish Reject, congestion 0x00086303 Establish Reject, unsupported IAI version 0x00086304 Establish Reject, unsupported UE class 0x00086305 Establish Reject, USIM required 0x00086306 Establish Reject, physical channel failure 0x00086307 Establish Reject, access Class not allowed 0x00086308 Establish Reject, unspecified 0x00086309 Conn.
Packet switched services Cause code Description 0x00086321 Deregister, Lease Mode handover failed 0x00086322 Deregister, Radio Failure 0x00086323 Deregister, Unsupported UE subclass 0x00086324 Deregister, Elevation too low 0x00086325 Deregister, Protocol Failure 0x00086326 Deregister, Invalid UE capabilities Table 7-19: Cause codes received from RAN (SDM cause codes added with 0x00086300) (Continued) Cause code Description 0x00024002 Network failure IMSI unknown (HLR) 0x00024003 Network
7777 Packet switched services Cause code Description 0x00051004 Reject, missing pin 0x00051005 Reject, no selected PLMN 0x00051006 Reject, PLMN forbidden 0x00051007 Reject, PLMN/GPRS not allowed Data interfaces Table 7-21: Cause codes from the RM, also used for circuit-switched 99-137719-D Confidential - For internal use 7-27
Management services 7.7 Management services The following subsections describes the management services supported by the BGAN XL Radio Module. 7.7.1 HTTP interface This subsection contains all the services available via the HTTP protocol. The HTTP services are available using the HTTP 1.1 protocol (RFC 2616 [13]) to the IP address assigned in section 7.4 on page 7-5 at the port number defined in sys.sw.http.port (see 6.4.14 on page 6-19). 7.7.1.
7777 Management services If the BGAN XL Radio Module gets a reboot request (MSG_REBOOT, section 8.5.2.8.4 on page 8-25) it will close all HTTP connections and reject new connections. In both cases the RM will return HTTP response code 200 with an additional HTTP header: “X-Reboot: OpReboot\r\n”: HTTP/1.1 200 OK X-Reboot: OpReboot Content-Length: 0 7.7.1.3.1 Reading all parameters Reading all parameters is done by invoking the HTTP GET method for the URL config.xml.
Management services 7.7.1.3.2 Writing a set of parameters Writing a set parameters is done by invoking the HTTP PUT method for the URL config.xml. The request body is a XML document containing the parameters to write to the configuration store. Writing a set of parameters will be supported in future releases. Important 7.7.1.3.3 Reading a parameter Individual parameters are read by performing a HTTP GET for an URL that represents the parameter.
7777 Management services Note that the client side HTTP implementation may end the connection before the BGAN XL Radio Module sends back any data. Such a timeout should simply be handled by resending the request. A typical sequence when waiting for a long time then becomes: 1. Client sends notification request 2. Client timeout 3. Client re-sends notification request 4. Client timeout 5. Client re-sends notification request 6. BGAN XL Radio Module sends back a HTTP response 7.
Management services 7.7.1.3.6 Subscribing to notifications on multiple parameters The BGAN XL Radio Module provides an interface to subscribe for changes on a set of parameters which minimizes overhead and minimizes the use of open socket connections. The set of parameters, which is to be subscribed for changes, must be specified in an XML file. Example: PAGE 1897777 7.7.2 Syslog interface Figure 7-4: Notification sequence with multiple parameters The BGAN XL Radio Module supports a subset of the syslog protocol described in RFC 5424 [10] and RFC 5426 [11] and operates as a syslog originator whereas the application processor operates as a syslog collector or relay. As allowed in the RFC, the RM will use its IP address in the HOSTNAME field of the syslog protocol.
Management services Value Severity 3 Error: error conditions 4 Warning: warning conditions 5 Notice: normal but significant condition 6 Informational: informational messages 7 Debug: debug-level messages Table 7-26: Syslog entries — severity levels The services.syslog.relay_ip contains the IP of the syslog collector (application processor). By default only events with a severity level of 6 or lower will be transmitted to the application processor.
7777 All RM-specific user events use - as shown in the example - APP-NAME ‘RM’, facility ‘local0’ and SD-ID ‘3750@cobham’.
Management services Event id Information level Event Text Explanation 0x1800 Warning Registration for data failed The terminal has not yet been allowed to register for data services (Packet Switched). 0x2000 Informational Satellite signal weak The signal from the satellite is weak. 0x2900 Warning Network failed authentication The terminal does not accept the network as a valid BGAN network.
7777 Event id Information level Event Text Explanation 0x8029 IAI-2 Adaptation Layer: Silent deregistration, satellite connection temporarily lost The IAI-2 adaptation layer reports silent deregistration causing temporary loss of the satellite connection. Informational SubID = 0 means a "true" silent de-registration from the BCt layer, while sub id = 1 is used for a number of other cases, such as security command failure or integrity command failure.
Management services • Supplementary Services (TS 27.007 [1]) • SMS handling (TS 27.005, [2]) The AT shell is accessed using the telnet protocol (RFC 854, [15]) to the IP address setup in section 7.4 on page 7-5 at port number 5454 using USB EEM as connection to the BGAN XL Radio Module. Only a subset of AT commands listed in [1] and [2] is released for use on the BGAN XL Radio Module. All other AT commands present in the AT shell are for future use only. 7.7.
7777 7.7.5 Data tunnel The BGAN XL Radio Module provides four data tunnels providing communication links between the data interface and the control interface. The RM listens on UDP port 130 and TCP port 131 and accepts only one session at a time on each port. The data received on the respective ports is forwarded to the control interface.
Test-specific protocols 7.8 Test-specific protocols The following subsections provides information on the protocols supported by the BGAN XL Radio Module to enable test required for type approval. 7.8.1 BPLT The terminal communicates with the BGAN Physical Layer Tester (BPLT) by exchanging messages over TCP connections initiated by the BPLT. The BPLT issues messages to the terminal to request it to perform operations such as configuring its transmitter or receiver.
7777 7.8.2 BPT The BGAN Protocol Tester (BPT) provides a complete development and compliance environment for the Inmarsat Air Interface adaptation, bearer control and bearer connection layers for BGAN as well as 3GPP Non Access Stratum (NAS) and the ISDN sub-system.
TSI/PCM interface 7.9 TSI/PCM interface The TSI/PCM interface of the BGAN XL Radio Module may be used as data interface for ISDN RDI/UDI calls. If the integrator chooses to use the TSI/PCM interface he may in addition enable the reporting by the BGAN XL Radio Module of clock drift and buffer drift as described in section 11.4 on page 11-10. 7.9.
7777 TSI/PCM interface 7.9.2 Data formats The data format for ISDN data sent and received on the TSI/PCM interface is 8-bit PCM A-law. The drift information is distributed via a dedicated TSI slot as specified in section 6.6.5 on page 6-30. The drift information is constructed by a 3 byte frame and is distributed to the integrator periodically every 4th second if distribution of at least one of the drift parameters has been enabled as per section 6.6.5 on page 6-30. Byte 1 ID (7..4) Check sum (3..
TSI/PCM interface 7-44 Confidential - For internal use 99-137719-D
8888 Chapter 8 Control interface This chapter has the following sections: 8.1 Terminology ..................................................................................... 8-2 8.2 Physical layer ................................................................................... 8-2 8.3 8.3.1 8.3.2 8.3.3 8.3.4 Link layer ......................................................................................... 8-3 Format of the protocol data unit (PDU) ...........................................
Terminology 8.1 Terminology The control interface is the interface for controlling and configuring the BGAN XL Radio Module. The control interface implements a proprietary protocol for exchanging messages and data between a master and a slave. The BGAN XL Radio Module is the slave. The unit responsible for controlling and configuring the BGAN XL Radio Module is the master. The messages transferred between the master and the RM are defined as Service Data Units (SDUs).
8888 Link layer 8.3 Link layer The following subsections define the link layer applicable for the control interface. 8.3.1 Format of the protocol data unit (PDU) The control interface operates with a PDU format as illustrated below: 1 bit FS 1 byte 1 byte 7 bit Payload length 1 byte SOF PRIO Fragment.
Link layer }; 0x6c, 0x62, 0x48, 0x46, 0x54, 0x5a, 0xe0, 0xee, 0xfc, 0xf2, 0xd8, 0xd6, 0xc4, 0xca, 0x90, 0x9e, 0x8c, 0x82, 0xa8, 0xa6, 0xb4, 0xba, 0xfd, 0xf3, 0xd9, 0xd7, 0xc5, 0xcb, 0x71, 0x7f, 0x6d, 0x63, 0x49, 0x47, 0x55, 0x5b, 0x01, 0x0f, 0x1d, 0x13, 0x39, 0x37, 0x25, 0x2b, 0x8f, 0x81, 0xab, 0xa5, 0xb7, 0xb9, 0x03, 0x0d, 0x1f, 0x11, 0x3b, 0x35, 0x27, 0x29, 0x73, 0x7d, 0x6f, 0x61, 0x4b, 0x45, 0x57, 0x59, 0x1e, 0x10, 0x3a, 0x34, 0x26, 0x28, 0x92, 0x9c, 0x8e, 0x80, 0xaa, 0xa4, 0xb6, 0xb8, 0xe2, 0xec, 0
8888 Framing layer 8.4 Framing layer The following subsections define the framing layer applicable for the control interface. 8.4.1 Format of the service data unit (SDU) The SDU format is defined as below: 1 byte 0 – 512 bytes PORT SDU PAYLOAD Figure 8-3: Format of the service data unit • SDU payload: SDU data. Note Data types in the SDU payload are transmitted in little endian order. 8.4.
8-6 Confidential - For internal use SOF Lo 2 1 60 88 Data C Len Port 16 bytes Data D 43 bytes Data B CRC PDU Data E 23 bytes Data F 55 Len Port CRC SOF Hi 0 1 9 Data D Data E Len 21 bytes 16 bytes Data A CRC SOF Lo 1 0 60 8 bytes Len Data F 23 bytes 41 bytes Data F CRC Len Data F CRC SOF Lo 0 0 42 CRC SOF Lo 0 0 42 41 bytes Data D Len 21 bytes 16 bytes CRC SOF Lo 1 0 60 Example with a SDU of 160 bytes, sent with priority low on port 88 Data D 43 bytes Data F 64 bytes Data E
8888 Application layers 8.5 Application layers 8.5.1 Overview The control interface of the BGAN XL Radio Module provides a set of application layer protocols which is used for configuring and controlling the RM. These protocols are also referred to as the control interface protocols. The following application layer protocols must be implemented by the master: Protocol Description Port(s) Reference Management Operation management 1 8.5.2.4 Configuration 8.5.2.5 Event reporting 8.5.2.
Application layers A set of mandatory protocols are supported to provide extra functionality for integrating the RM in a product. Protocol Description Port(s) Reference Tunnel Direct communication between Data Interface and Control Interface master 130, 131 8.5.7 Debug shells Debug shell interfaces 4, 126, 127 8.5.8 Extended POST 64 8.5.9 Functionality to help perform extended POST and validation Table 8-3: Mandatory application layer protocols 8.5.
8888 Application layers Message Direction Summary Reference MSG_TFTP_RRQ In Request a transfer of a file 8.5.2.7.1 MSG_TFTP_DATA Out Data packet for TFTP transfer 8.5.2.7.2 MSG_TFTP_ACK In TFTP acknowledgement message 8.5.2.7.3 MSG_SUSPEND_REQ In Set Radio Module in suspend (only available in IAI2 mode) 8.5.2.8.1 MSG_SUSPEND_ABORT In Exit from suspend mode 8.5.2.8.2 MSG_POWERDOWN In Power down RM 8.5.2.8.3 MSG_REBOOT In Reboot RM 8.5.2.8.
Application layers The BGAN XL Radio Module will respond to messages with either an acknowledge or a not-acknowledge message indicating the result of the corresponding operation. This is illustrated in the figure below: Master RM MSG_WAVEFORM [op=10, ti=1] MSG_ACK [op=8, ti=1] MSG_CONFIG_WRITE [op=3, ti=2] MSG_ACK [op=8, ti=2] Figure 8-6: Management protocol message format Each management protocol message received in the RM is executed in sequential order.
8888 Application layers transmission has failed. In this case the master should try again, which is illustrated below. Master RM MSG_CONFIG_WRITE_REQ [op=3, ti=4] [ timeout ] MSG_CONFIG_WRITE_REQ [op=3, ti=5] MSG_ACK [op=8, ti=5] Figure 8-8: Message timeout handling The timeout period depends on the individual messages and is specified in the message descriptions. Note If the RM detects transmission errors (crc, framing errors...), it will output Syslog messages which informs of the detected error.
Application layers Cause code Description 19 The requested operation is not supported. See Syslog output for further details. 25 The BGAN XL Radio Module could not activate the requested waveform ID. See Syslog output for further details. 28 The BGAN XL Radio Module could not load the requested waveform ID. See Syslog output for further details. Table 8-7: MSG_WAVEFORM cause codes Response timeout: 4000 ms.
8888 Application layers Data field Type Length Offset Value Comment Opcode U8 1 0 1 Transaction ID U8 1 1 0-255 Type U8 1 2 0: Integer Type of record 1: String 2: Byte array RecIdLen U8 1 3 Record ID ARRAY RecIdL 4 en 0-128 Length of ‘Record ID’ field N/A Record identification in the format n.n.n.
Application layers offset \ byte 0 1 2 3 0 Opcode Transaction ID Type RecIdLen 4 Record ID .... ..... 4+RecIdLen ValueLen .... .....
8888 offset \ byte 0 1 2 4+RecIdLen ValueLen .... 3 ..... Value Table 8-13: MSG_CONFIG_WRITE_REQ data format (Continued) Data field Type Length Offset Value Opcode U8 1 0 3 Transaction ID U8 1 1 0-255 Type U8 1 2 0: Integer Comment Type of record 1: String 2: Byte array RecIdLen U8 1 Record ID ARRAY RecIdL 4 en ValueLen U16 Value ARRAY ValueL 6+Rec N/A en IdLen 2 3 0-128 Length of ‘Record ID’ field N/A Record identification in the format n.n.n.
Application layers Cause code Description 6 Write prohibited (read only record) 23 General error. See Syslog output for details. Table 8-15: MSG_NACK cause codes returned by a MSG_CONFIG_WRITE_REQ Response timeout: 2000 ms 8.5.2.5.4 MSG_CONFIG_NOTIFY_REQ Message to request notifications for a given setting or setting group. offset \ byte 0 1 2 3 0 Opcode Transaction ID Reserved RecordIdLen 4 Record ID .... .....
8888 Application layers Master RM MSG_CONFIG_NOTIF_REQ [ti=4, param=x.y] MSG_ACK [ti=4] MSG_CONFIG_NOTIF_REQ [ti=5, group=z] MSG_ACK [ti=5] MSG_NOTIFY_DATA [ti=4, param=x.y] MSG_NOTIFY [ti=5, param=z] Setting x.y is updated Setting group z is updated Figure 8-12: Example using MSG_CONFIG_NOTIF_REQ Cause code Description 2 Record not found 23 General error. See Syslog output for details. Table 8-18: MSG_NACK cause codes returned by a MSG_CONFIG_NOTIF_REQ Response timeout: 2000ms 8.5.2.5.
Application layers Data field Type Length Offset Value Comment Opcode U8 1 0 5 Transaction ID U8 1 1 0-255 RecIdLen U8 1 3 0-128 Length of ‘Record ID’ field Record ID ARRAY RecIdLen 4 N/A Record identification in the format n.n.n.n (ASCII characters) Table 8-20: MSG_CONFIG_NOTIFY data fields See 8.5.2.5.4 for further details. 8.5.2.5.6 MSG_CONFIG_NOTIFY_DATA Message sent when a registered record is changed. offset \ byte 0 1 2 3 0 Opcode Transaction ID Type RecIdLen 4 Reco
8888 8.5.2.6 Event reporting 8.5.2.6.1 MSG_USER_EVENT (FOR INTERNAL USE) Message to report a user event to the BGAN XL Radio Module. offset \ byte 0 1 2 3 0 Opcode Transaction ID Event ID 4 Unit ID Sub ID 8 Change Info Table 8-23: MSG_USER_EVENT data format Data field Type Length Offset Value Comment Opcode U8 1 0 7 Transaction ID U8 1 1 0-255 Event ID U16 2 2 see 7.7.2.1 on page 7-34. The id is a part of the event identification.
Application layers 8.5.2.6.2 MSG_SYSLOG Message to report a Syslog message to the BGAN XL Radio Module which will get forwarded to the data interface. offset \ byte 0 1 2 3 0 Opcode Transaction ID Timestamp [s] 4 ..... Timestamp [ms] 8 Priority Sequence 12 DataLen Data ... .....
8888 Application layers MSG_SYSLOG messages are acknowledged with MSG_ACK when accepted by the BGAN XL Radio Module. Cause code Description 32 Syslog data length too large Table 8-27: MSG_NACK cause code returned by a MSG_SYSLOG Response timeout: 2000ms 8.5.2.7 File transfer (FOR INTERNAL USE) The BGAN XL Radio Module can store product specific files uploaded via the data interface and provides a protocol for reading those files via the control interface.
Application layers It is up to the integrator to implement timeout handling and block number verification.
8888 8.5.2.7.2 MSG_TFTP_DATA (FOR INTERNAL USE) Message containing file data. offset \ byte 0 1 2 3 0 Opcode Transaction ID Block number 4 Data .... ..... Table 8-30: MSG_TFTP_DATA data format Data field Type Length Offset Value Comment Opcode U8 1 0 12 Transaction ID U8 1 1 0-255 Block number U16 2 2 any Block number of the current data block Data ARRAY 0-500 4 N/A Data block Table 8-31: MSG_TFTP_DATA data fields See 8.5.2.7 for more information. 8.5.2.7.
Application layers 8.5.2.8 Power management The following subsections define the messages used to control the power management of the BGAN XL Radio Module. 8.5.2.8.1 MSG_SUSPEND_REQ Message to set the BGAN XL Radio Module in suspend mode. See also section 11.5.2 on page 11-13 for further description of suspend mode and limitations when using it with SDM sleep. offset \ byte 0 1 2 0 Transaction ID Time [ms] Opcode 3 Table 8-34: MSG_SUSPEND_REQ data format Data field Type Length Offset Value Op
8888 offset \ byte 0 1 0 Transaction ID Opcode Table 8-38: MSG_POWERDOWN data format Data field Type Length Offset Value Opcode U8 1 0 16 Transaction ID U8 1 1 0-255 Comment Table 8-39: MSG_POWERDOWN data fields Master RM MSG_POWERDOWN MSG_ACK Figure 8-15: Power down message flow Response timeout: 6000 ms. 8.5.2.8.4 MSG_REBOOT Message to inform the BGAN XL Radio Module that it will be rebooted. When the system has decided to reboot/restart the RM the MSG_REBOOT must be sent.
Application layers Master Master RM RM MSG_POWERDOWN MSG_REBOOT MSG_MGN_ACK MSG_ACK Figure 8-16: Prepare for reboot message flow Response timeout: 6000 ms 8.5.2.8.5 MSG_RESET_REQ Message to request the control interface master to reset the BGAN XL Radio Module. The RM can request the control interface master to reset/reboot the RM using this message. If the RM has not been rebooted within 4000 milliseconds, it will reboot itself. offset \ byte 0 1 2 0 Transaction ID Reset Cause Opcode Table 8-42
8888 Application layers Data field Type Length Offset Value Transaction ID U8 1 0-255 1 Comment Table 8-45: MSG_ACK data fields The transaction identifier has the same value as the message being acknowledged. 8.5.2.9.2 MSG_NACK offset \ byte 0 1 2 0 Transaction ID Cause Code Opcode Table 8-46: MSG_NACK data format Data field Type Length Offset Value Opcode U8 1 0 9 Transaction ID U8 1 1 0-255 Cause code U8 1 2 See table below Table 8-47: MSG_NACK data fields Cause
Application layers 8.5.2.10 Aero-specific management The following sections describe messages which are used only in aeronautical terminals (see Table 3-4 for an overview of aeronautical BGAN classes). 8.5.2.10.1 MSG_AAGW_TIME The calculation of the AAGW timestamp is described in the SDM (v3c3) [18].
8888 Application layers 8.5.2.11 Security management (FOR INTERNAL USE) 8.5.2.11.1 MSG_SHELL_AUTHENTICATION (FOR INTERNAL USE) Message to request the BGAN XL Radio Module to enable authentication on the shell interfaces. When enabled, telnet access to DSP shell is denied and root login is required to login to CPU telnet shell. Shell authentication can only be disabled by rebooting the RM. When a production SIM card is inserted, shell authentication is automatically disabled until the card is removed.
Application layers 8.5.2.12 Bootloader security 8.5.2.12.1 MSG_SHA256_HASH RM bootloader v1.08 and newer will send a message control interface with a SHA256 hash of the application image before it loads the image. offset \ byte 0 1 0 Opcode Transaction ID .... .... .... .... 32 .... Len Hash ....
8888 Radio Module Board Processor R-APDUs C-APDUs USIM module Control interface USIM hw driver USIM card Control interface Control Interface serial link Figure 8-17: Typical USIM setup The flow of messages between the USIM HW driver and the USIM module are ISO 7816 APDUs. The APDU is an application level protocol as specified in the ISO 7816-4, which takes place between the USIM card (connected to the BP) and a host application (implemented in the RM).
Application layers Message direction: RM->BP offset \ byte 0 1 2 0 C-APDU (up to 512 bytes) .... ..... 508 ..... 3 Table 8-57: MSG_USIM_CAPDU data format Data field Type Length C-APDU ARRAY 0 - 512 Offset Comment 0 ISO/IEC 7816-4 5.3 Table 8-58: MSG_USIM_CAPDU data fields The Radio Module expects an R-APDU answer within 6000ms. Note The BGAN XL Radio Module uses relative file access in the USIM card in order to optimise file access response time.
8888 Application layers 8.5.4 Navigation protocol The navigation protocol specifies how to transfer positioning data to the BGAN XL Radio Module. 8.5.4.1 Overview The navigation protocol is an acknowledgement base protocol which consists of the three messages listed below: Message Direction Summary Reference MSG_NAV_REPORT In Positioning information message 8.5.4.2 MSG_NAV_ACK Out Acknowledgement of MSG_NAV_REPORT 8.5.4.4 MSG_NAV_NACK Out Not-acknowledgement of MSG_NAV_REPORT 8.5.4.
Application layers offset \ byte 0 1 2 3 0 Opcode Transaction ID Fix type Origin of fix 4 UTC time in seconds 8 Latitude 12 Longitude 16 Altitude 20 Velocity ECEF x 24 Velocity ECEF y 28 Velocity ECEF z 32 Number of satellites 36 HDOP Table 8-62: MSG_NAV_REPORT data format Data field Type Length Offset Value Comment Opcode U8 4 0 4 Transaction ID U8 1 1 0-255 Fix type 1 2 0-3 U8 0: No fix 1: Dead reckoning 2: 2D fix 3: 3D fix Origin of fix U8 1 3 0-3 0: Manu
8888 Application layers Data field Type Length Offset Value Comment Longitude S32 4 12 Longitude in degrees (1e7) (ie 121234567 specifies 12,1234567 degrees E) Altitude S32 4 16 Altitude in mm Velocity ECEF x S32 4 20 Velocity in ECEF (Earth-Centered, EarthFixed) coordinate system.
Application layers Data field Type Length Offset Value Transaction ID U8 1 1 0-255 Cause Code U8 1 2 3-4 Comment Table 8-65: MSG_NAV_NACK data fields Cause code Description 3 Unknown opcode 4 Message length mismatch Table 8-66: MSG_NAV_NACK cause codes 8.5.4.4 MSG_NAV_ACK Message response when the BGAN XL Radio Module has accepted the MSG_NAV_REPORT. offset \ byte 0 1 0 Transaction ID Opcode Table 8-67: MSG_NAV_ACK data format Data field Type Length Offset Value Opcode U8 1
8888 Application layers It is the responsibility of the integrator of the BGAN XL Radio Module to design an antenna pointing algorithm which matches the antenna and can accommodate requirements such as reliable pointing, fast channel acquisition and meaningful GUI information. A use case illustrating a simplified pointing procedure can be found in section 12.3.1 on page 12-6. 8.5.5.1 Message overview The protocol messages related to antenna pointing are listed in the following table.
Application layers Message Direction Summary MSG_BGAN_SKYSCAN_RESTART In Reference If the command is accepted then it 8.5.5.13 will result in a restart of the satellite search with a new MSG_BGAN_START_SKYSCAN MSG_BGAN_SKYSCAN_RESTART_ Out RESP Information about accept or reject of 8.5.5.14 MSG_BGAN_WAVEFORM_CNO Information about the signal quality. 8.5.5.15 Out MSG_BGAN_SKYSCAN_RESTART Table 8-69: Control Interface global waveform search messages (Continued) 8.5.5.
8888 The figure below illustrates the message flow. Master RM MSG_BGAN _SKYSCAN _ALLOWED MSG_BGAN _START _SKYSCAN _ALLOWED _RESP(valid = true or false ) MSG_BGAN_START_SKYSCAN [NumFreq=1 (to 2)] MSG_BGAN_SKYSCAN _RESULT [result = not tracking ] MSG_BGAN _SKYSCAN _RESULT _RESP(valid = true or false ) MSG_BGAN_START_SKYSCAN [NumFreq=2 (to 4)] MSG_BGAN_SKYSCAN _RESULT [result = not tracking ] MSG_BGAN _START_SKYSCAN [NumFreq=8 (to 16 i.
Application layers All input messages not received in the indicated states are rejected. Despite an input message is rejected the RM sends the expected response message, but valid field = false and the associated state shift is not executed. In case the response message contains measurement result fields, these fields are not valid. 8.5.5.3.1 State enumeration Several response messages contain a state field. These fields have the following values: 0. STATE_IDLE 1. STATE_WAIT_START_SKYSCAN 2.
8888 Data field Type Length Offset Value Opcode U8 1 1 0 Comment Table 8-71: MSG_BGAN_SKYSCAN_ALLOWED data fields 8.5.5.5 MSG_BGAN_SKYSCAN_ALLOWED_RESP The message is sent from the RM to inform about execution of the input message MSG_BGAN_SKYSCAN_ALLOWED. offset \ byte 0 1 2 3 0 Valid State Reject cause Opcode Table 8-72: MSG_BGAN_SKYSCAN_ALLOWED_RESP data format Data field Type Length Offset Value Opcode U8 1 0 2 Valid U8 1 1 0-1 Comment 0: MSG_BGAN_SKYSCAN_ALLOWED not
Application layers offset \ byte 0 1 2 36 Elevation .... .... .... .... 68 Longitude .... .... .... ....
8888 Application layers normal protocol operation. An unsuccessful result will force a new MSG_BGAN_START_SKYSCAN message to be issued with more global frequencies than the last message (if possible). offset \ byte 0 1 2 0 Result Frequency Opcode 3 Table 8-76: MSG_BGAN_SKYSCAN_RESULT data format Data field Type Length Offset Value Opcode U8 1 0 4 Result U8 1 1 0-1 Comment 0: Tracking 1: Not tracking Frequency U16 2 2 If the result is tracking this is the satellite frequency in
Application layers 8.5.5.9 MSG_BGAN_CHECK_POWER Message to request the BGAN XL Radio Module to start a power check (i.e. measure the channel power) on one or more frequencies. Master RM MSG_BGAN_CHECK_POWER [NumFreq=n] MSG_BGAN_CHECK_POWER_RESP [wide[n], narrow[n]] Figure 8-23: Check power message flow offset \ byte 0 1 2 3 0 Opcode NumFreq Frequencies .... .... 32 .... ....
8888 Application layers The BGAN XL Radio Module both delivers a wide and a narrow power estimate in which the filter bandwidths can be configured independently (see more in section 6.8.8 on page 6-52). The wide power estimate is in general calculated in a 36 kHz bandwidth and the narrow power estimate is calculated in a 14 kHz bandwidth as illustrated in the right section of Figure 8-24. The key parameters for determination of the narrow bandwidth are listed in the table below.
Application layers The characteristics of the wide (36 kHz) and narrow (14 kHz) band filters are plotted in the figure below together. Minimum clock misalignment Ideal clock (no offset) Maximum clock misalignment ‐5 ‐5 ‐10 ‐10 ‐15 ‐15 ‐20 ‐20 dB 0 dB 0 ‐25 ‐25 ‐30 ‐30 Necessary search bandwidth ‐35 Narrow Wide ‐35 ‐40 ‐40 ‐45 ‐45 ‐3 ‐2 ‐1 0 1 2 3 ‐3 ‐2 Normalized frequency ‐1 0 1 2 3 Normalized frequency Figure 8-24: Wide and narrow filter characteristics. 8.5.5.
8888 Application layers Data field Type Length Offset Value Comment Opcode U8 1 0 12 Number slots U8 1 1 1-16 Number of slots used in each of the power arrays valid U8 1 2 0-1 0: MSG_BGAN_CHECK_POWER_RESP is not executed 1: MSG_BGAN_CHECK_POWER_RESP is executed Reject cause U8 1 3 See section 8.5.5.3.2 on page 8-40. State U8 1 4 See section 8.5.5.3.1 on page 8-40. Reserved ARRAY 3 , U8 5 0 Power narrow ARRAY 64 , S32 8 List of narrow power measurements. 16 entries.
Application layers 8.5.5.11 MSG_BGAN_CHECK_WAVEFORM Message to request the BGAN XL Radio Module to start a waveform check for a global BGAN carrier on the specified channel number. Master RM MSG_BGAN _CHECK_WAVEFORM [freq1] MSG_BGAN _CHECK_WAVEFORM_RESP [valid=false] MSG_BGAN _CHECK_WAVEFORM [freq2] MSG_BGAN_CHECK_WAVEFORM_RESP [valid=true,cno=val] MSG_BGAN_WAVEFORM_CNO [cno=val] … Every 80ms ...
8888 Application layers 5. The outcome of this acquisition is either unsuccessful or successful: If the outcome is unsuccessful, the BGAN XL Radio Module cannot acquire the bearer within a specified time-out period. In this case the response MSG_BGAN_CHECK_WAVEFORM_RESP will contain a carrier-to-noise ratio (CNo) equal to 0 dBHz and an estimate of the channel power (wide). An unsuccessful response will be delivered approximately 360ms (see 6.8.
Application layers Data field Type Length Offset Value Comment Reject cause U8 1 4 See section 8.5.5.3.2 on page 8-40. State U8 1 5 See section 8.5.5.3.1 on page 8-40. Table 8-89: MSG_BGAN_CHECK_WAVEFORM_RESP data fields 8.5.5.13 MSG_BGAN_SKYSCAN_RESTART This message is sent to the BGAN XL Radio Module to signal a restart of the satellite search is needed. A typical reason for issue could be user action in a terminal GUI.
8888 Data field Type Length Offset Value Opcode U8 1 0 7 Valid U8 1 1 0-1 Comment 0: MSG_BGAN_SKYSCAN_RESTART not executed 1: MSG_BGAN_SKYSCAN_RESTART executed. State U8 1 2 See section 8.5.5.3.1 on page 8-40. Reject cause U8 1 3 See section 8.5.5.3.2 on page 8-40. Table 8-93: MSG_BGAN_SKYSCAN_RESTART_RESP data fields 8.5.5.
Application layers This message only identifies an abnormality and the source, The syslog contains further information. offset \ byte 0 1 0 Cause code Opcode Table 8-96: MSG_ABNORMALITY Data field Type Length Offset Value Opcode U8 1 0 1 Cause code U8 1 1 0: Internal RF 1: External RF Comment Source of the abnormality 2: Temperature Alert 3: Fatal Error 4: Position Needed 5: Doppler Velocity 6: Doppler Acceleration Table 8-97: MSG_ABNORMALITY data fields Depending on the cause code,
8888 Application layers • Cause code 6: The RM has calculated an unrealistic change in Doppler velocity (doppler acceleration is unrealistic). The cause is probably that position and/or velocity is wrong. The RM will not send data on-air if this is case. 8.5.6.2 MSG_ABNORMALITY_OK This message clears one or more abnormality situations. offset \ byte 0 1 0 Cause code Opcode Table 8-98: MSG_ABNORMALITY_OK Data field Type Length Offset Value Comment Opcode U8 1 0 2 Cause code U8 1 1 0: D
Application layers The RM will discard any data received if the receiving end is not ready to receive/accept the data. For example if the board processor transmits data on a specific tunnel port which has not been opened by the application processor. Important The current release only supports one TCP and UDP tunnel. Four data tunnels will be supported in future releases. 8.5.
8888 Application layers 8.5.8.2 MSG_DBGSHELL_DATA Message containing the debug shell character data. offset \ byte 0 1 2 0 Opcode Transaction ID Data ... 4 ... 3 Table 8-102: MSG_DBGSHELL_DATA data format Data field Type Length Offset Value Opcode U8 1 0 1 Transaction ID U8 1 1 0-255 Data Array 0-32 2 Comment Table 8-103: MSG_DBGSHELL_DATA data fields 8.5.
Application layers 8.5.9.1.1 MSG_EXT_POST_RF_CONTROL Message to initiate RF control extended POST. offset \ byte 0 1 0 Transaction ID Opcode Table 8-104: MSG_EXT_POST_RF_CONTROL data format Data field Type Length Offset Value Opcode U8 1 0 1 Transaction ID U8 1 1 0-255 Comment Table 8-105: MSG_EXT_POST_RF_CONTROL data fields 8.5.9.1.2 MSG_EXT_POST_RF_CONTROL_RESP Response message to MSG_EXT_POST_RF_CONTROL. offset \ byte 0 1 2 3 0 Opcode Transaction ID Tx acknowledge ...
8888 offset \ byte 0 1 2 0 Transaction ID Cause Code Opcode Table 8-108: MSG_EXT_POST_RF_CONTROL_NACK data format Data field Type Length Offset Value Opcode U8 1 0 3 Transaction ID U8 1 1 0-255 Cause Code U8 1 2 1-4 Comment Table 8-109: MSG_EXT_POST_RF_CONTROL_NACK data fields Cause code Description 1 Internal error. See Syslog output for further details. 2 Operation not allowed. The BGAN XL Radio Module is not in Service mode. See Syslog output for further details.
Application layers offset \ byte 0 1 0 Frequency Opcode 4 2 3 EIRP backoff Table 8-111: MSG_BGAN_START_CW data format Data field Type Length Offset Value Comment Opcode U8 1 0 20 Frequency U32 4 1 15180000001700000000 Frequency in Hz. EIRP backoff U32 2 5 0-1000 In steps of 0.01 dB. Table 8-112: MSG_BGAN_START_CW data fields 8.5.10.2 MSG_BGAN_STOP_CW Message to request the RM to stop transmission of a CW previously started with message described in section 8.5.10.1.
8888 Application layers Data field Type Length Offset Value Opcode U8 1 0 22 Valid U8 1 1 Comment 0: ESNO not valid else ESNO valid ESNO U16 2 2 Es/No in 0.1 dB Table 8-116: MSG_BGAN_FAST_ESNO_REPORT data fields 8.5.10.4 MSG_SET_IN_CW_MODE Used by RM to request L-Band return signal path to handle CW TX signal or BGAN burst TX signal. Only used in BPLT mode. offset \ byte 0 1 0 Setting Opcode Table 8-117: MSG_SET_IN_CW_MODE data format Data field Type Length Offset Value Opco
Application layers 8-60 Confidential - For internal use 99-137719-D
9999 Chapter 9 RF & RF control interface This chapter has the following sections: 9.1 RF interface ...................................................................................... 9-2 9.1.1 Transmission timing ....................................................................... 9-2 9.1.2 Output power (Tx) ........................................................................... 9-3 9.1.3 9.1.4 9.1.5 Receiver inputs (Rx1 & Rx2) .............................................................
RF interface 9.1 RF interface The BGAN XL Radio Module has a dedicated RF signal interface which consists of one output connection (Tx), two receive input connections (Rx1 and Rx2) and a precision reference clock input/output (Ref Clk). The Rx2 receiver input gives the integrator the opportunity to interface to the BGAN XL Radio Module at IF to implement an external downconverter as the primary input or as a part of an antenna-diversity solution.
9999 ([WHUQDO 3ODWIRUP 7HUPLQDO %RDUG SURFHVVRU +3$ /1$ &RQWUROOHU &RQWURO ,QWHUIDFH 5) &RQWURO ,QWHUIDFH %*$1 ;/ 5DGLR 0RGXOH 3URWRFRO SURFHVVRU ,) ,QSXW 5[ $ ' & 8SFRQYHUWHU 7[ $SSOLFDWLRQ SURFHVVRU 'DWD ,QWHUIDFH 0RGHP 76, ,QWHUIDFH , Q W H U I D F H V 5[ UI GHOD\ U[ H[WHUQDO 'RZQFRQYHUWHU ' $ & /1$ $ ' Q X W S H O Q UI GHOD\ U[ H[WHUQDO H Q [ D 'RZQ &RQYHUWHU +3$ UI GHOD\ W[ H[WHUQDO 3RZHU 6XSSO\ 5HIHUHQFH &ORFN 3RZHU 6XSSO\ ,QWHUIDFH 5HI &ON Figure 9-1: RF signa
RF interface The integrator must specify the nominal output power at the Tx connector of the BGAN XL Radio Module using the configuration parameter .rf.gain.tx.nominal_power which is specified in section 6.8.6 on page 6-50. 9.1.2.2 Gain compensation The BGAN XL Radio Module includes an algorithm which can compensate for external gain variations in e.g. the HPA. The algorithm operates on pairs of frequencies and gain corrections and performs either: 1.
9999 RF interface Note Gain variations over temperature must be handled externally by updating the compensation parameters (or the nominal power) according to the temperature drift. 9.1.2.3 Back-off level During normal operation the BGAN XL Radio Module will continuously adapt the output power to get the optimum trade-off between the required data bandwidth and the link conditions on the air interface.
RF interface Note The BGAN XL Radio Module does not have a special feedback loop incorporated to control the output power. If higher precision is needed (see section 5.6.5) the integrator should incorporate his own feedback loop in the externally connected HPA and align it with the reported EIRP information provided via the RF control interface (see section 9.2). 3QRP *FRPS 3RXW (,53 *+3$ )L[HG %RDUG SURFHVVRU 5) &WUO ,) 'DWD ,) 5[ &WUO ,) /1$ &RQILJXUDWLRQ V\VWHP 76, 7[ 5[ %*$1 ;/ 5D
9999 RF interface +3$ /1$ &RQWUROOHU &WUO ,) 5) &WUO ,) %*$1 ;/ 5DGLR 0RGXOH 'RZQ FRQYHUWHU 76, 7[ 5[ 'DWD ,) 5[ %RDUG SURFHVVRU 3RZHU /1$ ' X S O H [ $ Q W H Q Q D +3$ 5HI &ON Figure 9-4: Configuration with Rx2 as primary input.
RF interface Use of the secondary receiver input dictates that the wanted channel is aligned to a specific IF which has been selected very carefully to ensure that no spurious products occur. BGAN Rx2 Illegal range Illegal range MHz Maximum Standard Minimum Figure 9-6: Rx2 IF spectrum range The IF can be specified within the legal range shown in the table below using the configuration parameter .rf.rx2.chain.enable specified in section 6.5.3 on page 6-23.
9999 RF interface parameter which can be used to re-adjust an externally connected oscillator. This parameter is designated .clk.drift and is specified in section 6.7.2 on page 6-37. The aging parameter represents the estimated oscillator aging in ppm and is updated regularly. It is the intention that the integrator must read this parameter once during start-up and adjust any externally connected oscillator accordingly. 9.1.
+3$ /1$ &RQWUROOHU &WUO ,) 5) &WUO ,) 'DWD ,) 5[ %RDUG SURFHVVRU 5[ )UT $7& VHOHFW RF interface %*$1 ;/ 5DGLR 0RGXOH 76, 3RZHU ' X S O H [ $7& /1$ 7[ 5[ $7& )LOWHU $ Q W H Q Q D +3$ 5HI &ON Figure 9-9: Configuration for use in ATC environments (simplified) +3$ /1$ &RQWUROOHU &WUO ,) 5) &WUO ,) UI GHOD\ U[ H[WHUQDO 'DWD ,) 5[ %RDUG SURFHVVRU 5[ )UT $7& VHOHFW In order to operate properly with an externally connected ATC filter, the RM must be informed about change in the
9999 RF interface If there is no external interference filter in the terminal, it is up to the integrator to design an power detector circuit for interference that informs the RM when interference is present resulting in a switch to ATC mode (reduced gain/high IIP3).
RF control interface 9.2 RF control interface The BGAN XL Radio Module has a dedicated RF control interface which consists of a standard 4-wire SPI controller and four discrete pins as illustrated below. The interface is used for communication of timing-critical information between the physical layer of the BGAN modem and an external connected HPA/LNA. SPI transfers always consist of a data exchange.
9999 RF control interface 9.2.2 Rx control signal (B2B_Rx_Ctrl) This signal notifies about an active (High) or inactive (Low) receiver chain. The signal is mainly included to satisfy the strict requirements from the portable and battery driven terminal products. The Rx_up time can be controlled via the parameter .rfctrl.rx.receiver.up (see section 6.5.5.2 on page 6-26). The B2B_Rx_Ctrl signal is active high (i.e. high = active, low = inactive).
RF control interface The standard values of Burst init (tinit) and Burst start (tstart) are illustrated in the table below, but values are configured using the parameters .rfctrl.tx.burst.init and .rfctrl.tx.burst.start (see section 6.5.5.1 on page 6-25). Signal description Signal timing in respect to t0. Tolerance Burst init (rising) - 180 s Burst start (falling) - 44.63 s ±250 ns ±250 ns Table 9-3: Standard timing of Tx synchronization signal 9.2.
9999 RF control interface on page 8-51), and enter a dedicated error state where all modem functionality will be deactivated. t0-tguard t0 t1-tguard t0+tguard t1 t1+tguard B2B_Tx_Ack Tx out L-band signal Burst No-transmission data Transmission No-transmission Figure 9-14: Timing of the Tx acknowledgement signal (B2B_Tx_Ack) The transmission supervisory functionality is per default activated. It can be deactivated by the parameter .rfctrl.tx.ctrl.tx_ack_en (see section 6.5.5 on page 6-24).
RF control interface CW UW/DATA normalized power t0 R5T1X R5T2Q R5T2X R5T45Q R5T45X Figure 9-15: Illustration of the timing point t0. Applicable for all BGAN bearer types: • t0: Start of first CW symbol. Instantaneous Tx power level of -6 dBc (according to Tx burst information EIRP). For 79.52 ms preamble possibly preceding the R80T0.5Q and R80T1Q bearer types: • t0: Start of first preamble symbol. 655 s prior to instantaneous Tx power level of -6 dBc (according to Tx burst information EIRP).
9999 RF control interface The figure illustrates how the RF control timing events are aligned accordingly to the burst power mask where the specified timings offsets (T1 ..T10) are as defined in the SDM. tup tinfo tinit t0 tstart t1 tdown time 44.
RF control interface Symbol rate fsym Burst Duration 5 ms (R5) 20 ms (R20) 80 ms (R80) With preamble Without preamble 16.800 (T0.5) n.a. 330 1344+1344 XN 2+1344 XN 33.600 (T1) 156 660 2688+2688 XN 4+2688 XN 67.200 (T2) 312 1320 n.a. n.a. 84.000 (T2.5) n.a. n.a. n.a. 10 + 6720 XN 151.200 (T4.5) 702 2970 n.a. n.a. 168.000 (T5) n.a. n.a. n.a. 20 + 13440 XN Table 9-4: Burst duration in symbols (D) 9.2.5.
9999 f1 Start of frame first UW ymbol Frame start ½ symbol Frame 1 Start of first CW symbol Pnominal - x dB 2000 us CW80 or CW20 f0 Frame 0 180 us 180 us 2000 us 44.63 us 44.63 us t0 tinfo tinit tstart t0 tinfo tinit tstart Figure 9-17: Continuous transmission operation During continuous transmission the definition of the initial timing point, t0, is identical to the definition described in section 9.2.5.
RF control interface point (as defined by f0, f1 and f2) is larger than later intervals (summarized in the table below). Symbol rate fsym Time between consecutive t0 f0 f1 With preamble Without preamble 16.800 (T0.5) 1342 (79.88 ms) 33.600 (T1) 2684 (79.88 ms) Without preamble With preamble Without preamble 2+1344 2+1344 (80.12 ms) (80.12 ms) 1344 (80 ms) 1344 (80 ms) 1344 (80 ms) 4+2688 4+2688 (80.12 ms) (80.12 ms) 2688 (80 ms) 2688 (80 ms) 2688 (80 ms) 84.000 (T2.5) n.a.
9999 RF control interface of the previous burst will enter the ramp-up period of the next burst) as illustrated in the figure below.
RF control interface 9.2.7 Burst sequence example The example in the figure below illustrates how the RF control interface signals, during a two-burst sequence, will be exercised.
9999 RF control interface master. The definitions of the different messages are described in detail in section 9.2.8.3 on page 9-24. From slave (Platform) From master (Radio Module) MISO frame structure MOSI frame structure MSByte a MSByte r/w res dest data data data data LSByte address data data data LSByte data lsb msb lsb msb Figure 9-20: Structure of the SPI words 9.2.8.
RF control interface The slave must respond to each message from the BGAN XL Radio Module with an 8 bit status word in front of the data message formatted as shown below. a Access type Reserved lsb msb Status word r6 r5 r4 r3 r2 r1 r0 [0 = write only, 1 = read/write] [not used] Figure 9-22: Structure of the status word • The Access type bit is used to signal if the slave supports read accesses.
9999 RF control interface the efficiency of the user terminal. A detailed description of the return bearer types and their subtype identifiers are in chapter 2 (or in the latest version of the SDM). R/W Destination Address Message (1 bit) (3bit) (4 bit) name W(1) Tx (000) 0x0 (0) Description Tx Burst A burst message to the external transmitter information chain containing information about transmitted burst type, frequency and EIRP level. Bit 31..24: Spare Bit 23..16 : EIRP level as described below.
RF control interface Bearer type Code rate range No 8-bit value R5T1X (burst) L3 (11) to H6(20) 0 0x00 R5T2X (burst) L3 (11) to H6(20) 1 0x01 R5T4.5X (burst) L3 (11) to H6(20) 2 0x02 R20T1X (burst) L3 (11) to H6(20) 3 0x03 R20T2X (burst) L3 (11) to H6(20) 4 0x04 R20T4.5X (burst) L3 (11) to H6(20) 5 0x05 R5T2Q (burst) L8 (6) to RE(14) 6 0x06 R5T4.5Q (burst) L8 (6) to RE(14) 7 0x07 R20T0.
9999 RF control interface Bearer type Code rate range No 8-bit value T2Q (unframed) n.a 27 0x1B T2.5Q (unframed) n.a 28 0x1C T4.5Q (unframed) n.a 29 0x1D T5Q (unframed) n.a 30 0x1E T0.5X4 (unframed) n.a 31 0x1F T1X4 (unframed) n.a 32 0x20 T2X4 (unframed) n.a 33 0x21 T2.5X4 (unframed) n.a 34 0x22 T4.5X4 (unframed) n.a 35 0x23 T5X4 (unframed) n.a 36 0x24 T0.5X16 (unframed) n.a 37 0x25 T1X16 (unframed) n.a 38 0x26 T2X16 (unframed) n.a 39 0x27 T2.
RF control interface Bearer type Code rate range No 8-bit value T5X16 (unframed) n.a 42 0x2A T0.5X32 (unframed) n.a 43 0x2B T1X32 (unframed) n.a 44 0x2C T2X32 (unframed) n.a 45 0x2D T2.5X32 (unframed) n.a 46 0x2E T4.5X32 (unframed) n.a 47 0x2F T5X32 (unframed) n.a 48 0x30 T0.5X64 (unframed) n.a 49 0x31 T1X64 (unframed) n.a 50 0x32 T2X64 (unframed) n.a 51 0x33 T2.5X64 (unframed) n.a 52 0x34 T4.5X64 (unframed) n.a 53 0x35 T5X64 (unframed) n.
10101010 Chapter 10 This chapter has the following sections: 10.1 Self testing ......................................................................................10-2 10.2 Continuous monitoring ....................................................................10-6 10.3 Fail-safe feature ............................................................................. 10-11 10.4 Error mode .....................................................................................10-16 10.
Self testing 10.1 Self testing During startup the BGAN XL Radio Module performs a minor subset of tests to validate the internal connectivity to its sub-components and to verify that the RM is still operational. The table below shows the entries in the configuration system where the results are stored ('' is an integer that indicates the unit number. '' is an integer that indicates the POST number). post id cnt desc result status unit name Figure 10-1: Parameter hierarchy for POST parameters.
10101010 Self testing 10.1.1 Internal POST, UNIT 0 This subsection presents unit 0 POST entries which are related to the operation of the protocol layers (CPU/Interfacing/Digital Hardware). Parameter name post External Type / access Domain Range [min;max] Comment .unit.name.0 r string / ram ‘RM CPU’ Unit-name of unit 1. .status.0 r int / ram [0..4]* POST status of unit 1 .cnt.0 r int / ram [0..2^32-1] Number of POSTs for unit 0 .desc.0.0 r string / ram Testing CPU connectivity. .
Self testing Parameter name External Type / post access Domain Range [min;max] Comment .desc.1.3 r string / ram ’DSP POST RX PLL’ Testing RX PLL connectivity. .result.1.3 r int / ram .desc.1.4 r string / ram ’DSP POST TX PLL’ Testing Tx PLL connectivity. .result.1.4 r int / ram .desc.1.5 r string / ram ’DSP POST FPGA’ Testing FPGA interface connectivity. .result.1.5 r int / ram .desc.1.6 r string / ram ’DSP POST FPGA Testing FPGA DDR RAM connectivity. DDR-RAM’ .result.1.
10101010 0: Jan 01 00:18:23 POST Failed: [0104] - DSP POST TX PLL 1: Jan 01 00:18:23 Undefined Alarm for POST id: [0104] - DSP POST TX PLL • FPGA - validates that the interface connectivity between the DSP and FPGA. If the test fails a syslog entry will appear: Event log: 0: Jan 01 00:18:23 POST Failed: [0105] - DSP POST FPGA 1: Jan 01 00:18:23 Undefined Alarm for POST id: [0105] - DSP POST FPGA • FPGA DDR-RAM - validates that the interface connectivity between the FPGA and the DDR-RAM.
Continuous monitoring 10.2 Continuous monitoring The BGAN XL Radio Module provides functionality to continuously monitor the internal system components and operational mode. This functionality is referred to as continuous monitoring and uses syslog for distribution of events and data logging. 10.2.1 Events The syslog events of the BGAN XL Radio Module provide detailed information of events and exceptions during start-up and operation.
10101010 Group Syslog Text Explanation modem/main Inconclusive sequencing [Service|Operating BGAN] activation! A fatal error occurred during activation and the modem cannot complete the requested startup procedure. modem/rfctrl TxAck - Active during none transmission! The BGAN XL Radio Module has detected that the polarity of the Tx acknowledgement signal is active during a none-transmission period. This generates an abnormal behavior message.
Continuous monitoring Group Syslog Text Explanation modem/main Internal error detected string The diagnostic system has detected an internal minor error. string: Detailed information modem/fec Internal error detected string The diagnostic system has detected an internal minor error. string: Detailed information modem/main Inconclusive sequencing string The sequence of a requested terminal support function is inconclusive and modem cannot complete the requested operation.
10101010 10.2.2.1 Messages Group Syslog Text Explanation modem/clk mode=value1, drift=value2 ppm x100 Specifies the mode (value1) of the clock drift estimation and the estimated clock drift (value2) in ppm x 100 modem/main evm^2=value Specifies the mean squared estimate of the EVM as defined in the SDM. Update rate: every 4th second modem/main EsN0=value dB Specifies the signal-to-noise ratio of the received signal in decibel.
Continuous monitoring Group Syslog Text Explanation modem/main gain adj=value dB Specifies the latest gain adjustment (in dB) performed by the demodulator AGC. modem/main input distance=value Specifies the input symbol distance (in 15 bit unsigned ADC units) measured by the demodulator. modem/main code rate (UW)=value Specifies the code rate (range [0..14]) found by the demodulator (found from UW). modem/main bearer type (re-tune)=value Specifies the bearer type (range [0..
10101010 Fail-safe feature 10.3 Fail-safe feature The BGAN XL Radio Module has a variety of fail-safe features which prevent incorrect transmission and makes sure that fault conditions are quickly observed and reported. If something goes wrong as described in the following sections, a message is relayed to the Board Processor which must take appropriate action, see the message definition with suggested action in section 8.5.6.1 on page 8-51. 10.3.
Fail-safe feature 10.3.2 RF monitoring The BGAN XL Radio Module can monitor the RF Interface (see section 9.1 on page 9-2) for abnormalities. If any issues are observed, all transmission is stopped and the RM will generate an abnormal behavior message, MSG_ABNORMALITY (see section 8.5.6.1 on page 8-51), enter a dedicated error state and create an entry in the syslog. The following issues with the RF interface are supervised: • Discrepancies with Tx_Acknowledgement signal (see section 9.2.
10101010 Event id Event text Temperature limit 0x1010 Temperature too low (critical) -40 degree Celsius 0x1100 High temperature 70 degree Celsius 0x1120 Too high temperature warning 75 degree Celsius 0x1110 Temperature too high (critical) 84 degree Celsius Table 10-8: User events related to temperature reported by RM temperature sensor. (Continued) Note Temperatures listed in the table above refer to the temperature measured by the BGAN XL Radio Module (see section 6.4.3 on page 6-15).
Fail-safe feature Below is a flow chart of how the various events are raised in the BGAN XL Radio Module. &ULWLFDOO\ ORZ WHPS ! GHOWD WHPS 7RR ORZ WHPS ! GHOWD WHPS /RZ WHPS ! GHOWD WHPS 1RUPDO WHPS ! WHPS GHOWD +LJK WHPS ! WHPS GHOWD 7RR KLJK WHPS ! ,QIRUP ,QWHJUDWRU RI $EQRUPDO HYHQW DQG UHVHW &ULWLFDOO\ KLJK Figure 10-2: Temperature handling flow chart The delta value when moving between events is not a static value, but a built-
10101010 10.3.5 Navigational monitoring When the Doppler correction is enabled (see section 6.6.3 on page 6-29), then the BGAN XL Radio Module compensates its receive and transmit frequencies according to the calculated Doppler velocity. The calculated Doppler velocity is the terminal velocity vector projected onto the terminal to satellite direction. The calculation is based on input data extracted from the navigational reports (MSG_NAV_REPORT, see section 8.5.4.
Error mode 10.4 Error mode The BGAN XL Radio Module will enter the error mode (sys.status.mode) if one of the following situations occur: 1. Internal POST fails. 2. If an abnormal behaviour of the modem has been detected which causes the RM to enter fail-safe operation. Fail-safe operation is activated if one of the following circumstances has been detected: • The Tx Acknowledge signal indicates an ongoing transmission although the transmitter inside the RM is inactive.
10101010 10.5 Diagnostic reporting The BGAN XL Radio Module provides a diagnostic report for identifying problems in the field and during integration. The diagnostic report contains events, status and internal system information of the RM and is very useful for the support team. The RM uses Syslog to output real-time status information, while the diagnostic report is primarily used after a failing operation to collect additional system information for the support team.
Diagnostic reporting The HTML representation of the diagnostic report can be viewed using the URL http://[rm-ip]:8080/diagnostic. Figure 10-4: Diagnostic report browser view using Chrome The diagnostic view is grouped into sections which can be expanded and collapsed to get an overview of the diagnostic report. All the sections can be expanded using the query string http://[rm-ip]:8080/diagnostic?show=expanded.
11111111 Chapter 11 Terminal support 11 11.1 Terminal support This chapter describes the following sections: Overview ..........................................................................................11-2 11.2 Software update ...............................................................................11-3 11.3 Extended POST .................................................................................11-6 11.4 Drift estimation .............................................................
Overview 11.1 Overview A number of functions are implemented in the BGAN XL Radio Module to support integration, operation and troubleshooting of the complete terminal.
11111111 11.2 Software update 11.2.1 Introduction The software of the BGAN XL Radio Module is updated through the data interface using the HTTP protocol and the PUT method (RFC 2616 [13]). 11.2.2 Update procedure If there is valid application software in flash and the control interface interrupt input signal (Irq_In, see 5.7.1 on page 5-20) is not active high when the RM is taken out of reset, the RM will start the application software.
Software update first time, the software will be marked invalid, and the RM will use the previous loaded software after a system reset. A software update is accepted if the RM exits the ‘initial’ state, which can be checked using the sys.status.mode parameter. Note It is important not to reboot the RM when it is booting the updated software for the first time. If the RM is reset during the first boot attempt, the internal software update validation will fail and the RM will not apply the updated software.
11111111 Software update In safemode/bootloader the serial Control Interface is disabled and the BGAN XL Radio Module will only accept Telnet connections on the static IP 192.168.1.1 port 23. The software update procedure uses TFTP and is initiated by the shell command “tftp_tiif x.x.x.x software_file.tiif”. The sequence is illustrated below.
Extended POST 11.3 Extended POST When in service mode the BGAN XL Radio Module provides test functions to make interconnection tests of its various interfaces in order to allow the integrator to perform thorough testing of the terminal. These test functions are referred to as extended POST and are controlled by the integrator who must perform the pass/fail validation. The extended POST functions support tests of the following interfaces: • RF control interface (read/write test).
11111111 The test procedure is as follows: 1. Start the test by sending the following message on the control interface: MSG_EXT_POST_RF_CONTROL 2. The BGAN XL Radio Module will now initiate the test sequence described in section 11.3.1.3 below. 3.
Extended POST 11.3.1.3.1 SPI MISO The SPI MISO signal is sampled simultaneously with the transmission of the second MOSI message as shown in the figure below. The content of the MISO message is returned to the integrator for evaluation. 06*B(;7B3267B5)B&21752/ >UHVXOW@ 06*B(;7B3267B5)B&21752/ WXS WLQLW W a PV PV W PV PV WGRZQ a PV PV % %B7[B&WUO % %B7[B6\QF W[BDFN VDPSOH % %B7[B$FN W[BDFN VDPSOH PV WJXDUG 026, [ & 0,62 VDPSOHG 5) &WUO ,) 63, 026, [
11111111 11.3.3 Bit-Error-Rate testing (BER) The BGAN XL Radio Module offers a functionality so that the integrator can perform a simple Bit Error Rate test of an L-band signal (injected at the Rx connector via an external BGAN modulator). The integrator has the opportunity to bypass the FEC decoding (via the parameter specified in section 6.6.8 on page 6-31) and thereby get the raw bits from the channel.
Drift estimation 11.4 Drift estimation During normal run time operation the BGAN XL Radio Module offers the possibility to distribute various drift information to the integrator via a dedicated slot on the TSI bus: 1. The symbol clock drift of the received forward channel (which is directly related to a misalignment of the reference oscillator) is continuously measured. The clock drift information is available via a set of parameters located in the configuration system (see section 6.7.
11111111 located in the configuration system (see section 6.6.5) controls enabling of the clock drift information. 11.4.2 CS FIFO drift The CS FIFO drift information is distributed over the PCM/TSI bus. It is represented as an 8-bit signed value (byte 3) which yields a range of: [-27, 27-1] x 0.0625ppm = [-8.0000, +7.9375]ppm = [0x80, 0x81 … 0xFF, 0x00, 0x01 … 0x7E, 0x7F] This 8-bit representation covers the worst-case drift in the circuit switched fifo.
Power management 11.5 Power management The BGAN XL Radio Module is designed to save as much power as possible for two main reasons: 1. Save battery power, relevant for battery powered (portable) products. 2. To reduce the heat dissipation (all products) in the terminal. When in service or operating mode the BGAN XL Radio Module operates with an autonomous power management scheme which is designed to save as much power as possible at all times.
11111111 Power management The following figure illustrates an example of an SDM sleep scenario. The RM (mainly the IAI2- and UMTS protocol) is inactive in 58 frames (each 80 ms), then the receiver is started up with a ramp up of 5 frames waiting for any data in the 64th frame. Rx ”sleeping” (58 frames) Rx ”active” (1 frame) Terminal support Rx ”ramp up” (5 frames) Sleep mode period (64 frames) Figure 11-6: SDM sleep mode sequence (example).
Power management The RM will initiate the power up sequence illustrated in the right half of Figure 11-7 upon reception of an abort notification (refer to section 8.5.2.8 on page 8-24 or section 6.6.11 on page 6-32). In most short-term power failures (10 ms .. 200 ms) the RM will be capable of restoring any active calls and/or data sessions after the power has been re-established and the power up sequence has completed.
11111111 Name Time [ms] Description t3 20 The typical time consumed from a MSG_SUSPEND_ABORT is received to bring the entire modem out of suspend mode and enter receive only state. t4 240 The typical time consumed to enter the full operational state. Depending on the physical conditions on the forward channel the time can in some scenarios be higher than 420 ms. It takes some additional time before the RM has received reservations from RAN and can transmit.
Power management 2. If the integrator needs the power consumption to be reduced significantly, as described in the previous section, interaction from the RM is required. In scenarios where the integrator has knowledge that the satellite signal is not available the RM can be forced into suspend. In suspend, all modem activities will be de-activated until the RM is informed otherwise.
11111111 AP - BP links 11.6 AP - BP links 5) &RQWURO ,QWHUIDFH %*$1 ;/ 5DGLR 0RGXOH WXQQHO 'DWD ,QWHUIDFH 'RZQFRQYHUWHU 5[ WXQQHO &RQWURO ,QWHUIDFH Terminal support As illustrated in the figure below the BGAN XL Radio Module provides two different mechanisms to assist communication between the data interface and the control interface. A simple put and get interface (via the internal configuration system) and a more sophisticated data tunnel using UDP/TCP.
Integrator’s interface 11.7 Integrator’s interface The Integrator’s interface is an HTTP based interface to a number of functions relevant to an entity implementing the BGAN XL Radio Module in a product. The following functions are supported: • CW transmission • Unframed transmission • BGAN transmission • BGAN reception • Spectrum analyzer Not all functions can be used concurrently, i.e. the three transmission functions are mutually exclusive.
11111111 • Timing corrections • Synchronized by demodulator or simulated • If CW80 is present or not for LDR bearer types. These transmitter functions are described in the following sections together with a thorough description of their interfaces. 11.7.
CW transmission 11.8 CW transmission The BGAN XL Radio Module offers the capability to transmit a continuous wave (CW) manually. This functionality is a special case of the unframed transmission functionality (see section 11.9) and can be achieved in ‘service’ and ‘BPLT waveform’ modes. The CW is RRC filtered and generated with a symbol rate of 168000 S/s which generates harmonics (+/- 168 kHz away from the CW). The typical level of this harmonic is -50dBc 11.8.
11111111 11.8.2 Python Function name Description start( ...) This function starts a CW transmission (‘service’, ‘BPLT waveform’ mode). Parameters: Frequency in Hz [1518000000..1700000000], in steps of 1 Hz EIRP backoff in dB [0..10] with 0 as max, in steps of 0.01 dB Constraints: Expect a delay of approx. 55 ms from Tx start to the signal is present on the RF connector. stop() This function stops an ongoing CW transmission. Constraints: Expect a delay of approx.
Unframed transmission 11.9 Unframed transmission The BGAN XL Radio Module offers the capability to transmit a modulated carrier (without framing) manually. This functionality can be achieved in ‘service’ mode. The integrator must be aware that the unframed transmission allows combinations of symbol rate and modulation type which are not supported by the SDM.
11111111 Unframed transmission 11.9.2 Python Function name Description start(...) This function starts an unframed transmission (‘service’ mode). Terminal support Parameters: Frequency in Hz [1518000000..1700000000], in steps of 1 Hz EIRP backoff in dB [0..10] with 0 as max, in steps of 0.01 dB Symbol rate in S/s [16800, 33600, 67200, 84000, 151200, 168000] Known modulations ['Q', 'X4', 'X16', 'X32', 'X64'] Constraints: Expect a delay of approx.
BGAN transmission 11.10 BGAN transmission The BGAN XL Radio Module offers the capability to transmit BGAN formatted bursts manually. This functionality can be achieved in ‘BPLT waveform’ mode. To transmit BGAN formatted bursts the BGAN XL Radio Module must be locked to a forward BGAN carrier as the Tx carrier is synchronised to it. The BGAN reception functionality (see section 11.11) can be used to acquire a ‘simulated’ or ‘real life’ BGAN carrier (which enables burst transmission).
11111111 • Frequency offset in Hz (range from -100 kHz to +100 kHz from centre)1 • EIRP backoff in dB (range from 0 dB to 10 dB) • Timing in microseconds (range from -180 s to +180 s)2 The figure above holds an example where a R5T4.5QL8 burst is transmitted in slot 0 and R5T1XL3 is transmitted in slot 8. All the remaining slots (1..7 and 9..15) are empty. Bearer types corresponding to 20 ms bursts are specified on 4-slot boundaries (i.e., entries 0, 4, 8, 12).
BGAN transmission Tx timeplan example (frame 0..7 = FR80T5X16L3 and frame 8..
11111111 11.10.2 Integrator’s interface Functionality Actions States Modes supported Blocks functionality Notes: Tx Burst (/txburst/) start, stop Idle, Bursting BPLT Yes, blocks CW and unframed transmission • Tx Burst requires an input signal from either an internal BGAN frame generator, a Physical Layer Tester or a real signal to work, as this is used for synchronization.
BGAN transmission Parameter Name Valid Values Mandatory ones: payload data is filled with all ones. No Payload Data pd Default random zeroes: payload data is filled with all zeroes. random: payload data is filled with a random sequence of bytes. Seed value used to determine the random values are only modified with each byte written. counter: payload data is filled with a 16 bit continuous counter. Start value is incremented by 1 for each FEC block.
11111111 BGAN transmission 11.10.3 Python Function name Description start(...) This function starts a BGAN transmission (‘BPLT waveform’ mode). Terminal support Parameters: Frequency in Hz [1518000000..1700000000], in steps of 1250 Hz Bearer type (e.g. R5T1X) Code rate [L14..L1,R,H1..H6] Self Imposed Delay in s [0..80000] EIRP backoff in dB [0..10] with 0 as max, in steps of 0.
BGAN reception 11.11 BGAN reception The BGAN XL Radio Module offers the capability to manually set up a reception of a carrier with a BGAN formatted bearer type. This functionality can be achieved in ‘BPLT waveform’ mode. When the forward bearer synchronisation is simulated the reference clock will be initialised to the value specified in section 6.7.2 on page 6-37. 11.11.
11111111 11.11.2 Python Function name Description start(...) This function is used to start an reception of a BGAN bearer (‘BPLT waveform’ mode). Terminal support BGAN reception Parameters: Frequency in Hz [1500000000..1600000000], in steps of 1250 Hz Bearer type (e.g. F80T25X4) Simulate reception of a forward channel signal (on | off) Constraints: Expect a delay of approx. 5 ms before the command has been issued.
Spectrum analyzer 11.12 Spectrum analyzer The spectrum analyzer (SA) is meant as a tool to be used in development, in production and in the field in any terminal using the BGAN XL Radio Module. The FFT based SA is available when the BGAN XL Radio Module is operating in ‘service’ mode. The SA is able to calculate parameters characterising the signal and to generate data to be used in a plot of the power spectrum of the signal applied.
11111111 Terminal support Spectrum analyzer Figure 11-13: Example of a spectrum as shown in a web browser The spectrum plot above illustrates a spectrum of a CW signal at 1550030000 Hz which has been applied to the Rx1 connector of the BGAN XL Radio Module. The x-axis (frequency axis) will auto-scale depending on the span chosen. The y-axis has a fixed-scale dBFS (dB Full Scale). The raw data being plotted can be accessed at: .../fft/fft_data.
Spectrum analyzer 11.12.2 Measurement principles The following subsections summarize the measurement principles used by the spectrum analyzer. The figure below is used to visualize the different power definitions.
11111111 11.12.2.2 Max peak The peak power (B) is calculated in dBm as the total power within a band of +/- 3 bins from the maximum FFT bin: Pwr peak k+n = 10 log P i i = k – n The peak power value is given in dBm and the value can be extracted from: .../fft/fft_data via the variable spectrum.header.peak_power.rx1 likewise the frequency offset of the max peak frequency (given in Hz) is located in the variable spectrum.header.peak_freq. 11.12.2.
Spectrum analyzer 11.12.2.
11111111 Spectrum analyzer 11.12.2.8Resolution bandwidth Span Resolution bandwidth (RBW) 2 kHz 1 Hz 20 kHz 10 Hz 200 kHz 100 Hz 2 MHz 1 kHz Terminal support The spectrum analyzer utilizes a fixed number of FFT bins (2000 points) whereas the resolution bandwidth becomes scalable with the selected span as listed in the table below. Table 11-12: RBW versus selected span 11.12.
Spectrum analyzer The different gain contributions are listed in the table below, for internal information only, however it is beyond scope of this manual to go into details about how these are controlled. Section Gain Analog LNA: enabled (+17 dB) / bypassed VGA1: enabled (+17 dB) / bypassed VGA2: variable 0 – 28 dB Digital DDC: variable 0 – 32 dB Table 11-13: Gain 11.12.
11111111 Parameter Name Valid Values Mandatory Default Window Type win none, hanning, hamming, blackman No none Phase Noise Offset (Hz) pno -span/2..span/2 No 0 Phase Noise Bandwidth (Hz) pnbw 1..span-1 No 1 Spur Search Bandwidth (Hz) spur 1..span-1 No 1 Receiver Gain (dB) gain -100..32 (in steps of 0.
Spectrum analyzer Function name Description configure_spur(...) This function configures the spur search bandwidth of the spectrum analyzer. Parameters: Spur search bandwidth in Hz [1..span-1] configure_gain(...) This function configures the gain of the spectrum analyzer. Parameters: Gain in the receiver chain in dB [-100..32], in steps of 0.01 dB set_FFT(...) This function configures the complete spectrum analyzer in one of four modes.
11111111 Function name Description get_bins() This function gets the bins of a calculated spectrum. Returns: contains all the bins specifies the number of bins specifies span/2 data_array contains spectrum in dBFS, subtract the value of dbm_offset to get spectrum in dBm configure_manual_gain(...) This function configures the gain the spectrum analyzer manually. For advanced users only.
SIM lock 11.13 SIM lock This section describes the SIM lock (or personalization lock) interface on the BGAN XL Radio Module. Three different SIM lock types are supported. It is possible to lock the user terminal to: • (2) A specific service provider by using the group identifier of the USIM card. • (3) A specific corporate SIM card owner by using the group identifier. • (4) A specific SIM card.
11111111 SIM lock 0 Ok. SIM lock code was stored 1 Operation failed because a SIM lock code already has been stored 2 String in .set.password is too short 3 String in .set.password is too long 4 String in .set.password parameter contain invalid characters. Terminal support Code Description Valid characters are: 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, a, b,c, d,e, f, A, B, C, D, E, F 5 Could not write to flash 6 .set.
SIM lock Return code Description 10 Storage read operation failed. 11 Wrong code entered. 255 Used to trigger a request. See the next section for a description. Table 11-18: Return codes from the SIM lock interface (Continued) There are 5 interfaces for communication with the SIM lock feature, they are asynchronous of nature. The following steps are general guidelines for all 5 interfaces. 1. Each interface has a .result parameter. Before making a request, the client must read this key.
11111111 SIM lock 11.13.2.1 Check SIM lock password Parameter name External Type / protocols.umts.personali access Domain zation Values Comment [min;max] .check.sim_lock_passwd r/w t4 §4 string / ram n.a. SIM lock code (password) which must be verified. The code must be provided in order to get access to the SIM lock information. Must be 32 bytes hex characters. .check.result r/w t4 §4 string / ram n.a. The result of the .sim_lock_passwd check. A SIM lock code must be written to .
SIM lock .penalty_time.result = ; where is one of the numeric codes from Table 11-18 and is the penalty time in seconds, only valid if is 0. 11.13.2.3 Set SIM lock This interface is used to set a SIM lock of a specific category. Parameter name External Type / protocols.umts.person access Domain alization Values Comment [min;max] .set.lock_category r/w t4 §4 int / ram [2..4] .set.imsi_or_gid2 r/w t4 §4 string / ram n.a.
11111111 11.13.2.4 Get SIM lock This interface is used to get information on the current SIM lock category, if any. Parameter name External Type / protocols.umts.per access Domain sonalization .get.result Values Comment [min;max] r/w t4 §4 string / ram n.a. A result string containing information regarding the current SIM lock, if any is present. Table 11-22: Get SIM lock information Result syntax: .get.
Supplementary services (eMLPP registration) 11.14 Supplementary services (eMLPP registration) Most supplementary services (call forward, call barring etc.) can be set with AT commands (see 7.5.11 on page 7-12). For eMLPP the AT command AT+CAEMLPP can be used to set the eMLPP priority in the network. The AT command must however only set the priority if this is allowed by the SIM card.
11111111 S-Band terminal (FOR INTERNAL USE) 11.15 S-Band terminal (FOR INTERNAL USE) If using the RM in S-Band class 7S terminal the following parameters must be set: • • • • sys.product_type = 5 protocols.bgan.functionality.sband = 1 protocols.bgan.functionality.class = 7 protocols.bgan.functionality.ssr_muting.
S-Band terminal (FOR INTERNAL USE) 11-50 Confidential - For internal use 99-137719-D
12121212 Chapter 12 Use cases 12 This chapter has the following sections: 12.1 Startup and mandatory configuration .............................................. 12-2 12.2 Calibration ....................................................................................... 12-4 12.3 Network registration .......................................................................12-6 Use cases 12.4 Connection setup .............................................................................12-8 12.
Startup and mandatory configuration 12.1 Startup and mandatory configuration 12.1.1 Service activation This use case presents a simplified description of the required service activation procedure to get access to the service related API offered by the BGAN XL Radio Module. 1. Power up the BGAN XL Radio Module 2. Read the configuration parameter: 'sys.status.mode' 3. Loop step 2 until 'sys.status.mode' is ‘ready’. 4. Read the configuration parameters: 'post.status.1' and 'post.status.
12121212 Startup and mandatory configuration 12.1.3 Waveform activation (BPLT mode) This use case presents a simplified procedure describing how a waveform is loaded in the BGAN XL Radio Module and activated to operate in BPLT mode. The use case assumes that the RM has already been brought into an active service mode. 1. Load the waveform by sending: MSG_WAVEFORM (load=0, BPLT=1). 2. Wait for acknowledge via the message: MSG_ACK. 3. Read the configuration parameter: 'sys.status.
Calibration 12.2 Calibration 12.2.1 Tx power calibration This use case presents a simplified description of a calibration procedure for an antenna cable loss. The procedure is initiated and controlled by an antenna control module (ACM) located outside the BGAN XL Radio Module. 1. Put the RM into 'service mode' (refer to section 12.1.1). 2. Put the antenna into 'cable loss calibration mode'. 3. Select the appropriate cable loss calibration algorithm according to class type and antenna type. 4.
12121212 Calibration 14. Set the parameter protocols.bgan.interface.rf.gain.tx.locked to 1 indicating that the parameters are being updated. 15. Configure the RM with the calculated compensation factor via the parameters: protocols.bgan.interface.rf.gain.tx.pwr_freq1..15 and protocols.bgan.interface.rf.gain.tx.pwr1..15. 16. Set the parameter: protocols.bgan.interface.rf.gain.tx.pwr_pairs to the needed number of frequency points (1..15). 17. Reset protocols.bgan.interface.rf.gain.tx.
Network registration 12.3 Network registration 12.3.1 Global beam search This use case presents a simplified description of an antenna pointing procedure, which is initiated and controlled by the satellite search protocol. The integrator should execute the following steps using an appropriate antenna pointing procedure suited to the antenna type. For example antennas with build-in power detector are free to skip measurements of channel power.
12121212 7. Stop sky-scan in the BGAN XL Radio Module by sending: MSG_BGAN_SKYSCAN_RESULT indicating that the sky-scan has succeeded. 8. Signal sky-scan mode done to the antenna. 12.3.2 Registration When the preceding two use cases have been successfully done the next steps of the registration procedure are as follows: 1. Notify the BGAN XL Radio Module that a USIM card is available by setting the configuration parameter platform.usim.status to 1. The RM now uses the protocol specified in section 8.5.2.
Connection setup 12.4 Connection setup 12.4.1 PS setup This use case presents a simplified description of how to do a PS setup of a primary PDP context from a module in the application processor. 12.4.1.1 General note on AT commands for PS setup As described in section 7.6.4 on page 7-21, parameters for a PDP context family can be manipulated on the BGAN XL Radio Module via an AT shell on the RM.
12121212 Connection setup client with the following parameters. The exact naming of these parameters depends on your choice of SIP implementation on the application processor. Parameter Value Server address 192.168.1.1a Server port 5060 User name (protocols.sip.user-name) sip1 Password (protocols.sip.password) sip1 Codec (protocols.sip.codecs) PCMA RTP packet time (ptime) 20 ms Use cases Register with server to make outgoing calls Yes Table 12-1: CS setup a.
Operation 12.5 Operation 12.5.1 ATC handling This use case presents a simplified flow of an ATC configuration without an external ATC filter (the responsibility of detecting an ATC interferer is performed externally). 1. Provide the RM with mandatory and additional configuration as described in section 12.1.1 and 12.1.2. 2. Activate the RM to operate in 'bgan_waveform mode'. 3.
12121212 12.6 Services 12.6.1 Spectrum analyzer (spectrum measurement) This use case illustrates how the internal spectrum analyzer is configured and activated to generate an FFT spectrum of a received forward signal. The use case assumes that the BGAN XL Radio Module has already been brought into an active service mode and a signal has been injected at Rx1 at 1550.01 MHz.
Services 1000000.000 -1000000.000 -24.216 -126.497 2000 100 1 12.6.2 Spectrum analyzer (spurious search) This use case illustrates how the internal spectrum analyzer is configured and activated in relation to spurious measurements of a received forward signal.
12121212 Services Use cases 1550000000 10.000 -237000.000 -116.721 388000.000 -124.279 -158000.000 -127.197 178000.000 -128.352 1000.000 1000000.000 -1000000.000 -24.260 -126.
Services 6. Find the phase noise measurements at http://192.168.1.1:8080/fft/fft_data, which contains information similar to (note the phase_noise value): 49.080 -78.333 -29.253 -78.348 -29.268 10000.000 -165.565 -116.485 87.
12121212 Services 11. Find the phase noise measurements at http://192.168.1.1:8080/fft/fft_data, which contains information similar to (note the significantly higher phase_noise value): Use cases 70.100 -78.480 -8.380 -78.487 -8.387 10000.000 -168.817 -98.
Services protocols.bgan.functionality.satellite_table.change.channel.alternate to the new values. 5. Set protocols.bgan.functionality.satellite_table.change.default to 0. 6. Reset protocols.bgan.functionality.satellite_table.change.locked to indicate that the parameters have been updated and are ready to be used. 7. The RM will now read the changed values and update the satellite table. The satellite table will only be update if the .satellite_id set in step 3 already exists. 12.6.
12121212 12.7 Physical & protocol layer test 12.7.1 BPLT testing Square Peg communications Inc. has created an elaborate User’s Guide to the BPLT which provides a system overview and instructions as to how the environment is installed, operated and maintained as well as hints to troubleshooting the BPLT setup if it malfunctions. In order for the BGAN XL Radio Module to be able to communicate with the BPLT, it is necessary to activate the BPLT waveform. The steps to achieve this are described in 12.1.
Physical & protocol layer test forward/return data, satellite longitude and UE position. The full range of necessary information is described in the documentation from Square Peg1. Most requirements for how to execute a BPLT are described in these documents, but special attention is necessary regarding Doppler correction. 12.7.1.
12121212 Physical & protocol layer test BPLT Input Transmit output Satellite Longitude UE Position UE Velocity LESP Doppler Input ser Channel 1 N/A 2 S1 3 N/A N/A N/A N/A S1, P1, V1 L1 P1 4 L1 5 6 N/A V1 S2 Use cases Time S2, P1, V1 7 V2 S2, P1, V2 Table 12-2: Doppler compensation execution as result of Doppler compensation source data input to the RM Table 12-2 shows an example of how the RM uses the Doppler compensation source data to calculate the Doppler compensation based o
Physical & protocol layer test 12.7.1.
12121212 6. Run the spectrum analyzer (see 12.6.1 on page 12-11) with the following parameters set • Span: 200 kHz • Centre frequency: 1542.0 MHz • Number of averages: 64 • Window Type: Blackman • Rx Auto Gain: 0 dB • Click Save All and then Run Spectrum followed by Refresh Spectrum. 7. Log the CW Level found by the Spectrum analyzer ( ). See 12.6.1 on page 12-11: Level RM = – xx dBm 8. Calculate the UT LNA gain between UT input and RM input: Gain LNA = Level RM – Level UT dB 9.
Physical & protocol layer test 12.7.2.1 Test setup The following illustration shows a standard test setup. ISDN Test Equipment ISDN UT under test RF (L-band, Uu-Interface) BPLT ISDN Cross Over Cable ISDN Terminator Ethernet Ethernet switch (local net) Ethernet BPT RS232/USB/Ethernet (R-Interface) (PC running Test Case Manage Figure 12-3: Physical and protocol layer test, setup Specific information for the setup of the environment, IP addresses, port numbers etc.
12121212 • Reboot the RM for changes to take effect. • It is only necessary to run this script once when setting up a user terminal for protocol testing. 3. Execute the appropriate Python script, depending on which MTR script(s) must be executed. As a rule of thumb, one Python file corresponds to a test suite, however it is worth noting that some MTR scripts require a slightly different configuration and is therefore associated with a different Python script than the suite it is a part of.
Physical & protocol layer test port numbers etc. The BGAN XL Radio Module shall also be in test script mode during the test. UT under test RF (L-band, Uu-Interface) BPLT Ethernet Ethernet switch (local net) Ethernet BPT (PC running Test Case Manager) Ethernet Ethernet 2W/4W VCTS Ethernet RS232 VCDS (PC running Terminal programs and VCDS) Figure 12-4: VCTS test setup The principle of operation is as follows. A circuit-switched call is established between the terminal and the BPT/BPLT.
13131313 Chapter 13 Applications 13 This chapter has the following sections: 13.1 Typical application ........................................................................... 13-2 Applications 13.2 Minimum application .......................................................................
Typical application 13.1 Typical application Figure 13-1 shows a block diagram of a typical integrated terminal based on a BGAN XL Radio Module. 7HUPLQDO 5) &RQWURO ,QWHUIDFH %*$1 ;/ 5DGLR 0RGXOH 'RZQFRQYHUWHU 5[ &RQWURO ,QWHUIDFH /1$ $ ' & 3URWRFRO SURFHVVRU ,) ,QSXW 5[ $SSOLFDWLRQ SURFHVVRU +3$ /1$ &RQWUROOHU 'DWD ,QWHUIDFH 8SFRQYHUWHU ' X S O H [ 0RGHP 76, ,QWHUIDFH , Q W H U I D F H V %RDUG SURFHVVRU 7[ 8 6 , 0 ' $ & 3RZHU 6XSSO\ 5HIHUHQFH &ORFN 3RZHU 6XSSO\ ,QWHUIDFH
13131313 Minimum application 13.2 Minimum application Figure 13-2 shows a block diagram of a minimum terminal based on a BGAN XL Radio Module 7HUPLQDO 8 6 , 0 %RDUG SURFHVVRU %*$1 ;/ 5DGLR 0RGXOH /1$ 5[ 3URWRFRO SURFHVVRU ,) ,QSXW 8SFRQYHUWHU 7[ $ ' & ' X S O H [ 0RGHP 76, ,QWHUIDFH ' $ & 3RZHU 6XSSO\ 5HIHUHQFH &ORFN 3RZHU 6XSSO\ ,QWHUIDFH 5HI &ON $ Q W H Q Q D +3$ Applications 'RZQFRQYHUWHU 'DWD ,QWHUIDFH 8 6 % 5) &RQWURO ,QWHUIDFH 5[ &RQWURO ,QWHUIDFH Figure 13-2: Mi
Minimum application 13-4 Confidential - For internal use 99-137719-D
14141414 Chapter 14 Type approval 14 This chapter has the following sections: 14.1 Introduction ..................................................................................... 14-2 14.2 Pre-approved MTRs .........................................................................14-6 14.3 Physical layer .................................................................................. 14-7 14.4 Protocol layer .................................................................................
Introduction 14.1 Introduction A BGAN terminal must undergo a type approval campaign and be type approved by Inmarsat before it can be sold to customers. A type approval campaign will typically comprise the steps shown in the figure below. %HWD 7HVW $OSKD 7HVW )DFWRU\ $FFHSWDQFH 7HVW )$7 3UH &RQWLRQDO 7\SH $SSURYDO 3&7$ 7\SH $SSURYDO 3URFHGXUH Figure 14-1: Typical Type Approval Procedure Upon completion of all the tests included in the type approval campaign, Inmarsat will evaluate the test reports
14141414 • Audio Tests MTRs Normally, a product is required to pass all of the specified tests in order to be granted a type approval. Some tests may be excluded though, if they do not apply to the particular terminal class in question. The MTRs are defined in documents which are written and provided to the terminal manufacturers by Inmarsat. The actual MTR documents are covered by an NDA and may not be reproduced here. The integrator can request them directly from Inmarsat.
Introduction 14.1.3 Factory acceptance test The Factory Acceptance Test (FAT) serves as an Inmarsat approval milestone that when passed - will grant permission to go ahead with the beta test campaign with selected customers and pave the way towards full type approval. The FAT campaign consists of re-execution and reporting of MTRs but in addition to the PCTA some of the scripts must be executed in different environmental conditions (vibrations, humidity and extreme temperatures).
14141414 Introduction 14.1.5 Beta test The purpose of the beta test is to validate the BGAN terminal in the target environment by real customers in order to spot possible issues and obtain end-user feedback about the product. The beta test will be performed by end-users identified by the BGAN terminal vendor. Also, Inmarsat will typically be offered a system in order to make a test and provide feedback. The scope of the specified beta test requires the end-user to make some predefined tests.
Pre-approved MTRs 14.2 Pre-approved MTRs In order to ease the type approval process for integrators certain MTRs have been preapproved in agreement with Inmarsat. This means that integrators can refer to these pre-approvals in their test plans when they apply for type approval. The pre-approved MTRs are all testing functional areas of which the performance is defined by the BGAN XL Radio Module.
14141414 14.3 Physical layer The test setup for verification of the physical layers is based on a BPLT. The BPLT executes MTR defined test scripts which are specially designed to verify the performance of the BGAN physical layers. The BPLT contains channel boards interfacing to the RF interface of the BGAN terminal and an Ethernet interface connecting it to a data interface of the BGAN terminal as shown in the following figure.
Physical layer BPLT Mode the RM can be controlled using the interface protocols described in section 7.8.1 on page 7-40. Important The BGAN XL Radio Module holds a deviation for MTR 7, 9 and 23. The exact extent of these deviations are described in a subsection under the respective MTRs! Important ATC MTR is not part of the subsections below and must be tested by the integrator. 14.3.
14141414 Class 6H,7H Class 8,9,14 Class 10,11 L RM RM RM RM M RM RM RM RM O RM RM RM RM W RM RM X RM RM Y RM RM Z RM RM Class 2 Class 1H Sub-Test Class 4 Physical layer Table 14-2: Sub test specifications: QPSK frame acquisition (Continued) a. Not required for type approval. 14.3.2.
RM Class 10,11 RM RM Class 8,9,14 Class 6H,7H L W Class 4 Class 2 Class 1H Sub-Test Physical layer Table 14-4: Sub test specifications: QPSK Packet Error Rate. 14.3.4 MTR 9 QAM Frame Acquisition Sub-Test Class 1H Class 2 Class 4 Class 6H,7H Class 8,9,14 Class 10,11 MTR 9 QAM Frame Acquisition, verifies the Frame Acquisition performance of the terminal when receiving a QAM forward bearer.
14141414 14.3.4.1 Deviations MTR Name and Function Sub-test Class Deviation granted 9 QAM Frame Acquisition E All July 2nd 2013 Re-acquisition after Blockage Original requirement: Blocking Level: -20 dB, PER (6th frame): 0.01, PER (7th frame): 0.001 Achieved Performance: Blocking Level: -30 dB, PER (6th frame): 0.20, PER (7th frame): 0.001 The BGAN XL Radio Module has been granted a permanent deviation on this MTR.
Physical layer 14.3.6 MTR 11 QPSK selectivity Class 1H Class 2 Class 4 Class 6H,7H Class 8,9,14 Class 10,11 Sub-Test MTR 11 QPSK selectivity, verifies the Packet Error Rate performance of the terminal in the presence of out-of-band interfering signals and in-band adjacent channel interferers, when receiving a QPSK forward bearer. INT INT INT INT INT INT Table 14-8: Sub test specifications: QPSK selectivity. 14.3.
14141414 Physical layer 14.3.9 MTR 14 EIRP Determination and Stability Class 4 INT INT INT INT INT INT INT INT Class 10,11 Class 2 INT INT INT INT Class 8,9,14 Class 1H A B H I L M Class 6H,7H Sub-Test MTR 14 EIRP Determination and Stability, verifies the transmitted EIRP of the terminal. INT INT INT INT INT INT INT INT Table 14-11: Sub test specifications: EIRP determination and stability 14.3.
Physical layer 14.3.12 MTR 17 Transmitter Phase Noise Class 1H Class 2 Class 4 Class 6H,7H Class 8,9,14 Class 10,11 Sub-Test MTR 17 Transmitter Phase Noise, verifies the transmitted phase noise of the terminal. RM RM RM RM RM RM Table 14-14: Sub test specifications: Transmitter Phase Noise. 14.3.
14141414 14.3.15 MTR 20 Modulator Performance RM/INT RM/INT RM/INT Class 10,11 RM/INT Class 8,9,14 Class 4 RM/INT RM/INT Class 6H,7H Class 2 H L Class 1H Sub-Test MTR 20 Modulator Performance, verifies the modulation characteristics of the terminal. RM/INT RM/INT RM/INT RM/INT Table 14-17: Sub test specifications: Modulator Performance The BGAN XL Radio Module is tested against a tougher requirement: EVM2 1.5e-3 and then released. Note 14.3.
Physical layer 14.3.17.1 Waiver Deviation granted MTR Name and Function Sub-test Class 23 C/No Measurement and Reporting A 1/HDR, July 2nd 2013 2, 3 At high C/No the demodulator estimates slightly too low (~0.1 dB). A new algorithm for C/No estimation is planned and will be implemented in a future software release. The BGAN XL Radio Module has been granted a temporary waiver on this MTR. Table 14-20: Waivers on C/No measurement 14.3.
14141414 Physical layer 14.3.20MTR 26 Transmitter Power Spectral Density INT INT INT INT Class 10,11 INT Class 8,9,14 Class 4 INT INT Class 6H,7H Class 2 H L M Class 1H Sub-Test MTR 26 Transmitter Power Spectral Density, verifies the transmitted burst spectral shape. INT INT INT Table 14-23: Sub test specifications: Transmitter Power Spectral Density The BGAN XL Radio Module is release-tested against a tougher spectral mask: mask reduced by 8 dB for the R80T0.
Protocol layer 14.4 Protocol layer The test setup used for verification of the protocol layers is based on a BGAN Protocol Tester (BPT). The BPT executes the different protocol layer test scripts defined by protocol test MTR documents. The protocol tests are performed in a closed loop test setup using a BPT and a BPLT as outlined in Figure 14-4 below.
14141414 no HDR or ISDN support for example, has not been validated against the ISDN suite or the HDR test cases. The test results can be replicated and verified by the integrator by following the guidelines described in section 12.7.2 on page 12-21 along with the protocols and software mentioned in section 7.8 on page 7-40. It may be necessary for the integrator to at least verify the ISDN test result with their own ISDN equipment. 14.
Audio tests Note Access to two 4-wire interfaces is required in order to perform this test. 14.5.4 MTR 43 Voice Codec Testing Using VCTS MTR 43 Voice Codec Testing Using VCTS, evaluates the quality of AMBE+2 voice codec implementation in a terminal. Sub-Test Bit Exact End-to-End All Classes RM INT Table 14-30: Sub test specifications: Voice Codec Testing Using VCTS.
AAAA References A A.1 Applicable standards and RFC 99-137719-D [1] 3GPP TS 27.007 V4.7.0 (2010-03), 3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; AT command set for User Equipment (UE) (Release 4) [2] 3GPP TS 27.005 V4.2.
Applicable standards and RFC [14] Request for Comments: 3550, July 2003, RTP: A Transport Protocol for Real-Time Applications [15] Request for Comments: 854, May 1983, TELNET PROTOCOL SPECIFICATION [16] Universal Serial Bus Specification, revision 2.0 (also referred to as the USB Specification) [17] On-The-Go Supplement to the USB 2.0 Specification, Revision 1.0, Dec 18, 2001 [18] [SDM] BGAN System Definition Manual, Release 4.8.
2222 Glossary Glossary A AAGW ACARS Aircraft Gateway. A functional block inside the aeronautical class terminal. ACARS Aircraft Communication Addressing and Reporting System. A system for transmission of short messages between aeronautical class terminals and ground stations. ACM Antenna Control Module. ADC Analog-to-Digital Converter is a device that converts an analog signal into a digital signal.
Glossary BOM A bill of materials (BOM) is a list of the raw materials, sub-assemblies, intermediate assemblies, sub-components, parts and the quantities of each needed to manufacture a product. BPLT BGAN Physical Layer Tester. A tester that supports the testing of physical layer performance and User Terminals (UTs) implementing Inmarsat’s Broadband Global Area Network (BGAN), Fleet Broadband and Swift Broadband services. BPT BGAN Protocol Tester.
2222 eMLPP Enhanced Multi-Level Precedence and Preemption. A supplementary service used to deliver Safety Priority Voice Calls as defined by Inmarsat. ESD ElectroStatic Discharge is the sudden flow of electricity between two objects caused by contact, an electrical short, or dielectric breakdown. ESD can be caused by a buildup of static electricity by tribocharging, or by electrostatic induction.
Glossary ISDN Integrated Services Digital Network is a set of communication standards for simultaneous digital transmission of voice, video, data, and other network services over the traditional circuits of the public switched telephone network. ITSI Time-Slot Interchange, a technique used in switches in communications networks to allow multiple inputs and outputs to be interchanged on the same interface. L LDR Low Data Rate. LESP LES Packet (channel type), LES = Land Earth Station.
2222 Glossary O Open Systems Interconnection is a standard defined software model which holds a prescription of characterizing and standardizing the functions of a communications system in terms of abstraction layers. In the OSI model the communication functions are grouped into logical layers and a layer serves the layer above it and is served by the layer below it. OTG On-The-Go. Glossary OSI P PABX Private Automatic Branch Exchange. PAST Person Activated Self Test. PCB Printed Circuit Board.
Glossary Q QAM Quadrature Amplitude Modulation. QoS Quality of Service refers to several related aspects of telephony that allow the transport of traffic with special requirements on aspects of a connection. It comprises aspects of a connection relating to capacity and coverage of a network, for example guaranteed maximum blocking probability and outage probability.
Service Data Unit. SID Self Imposed Delay is a delay calculated by the BGAN mobile to achieve a correct transmit timing. The value depends on the position (on the earth) of the mobile and the satellite state vector describing the current position of the Inmarsat satellite (I4). SIP Session Initiation Protocol is a signaling protocol widely used for controlling communication sessions such as voice and video calls over Internet Protocol (IP).
on the internet. USIM Universal Subscriber Identity Module. W WEEE Glossary-8 Waste Electrical and Electronics Equipment.
3333 Index Index A C activation service, 12-2 waveform (BPLT mode), 12-3 waveform (IAI2 mode), 12-2 aeronautical shock, vibration, 5-7 AGC level, 6-37 antenna diversity, 9-7 application, 13-2 minimum, 13-3 typical, 3-3 application layer control interface, 8-7 application processor, 4-9 approvals, 3-11 assembling, 5-2 AT shell, 7-37 ATC activation, 6-52 ATC configuration, 9-9 calibration use case, 12-4 certifications, 3-11 circuit switched services, 7-6 Clock drift distribution, 6-30 configuration system
Index framing layer control interface, 8-5 network registration use case, 12-6 G O global beam search, 12-6 order number, 3-11 oscillator external reference, 9-8 output level normal tx, 6-50 variation, Tx, 6-51 H humidity, 3-5, 5-6 P I IAI2 mode waveform activation, 12-2 integration options, 3-3 integrator, 1-1, 4-5, 6-7 interface coaxial, reference clock, 5-19 control, 1-1 data, 1-1 overview, 4-3 Rx1 coaxial, 5-16 Rx2 coaxial, 5-17 syslog, 7-33 Tx coaxial, 5-18 interface description control, 5-20
3333 Index S U service activation, 12-2 settings, 6-72 shock, 3-6 aeronautical, 5-7 signal input (Rx2), 9-6 signal-to-noise reports, 6-30 SIM, 11-42 SIP registering, 7-6 Sky-scan check power, 6-52 check waveform, 6-53 software update, 7-33 software version, 1-1 Specifications, A-1 specifications humidity, 3-5, 5-6 shock, 3-6 temperature, 3-5, 5-6 vibration, 3-6 spectrum analyser, 11-32 configuration, 6-58 use case, 12-11 SPI timing RF control, 5-22 syslog interface, 7-33 use case calibration, 12-4 netw
99-137719-D www.cobham.com/satcom RMIntegratorsManualCover.
