Method and apparatus for limiting a transmission in a dispatch system

[Field of invention]

The present invention relates to communication systems in general, and more particularly to methods and devices for limiting transmission in dispatch systems.

[Background of invention]

Dispatch communication systems are known. Dispatch communication systems are often used for dispatch calls, which are semi-double. In such a dispatch call, one user is sending or talking, and all other users on the dispatch call or in the group participating in the dispatch call are receiving or listening. In general, a talking user must let go of the channel in order for another user to access the channel and talk to another user. This is a problem when the talker, or the user acting as the talker, is reluctant to let go of the channel and allow another user to talk, or cannot let go (equipment malfunction). Present. It is known that timers are used to allow other users to request and access channels as the timer elapses, thus responding to groups of dispatch calls. However, users who are not currently talking do not know when the timer has elapsed. In addition, there are many situations in which a single timer with a single value does not provide satisfactory performance for changing the user of the system. Obviously, there is a need for more flexible ways to limit transmissions in dispatch communication systems.

[Detailed Description of Preferred Embodiment]

Attachments (the same reference numerals refer to the same or functionally similar elements throughout the individual drawings; incorporated into the specification and form part of the specification, with the following detailed description). Is helpful in further exemplifying the various embodiments according to the invention and explaining all the various principles and advantages according to the invention.

As an overview, the present disclosure relates to systems, methods, and devices or devices that provide communication services to users of such systems and devices, and more specifically in a dispatch environment. It relates to techniques for ensuring adequate access to such services. More specifically, various invention concepts and principles implemented in the system controller or user device and the method of the system controller or user device, and various related factors relating to the dispatch call and the user of the dispatch call. Explains and describes various invention concepts and principles that moderately limit transmission in dispatch communication systems and dispatch calls, all in consideration of the convenience and benefits of users or consumers of such dispatch services. Will be done. Dispatch systems, equipment, etc. rely on certain types of connections, and thus networks, which can be any combination of wired and wireless networks. Specific targeted networks can be organized in a generally structured way based on wide area networks (WANs) or local area networks (LANs) and should be suitable for conservative bandwidth communications. .. The preferred form of access to this network by the user equipment and its associated users is systems such as the Integrated Digital Enhanced Network (IDEN) and networks that provide services to various public safety organizations. It is expected to be via a wireless protocol or an extension thereof that can be seen in conventional dispatch networks and the like.

As further described below, the principles and combinations of principles of various inventions are used in favor of limiting transmissions resulting from user carelessness or equipment failure. Therefore, various problems associated with known systems that ignore this problem or that rely on certain inflexible techniques are mitigated. Thereby, when these principles or equivalents of such principles are utilized, a fair and reasonable method of controlling the duration of transmission from the user is advantageously facilitated.

The present disclosure is provided to further illustrate in the possible manner the best forms of making and using the various embodiments according to the invention. This disclosure does not limit the invention in any way and is further provided to enhance understanding and recognition of the principles of the invention and the advantages of the invention. The present invention is defined exclusively by the appended claims. The appended claims include all amendments made while this application is pending and all equivalents of the issued claims.

Use of related terms such as first and second, top and bottom, if any, uses one entity or action and another entity or action, not necessarily the actual between such entities or actions. It is further understood that no such relationship or order is required or implied, and that it is used solely for distinction. Most of the functions of the invention and many of the principles of the invention are best implemented by or in software programs and instructions. Those skilled in the art are disclosed herein, despite considerable effort in some cases, as well as many design choices motivated by, for example, available time, current technology, and economic considerations. Guided by concepts and principles, it is believed that such software instructions can be easily generated with minimal experimentation. Therefore, in order to be concise and to minimize any risk of obfuscating the principles and concepts according to the invention, further description of such software, if any, of the principles and principles used by the preferred embodiments We will limit ourselves to what is essential in terms of concept.

