Transcript 1.8 GPM Training Deck

MOTOTRBOTM
LINKED CAPACITY PLUS
MOTOROLA SOLUTIONS LEARNING
Motorola Public Document Classification, Dimetra IP Compact 3.0 to 4.1 Delta
July 2011
Module Name
1
LINKED CAPACITY PLUS VALUE PROPOSITION
“Connect More People, In More Locations, For Less”
Communicate to a large field force across a wide
area with a scalable, easy to use system…
•Wide Area Coverage
Links adjoining single sites across an IP Network
•High Capacity
Digital communication for up to 1200 users
using 12 voice paths per site across 5 sites
•Cost Effective
Does not require additional hardware
PAGE 2
LINKED CAPACITY PLUS OVERVIEW
 Combines all the benefits of IP Site Connect and Capacity Plus
 Adds CAPACITY to existing IP Site Connect (IPSC) systems
 Adds COVERAGE to existing Capacity Plus (Cap+) systems
 No central controller needed




Logic is managed in a distributed fashion like Cap+
Does not use a dedicated control channel
Resilient to channel interference
Suitable for shared channels
 Repeaters (Peers) / sites connected via an IPv4 based network like IPSC
 Linked Capacity Plus (LCP) requires more bandwidth than IPSC
 Consists of up to 5 sites
 Up to 6 trunked (voice and data) & 3 data revert repeaters per site
 Same number of repeaters per site not required
 Tolerates failures by design
 The Master repeater is the single point of failure, however this single point
of failure is limited only to the arbitration of IP addresses
PAGE 3
LINKED CAPACITY PLUS OVERVIEW
}=
A set of Single-Site Capacity Plus systems +
Physical connection like an IP Site System +
Some additional software
Linked Capacity Plus
Capacity Plus  Trunking
IP Site Connect 
Link Management,
Wide Area call processing
Additional Software 
Dynamically forms an IPSC between
the current Rest channels
1. Identifies the Rest channel
2. Combines the Call set-up
procedures (i.e. Arbitration + TRT)
Can use MTR3000 and/or 32MB DR
3000 repeaters (but NOT 8MB DR
3000 repeaters).
Site 1
Site 2
Site 3
BR 11
BR 21
BR 31
Master
BR 12
BR 22
BR 32
BR 13
BR 23
BR 33
BR 14
BR 24
System
Wide
Master
Switch
Switch
Switch
Router
Router
Router
WAN IP Network
Rest Channels
PAGE 4
LINKED CAPACITY PLUS OVERVIEW
Features
 Includes the following MOTOTRBO “special” features







Enhanced privacy
Transmit Interrupt
Digital telephone patch
GPS (including enhanced)
Data applications (ADP interfaces)
Option board
RDAC
 Includes the following trunking system features
 Selective site light-up:
 Dynamic for individual calls
 Static for talkgroup calls
 Automatic subscriber roaming
 Site restriction
PAGE 5
LINKED CAPACITY PLUS OVERVIEW
Features
 Supports up to 254 Local and Wide Area TALKGROUPS
 Local and Wide Area Talkgroups










The ID space for Talkgroups is limited to {1..254}
A customer can define some of these IDs (say “w”) as Wide Area
The remainder of the IDs are Local
Local Talkgroup IDs can be reused at different sites
Thus, total number of talkgroups = (254 – w) * s + w
(where “s” is the number of sites)
No local channels like IPSC
No local All Call Talkgroup
A Wide Area Talkgroup ID is associated with a set of sites
 Enables Statically defined Selective site “light up” for Talkgroup calls
A number of channels at each site can optionally be reserved for Wide Area
talkgroup calls.
All Wide Area talkgroup repeater configuration parameters are provisioned into
the Master repeater only.
PAGE 6
LINKED CAPACITY PLUS OVERVIEW
Features - Data
 LCP data is similar to Cap+…




Radio to Radio data is always on a trunked channel
Server to Radio data is always on a trunked channel
Radio to Server data is either on a trunked or data revert channel
Radios share the revert channels
 LCP data is similar to IPSC…
 Supports both local and wide area data revert channels
 A wide area / local setting is configured into all data revert repeaters
 A wide area data revert channel is formed by multiple data revert channels (one per
site) sharing a common Channel ID
 Initially, LCP supports server data via Control stations ONLY
 In the future, LCP will also support server data via the repeater IP interface
