Northern New York Border Patrol

Status
Not open for further replies.

JASII

Memory Capacity
Joined
Apr 29, 2006
Messages
3,073
Network Access Code

Conventional P25 systems don't support CTCSS tone or DCS code for access. Instead they use what is called a Network Access Code, or NAC. This is a 12 bit code that prefixes every packet of data sent (including voice packets).

The NAC is a feature similar to CTCSS or DCS for analog radios. That is, radios can be programmed to only break squelch when receiving the correct NAC. NAC's are programmed as a 3 digit hexadecimal code that is transmitted along with the digital signal being transmitted.

Project 25 - Wikipedia, the free encyclopedia

Project 25 (P25) or APCO-25 refer to a suite of standards for digital radio communications for use by federal, state/province and local public safety agencies in North America to enable them to communicate with other agencies and mutual aid response teams in emergencies. In this regard, P25 fills the same role as the European TETRA protocol, although not interoperable with it.
Contents

* 1 Suite of Standards Overview
o 1.1 History
o 1.2 Introduction
o 1.3 P25 Open Interfaces
o 1.4 P25 Phases
* 2 Conventional Project 25 Implementation
* 3 Adoption
* 4 See also
* 5 Notes
* 6 External links


Public safety radios have been upgraded from analog to digital since the 1990s because of the limitations of analog transmission, and also because of the technological advances and expanded capabilities of digital radio.

Project 25 audio
Play sound
NTIS-produced two-way radio audio. Sequence segments (1) original audio, (2) recovered analog FM with noisy signal, (3) recovered digital audio. — 199 KB
Problems listening to this file? See media help.

Varying user protocols and different public safety frequency bands, made it difficult for Public Safety to achieve interoperability and widespread acceptance among the public safety agencies. However, the lessons learned during the disasters that the United States faced in the past decade, have forced agencies to assess their requirements during a disaster when the basic infrastructure is in a state of failure. To meet the growing demands of public safety digital radio communications, the FCC at the directive of the Congress initiated an inquiry in 1988, to receive recommendations from users and manufacturers to improve the communication systems in existence.[1] Based on the recommendations, in October of 1989 APCO Project 25 came into existence in a coalition with APCO, National Association of State Telecommunications Directors (NASTD), National Telecommunications and Information Administration (NTIA), the National Communications System (NCS), National Security Agency (NSA) and the US Department of Defense (DoD), to find solutions that best serve the needs of public safety management.[1][2] In addition, a steering committee consisting of representatives from the above mentioned agencies along with FPIC, DHS Coast Guard and the Department of Commerce's the National Institute of Standards Technologies (NIST), Office of Law Enforcement Standards was established to decide the priorities and scope of technical development of P25.[2]
[edit] Introduction

Interoperable emergency communication is integral to initial response, public health, safety of communities, national security and economic stability. Of all the problems experienced during disaster events, one of the most serious problems is communication due to lack of appropriate and efficient means to collect, process and transmit important and timely information. In some cases, radio communication systems are incompatible and inoperable not just within a jurisdiction but within departments or agencies within the same community. [3] Non-operability occurs due to use of outdated equipment, limited availability of radio frequencies, isolated or independent planning, lack of coordination and cooperation between agencies, community priorities competing for resources, funding and ownership and control of communications systems. []404 Error - Page Not Found. Recognizing and understanding this need, Project 25 (P25) was initiated collaboratively by public safety agencies and manufacturers to address the issue with emergency communication systems. P25 is collaborative project to ensure that two-way radios are interoperable. The goal of P25 is to enable public safety responders to communicate with each other and, thus, achieve enhanced coordination, timely response, and efficient and effective use of communications equipment.[4] P25 was established to address the need for common digital public safety radio communications standards for First Responders and Homeland Security/Emergency Response professionals. TIA TR-8 facilitates such work through its role as an ANSI-accredited Standards Development Organization (SDO).
“ Project 25 (P25) is a set of standards produced through the joint efforts of the Association of Public Safety Communications Officials International (APCO), the National Association of State Telecommunications Directors (NASTD), selected Federal Agencies and the National Communications System (NCS), and standardized under the Telecommunications Industry Association (TIA)... The P25 suite of standards involves digital Land Mobile Radio (LMR) services for local, state/provincial and national (federal) public safety organizations and agencies...

