NXDNTM Specification Overview

Level 1Version 1.2

Issued : January 19, 2012

JVC KENWOOD Corporation

Icom Incorporated

Note : NXDN is the trademark of JVC KENWOOD Corporation and Icom Incorporated.

2

1. Contents

1. Contents2. Purpose3. Copyright and Intellectual Property 4. Use Disclaimer5. Scope of this Document6. Items Discussed7. NXDNTM Compliance Certification8. Revision Record for this Document

P.1 P.2 P.3 P.4 P.5 P.6 ～ 35P.36 P.37

3

2. Purpose

• This document provides a brief overview of the NXDNTM common air interface protocol and call features related to the supporting IP network systems which are shared under a technology and cooperative development agreement between JVC KENWOOD Corporation and Icom Incorporated.

• The contents of this document are disclosed without limitation for the purpose of expanding NXDNTM with interested parties.

4

3. Copyright and Intellectual Property

• This document and its contents are copyright protected and are the property of JVC KENWOOD Corporation and Icom Incorporated.

• Certain technologies discussed in this document are the intellectual property of JVC KENWOOD Corporation and/or Icom Incorporated.

• Use of any intellectual property contained in this document is not permitted unless authorized by JVC KENWOOD Corporation or Icom Incorporated.

5

4. Use Disclaimer

• Alterations or deletions of any item in this document may be done without obligation of any prior notice provided no agreement to the contrary exists between JVC KENWOOD Corporation and Icom Incorporated and the party this document is disclosed to.

• If the receiving party sustains tangible or intangible damages from the use or consideration of use of the contents, including any subsequent alterations or deletions, neither JVC KENWOOD Corporation or Icom Incorporated shall be held liable and accountable for any compensation for said damages.

6

5. Scope of this Document

• A brief overview of the specifications pertaining to:

a) Wireless communication systems for the Americas’ private land

mobile markets in the VHF, UHF and 800MHz frequency bands and,

b) the FDMA method for 6.25kHz or 12.5kHz bandwidth and,

c) the system using this communication protocol

7

6. Items Discussed

The following items are specified in this document.6-1 Defined Services Voice Call Services (Group, Individual, etc.) Data Call Services (Long Data, Short Data, etc.) Supplemental Services (Status Call, Emergency, Encryption, etc.) Trunked System Services (Registration, Roaming, etc.)6-2 Conventional System6-3 Trunked System6-4 Channel Parameters6-5 Vocoder6-6 Concept of Channel Definition (Conv. & Type-C) Frame Structure Concept Voice Frame Structure (Conv. & Type-C) Data Frame Structure (Conv. & Type-C) Control Channel Frame Structure (Type-C) Random Access on Control Channel (Type-C) Link Time of Group Call (Type-C)6-7 Concept of Channel Definition (Type-D) Voice Frame Structure (Type-D) Data Frame Structure (Type-D) Link Establishment Frame Structure (Type-D) Link Time of Group Call on Home Repeater (Type-D)

"Conv.": Conventional"Type-C": Type-C Trunking"Type-D": Type-D Trunking

8

6-1-1. Defined Services in Conventional System

Service Direct via Repeater

Voice Service

Unaddressed Voice Call (using RAN) Mandatory Mandatory

Group Voice Call Std. Option Std. Option

Individual Voice Call Std. Option Std. Option

Interconnect Voice Call n/a Std. Option

Data Service

Data Call (Group, Individual) Std. Option Std. Option

Short Data Call (on Control Channel) n/a n/aSimultaneous Data Call Std. Option Std. Option

SupplementaryService

Status Call Std. Option Std. Option

Emergency Call & Alert Std. Option Std. Option

Remote Control (Stun, etc.) Std. Option Std. Option

ESN Validation Std. Option Std. Option

Late Entry Mandatory Mandatory

Encryption Std. Option Std. Option

Mandatory : Mandatory Service Std. Option : Standard Option Service

9

6-1-2. Defined Services in Trunked System

Service Type-CType-D

Multi Site Single Site

Voice Service

Group Voice Call Mandatory Mandatory Mandatory

Individual Voice Call Mandatory Mandatory Mandatory

Interconnect Voice Call Std. Option Std. Option Std. Option

Data Service

Data Call (Group, Individual) Std. Option Std. Option Std. Option

Short Data Call (on Control Channel) Std. Option n/a n/aSimultaneous Data Call Std. Option Std. Option Std. Option

SupplementaryService

Status Call Std. Option Std. Option Std. Option

Emergency Call & Alert Std. Option Std. Option Std. Option

Remote Control (Stun, etc.) Std. Option Std. Option Std. Option

