1、 EIA TSBL02-AABG 96 W 3234600 057b044 Obi m TIADCIA TELECOMMUNICATIONS SYSTEMS BULLETIN APCO Project 25 Conventional Control Messages New Technology Standards Project Digital Radio Technical Standards TSBlO2.AABG JULY 1996 TELECOMMUNICATIONS INDUSTRY ASSOCIATION Copyright Telecommunications Industry
2、 Association Provided by IHS under license with EIANot for ResaleNo reproduction or networking permitted without license from IHS-,-,-EIA TSBL02-AABG 96 3234b00 0576045 TT8 NOTICE TIA/EIA Engineering Standards and Publications are designed to serve the public interest through eliminating misundentan
3、dings between mufcturers and purdusers, hcititating interchangeability and improvement of products, and assisting the purchaser in selecting and obtaining with minimum delay the proper product for his particular need. Existence of such Standards and Publications shall not in any respect preclude any
4、 member or nonmember of IA/EIA fkom manufhturing or selling products not conforming to such Standards and Publications, nor shall the existence of such Standards and hiblications preclude their voluntary use by those other than TMIA members, whether the standard is to be used either domestically or
5、internationally. Standards, Publications and Bulletins are adopted by MIA in accordance with the American National Standards Institute (ANSI) patent policy. By such action, TIA/EIA does not assume any liability to any patent owner, nor does it assume any obligation whatever to parties adopting the S
6、tandard, Publication or Bulletin. Technical Bulletins are distinguished fiom MIA Standards or Interim Standards, in that they contain a compilation of engineering data or informaton ud to the technical community, and represent approaches to good engineering practices that .are suggested by the formu
7、lating committee. This Bulletin is not intended to preclude or discourage other approaches that similarly represent good engineering practice, or that may be acceptable to, or have been accepted by, appropriate bodies. Parties who wish to bring other approaches to the attention of the formulating co
8、mmittee to be considered for inclusion in fbture revisions of this Bulletin are encouraged to do so. It is the intention of the formulating committee to revise and update this Bulletin fiom time to time as may be occasioned by changes in technology, industry practice, or government regulations, or f
9、or otha appropriate reasons. (From Project No. 3604, formulated under the cognizance of the TIA TR-8.10 Trunking and Conventional Control Subcommittee.) Published by OTELECOMMUNICATIONS INDUSTRY ASSOCIATION 1996 Standards and Technology Department 2500 Wilson Boulevard Arlington, VA 22201 PRICE: Ple
10、ase refer to the current Catalog of EM, JEDEC and TIA STANDARDS and ENGmERING PUBLICATIONS International (303-397-7956) or call Global Engineering Documents, USA and Canada (1-800-854-7179) Ail rights reserved Printed in U.S.A. Copyright Telecommunications Industry Association Provided by IHS under
11、license with EIANot for ResaleNo reproduction or networking permitted without license from IHS-,-,-EIA TSBLOZ=AABG 96 E 3234600 0576046 934 TSB-102.AABG 1. Introduction APCO Project 25 applies to both conventional and trunked systems. The distinction between conventional and trunking systems may be
12、that trunking systems include a centralized controlling device which is used to assign channels to subscribers as service is demanded. This controlling device is absent in a conventional system. A large set of useful functions are defined for trunking systems, including but not limited to the functi
13、ons necessary for subscribers to request service and for the controller to grant service. Trunking also defines functions which may be applied to conventional systems, such as an Emergency Alarm. This document is intended to name those functions that are defined for trunking which may be applied to
14、conventional systems. 2. Scope This document defines the control messages of trunking for APCO Project 25 that may be applied to conventional systems. These control messages are extensions to the basic Common Air Interface. Conventional systems for APCO Project 25 are defined to be any non-trunked s
15、ystem which conforms to the standards and specifications of reference 11 or its subordinate documents, where a trunked system is defined to include a centralized controller that assigns requests for service by subscribers to specific radio channels. Conventional systems therefore do not have a contr
16、oller which assigns radio channels in the same sense as defined in reference 2. 3. Overview The following control messages of trunking systems are useful in some conventional systems. Those control messages for services that are listed as standard options in reference I are labeled accordingly. Emer
17、gency Alarm Call Alert - Standard Option Radio Check Radio Inhibit and Radio Uninhibit - Standard Option Status Update and Status Request Message - Standard Option Telephone Interconnect Dialing - Standard Option Radio Unit Monitor - Standard Option These control messages are defined in this documen
18、t for conventional systems by using the trunking definitions given in reference 2. 4. References These references are the latest version available at the time this document was written. 1 . Project 25 System and Standards Definition, TSB-102, September 1995. 1 Copyright Telecommunications Industry A
19、ssociation Provided by IHS under license with EIANot for ResaleNo reproduction or networking permitted without license from IHS-,-,- EIA TSBL02.AABG 96 = 3234600 0576047 870 = Definition Section(s) in Reference 2 TSB-102.AABG Alias 2. Trunking Control Channel Messages, to be published as 3. Recommen
20、ded Common Air Interface, TSB-102.BAAA, April 1994. 4. Trunking Procedures, to be published as TSB-102.AABD, 20 May 5. Telephone Interconnect Requirements and Definitions (Voice Service), 6. Common Air Interface Operational Description for conventional TSB-102.AABC, May 31 , 1996. 1996. IS-102.BADAI
21、 May 1996. Channels, TSB-102.BAAD, October 1994. Section 6.1.6 defines the alarm. Section 6.2.1 defines the ACK. Section 6.1.4 defines the alert. Section 6.2.1 defines the ACK. Section 6.2.6 defines the extended function. Section 6.2.6 defines the extended function. The extended function includes th
22、e Radio Check and its ACK. The extended function includes the Inhibit, Uninihibit, and their ACKs. update. Section 6.1.15 defines the status update. Section 6.2.1 defines the ACK for a Status Section 6.2.17 defines the status query. l Section 6.1.1 4 defines the status response. Section 6.1.1 1 defi
23、nes the message update. Section 6.2.1 defines the ACK for the Section 4.1.4 defines the formats for message update. transmitting dialing digits for telephone interconnect, Section 6.2.24 defines the command. l Section 6.2.1 defines the ACK. 5. Revision History EMRG-ALRM-REQ ACK-RSP-FNE CALL-ALRT-REQ
24、 ACK-RSP-FNE EXT-FNCT-CMD EXT-FNCT-CMD STS-U PDT-REQ ACK-RSP-FNE STS-Q STS-Q-RSP MSG-UPDT-REQ ACK-RSP-FNE TELE-INT-DIAL-REQ RAD-MONCMD ACK RSP-FNE March 1 O, 1995, version 0.0, initialized the definitions of conventional features. June 30, 1995, substitute control messages for features. January 24,
25、1996, updated section numbers for revised reference 2 and also June 4, 1996, updated from letter ballot comments. added addressing information. 6. Control Messages Specifications Category Name Emergency Alarm Call Alert Radio Check Radio Inhibit i Originator (7-9) Recipient (4-6) O rig inato r (7-9)
26、 Recipient (7-9) ng for Conventional Features Source Address I Tarnet Address I Recipient (4-6) Originator (7-9) Recipient (4-6) Originator (4-6) Status Request & Response STS-O STS-Q-RSP Originator (7-9) Recipient (4-6) Originator (3-5) Originator (4-6) Recipient (4-6) Recipient (4-6) Originator (7
27、-9) Recipient (7-9) Originator (7-9) - Table 6-2 defines the source and target address values in relation to the originator and recipient devices shown in figure 6-1 for each conventional control transaction. In the case of the ACK-RSP-FNE message, the Additional Informance Valid flag (AIV) shall be
28、 set, and the Extension flag (E) shall be 3 Copyright Telecommunications Industry Association Provided by IHS under license with EIANot for ResaleNo reproduction or networking permitted without license from IHS-,-,-EIA TSBLOZ-AABG 96 3234600 0576049 643 Radio Check Radio Inhibit & Uninhibit Status U
29、pdate (un-solicited) Status Request & Response Message Telephone Dialing Radio Unit Monitor TSB-102.AABG _ 4:, Section 12.2. See difference 1. 4:, Section 12.3 and 12.4. See differences 1, 5. 4, Section 10.3.1. See differences 1, 2, 3, 4, 6. :4, Section 10.4. See differences 1, 2, 3, 4, 6. :4, Secti
30、on 10.2. See differences 1, 2, 3,4, 6. 5, Section 2.1.2, Section 3.7. - - cleared, so that the message can be symmetrically addressed with both a source and target address. Table 6-3 Procedures for Conventional Features I Cateaorv Name I Procedure Sectionk in References 141 or i51 1 Emergency Alarm
31、Call Alert 1 4, Section 10.5. See differences 1, 4. I 41. Section 10.1. See differences 1. 2. 3.4. 6. I The procedures for these messages generally follows the trunking procedures described in reference 4. The specific sections in reference 4 are given in Table 6-3. There are some differences for co
32、nventional systems, which abbreviate the given trunking procedures. The following specific differences are noted in Table 6-3. 1. The random access protocol for the trunking control channel is not followed, because there is no control channel. Instead, the channel access procedure given in reference
33、 6, section 8.1 shall be followed. This procedure is intended to follow a polite channel access procedure. In the particular case of the emergency alarm, an impolite channel access procedure may be followed which ignores the status symbols on the channel. repeating information, as described in refer
34、ence 6, section 7. Consequently, trunking procedures for the RFSS shall be ignored for conventional systems. 3. Many trunking procedures for subscriber radios are designed to terminate retransmissions if the subscriber radio hears the RFSS repeat a message, This is allowed for call alerts, status up
35、dates, etc. Since the RFSS does not take any responsibility for retransmissions by itself, the termination of retries by subscribers in response to a control message repeated by the RFSS shall not be followed in conventional systems. 4. A conventional RFSS does not contain any control elements, exce
36、pt for the possibility of a dispatch console. Consequently, the Deny Response (DENY-RSP) and Queued Response (QUE-RSP) messages defined for trunking do not apply, and are not necessary. 5. A conventional RFSS does not maintain any affiliation, registration, or authentication records. Consequently, p
37、rocedures that include affiliation, registration, or authentication can proceed without requesting or initiating these functions. roaming. Consequently, the extended addressing defined for many of the messages, which includes the WACN and System ID in the message, is 2. The RFSS in a conventional sy
38、stem is only responsible for transparently 6. Conventional systems do not contain any visitor location registers for 4 Copyright Telecommunications Industry Association Provided by IHS under license with EIANot for ResaleNo reproduction or networking permitted without license from IHS-,-,-EIA TSBLOZ
39、.AABG Yb m 3234600 057b050 3b5 TSB-102.AABG not useful. In all cases the abbreviated or shortened form of the messages are sufficient. in the specific case of telephone dialing, the procedures are given in reference 5. 5 Copyright Telecommunications Industry Association Provided by IHS under license with EIANot for ResaleNo reproduction or networking permitted without license from IHS-,-,-Copyright Telecommunications Industry Association Provided by IHS under license with EIANot for ResaleNo reproduction or networking permitted without license from IHS-,-,-
