interoperation
status messaging only, the aim of ODINI is to support all functionalities which are important to end-users of mission- critical radio networks. A real-life example of this scenario is cross-border operation
by public safety offi cers. When an off ender crosses the border during a car chase, the police can continue communicating whilst driving into the foreign country. Obviously, national policy should allow this type of scenario, but with the focus on international collaboration to combat crime, there is certainly a trend to permit such operations.
Solution based on IP ODINI aims at supporting these scenarios by means of an open solution. Although some interoperability solutions currently exist, they are often too limited in their functional scope, are based on proprietary solutions, or are based on obsolescent technologies. ODINI is ambitious in respect of supporting diff erent
scenarios and providing a wide range of functionalities. However, the focus is on simplicity by eliminating the unnecessary mechanisms often found in telecommunication standards. In addition, ODINI is based on existing, proven, IP networking standards which eliminate the need to defi ne and validate the lower layer protocols. Currently, ODINI fully supports the tactical patch
scenarios for group calls. Individual calls and the scenarios for expanding coverage and migration to other networks will be supported by protocol extensions. It must be noted that implementation of ODINI is not
limited to one air interface protocol only: networks with diff erent air interfaces (TETRA, Tetrapol, APCO-25, DMR) can also be interconnected by means of ODINI. In the longer term, ODINI will also provide
interoperability between devices operating on IP-enabled mobile networks. Today, these networks are not robust enough for mission-critical applications.
Individual call Group call
Site" A2
MS A1
Site" A1
But with the implementation of fi ne-grained Quality-of-
Service, for example within the WiMAX and LTE standards, it is expected that TETRA functionality can be made available on terminals without sacrifi cing call setup delay and robust operation. In principle, ODINI is already capable of this, but further
defi nition of typical TETRA services over IP through ODINI will be necessary to provide identical services in order to emulate the rich functionality of TETRA.
An ODINI ecosystem ODINI can be regarded as a middle-layer protocol supporting diff erent scenarios which embody one common requirement: mission-critical communications. Currently this market is dominated by companies
promoting proprietary solutions. To avoid adding another proprietary solution to the scenarios listed here, Rohill has decided to take a dramatically diff erent approach: to publish the ODINI protocol with no restrictions on disclosure. Open-source software will be made available to interested parties in order to stimulate deployment of ODINI. T e rationale behind this approach is simple. It is the
most eff ective method of opening markets which are currently tightly controlled by a few large suppliers, as well as creating an environment in which best-of-class products and services can be combined and re-used in multiple projects. T e ODINI ecosystem is based on commercial off -the-
shelf (COTS) products in combination with software-based solutions from third-party suppliers. System gateways are necessary to make a third-party infrastructure compatible with the ODINI protocol. By means of the system gateway, it is possible to support one or more scenarios for network interconnection. Supporting multiple scenarios often requires access to multiple interfaces in the third-party radio network.
MS B2 MS A2
Site" B1
Site" B3
MS B1
Site" A3
MS A3
Site" B2
Site" B4
SwMI A
32
IP network
SwMI B
Migration to another network: ODINI
aims to support all network functions important to users
TE TRA TODAY Issue 2 February - April 2011
Page 1 |
Page 2 |
Page 3 |
Page 4 |
Page 5 |
Page 6 |
Page 7 |
Page 8 |
Page 9 |
Page 10 |
Page 11 |
Page 12 |
Page 13 |
Page 14 |
Page 15 |
Page 16 |
Page 17 |
Page 18 |
Page 19 |
Page 20 |
Page 21 |
Page 22 |
Page 23 |
Page 24 |
Page 25 |
Page 26 |
Page 27 |
Page 28 |
Page 29 |
Page 30 |
Page 31 |
Page 32 |
Page 33 |
Page 34 |
Page 35 |
Page 36 |
Page 37 |
Page 38 |
Page 39 |
Page 40 |
Page 41 |
Page 42 |
Page 43 |
Page 44