ESN Validation n/a Std. Option Std. Option

Late Entry Mandatory Mandatory Mandatory

Encryption Std. Option Std. Option Std. Option

System Service

Registration Mandatory Mandatory n/a

Roaming Mandatory Mandatory n/a

Over the Air Update n/a Mandatory n/a

Authentication Std. Option Mandatory Std. Option

Composite Control CH Std. Option n/a n/a

Call Queuing Std. Option n/a n/a

2nd Home Repeater n/a Std. Option Std. Option

Priority Monitor Std. Option Std. Option Std. Option

Failsoft Std. Option n/a n/a

Mandatory : Mandatory Service Std. Option : Standard Option Service

10

6-1-3. Voice Call Services

Unaddressed Voice Call (RAN Only)A Subscriber Unit (SU) or console can provide a Voice Call intended for calls to Subscriber Units with same RAN (Radio Access Number), without using any identifier for selective call.

Group Voice CallA Subscriber Unit (SU) or console can provide a Group Voice Call intended for calls to multiple Subscriber Units. According to group settings, this can provide a Conference Call for two-way voice calls between selected groups or a Broadcast Call for one-way voice calls to the selected Group.

Individual Voice CallA Subscriber Unit (SU) or console can provide an Individual Voice Call intended for calls to a specified Subscriber Unit.

Interconnect CallTrunking Repeater Sites (TRS) or Conventional Repeater Sites (CRS) can be connected to telecommunication networks (PSTN/ PSDN), which can offer individual or group voice calls between Subscriber Units and the PSTN/PSDN.

11

6-1-4. Data Call Services

Data CallA Subscriber Unit (SU) or console can transfer data (e.g. text, or AVL data) to an individual or group members. A Data Call can be sent to one specified Subscriber Unit or a Broadcast Data Call to a group can be selected.

Short Data CallA Subscriber Unit (SU) or console can transfer a small amount of data to individual or group members. The size of transmission data has a limit because the control channel of a Trunking Repeater Site (TRS) is used. A Short Data Call can be sent to one specified Subscriber Unit or a Broadcast Short Data Call to a group can be selected.

Simultaneous Data CallA Subscriber Unit (SU) or console can transfer data at a low speed simultaneously with a voice call during Individual Voice Calls or group voice calls. This function enables data transmission similar to a Short Data call during a voice call.

12

6-1-5. Supplementary Services (1)

Status Call (Status Notice and Status Inquiry)A Subscriber Unit (SU) or console can transfer a simple and fixed message to individual or group members. There are 2 types of usages: preconfigured particular status messages and user defined free-style status messages. Also, there are two methods to send or get a status: Status Notice is a function that an SU sends a status message as necessary, and Status Inquiry is that an SU sends a status message when it receives an inquiry command message.

Emergency Call & AlertWhen a Subscriber Unit (SU) is in emergency condition, an emergency voice call or emergency status message can be sent to an individual or group members.

Remote Control (Stun/Revival/Kill, Monitor)A Subscriber Unit (SU) or console can set a specified Subscriber Unit to an inoperative state remotely. There are three kinds of states, Stun, Revival, and Kill, and a Subscriber Unit or console can initiate any of these if enabled. Furthermore, an SU or console can let a specified Subscriber Unit transmit remotely (Remote Monitor).

13

6-1-6. Supplementary Services (2)

ESN Validation

Each Subscriber Unit (SU) has a unique Electronic Serial Number (ESN) that is written in its memory device at a factory. A validation facility such as a console can authorize an SU using ESN and prevent unauthorized usage of the system.

Late Entry

Late Entry enables those Subscriber Units that access a call after a group call is established to automatically join the group call. This scenario could occur when a Subscriber Unit enters the region from outside the coverage area, or if a Subscriber Unit is turned ON after a group call is established.

Encryption

Contents of voice communication and data communication may be encrypted. Three encryption modes are available; Scramble Mode (15-bit key), DES Mode (56-bit key) and AES Mode (256-bit key).

14

6-1-7. Trunked System Services (1)

Registration

In a Trunked Radio System, a Subscriber Unit searches for another control channel when the unit is turned ON, or if the receive signal becomes low in standby mode, to select another Trunking Repeater Site with better signal conditions and the Unit ID may be registered in the new Trunking Repeater Site.

Roaming

In a Trunked Radio System that has multiple Trunking Repeater Sites (TRS), the location registration is updated and traced in Trunking Repeater Sites when a Subscriber Unit moves around sites. Trunking Repeater Sites broadcast the neighboring site information to transfer the Subscriber Units appropriately.

Over the Air Update

In Trunked Radio System, Trunking Repeater Sites (TRS) can inform SU over the air, when a new site is added.

