JP2967573B2 - Communication method in trunk RF communication repeater architecture, and trunk RF communication repeater architecture - Google Patents

Description

This application is related to pending U.S. Patent Applications Nos. 056,922 and 085,572 filed June 3, 1987.

The present invention relates generally to trunk wireless relay schemes.
More specifically, a radio frequency relay having "fail-soft" features, such as having trunk operation and other communication capabilities, even if a major component of the architecture (e.g., primary controller) fails. Related to the architecture of the equipment point.

The trunk operation of a wireless repeater (multiple users sharing one repeater communication line in time) is well known.
Early trunk schemes used analog control signals, but recent schemes use digital control signals. For various different reasons, the control signals are used on dedicated control lines and / or different operating lines, but with different effects. Some, but not all, representative publications and U.S. patents that describe conventional typical trunk radio relay schemes include U.S. Patent Nos. 3,292,178, 3,458,664, and 3,571,519.
No. 3,696,210, No. 3,906,166, No. 3,936,61
No. 6, No. 3,970,801, No. 4,001,693, No. 4,010,3
No. 27, No. 4,012,597, No. 4,022,973, No. 4,027,
No. 243, No. 4,029,901, No. 4,128,740, No. 4,13
No. 1,849, No. 4,184,118, No. 231,114, No. 4,30
9,772, 312,070, 4,312,074, 4,32
No. 6,264, No. 4,339,823, No. 4,347,625, No. 4,3
No. 60,927, No. 4,400,585, No. 4,409,687, No. 4,
No. 430,742, No. 4,430,755, No. 4,433,256, No.
Nos. 4,450,573, 4,485,486 and 4,578,815.

U.S. Pat. No. 4,360,927 teaches, in part, that the called device (1
Prior to allowing communication to proceed with one or more), avoiding the use of a dedicated control line by performing a bandshake with the repeater / other point controller on the captured "vacant" working line. This is an example of a switched line relay system.

Trunk wireless relaying schemes have many applications in practice and possibly. However, one important application is the public trunk (PST) scheme. For example, one city area can use one trunk wireless relay system to perform efficient wireless communication between individual wireless devices in many different organizations. Each agency can communicate efficiently between individual devices or sub-devices of different organizations (eg, different devices in police station patrol cars,
It may be necessary to have efficient communication between different devices of a criminal or drug investigator). Sometimes it may be important to communicate simultaneously to a pre-defined group of devices (eg, all devices, all patrol cars, all patrol police, etc.). At the same time,
Other agencies (eg, fire departments, transportation departments, water bureaus, emergency / emergency services, etc.) may require similar communications services. As you know if you know trunk theory,
If a relatively small number of wireless repeaters are trunked (i.e., shared by all possible devices for use "as needed"), all of these within a given geographic area Demand can be efficiently met.

Today, there are various trunk communication systems on the market, each with its own advantages and disadvantages. One thing common to all systems is that (1) the optimal communication baud rate cannot be used,
(2) Diagnosis, location confirmation and correction of hardware failure cannot be performed, and (3) Trunk operation cannot be supported continuously when a failure occurs at a point other than the RF signal. It is an architecture. The significance of each of these three points will now be described individually.

(1) Optimal communication speed The telecommunications industry has invested considerable time and money in deciding the best way to transmit data at 800 MHz over cellular telephone lines. Data transmission efficiency is important because it increases both the frequency efficiency and the user efficiency of the scheme. In conclusion, the optimal baud rate was the highest baud rate of the two-level encoded data maintained by the bandwidth of the line. For a public trunk (PST) system with a 2.5kHz line bandwidth, 9,600 baud is the highest speed that can be sustained. However, due to the hardware and architecture that cannot support the stronger processing conditions associated with higher baud rates, existing schemes use lower baud rates (300 baud) or lower than optimum baud rates (3,600 baud).
Bo) is used.

(2) A primary point controller using a computer that detects the location of a hardware failure and monitors the activity of a correction point to detect a failure at the point facilitates the failure detection and correction process. On the other hand, if the same computer constitutes all intelligence at other points, it will be difficult to detect faults inside the controller itself. Existing schemes do not have a computer to detect failures effectively, or the computer has all the intelligence of the point (so that you want to effectively diagnose your own failure or cannot recover it) ).

(3) Trunk / fail-soft operation There are at least three reasons why the trunk capability must not be lost due to the failure of the point controller. First, since this scheme is a trunk scheme, there may be more radios in this scheme than in the normal scheme. Therefore, the absence of trunk mode means that
This leads to overload of the scheme (since the trunk scheme can handle much more traffic than the non-trunk scheme). As a result, the wireless device is pushed out of the scheme, or the wireless device cannot start accessing the scheme.

Second, from the user's point of view (for example, from the trunk method,
Changing the mode of operation (in a manner in which the user has to manually select his own operating frequency) is especially forcing the user to listen to all conversations-even conversations unrelated to him. Sometimes it causes extra confusion (in a typical trunk scheme, only the device that is going to be the party to the conversation tunes to the frequency on which the communication takes place).

Third, point controller failures are not statistically unrelated to on-site emergencies. For example, a storm that could lead to a site emergency could cause a power problem that could damage the point controller. Therefore, the benefits provided by trunk communication may be most needed when the point controller fails.

Fault tolerance can be the most elaborate part of a scheme and cannot be effectively conceived after the scheme design process. So far, trunk communication schemes have been designed with little regard for fault tolerance, and the only way to gain reliability is for the ultimate user to invest in redundant hardware. Providing a true failure-tolerant trunk radio scheme to the end user requires design and configuration considerations of the scheme throughout the development cycle, starting with the idea of the scheme itself.

A trunk communication scheme must be evaluated based on all aspects of its operation, including its fault tolerance. As an architecture of a repeater point for trunk (or even non-trunk) communication systems, there is an architecture which has excellent fault tolerance and which overcomes the above-mentioned disadvantages inherent in all other known existing trunk systems. It has been developed. Briefly, the present invention
Separating signal processing functions from data processing and control functions, providing a unique point of architecture that distributes both types of processing functions throughout the architecture.

Dedicated signal processing hardware (configured as so-called "trunking cards" or TCs) for each radio frequency line (and radio transmitter and receiver operating on that line) requires the associated line Performed signal processing.
Each dedicated signal processing trunking card operates substantially independently, except for the higher level of necessary coordination with the other trunking cards and the primary point controller calculator. During normal operation of this scheme, most control functions are performed by a point controller (eg, a high-speed computer with sophisticated real-time control capabilities) and the trunking card
A processor can dedicate all of its processing resources to processing signals associated with the particular RF line for which it is dedicated. Although the synchronization lines and serial communication lines are shared by all line processing trunking cards, the flow of control information during normal operation of the scheme occurs between the trunking cards and the point controller.

One line signal processing trunking card is assigned to operate on a dedicated trunking control line (any trunking card can operate on a control line, but assigns any trunking card). If the assigned card fails, another trunking card takes over). All mobile station devices that are not participating in valid communication on the working line monitor the control line, and in order to communicate with other mobile station devices or consoles, issue a command to move to the working line on this control line. Receive.

In the conventional system, if the alternate point controller is not put on the track due to the failure of the point controller, the entire system will not operate until it does so (or at best, it starts operating in the non-trunk mode, This line operates independently as a repeater, with little or no coordination between the operation of different lines). In the system of the present invention, the trunking card assigned to operate on the control line detects the failure of the point controller almost instantaneously, and when this is detected, the point controller in which the trunking card no longer fails is detected. Instead of trying to communicate with the trunk, instead of operating in a "fail-soft" mode, where control information is exchanged with each other over a supporting serial link (BSL) that is not used during normal operation of the scheme.・ Control the card. Communication between the trunking cards over the supporting serial link is coordinated by the control line trunking cards, each trunking card independently managing the state information of the scheme,
And each trunking card updates the state change of the control line trunking card and all other trunking cards.

In failsoft mode, the control functions handled by the point controller during normal mode operation are handled in a distributed manner by the trunking card. For example, during normal mode of operation, a downlink trunking card that simply passes messages between the point controller and the operator control console sends messages from the console via the BSL during failsoft operation. It begins communicating directly to the working and control line trunking cards and also monitors status messages generated by the various trunking cards and communicates these messages to the console. The control line trunking card, when in fail-soft mode, initiates the assignment of a working line for trunk communication instead of relying on a point controller to assign the line.
The working line trunking card is also in fail-soft mode, and in the normal mode, starts to perform the control function performed by the point controller.

When in fail-soft mode, advanced control functions (eg, call recording, dynamic group reorganization, etc.) are lost, but the trunking control functions are distributed between the trunking cards. , Trunk operation ability is maintained. As a result, failure of the primary point controller has little or no effect on normal communication and trunking capabilities.

More specifically, during the failsoft mode, the control line trunking card receives a message during each incoming control line slot (the period during which the mobile station or portable transceiver transmits its active line acquisition request). It is determined whether or not. If an incoming message is coming, the trunking card assigned to the control line processes the message. For example, if the incoming message is from a mobile station device requesting communication with another mobile station device, control line trunking
The card selects an idle working line, communicates a line assignment message to the calling and called mobile station equipment via the control line, and communicates to the selected working line trunking card via the supporting serial link. Also communicate a line assignment message.

