Method and apparatus for providing a dispatch call

FIELD OF THE INVENTION

[0001] The present invention relates generally to providing a dispatch call, and in particular, to a method and apparatus for providing a dispatch call within a communication system.

BACKGROUND OF THE INVENTION

[0002] Unlike standard interconnect services provided by today's cellular systems, a dispatch group call service enables a user to communicate with a group of people simultaneously and instantaneously, usually by depressing a push-to-talk (PTT) button. Using a cellular communication system's standard interconnect services would not allow such a call to occur instantaneously since either a telephone number would need to be dialed for a three-way call or arrangements would need to be made to setup a conference call.

[0003] Likewise, the dispatch service enables a user to communicate with another user quickly and spontaneously. This feature is ideal for two people who are working together but are unable to speak with one another directly such as two people working in concert but in different parts of a building. Where a wireless telephone call is more appropriate for a conversation, short messages between two people as they work are better facilitated by the dispatch call service.

[0004] During a typical dispatch call, over-the-air channels assigned to the call are maintained until an inactivity timer (hang timer) has expired. In particular, a base station monitors the dispatch call, and if there exists no activity for a period of time, the base station, in collaboration with other infrastructure elements, will drop the over-the-air channels broadcasting the call to the remote units. If activity resumes, the base station will then reassign channels to the conversation, and again monitor for inactivity.

[0005] One feature provided to dispatch call participants is the ability to opt-out of a dispatch call. For example, a particular user may be a member of a group, yet have no interest in participating in a particular group call (e.g., the user is in a meeting, Church, . . . , etc. and does not want to be bothered). In this situation, the user may instruct the communication system that it does not wish to participate in the call. The communication system will then drop the channel providing the call to the remote unit and the user will no longer participate in the particular group call. During subsequent group calls (at later times), the user will again be pulled into the call.

[0006] Although the above procedure allows a user to leave a particular call and remain a participant in subsequent calls, a problem can arise when the hang timer is allowed to expire and the current call continues after such. In such situations, a different call is set up having the original participants. A user that has chosen to leave the original group call will again be pulled into the call, and must again chose to leave the call. Therefore, a need exists for a method and apparatus for providing a dispatch call within a communication system that reduces the chances that a user will be pulled back into a call that they have chosen to leave.

BRIEF DESCRIPTION OF THE DRAWINGS

[0007]FIG. 1 is a block diagram of a communication system in accordance with the preferred embodiment of the present invention.

[0008]FIG. 2 illustrates a prior-art dispatch call.

[0009]FIG. 3 illustrates a dispatch call in accordance with the preferred embodiment of the present invention.

[0010]FIG. 4 is a block diagram of a base station in accordance with the preferred embodiment of the present invention.

[0011]FIG. 5 is a flow chart showing operation of the base station of FIG. 4 in accordance with the preferred embodiment of the present invention.

[0012]FIG. 6 is a flow chart showing operation of the group call database in FIG. 1 in accordance with the preferred embodiment of the present invention.

DETAILED DESCRIPTION OF THE DRAWINGS

[0013] To address the above-mentioned need, a method and apparatus for providing a dispatch call is provided herein. In accordance with the preferred embodiment of the present invention, a second (session) timer is introduced in addition to the first (hang) timer. A base station monitors a dispatch call, and if there exists no activity for a period of time greater than the hang-timer threshold, the base station will drop the over-the-air channels broadcasting the call to the remote units. However, all active participants to the call will be maintained until the session timer expires. Once the session timer expires, the talk-group participants will be reset to their original members.

[0014] Because the session timer holds the associated book keeping (i.e., the modified group call participants) for a time greater than the hang timer, the call channels can be dropped without dropping the associated session members. This greatly reduces the chances that a user, who has opted out of a call, will again become a participant in the call. Additionally, because the user is again added to the call group after the session timer has expired, the user will be involved in future calls for the group.

[0015] The present invention encompasses an apparatus for providing a dispatch call. The apparatus comprises a controller coupled to a first and a second timer wherein the first timer causes a channel to be dropped after a first threshold and the second timer causes participants to the dispatch call to be reset after a second threshold.

[0016] The present invention additionally encompasses a method for providing a dispatch call. The method comprises the steps of providing the dispatch call to a first plurality of remote units, and receiving an option message from a remote unit, wherein the option message comprises instructions to exclude or include the remote unit in the dispatch call. The dispatch call is provided to a second plurality of remote units in response to the option message and all over-the air channels to the dispatch call are dropped. After dropping the channels, a request is received to again provide the dispatch call and in response to the request, the dispatch call is again provided to the second plurality of remote units.