15

6-1-8. Trunked System Services (2)

Authentication

Using a unique Electronic Serial Number (ESN) given to each Subscriber Unit, a Trunking Repeater Site can authorize a Subscriber Unit and prevent unauthorized usage of the system.

Composite Control Channel

At a Trunking Repeater Site, if a new transmission request is placed when all traffic channels in the site are busy, a control channel may be assigned temporarily as a traffic channel to enable communication.

Call Queuing

At a Trunking Repeater Site, if an SU sends a new call request when all traffic channels in the site are busy, the TRS sets the SU queuing state and may keep the SU waiting until the call request is processed.

16

6-1-9. Trunked System Services (3)

Secondary Home Repeater

In a Trunked Radio System, SU registers the Trunked Repeater (TR) called Home Repeater. If the line control of the TR becomes inoperative because of some trouble, another TR becomes Secondary Home Repeater which performs line control temporarily.

Priority Monitor

In the state where an SU is making a group call on a traffic channel, when a priority Group Call begins on other traffic channel or a call request of Individual Call addressing the SU occurs, the SU drops out of the Group Call and can participate in the priority Group Call or the Individual Call.

Failsoft

If a Trunking Repeater Site (TRS) fails and loses its channel control, the TRS behaves equivalent to a conventional repeater by repeating the received signal so that it provides minimum service to SUs and allows communications between SUs within the service area.

17

6-2. Conventional System

16 bit Unit ID, uniquely definable for each system– Identifiable approx. 65,000 units per system

16 bit Group ID, uniquely definable for each system– Identifiable approx. 65,000 groups per system

6 bit Radio Access Number (RAN)– CTCSS/CDCSS like operation

Similar operation to an analog system possible– Group call using only RAN (CTCSS/CDCSS like)– Selective call using RAN and Unit/Group ID (CTCSS + DTMF like)

• Even if in Selective Call, Late Entry function works properly – Community Repeater operation with RAN

4800bps/6.25kHz and 9600bps/12.5kHz available

18

6-3-1. Trunked System

Two types of trunked systemType-C; Centralized control method with the dedicated control channelType-D; Distributed control method without the dedicated control channel

System Configuration– Support Multi Site Configuration– Support Multi System Configuration

19

6-3-2. Type-C Trunked System

Features– Using a dedicated control channel transmitting continuously,

• Suitable for the sites with many channels and the systems with many sites• Efficient packet switched data mode• Rapid control channel hunting and site roaming

– Exclusive channel license necessary

System Identification– 24-bit Location ID for identifying each system and each site– 6-bit Site Code for identifying each site

Subscriber Identification– 16-bit Unit ID --- Identifiable approx. 65,000 units per system– 16-bit Group ID --- Identifiable approx. 65,000 groups per system

Available Mode– 4800bps/6.25kHz and 9600bps/12.5kHz available

20

6-3-3. Type-D Trunked System

Features– All of channels available as traffic channel– Efficient channel use in a small number of channels – Less channel interference– Shared channel license available

System Identification– 19-bit System ID for identifying each system– 8-bit Site Code for identifying each site

Home Repeater & Subscriber Identification– 5-bit Home Repeater/Prefix for identifying each sub-group– 11-bit Unit ID --- Identifiable approx. 2,000 units per prefix– 11-bit Group ID --- Identifiable approx. 2,000 groups per prefix

Available Mode– 4800bps/6.25kHz available

21

6-4. Channel Parameters

Dual Data Rates and Dual Channel Bandwidths– 4800bps & 9600bps, 6.25kHz BW & 12.5kHz BW

Common Parameters– Channel Access FDMA/SCPC– Vocoder AMBE+2TM

– Modulation 4 Level FSK– TX BB Filter Root Raised Cosine(=0.2) + sinc– RX BB Filter Root Raised Cosine(=0.2) + 1/sinc

Parameters for 6.25kHz Channel (Mask E)– Data Rate 4800bps– Frame Length 80ms– Deviation ±1050Hz@±3symbol 、

±350Hz@±1symbol Parameters for 12.5kHz Channel (Mask D)

– Data Rate 9600bps– Frame Length 40ms– Deviation ±2400Hz@±3symbol 、

±800Hz@±1symbol

2L FSK+1- 1

4L FSK

+3+1- 1- 3

CDCSS and LTR

NXDNTM & C4FM

22

6-5. Vocoder

AMBE+2TM from DVSI Inc.– 3600bps EHR (Enhanced Half Rate)

• Voice; 2450bps, FEC; 1150bps– 7200bps EFR (Enhanced Full Rate)