PAGE 7
LINKED CAPACITY PLUS OVERVIEW
Features - Data
Flexibility for configuring Data Revert Repeater Channel IDs.
Example System 1
Site 1 (Ch ID 33W)
Site -2 (Ch ID 33W) Site 3 (Ch ID 33W) Site 4 (Ch ID 33W)
Site 5 (Ch ID 33W)
Example System 2
Site 1 (Ch ID 33W) Site -2 (Ch ID 33W) Site 3 (Ch ID 33W)
Site 4 (Ch ID 35W)
Site 5 (Ch ID 35W)
Site 4 (Ch ID 47L)
Site 5 (Ch ID 47L)
Example System 3
Site 1 (Ch ID 33L)
Site -2 (Ch ID 33L)
Site 3 (Ch ID 43L)
PAGE 8
LINKED CAPACITY PLUS OVERVIEW
Features
LCP does not support…
 Priority Queuing of Calls
Requires a central controller
 Priority Monitor*
This is however supported for All Call and Emergency call
 Subscriber Access Control
Will however be supported in a release later this year
(* this is the ability for radios to leave a call in progress to join a higher priority call)
PAGE 9
LINKED CAPACITY PLUS OVERVIEW
System Loading
 For the purpose of the following:
 T = Total number of Radios supported by LCP system
 R = Number of Radios supported by Cap+ system
 N = Number of trunked channels at the smallest LCP site
 S = Number of LCP Sites
 W = Average number of Sites associated with Wide Area Talkgroups
 L = Number of Local calls as a fraction of the total number of calls
 A LCP system handles Local calls as efficiently as Cap+, therefore if all calls are Local, T =
the sum of the number of radios supported by each individual site.
 The number of radios supported by a given LCP site = the number of radios
supported by a Cap+ system having the same number of trunked channels.
 If there are Wide Area calls, T is estimated by first estimating R for a Cap+ system having
N trunked channels (note: Wide Area calls generally take 240ms longer to start).
 If all calls are Wide Area, T = R.
 If there are a mixture of both Local and Wide Area calls, T = R*S (L + (1-L)/W)
PAGE 10
LINKED CAPACITY PLUS OVERVIEW
 Requires a software upgrade of radios and repeaters
 Repeaters must have 32MB of flash memory
 Compatible with current and next generation MOTOTRBO radios
 Requires feature activation in the repeater




HKVN4108A
HKVN4063A
HKVN4109A
HKVN4070A
DR 3000 Full license key*
DR 3000 Incremental license key (from Cap+)
MTR3000 Full license key*
MTR3000 Incremental license key (from Cap+)
 New LCP compatible version of RDAC available
 GMVN5520F