[0017] The present invention additionally encompasses a method for providing a dispatch call within a communication system. The method comprises the steps of providing the dispatch call to a first plurality of remote units, receiving an option message, wherein the option message comprises instructions to exclude or include a remote unit in the dispatch call, providing the dispatch call to a second plurality of remote units in response to the option message, and determining that a first timer has expired. Once it has been determined that the first timer has expired all over-the-air channels are dropped. When a request is received to provide the dispatch call it is determined if a second timer has expired and the dispatch call is provided to the first plurality of remote units if the second timer has expired, otherwise providing the dispatch call to the second plurality of remote units.

[0018] The present invention additionally encompasses a method for providing a dispatch call. The method comprises the steps of receiving a request to provide the dispatch call, receiving a first list of call participants, providing the dispatch call to members of the first list of call participants, receiving a message from a remote unit, wherein the message is a request by the remote unit to either opt in, or opt out of the dispatch call, in response to the request, modifying the first list to create a second list of call participants, providing the dispatch call to members of the second list of call participants, detecting inactivity in the dispatch call, dropping over-the-air channels in response to the inactivity, receiving request to again provide the dispatch call, and again providing the dispatch call to members of the second list of call participants.

[0019] Finally, the present invention encompasses a database comprising a master list containing a first set of group-call participants for a group-call identification and a session list containing a second set of group-call participants for the group-call identification.

[0020] Turning now to the drawings, wherein like numerals designate like components, FIG. 1 is a block diagram of communication system <b>100</b> in accordance with the preferred embodiment of the present invention. In the preferred embodiment of the present invention, communication system <b>100</b> utilizes the Motorola Inc. iDEN system protocol, but in alternate embodiments communication system <b>100</b> may utilize other analog or digital cellular communication system protocols capable of supporting group call operation. Such protocols include, but are not limited to, the next generation Global System for Mobile Communications (GSM) protocol, or the CDMA system protocol as described in “Personal Station-Base Station Compatibility Requirements for 1.8 to 2.0 GHz Code Division Multiple Access (CDMA) Personal Communication Systems” (American National Standards Institute (ANSI) J-STD-008).

[0021] Communication system <b>100</b> includes group-call database <b>112</b> coupled to Radio Access Networks (RANs) <b>121</b>-<b>122</b>. Each RAN <b>121</b>-<b>122</b> comprises a plurality of remote, or mobile units (MUs) <b>113</b>-<b>118</b>, at least one Base Transceiver Station (BTS) <b>101</b>-<b>102</b>, and at least one Dispatch Application Processor (DAP) <b>119</b>-<b>120</b>. Although not shown, RANs <b>121</b>-<b>122</b> additionally include well known network elements such as Mobile Switching Centers (MSCs), Centralized Base Station Controllers (CBSCs) in a circuit switch network, or such as Multiple Control Unit (MCUs) in a CDMA system, and Radio Network Controller (RNCs), Gatekeepers (GKs) and GateWays (GWs) in a packet switch network. It is contemplated that network elements within communication system <b>100</b> are configured in well known manners with processors, memories, instruction sets, and the like, which function in any suitable manner to perform the function set forth herein.

[0022] As shown, base stations <b>101</b>-<b>102</b> are capable of communicating with remote units <b>113</b>-<b>118</b> via over-the-air channels <b>103</b>-<b>108</b>, respectively. Each over-the-air channel <b>103</b>-<b>108</b> preferably comprises a unique frequency/timeslot (or code in a CDMA system), however, in alternate embodiments (e.g., multicast scenarios) channels <b>103</b>-<b>108</b> may be shared among remote units <b>113</b>-<b>118</b>. In the preferred embodiment of the present invention base stations <b>101</b>-<b>102</b> are capable of providing dispatch services to remote units <b>113</b>-<b>118</b> over channels <b>103</b>-<b>108</b>. When providing dispatch services, communication system <b>100</b> maintains in its group-call database, master list <b>123</b> containing information on which remote units <b>113</b>-<b>118</b> belong to which groups. This information typically is stored in a persistent way. To enable the preferred embodiment of the present invention, the communication system <b>100</b> also maintains in its group-call database, a session list <b>124</b> to keep track of the actual participants each group call in progress. A session list can be stored in volatile memory, which allows for an economical implementation.