• Voice; 4400bps, FEC; 2800bps

4800bps mode can use only the EHR 9600bps mode can use the EHR or optional EFR

P25 Vocoder Compatibility – P25 Phase 1 uses 7200bps IMBETM which is has less quality than

EFR– EFR has a backward compatibility to IMBETM

23

6-6-1. Concept of Channel Definition

3 Physical Channels (same meaning as “Carrier” or “Frequency”)– RCCH (RF Control Channel for Type-C Trunking)– RTCH (RF Traffic Channel for Type-C Trunking)– RDCH (RF Direct Channel for Conventional)

9 Functional Channels (transferred information dependent) – VCH (Voice Channel for Vocoder data)– SACCH (Slow Associated Control Channel)– FACCH1 (Fast Associated Control Channel 1)– UDCH (User Data Channel)– FACCH2 (Fast Associated Control Channel 2)– BCCH (Broadcast Control Channel)– CCCH (Common Control Channel)– UPCH (User Packet Channel)– LICH (Link Information Channel)

5 functional channels for RTCH and RDCH

3 functional channels for RCCH

1 common functional channel

Conv. & Type-C

24

6-6-2. Frame Structure Concept

FSW LICH different usage every mode (voice, data, …)3481620

384 bits

80ms@4800bps

4800bps and 9600bps modes have the same frame structure One frame always has a 384 bit length regardless of the modes

– 4800bps: 384 bits / 4800 bps = 80 ms frame length– 9600bps: 384 bits / 9600 bps = 40 ms frame length

FSW (Frame Sync Word) and LICH in the head of frame– FSW is the fixed 20 bit pattern for synchronization– LICH indicates the kind of radio channel and functional channel– Subscriber determines the area following LICH by decoding LICH

FSW LICH different usage every mode (voice, data, …)16 34820

40ms@9600bps

Common

25

6-6-3. Voice Frame Structure in 4800bps

FSW LICH SACCH VCH VCH VCH VCH72 72 72 7216 6020

384 bits80ms@4800bps

Voice Only

Data with Voice FSW LICH SACCH FACCH1VCH VCH

RTCH (trunk) and RDCH (conv.) have the same frame structure AMBE+2TM converts each 20ms voice signal to digitized data

– 3600bps x 20ms = 72bit, 4 VCH are included in 80ms frame Using “steal”; 2 VCH change to FACCH1, simultaneous Data

w/Voice function is available SACCH always attaches VCH for sending the control data

– Group/Unit ID and many kind of control information FACCH1 is used for Simultaneous Data (Data w/Voice) and

Status Call and many kinds of control messages

Stealing

Conv. & Type-C

26

6-6-4. Voice Frame Structure in 9600bps

Compatible frame structure with 4800bps, less design complexity In 9600bps mode, more flexible operation is available

– Using FACCH1, faster Data w/ Voice with no voice quality degradation– Using EFR Vocoder, higher voice quality is available– If FACCH1 is not needed, intermittent Tx and Rx allows for longer

battery Life

40ms, half the 4800bps mode

FSW LICH SACCH VCH VCH VCH VCH72 72 72 7216 6020

80ms, 384 bits

80ms@4800bps

FSW LICH SACCH VCH VCH VCH VCH40ms@9600bps FSW LICH SACCH FACCH1 FACCH1

residual time of 40msgives more functionality

Conv. & Type-C

27

6-6-5. Data Frame Structure

Data frame sends user data (e.g. text, AVL, image data, etc) In a Long Data Call, user data is divided into many packets, and

each packet is divided into blocks again, then one block is carried by one UDCH.

FACCH2 is used for Status Call and some control messages

FSW LICH UDCH or FACCH23481620

384 bits

80ms@4800bps40ms@9600bps

Conv. & Type-C

28

6-6-6. Control Channel Frame Structure

Inbound frame has a 96 bit guard time not to transmit– Guard time is 20ms@4800bps or 10ms@9600bps. This timing does not

require the severe ramping time for TX APC circuitry Outbound frame has an E field and a Post field

– E (collision control) field is for random access control– Post field is for faster frame synchronization

FSW LICH CAC (CCCH or UPCH)2521620

384 bits80ms@4800bps 40ms@9600bps

FSW LICH CAC (BCCH or CCCH or UPCH) E Post

Guard96

3001620 24 24

Inbound

Outbound

Type-C

29

6-6-7. Random Access on Control Channel in 4800bps

CCCH

80ms

One random access slot identifies one frame Subscriber transmits at 40ms offset to outbound frame Typically the subscriber sends one message using one slot

– Registration, Call request, Status, etc When sending Short Data, the subscriber can use plural slots

