Motorola's SmartNet Systems

Type-II Fleetmapping

Information is exchanged between the Subscriber units and the Central Controller using Outbound Signaling Words (OSW) from the Central Controller and Inbound Signaling Words (ISW) - from the subscriber units.

The information is transmitted in a timing format called Word Frame separated by Word Frame Interrupts (WFI). The Word Frame is a 23.3 mSec time frame in which all signals are transmitted.

The central controller determines a Type-II radio user by interpreting a 16-bit ID field, which informs the central controller of the Type-II individual ID.

A 16-bit Individual ID address is equivalent to a 4 digit hexadecimal number (from $0000 to $FFFF).

• If group information is required, another 16-bit field informs the central controller of the announcement/talk group. The announcement/talk group number is coded into the 12 most significant bits of the 16-bit field. The last 4 bits (T-bits) provide additional call type information for dual word formats. T-bits inform the central controller of an announcement/talk group, clear or coded transmission, emergency or standard, etc.

A 12-bit announcement/talk group address is equivalent to a 3 digit hexadecimal number (from $000 to $FFF).

Information is exchanged between the Subscriber units and the Central Controller using Outbound Signaling Words (OSW) from the Central Controller and Inbound Signaling Words (ISW) - from the subscriber units.

The information is transmitted in a timing format called Word Frame separated by Word Frame Interrupts (WFI). The Word Frame is a 23.3 mSec time frame in which all signals are transmitted.

The central controller determines a Type-II radio user by interpreting a 16-bit ID field, which informs the central controller of the Type-II individual ID.

A 16-bit Individual ID address is equivalent to a 4 digit hexadecimal number (from $0000 to $FFFF).

• If group information is required, another 16-bit field informs the central controller of the announcement/talk group. The announcement/talk group number is coded into the 12 most significant bits of the 16-bit field. The last 4 bits (T-bits) provide additional call type information for dual word formats. T-bits inform the central controller of an announcement/talk group, clear or coded transmission, emergency or standard, etc.

A 12-bit announcement/talk group address is equivalent to a 3 digit hexadecimal number (from $000 to $FFF).

Type-II analog fleet maps use only one size code, "X". The weighted point value for "X" is always one. You can have a maximum of eight weighted points for a single Type-II trunked system. Each "X" size code provides 512 announcement/ talkgroups and 8192 individual IDs. There is no limit (within the capacity of the system) to the number of:

• Different talkgroups that can be assigned to a specific announcement group (Multigroup).
• Different Type-II individual IDs that can be assigned to a specific talkgroup.

Type-II ID Construction

A Type-II Individual ID begins with a "7" followed by 5 decimal digits ranging from 00000 to 65535. The five digits are a direct decimal conversion of the 4-digit hexadecimal individual address. To convert a hexadecimal address to a Type-II individua1 ID:

Step 1.
Convert the 4 digit hexadecimal address to decimal; $0000 through $FFFF in hex equals 00000 through 65535 in decimal.

Step 2.
Add 700000 to the decimal number: 00000 through 65535 equals 700000 through 765535.

Due to the limitations within the system, a Type-II system typically allows for approximately 48,000 active IDs (Start Site and SmartWorks systems have a maximum of 16,000 active IDs). Type-II Announcement (MultiGroup) or TalkGroup IDs: A Type-II Announcement/talk group ID begins with an "8" followed by 5 decimal digits ranging from 00000 to 04095. The five digits are a direct decimal conversion of the 3-digit hexadecimal announcement of talk group address. To convert a hexadecimal announcement/talk group address to a Type-II announcement/talk group ID:

Step 1.
Convert the 3 digit hexadecimal address to decimal; $000 through $FFF in hex equals 00000 through 04095 in decimal.

Step 2
Add 800000 to the decimal number 00000 through O4O95 equals 800000 through 804095.

Type-II signaling structures have limitations on the IDs that can be assigned. Refer to the Table shown on the overhead for a description of the Type-II ID limitations. In addition to the conflicts listed in this table, the Priority Monitor feature wants only odd numbered ID's to be assigned. Assigning only odd numbers to subscribers reduces the assignable numbers to half (i.e. 4096 to 2O48). Priority Monitor is explained in more detail in the features section.

Hybrid systems offer advantages of a Type-II system while allowing both Type-I and Type-II radios to use the system at the same time. Type-II 'Hybrid' radios (Type IIi) with the capability to use Type-II signaling protocol in a Type-I fleet/subfleet must be assigned to a designated mixed fleet before they can communicate. However, a Hybrid system may or may not contain mixed fleets. Type-I and Type-II Trunking ID limitations apply to all Hybrid systems.