[0023] When a remote unit initially presses the push-to-talk button, a PTT_on message is sent to the serving base station, causing a set of resources to be allocated. When the remote unit releases the push-to-talk button, the remote unit sends a PTT_off indication to the base station the resources remain dedicated to the remote unit for some period of time (hang time, e.g., 12 seconds). During the time when the user is not depressing the push-to-talk button, the base station transceiver subsystems send idle frames to preserve the link power control. In this way, when the remote unit user subsequently depresses the push-to-talk button, the link is completely established and immediately responsive. This type of operation accommodates the natural use of a dispatch system.

[0024] The hang timer is used to detect the end of a call. When no remote user depresses the push-to talk button before the hang timer expires, the infrastructure considers the call terminated, and releases the resources for use in other calls. When occasionally a remote user depresses the push-to talk button after the hang timer expires, the infrastructure sets up a new call, allocating a new set of resources. For efficient use of resources, a shorter hang timer value should be used. The preferred embodiment of the present invention enables the use of very short hang timer values (e.g., 4 seconds), while alleviating the problem of rejoining remote units to a particular call they opted out of.

[0025]FIG. 2 illustrates a prior-art dispatch call. As shown, there exists four users that originally participate in the call (User <b>1</b>, . . . , User <b>4</b>). At time t₀User <b>1</b> initiates the group call by depressing a PTT button, causing the appropriate resources to be allocated to allow group dispatch calling between the users. As shown, the dispatch call begins with User <b>1</b> actively talking to other members of the group. At time t₁User <b>1</b> ceases talking. Also, at this time, User <b>4</b> opts out of the call by notifying his serving base station using an option message, causing the downlink channel to be dropped. It should be noted that in the preferred embodiment of the present invention the option message allows a remote unit to be included or excluded in the dispatch call. For example, any remote unit currently in the call and wishing to leave the call will send an option message “opting out” of the call, while any remote unit, not currently part of the dispatch call, can send an option message “opting in” the call.

[0026] Continuing, at time t₂, User <b>2</b> begins talking and ends talking at time t₃. As discussed above, during periods of inactivity, an inactivity timer is initiated, however, because the period of inactivity (i.e., t₂-t₁) was not greater than the inactivity timer threshold (T_h), all currently-active downlink channels are maintained by the system. User <b>3</b> begins talking at time t₄. Again, because the period of inactivity (i.e., t₄-t₃) is not greater than T_h, all active downlink channels are maintained by the system. At time t₅User <b>3</b> stops talking, and at time t₆the inactivity timer expires (i.e., t₇-t₅&gt;T_h), causing all channels to be dropped by the system. However, after the inactivity timer has expired, User <b>3</b> again begins to talk (at time t₇), causing the system to again allocate resources to all members of the group. This causes User <b>4</b> to again become a participant in the conversation.

[0027] In order to solve this problem, in the preferred embodiment of the present invention a second timer (session timer) is introduced in addition to the hang timer. In addition to the second timer, a second bookkeeping is done for the call membership (session participant list) in addition to keeping track of the original group membership. In the preferred embodiment of the present invention the session timer causes changes to a group call to be maintained until the session timer has expired.

[0028]FIG. 3 illustrates a group call in accordance with the preferred embodiment of the present invention. As shown, there exists four users that originally participate in the call (User <b>1</b>, . . . , User <b>4</b>). These original participants are entered into a session participant list <b>124</b>. At time t₀User <b>1</b> initiates the group call by depressing a PTT button, causing the appropriate resources to be allocated to allow group dispatch calling between the users. As shown, the dispatch call begins with User <b>1</b> actively talking to other members of the group. At time t₁User <b>1</b> ceases talking. Also, at this time, User <b>4</b> opts out of the call by notifying his serving base station using an option message, causing the downlink channel to be dropped. At this time, User <b>4</b> for remains a member of the group, but is removed from the session participant list.