P25 is applicable to LMR equipment authorized or licensed, in the U.S., under the National Telecommunications and Information Administration (NTIA) or Federal Communications Commission (FCC) rules and regulations.

Although developed primarily for North American public safety services, P25 technology and products are not limited to public safety alone and have also been selected and deployed in other private system application, worldwide.[5]

P25 equipment has also been selected for a railroad system, including rolling stock, personnel, and transportation vehicles.[citation needed]

P25-compliant systems are being increasingly adopted and deployed. Radios can communicate in analog mode with legacy radios, and in either digital or analog mode with other P25 radios. Additionally, the deployment of P25-compliant systems will allow for a high degree of equipment interoperability and compatibility.

P25 standards use the Improved Multiband Excitation (IMBE) vocoders which were designed by DVSI to encode/decode the analog audio signals.

P25 may be used in "talk around" mode without any intervening equipment between two radios, in conventional mode where two radios communicate through a repeater or base station without trunking or in a trunked mode where traffic is automatically assigned to one or more voice channels by a Repeater or Base Station.

The protocol supports the use of DES encryption (56 bit), 2-key Triple-DES encryption, 3-key Triple-DES encryption, AES encryption at up to 256 bits keylength, RC4 (40 bits, sold by Motorola as Advanced Digital Privacy), or no encryption.

The protocol also supports the ACCORDION 1.3, BATON, FIREFLY, MAYFLY and SAVILLE Type 1 ciphers.
[edit] P25 Open Interfaces

P25's Suite of Standards specify eight open interfaces between the various components of a land mobile radio system. These interfaces are:

* Common Air Interface (CAI) - standard specifies the type and content of signals transmitted by compliant radios. One radio using CAI should be able to communicate with any other CAI radio, regardless of manufacturer
* Subscriber Data Peripheral Interface - standard specifies the port through which mobiles and portables can connect to laptops or data networks
* Fixed Station Interface - standard specifies a set of mandatory messages supporting digital voice, data, encryption and telephone interconnect necessary for communication between a Fixed Station and P25 RF Subsystem
* Console Subsystem Interface - standard specifies the basic messaging to interface a console subsystem to a P25 RF Subsystem
* Network Management Interface - standard specifies a single network management scheme which will allow all network elements of the RF subsystem to be managed
* Data Network Interface - standard specifies the RF Subsystem's connections to computers, data networks, or external data sources
* Telephone Interconnect Interface - standard specifies the interface to Public Switched Telephone Network (PSTN) supporting both analog and ISDN telephone interfaces.
* Inter RF Subsystem Interface (ISSI) - standard specifies the interface between RF subsystems which will allow them to be connected into wide area networks

P25 Phases
A hand-held Project 25 radio used in US systems.

P25-compliant technology is being deployed in several phases:

* Phase 1

Phase 1 radio systems operate in 12.5 kHz analog, digital or mixed mode. Phase 1 radios use Continuous 4 level FM (C4FM) modulation for digital transmissions at 4800 baud and 2 bits per symbol, yielding 9600 bits per second total channel throughput. Receivers designed for the C4FM standard can also demodulate the "Compatible quadrature phase shift keying" (CQPSK) standard, as the parameters of the CQPSK signal were chosen to yield the same signal deviation at symbol time as C4FM while using only 6.25 kHz of bandwidth.

Vendors are currently shipping Phase 1 P25-compliant systems. These systems involve standardized service and facility specifications, ensuring that any manufacturers' compliant subscriber radio has access to the services described in such specifications. Abilities include backward compatibility and interoperability with other systems, across system boundaries, and regardless of system infrastructure. In addition, the P25 suite of standards provides an open interface to the radio frequency (RF) subsystem to facilitate interlinking of different vendors' systems.

* Phase 2

To improve spectrum utilization, Phase 2 is currently under development with concurrent work being done on 2-slot TDMA and FDMA (CQPSK) modulation schemes. Phase II will likely use the AMBE+2 vocoder to reduce the needed bitrate so that one channel will only require 4800 bits per second.