On the other hand, if no message is received, the trunking card assigned to the control line polls other trunking cards in this scheme for status information. Each trunking card responds via the supporting serial link in the corresponding time slot assigned to it. The entire polling process is quick (for example,
Complete (prior to the end of the inbound control line message slot).

The trunking card assigned to the control line periodically sends a synchronization signal to other trunking cards via the synchronization line during the normal operation mode and the fail-soft operation mode, and these other cards are used. Device loosely synchronizes the communication on the working line with the communication on the control line. The control line trunking card is the "master" of point synchronization timing because it controls the timing of the synchronization lines connected to all other trunking cards. In the preferred embodiment, the width of the synchronization pulse generated by the control line trunking card is used to inform other trunking cards whether the scheme is normal operation or fail-soft operation.

Because each line trunking card independently processes the RF signals transmitted and received by the associated repeater on the associated line, during normal operation and during fail-soft operation,
High speed communications (eg, 9,600 baud) can be supported without overloading the point controller (all signal processing is done within the trunking card itself). Each trunking card is a separate parallel (eg RS-232C)
It is connected via a data link to the primary point controller computer. Thus, failure of the parallel link and / or trunking card does not disrupt communication between the primary controller and the remaining trunking cards. In addition, this feature allows a point controller (or service person) to more accurately diagnose a failure that has occurred.

One of the most important advantages of the point architecture provided by the present invention will be that no single point of failure will result in a loss of trunk operation.

Higher level scheme features (eg call recording and dynamic group reorganization) if the point controller computer fails.
Signal processing, and more importantly, the trunking capability is still performed in a distributed manner by the line trunking cards (this is because trunking control is provided within each trunking card). Because it has enough computing power to do the processing). Trunking·
If the card fails, the device can be removed from use and normal operation can be continued with one less RF line. In the preferred embodiment, all trunking cards are identical (all have the same program), so if the trunking card assigned to operate on the control line fails, that trunking card will fail. Can be taken out of use and another trunking card can be assigned to operate on the control line (each line trunking card can act as a control line trunking card).

The scheme of the present invention is sometimes referred to as a "digital" trunk scheme because the trunk control is performed continuously by digital signals sent over a dedicated "control" data line. All devices are programmed to automatically return to the intended primary control line when turned on or reset. If the expected control line data type is not found on this line, alternate and possible control lines are monitored in sequence, in sequence, until a valid control line is found. In this way, the ordinary control line equipment at the central control point can be temporarily taken out of use (for maintenance, for example). With this same feature, if the legitimate control line malfunctions unexpectedly or becomes otherwise unusable,
The operation of the trunk system can be continued.

If the supporting serial link between the trunking cards fails while the primary point controller is still in operation,
No operational features are lost due to the alternating use of the serial link and the point controller communication path. If the synchronization link between the trunking cards fails, the RF line access time will increase slightly (eg, from 280 ms to 320 ms) due to the loss of loose synchronization between the control and working lines. However, this slight increase in access time is invisible to the user.

Perhaps one of the greatest advantages of the point architecture provided by this invention is the property of fault tolerance. Conventional repeater architectures have provided some degree of fault tolerance simply by providing redundant hardware, such as a support point controller.
This solution of using redundant hardware is not only expensive, but also less reliable than the distributed processing architecture provided by the present invention. For example, in a system that uses redundant hardware in the part that operates the supporting hardware, there is a possibility that the system itself will fail and the system cannot be recovered.

Technology has finally made trunk radio schemes that are more tolerant of faults a reality. The architecture provided by the present invention provides a fault tolerant architecture having a permanent point controller supported by a "hot" stand-by point controller using one universal point controller. It has three times higher trunk operation reliability than the trunk operation reliability.

Given the demand for communication today and what the current technology can supply, a fault tolerant wireless communication scheme is required.
Evaluating the capabilities of a given scheme requires an understanding of the trade-offs that a design engineer chooses in setting a balance between function, cost, and fault tolerance. Finally, an effective evaluation of the scheme selects those that communicate with fault tolerance.

The above and other features and advantages of the present invention will be better understood from the following detailed description of the presently preferred embodiments of the invention with reference to the drawings.

A trunk wireless relay system as an example of the present invention is generally shown in FIG. As shown, the various groups of individual devices communicate with each other (either inside their own group and possibly outside of it) via a shared radio repeater that is part of trunk trunking scheme 100. The originating console 102 may be provided directly at the transit point 104 or may be located remotely via another communication facility 106, as will be readily appreciated by those skilled in the art. As will be appreciated by those skilled in the art, there may be multiple outgoing consoles 102 (eg, one for each separate party) and a master or monitoring outgoing console for the entire scheme.

The central unit 100 comprises one or more satellite receivers 100-
FIG. 2 together with FIG. 1 is shown in some detail. As can easily be seen, the satellite receiver device is spatially separated from the central point 100. This is because radio reception may be temporarily better at one or the other of the selected antenna devices. To this end, the received signals from the satellite sites as well as from the central unit are combined in a "voting" circuit to select the best available signal for the control or communication process.

At the central point, the transmitting antenna 200 and the receiving antenna 202
(Which may be a common antenna structure) can be used with ordinary signal combining / decombining circuits 204, 206, which will be apparent to those skilled in the art. Because of this,
The transmitting and receiving RF antenna circuits 200 to 206 include a plurality of RF
Allowance for multiple transmission / reception lines of multiple duplex RF lines at relay "stations" 300, 302, 304, 306, etc. Typically, there may be 24 such stations. The transmitter and receiver circuits of each station are
As also shown generally in FIG. 2, it is typically controlled by a dedicated control shelf CS (eg, a microprocessor-based control circuit). The logic circuit of such a control shelf attached to each station is controlled by a trunking card TC (for example, another logic control circuit based on a microprocessor) 400, 402, 404, 406. If desired, another trunking card 408 can be dedicated for digital data communication. All trunking cards 400-408 communicate with one another and / or the primary point controller 410 via a dedicated data bus 412. The primary point controller (and optional support controller if desired) may be a commercially available general purpose processor (eg, a PDP11 / 73 processor with an 18 MHz J11 chip device). The main "intelligence" and control capabilities of the entire scheme are in the controller 410, so that the trunk relay service can continue even if the controller 410 malfunctions or is otherwise unavailable. Alternate support or "fail-soft" control functions are incorporated in the trunking cards 400-408.

A telephone interconnect 414 may optionally be provided for the switched public telephone line. Typically, scheme management terminals, printers, etc. 416 also provide one or more outgoing consoles 102 for overall management and control of the scheme.
With). If desired, special test and alarm facilities 418 can also be provided.

Signal "voting" circuits 500, 502, 5054, 506, 508 receive a plurality of input digital or analog signals and select the strongest and / or otherwise the most reliable one of these input signals. It is connected so that it may output it. For this reason, the received signal from the central point 100 of the system is input to each of the line vote decision circuits 500 to 508, and another similar input signal is generated at the receiver at the point 100-1 of the satellite receiver. Is input to each voting circuit. Thereafter, the results of the voting process are sent back to the trunking card circuits 400-408, where they are further processed as valid "receive" signals.

The architecture of the point for communicating control data and a somewhat more detailed illustration are shown in FIG. In this case, it will be appreciated that the PDP 11/73 controller 410 communicates with up to 24 trunking control cards TC via the 19.2 kilobyte bus 412. These cards control the respective repeater circuits on separate lines. Outgoing console
Another high-speed 19.2 KB bus 420 on downlink with 102
(This downlink includes the downlink trunking card). Communication with the central processor 401 and other data occurs over a 9,600 baud link, as shown in FIG. The point controller 410 may include, for example, 128 kilobytes of code PROM, 1 megabyte of RAM, and a 32THV-11 / J compatible RS-232C port (connected to each bus 412). Typically, the controller 410 is programmed with micropower Pascals and a multitasking event driven operating system to manage all of the various data communication ports in an acceptable real-time manner. I do.

On each controlled trunk, a 19.2 kilobyte data bus 412 (and, if desired, another similar bus connected to an optional support point controller) is monitored by the 8031 microprocessor in the TC module. Is done. The TC trunking control module uses clock synchronization and "fail-soft" indication (for example, it cannot use the normal control by the central controller 410, and uses an alternate distributed control algorithm within each trunking control module TC. Hardwired input to indicate that it should be implemented). Control of the associated repeater control shelf CS is normally performed using dedicated audio and communication audio and control buses. In a preferred embodiment, a common dedicated audio signal path (not shown) connects each control shelf CS with console 102,
A conventional audio path switch (also not shown) can connect the audio signal path of the selected control shelf to another selected control shelf, telephone interconnect block 414, console 102, etc.

Referring now to FIG. 4, in a preferred embodiment,
Each trunking card TC is a microprocessor 50
2 and associated random access memory (RAM)
504, a multiplexer 506 and a modem 508.
Microprocessor 502 executes software stored in random access memory 504 (which is preferably non-volatile) to perform various control functions, including a "fail soft" mode of operation. I do.
Microprocessor 502 transmits the digital control signal via modem 508 and dedicated serial control line 510 to the associated repeater transmitter and receiver. For example, the microprocessor 502 performs keying and unlocking operations of the associated repeater transmitter, controls the repeater transmitter and receiver to process audio or digital signals, and avoids wasting energy. Therefore, power can be cut off from the transmitter and the receiver. The digital signal received by the repeater receiver is transmitted to microprocessor 502 via path 510 and modem 508, and the digital signal to be transmitted is transmitted from the microprocessor to the repeater transmitter.

Each trunking card TC has three serial ports A,
Has B and C. Multiplexer 506 selects at any one time only one of the receive ports A, B, C to be monitored by the trunking card (the select input of the multiplexer is controlled by microprocessor 504). Port A is connected via dedicated parallel RS-232 line 412
Connected to next point controller 410. Port B is connected to an alternate point controller (if it is used) via a similar dedicated RS-232 signal path. Port C is connected to the supporting serial ring BSL. This interconnects all trunking cards TC in a daisy chain (as shown in FIG. 3).