RDAC CD
* The full LCP license does not support Cap+ channels, so if a repeater needs also to
support Cap+ channels then a Cap+ / Incr. LCP license combination should be
purchased instead.
PAGE 11
LINKED CAPACITY PLUS OVERVIEW
Backwards compatibility with Cap+
An old (non-upgraded) Cap+ radio will only operate on a single LCP site. However, its
ID must still be unique across all sites for the LCP system.
Site 1
Site 2
(1) Old radios can neither make nor
receive Wide Area Individual Calls
(2) Old radios can receive incoming audio
targeted to a Wide Area TG but can
not transmit audio to a Wide Area TG.
Compatible Individual calls
(1)
Old
Old
(1)
New
(1)
(2)
New
(2)
Compatible Group calls
Incompatible Calls
OldNew
Local TG
New
New
Wide Area
TG
PAGE 12
LINKED CAPACITY PLUS COMPONENTS
Complete System
TRNK CS
Site 1
BR 11
Site 2
BR 21
Site 3
BR 31
Master
BR 12
BR 22
BR 32
Conv CS
Conv CS
RDAC
PC1
BR 14
Router + Switch
BR 23
BR 24
LAN Network
BR 13
LAN Network
TRNK CS
Router + Switch
BR 33
BR 34
LAN Network
Rest Channels
System
Wide
Master
Router + Switch
WAN IP Network
Data Revert Repeaters
(Optional)
PAGE 13
LINKED CAPACITY PLUS COMPONENTS
The role of the “Master”
Rest Channels
Site 3
BR 31
Master
Conv CS
Conv CS
RDAC
PC1
BR 14
Router + Switch
BR 22
BR 23
BR 24
LAN Network
BR 13
LAN Network
TRNK CS
BR 12
System
Wide
Master
Router + Switch
BR 32
BR 33
BR 34
LAN Network
•Requires a static IP address which all
repeaters (via their configuration) need to be
aware of
•Introduces repeaters to each other
Site 2
•Is the single
of failure
Sitepoint
1
BR 21
TRNK CS
BR 11
Router + Switch
WAN IP Network
Data Revert Repeaters
(Optional)
PAGE 14
LINKED CAPACITY PLUS COMPONENTS
If the Master repeater fails…
The system continues to function
Additional repeaters, sites, or host PCs CANNOT be added to the system
A redundant repeater can be switched to act as a Master
PAGE 15
LINKED CAPACITY PLUS COMPONENTS
•Exchange “Keep Alive” messages
Rest Channels
•Use information to dynamically configure system
•Participate in selecting the next Rest Channel
2
•DistributeSite
the1voice/data payload to allSite
repeaters
TRNK CS
BR 11
BR 21
Site 3
BR 31
Master
BR 12
BR 22
BR 32
Conv CS
Conv CS
RDAC
PC1
BR 14
Router + Switch
BR 23
BR 24
LAN Network
BR 13
LAN Network
TRNK CS
Router + Switch
BR 33
BR 34
LAN Network
The role of a Repeater (Peer)
Router + Switch
WAN IP Network
Data Revert Repeaters
(Optional)
PAGE 16
LINKED CAPACITY PLUS COMPONENTS
Communication among repeaters
1) LCP repeaters at a given site use IP Limited Broadcast address (255.255.255.255)
messages to communicate among each other when managing (for example) the site’s Rest
Channel (note: Cap+ repeaters communicate with each other using multiple unicast
messages).
2) LCP repeaters at a given site are configured with a common Site IP Address (referred to as
the Rest Channel IP Address by the CPS) and the current Rest Channel repeater at the
site uses this Site IP Address when sending periodic Keep Alive messages to the other
sites.
3) At the start of a new call the source Rest channel repeater does not know which are the
current Rest channel repeaters at the other sites. The source Rest channel repeater
therefore sends one message to each Site IP Address associated with the call (note: the
source Rest channel repeater finds out from the Master repeater which Site IP Addresses
to use). When a repeater at a given site receives a Site IP address message, it rebroadcasts this message to the other repeaters at that site using the IP Limited Broadcast
address message (note: the repeater that receives the Site IP Address message will
normally be the Rest channel repeater unless the Rest channel has changed since the last
Keep Alive message was generated). The current Rest Channel repeater at the site then
responds to the Site IP address message. This mechanism enables all repeaters involved
in a call to learn which are the other repeaters (at the other sites) involved in the same call.
PAGE 17
LINKED CAPACITY PLUS BACK END NETWORK
•Repeaters at a site are connected over a LAN like
Rest Channels
Cap+
•Repeaters use an IP Limited Broadcast address to
communicate with all repeaters at its site
Site 2
Site 1
•Only LCP repeaters
should be present on the LAN
TRNK CS
BR 11
BR 21
Site 3
BR 31
Master
BR 12
BR 22
BR 32
Conv CS
Conv CS
RDAC
PC1
BR 14
Router + Switch
BR 23
BR 24
LAN Network
BR 13
LAN Network
TRNK CS
Router + Switch
BR 33
BR 34
LAN Network
LAN Network
Router + Switch
WAN IP Network
Data Revert Repeaters
(Optional)
PAGE 18
LINKED CAPACITY PLUS BACK END NETWORK
WAN IP Network
TRNK CS
Rest Channels
Site 1
BR 11
BR 21
Site 3
BR 31
Master
BR 12
BR 22
BR 32
Conv CS
Conv CS
RDAC
PC1
BR 14
Router + Switch
BR 23
BR 24
LAN Network
BR 13
LAN Network
TRNK CS
Router + Switch
BR 33
BR 34
LAN Network
•An IP Network is used for voice/data
communication between sites like IPSC
•Requires greater bandwidth (compared to IPSC)
from ISP provider
Site 2
Router + Switch
WAN IP Network
Data Revert Repeaters
(Optional)
PAGE 19
LINKED CAPACITY PLUS BACK END NETWORK
Router + Switch
TRNK CS
Rest Channels
Site 1
BR 11
Site 2
BR 21
Site 3
BR 31
Master
BR 12
BR 22
BR 32
Conv CS
Conv CS
RDAC
PC1
BR 14
Router + Switch
BR 23
BR 24
LAN Network
BR 13
LAN Network
TRNK CS
Router + Switch
BR 33
BR 34
LAN Network
All repeaters (and only the repeaters) at a
site must be behind a router and a switch
Router + Switch
WAN IP Network
Data Revert Repeaters
(Optional)
PAGE 20
LINKED CAPACITY PLUS BACK END NETWORK
Considerations
1) The Master repeater is the only repeater which must have a static IPv4 address, the other
repeaters (and RDAC applications) may have either static or dynamic IP IPv4 addresses.
2) Since LCP repeaters at a given site use IP Limited Broadcast address messages to
communicate among each other, then:
- All repeaters pertaining to a given site must be behind a single Ethernet Switch/Router
- This is because IP Limited Broadcast address messages never get forwarded by a
site’s router to the WAN.
- The only devices that can be on the site’s LAN are the repeaters pertaining to that site
(and any RDAC applications)
- This is because IP Limited Broadcast address messages (which are received by
all devices on the LAN) could have an undesired effect on other devices.
- Hairpinning routers generally* do not need to be used
- Again, this is because IP Limited Broadcast address messages never get
forwarded by a site’s router to the WAN.
*
A Hairpinning router must be used at a site if that site contains multiple LCP devices and
one of these devices is either a Master repeater or an RDAC application, since:
i. Peers need to address the Master repeater using its WAN address.
ii. An RDAC application communicates directly with repeaters (rather than using IP
Limited Broadcast address messages).
PAGE 21
LINKED CAPACITY PLUS BACK END NETWORK
Considerations
3) If no more than 3 repeaters per site need to be supported, then the “D Link EBR2310”
Ethernet Switch/Router should be sufficient.
4) For expanding the number of switch ports, the “HP Procurve 2510-24 (J9019B)” Ethernet
Switch can be used in conjunction with the EBR-2310 Router.
5) The CISCO ASA-5505 (8 port) Switch/Router can also be used.
6) For a customer LAN, no Public IP address is required if a Remote IP network connection is
not required from any other public network. If for example RDAC is required to be
connected from the Public system without using a VPN configuration, then one Public static
IP address is required.
7) Once the IP network is setup and rigorously tested (bandwidth analysis etc.), it is advisable
not to change or keep changing IP network configuration. Overall quality and reliability of
the LCP system is highly dependent upon a stable IP network.
8) Refer to the System Planner for details on how to calculate the bandwidth requirements of
the backend network.
PAGE 22
LINKED CAPACITY PLUS PROCEDURES
 All Start
 A Wide Area Talkgroup call only starts if channels are available at all associated sites
 Local calls can capture all the trunked channels at a site, leaving no channels
