Transcript Teltronic Conference 2005 - Beyond The TETRA Technology

1st Ireland TETRA Conference - TETRA MoU Association
Dublin, 13th April 2005
Beyond the TETRA Technology
Beyond the TETRA Technology
TETRA MoU Association Conference
Introduction
Teltronic, 2005
Introduction (I)
The context
 The technology is just the way to provide the user with a
certain service, not the end itself.
 Users don’t normally speak the language of the technology,
and so we need to be able to understand their needs and to look
for the way to give them a solution.
 For a complete solution, the degree of satisfaction experimented
by the user depends on the quality of service they feel,
independently of the technology that supports the application.
Teltronic, 2005
Introduction (II)
What we will offer in the presentation
 The way to provide TETRA terminals with extra added value to
make easier the development of advanced applications.
 The main keys of flexibility, scalability and connectivity to
allow choosing the best option for your TETRA network topology.
 Study cases based on real situations where TETRA needs to
satisfy strong user requirements.
Teltronic, 2005
Introduction (III)
What we expect to achieve
 To demonstrate -once again- that TETRA represents the best
option for professional radio communications today.
 To open your minds towards new ways to take benefit of such a
powerful technology, also being aware of its limits and the way to
overcome them.
 To provide the keys to you for optimal decision making in your
present and future investments in TETRA products.
If you still don’t believe in TETRA,
you will starting today !
Teltronic, 2005
Introduction (IV)
 Presentation overview
INTRODUC
TION
Teltronic, 2005
TERMINAL
NETWOR
K
SUMMAR
Y
Beyond the TETRA Technology
TETRA MoU Association Conference
The Terminal
Driving your applications to the limit
Teltronic, 2005
Beyond the TETRA Technology
TETRA MoU Association Conference
The Terminal
Index of contents
• The role of the terminal in a system
• Improving the terminal capabilities
• Examples of customised scenarios
Teltronic, 2005
The role of the terminal in a system (I)
 Which are the kind of elements normally requested
to solve a complete application?
Multiple audio interfaces
• Microspeaker
• In-vehicle hands-free kit
• 600Ω balanced interface
• Audio recording output
• Ambience listening mic input
Extended I/O capabilities
?
• External PTT (foot-switched) input
• Event-controlled outputs
• Emergency signal input
Data transmission & control
• External access to data transmission services
Integration with other
communication
peripherals
• GPS receiver
• GSM transceiver
• Analog radio transceiver
Teltronic, 2005
• Remote radio unit control protocol
MMI customised access
• User logging
• Shortcuts to user services
• Software customisation at application level
• Customised user front-ends
The role of the terminal in a system (II)
 Is there a way to optimise these kinds of extra
requirements?
?
YES !
APPLICATION ELEMENTS
Peripheral
#1
External
peripherals
USER
Peripheral
#n
Audio
interface
Customised
MMI
TETRA
radio unit
External
I/O
TETRA terminal
…by integrating into the TETRA terminal part of those elements
that normally are required for such advanced scenarios.
Teltronic, 2005
Beyond the TETRA Technology
TETRA MoU Association Conference
The Terminal
Index of contents
• The role of the terminal in a system
• Improving the terminal capabilities
• Examples of customised scenarios
Teltronic, 2005
TETRA + GPS (I)
 Some ways to improve the classical AVL (Automatic
Vehicle Location) solution

GPS information packed
in smaller messages: More
efficient in use of bandwidth.
GPS info
SDS
type 4
TETRA MS
GPS
TETRA SwMI
GPS info
CONTROL
UNIT
PEI
Teltronic, 2005
USER
GPS receiver integration in
TETRA terminals: Single
TETRA + GPS devices.


LINE
DISPATCHER
STATIONS
Methods to decide about the way
and the timing to send the GPS
information: It also makes the
application more efficient in use of
system resources.
TETRA + GPS (II)
+
GPS
=
Single
terminal
message format
Standard NMEA 0183 v2.01 RMC message
SDS-T4  68 or 70 bytes (without/with TL)
Shortened GPS info (less
resolution)
SDS-T3  8 bytes
Confined area GPS
info
SDS-T2  4 bytes
GPS info (*)
• Latitude
• Longitude
• Position age
• Course
• Speed
• Time
• Position validity
• GPS receiver status
(*) some parameters can appear optionally according to
the message format
size
 GPS messages