When multiplexer 506 selects port A (which is typically the case during normal operation of the scheme), it receives a message (in digital signal form) from primary point controller 410 and controls the primary point control. To the alternate point controller via a parallel line connected to port B. Similarly, if multiplexer 506 selects port B, it will receive a message from an alternate point controller (not primary point controller 410),
All messages that microprocessor 502 sends to the alternate point controller are also sent to the primary point controller. In this way, the state change information of the alternate point controller is constantly updated, and if the primary point controller fails, the control of the system can be immediately taken over.

In normal operation, the trunking card processes the signals received and the signals to be transmitted, and performs very few control functions. All or most of the control functions are the primary point controller 410
(Or an alternate point controller if it is running). The primary point controller 410 performs high-level control functions (eg, call recording, dynamic group reorganization, etc.), as well as simple control functions (eg, trunk line assignment, call priority). To run multitasking event-driven software, such as
As described in pending U.S. Patent Application Serial No. 056,922 filed June 3, 1987.

During normal operation of the scheme, the trunking card generally simply receives the received digital control signal from the primary point controller 41.
0, the digital control signal to be transmitted from the primary point controller is transmitted to the transmitter of the associated repeater, and the other is directly responded to the control signal transmitted from the primary point controller. (E.g., starting transmission, releasing the key of the transmitter of the associated repeater, etc.). During normal operation, the microprocessor 502 allocates most of its processing resources to processing signals received by one repeater receiver and signals to be transmitted by one repeater transmitter. Therefore, the preferred embodiment scheme supports very high data rates (eg, 9,600 baud).

During normal operation mode of scheme 100, supporting serial link B
I don't use or need SL. Various trunking
The independent operations of the cards are coordinated by the primary point controller 410, and the signal processing operations performed by the various trunking cards are controlled by the synchronization signals generated by one trunking card assigned to the control line. By
Loosely synchronized. This synchronization signal is transmitted to the remaining trunking cards via the frame synchronization control line 520.

The frame synchronization control line 520 is a single line that connects all trunking cards in a daisy chain. Regardless of which trunking card, the trunking card assigned to the control line is
To inform all other trunking cards of the beginning of each slot in the outbound control circuit.

One trunking card and its associated repeater transmitter and receiver are assigned to operate on the intended full-duplex control communication line. Whenever the mobile station device is not actually participating in the communication (this communication takes place on the working line assigned to the other trunking card), the mobile station device always monitors its control line. Briefly, the control line is "slotted" (ie, multiplexed in a time division manner) and "outbound" control line signals are continuously transmitted from the control line transmitter. The time required for the mobile station device monitoring the control line to synchronize with the frame synchronization signal continuously transmitted to the outgoing control line, and for the mobile station device to synchronously receive and transmit the control line signal. To shorten.

In the preferred embodiment, a trunking card assigned to monitor operation of the control line emits a control line frame synchronization timing signal, which is placed on frame synchronization control line 520 (and externally). It is sent to the associated control line repeater transmitter for transmission over the direction control line). Referring to FIG.
The control line trunking card takes approximately 5 milliseconds (48 msec) from the start of each outgoing control circuit slot (the beginning of the slot is indicated by the transmission of a 16-bit Barker code).
Bit) later, it generates a sync pulse of approximately 833 microseconds in duration. Any trunking card can drive the frame sync control line 520 (since any line may be called to perform the function of the control line), but is currently assigned to the control line. Only the trunking card actually drives this line. The beginning of each control line slot is marked by a positive going pulse on frame synchronization control line 520.

Each other trunking card of the scheme 100 continuously monitors the frame synchronization control line 520, and the microprocessors of these other trunking cards control the signal processing function by pulsing this synchronization control line. Therefore, it is synchronized with the timing of the control line. The mobile station device was transmitted over the outgoing control line. When the command to switch the frequency to the working line is received, the mobile station equipment is already synchronized with the control line timing. All the working lines are synchronized with the control line by the frame synchronization control line 520, and the mobile station apparatus starts receiving the signal of the working line (which is loosely synchronized with the signal of the control line). Up to this point, the communication between the mobile station device and the transmitter and receiver of the operation line is set very quickly, and the mobile station device is synchronized with the independent operation line timing. The lengthy process of resynchronizing is not required.

Thus, the preferred embodiment scheme 100 uses common timing for all operating and control lines (and downlinks).

In the scheme 100 of the preferred embodiment, the frame synchronization control line 5
The duration of the pulse applied to 20 indicates whether the mode is normal mode or fail-soft mode.
The control line trunking card tests whether the primary point controller 510 has failed, and if a failure occurs (and an alternate point controller is unavailable or not provided), this trunking is performed. The card starts operating the scheme in fail-soft mode by increasing the duration of the sync pulse applied to the frame sync control line 520. In the preferred embodiment, the sync pulse has a duration of 833 microseconds (8-bit timing) during normal operation, and about 2.5 milliseconds (24-bit timing) when scheme 100 is failsoft. With a long duration.

Trunking and isolation using a normal design of electrical isolation circuit
The card is electrically isolated from the frame synchronization control line 520,
Thus, when any of the trunking cards fails, the possibility that the frame synchronization control line will fail is reduced.
If the control line trunking card does not apply a synchronization pulse to line 520 (or if the line itself fails), all other trunking cards will control their own independent synchronization timing generated within the control line. Use instead of the synchronization timing. When the working line is no longer synchronized with the control line, the access time of the working circuit increases, but a slight increase (from 280 ms to 320 ms) due to the loss of loose synchronization between the control line and the working line. Are invisible to the user of the mobile station device.

When the preferred embodiment scheme 100 starts operating in fail-soft mode, all trunking card multiplexers 506 select port C and the supporting serial link (BSL) is activated (in the preferred embodiment, During normal operation, the BSL does not transmit any signals). When the fail software is activated, the trunking card is the primary point controller 51
Stop sending and receiving signals to and from the trunking cards via the BSL, instead, signaling trunking and distribution in a manner distributed by the trunking cards. A control step constituting another operation is performed. If the BSL breaks down,
In the preferred embodiment, scheme 100 cannot operate in fail-soft mode, but it is very unlikely that both the BSL and the primary point controller (and the optional point controller) will all fail simultaneously.

When the method 100 is in the failsoft mode, the BSL exchanges control signals between the trunking cards. The control line trunking card is the master of the BSL, and no other trunking cards transmit on the BSL except to respond to polling messages from the control line trunking card. In the preferred embodiment, the message protocol of BSL is as follows.

Start bit (1) Data bit (8) Stop bit (1) BSL communication is half-duplex. In the preferred embodiment, only a few different types of messages are carried in the BSL. These messages are updated poll messages,
These are the general poll message, the downlink poll message, and the line allocation message. The working line is assigned by a line assignment message transmitted by the BSL. Update polling message and overall polling
The message is used to maintain the current line assignment information in each trunking card (especially in the control line trunking card), as well as when the downlink trunking card sends a Used to inform availability and other status information. Downlink polling provides a mechanism by which the downlink trunking card authorizes the BSL to send line assignment and line key release messages generated at the console.

Approximately 20 milliseconds after the beginning of each frame on the inbound control line, the control line trunking card determines whether there is an inbound message (eg, a line allocation request message generated by the mobile station equipment). If an inbound message is present, the control line trunking card waits until a message is received, which is the group call,
If an individual call or an emergency call line request message, respond to it (all other incoming messages are:
During failsoft, it is ignored in the preferred embodiment). In response to the line request message, the control line trunking card (if the working line is available) generates a line allocation message, transmits the line allocation message on the outgoing control line, and transmits the line allocation message to the BSL. To assign an operating line. The trunking card attached to the working line assigned by the line assignment message constantly monitors the BSL and, in response to the line assignment message transmitted from the BSL, communicates with the device of the requesting mobile station. Set.

As soon as the signal transmitted on that line has ended, the working line is "dropped" (ie, disabled). (In a preferred embodiment, after the mobile station device (or console) on the active working line releases the key, the "hang time" after which the working line remains assigned to a particular communication is: Very short, except when dealing with emergency calls of special priority.) In a preferred embodiment, the trunking card attached to the working line is used as soon as the communication message ends (or shortly thereafter). The key of the transmitter attached thereto is released, and processing of the incoming signal on the operation line is stopped. As a result, working lines become free and can be reassigned as soon as they no longer convey valid conversations,
The working line trunking card independently and autonomously terminates the service of the working line.

When scheme 100 is in failsoft mode, the control line trunking card uses polling to determine when the line has dropped and is available for reassignment. Using the update poll message,
Request responses from all active line trunking cards that have changed state since the previous polling message. The global polling message forces all lines to respond, and in the preferred embodiment is sent to all trunking cards at least once every two seconds. If any trunking card does not respond to the global polling message, the control line trunking card considers it inactive and removes it from use (in the preferred embodiment, it is actually physically Does not disconnect).

In the preferred embodiment scheme 100, there are 24 trunking cards and downlink trunking cards. In order to increase the response speed to polling, any given update polling message or whole polling message conveyed via BSL is directed to only half of the trunking cards (every polling will result in a downlink -Although the response from the trunking card is promoted). For this reason, not all operating lines are polled at once. Instead, the twelve low or high lines are polled with either an update poll message or a full poll message. In the preferred embodiment, one example of a typical poll message format is shown in FIG. 6B.

In the preferred embodiment, the BSL is time-shared among all trunking cards, and the signals it carries are:
Multiplexing is performed in a time-division manner to prevent data transmission conflicts. Each trunking card sends a response to polls directed against it for a predetermined period (slot) assigned to it. The inbound frame of the control line is divided into 15 equal slots, each having a duration of 1.778 milliseconds. If the control line trunking card determines that there is no inbound message, it sends that polling message (either a general polling or an update polling message) during slot 0 (see FIG. 7).