[0029] Continuing, at time t₂, User <b>2</b> begins talking, and finishes talking at time t₃. Because the period of inactivity (i.e., t₂-t₁) is not greater than the inactivity timer threshold (T_h), all active downlink channels are maintained by the system. User <b>3</b> begins talking at time t₄Again, because the period of inactivity (i.e., t₄-t₃) is not greater than the inactivity timer, all active downlink channels are maintained by the system. At time t₅User <b>3</b> stops talking, and at time t₆the inactivity timer expires. As in prior art systems, the expiration of the inactivity, or hang timer, causes all channels to be dropped by the system. However, unlike prior-art systems, User <b>4</b> is not added to subsequent group calls unless the group call is made after expiration of the session timer (i.e., after T_s). Therefore, when User <b>3</b> again begins to talk (at t₇), only participants from the session participant list are included in the call, and User <b>4</b> does not become a participant in the conversation. Thus, in the preferred embodiment of the present invention when there exists no activity for a first period of time, all active channels are dropped with the group session participants being maintained, and when there exists no activity for a second period of time (e.g., 40 seconds) the group-call participants are reset to their original configuration. This is illustrated at time t₉where User <b>3</b> places a group call to the participants. At this time, because t₂-t₁&gt;T_s, the session timer has expired, causing User <b>4</b> to again be added to the call. In the preferred embodiment of the present invention, the second period of time used for the session timer is chosen to be much longer than the hang time. This, for example, gives a participant sufficient time to lay down the phone during the group call, to look up some information on a computer and to connect back to the original group call.

[0030] Because the session timer holds the associated book keeping (i.e., the modified group call participants) for a time greater than the hang timer, the call channels can be dropped without dropping the associated session members. This greatly reduces the chances that a user, who has opted out of a call, will again become a participant in the call. Additionally, because the user is again added to the call group after the session timer has expired, the user will be involved in future calls for the group.

[0031]FIG. 4 is a block diagram of a base station in accordance with the preferred embodiment of the present invention. As shown, the base station (e.g., base station <b>101</b>) comprises transceiver <b>401</b>, session timer <b>403</b>, hang timer <b>405</b>, and controller <b>407</b>. As known in the art, when a remote unit (e.g., remote unit <b>113</b>) initiates a dispatch connection, a series of transactions must take place to allocate resources. For example to initiate a connection, a remote unit sends an origination message on an access channel comprising a PTT_on message indicating that the push-to-talk button has been depressed, along with an identification of a talk group. Controller <b>407</b> accesses group-database <b>112</b>, provides database <b>112</b> with a talk-group identification, and is supplied a list of users in communication with base station <b>101</b>. Controller then establishes a downlink channel to all remote units in communication with base station <b>101</b>.

[0032] As discussed above, during a call, a remote unit (e.g., remote unit <b>114</b>) may desire to no longer participate in the call. If this is the case, controller <b>407</b> may receive an option message, indicating that remote unit <b>114</b> no longer desires to participate in the dispatch call. When such messages are received, controller <b>407</b> accesses group-call database <b>112</b> and provides database <b>112</b> with the option message, causing database <b>112</b> to temporarily modify the talk group, removing remote unit <b>114</b>. Controller <b>407</b> will additionally drop the channel between base station <b>101</b> and remote unit <b>114</b>.

[0033] As discussed above, during the group call, controller <b>407</b> will activate session timer <b>403</b> and hang timer <b>405</b> whenever transmission to/from remote unit <b>113</b> ceases. If there exists no transmission to/from remote unit <b>113</b> for a time greater than the hang-time threshold (T_h), then controller <b>407</b> will drop all channels for those remote units participating in the call. Similarly, if there exists no transmission to/from remote unit <b>113</b> for a time greater than the session-time threshold (T_s), then controller <b>407</b> will notify group-call database <b>112</b>, causing database <b>112</b> to “reset” the talk group to its original participants (by deleting the session participant list).

[0034] Operating communication system <b>100</b> as such allows the call channels to be dropped without dropping the associated group members. For example, once the channels are dropped, further communication to the talk group will cause the original series of transactions to take place in order to allocate the necessary resources, including the accessing of database <b>112</b>. As discussed above, database <b>112</b> provides base station <b>101</b> with a list of call participants associated with the talk group, however, unlike the original call establishment, unless the session timer has expired, remote unit <b>114</b> will not be included as a member of the group.