Hybrid systems were developed to provide an easy migration path from the original Type-I systems to Type-II signaling/fleetmapping. The transition allows systems to maintain the original Type-I subscriber units while allowing the addition of Type-II radios. Type-II subscribers cannot talk directly with Type-I subscribers or visa-versa. Type-I only systems are no longer available as a new Motorola trunked system.

Hybrid systems contain both Type-I Size Codes (B through K, M, 0, and/or Q) and Type-II Size Code (X). NOTE: Size Code "A" is not available. In certain situation, size codes; B, G, and I cannot be used.

It is important to know the location of the different size codes with respect to the prefixes (the Fleetmap) when adding or changing subscriber IDs to the system. Type-II analog IDs may only be assigned within the Prefix ranges having Size Code X. Type-I IDs must remain only in Prefixes containing Type-I Size Codes.

Type-I signaling/fleetmapping and Hybrid signaling/fleetmapping sit not supported with the MTC 3600 Trunked Central Controller.

Prefix 7 contains an "X" Size Code (Type II). All other Prefixes are Type-I. This method of Hybrid fleetmapping allows Type-I subscribers and Type- II subscribers to use the same system, but they cannot talk directly to each other. Type-I subscribers are assigned to Fleets within Prefixes 0 through 6 while Type-II subscribers are assigned JDs within Prefix 7. Prefix 7 provides for 512(256 odd numbers) Talkgroups and up to 8192 individual IDs. The range of Type-II individual IDs is 757334 to 76534. Available Type H Talkgroup ID range is 803583 to 804095.

Partitioned Elects have one or more Elects in a given Type-I prefix converted to Type II. Address memory for the substituted Fleet(s) is available for Type-II subscriber and talkgroup D's. This method allows Type-I subscriber units and Type-II subscriber units to operate in the same system, but they cannot talk to each other. Fleets partitioned to Type-II cannot be used to assign Type-I IDs. The actual number of Type-II announcement/talkgroups made available for each fleet partition depends upon the size code and the prefix the fleet is in.

Partitioned Subfleets have one or more Subfleets in a given Type-I prefix converted to Type II. Address memory for the substituted Subfleet(s) is available for Type-II subscriber and talkgroup ID's. Partitioned Subfleets provide any part of the address range in the prefix to be allocated to Type-II IDs. This method allows Type-I subscriber units and Type-II subscriber units to operate in the same system, but they cannot talk to each other.

Subfleets partitioned to Type-II cannot be used to assign Type-I IDs. The actual number of Type-II announcement/talkgroups made available for each fleet partition depends upon the size code and the prefix the fleet is in.

Restrictions:

1. Subfleet 0 is the Fleet-Subfleet call pattern for a Fleet-wide call and is not used.
2. Subfleets 1, 2, and 3 are not used because of specific Type-I call processing restrictions.
3. The last subfleet in each size code is not used because it is needed for Type-I ID. Private Call II, Dynamic Regrouping, and extended function commands.
4. Size Codes A, E, G, H, and L are not used because there are only two Subfleet bits in the 16-bit map. A Subfleet partition requires at least three Subfleet bits for defining subfleets.
5. All the rules limiting Type-II IDs and talkgroups apply to a subfleet partition.

Mix Type-II IDs with an existing Type-I fleet. This result is called a Mixed Fleet. This method allows Type-I radios to talk to Type-II radios on the am system, in the same fleet. A mixed fleet is the only hybrid method that allows Type-I and "hybrid" radios to talk to each other. Type-II "hybrid" radios with capabilities to use Type-I or Type-II signaling protocol must be assigned to a mixed fleet before they can communicate.

The Fleetmap must contain an "X" size code. Mixed fleets allocate addresses for only Type-I radios. Type-II radios must have addresses allocated somewhere in the address range.

Type-II radios use the mixed fleet ID as a "pseudo announcement group", and the mixed fleet's subfleets as "pseudo talk groups" Any valid Type-II ID can be affiliated with a mixed fleet. The total number of Type-II IDs that can be affiliated to a mixed fleet is restricted to the number of Type-II IDs available within the system.

The first 16 Type-I individual IDs of a Mixed Fleet cannot be used. Therefore, a mixed fleet must use a size code with more than l6lDsperfleet. Size Code "A" cannot be used for Mixed Fleets.

The Central Controller decodes a mixed fleet T-bit field by distinguishing a Type-I individual ID from a Type-II talkgroup T-Bit. It processes all IDs less than or equal to $000F as the first 16- bit field of a Type-II ID. All individual IDs greater than $000F are processed as a Type-I ID in a mixed fleet. A Mixed Subfleet is not allowed, but if its part of a Mixed Fleet, you can assign both Type-I and Type-II radios to it.