As can be seen from FIG. 6C (a diagram illustrating one example format of a poll response message), in the preferred embodiment, the poll response message is relatively short, with a parity bit, a response bit (always set in the poll response), and a response. A bit indicating whether the serving circuit is allocated or not (this bit is set if the circuit is allocated and not set otherwise), and a 4-bit field identifying the responding circuit Including only. The polling response of the downlink trunking card is such that in the preferred embodiment, the assigned / unassigned bit is set if the downlink trunking card has received a message from the console, otherwise it is set. Apart from not being done,
It has the same format.

In the preferred embodiment, the "Polling Type" field of the polling message (an example of which is shown in FIG. 6B) specifies the type of polling. That is, the update polling line 1-12 (3BH), the update polling line 13-24 (3DH), and the entire polling line 1-12 (2F
H) or the entire polling line 23-24 (2CH). Code 23H in this Polling Format field indicates downlink polling, and the code in this field
AAH indicates that the message contains the first byte of the line assignment message.

The trunking card 412 (1) -412 (12) responds to the update polling line 1-12 message or the global polling line 1-12 message in response to the slot 0 following slot 0 used to indicate the polling request. A polling response is added to each of the 12 (see FIG. 7). Downlink ・
The trunking card responds during the 13th time slot of the update poll or general poll for lines 1-12 and also during the 13th time slot of the update poll or general poll for lines 13-24. I do. Trunking cards 412 (13) -412 (24)
Respond during an update poll or general poll directed to lines 13-24 during time slots 1-12, respectively.

The global polling message requests that all trunking cards (as well as downlink trunking cards) attached to the line to which global polling is directed respond, and the control line trunking card ( And an operating line trunking card that generates a status signal below the audible range) can determine which trunking card is active. If any trunking card does not respond to the directed polling, the control line trunking card considers it unavailable. Line 1
Global polling messages directed to 12 and 13-24 are sent from the control line trunking card approximately once every two seconds.

The update poll message requires that all trunking cards except the control line that have changed state since the previous poll (update poll or global poll) respond. Update polling messages can be different types of messages (for example,
Message, downlink polling message or line allocation message), except in BSLs, which are used in every control line time slot. The response to the update poll message informs the failsoft mode scheme 100 which operating lines are dropped and available for reassignment.

Downlink polling messages are special messages, which are downlink trunking messages.
Card sends control message received from console to BS
Request to respond by placing on L. Method 1
When 00 is in normal mode and the point controller 410 is operating normally, the downlink trunking card exchanges messages between the point controller and the console 102. Console 102 is used by the originator to initiate, monitor, or otherwise join a call. During normal operation, a message generated by the console conveys to the downlink trunking card (in the preferred embodiment, this is the same as the trunking card for the control and operating lines), The ranking card simply passes the message to the point controller (such messages include line request messages, etc.). The point controller performs the task requested by the console message and then sends a response / confirmation message to the downlink trunking card for transmission to the console.

When scheme 100 is in failsoft mode, the downlink trunking card is
Stop communication with 0 and exchange messages between the point controller and the BSL instead. When failsoft, the format of the console messages supported may be somewhat more limited than the messages supported during normal operation. In a preferred embodiment, the downlink trunking card is accessed from the console during failsoft operation.
A line request message and a key release message can be transmitted to the BSL. FIG. 6D is a diagram showing an example of a format of a line request message transmitted on the downlink, and FIG. 6E is a diagram showing an example of a format of a line key release message transmitted on the downlink. The downlink trunking card also transmits messages (eg, key release messages and status information messages) from the BSL to the console 100.

During failsoft, downlink trunking,
When the card receives a line request or key release message from the console, the next full poll or update poll generated by the control line trunking card
Message and then respond to this poll message with an indication that a console message has been received. Shortly thereafter, control line trunking
The card emits a downlink polling message and the downlink trunking card allows the message it receives from the console to be placed on the BSL (see FIG. 8).

The control line trunking card monitors the downlink polling response to determine if a console at the originating center has requested a line assignment. This is because the control line trunking card must generate a line assignment message in response to a downlink line request message. As mentioned earlier, the working line trunking card in the working state
As soon as communication is over, the line is dropped independently, and when the next update poll or full poll message is received, the control line trunking card is simply notified that the line has been dropped. Each active line trunking card also monitors the downlink poll response to determine if the line should be dropped (unkeyed) at the console's direction. Control line trunking
The card issues a console line assignment message to assign a line, but responds to downlink polling, and in response to the line key release message generated by the downlink trunking card, deactivates the active line. What is released is the working line trunking card itself.

The downlink trunking card monitors all BSL traffic and continually updates the console with line assignment messages, line solicitation messages originating at the mobile station equipment and line up / down status. . The console uses this information to inform the console operator of the ongoing communication,
Confirm that the operation requested by the operator has been performed successfully.

FIG. 6A shows a line request message sent by the mobile station equipment received by the receiver of the control line repeater, or a line request message issued by the console issued by the downlink trunking card to the BSL. FIG. 10 is a diagram showing a format of an example of a line assignment message generated by a control line trunking cart in response to any of the following. The control line trunking card transmits the line assignment message on the outgoing control line, causing the BSL to send the line assignment message during the same time slot of the control line.
The line assignment message transmitted on the outgoing control line is
The devices of all mobile stations monitoring this control line receive and
Directs the specified mobile station device (or group of mobile stations) to the specified working line (the control line trunking card maintains a table of available lines and, based on the polling response, The table is constantly updated so that it can always determine which lines are available and assign available working lines).

Each working line trunking card monitors the line assignment message transmitted by the BSL, and the trunking card attached to the affected working line sends a confirmation message in response to the operation line assignment message, In response to the line assignment message of the outgoing control line, the terminal listens to the handshake communication transmitted by the mobile station device switched to the newly allocated operating line, and then listens to the mobile station device on the operating line. Support communication between FIG. 9 is a diagram showing the relative timings of applying the same line allocation message to the line request message, outgoing control line allocation message, and BSL.

Referring to FIG. 6A, control line trunking
When the line assignment message generated by the card is a polling byte (code AAH), the message type field (when in failsoft, since the method 100 does not support any special messages, it is typically code 08
H), a nibble indicating whether the line assignment was requested by the console or by the mobile station equipment, MT-
A code field, communication type field, logical identification number of the calling device (if the mobile station device has requested a call), group of mobile stations (not just individual mobile station devices)
, A field containing the selection of the assigned line (1-24 in the preferred embodiment), a called group ID field indicating a group of called or individual mobile station devices, The hang time field, a standard / special bit, which specifies the length of time that the working line trunking card must keep the working line allocated after the communication is over (in the preferred embodiment, always a special Bit indicating whether the incoming message should or should not be repeated (the value of this bit is related to the type of communication; eg, communication between the console and the individual requires repetition) Communication between the console and the group requires repetition), and an 8-bit parity field.

When the scheme 100 is in failsoft mode, only a subset of the different types of normally available line assignment messages can be supported. In the preferred embodiment, three types of channel line messages are supported during failsoft. Individual call messages (set up communication between the console and the individual mobile station device or between two individual mobile station devices), group call messages (console and the group of mobile station devices). And communication between all mobile station devices within a group) and emergency messages (same as individual or group messages except that the working line hang time is extended) FIGS. 10 to 13 are flowcharts showing an exemplary program control process performed by the trunking card of the preferred embodiment to implement the failsoft mode. Next, the operation of the fail-soft mode method 100 will be described with reference to these flowcharts.

FIG. 10 illustrates the steps taken by each trunking card to determine whether scheme 100 is operating in normal mode or failsoft mode.
It is a flowchart of the control process of the example program. Each trunking card determines what function it is performing by first testing the state of the internal switch (decision block 602). In the preferred embodiment, all trunking cards are the same for increased compatibility (and for other benefits). In the preferred embodiment, each trunking card has a manual three position switch within it, which is used to tell the trunking card whether it is associated with a control line, working line or downlink. To instruct. Decision block 602 simply determines the position of this switch in the preferred embodiment. If desired, the manual switch may be replaced by a software-managed register or storage location, the contents of the register automatically swapping trunking card functions without technician intervention. Can be changed under software control based on various conditions.

The control line trunking card is one card that can initiate a switch to failsoft mode in the preferred embodiment scheme 100. The control line trunking card determines whether the primary point controller 410 is operating correctly (e.g., four consecutive points that the control line trunking card expects via a dedicated RS-232 parallel communication line). A test is made to determine if the controller response is "bad", i.e., absent or unrecognizable (decision block 604). If the control line trunking card determines that the primary point controller 410 is operating properly, it will subsequently pulse the frame sync control line 520 for a normal duration (approximately 833 microseconds in length). Apply (block 606) and execute a "normal" mode control line software routine (block 608) (this routine is performed, inter alia, from the receiver of the repeater to which the control line trunking card is associated. Sends all received messages to the parallel point controller 410 and performs the functions designated to be performed by the primary point controller via control signals sent to it via the associated RS-232 port. Instruct them to do so). On the other hand, if the decision block 604 determines that the primary point controller is not operating properly, the control line trunking card will apply a wide synchronization pulse (eg, 3 × 833 microseconds long) to the synchronization line 510. Start to apply and thus
Inform all other trunking cards that the method 100 is now in failsoft mode and begin executing the failsoft software routine (blocks 610 and 612). The details of this routine will be described shortly with reference to FIG.

The working line trunking card determines whether the scheme 100 is in fail-soft mode by testing the duration of the sync pulse received over the sync line 520 (decision block 614). The working line trunking card executes the "normal" working line software routine when scheme 100 is not in failsoft mode (block 616), and failssoft operation when the scheme is in failsoft mode. Execute the line software routine (block 618). Similarly, the downlink trunking card tests the duration of the pulse on sync line 520 to determine whether scheme 100 is in fail-soft mode (decision block 620), and the scheme is "normal". When operating in mode, execute the "normal" downlink software routine (block 62).
2) If the scheme is operating in failsoft mode, execute the failsoft downlink software routine (block 624).