available for Wide Area Talkgroup calls. To overcome this, LCP allows a
configurable number of channels at each site to be reserved for Wide Area
Talkgroup calls.
 Call queuing is not supported, however a radio tries up to 3 times to setup a call
with random delays inserted in between each attempt.
 Selective Site Light Up for Individual Calls




An Individual call setup goes out on all sites where a channel is available.
These sites all attempt a high-speed handshake (called “RTR”) with the target
radio.
The site that succeeds with the high-speed handshake and the site where the
initiating radio is located remain in the call while the other sites drop out. If the
initiating and target radios are on the same site this leaves 1 site involved in the
individual call and if the initiating and target radios are on different sites this
leaves 2 sites involved in the individual call.
The high-speed handshake occurs concurrently with the call set-up, so no
additional delay.
PAGE
23
LINKED CAPACITY PLUS PROCEDURES
 Start of a Call
 “TRT” in Cap+ restricts the effect of collisions.
 “Arbitration” in IPSC ensures that all the sites select the same call.
 LCP improves and combines these two processes into a single process called “TR-ART”.
 This process can also allocate the channels for up to 5 concurrent calls (each
occurring at separate sites) in one arbitration.
 The Wide Area Call setup time for LCP is approximately 240 ms more than for Cap+
(this increases where more than 2 concurrent calls need to be allocated).
 The Local Call setup time for LCP is same as for Cap+.
 LCP supports Digital Telephone Patch Calls.
 A radio can receive an incoming telephone call on any site, however a radio can