A simplified, representative system-level diagram showing a communication system that can act as a dispatch communication system or a system suitable for supporting dispatch calls is described and described with reference to FIG. This figure shows System 100. System 100 includes controller 103 and audio replicator 105ADP (Audio Duplicating Processor). ))including. These controllers 103 and voice replicator 105 are interconnected and are also connected to the distributed network 107. The distributed network 107 includes a radio access network (not shown) that supports distribution to one or more cells 109, 111. The distributed network 107 is shown to have 802.11 functionality via the 802.11 access point (AP) 113 and wireline distribution capability via the Internet telephone 115. Generally, a network element is known to have a controller responsible for scheduling communications and resources such as cell sites, traffic channels, and controlling access to the network by various communication units. ADP replicates or wraps the sound or traffic from the talker, making that sound or traffic available to each of the other users involved in the dispatch call. However, as we describe, various changes to the controller according to the principles and concepts described herein are required to achieve the intended transmission restrictions.

Multiple communication units such as cellular handsets, messenger devices, personal digital assistants (PDAs), portable computers, etc., each preferably having voice communication capabilities and preferably having multiple related users, individuals, or parties. Note that, device, or subscriber device is also shown. Specifically, this figure shows an IP phone 115 with user 116, a handset or cellular phone 117 with user 118, a handset 119 with user 120, a handset 121 with user 122, and a handset 123 with 802.11 functionality with user 124. There is. User 118 is shown trying to join the conversation, and user 120 is shown making an extended statement of duration. These users or individuals are connected to network 107 with various other entities or resources or users not shown in a variety of commonly known ways via their respective communication units or devices as described above. ..

The illustrated user and associated unit or device can be thought of as a group participating in a dispatch call. This group can be defined in various known ways. In general, a dispatch call can be (sent) at one time by 1 user. A human being, at which time all other users are in a listening (receiving) state, a half-double call. This dispatch call is typically set up and managed via controller 103. The user who wants to talk sends a talk request to the control channel. The controller issues or grants talk rights over the control channel at the appropriate time. Usually, this appropriate time includes some time after the current talker releases the channel due to the abortion of transmission. Usually, the talk request is initiated by the user activating a push-to-talk (PTT) button in one of the communication units. Allowing or notifying a talk request includes an audible signal on the user's unit or device. The unit is then allowed to start transmitting and releasing the PTT button releases the traffic channel. Semi-duplex mode offers certain advantages, such as the ability to use the same channel at cell site 109 for both units 117, 119.

A flowchart of an embodiment of a preferred method of limiting transmission in the dispatch communication system of FIG. 1 will be described and described with reference to FIG. In this method 200, the duration of the transmission from the user 120 is extended, for example, due to the user 120's wonder, but probably due to the malfunction of the device of the communication unit 119. However, it limits transmission in the dispatch communication system. This method starts at 201 and indicates that at 203, the first user or first communication unit, such as user 120 or unit 119, is granted the first talk right. The normal process of dispatch calls is shown in 205, 206, and 207. Here, the second talk request is received at 205 from another communication unit or user and is rejected at 206 as long as the first user has the right to talk. After being rejected at 206, the process continues to loop back to 205, and if there is no request from another user, the process moves to 207. In other embodiments, the process moves to 207, regardless of requirements. At 207, the process checks whether the first unit has relinquished talk permission or talk rights. If not abandoned, 209 indicates that the first user evaluates whether the first user should still have, retain, or retain the first talk right. If it should still have, the process loops back to 205 and continues the inspection as described above.

As further explained below with reference to FIG. 3, in 207, if it is determined that the first user has waived the talk right or permission, or by evaluation, the first user retains the talk right. If it is determined that it should not be, 211 determines that the first talk right is no longer applicable if the evaluation determines that the first talk right is no longer applicable to the second user or other user. Indicates to notify. This notification positively indicates to other users that they can access the traffic channel if they want to access the traffic channel. At this point, if the permission has not yet been relinquished, we see this as true until the second user requests the second talk right, so the first user keeps the talk right. Please note that it is allowed. The process or method checks at 213 whether a talk request from the second user has been received, and if so, at 217 the first talk right is no longer available. It indicates that the first talk right is terminated when it is determined by the evaluation of 209 that it cannot be applied, and the second talk right is granted to the second user in response to the talk request. If no talk request from the second user has been received, 215 checks to see if the first unit has relinquished permission for the channel or first talk right, and if not, this. Note that the method loops to 213. If so or after 217, this method ends. Notifying other users at 211 is also the first of all other users of the dispatch call, or of all other users of the dispatch call who have never been active talkers during the dispatch call. All other users of the dispatch call that have a higher priority than that of the user, or all other users that have certain properties such as priority, rank, and specified length of talk time, or the dispatch co. It can include notifying a user who has a clear reserved time to talk on the phone, or a user whose request is denied while the first user has the right to talk. This notification can be given to the appropriate group or subgroup at the same time, for example, in the order of highest priority to lowest priority or in the order in which the talk request is rejected. This information is available to the controller from its database, apart from specific methods that need to be determined in advance, or specific methods that need to be determined in real time in some way, such as through a moderator.