In the preferred embodiment, the memory 504 of each trunking card contains copies of normal and failsoft control line software routines, normal and failsoft operating line software routines and normal and failsoft downlink software.・ Routine is stored (however, one control line trunking is actually performed)
Only the card performs the control line routine and only the downlink trunking card performs the downlink routine).

FIG. 11 is a flowchart of the control steps of an exemplary program in the failsoft control line software routine of block 612 of FIG. The control line trunking card waits for the beginning of the control line frame (decision block 630). The timing of the control line frame is controlled by conventional software or hardware oscillators or timer circuits provided on the control line trunking card. At the beginning of the next control line slot (frame), the control line trunking card determines whether it is necessary to generate a line assignment message in response to the line solicitation message received during the previous slot. Yes (decision block 632). If a line assignment message should be generated, control line trunking
The card controls its associated repeater transmitter to send the assignment message on the outgoing control line and also applies the circuit assignment message to the BSL (block 634,
6A and 9). Thereafter, it is tested whether the control line trunking card has received an incoming message (decision block 636). After sending the line assignment message, the control line trunking card simply has the beginning of the next control line slot. This is because by the time the control line message ends, the current slot is almost over (in the preferred embodiment, there is no point between receiving the control line message and sending the line assignment message). A three-slot delay is introduced to give the controller time to process the line request, which is also maintained in fail-soft mode to maintain system timing).

If a control line message comes from the mobile station device (decision blocks 636, 638), the control line trunking card receives the incoming control message (block 640) and determines whether it is a line assignment request message (decision). Block 642). During fail-soft mode,
Only individual, group or emergency line assignment request messages are handled by the control line trunking card; all other inbound control line messages are ignored.

If there is an incoming control line message, the control line trunking card checks if the downlink trunking card has a console message to put on the BSL (just by testing the last poll response). Test (decision block 644). If the downlink trunking card has a console message on the BSL, the control line trunking card generates a downlink poll (block 64).
6, receive the message placed on the BSL by the downlink trunking card in response to downlink polling (block 64).
6), then determine if the console message is a line allocation request (decision block 642) (control line trunking card ignores console key release message).

If either the console or the mobile station device has requested a line assignment (tested by decision block 642), the control line trunking card will return to the fail-soft mode if it is stored in its memory 504. In the meantime, determine whether there is a line available for allocation by testing the line allocation table, which is constantly updated by polling and response (this memory update involves a dedicated RS232 parallel signal path during normal mode). The trunking card also uses the line allocation information supplied from the point controller 410 via the PC to transfer the current state and the line allocation information to the internal state even if the trunking card needs to switch to the fail-soft mode. As if you remembered it.) If the line is not available (decision block 648), an internal flag is set and the line allocation message to be generated by block 634 during the next control line slot is:
Indicates that all lines are busy in the line field (number
(See Fig. 6A) (block 650). If there is a line available for assignment, the control line trunking card sends a line assignment message during the next control line slot (block 634).
In preparation, the allocated line is stored in an internal buffer used to construct the line allocation message shown in FIG. 6A (block 652). Thereafter, control returns to decision block 630 to wait for the next control line slot.

If there is no need to generate an outgoing line assignment message during the current control line slot, no incoming control line messages, and the downlink trunking card has not received a console message, the control line trunking card (Eg, by testing the value of an internal timer to see if about two seconds have elapsed since the last full poll message was generated)
It is determined whether it is time to generate a full poll message (block 654). At the time of the global poll message, the control line trunking card applies the global poll message (for either the low or high line) to the BSL (block 656) and responds to the global poll message. And updates the "busy" table stored in control line trunking card memory 504 which is used to indicate which lines are active and which lines are not in use (block 65).
8). The control line trunking card considers all trunking cards that do not respond to the global poll message as inactive and does not attempt to assign the line associated with them as the active line. However, if a trunking card that did not previously respond to a global polling message starts responding to such messages again, the control line trunking card updates its busy table so that its associated line is Indicates that it is operating again.

If decision block 654 determines that it is not the time of the global poll message, the control line trunking card generates an update poll message for either the low or high side circuit (block 660) (in the preferred embodiment). Update poll message is alternately generated for the lower and higher lines), if there is a response to the update poll message, decode it and generate the last full poll or update poll message. If there is a line allocated thereafter, its line allocation table (its memory 50
4) (block 662).

FIG. 12 is a flowchart of an exemplary program control process performed by the working line trunking card when the method 100 is operating in the failsoft mode (block 618 of FIG. 10). The working line trunking card waits for the next sync pulse on sync line 520 and then B
Look for SL poll message (blocks 672,674,
676). If a global poll message is present, the working line trunking card will
A determination is made as to whether the message was addressed to him (decision block 678). (For example, if the message is line 13
If it is intended for −24 and the working line trunking card is attached to line 11, there is no need to respond to the global poll message. ) Global polling directed to the working line trunking card
If a message is received, the working line trunking card responds to this poll (block 680). At the same time, the working line trunking card analyzes the responses generated by the other trunking cards and updates the internal "busy" line state table accordingly (block 682). In the preferred embodiment, the status information of the scheme (eg, whether the scheme is in normal mode or
Mode, which line is assigned, which line is in use), along with other information, are continuously transmitted via the active line, and the current line of the scheme Update the device of the mobile station operating on. Therefore, in the preferred embodiment, (control line trunking
All trunking cards (not just cards) maintain a busy table and a line allocation table.

If the working line trunking card determines that an update poll message has been generated by the control line trunking card (block 674), the update poll message is directed to the line bank of which it is a member. If the state has changed since the last update poll or global poll message directed to it, then respond to the update poll message (blocks 684,686).

If the control line trunking card generates a downlink polling message, the working line trunking card is the only trunking card that responds to downlink polling, No need to respond. However, the downlink trunking card may apply a console generated key release message instructing the working line to drop from the line. Thus, all working line trunking cards monitor the response of the downlink poll and if the downlink responds with a command instructing the working line trunking card to drop the line, the working line trunking card will respond. The ranking card controls the repeater's transmitter to transmit the dot string and then stops transmitting altogether (decision block
688, block 690).

Finally, if the control line trunking card generates a line assignment message during the current control line slot (testing at decision block 692), the working line trunking card sends the line assignment message to this working line trunk. If a ranking card has been selected, transmission begins (block 694), and the caller's logical identification code is stored in its memory 504 (block 696), and the associated operation continues for the duration of the call. Monitor the operation of the transmitter and receiver of the line repeater. The working line trunking card updates its line state table after every operation it performs, and then has the beginning of the next control line slot (blocks 698,682,670).

FIG. 13 is a flow chart showing the steps of an example program performed by a downlink trunking card when the method 100 is in failsoft mode (block 624 of FIG. 10). The downlink trunking card waits for the beginning of the next control line slot (decision block 702), and then determines whether the control line trunking card has placed a full or update poll message on the BSL (decision block). 704,706). If the polling message is generated by the control line trunking card, the downlink trunking
The card monitors the response to polling messages generated by the various operating lines and informs the console of any state changes (eg, the operating line has been assigned but has not been released). In the preferred embodiment, the downlink trunking card manages a first-in-first-out queue in its memory 504 and provides several messages for the console at the opportunity for the console to receive and parse the messages. Until is received, it can be temporarily stored (block 708).

The downlink trunking card also manages an inbound queue containing line request and key release messages generated by the console. (Decision block 710
If there is a console message in the inbound queue, the downlink trunking card will be polled (regardless of whether the polling message is a full poll or an update poll message) Control line trunking, indicating that there is a console message to be placed on the BSL (regardless of the bank of the line to which the message was directed)
Respond to the card's polling message (block 712, see FIG. 6C). For a full poll message, the downlink trunking card is BS
If there is no console message to put on L, it responds to indicate that it is operational (decision block 714, block 716).

When the control line trunking card generates a downlink polling message (decision block 71)
8) The downlink trunking card scans its inbound queue to determine if a key release message is stored (block 720) (the key release message is a line allocation in the preferred embodiment). Higher priority than solicitation messages). If a key release message originated at the console is stored in the queue, the downlink trunking card generates a line key release message and applies it to the BSL (block 722) (see FIG. 6E). . If a line allocation request message sent from the console is stored in the queue, the downlink trunking card generates a downlink line request message (see FIG. 6D) and applies this message to the BSL ( Block 724).

Control line trunking card (decision block 726
If a line allocation message, rather than a polling message, is generated (as tested), the downlink trunking card monitors this line allocation request message and communicates its contents to the console via the downlink queue, The logical ID of the individual or group of the called party is stored (block 728).

FIGS. 21 to 23 are time diagrams showing examples of signals transmitted and received by scheme 100 during operation of this scheme in fail-soft mode. These communication sequences and timings are basically the sequences and sequences generated by a normally operating system as described in pending U.S. Patent Application Serial No. 056,922, filed June 3, 1987. The timing is basically the same. In general, a user of a mobile station device communicating with the scheme 100 does not see any difference in the operation of the scheme between the normal mode and the failsoft mode. Since the special calling function is not supported in the failsoft mode, the special call request generated by the mobile station device is ignored. Via the control line and the operation line, the method 100
State information that is constantly transmitted by the
Contains a bit indicating that the system is failsoft, so that the user does not initiate a special call during the failsoft operation (or the mobile station device itself is in the failsoft mode). Sometimes, they may have the intelligence to prohibit the initiation of all calls other than individual, group and emergency calls.)