only initiate an outgoing telephone call on a site connected to an APP (i.e. a
radio can not initiate a telephone call via an APP connected to a different site).
PAGE 24
LINKED CAPACITY PLUS PROCEDURES
Wide Area Group Voice Call
1. A radio starts a call on an idle Rest Channel
The radio transmits a burst over the air and waits for the response from the Rest Channel.
1
BR 11
BR 21
BR 31
BR 12
BR 22
BR 32
BR 13
BR 23
BR 33
Master
BR 34
BR 14
Site 1
Site 2
Switch
Router
Site 3
Switch
Router
Switch
Router
WAN IP Network
Note: If two or more radios at a site start calls at the same time their call starts will collide, the Rest Channel repeater may not
receive the transmission correctly and will not provide a response. If the radio does not get the response from the Rest Channel
repeater it will retry after a random delay.
PAGE 25
LINKED CAPACITY PLUS PROCEDURES
Wide Area Group Voice Call
2. When a burst is received the Rest Channel repeater
a.
b.
c.
Selects the next Rest channel (like Cap+) and informs the start of the call and the new Rest Channel to all
repeaters at the site.
Tells the radio its call is conditionally accepted, starts an “arbitration window” (the duration depends on
the inter-repeater delay) and asks the radio to wait for the final acceptance.
Invites the Rest Channels at the other sites to join the call (invitations sent using site common IP
addresses).
2b
BR 11
BR 21
BR 31
BR 22
BR 32
BR 23
BR 33
2c
BR 12
BR 13
2a
Master
BR 34
BR 14
Site 1
Site 2
Switch
Router
Site 3
Switch
Router
Switch
Router
WAN IP Network
Note: Each site has a common IP address. A message addressed to the common IP address is received by all the repeaters at the site.
PAGE 26
LINKED CAPACITY PLUS PROCEDURES
Wide Area Group Voice Call
3. When an invitation is received from the source repeater, the Rest Channel at the destination sites
a.
b.
c.
Select the next Rest channel and inform the start of the call and the new Rest Channel to all
repeaters at their sites.
Inform the non-participating radios the Rest Channel has changed.
Accepts or Rejects the invitation depending on the channel availability at its site.
BR 11
BR 21
BR 31
3c
BR 12
3b
BR 22
3a
3b
BR 32
3a
BR 13
BR 23
BR 33
Master
BR 34
BR 14
Site 1
Site 2
Switch
Router
Site 3
Switch
Router
Switch
Router
WAN IP Network
PAGE 27
LINKED CAPACITY PLUS PROCEDURES
Wide Area Group Voice Call
4. During the “arbitration window”, if the source repeater receives no rejections from the sites
associated with the talkgroup then it informs the source radio to start the call. If one or
more rejections are received, then the source repeater asks the source radio not to start the
call.
4
BR 11
BR 21
BR 31
BR 12
BR 22
BR 32
BR 13
BR 23
BR 33
Master
BR 34
BR 14
Site 1
Site 2
Switch
Router
Site 3
Switch
Router
Switch
Router
WAN IP Network
PAGE 28
LINKED CAPACITY PLUS PROCEDURES
Wide Area Group Voice Call
5. When permission is received to start a call
a.
b.
c.
The source radio transmits a voice header followed by a voice burst every 60ms.
The source repeater sends the header/bursts to all repeaters participating in the call.
The destination repeater transmits the received header/bursts over the air.
5a
BR 11
BR 21
BR 31
5b
BR 12
5c
BR 13
BR 22
5c
BR 23
BR 32
BR 33
Master
BR 34
BR 14
Site 1
Site 2
Switch
Router
Site 3
Switch
Router
Switch
Router
WAN IP Network
PAGE 29
LINKED CAPACITY PLUS PROCEDURES
Private Voice Call
Steps 1 to 4a of a Private Voice Call are the same as a Wide Area Group Voice Call.
4b. The destination repeaters ask the destination radio to respond by transmitting a query over the air.
4c. If the destination radio is present then it responds.
4d. If the destination repeater does not receive a response, it informs the source repeater it is not interested in
participating in the call.
4a
BR 11
BR 21
S
BR 31
4b
4d
BR 12
X
BR 22
4b
D
BR 13
BR 23
BR 32
4c
BR 33
Master
BR 34
BR 14
Site 1
Site 2
Switch
Router
Site 3
Switch
Router
Switch
Router
WAN IP Network
S: Source Radio
D: Destination Radio
PAGE 30
LINKED CAPACITY PLUS PROCEDURES
Private Voice Call
5. When permission is received to start a call
a.
b.
c.
The source radio transmits a voice header followed by a voice burst every 60ms.
The source repeater sends the header/bursts to at most one repeater (i.e. the repeater which did
not send a rejection).
The destination repeater transmits the received header/bursts over the air.
5a
BR 11
BR 21
S
BR 31
5b
BR 12
BR 22
5c
BR 32
D
BR 13
BR 23
BR 33
Master
BR 34
BR 14
Site 1
Site 2
Switch
Router
Site 3
Switch
Router
Switch
Router
WAN IP Network
S: Source Radio
D: Destination Radio
PAGE 31
LINKED CAPACITY PLUS PROCEDURES
Wide Area All Call
1. A radio starts a Wide Area All Call on an idle Rest Channel
Steps 1 to 4a are the same as a Wide Area Group Call.
1
BR 11
BR 21
BR 31
TG
TG
A
BR 12
BR 22
BR 32
BR 13
BR 23
BR 33
TG
E
E
Master
BR 34
BR 14
E
Site 1
Site 2
Switch
Router
Site 3
Switch
Router
Switch
Router
WAN IP Network
E : Radios participating in an Emergency Call
TG: Radios participating in a Talk Group Call
Note: LCP does not support Local All Call.
PAGE 32
LINKED CAPACITY PLUS PROCEDURES
Wide Area All Call
4b. The start of a Wide Area All Call is announced on the Traffic and Rest Channels of all sites
4c. All radios receiving non-emergency calls move to the channels where the Wide Area All Call is in
progress. These radios make a late entry into the Wide Area All Call.
4a
BR 11
BR 21
BR 31
BR 12
BR 22
BR 32
4b
4b
4b
BR 13
BR 23
BR 33
E
E
Master
BR 34
BR 14
E
Site 1
Site 2
Switch
Router
Site 3
Switch
Router
Switch
Router
WAN IP Network
E : Radios participating in an Emergency Call
PAGE 33
LINKED CAPACITY PLUS PROCEDURES
Phone Call (Radio to Phone)
LCP supports only Private Radio to Phone Calls (i.e. no Talkgroup Radio to Phone Calls).
A radio can only initiate a phone call at a site where there is at least one Phone Patch device.
1. A radio starts a Phone Call on an idle Rest Channel by transmitting a burst over the air
2. The Rest Channel provides the current status (i.e. busy or idle) of all “phone capable”
channels at the site.
1
P
BR 11
BR 21
BR 31
BR 12
BR 22
BR 32
2
P
Phone
Patch
BR 13
Phone
Patch
BR 14
P
BR 23
BR 33
Master
BR 34
Site 1
Site 2
Switch
Router
Site 3
Switch
Router
Switch
Router
WAN IP Network
P: Radio initiating a call to a phone
Note: If there is no idle phone capable channel at the site, the radio retries after a random delay
PAGE 34
LINKED CAPACITY PLUS PROCEDURES
Phone Call (Radio to Phone)
3. A radio moves to an idle phone capable channel and initiates a phone call.
4. The remaining steps are the same as for Private Voice Call.
BR 11
BR 21
BR 31
BR 12
BR 22
BR 32
P
BR 13
Phone
Patch
Phone
Patch
P
BR 23
BR 33
Master
BR 34
BR 14
Site 1
Site 2
Site 3
3
P
Switch
Router
Switch
Router
Switch
Router
WAN IP Network
P: Radio initiating a call to a phone
PAGE 35
LINKED CAPACITY PLUS PROCEDURES
Group Phone Call (Phone to Radio)
LCP supports both Private and Group Phone to Radio Calls.
1. When a phone call is received, the Phone Patch activates the “PTT Line”, and the repeater requests,
receives and verifies the DTMF digits.
2. The repeater checks for an idle slot, and if a slot is idle starts the call.
3. The source repeater invites the Rest Channels at the destination sites to join the call.
4. After the “arbitration window”, the Rest Channel announces the start of the phone call.
4
BR 11
BR 21
BR 31
P
4
4
BR 12
4
BR 22
P
BR 32
P
3
Phone
Patch
Phone
Patch
1
BR 13
BR 23
BR 33
Master
BR 34
BR 14
Site 1
Site 2
Switch
Router
Site 3
Switch
Router
Switch
Router
WAN IP Network
PAGE 36
Note: If there is no idle phone capable channel at the site, the radio retries after a random delay P: Radio initiating a call to a phone
LINKED CAPACITY PLUS PROCEDURES
Group Phone Call (Phone to Radio)
5. The participating radios at the source site moves from the Rest Channel to the Phone Channel.
6. The Rest Channels at the destination sites move.
7. The Non-participating radios move to the new Rest Channels.
BR 11
BR 21
BR 31
BR 12
BR 22
BR 32
P
Phone
Patch
BR 13
P
BR 23
BR 33
P
Phone
Patch
Master
BR 34
BR 14
Site 1
Site 2
Switch
Router
Site 3
Switch
Router
Switch
Router
WAN IP Network
P: Radio initiating a call to a phone
Note: If there is no idle phone capable channel at the site, the radio retries after a random delay
PAGE 37
LINKED CAPACITY PLUS PROCEDURES
Emergency Voice Call
1.
An emergency call starts just like a talkgroup call unless
a.
An Emergency Call to the same talkgroup is already in progress, in which case the call starts over the same
channels either politely (after interrupting the ongoing call) or impolitely.
A Rest Channel at a site is not idle, in which case the Rest Channel drops the ongoing call and participates in
the Emergency Call
b.
E
BR 11
BR 21
BR 31
BR 12
BR 22
BR 32
BR 13
BR 23
BR 33
S
BR 14
Site 1
Site 2
Site 3
BR 11
BR 21
BR 31
BR 12
BR 22
BR 32
BR 13
BR 23
BR 33
BR 14
Site 1
BR 34
BR 34
Site 2
This figure shows the
state before the
initiation of the
emergency call. A radio
a site 3 is sourcing an
interruptible call for the
emergency talkgroup.
This figure shows the
state after the initiation
of the emergency call by
a radio at site 1. Note
that the Rest channels
do not change and the
radio at site 3 has
stopped its
transmission.
Site 3
PAGE 38
LINKED CAPACITY PLUS PROCEDURES
Emergency Voice Call
User initiation
of Emergency
Yes
Move to Rest Channel