Significant attention is also paid to interoperability with legacy equipment, interfacing between repeaters and other subsystems, roaming capacity and spectral efficiency/channel reuse. In addition, Phase 2 work involves console interfacing between repeaters and other subsystems, and man-machine interfaces for console operators that would facilitate centralized training, equipment transitions and personnel movement.
[edit] Conventional Project 25 Implementation

Conventional P25 systems don't support CTCSS tone or DCS code for access. Instead they use what is called a Network Access Code, or NAC. This is a 12 bit code that prefixes every packet of data sent (including voice packets).

The NAC is a feature similar to CTCSS or DCS for analog radios. That is, radios can be programmed to only break squelch when receiving the correct NAC. NAC's are programmed as a 3 digit hexadecimal code that is transmitted along with the digital signal being transmitted.

Since the NAC is 3 digit hexadecimal number (12 bits), it gives 4096 possible NAC's for programming, which far exceeds all its analog counterparts combined. It should be noted that 3 of the possible NAC's have special meaning:

* 0x293 ($293) - the default NAC
* 0xf7e ($F7E) - a receiver set for this NAC will unsquelch on any NAC received
* 0xf7f ($F7F) - a repeater receiver set for this NAC will allow all incoming signals and the repeater transmitter will retransmit the received NAC.
 

radionerd13669

Useless Contributor
Joined
Jun 19, 2007
Messages
373
Location
Northern,New York
Where was anyone confused about NAC codes????

Conventional P25 systems don't support CTCSS tone or DCS code for access. Instead they use what is called a Network Access Code, or NAC. This is a 12 bit code that prefixes every packet of data sent (including voice packets).

The NAC is a feature similar to CTCSS or DCS for analog radios. That is, radios can be programmed to only break squelch when receiving the correct NAC. NAC's are programmed as a 3 digit hexadecimal code that is transmitted along with the digital signal being transmitted.

Project 25 - Wikipedia, the free encyclopedia

Project 25 (P25) or APCO-25 refer to a suite of standards for digital radio communications for use by federal, state/province and local public safety agencies in North America to enable them to communicate with other agencies and mutual aid response teams in emergencies. In this regard, P25 fills the same role as the European TETRA protocol, although not interoperable with it.
Contents

* 1 Suite of Standards Overview
o 1.1 History
o 1.2 Introduction
o 1.3 P25 Open Interfaces
o 1.4 P25 Phases
* 2 Conventional Project 25 Implementation
* 3 Adoption
* 4 See also
* 5 Notes
* 6 External links


Public safety radios have been upgraded from analog to digital since the 1990s because of the limitations of analog transmission, and also because of the technological advances and expanded capabilities of digital radio.

Project 25 audio
Play sound
NTIS-produced two-way radio audio. Sequence segments (1) original audio, (2) recovered analog FM with noisy signal, (3) recovered digital audio. — 199 KB
Problems listening to this file? See media help.

Varying user protocols and different public safety frequency bands, made it difficult for Public Safety to achieve interoperability and widespread acceptance among the public safety agencies. However, the lessons learned during the disasters that the United States faced in the past decade, have forced agencies to assess their requirements during a disaster when the basic infrastructure is in a state of failure. To meet the growing demands of public safety digital radio communications, the FCC at the directive of the Congress initiated an inquiry in 1988, to receive recommendations from users and manufacturers to improve the communication systems in existence.[1] Based on the recommendations, in October of 1989 APCO Project 25 came into existence in a coalition with APCO, National Association of State Telecommunications Directors (NASTD), National Telecommunications and Information Administration (NTIA), the National Communications System (NCS), National Security Agency (NSA) and the US Department of Defense (DoD), to find solutions that best serve the needs of public safety management.[1][2] In addition, a steering committee consisting of representatives from the above mentioned agencies along with FPIC, DHS Coast Guard and the Department of Commerce's the National Institute of Standards Technologies (NIST), Office of Law Enforcement Standards was established to decide the priorities and scope of technical development of P25.[2]
[edit] Introduction