FIG. 14 shows the signals generated by scheme 100 during a fail-soft mode operation when a mobile station originates a call to another individual mobile station. At A, the control line trunking card controls its associated repeater transmitter to transmit a continuous stream of control messages, which all inactive mobile stations monitor and receive. During this time, if no incoming control line radio message is detected by the control line trunking card during the control frame, the control line trunking card will start approximately 20 ms after the beginning of the control line frame. And poll the working line and the downlink trunking card via the BSL. Up to 12 working line trunking cards and downlink trunking cards respond with status information and control line trunking cards.
The card records the activity of the various lines as well as the need to collect console messages that the downlink trunking card stores.

At B, the mobile station device that wants to make an individual call transmits an allocation request message on the control line in synchronization with the received control line message. The individual call assignment request message indicates the logical ID of the called mobile station device together with other information. During normal operation of scheme 100, the control line trunking card simply sends this solicitation message to one.
It simply passes through to the next point controller 410. However, during the failsoft operation, the control line trunking card itself responds in C with a pair of line assignment messages sent over the outgoing control line at C, along with the BSL.
Send a line assignment message to the working line trunking card and the downlink trunking card via.

The trunking card for the selected working line processes the new call starting with D by sending an acknowledgment message. The originating mobile station (which has, by this time, shifted to the working line frequency in response to a line assignment message sent over the outgoing control line)
Receives an acknowledgment message sent over the working line, and starts transmitting E from the 384 bit dot as well as the subsequent audio. At F, the working line trunking card receives the dot transmitted from the mobile station, and controls the mobile station device to release the audio from the device.
Send a key mute release message. In the meantime, all active line trunking cards update their line allocation tables to reflect this new line allocation. If the updated information is a message below the audible range, G
Is transmitted via the operating lines in all operating states. The downlink trunking card receives the line assignment message via the BSL and informs the console about this line assignment.

At I, the transmitting mobile station releases the key and sends a non-slot type key release message to the working line receiver. In response, the working line trunking card controls its associated transmitter to transmit 896 to 2816 bit dots, thus causing all mobile stations to drop from the line. At this point, the working line trunking card has autonomously released the working line. The working line trunking card responds to the next control line polling message that it is unassigned, and the control line trunking card (as well as all other working line trunking cards) responds to this operation. The line assignment table is updated to reflect the release of the line. The downlink trunking card monitors the polling response of the working line trunking card and sends a key release message to the console to indicate that the conversation has been interrupted.

FIG. 15 is a diagram showing signal timings as an example of signals generated in response to a console transmitting a call to an individual mobile station device. At A, the control line sends a continuous stream of control messages, all inactive mobile stations receive it, and if the control line trunking card does not detect an incoming control line radio message, the control line Trunking card polls other trunking cards. At B, the console attempting to place an individual call sends an individual call message to the downlink trunking card. method
During 100 normal modes of operation, the downlink trunking card simply passes this individual call message to the primary point controller 410 so that it is properly processed. However, in fail-soft mode operation, the downlink trunking card responds to the next poll generated by the control line trunking card with a poll response indicating that downlink polling is needed. I do. At this time, the control line trunking card generates downlink polling,
The trunking card sends a call request message to the control line trunking card via the BSL. At C, the control line trunking card generates a line assignment message, sends this message on the outgoing control line, applies this message to the BSL, and the trunking card for the assigned working line Process is started. The trunking card of the selected working line activates its associated transmitter, all other working line trunking cards update the circuit allocation table accordingly, and the downlink trunking card: Notifies the console that the line has been allocated.

In response to receiving the outgoing control line assignment message, the called mobile station device switches to the assigned working channel, and receives a confirmation message from the working channel at D. When the conversation is over, the console sends a key release message at I to the downlink trunking card.

In response to the next poll generated by the control line trunking card, the downlink trunking card indicates a need for downlink polling, and typically the control line trunking card is almost immediately This happens. In response to this downlink poll, the downlink trunking card applies a console key release message to the BSL, and all downlink trunking cards, including the working line trunking card, that are handling the working line to be dropped. The working line trunking card monitors this. In J, the working line trunking card is 89
By transmitting a dot of 6 to 2,816 bits, all mobile station devices are dropped from the line. Control line trunking
In response to the card's next poll message, the working line trunking card responds with no allocation. The downlink trunking card decodes the poll response message and sends a message to the console confirming that the working line is in a dropped state.

The group of calls originated by the mobile station device and the console cause the system 100 to generate communications that are substantially identical to those shown in FIGS. 14 and 15. The main difference is that all mobile stations in the group of calls, rather than individual mobile stations, switch to the working line assigned in D and receive the confirmation message. The control line trunking card maintains, in its memory 504, a list of individual and group mobile station devices already assigned to a line, and a mobile station device for a group already assigned to a line. In response to the call originated from the, an individual call signal is generated on the outgoing control line, and this signal is used by the calling mobile station device to participate in a group of conversations already being performed on the operating line. To do so.

FIG. 16 is a diagram showing an example of communication performed in a fail-soft mode in response to an emergency group call started by the mobile station device. At A, the control line trunking card causes a continuous stream of control messages to be transmitted by the repeater transmitter attached to it, and all inactive mobile stations receive this while performing routine polling functions. Accomplish. A mobile station device which is going to make an emergency group call, synchronizes with the control line message received at B,
An assignment request message is transmitted on the inward control line. The control line trunking card responds by sending a line assignment message from the associated transmitter to select the group of calls and passing this line assignment message at C.
Put on BSL.

All mobile stations in the group of the called party immediately switch to the assigned working line, and the trunking card of the assigned working line makes a key connection in response to the line assignment message transmitted from the BSL. . Handshake is performed at D, E and F. At G, active mobile station devices on other active lines receive the line assignment message below the audible range and update the state of scheme 100 with those mobile station devices. When the transmitting mobile station releases the key, it sends a key release message at I. The working line trunking card keeps track of the delay of the hang time from the key release of the transmitting mobile station device, thus keeping the line ready for an emergency call. When the hang time expires, the working line sends a dot at J, causing the mobile station device to drop from the working line, return to the control line, and then release the key on the transmitter. In response to the next poll from the control line trunking card, the working line trunking card responds with no allocation, and uses this to use the control line trunking card and other working line trunking cards. Along with updating the line allocation table on the card, the downlink trunking card also uses it to inform the console that the working line is no longer allocated.

Fault Tolerance Assessment According to the initial functional specification of the scheme, the scheme can be designed to be fault tolerant, using five steps performed as an interactive process. This is shown in the flowchart of FIG. The purpose of the following description is to focus on the breadth and depth of the decision required at each stage.

Step 1: Objective of Fault Tolerance First, create a specification of fault tolerance. This is an objective measure of the evaluation when the design is completed. More importantly, it assists the user in estimating the economic, managerial and human resources needed to manage and support the scheme, as well as the necessary business contracts and various failures caused by failures. Operating modes, and the need for contingency planning for various emergencies.

 An example of a specific part of the specification is as follows.

Coverage (of faults) There are two definitions of fault tolerance in this term (neither should be confused with RF coverage).
The coverage ranges from 0 to showing how much of the error can be automatically detected (first definition) and then automatically avoided by reconstructing the form (second definition). It is a number of 1. It is clear that the first definition is an inevitable subset of the second definition, and it may be ambiguous what constitutes a successful automatic evasion by formal restructuring. This is preferred. The development of microprocessors and calculators has made it easier to achieve 90% coverage figures, and with considerable engineering design effort, 95% coverage figures can be achieved. It is possible. Numbers in excess of 99% are achievable, but with a considerable engineering burden. Note that the coverage numbers are difficult to corroborate, and double redundancy usually results in poor coverage of failures, especially when dealing with computers.

Redundancy Versus Slow Degradation While some applications require full redundancy, most applications can take advantage of "slow degradation". The former invests in computers and other equipment idle playing waiting for a failure to occur, but with little extra benefit to the end user. Typically, we agree to give up some if not all features when a failure occurs, in order to invest the capital that would otherwise be invested in other areas (eg, radios).

Failure modes Failure forces the scheme into various modes. It is important for the application that the "acceptable" failure mode is truly appropriate. For example, if the engine fails,
Converting an aircraft at 35,000 feet to a bus is clearly a mismatch (of course, doing so on the ground is acceptable). A more subtle mismatch is the conversion of the full-load trunk scheme to the overloaded normal scheme because one computer has failed.

4MTBF-Average time between failures This is the average length of time the scheme will continue to work if the scheme is functional. The various numbers of the MTBF may be meaningful, depending on the characteristics of the different modes of operation (e.g. MTBF of individual parts whose failure is considered to lose at least 1/2 line, MTBF of the scheme, Or the trunk capacity of the scheme MTBF).

MTTR-Average Time to Repair This is the average amount of time it takes to repair a failure if one has occurred. As with MTBF, individual parts
From MTTR to MTMT of line, MTTR of computer or MT of various features
Until the TR, there are various numbers of interest.

Step 2: Determining feature priorities The design of the scheme by the seller and the choice of the scheme by the procurement agency should take into account the communication issues to be addressed in order to prioritize the various functions that the scheme should perform. Some features are absolutely important, others are highly desirable, and others are only for convenience. By ranking the various features, a slow degradation of the scheme can be designed. In fact, this process is key to matching the failure mode with the targeted end use in the field.

An obvious example is when the control logic circuit of one line breaks down in a 20-line system. In this case, trunk operation is more important than this one line,
The end user will opt for trunking over 19 lines, rather than switching to normal failsoft mode with 20 lines.

In the trunk communication system, there is a tendency that reliable and efficient communication is prioritized without changing the operation mode for the user. This is a normal fail soft
Schemes designed to go into mode simply lose features (eg, interconnect and dynamic group reorganization), but maintain trunk operation with no visible changes to the end user Equations, which mean undesirable. The former ignores user demand so as to simplify engineering problems by placing an burden on the ultimate user. The latter adds to the burden on the design engineer of the scheme, adding to the difficulty of the engineering problem, but protecting the ultimate user demand.

 The following is an example of a list of preferred feature priorities.