Radio on
Traffic
channel?

No


Emergency Call transmitted
over ongoing Emergency
Call because receiving
radios already on channel.
Yes
Emergency
Call for same
Talkgroup
already
active?

No
Emergency Call transmitted
on Idle Rest channel.
Yes
Rest Channel
Idle?
LCP only uses impolite channel access for
emergency calls (where necessary).
When a repeater detects an impolite call it
updates the system call status to the new call.
LCP frees up channels at associated sites (if
necessary) during an emergency call setup.
The start of an emergency call is announced over
all busy channels at all associated sites, thereby
allowing radios to leave their current calls and
join the emergency call (where applicable).
After setting up an emergency call, if there are no
free channels left at a site then the busy rest
channel shifts to a channel where there is a non
emergency call in progress (thus ensuring that
one emergency call does not clear down another
emergency call).
No
Emergency Call transmitted
impolitely over busy Rest
channel.
No
Call on busy
Rest Channel
interruptible?
Yes
Transmit interrupt used to
stop ongoing call.
Emergency Call then
transmitted on Idle Rest
channel.
PAGE 39
LINKED CAPACITY PLUS PROCEDURES
Roaming




To minimise the amount of Beacon signalling
 An LCP (Roaming) Beacon is appended to every 5th Cap+ (Lost Signal Detection) Beacon