The techniques used to notify users or notify users can be achieved in a variety of ways, where a particular technique will probably be specific to the system communication unit. For example, to notify a user of an IP-enabled handset, such as units 115 or 123, the controller can send control commands with an IP datagram addressed to the IP address of that handset, while the cellular handset 117, For 119 and 121, the controller can send control commands on the control channel associated with the traffic channel used for the call. Alternatively, the controller may notify one or more users by mixing audible information into the acoustic traffic after or before the acoustic traffic from the talker is turned back at the APD105.

With reference to FIG. 3, a more detailed flowchart of the evaluation unit 209 of the method of FIG. 2 will be explained and explained. This method is shown to start at 301 with a "NO" input from 207 and evaluate at 303. This evaluation further includes detecting the transmission characteristics from the first user and thereby presuming the intention of the first user to waive the first talk right. Detecting transmission characteristics means that the device is malfunctioning due to a device failure in the transmission from the first user, or perhaps the device is placed in a state where the PTT button remains activated. You may detect a long silence that means you are, or you may recognize words such as "OVER", "OVER and OUT", "COME BACK", etc. that indicate the end of transmission. Well, or may detect a high level of excitement by the first user, as indicated by interjections, fast-spoken words, or loud spoken words. One of ordinary skill in the art would be able to anticipate other speech characteristics indicating that the transmission would be terminated.

In any case, if no characteristic is detected, the 305 checks or determines if the timer has exceeded or passed a predetermined threshold. The value of this timer or threshold can be experimentally determined to provide satisfactory results, or it can be changed according to the specifications of a particular dispatch call. For example, a call is a routine If the assignment) is given to various users, a relatively short time is expected. On the other hand, if the dispatch call follows comparing many opinions from many users, a long timer duration is expected. In any case, when the timer expires, 307 shows an evaluation that takes into account the various properties associated with the first user. These properties associated with the first user may include, for example, the priority of the first user, the relative priority of the first and second users or other users, or the first user. It may include one or more of the accepted talk durations. For example, a boss probably has a higher priority than a new police officer. Users who schedule dispatch calls can be allowed longer talk times than other participants, and so on.

If none of the properties appear to exhibit any special treatment, 309 indicates further considerations. Specifically, 309 is, for example, one of the number of other users in the dispatch call, the number of times the first user was talker during the dispatch call, and the number of times the other user was talker during the dispatch call. Or, it indicates that two or more are further considered for evaluation. For example, if the dispatch call has only two users, it may be appropriate for one of the users to send longer. On the other hand, if one user is the main talker, it may be beneficial to allow other users to talk. Similarly, if a user does not speak much, it may be appropriate to listen to what the user wants to say as soon as possible. If other properties associated with the user indicate so in 307, or other considerations from 309 do so, 311 acknowledges by adding a given amount of time to the timer. Indicates that the talk time given is adjusted.

In 305, if the timer has not elapsed, the path of "NO" is followed to proceed to 313. At 313, it is checked to get input from the moderator of the dispatch call. The moderator can be, for example, the boss or the person who scheduled this call. The input is actually considered to be "let someone else talk". Finally, if the characteristic indicating the end of transmission is not detected at 303, the timer has not elapsed at 305, and the moderator input has not been received at 313, the first user has the right to talk. Allowed to maintain, follow "YES" pass 315 to 205. If the trait is detected at 303, or if the timer elapses without property 307 or other considerations 309 indicating an increase in talk time 305, or if such properties or considerations mean adjustments. After that adjustment in 311 or if the moderator indicates so in 313, follow path 317 of "NO" to 211 and the first user wants to talk. Expected to end.