1) Mobile station-mobile station communication 2) Outgoing console operation 3) Trunk operation (full speed access) 4) Priority scanning 5) Diagnostics of line logic 6) Call queue 7) Dynamic grouping Reorganization 8) Patch 9) Interconnection 10) Background diagnosis 11) Validation of user Step 3: Defining the architecture Defining an architecture that is tolerant to failure is another consideration for the design task. It is in addition. The main issues are functionality, modularity, hardware / software combination and feasibility. But
This time, interdependencies, distribution of functions, redundancy and coverage / recovery algorithms must be considered. These additional problems add considerably to the complexity of the scheme as well as the processor load.

One consequence of a sound architecture design is modularity. Aside from cases where the coupling of modularity of functions with modularity of hardware and software becomes even more important, a design that is
I can say that. The goal is to minimize the interdependencies between the various modules of the scheme, as well as the number of hardware modules required for any particular feature. This minimizes the probability of losing features when a fault occurs, and maximizes the probability that the process of reconstructing the form will be successful. Similarly, "common"
Reducing hardware minimizes the likelihood that a single point of failure will halt operation of the overall scheme.

Usually, hardware and software are considered separately, but in designs that are fault tolerant, they are very interdependent. The distinction between "hardware architecture" and "software structure" becomes less clear at the system level (when evaluating the scheme, do not consider both without understanding the trade-offs between the two) ).

However, it calls attention to one particular software problem. Software modules are extremely important.
In a fault tolerant manner, a type of reconfiguration capability is achieved by having different hardware modules perform similar functions. Thus, the modularity of the software guarantees the simplicity, predictability and reliability of the code by forcing one type of software to exist for any particular function.

Error propagation is another problem. When a failure occurs in the scheme, it can spread (eg, a failed part of the computer bus may stop the entire computer). In the trunk system, this suggests modularity and distribution processing. For this reason, it is not considered that all control functions are arranged on a single-bus computer.

In particular, in the trunk system, all of these problems suggest that communication and control of the line be put on each line, and control of the whole point is put on the point controller. In this way, each line becomes a self-contained device, providing the advantages of the features, as well as the ability to provide some form of reconfiguration. This also removes the signal processing load from the point controller, so that the point controller can be a general purpose computer, hardware off-the-shelf, a multitasking operating system and high standards. Language. This further enhances the reliability of software and hardware.

The next issue with architecture is coverage. The purpose of coverage is to detect failed modules so that they can be removed from service. Coverage should be achieved by both internal (self-diagnostic) as well as inter-module diagnostic algorithms. Inter-module testing of control modules should not use extra hardware and should use only existing hardware interfaces. On the other hand, in a test between functional modules other than control such as RF, specific hardware is often required.

In a trunk scheme, the diagnosis should be such that the effect on the point controller load is negligible. Performing the diagnostic function may result in more load and therefore less processing that can be provided to the final user characteristics. This is another reason that any yaw custom controller can be inadequate. In a preferred embodiment, monitoring of the diagnostic peripherals and all other diagnostic functions are performed in standard form.
Performed by a background software routine via the RS-232 interface hardware block. Real-time monitoring effectively loads the point controller and only places a load on the processor if a fault is detected or if the point controller has nothing else to do.

As part of the design of coverage, failures are ranked based on both the likelihood that they occur and the consequences. Therefore, an algorithm for detecting the most probable fault is designed. It is not possible to completely cover any, for example, all modules. However, the results should be used when assessing the coverage of each hardware and software component for the probability of failure and assessing the suitability of a given architecture. This maximizes coverage for the fault with the highest likelihood, but also takes into account the consequences of failing to detect when a fault has occurred. In this regard, one must consider the required type of reconstruction algorithm and the resulting complexity. This is because if the scheme cannot be reconstructed when the scheme fails, even if the coverage is complete, it is useless.

In the trunk system, in addition to the RF failure, the most likely failure is the point controller or its peripheral device. In the preferred embodiment, the consequences of not detecting a peripheral failure are minimized (since the hardware is not centralized in the same box as the center of the scheme). As another precautionary measure, any peripheral failure for false diagnosis, which could have serious consequences if not detected, has an alternate path for the point controller to verify. . The same can be said for a failure of a line logic card. Numerous other processors are watching the point controller. Because these processors can behave autonomously, incorrect diagnosis of a point controller by one processor affects only that processor and not the other parts of the scheme.

Healing is the pinnacle of defining an architecture.
This is the point at which the goal of step 1, the determination of the priority level of step 2, the duplication of functions between the modules of the scheme, and the full range of coverage operate. The mode of operation of the scheme must define and detail which features / functions are available under various types of reconfiguration modes due to failure. Once the various modes have been defined, switching between the modes must be determined. Usually, this requires an intermediate state. All states (technically, each mode of operation is considered a state) must be carefully examined and defined in this regard. It is imperative that the oscillating behavior of state switching be avoided, and that when a module diagnoses itself or another module defective, the decision only affects itself.

There must be a methodology to verify the process of reconstruction of coverage and type. Now is the right time to create such a test procedure.

The preferred embodiment is an excellent trunk-based solution that is fault tolerant. Line faults can be detected from three paths (point controllers, RF monitors that monitor the output of the repeaters in a multiplexed fashion, and point controllers with or without significant load). A test device that can independently test the operation of the trunking card. Peripheral device failures remain local to the peripheral device, and only the function of the failed peripheral device is lost. If the downlink is down (this is the interconnection between the point and the originating center), use one line (as opposed to paying for the unused redundant telephone line every month) It can be removed from the state and used as a downlink. If the point controller fails, control of the trunk operation is taken over by the control card of the repeater. The trunk operation continues, and the user does not notice the difference in the line access time. If the logic of another line fails after the point controller fails, the scheme can still be reconfigured.

Step 4: Cost / Resource Utilization Next is when the scheme is still promising and it is time to determine if some of the design goals set earlier are actually worth the cost. Engineered fault tolerance schemes have very little, if any, play hardware whose sole purpose is to provide redundancy. Expensive play hardware suggests that the initial design was inadequate or that the design constraints were too severe. If the ability to tolerate failures appears to be costly, more effort should be directed to the design of the architecture of Step 1 and the design goals should be tactically relaxed.

The architecture should check with reference to the feature priority determination set in step 2. Does the formal reconstruction mode, with its relative probability of occurrence, truly adhere to the design criteria indicated by this list? Is the prioritized list itself practical, given the additional understanding gained during the design process? Of course, the design process returns to this point repeatedly.

The complexity of the architecture should be examined to determine if any risks or feasibility issues exist.
Measuring complexity can be difficult. Block diagrams, state diagrams, and flowcharts may be over-simplified to concentrate complex problems into one block, combine states, and emphasize derivative details. These may not represent a relationship between the probability of failure and the degree to which the scheme detects it and successfully reconstructs the form. Without the Markov model, the problem of reliability is virtually impossible to test and the reconstruction of the form is completely unreliable.

Step 5: Modeling To determine whether the scheme meets the fault tolerance goals selected in Step 1, a model of the scheme can be created. The Markov chain is an excellent means, as it gives the MTBF and MTTR figures and also gives the probability that the scheme is in each possible state. It is based on:

(1) A component failure is modeled using a probability distribution of an exponential function. This ignores infant mortality, but proves to be a good model if the device is burned.

(2) The failure rate for a set of parts is also exp (A) × exp
Since (B) = exp (A) + (B), the distribution is also an exponential function. Failure rates can be calculated using a military handbook for the individual components that make up the assembly, or can be determined by performing life tests.

(3) P (fault in period t, t + T) = exp (− / T).
This does not lose precision in the final result, just approximating / T.

(4) Theorem: Every non-reducible aperiodic Markov chain of every finite state has a marginal distribution. This limit distribution is the only equilibrium distribution.

(5) In the equilibrium state, -P (in state k at time t) is the same as P (in state k at time t + T).

(6) It can be proved that the worst case solution of the steady state is the number of MTBF (this is because the method is at time t = 0).
Represents the maximum failure rate that can occur when operating on

(7) The sum of the probabilities of leaving a state must be equal to 1 (including the probability that a state itself exists to return to itself).

(8) The sum of the probabilities of all states is equal to one.

(9) The MTBF of the method is the reciprocal of the failure rate.

(10) The operation state is a state where the system can be used (for example, a trunk operation is performed). The non-operation state is a state where the method cannot be used.

The failure rate of the (11) method is the sum of the probability of entering an inactive state from an arbitrary operational state. See formula below.

With these 11 facts, a Markov model can be constructed, and a solution can be found using linear algebra. An example of two modules is shown in FIG.

Modules “x” and “y” both have different failure rates and the same repair rate. The probability of changing to various states in any short period is indicated by an arrow. 4
The process of solving the probabilities in each of the two states is as follows.

When you solve this The interpretation of the state can be considered in two ways as shown below.

If in series, the scheme requires both modules to be active. This means that state 1 is the only operating state. In parallel, only one of the two modules is required for the scheme to be active, meaning that states 1, 2 and 3 are active.

Obviously, for the series case, the failure rate is the sum of the failure rates of the two modules. In fact, the model predicts that exactly. On the other hand, the failure rate in the parallel case is not so obvious, and without a model, it is not known what the failure rate will be.

With this relatively simple model, you can see how complex the solution is. By substituting the failure rates with values for various failure rates and repair rates, the simultaneous equations can be solved using the off-the-shelf / normal software package. With a large model, a fairly sophisticated software package is available for a complete analysis of reliability.

