eUPG670 Device Overview

1.The eUPG670 enables the interworking of an eLTE system and a narrowband system (such as TETRA) through built-in vehicle-mounted terminals. It also provides interconnection functions, such as group voice calls, group selection, and SMSs.

   The eUPG670 uses built-in vehicle-mounted terminals to provide interconnection functions, such as group voice calls and group selection.

Currently, the built-in vehicle-mounted terminals MTM5200, MTM5400, GM338, and MTM800E apply to the eUPG670 and provide the following functions:

• Configuring the interconnection between eLTE groups and narrowband groups, such as TETRA
• Managing channel resources of the built-in vehicle-mounted terminals, such as the volume, working mode, and group mapping
• Displaying the subscribed group and current group information of the built-in vehicle-mounted terminals
• Enabling P2P short message exchanges between the eLTE system and a narrowband system such as TETRA (available only in Signaling control mode).
  NOTE:

  Limited by TETRA network, concurrent operations of short message and group call are not recommended.

The eUPG670 does not support forced release and emergency group calls.

Floor preemption between broadband and narrowband systems is supported on the condition that the third-party system supports floor preemption judgment. The eUPG670 transmits and receives only floor messages of two parties. In this case, floor judgment is performed in the dispatching system of both parties. You are advised to retain the disabling state of floor preemption for the third-party system by default and enable the function as required.

Product Structure

This section describes the software and hardware structures of the eUPG670.

Software Structure

The eUPG670 uses the same software platform as the eAPP610 and also uses ACE-based (ACE is short for adaptive communication environment) self-development software platform.

• The software subsystems provide a basic platform for further development, operating, deployment, commissioning, maintenance, and upgrade for the eUPG670.
• The ACE-based software subsystems can work with third-party software or run on another OS (Linux) to provide a service-oriented distributed message architecture, basic components, and O&M functions.

Figure 2-3 shows the software structure of the eUPG670.

Figure 2-3 Software structure

Hardware Architecture

• Appearance

  The eUPG670 is an indoor rack-mounted device with a 19-inch case-shaped structure and a height of 2 U. Figure 2-4 shows the appearance.

  Figure 2-4 Appearance of the eUPG670
  
• Internal structure

  The eUPG670 provides two slots for installing two built-in vehicle-mounted terminals, respectively. The eUPG670 uses cables to connect the inter-system vehicle-mounted terminals, x86 development board and its transfer board, power module, and RF ports, forming an independent working unit. The front panel can be uninstalled, facilitating the maintenance and commissioning of the inter-system vehicle-mounted terminal. In normal cases, the panel is not removed, to protect the vehicle-mounted terminals from damages or misoperations.

Interfaces and Protocols

This section describes interfaces and protocols used between the eUPG670 and internal devices, and between the eUPG670 and other NEs.

Table 2-2 External interfaces of the eUPG670 and protocols

Interconnected NE	Protocol	Description
Built-in vehicle-mounted terminal	Signaling or COR	Transmits voice data.
eAPP610	SIP and RTP	Enables communications based on the SIP protocol and the RTP protocol encapsulated by the gateway SDK.
eUDC660	RESTFUL	Pushes group-related data.
eOMC910	ZMQ	Manages the information report (versions and alarms).