– CCCH for a single message, UPCH for plural messages

Inbound

Outbound CCCH CCCH CCCH CCCH

CCCH

CCCH

Unit #1

Unit #2

20ms guard time40ms offset

Type-C

30

6-6-8. Link Time of Group Call in 4800bps

Group Call Sequence (E field handling is omitted)– User presses the PTT, then– Subscriber sends Call Request using random access on RCCH, then– Controller assigns RTCH and Subscriber receives RTCH ASSIGN, then– Subscriber moves to the assigned RTCH and starts transmission, then– User hears the Proceed Tone and begins to talk

Typical Link Time is 320 ms in 4800 bps (similar to LTR system)

Inbound RCCH

CCCH CCCH

REQ

40ms

ASSGN CCCH

RX

Inbound RTCH

Outbound RCCH

PTT

40ms

CCCH CCCH

Voice Voice Voice

320ms typically

CCCH

80ms

Type-C

31

6-6-9. Link Time of Group Call in 9600bps

CCCH

40ms

Typical Link Time is 220 ms in 9600 bps– Call sequence is the same as that of 4800bps– Inbound frame offset is 0 ms– However Tx <-> Rx switching time are still 40ms

This link time is one of the shortest Link Time in LMR systems

Inbound RCCH

CCCH

REQ

ASSGNCCCH CCCH CCCH

RX

VoiceInbound RTCH

Outbound RCCH CCCH

PTT

220ms typically

Type-C

32

6-7-1. Concept of Channel Definition

1 Physical Channels (same meaning as “Carrier” or “Frequency”)– RTCH2 (RF Traffic Channel 2)

6 Functional Channels (transferred information dependent) – VCH (Voice Channel for Vocoder data)– SCCH (Signaling Control Channel)– FACCH1 (Fast Associated Control Channel 1)– UDCH2 (User Data Channel 2)– FACCH3 (Fast Associated Control Channel 3)– LICH (Link Information Channel)

6 functional channels for RTCH2

Type-D

33

6-7-2. Voice Frame Structure

FSW LICH SCCH VCH VCH VCH VCH72 72 72 7216 6020

384 bits80ms@4800bps

Voice Only

Data with Voice FSW LICH SCCH FACCH1VCH VCH

RTCH2 have the same frame structure as RTCH/RDCH except SCCH

Using “steal”; 2 VCH change to FACCH1, simultaneous Data w/Voice function is available

SCCH always attaches VCH for sending the control data– Group/Unit ID and many kind of control information

FACCH1 is used for Simultaneous Data (Data w/Voice) and Status Call and many kinds of control messages

Stealing

Type-D

34

6-7-3. Data Frame Structure

FSW LICH SCCH UDCH2 or FACCH328816 6020

384 bits

80ms@4800bps

Data frame sends user data (e.g. text, AVL, image data, etc) In a Long Data Call, user data is divided into many packets and

each packet is divided into blocks again, then one block is carried by one UDCH2.

FACCH3 is used for Status Call and some control messages

Type-D

35

6-7-4. Link Establishment Frame Structure

FSW LICH SCCH FACCH1 Guard144 14416 6020

384 bits80ms@4800bps

Inbound

Outbound FSW LICH SCCH NFACCH1 Post

Frames during link establishment are similar to the frame structure of Voice Frame

Inbound frame has a 144 bit guard time not to transmit Outbound frame has a Null field and a Post field

– E (collision control) field is for random access control– Post field is for faster frame synchronization

144 12016 6020 24

Type-D

36

6-7-5. Link Time of Group Call on Home Repeater

Group Call Sequence – User presses the PTT, then– Subscriber sends Call Request using random access, then– Subscriber receives Call Response from Home Repeater indicating

receive success, then– Subscriber starts transmission on Home Repeater, then– User hears the Proceed Tone and begins to talk

Typical Link Time is 400 ms (similar to LTR system)

Inbound

Outbound

50ms

RX

PTT

70ms

Voice Voice

400ms typically

80ms 70ms

REQ

RESP RESP NNRX

Type-D

37

7. NXDNTM Compliance Certification

• Compliance Certification for NXDNTM compatible products produced and/or sold by NXDN Forum members are defined as follows;

1) Developers must apply to Technical Working Group according to

the NXDNTM Compliance Certification Procedure document provided to

the Forum members.

2) Compliance Certification includes application examination,

conformance tests and other requirements.

3) The use of the NXDNTM logo mark is permitted upon successful

completion of the Compliance Certification.

38

8. Revision Record for this Document

1) August 3, 2007 　 Version 1.0

2) February 5, 2008 Version 1.1

3) January 19, 2012 Version 1.2