management strategy
• by request from the
AVL control centre,
• by timeout, every
programmed time
intervals,
• by distance threshold
in a programmable value,
• automatic sending
during emergency calls.
Teltronic, 2005
TETRA + GSM
 Some reasons to a dual TETRA+GSM terminal
 The possibility of communication for mobile users that often
need to leave the home coverage area increases their level of
service anywhere.
 A single MMI for TETRA and GSM operation makes easier
the user interaction.
 A compact solution reduces complexity in installations and
avoids the user managing two separate communication devices.
+
Teltronic, 2005
=
Single
terminal
Interfacing the TETRA terminal
 Some ways to enhance the usability on the terminal
 Customising the MMI
• by including specific user interaction procedures adapted to certain
circumstances of use,
• by developing special user front-ends to better fit the different scenarios of
use and installation.
 Increasing the strength of the PEI
• by incorporating additional commands for complete interaction with
external control applications,
• by selecting which services are managed through the PEI and which ones
are controlled from the MMI.
 Expanding the external interaction mechanisms
• by the use of input/output control signals associated to certain events.
Teltronic, 2005
Beyond the TETRA Technology
TETRA MoU Association Conference
The Terminal
Index of contents
• The role of the terminal in a system
• Improving the terminal capabilities
• Examples of customised scenarios
Teltronic, 2005
Advanced vehicular configuration (I)
 USUAL REQUIREMENTS
- Half-duplex and duplex voice calls.
- Status and short data transmission.
- Remote database and file access.
- GPS-based vehicle location system.
Teltronic, 2005
Advanced vehicular configuration (II)
 Example: CONFIGURATION STRUCTURE
PC vehicular unit
Loudspeaker
MMI front-end
Hands-free mic
Foot
switch
Fist microspeaker
PTT
Teltronic, 2005
Motorbike adapted equipment (I)
 USUAL REQUIREMENTS
- Half-duplex and duplex voice calls.
- Status and short data transmission.
- Outdoor operation (dust & water
protection, high audio, noise cancellation).
- Simplest user interaction.
- GPS-based location system.
Teltronic, 2005
Motorbike adapted equipment (II)
 Example: CONFIGURATION STRUCTURE
Helmet audio
system
PEI & audio
PTT on handlebars
Battery
Outdoor speaker
Teltronic, 2005
Bus on-board equipment (I)
 USUAL REQUIREMENTS
- Half-duplex and duplex voice calls.
- Status and short data transmission.
- Vehicle sensors transmission.
- MMI integrated on driver’s dashboard.
- Interaction with passenger information system.
- GPS-based location system.
Teltronic, 2005
Bus on-board equipment (II)
 Example: CONFIGURATION STRUCTURE
TETRA MS
Bus
driver’s
MMI
- PTT
- Emergency button
- Call request
Ambience
listening
microphone
Control unit
Telemetry
sensors
PEI
Bus driver’s
audio system
Hands-free
audio kit
Audio
interface
Passenger
information
system
engine,
speed,
doors...
control
Billing
system
data
DISPLAY
Other
peripherals
Handset
Teltronic, 2005
Railways & underground train equipment (I)
 USUAL REQUIREMENTS
- Half-duplex and duplex voice calls.
- Status and short data transmission.
- Dual MMI console integrated on driver’s dashboards.
- Interaction with passenger information system.
- Interaction with on-board train computer.
- Integration of multiple communication subsystems.
Teltronic, 2005
Railways & underground train equipment (II)
 Example: CONFIGURATION STRUCTURE
MMI
console
Display
LED
indicators
Keypad
CONTROL
MODULE
Handset
Communications rack
Auxiliary
buttons
Hands free
audio system
CONTROL MODULE
VHF
analog
radio
TETRA
radio
unit
to TETRA antenna
to VHF antenna
AUDIO INTERFACE
to MMI console #n
Teltronic, 2005
to train’s
control system
to passenger
audio system
Railways & underground train equipment (III)
 Example: INSTALLATION DETAILS
MMI
console
Communications rack
(TETRA + analog VHF)
Overview of
communication
devices
MMI
console
Train’s main
control system
Teltronic, 2005
Beyond the TETRA Technology
TETRA MoU Association Conference
The Network
A new world of flexibility and scalability
Teltronic, 2005
Beyond the TETRA Technology
TETRA MoU Association Conference
The Network
Index of contents
• Introduction
• Transport
• Redundancy
• Scalability
• Connectivity
Teltronic, 2005
Introduction to the network (I)
NEBULA is the TETRA infrastructure by Teltronic. It has been
designed over a star configuration topology.
Teltronic, 2005
NEBULA ACRONYMS:
SCN: Switching Control Node
SBS: Site Base Station
Introduction to the network (II)
 A flexible topology provides the customer with different alternatives to