[0035]FIG. 5 is a flow chart showing operation of the base station of FIG. 4 in accordance with the preferred embodiment of the present invention. The logic flow begins at step <b>501</b> where controller <b>407</b> determines if a group call needs to be initiated, and if so, the logic flow continues to step <b>503</b>. At step <b>503</b> controller <b>407</b> accesses group call database <b>112</b> to obtain call participants. Uplink/Downlink channels are then established with the call participants (step <b>505</b>) and all uplink/downlink communication is provided to the remote unit (step <b>507</b>). In particular, uplink/downlink communication is continuously supplied to the remote units involved in a call, unless the remote units opt out of the call. As discussed above, if an option message is received, the base station provides this message to database <b>112</b>, where the call participants are appropriately updated. The dispatch call is then provided to the updated members of the group call.

[0036] Continuing, controller <b>407</b> continuously monitors the call to determine if inactivity exists (step <b>509</b>). If at step <b>509</b>, communication ceases then controller <b>407</b> determines if inactivity has existed for greater than T_h(step <b>511</b>), and if not, the logic flow returns to step <b>507</b>. If, however inactivity has existed for greater than T_h, the logic flow continues to step <b>513</b> where all channels associated with the group call are dropped.

[0037] Once all channels have been dropped, group-call database <b>112</b> still maintains updated group participant information in session list <b>124</b>. Therefore, if the channel is re-established at this point, accessing group-call database will provide the base station with call members that have not opted out of the call and the base station will again provide the dispatch call to the updated members of the group. With this in mind, at step <b>505</b> controller <b>407</b> determines if communication for the group call has still ceased, and if not, the logic flow returns to step <b>503</b> where the group-call database is accessed. However, if at step <b>515</b> it is determined that communication has still ceased, the logic flow continues to step <b>517</b> where it is determined if T&gt;T_s. If T&gt;T_s, the session timer has expired, and group-call database <b>112</b> is notified (step <b>519</b>), causing database <b>112</b> to reset the talk-group participants to the original members. The logic flow returns to step <b>501</b>. Thus in accordance with the preferred embodiment of the present invention the dispatch call is provided to a first plurality of remote units if the session timer has expired, otherwise the dispatch call is provided to a second plurality of remote units.

[0038]FIG. 6 is a flow chart showing operation of the group call database in FIG. 1 in accordance with the preferred embodiment of the present invention. The logic flow begins at step <b>601</b> where database <b>112</b> receives a group identifier from a base station. When received, database <b>112</b> immediately determines if session list <b>124</b> exists (step <b>603</b>) and if so, the group members are determined from session list <b>124</b> (step <b>605</b>), otherwise the group members are determined from master list <b>123</b> (step <b>607</b>). As discussed above, master list <b>123</b> contains a first set of group-call participants based on a group call identification while the session list contains a second set of group-call participants for the same group call identification, only the session list does not contain members that have chosen to opt out of the group call. Thus, the second set of set of group-call participants is a subset of the first set of group-call participants.

[0039] Once determined, database <b>112</b> provides base stations serving the members of the call with member information (step <b>609</b>). During the call, database <b>112</b> continuously monitors for any changes or modification to the group. As discussed above, when a user opts out of a call, database <b>112</b> is provided with the opt-out information in an option message from the user's serving base station. With this in mind, at step <b>611</b>, database <b>112</b> continuously monitors if any changes to the group have been made and if not, the logic flow continues to step <b>615</b>, otherwise at step <b>613</b> session list <b>124</b> is either updated (if it exists) or created (if it does not exist). The logic flow continues to step <b>615</b>. At step <b>615</b> it is determined if the session timer has expired. As discussed above, when a session timer expires, the base station will provide such notification to database <b>112</b>. If this occurs, then session list <b>124</b> is deleted (step <b>617</b>), otherwise the logic flow returns to step <b>611</b>.

[0040] While the invention has been particularly shown and described with reference to a particular embodiment, it will be understood by those skilled in the art that various changes in form and details may be made therein without departing from the spirit and scope of the invention. For example, it should be noted that the session participant list can be modified during a call by the addition of a new session participants. New session participants can be added when they are pulled into the conversation by a current session participant, for example by calling the new participant with an opt-in request. New session participants can also be allowed to add themselves by selecting to call into the group session with an opt-in request. Database <b>112</b> is notified of the addition of an additional participant information by a base station using an option message, where the option message contains opt_in information for the additional participant. The new participant is added to the session participant list and only the participants in that list are included in the call (as described above). Additionally, it is contemplated that when a participant reconnects to the group while a session is in progress, the participant is treated like a new participant, except that the reconnecting remote unit is not added to the session participant list because the remote unit is already included. It is intended that such changes come within the scope of the following claims.