To facilitate faster scanning
 The Rest Channels at all the sites synchronise their Beacons
 The LCP (Roaming) Beacons at a given site contain a list of Rest Channel IDs for that site’s
neighbouring sites
Radios use the list of Rest Channel IDs for a site’s neighbouring sites to determine which channels to scan
when trying to roam using either Passive or Active Site search
The list of neighbouring
sites for each site is
CPS Configurable Interval
5 * Cap+ Beacon Interval
configured only into the
Site 1
Master repeater (note:
Rest
the Master repeater
Channel
Site 2
shares this information
Rest
with all the other
Channel
repeaters in the system) Site 3
Rest
Channel
Site 4
Rest
Channel
Site 5
Rest
Channel
Cap+ Beacon
LCP Beacon
PAGE 40
LINKED CAPACITY PLUS PROCEDURES
Roaming – Passive Site Search (Automatic Roaming)
 For LCP a radio builds up a sorted roam list based on the LCP (Roaming) Beacons channels
transmitted on the home site’s Rest Channels.
 While the home site signal strength remains above a programmable threshold, the radio
remains on the home site.
 If the home site signal strength drops below a programmable threshold, then the radio starts
to scan through the sorted roam list for a new site
 The radio only scans for a new site while in the idle state (e.g. it does not scan for a new
site while still receiving a call of interest on the current site).
 Also, the radio does not scan for a new site if the radio’s Site Lock feature is enabled.
 During a Passive Site search, the radio identifies the site with the strongest signal and then
makes that site its new home site.
 If a better site is not found, then the radio remains on the current home site and continues
scanning.
 While a radio is carrying out a Passive Site Search, it needs to leave its current home site for
short durations which may cause the radio to miss activity on its home site (resulting in late
entry to voice calls, or missed control/data).
 To minimise missed activity, the programmable threshold should not be configured too
high.
 Additionally, a user may suspend automatic roaming using the Site Lock feature (this is
particularly useful if the radio is stationary and the user is satisfied with the quality of
service from the current home site).
PAGE 41
LINKED CAPACITY PLUS PROCEDURES
Roaming – Active Site Search
 Active Site Search consists of the radio sending wake-up messages to each site in its sorted
roam list (which it builds up from the LCP Beacons) until it finds an active site.
 Active Site Search is initiated as follows:
 When the radio initiates a transmission and it’s home site rest channel repeater can not be
woken.
 Or, when the user initiates a Manual Site Roam (either using the menu or a programmable
button).
 On waking a repeater, the radio synchronises itself with the repeater, completes the