address the main topics of every system architecture design: transport,
redundancy, scalability and connectivity.
TRANSPORT:
Customers could already have an existing
transport network and they would like to reuse
it with the new TETRA system.
SBS
Link
SBS
SCN
IP
network
SBS
REDUNDANCY:
The only way to guarantee the lowest service
gap in case of faliure of any element in the
system.
SCALABILITY:
Early and low-cost mechanisms to upgrade
and expand the system are highly valuable.
Transport
Connectivity
Teltronic, 2005
Scalability
Redundancy
CONNECTIVITY:
The system oftenly needs to be connected to
other external systems and/or applications.
Beyond the TETRA Technology
TETRA MoU Association Conference
The Network
Index of contents
• Introduction
• Transport
• Redundancy
• Scalability
• Connectivity
Teltronic, 2005
Transport (I)
 Synchronous links:
V.35 link: Standard link in transport environments. Access
to PDH, SDH, microwaves.
Bandwidth: 64 Kbps up to 2 Mbps.
G.703/G.704: [E1 or T1]: Standard link in transport
environments. Access to PDH, SDH, microwaves. Circuit
connection to other standardised systems.
Bandwidth: 64 Kbps per slot, frame structure up to 2 Mbps.
BRI - PRI [ISDN]: Access through public networks.
Bandwidth BRI (Basic Rate Interface): 128 Kbps.
Bandwidth PRI (Primary Rate Interface): 2 Mbps.
Teltronic, 2005
Transport (II)
 Asynchronous links - Layer 2:
LAN links (Layer 2 - Ethernet links):
LAN (Corporate local area networks) :
- Always through switches (instead HUB).
- Ethernet rings (Rapid Spanning tree, 802.1w).
Bandwidth: 10 Mbps, 100 Mbps, 1 Gbps.
WiFi / WiMAX:
- 2.4 GHz, 5.4 GHz (with or without license)
Bandwidth: From 1Mbps up to over 54Mbps.
Optical Fiber (using optical backbones):
- Solutions like HyperRing.
Bandwidth: 100 Mbps, 1Gbps...
Teltronic, 2005
Transport (III)
 Asynchronous links - Layer 2:
SBS
SBS
SCN
WiFi
Connection
Standard Office Local Area
Network
Ethernet Switches
SBS
Optical Fiber
LAYER2 SYSTEM ACCESS:
: Ethernet connections
: Wireless connections
: Optical Fiber connections
Teltronic, 2005
Fiber
Access
70 Km
Ethernet Switch
Fiber
Access
Transport (IV)
 Asynchronous Links - Layer 3:
IRB (Integrated Routing and Bridging): Point-to-point link between two
routers through WAN connection with FR (Frame Relay).
The use of DLCI (Data Link Connection Identifier) in FR allows dividing
the bandwidth for the TETRA system and corporate communications.
VPN/MPLS (Multi Protocol Labelling Switching): Using layer 2 labels it is
possible to manage the QoS of the layer 3 packets.
xDSL / NetLAN: Access points distributed around the world.
Depending of the bandwidth required is recommended to use NetLAN
connections. These are not introducing the payload packet through the
Internet world.
Teltronic, 2005
Transport (V)
 Asynchronous Links - Layer 3:
• VPN / MPLS connections
• Dedicated Line (Frame Relay)
NetLAN
• NetLAN (not Internet access)
• xDSL (access through Internet)
FR
System links must ensure:
 Guaranteed bandwidth
• Control channel requires 16 Kbps
• Traffic channel requires 16 Kbps
 Minimum transport delay
 Delimited jitter
 Quality of Service (QoS)
Teltronic, 2005
ADSL
Beyond the TETRA Technology
TETRA MoU Association Conference
The Network
Index of contents
• Introduction
• Transport
• Redundancy
• Scalability
• Connectivity
Teltronic, 2005
Redundancy (I)
 Redundancy is a strong requirement for any professional
communication network:
A TETRA SYSTEM MUST BE REDUNDANT on:
BSR: Base Stations.
CNC: Switching Control Node Processor (redundant by two main units).
LINKS: Must be redundant in case of a fault in transport system.
PATHS: Different paths must be considered to connect the SCN from the SBS.
Physical Connections: Cables and hardware drivers can also fail, therefore
these must be duplicated.
Teltronic, 2005
Redundancy (II)
 Redundancy strategies must be applied to any critical part