Interoperable emergency communication is integral to initial response, public health, safety of communities, national security and economic stability. Of all the problems experienced during disaster events, one of the most serious problems is communication due to lack of appropriate and efficient means to collect, process and transmit important and timely information. In some cases, radio communication systems are incompatible and inoperable not just within a jurisdiction but within departments or agencies within the same community. [3] Non-operability occurs due to use of outdated equipment, limited availability of radio frequencies, isolated or independent planning, lack of coordination and cooperation between agencies, community priorities competing for resources, funding and ownership and control of communications systems. []404 Error - Page Not Found. Recognizing and understanding this need, Project 25 (P25) was initiated collaboratively by public safety agencies and manufacturers to address the issue with emergency communication systems. P25 is collaborative project to ensure that two-way radios are interoperable. The goal of P25 is to enable public safety responders to communicate with each other and, thus, achieve enhanced coordination, timely response, and efficient and effective use of communications equipment.[4] P25 was established to address the need for common digital public safety radio communications standards for First Responders and Homeland Security/Emergency Response professionals. TIA TR-8 facilitates such work through its role as an ANSI-accredited Standards Development Organization (SDO).
“ Project 25 (P25) is a set of standards produced through the joint efforts of the Association of Public Safety Communications Officials International (APCO), the National Association of State Telecommunications Directors (NASTD), selected Federal Agencies and the National Communications System (NCS), and standardized under the Telecommunications Industry Association (TIA)... The P25 suite of standards involves digital Land Mobile Radio (LMR) services for local, state/provincial and national (federal) public safety organizations and agencies...

P25 is applicable to LMR equipment authorized or licensed, in the U.S., under the National Telecommunications and Information Administration (NTIA) or Federal Communications Commission (FCC) rules and regulations.

Although developed primarily for North American public safety services, P25 technology and products are not limited to public safety alone and have also been selected and deployed in other private system application, worldwide.[5]

P25 equipment has also been selected for a railroad system, including rolling stock, personnel, and transportation vehicles.[citation needed]

P25-compliant systems are being increasingly adopted and deployed. Radios can communicate in analog mode with legacy radios, and in either digital or analog mode with other P25 radios. Additionally, the deployment of P25-compliant systems will allow for a high degree of equipment interoperability and compatibility.

P25 standards use the Improved Multiband Excitation (IMBE) vocoders which were designed by DVSI to encode/decode the analog audio signals.

P25 may be used in "talk around" mode without any intervening equipment between two radios, in conventional mode where two radios communicate through a repeater or base station without trunking or in a trunked mode where traffic is automatically assigned to one or more voice channels by a Repeater or Base Station.

The protocol supports the use of DES encryption (56 bit), 2-key Triple-DES encryption, 3-key Triple-DES encryption, AES encryption at up to 256 bits keylength, RC4 (40 bits, sold by Motorola as Advanced Digital Privacy), or no encryption.

The protocol also supports the ACCORDION 1.3, BATON, FIREFLY, MAYFLY and SAVILLE Type 1 ciphers.
[edit] P25 Open Interfaces

P25's Suite of Standards specify eight open interfaces between the various components of a land mobile radio system. These interfaces are:

* Common Air Interface (CAI) - standard specifies the type and content of signals transmitted by compliant radios. One radio using CAI should be able to communicate with any other CAI radio, regardless of manufacturer
* Subscriber Data Peripheral Interface - standard specifies the port through which mobiles and portables can connect to laptops or data networks
* Fixed Station Interface - standard specifies a set of mandatory messages supporting digital voice, data, encryption and telephone interconnect necessary for communication between a Fixed Station and P25 RF Subsystem
* Console Subsystem Interface - standard specifies the basic messaging to interface a console subsystem to a P25 RF Subsystem
* Network Management Interface - standard specifies a single network management scheme which will allow all network elements of the RF subsystem to be managed
* Data Network Interface - standard specifies the RF Subsystem's connections to computers, data networks, or external data sources
* Telephone Interconnect Interface - standard specifies the interface to Public Switched Telephone Network (PSTN) supporting both analog and ISDN telephone interfaces.
* Inter RF Subsystem Interface (ISSI) - standard specifies the interface between RF subsystems which will allow them to be connected into wide area networks

P25 Phases
A hand-held Project 25 radio used in US systems.

P25-compliant technology is being deployed in several phases:

* Phase 1