Input from the moderator can probably be obtained in a variety of ways with specific techniques depending on who the moderator uses or what form the moderator takes. For example, the moderator indicates that if you are using an IP-enabled handset such as communication units 115, 123, you should exit the talker using the user interface of that handset, i.e. by pressing the # key. It can generate an input or signal. The handset then sends control commands in the IP datagram addressed to the controller's IP address. If the moderator uses a cellular handset, such as communication unit 121, that handset is initiated by the moderator through the user interface and sends control commands over the control channel associated with the traffic channel used for the call. can do. Alternatively, the moderator may use a dispatch console station (not shown) connected to controller 103 via network 107. The console's user interface allows moderators to generate the inputs used in 313.

A block diagram of a preferred embodiment of controller 103 that limits transmission in a dispatch communication system will be described and described with reference to FIG. As described above, the controller 103 is used in the dispatch communication system and is arranged and constructed so as to limit transmission in the dispatch communication system. The controller includes transceiver 403. Transceiver 403 is connected to and from network 107, 401, and further interconnected to processor 405. The transceiver 403 is preferably a wireline transceiver such as an acoustic transceiver in addition to an Ethernet® transceiver suitable for packet data communication. The processor 405 is interconnected with an operator input / output 407 such as a conventional computer monitor or keyboard (not shown). A processor is a conventional reasonable high performance microprocessor-based unit, having one or more microprocessors.

Processor 405 includes memory 409 containing various software routines and instructions as well as data. As a result of these software routines, instructions and data being executed by the processor, the controller controls and manages the communication system and implements a method similar to the above for controlling transmissions suitable for dispatch calls. Memory includes various known RAMs, ROMs, EEPROMs, and magnetic memory elements such as hard drives. Software routines in memory include operating system 411, various operating variables and parameters, and date 413, scheduling routine 415, talk right grant 417, grant termination 419, notification 421, rating 423, characteristic detection 425, properties and parameters. Includes user database 427, timing 429, other considerations 431, and various other software routines and information 433 not relevant to this specification but apparent to those skilled in the art.

During operation, processor 405, in cooperation with the transceiver, sets up dispatch calls between user groups or between communication units associated with those users, then responds to talk requests and uses authorization routine 417 to create a first. The dispatch call generated as a result of granting the first talk right to one user and providing or sending it through the control channel and then granting the first talk right to the first user is monitored and evaluated routinely. The 423 is used to evaluate whether the first user should retain the first talk right, and if the evaluation routine determines that it is appropriate, the first talk right is no longer applicable. Acts to notify other second users. Despite this notification, the controller or processor allows the first user to retain the talk right until the second user requests the second talk right. Notifications are, for example, all other users of the dispatch call, other users of the dispatch call that have a higher priority than the first user, other users of the dispatch call that were not active talkers during the dispatch call, or Notified to other users with specific properties.

At some point, the controller, specifically the processor, works in concert with the transceiver to receive a talk request from a second user or another user and evaluates that the first talk right is no longer applicable. Sends a message to terminate the first talk right or authorization via routine 419 and gives the second talk right to the second user via routine 417 in response to a talk request. Allow and provide. The evaluation that decides that the first talk right should be withdrawn or terminated, or that it can be done, detects the transmission characteristic from the first user via routine 425, thereby. , As a result of estimating the intention of the first user to waive the first talk right as described above. This property includes one or more of the long silence of the transmission from the first user, the recognition of the word meaning the end of the transmission, or the high level of excitement by the first user. The processor and detection routine 425 requires a known speech recognition algorithm to perform some of these functions. It is also possible to determine whether the timer has exceeded a predetermined threshold value via routine 429 by evaluation by the controller or processor. Another factor in the evaluation is, or can be, a property consideration associated with the first user via routine 427. This consideration is one or more of the first user's priority, the relative priority of the first and second users, or the talk duration granted to the first user. Etc. In addition, the processor may also consider other or considerations via routine 431 when deciding whether a first user should retain the first talk right. Other such considerations or considerations are the number of other users in the dispatch call, the number of times the first user was talker during the dispatch call, or the number of times another user was talker during the dispatch call. home One or more of them, etc. In addition, the processor, in cooperation with the transceiver, obtains input from the dispatch call moderator indicating whether the first user should waive the talk right or waive the talk right within a certain amount of time. Can be done.