transmission and makes the new site its home site.
 If the end of the sorted roam list is reached and a site is not found, the radio provides the user
with a failure indication.
 Active Site Search does not necessarily find the best site, but rather allows the radio to move
to the next “in range” site.
 Radios only transmit a single (polite) wake up message to any given repeater, however there
may still be regulatory reasons why it might not be desirable for a radio to transmit wake up
messages on each of its sorted roam list member’s frequencies until a site is found. Where
this is the case, then radios should be configured with Active Site Search disabled.
PAGE 42
LINKED CAPACITY PLUS USER INTERFACE
Home Screen
Roaming Icon: Radio not in locked state.
It will disappear after the user locks the site.
Channel name
Press PB to
lock site
Turn on
repeaters
Out of range state
Unlock state
Lock State
(Same as Cap+)
Radio’s LED will flash yellow if radio in system busy or local system busy state
PAGE 43
LINKED CAPACITY PLUS USER INTERFACE
Site Information
Press Programmable Button to display site alias
Site Alias
Site Number
Press site button
to display site alias
Press Programmable Button to find site
Cannot
find site
Press PB
to find site
Successfully
Found Site
PAGE 44
LINKED CAPACITY PLUS CONFIGURATION
Repeater - Network
Select Master or Peer
Similar Configuration to Cap+
(note: the LCP beacon interval is five times the
Cap+ beacon interval and the LCP beacon
duration consists of a single burst appended to
every 5th Cap+ beacon)
PAGE 45
LINKED CAPACITY PLUS CONFIGURATION
Repeater - Talkgroups
 Wide Area Talkgroups are associated with a set of sites
 Enables statically defined Selective Site “Light-Up”
 Any Talkgroup not defined in this table is assumed to be a Local Talkgroup
 Subscribers do not need Wide Area or Local Talkgroup categorization
 These parameters are configured in one repeater only (the “Master”)
PAGE 46
LINKED CAPACITY PLUS CONFIGURATION
Repeater - Talkgroups
 Channels at each site can be reserved for Wide Area Talkgroups only
 Neighbouring sites for each site are defined
 Neighbouring sites are overlapping sites only and speed up automatic roaming
 These parameters are configured in one repeater only (the “Master”)
Site
1
Site
2
Site
3
Site
4
Site
5
Site
6
Site Id
1
2
3
4
5
6
Neighboring Sites List
2, 3
1, 3
1, 2
5
4, 6
5
PAGE 47
LINKED CAPACITY PLUS CONFIGURATION
Repeater - Channel
PAGE 48
LINKED CAPACITY PLUS CONFIGURATION
Subscriber - Overview
LCP Personalities
Channel lists for each site
Site list for all sites
PAGE 49
LINKED CAPACITY PLUS CONFIGURATION
Subscriber – Channel Lists for each site
Defines channels
at given site
PAGE 50
LINKED CAPACITY PLUS CONFIGURATION
Subscriber – Site List for all sites
Defines threshold for
radio to activate roaming
Using different RX Group
Lists for different sites
enables the radio to
belong to a site’s Local
Talkgroups when the
radio roams to that site.
Defines all sites
on which radio
is required to
operate
PAGE 51
LINKED CAPACITY PLUS CONFIGURATION
Subscriber – LCP Personalities
Defines all sites on which
the radio is required to
operate
PAGE 52
LINKED CAPACITY PLUS CONFIGURATION
Subscriber – Programmable Buttons
Buttons can be configured
for:
Locking the site
Roaming to another site
Checking the site alias
PAGE 53
LINKED CAPACITY PLUS CONFIGURATION
Important things to remember
 Subscriber and repeater beacon intervals need to be the same.
 For Cap+, subscriber beacon interval needs to be higher than repeater beacon interval.
 Data revert repeater requires Channel ID in the range 33 to 253.
 Cap+ and IPSC data revert repeaters do not require Channel ID configurations.
 RX Group List needs to be configured for each site.
 For Cap+ and IPSC, RX Group List is defined at a Personality / Channel level.
 If Contact name for selected Radio Personality corresponds to a talkgroup, then Radio
automatically listens for this talkgroup regardless of whether it’s contained in the RX Group List.
 Data revert channels need adding to Subscriber Data Channel Lists.
 Enables radio to select appropriate data revert channels at a given site.
 Radio IDs across system need to be unique.
 Includes Radio IDs for Repeaters, Subscribers and RDAC devices.
 Otherwise system will not function properly.
 Radio personality only needs to be configured for sites on which radio will operate.
 No need to add all system sites to radio personality.
PAGE 54