within the system:
Synchronous
World
SBS1
BSR
LAN
Asynchronous
World
SNI
G.703/G.704
E1 Link
Ethernet
Switch Redundant
Ethernet
Switch
Redundant
WAN
ISDN
E1 Link
SNI S/T
BRI Link
SNI
G.703/G.704
CNC
LAN
Ethernet
Switch
Teltronic, 2005
Redundant
Physical Connections
Redundant
Ethernet
Switch
SNI S/T
SCN (Switching Control Node)
Beyond the TETRA Technology
TETRA MoU Association Conference
The Network
Index of contents
• Introduction
• Transport
• Redundancy
• Scalability
• Connectivity
Teltronic, 2005
Scalability
 Systems must be designed to support upgrades with the minimum
impact over the working network. Both software and hardware
upgrades are expected to be supported.
 Software upgrades (Increasing functionality):
• Background FTP to upgrade functionality.
• The system must be continuously working.
• Secondary memory bank is required.
 Hardware upgrades (Expanding the network topology):
• Increasing network dimension or redundancies.
• Plug and Play.
• Hot swap connection.
Teltronic, 2005
Beyond the TETRA Technology
Teltronic Conference on Professional Mobile Communication
The Network
Index of contents
• Introduction
• Transport
• Redundancy
• Scalability
• Connectivity
Teltronic, 2005
Connectivity (I)
 General connectivity concepts in NEBULA
N2A: (NIIA) NEBULA IP Interface Access
TDP: TETRA Dispatcher Protocol
Standard IP Services
(PDP TETRA Services)
N2A
TETRA
Dispatcher
Services
TCP
UDP
TDP
VoIP (voz)
Teltronic, 2005
Telnet
FTP
http
smtp
TCP
UDP
 (Simplex, Duplex, Group

REGISTER AND CALL
CONTROL

MONITORING

INCLUSION / LISTENING /
TERMINATION

DGNA
calls, Status, SDS)
RTP
RTCP
Connectivity (II)
 Voice communication management (Dispatching)
SBS NEBULA
FIREWALL
SWITCH
Client SBS
Line Dispatcher 1
SNI
SCN NEBULA
SNI
SNI
GATEWAYRDSI
VoIP
GATEWAYRDSI
SWITCH
VoIP
VoIP (SCN RTP / RTCP)
XML (NMS) TDP (SCN Monitoring, Calls, PTT)
CNC
NMS Server
Line Dispatcher Server
FIREWALL
Client SCN
Line Dispatcher 1
Backbone
Corporate Network
GATEWAYRDSI
ISDN
Client SCN
Line Dispatcher n
PHYSICAL CONNECTION between Line Dispatcher stations and NEBULA
Teltronic, 2005
Beyond the TETRA Technology
TETRA MoU Association Conference
Summary
Teltronic, 2005
TETRA is a mature technology
Over 10 years
with TETRA
standard
Robustness
and
performance
already
demonstrated
Demonstrated
multi-vendor
scenarios
mature
technology
Hundreds
of
references
worldwide
It is the time to start thinking more and more on the customer
needs and their solutions than in the technology itself.
Teltronic, 2005
Maximising the user satisfaction
 In the road towards killer applications
 TETRA terminals can play a more relevant role on applications by
integrating them with complementary technologies and customising
the way to interact with the external elements.
 On the network side, flexibility+scalability+connectivity
mechanisms guarantee the feasibility almost in any solution
required.
 Suitable design strategies optimise the overall system efficiency.
Application providers should consider that.
 Manufacturers could adapt their products to better fit the users
needs for certain special scenarios, always within the
interoperability scope.
Teltronic, 2005
Thinking beyond TETRA
1
TETRA can now be considered as a mature and stable technology. There is
a lot of positive feedbacks from the real world. The TETRA toolbox is ready.
2
The user DOES NOT speak normally in TETRA language. We ALL
(manufacturers, application developers, system integrators, network operators)
need to learn their language.
3
Teltronic, 2005
toolbox
Common
language
USER SATISFACTION
…thinking
Beyond the TETRA Technology
…we will continue working to try to make your life easier.
Thank you very much for
your attention!
Further information on the
Web:
www.tetramou.com
www.teltronic.es
www.etsi.org