To demonstrate the usefulness of the Markov model, a 10-line model with the design shown in Fig. 2 was created and compared with a design that did not tolerate failures using redundant point controllers. The results shown below show that trunk operation could be lost in a failure-tolerant scheme with redundant controllers, but in a preferred embodiment failure-tolerant scheme Rather than the potential loss of
It turns out that it is three times larger.

Having described what is considered to be the presently preferred embodiment of the present invention, the claims are not limited to the embodiment described, but include the novel features and advantages of the present invention. Any changes, corrections,
And / or cover equivalent arrangements.

[Brief description of the drawings]

FIG. 1 is a general explanatory diagram of the trunk radio relay system of the present invention, FIG. 2 is a simplified block diagram of a central control point (and a satellite receiver point) of the trunk relay system of FIG.
The figure is a simplified block diagram showing the architecture of the main controller's general point with respect to the central control point, and FIG. 4 is a simplified line trunking card used in the various lines of the central point architecture shown in FIG. FIG. 5 is a block diagram, FIG. 5 is a diagram showing the timing of the synchronization control line in the method of FIG. 2, and FIGS. 6A to 6E are communications for messages sent via the support serial link shown in FIG. FIG. 7 is a diagram showing an example of a protocol, FIG. 7 is a diagram showing the timing of polling messages and responses of a supported serial link as an example of the system of FIG. 2, and FIG. 8 is an example of the system of FIG. FIG. 9 is a diagram showing the timing of downlink polling and response of the assisted serial link of FIG. 9, and FIG. 9 is a diagram showing the timing of a line assignment message of the assisted serial link as an example of the method of FIG. FIGS. 10 to 13 are flowcharts showing an example program control process performed by the trunking card of the system shown in FIG. 3 to perform the operation in the fail-soft mode. FIGS. 15 and 16 show the system of FIG. 2 during the failure software operation, during the transmission of an individual call by the mobile station device, an individual call by the control console and an emergency group call by the mobile station device. FIG. 17 is a schematic diagram showing an example of communication messages exchanged between the control and operation line relay station, the control console 102, and the mobile station device. FIG. 17 shows steps taken to design a system that is tolerant to failure. FIG. 18 is a diagram showing a two-module type Markov model according to the method of the present invention. Explanation of main symbols 300, 302, 304, 306: RF relay station 400, 402, 404, 406: trunking card circuit 410: primary point controller

────────────────────────────────────────────────── ─── Continuation of the front page (56) References JP-A-58-31624 (JP, A) JP-A-58-182937 (JP, A) JP-A-55-132137 (JP, A) (58) Investigation Field (Int.Cl. ⁶ , DB name) H04B 7/14-7/22 H04B 7/24-7/26 102 H04Q 7/06-7/38

Claims (16)

(57) [Claims] 1. A communication method in a trunk RF communication repeater architecture, wherein the communication method is temporarily assigned to a remote RF transceiver in response to a digital RF control line and a digital control signal sent through the digital control line. In the communication system in which a plurality of trunk RF operation lines are provided and the repeater architecture includes a relay device and is connected to a centralized point controller, the repeater architecture breaks down the centralized point controller. A communication method in a trunk RF communication repeater architecture, characterized in that when there is or is not present, the relay device is operated in a fail-soft mode for trunk-connecting the plurality of RF operation lines. 2. The communication method according to claim 1, wherein: (a) in a normal operation mode, the plurality of RF lines are used for use by the remote RF transceiver under the control of the point controller. And (b) in the fail-soft mode, the plurality of operating lines are controlled based on a control of a repeater coupled to at least one of the control line and the one of the plurality of operating lines. The communication method in a trunk RF communication repeater architecture, further comprising temporarily allocating for use by a remote RF transceiver. 3. An RF control circuit, comprising: a plurality of trunk RF communication lines for temporarily assigning a remote RF transceiver in response to a digital control signal sent through the RF control line; In a trunk RF communication repeater architecture that includes a repeater and is connected to a centralized controller that performs operations on at least some trunk connections, when the centralized controller is faulty or absent, the relay is A trunk RF communication repeater architecture comprising: a device for operating the repeater architecture in a fail-soft mode for trunk connection of a plurality of RF lines. 4. A trunk RF communication repeater system comprising an RF control line and a plurality of trunk RF communication lines, wherein said repeater system responds to a digital control signal sent through said RF control line. Wherein the plurality of trunk RF lines are temporarily allocated for use by a mobile RF transceiver, and wherein the repeater system includes a plurality of repeaters and is connected to a centralized controller. The trunk RF communication repeater system, wherein the system operates in a mode in which the plurality of repeaters maintain trunk connection capability when the centralized controller fails or is not present. 5. A trunk RF communication repeater system comprising an RF control line and a plurality of trunk RF communication lines, wherein the repeater system responds to a digital control signal sent through the RF control line. A plurality of trunk RF lines temporarily allocated for use by a mobile RF transceiver, and wherein the repeater system includes at least one repeater and is connected to a centralized controller; The system includes a device for operating the repeater system in a mode in which the repeater maintains trunk connection capability when the centralized controller fails or is not present.
Communication repeater system. 6. A trunk RF communication system comprising an RF control line and a plurality of trunk RF communication lines, the communication system comprising: a plurality of trunks in response to a digital control signal sent through the RF control line. A centralized trunking processor that normally temporarily allocates an RF line to an RF transceiver, and wherein the communication system includes:
A trunk RF communication system including a failsoft device that operates in a failsoft mode in which a repeater of the communication system maintains trunking capability without the need for a backup centralized trunking processor. 7. A land mobile radio public trunking RF communication system comprising an RF control line and a plurality of trunk RF operation lines, wherein said communication system performs at least one trunking-related operation. A trunking device, comprising: (a) temporarily switching the RF working line in response to a digital control signal sent through the RF control line for use by a mobile and / or portable RF transceiver; (B) controlling the communication system to perform at least a second trunking-related operation, wherein the centralized digital trunking device In case of failure or non-existence, the above-mentioned second trunking-related operation is not performed. Including Fueirusofuto apparatus for operating a relay of the communication system to perform a first trunking relationship operation, land mobile radio public trunking RF communication system. 8. A trunk land mobile RF communications repeater system for transmitting and receiving on a plurality of RF lines, each of said RF lines having a repeater coupled thereto, wherein one of said RF lines is Including a digital control line for transmitting a digital control signal having a baud rate of at least 9600 to a mobile and / or portable RF transceiver, wherein the relay device transmits and receives a trunking control signal between the relay devices, and the relay device transmits at least one of the RF lines. Trunk terrestrial RF communication repeater system that can control several trunk connections. 9. A trunk land mobile RF communications repeater system for transmitting and receiving on a plurality of RF lines, wherein each of said RF lines has a repeater coupled thereto, and wherein one of said RF lines is Including a digital control line for sending control signals to mobile and / or portable RF transceivers, for temporary use by at least one of the repeaters and by a requesting one of the mobile and / or portable transceivers. A trunk land mobile RF communication repeater system characterized by selecting an empty RF line for the purpose. 10. A digital control RF circuit and a plurality of operation RF circuits.
A method for reliable communication in a trunked wireless repeater system with lines, wherein said working lines are temporarily used by individual wireless units identified by digital control signals on said control lines. (A) providing a system capable of operating alternately in a normal mode and a fail-soft mode; and (b) in said normal mode, a trunk connection of said plurality of operating lines. Communicating a trunking control signal between the central processing unit and the plurality of trunking processing units coupled to the RF control line and the plurality of RF operation lines, wherein: c) controlling the trunk connection of the plurality of operating lines by the plurality of trunking processing devices in the fail-soft mode; In doing so, the trunk connection in the fail-soft mode is performed independently of a trunking control signal from the central processing unit, and a trunking control signal is communicated between the plurality of trunking processing units. A method of communicating in a trunk wireless repeater system, comprising: 11. The method of claim 10, wherein:
A method for communicating in a trunk wireless repeater system, further comprising performing, by the trunking processor, real-time signal processing functions associated with the control line and a plurality of operating lines. 12. The method of claim 10, wherein:
The controlling (c) communicates control signals in the trunk radio repeater system, including passing control signals between the trunking card processors over a digital link connected therebetween. Method. 13. A trunk wireless repeater system having a dedicated digital control line and a plurality of operating lines, wherein said operating line is temporarily suspended by an individual wireless unit specified by a digital control signal on said control line. Assigned to be used, wherein the repeater system alternately operates in a normal mode and a fail-soft mode, wherein the repeater system operates in the normal mode, and is connected to the control line and a plurality of operating lines. A central processing unit that controls trunk connection of the plurality of operating lines via the trunking processing device, and the plurality of trunking processing devices operate in the fail-soft mode, and perform trunking control by the central processing device. Cooperate and communicate with each other to control the trunk connection of the plurality of operating lines without the need for Trunked radio repeater system which comprises a number of trunking processor. 14. The repeater system according to claim 13, wherein said trunking processing device coupled to said control line cannot detect a signal generated by said control processing device. A trunk wireless repeater system including an apparatus for operating the system in the fail-soft mode. 15. A trunk radio frequency repeater system, comprising: a control line repeater for exchanging a digitally encoded RF control signal with a mobile radio transceiver through a dedicated RF control line; Some of the signals cause the mobile radio transceiver to communicate on an RF working line, and at least one working line repeater for exchanging RF signals with the mobile wireless transceiver through the RF working line; And a device for controlling the working line repeater to automatically take over the function of the control line repeater when a failure occurs. 16. A digitally trunked connection having a dedicated digital RF control line and a plurality of operation lines, the operation line being temporarily assigned in response to a digital control signal sent through the control line. In such an RF communication system, the method of operating the above communication system is to perform centralized control of the RF operating line by a centralized computer during normal operation, and to perform distributed control of RF operating line trunking when the centralized computer fails. A method of operating an RF communication system that includes operating in an airsoft mode.