A block diagram of a communication unit suitable for use in the system of FIG. 1 will be described and explained with reference to FIG. The communication unit or device of FIG. 5 is arranged, constructed, or operational in a dispatch communication system so that transmission from the communication unit or device is restricted. The communication unit includes a transceiver 503 connected to the antenna 501 and interconnected to the processor 505 if the unit is a wireless communication unit. Processor 505 is further connected to user interface 507. Transceivers are generally known, whether they are wireless (eg, radio frequency) transceivers or wired transceivers such as IP wired telephones. Processor 505 is a microprocessor-based unit that can include one or more general purpose microprocessors as well as one or more digital signal processors. All of these are arranged in the traditional way. The user interface 507 is also known and typically includes an acoustic transducer including a microphone 515 and a speaker 517, in addition to some form of display device 509, a keyboard or keypad 511 having a push-to-talk button or PTT button 513. ..

The processor further includes a memory 519 composed of known memory elements such as RAM, ROM, EEPROM and possibly magnetic base memory. This memory contains various software routines or instructions or codes that, as a result of being executed by the processor, behave as intended by the processor in the dispatch communication system. Most of these routines are not specifically shown, but will be apparent to those skilled in the art. Of course, memory is operating system 531, operating variables, parameters, and data 523, talk request routine 525, routine 527 that recognizes permission for talk requests, and various other things that are not relevant here and cannot be described too much. Includes routine 529 of.

When the communication unit is a unit involved in transmission that is unusually long for the situation or condition, such as the talker in FIG. 1, the unit generally behaves as follows. The processor works in concert with the transceiver, uses routine 523 to send a talk request, and in response to this talk request, uses routine 527 to receive and recognize the grant of the first talk right. At some point later, if the unit does not waive the talk permission or talk right and the evaluation of whether the communication unit should maintain the first talk right is negative, the communication unit Receive a message from the controller to end the first talk right.

The communication unit is one of the units constructed to participate in a dispatch call, or a unit that does not have talk rights at some point during excessive transmission from another unit. In addition, if the controller, or specifically the processor, works in concert with the transceiver to receive a notification that a talk request is allowed while another unit is transmitting and wishes to talk. When the transmission from the other communication unit is no longer privileged, it sends a talk request that preempts the previous permission of the talk right to the other communication unit, and then receives the permission of the talk right. For example, if the priority of the communication unit is higher than the priority of the other communication unit, the relative talk frequency of the communication unit is lower than that of the other communication unit, or the moderator is the other communication unit. In one or more cases where the preemption of the talk right is approved, this talk request preempts the permission of the talk right to the other communication unit.

The devices, processes, and systems described and described above, as well as the principles of their invention, are intended and to alleviate the problems caused by prior art dispatch call duration limiting techniques. Become. This prior art dispatch call duration limiting technique uses a constant inflexible timing technique that ignores the call or ignores everything else, inconvenient and discouraging users of the system. is there. By using the principles and concepts described above that limit transmissions only under the right circumstances, effective, efficient and easy-to-use dispatch calls are facilitated, thus contributing to user satisfaction and greatly. While reducing wasted time by groups of people, channels are not unnecessarily tied up. By giving the principles, concepts, and examples described above, one of ordinary skill in the art would be able to implement other alternative procedures that also provide contextual, faster and more efficient call restriction procedures. The appended claims are expected to cover other such cases as well.

This disclosure does not limit the true intended fair scope and intent of the invention, but is to illustrate how and how to use the various embodiments of the invention. The above description is not intended to be inclusive and is not intended to limit the invention to the exact forms disclosed. In view of the above teaching, it can be changed or modified. Embodiments (or embodiments) provide the best illustration of the principles of the invention and its practical application, and those skilled in the art will be able to utilize and study the invention in various embodiments. Selected and described for use with various changes suitable for a particular use. All such modifications and variations, as construed in accordance with a fair and legally impartial entitlement, are patents of this application within the scope of the invention as defined by the appended claims. Included within the scope of the invention, which can be amended while pending, and within the scope of all equivalents of the invention.

<figref num="1">A simplified and representative diagram showing a dispatch communication system suitable for supporting dispatch calls.</figref><figref num="2">FIG. 5 is a flowchart of an embodiment of a preferred method of limiting transmission in the dispatch communication system of FIG.</figref><figref num="3">A more detailed flowchart of some of the methods in Figure 2.</figref><figref num="4">A block diagram of a preferred embodiment of a controller that limits transmission in a dispatch communication system.</figref><figref num="5">A block diagram of a preferred embodiment of a communication unit suitable for use in the system of FIG.</figref>