Phase 1 radio systems operate in 12.5 kHz analog, digital or mixed mode. Phase 1 radios use Continuous 4 level FM (C4FM) modulation for digital transmissions at 4800 baud and 2 bits per symbol, yielding 9600 bits per second total channel throughput. Receivers designed for the C4FM standard can also demodulate the "Compatible quadrature phase shift keying" (CQPSK) standard, as the parameters of the CQPSK signal were chosen to yield the same signal deviation at symbol time as C4FM while using only 6.25 kHz of bandwidth.

Vendors are currently shipping Phase 1 P25-compliant systems. These systems involve standardized service and facility specifications, ensuring that any manufacturers' compliant subscriber radio has access to the services described in such specifications. Abilities include backward compatibility and interoperability with other systems, across system boundaries, and regardless of system infrastructure. In addition, the P25 suite of standards provides an open interface to the radio frequency (RF) subsystem to facilitate interlinking of different vendors' systems.

* Phase 2

To improve spectrum utilization, Phase 2 is currently under development with concurrent work being done on 2-slot TDMA and FDMA (CQPSK) modulation schemes. Phase II will likely use the AMBE+2 vocoder to reduce the needed bitrate so that one channel will only require 4800 bits per second.

Significant attention is also paid to interoperability with legacy equipment, interfacing between repeaters and other subsystems, roaming capacity and spectral efficiency/channel reuse. In addition, Phase 2 work involves console interfacing between repeaters and other subsystems, and man-machine interfaces for console operators that would facilitate centralized training, equipment transitions and personnel movement.
[edit] Conventional Project 25 Implementation

Conventional P25 systems don't support CTCSS tone or DCS code for access. Instead they use what is called a Network Access Code, or NAC. This is a 12 bit code that prefixes every packet of data sent (including voice packets).

The NAC is a feature similar to CTCSS or DCS for analog radios. That is, radios can be programmed to only break squelch when receiving the correct NAC. NAC's are programmed as a 3 digit hexadecimal code that is transmitted along with the digital signal being transmitted.

Since the NAC is 3 digit hexadecimal number (12 bits), it gives 4096 possible NAC's for programming, which far exceeds all its analog counterparts combined. It should be noted that 3 of the possible NAC's have special meaning:

* 0x293 ($293) - the default NAC
* 0xf7e ($F7E) - a receiver set for this NAC will unsquelch on any NAC received
* 0xf7f ($F7F) - a repeater receiver set for this NAC will allow all incoming signals and the repeater transmitter will retransmit the received NAC.
 

nycap

Member
Joined
Mar 13, 2008
Messages
196
i hear that. thats kind of a long post for people that understand what p25 is. but thanks anyways dude :)
 

ecps92

Member
Joined
Jul 8, 2002
Messages
15,041
Location
Taxachusetts
Thanks for the trashing of my monthly allotment of bits and bytes. :evil:

If you need to know what a NAC is try the RR WIKI with a link

The question that was posted was "What NAC?" not "What is a NAC?"

I was asking from the OP for the NAC he was getting on a particular frequency.

The NAC is a feature similar to CTCSS or DCS for analog radios. That is, radios can be programmed to only break squelch when receiving the correct NAC. NAC's are programmed as a 3 digit hexadecimal code that is transmitted along with the digital signal being transmitted.
 

Sprint

Member
Joined
Mar 16, 2004
Messages
68
Location
Kingston, Ontario
We've logged a few new active freq.

165.2375 it is P25 and may be the DATa ch.

162.2375 P25 NAC 301

162.785 P25 NAC 301

170.100 NAC 301


in the " clear " voice heard...
 

ecps92

Member
Joined
Jul 8, 2002
Messages
15,041
Location
Taxachusetts
165.2375 CBP Primary - NET-01 Repeater or TAC-01 Simplex [common]
however in some congested areas this might be a different NET-## with a non standard input.

162.2375? - Bears more monitoring. $301 points towards CBP,...but then..

162.7850 ? maybe 162.7875 or 162.7750 - again $301 points towards..

170.1000 - sound like a Repeater? or input.???
CBP Net-31 as a Repeater - many others as an input

We've logged a few new active freq.

165.2375 it is P25 and may be the DATa ch.

162.2375 P25 NAC 301

162.785 P25 NAC 301

170.100 NAC 301


in the " clear " voice heard...
 

ocscan

Member
Joined
Dec 19, 2002
Messages
361
Location
Ottawa, On
From Ottawa, about 45mi. north of Ogdensburg NY, I am hearding Clear and Encrypted P25 on 165.2375mhz. Unit numbers are in the 200 series. Nothing heard yet on the other frequencies listed above.
 

Sprint

Member
Joined
Mar 16, 2004
Messages
68
Location
Kingston, Ontario
Interesting...I believe there used to be a BP station located right there on US Route 3 or 11 ?

My plan is to upgrade into a LP gain antenna with hopes that will allow me to reach out a bit further.

Do you think that's simply a repeater off the Buffalo office ?
 

WatnNY

Database Admin
Database Admin
Joined
Dec 19, 2002
Messages
1,211
Location
Living The Dream In Tennessee
165.2375 has always been US Customs and very strong in Northern NY with repeaters in Watertown, NY and somewhere near Ogdensburg, NY.

163.6250 R $301 and now
163.7250 R Unk

163.625 is the Watertown, NY Border Patrol Repeater.
163.725 is the Fulton/Oswego, NY Border Patrol repeater.

Mike
 

Sprint

Member
Joined
Mar 16, 2004
Messages
68
Location
Kingston, Ontario
Have you ever heard the boats or air units ? I'm wondering if DEA uses their comms ?

We're starting to hear 170.100 with a decent sig here in Kingston .
 

Sprint

Member
Joined
Mar 16, 2004
Messages
68
Location
Kingston, Ontario
163.925

We've logged 163.925 for a while now . It sounds like speech inversion and does not register with NAC. S2 from this location.

Any ideas ?
 

WatnNY

Database Admin
Database Admin
Joined
Dec 19, 2002
Messages
1,211
Location
Living The Dream In Tennessee
163.625 had several transmissions this morning that were all encrypted or P25 - I didn't have the 996 up and running, but picked the transmissions up on the 780.

Mike
 

nycap

Member
Joined
Mar 13, 2008
Messages
196
We've logged 163.925 for a while now . It sounds like speech inversion and does not register with NAC. S2 from this location.

Any ideas ?

One of the challenges of monitoring fed bands in this area is that you have to filter out what’s coming from the Canadian side. If I hear French or speech inversion, then it’s not federal and I lock it out.
 

Sprint

Member
Joined
Mar 16, 2004
Messages
68
Location
Kingston, Ontario
From this location we don't copy any french but do hear a lot of business traffic. Tow, courier and misc business activity.

Can you copy much Fed activity on 380 - 420 ? I can copy Drum on 380 now.
 

nycap

Member
Joined
Mar 13, 2008
Messages
196
based on what youve said is guess that 163.9250 is a cab company from your side. Federal LMR is 406.1-420.
 

Sprint

Member
Joined
Mar 16, 2004
Messages
68
Location
Kingston, Ontario
New logs

we've managed tonight to capture a few new freqs and NAC

165.2875 NAC 355

165.8750 NAC 355 & NAC 357

interesting...some '' in the clear "
 

nycap

Member
Joined
Mar 13, 2008
Messages
196
165.2875 is ATF. Their ussually in the clear.

customs air ops on 165.8750; but in analog over vermont way.
 

ecps92

Member
Joined
Jul 8, 2002
Messages
15,041
Location
Taxachusetts
Odd, as pointed out 165.2875 is BATFE, but that's the wrong NAC .

Keep an eye/ear on that one. :wink:

165.8750 $357 is BP somewhere North of Watertown NY
the $355 NAC on that one is interesting as well [Not reported before]


we've managed tonight to capture a few new freqs and NAC

165.2875 NAC 355

165.8750 NAC 355 & NAC 357

interesting...some '' in the clear "
 

ocscan

Member
Joined
Dec 19, 2002
Messages
361
Location
Ottawa, On
Today from Ottawa (40 miles north of the NY/Ontario Border, I am getting alot of encrypted P25 on 163.625mhz NAC $355. Also traffic on 168.8500mhz NAC $358.
 
Last edited:
Status
Not open for further replies.
Top