US20140235286A1

US20140235286A1 - Continuous interface maintenance for group communications to a wireless communication device group

Info

Publication number: US20140235286A1
Application number: US14/264,641
Authority: US
Inventors: Bongyong SONG; Harleen Kaur Gill
Original assignee: Qualcomm Inc
Current assignee: Qualcomm Inc
Priority date: 2007-09-24
Filing date: 2014-04-29
Publication date: 2014-08-21
Also published as: WO2009042517A2; KR101082251B1; WO2009042517A3; JP5290299B2; JP2010541391A; CN101803279B; EP2193629A2; EP2206287A2; CN101803279A; US8644872B2; EP2206287B1; EP2193629B1; CN101803280A; JP5118200B2; JP2011501892A; KR20100060015A; ATE515854T1; US8761822B2; CN101803280B; WO2009042516A3

Abstract

A system, method, and computer device that selectively maintain an open interface to a communication control device that is controlling wireless communication to at least one of a plurality of wireless communication devices that are in a communication group, such as a push-to-talk (PTT) group. In one embodiment, the wireless communication device registers at the communication control device, such as a base station controller, and at least one interface is established between the communication control device and another computer device on the wireless communication network, such as a broadcast A10 interface with a broadcast serving node (BSN). The communication control device will then maintain the interface while the at least one wireless communication device, or at least one member device of the communication group, is registered such that group communications can more rapidly be delivered to the wireless communication device.

Description

CLAIM OF PRIORITY UNDER 35 U.S.C. §119

The present Application for Patent is a Continuation Application of Non-Provisional application Ser. No. 12/212,532, entitled “CONTINUOUS INTERFACE MAINTENANCE FOR GROUP COMMUNICATIONS TO A WIRELESS COMMUNICATION DEVICE GROUP,” filed Sep. 17, 2008, which claims priority to Provisional Application No. 60/974,838, entitled “CONTINUOUS INTERFACE MAINTENANCE FOR GROUP COMMUNICATIONS TO A WIRELESS COMMUNICATION DEVICE GROUP,” filed Sep. 24, 2007, and to Provisional Application No. 60/974,839, entitled “CONTINUOUS BROADCAST INTERFACE MAINTENANCE FOR GROUP COMMUNICATIONS TO WIRELESS COMMUNICATION DEVICES,” filed Sep. 24, 2007, each of which is assigned to the assignee hereof and hereby expressly incorporated by reference herein in its entirety.

BACKGROUND OF THE INVENTION

1. Field of the Invention
The present invention relates to point-to-point or point-to-multipoint wireless communications systems. More specifically, the present invention relates to a system and method for maintaining an open and continuous interface for group communications, such as push-to-talk (PTT) communications, to a wireless communication device that is a member of a communication group.
2. Description of the Related Art
In cellular wireless telecommunications, there have been several standards implemented regarding the creation and functionality of the communication infrastructure. One of the more recent standards is CDMA2000, where CDMA is an abbreviation for “code division multiple access.” CDMA2000 supports a Broadcast-Multicast Service (BCMCS), which allows optimization of the radio interface for delivery of BCMCS content stream(s) to one or more wireless communication devices in one or more regions of an cellular carrier's network. The CDMA2000 protocol allows for both voice and data to be transmitted to and from wireless communication devices and determines the appropriate resource allocation for communications, both to and from the wireless telecommunication device and the radio access network (RAN), and in between communication control devices, such as base stations, packet data serving nodes (PDSN), and broadcast serving nodes (BSN).
There exists a wireless telecommunication service that provides a quick one-to-one or one-to-many communication that is generically referred to as “Push-To-Talk” (PTT) capability. The specific PTT group of recipient devices for the communicating wireless device is commonly set up by the carrier. A PTT communication connection is typically initiated by a single button-push on the wireless device that activates a half-duplex link between the speaker and each member device of the group and once the button is released, the device can receive incoming PTT transmissions once the button is released. In some arrangements, the PTT speaker will have the “floor” where no other group member can speak while the speaker is speaking. Once the speaker releases the PTT button, any other individual member of the group can engage their PTT button and they will have the floor.
It is important to have a very fast setup of the signal path of the PTT call because of the desired immediacy of the voice communication. Accordingly, it would be advantageous to provide a system and method to expedite PTT communication setup with a target wireless communication device given the time-sensitivity of the communication. Such system and method can advantageously utilize existing cellular network infrastructure that would otherwise have latency delays in PTT communications. It is thus to the provision of such a system and method to expedite communications with a wireless communication device that the present invention is primarily directed.

SUMMARY OF THE INVENTION

Embodiments of the invention include systems, methods, and computer devices that selectively maintain an open interface to a communication control device that is controlling wireless communication to at least one of a plurality of wireless communication devices that are in a communication group, such as a push-to-talk (PTT) group. In one embodiment, the wireless communication device registers at the communication control device, such as a base station controller, and at least one interface is established between the communication control device and another computer device on the wireless communication network, such as a broadcast A10 interface with a broadcast serving node (BSN). The communication control device will then maintain the interface while the at least one wireless communication device, or at least one member device of the communication group, is registered such that group communications can more rapidly be delivered to the wireless communication device.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a representative diagram of a wireless network with a designated PTT group of wireless telecommunication devices communicating with a group communication server and other computer devices across the wireless network.

FIG. 2 is a representative diagram of one embodiment of a wireless network in a common cellular telecommunication configuration, having a group communication server control communications between the wireless telecommunication devices of PTT group members.

FIG. 3 is a block diagram illustrating the computer platform of the wireless telecommunication device embodied with PTT capability.

FIG. 4 is a block diagram illustrating one embodiment of BCMCS data streaming in a CDMA2000 architecture.

FIG. 5 is a call flow diagram of one embodiment of the BCMCS Flow Registration creating a broadcast A10 interface between the BSC/PCF and the BSN.

FIG. 6 is a flowchart of one embodiment of the process on the communication control device to maintain a continuous interface while at least one member of a PTT communication group is registered.

DETAILED DESCRIPTION OF THE INVENTION

In this description, the terms “communication device,” “wireless device,” “wireless communications device,” “PTT communication device,” “handheld device,” “mobile device,” and “handset” are used interchangeably. The terms “call” and “communication” are also used interchangeably. The term “application” as used herein is intended to encompass executable and non-executable software files, raw data, aggregated data, patches, and other code segments. The term “exemplary” means that the disclosed element or embodiment is only an example, and does not indicate any preference of user. Further, like numerals refer to like elements throughout the several views, and the articles “a” and “the” includes plural references, unless otherwise specified in the description.
Furthermore, the present invention is shown in several embodiments here as operating in a CDMA2000 network architecture. Reference can be had to the known standards and construction of CDMA2000 systems and network interfaces as would be known to one of skill in the art.
With reference to the figures in which like numerals represent like elements throughout, FIG. 1 illustrates one embodiment of a system 10 for with a group communication server 32 to one or more wireless telecommunication devices in a PTT group 12, such as the wireless telephone 14, smart pager 16 and personal digital assistant (PDA) 18, with other wireless telecommunication devices across a wireless network 20. In the system 10, each wireless telecommunication device 14,16,18 is capable of selectively directly communicating across the wireless communication network 20 with a target set of one or more other wireless telecommunication devices of the plurality. For example, the target set for mobile telephone 14 can be all devices in the communication group 12 or a subset thereof, such as pager 16 and PDA 18.
In this embodiment, the wireless telecommunication device (such as mobile telephone 14) sends a flag to at least the group communication computer device, shown here as server 32, which is present on a server-side LAN 30 across the wireless network 20, to indicate that the wireless device is present, i.e. accessible, on the wireless network 20. The group communication computer device 32 can share this information with the set of target wireless telecommunication devices designated by the first wireless telecommunication device, or can also share is with other computer devices resident on the server-side LAN 30 or accessible across the wireless network 20. The group communication computer device 32 can have an attached or accessible database 34 to store the group identification data for the wireless devices. It should be appreciated that the number of computer components resident on server-side LAN 30, or across the wireless network 20, or Internet generally, are not limited.
The direct communication, such as a PTT communication, can be established through a half-duplex channel between the communicating wireless telecommunication device 14,16,18 and the one or more other wireless telecommunication devices of the target set. Also, the group communication computer device 32 can attempt to bridge the requested direct communication with the target set if at least one of the wireless telecommunication devices of the target set have informed the group communication computer device 32 of their presence on the wireless network 20.
The group communication computer device 32 can also inform the wireless telecommunication device 14,16,18 of the inability to bridge a direct communication to the target set 12 upon none of the wireless telecommunication devices (or at least one) of the target set not having informed the group communication computer device 32 of their presence on the wireless network 20. Further, while the group communication computer device 32 is shown here as having the attached database 34 of group identification data, the group communication computer device 32 can have group identity data resident thereupon, and perform all storage functions described herein.
In overview, the system 10 selectively communicates to a wireless communication device 14,16,18 for a group communication across the wireless communication network 20 with the a group communication server 32 configured to receive a request at to establish a group communication with at least one target wireless communication device (e.g. mobile telephone 14), and the group communication server 32 send a request to the at least one target wireless communication device across the wireless communication network 20 indicating an incoming group communication. An intermediate computer device (such as base station controller 64 in FIG. 2) receives an access channel communication packet across an access channel from the at least one target wireless communication device that received the request to establish a group communication from the group communication server 32. The access communication packet indicates the whether or not there are bundled messages present in the packet, such as messages indicating the resources for the group communication to the at least one wireless communication device 14. Through the bundling of messages, the wireless communication device 14,16,18 can quickly send messages indicating the ability to handle the incoming communication, without the other computer device (such as base station 60) needing to examine all messages send from the wireless communication device 14,16,18 for bundled messages.
The group communication can be voice, applications, graphic media, such as pictures in JPEG, TIF, and the like, or audio files such as MP3, MP4, WAV, and the like. The media can also be streaming media, such as a multimedia application (Powerpoint, MOV file, and the like). Also, the group communication is typically half-duplex audio conferencing among members of the communication group 12.
FIG. 2 is a representative diagram of one embodiment of a wireless network in a common cellular telecommunication configuration, having a series of group communication computer devices, such as group communication server 32 that controls communications between the wireless communication devices of set group members ( devices 70,72,74,76) in a PTT system. The wireless network is merely exemplary and can include any system whereby remote modules communicate over-the-air between and among each other and/or between and among components of a wireless network 20, including, without limitation, wireless network carriers and/or servers. A series of group communication servers 32 are connected to a group communication server LAN 50. Wireless telephones can request packet data sessions from the group communication server(s) 32 using a data service option. Also shown on LAN 50 is a BCMCS Controller 33, the functionality of which is more fully set forth below in FIGS. 4 and 5.
The group communication server 32 are connected to a wireless service providers packet data service node (PDSN) such as PSDN 52, and/or a broadcast serving node 53 shown here resident as on a carrier network 54. Each PSDN 52 or BSN 53 can interface with a base station controller 64 of a base station 60 through a packet control function (PCF) 62. The PCF 62 is typically located in the base station 60. The carrier network 54 controls messages (generally in the form of data packets) sent to a messaging service controller (“MSC”) 58. The carrier network 30 communicates with the MSC 32 by a network, the Internet and/or POTS (“plain ordinary telephone system”). Typically, the network or Internet connection between the carrier network 54 and the MSC 58 transfers data, and the POTS transfers voice information. The MSC 58 can be connected to one or more base stations 60. In a similar manner to the carrier network, the MSC 58 is typically connected to the base transceiver station (sometimes referred to as “branch-to-source”)(BTS) 66 by both the network and/or Internet for data transfer and POTS for voice information. The BTS 66 ultimately broadcasts and receives messages wirelessly to and from the wireless devices, such as cellular telephones 70,72,74,76, by short messaging service (“SMS”), or other over-the-air methods known in the art. It should also be noted that carrier boundaries and/or PTT operator network boundaries do not inhibit or prohibit the sharing of data as described herein.
Cellular telephones and mobile telecommunication devices, such as wireless telephone 14, are being manufactured with increased computing capabilities and are becoming tantamount to personal computers and hand-held PDAs. These “smart” cellular telephones allow software developers to create software applications that are downloadable and executable on the processor of the wireless device. The wireless device, such as cellular telephone 14, can download many types of applications, such as web pages, applets, MIDlets, games and data. In wireless devices that have designated a communication group 12 (FIG. 1), the wireless communication device can directly connect with the other member of the set and engage in voice and data communication. However, all such group-direct communications will occur through, or be at the control of, the group communication server 32. All data packets of the devices do not necessarily have to travel through the group communication computer device 32 itself, but the group communication computer device 32 must be able to ultimately control the communication because it will typically be the only server-side 30 component that is aware of and/or can retrieve the identity of the members of the communication group, or direct the identity of the members of the communication group 12 to another computer device.
FIG. 3 is a block diagram illustrating one embodiment of the wireless telecommunication device being a mobile telephone 14 with a PTT button 78 that opens the direct communication to a target set of devices, i.e. other members of the communication group 12. The wireless device 14 is also shown as having a graphics display 80 to the user of the wireless device 14. The wireless device 14 includes a computer platform 82 that can handle voice and data packets, and receive and execute software applications transmitted across the wireless network 20 to include the group communications. The computer platform 82 includes, among other components, an application-specific integrated circuit (“ASIC”) 84, or other processor, microprocessor, logic circuit, programmable gate array, or other data processing device. The ASIC 84 is installed at the time of manufacture of the wireless device and is not normally upgradeable. The ASIC 84 or other processor executes an application programming interface (“API”) layer 86, which includes the resident application environment, and can include the operating system loaded on the ASIC 84. The resident application environment interfaces with any resident programs in the memory 88 of the wireless device. An example of a resident application environment is the “binary runtime environment for wireless” (BREW) software developed by QUALCOMM® for wireless device platforms.
As shown here, the wireless device can be a mobile telephone 14, with a graphics display 80, but can also be any wireless device with a computer platform 82 as known in the art, such as a personal digital assistant (PDA), a pager with a graphics display 26, or even a separate computer platform that has a wireless communication portal, and may otherwise have a wired connection to a network or the Internet. Further, the memory 88 can be comprised of read-only or random-access memory (RAM and ROM), EPROM, EEPROM, flash cards, or any memory common to computer platforms. The computer platform 82 can also include a local database 90 for storage of software applications not actively used in memory 88. The local database 90 is typically comprised of one or more flash memory cells, but can be any secondary or tertiary storage device as known in the art, such as magnetic media, EPROM, EEPROM, optical media, tape, or soft or hard disk.
In this embodiment of the wireless device, the computer platform 82 also includes a direct communication interface 92 that can open the direct communication channel from the wireless device, typically for the half-duplex voice communication in a PTT call. The direct communication interface 92 can also be part of the standard communication interface for the wireless device which ordinarily carries the voice and data transmitted to and from the wireless device. The direct communication interface 92 typically is comprised of hardware as is known in the art.
FIG. 4 is a block diagram illustrating one embodiment of BCMCS data streaming in a CDMA2000 architecture. Shown here are the potential home network, serving network, and third party locations with various resident elements. A BCMCS Controller 110 is responsible for managing and providing the BCMCS session information to the BSN 122 (via the SAAA 112), the BCMCS Content Server, the mobile station 126 (via the PDSN 120 function) and the RAN (via the BSN 122 function). The BCMCS Controller 110 may perform discovery operations to assist the mobile station 126 to find desired content.
BCMCS Content Server 114 makes BCMCS content available within an IP Multicast stream. It should be noted that the BCMCS Content Server 114 in the serving network is not necessarily the creator or source of the content, but is the last application level entity to manipulate (e.g., reformat) the content prior to the content reaching the BSN 122. The BCMCS Content Server 114 may store and forward the content from the BCMCS Content Provider 100,108, and/or merge the content from the multiple content providers. If higher layer encryption is enabled, the BCMCS Content Server 114 encrypts the stream content. In this embodiment, the BCMCS Content Provider 108 at a third party location is the creator or source of the content.
The BCMCS Subscriber Profile Manager 104 is an application that updates the subscriber profile in the Subscriber Profile Database 102 regarding subscribed BCMCS services. The user may interface to this application directly, or the carrier operator may reserve access to this application to their customer service agents. The interface between the user and the BCMCS Subscriber Profile Manager 104, and the interface between the BCMCS Subscriber Profile Manager 104 and the Subscriber Profile Database 102 are shown only for illustrative purposes of a common network configuration. The H-AAA 106 and S-AAA 112 are elements responsible for BCMCS authentications, authorizations, and accounting, and access the Subscriber Profile Database 102 to obtain information from the BCMCS user profile.
The PDSN 120 communicates using the unicast packet data service for packet data session establishment, to add and remove IP flows, etc., and acts as the first-hop router for IP traffic to and from the mobile station (MS) 126. The BSN 122 communicates with the BSC/PCF 124 to add and remove Multicast IP Flows. The BSN 122 may use IP multicast protocols to manage bearers supporting Multicast IP Flow between itself and the nearest router connecting back to the BCMCS Content Server 114. It also applies the flow treatment received from the BCMCS Controller 110 to the Multicast IP Flows. The multicast router MR 118 is optional entity used if the content is transmitted over a provisioned tunnel between the BSN 122 and the BCMCS Content Server 114. In this embodiment, this entity is responsible for performing the BCMCS Information Acquisition, BCMCS registration, and receiving Multicast IP flows. The BSC/PCF 124 are responsible for signaling, establishing, and tearing down bearer channels between the BSN 122 and the MS 126. The BSC 124 chooses the “best” bearer channel to the MS 126 based on considerations such as optimization of resources, required quality-of-service (“QoS”), etc.
The interface between BCMCS Controller 110 and BSN 122 via S-AAA 112 provides BCMCS session related information such as Flow Treatment (e.g., Header Compression), relevant QoS parameters such as required bandwidth, the mapping between BCMCS Flow ID and Multicast IP address and port number from the BCMCS Controller 110 to the BSN 122 via a predefined protocol. This interface also exchanges the BCMCS authorization information for BCMCS registration. The interface between BSN 122 and S-AAA 112 the BSN 122 will typically generate accounting information for the content flows. And the interface between BCMCS Controller and SAAA. This interface provides the BCMCS Controller 110 with authentication and authorization information. The S-AAA 112 may send BCMCS user profile received from the H-AAA 106 to the BCMCS Controller 110 during BCMCS Information Acquisition triggered by the MS 126. The BCMCS Controller 110 may also send accounting information to the S-AAA 112. The S-AAA 112 may also be used to relay the BCMCS session related information between the BSN 122 and BCMCS Controller 110.
The interface between BCMCS Controller 110 and BCMCS Content Provider 100,108 interface exchanges information including Content Provider Name, Program Name, session description (e.g., codec type), and security information, etc. This interface may also exchange the start time of the BCMCS session and duration of the BCMCS session. The interface between BCMCS Controller 110 and BCMCS Content Server 114 may exchange the security information, multicast IP Address and port number, and content management information (e.g., the start time of the BCMCS session and duration of the BCMCS session). The BCMCS Controller 110 uses this interface to add, modify, or remove BCMCS flows and this interface also provides a mechanism for message authentication of the BCMCS Content Server 114 and BCMCS controller 110 and protects integrity of its messages.
The interface between BCMCS Controller 110 and MS/UIM 126 provides the BCMCS client application in the MS 126 with access to information about available BCMCS sessions: typically including a Program Name, BCMCS Flow ID(s), broadcast access key (BAK)(s) and BAK Expiry time if the Multicast IP Flow(s) are encrypted, start time of the BCMCS session, duration of the BCMCS session, flow treatment (e.g., header compression), and session description (e.g., 36 codec type), etc. The PCF 124 initiates setup of an A10 connection by sending an A11-Registration Request message to the PDSN 129. The All-Registration Request message contains the extensions specified in the CDMA2000 standard. The All-Registration Request message may be retransmitted a configurable number of times, and if the connection setup request is acceptable, the PDSN 120 updates its binding record for the A10 connection by creating an association between the PDSN Session Identifier (PDSN SID) and the IMSI address, PCF-Address and PDSN-Address information. The PSDN SID is identical to the PCF Session Identifier (PCF SID). If the either the PCF or the PDSN does not support the appropriate Session Identifier Version, the PDSN may choose any PDSN SID.
The PCF 124 and the PDSN 120 use the PCF-IP-Address and the PDSN-IP-Address returned in the All- Registration Reply message as the A10 connection for the transport of user traffic. The PCF-IP Address and the PDSN-IP-Address form the unique link layer ID for each A10 connection. The PCF 124 and the PDSN 120 maintain an association of the mobile's IMSI address with the A10 connection. The release of an A10 connection is typically controlled by the PCF 124, however, the PDSN can also initiate A10 connection release, the PDSN 120 can requests that the PCF 124 release the connection.
FIG. 5 is shows one embodiment of the BCMCS Flow Registration creating a broadcast A10 interface between the BSC/PCF 142 and the BSN 144. The MS 140 receives content availability and radio parameter and information from the overhead messages. The MS 140 performs a BCMCS registration for BCMCS_FLOW_ID(s) with the authorization signature included. If the BSC/PCF 142 has BAK information, the RAN may check BAK_HASH. The BSC/PCF 142 sends the A11 BC Service Request to the BSN 144 to request RAN session information and includes the BCMCS_FLOW_ID and the authorization signature.
The BSN 144 sends the remote authentication dial in user service (“RADIUS”) Access-Request message to the S-AAA/BCMCS Controller 146. The message includes the BCMCS_FLOW_ID, Authorization Parameters, and Reason Code. In this example, the BSN 144 sets Reason 1 Code to 3 to indicate both authorization and BSN session information are needed. The BCMCS Controller 146 performs the authorization. Then the BCMCS Controller 146 sends the RADIUS Access-Accept message to the BSN 144 including BCMCS session information. The BSN 144 sends BC Service Response to the BSC/PCF 142 including BCMCS session information that the RAN needs. The RAN sends BC Registration Request to the BSN 144 to set up a broadcast A10 connection. The BSN 144 responds with BC Registration Response. The RAN sends Registration Accept to the MS 140. The BSN 144 may send an A11-BC-Registration Update message to the RAN in order to terminate the BCMCS flow(s). If the mapping is pre-provisioned information (BCMCSFlowID; multicast IP addr/port) at the BSN 144, only the BC registration request and reply between the BSC/PCF 142 and BSN 144 are necessary.
Typically, the MS 140 is allowed to send a BCMCS Flow Registration message around the time that the multicast flow (BCMCS flow) begins. If a BCMCS Flow Registration message is not received during the allowed registration period (e.g., too early or too late), the RAN generally ignores the registration. For some “dynamic” group communications, however, the start time of a flow is not known to the MS 140. For example, the initiation of a PTT group call is random and not known to the MS 140 in advance. The first multicast message of a PTT group call is typically a call announcement message that is sent by a PTT server to a plurality of group members, e.g., wireless communication device 14, 16 and 18. If the broadcast A10 connection between the BSN 53 and the base station 60 is not open at the time of call announcement, the message can be dropped or could be delayed. Therefore, it is desirable to maintain a continuous broadcast A10 connection for such dynamic BCMCS flows all the time as long as at least one group member is present.
FIG. 6 is a flowchart of one embodiment of the process on the communication control device (such as BSC/PCF 124 in FIG. 4) to maintain a continuous interface while at least one member of a PTT communication group is registered. A registration is received from a wireless communication device 14,16,18, as shown at step 150, and then a determination is made as to whether the registration is for the call announcement flow for a PTT group (or other dynamic group), as shown at decision 152. If the registration is not for a call announcement flow for a PTT group or other dynamic group as decision 152, then an broadcast A10 connection is established only if the registration is received during the allowed registration time period, as shown at decision 164. In this case, the connection will be opened at step 166. Otherwise, the registration is ignored and the process terminates, as shown at termination 172.
Otherwise, if the registration is for the call announcement flow for a PTT group at decision 152, then a determination is made as to whether the PTT group has any members registered at the communication control device, as shown at decision 154. In this case, the interface for the group should be already open and the RAN does not need to newly open an interface for the group. The RAN only needs to add the wireless communication device to the group member list of the group, as shown at step 156. If there are no devices yet registered on the communication control device for that communication group, then communication group for that wireless communication device is stored on a list at the communication control device, as shown at step 158, and then the interface is opened for the wireless communication device, as shown at step 160.
After the interface, such as a broadcast A10 interface, is opened for the wireless communication device, then a determination is made as to whether the wireless communication device has unregistered, as shown at decision 162. If the wireless communication device has not unregistered at decision 162, a wait state is entered and the interface remains open until the wireless communication device has unregistered. Once the wireless communication device has unregistered at decision 162, then a determination is made as to whether there are any communication group members left for the communication group of that wireless communication device, as shown at decision 168. If there are members of the communication group remaining registered, then the process thread returns to decision 162 to await another wireless communication device unregistering. Otherwise, if no members of the communication group are registered on the list of the communication control device (or if there was no communication group for the wireless communication device as could occur at decision 154) at decision 168, then the interface that was assigned to the wireless communication device and/or the communication group is released as shown at step 168, and then the process terminates as shown at termination 170.
It can thus be seen that system provides, in one embodiment, an inventive method for selectively maintaining an open interface to a communication control device that is controlling wireless communication to at least one of a plurality of wireless communication devices 14,16,18 that are in a communication group (PTT Group 12) through registering at least one wireless communication device 14 that is a member of a communication group (PTT Group 12) of wireless communication devices at the communication control device (BSC/PCF 142), the at least one wireless communication device 14 configured to receive group-directed communications for the communication group, and the at least one wireless communication device 14 selectively becoming unregistered from the communication control device, then establishing at least one interface between the communication control device and another computer device on the wireless communication network (such as a broadcast A10 being established between BSC.PCF 142 and BSN 144), the at least one interface permitting delivery of a group-directed communication (e.g., PTT group call announcement) to the at least one wireless communication device 14. Then maintaining the at least one interface while the at least one wireless communication device 14 is registered with the communication control device.
In one embodiment, the communication control device (BSC/PCF 142) can further maintain a list of registered wireless communication devices, and upon a wireless communication device 14 being unregistered, remove the unregistered wireless communication device from the list. The method can also further include releasing the at least one interface upon the wireless communication device 14 becoming unregistered. Establishing at least one interface can occur upon a group-directed communication directed to the at least one wireless communication device 14 being received at the communication control device (BSC/PCF 142), i.e. a incoming PTT call announcement is being sent to the wireless communication device 14. And if so embodied, at least one wireless communication device 14 can be placed on the list upon a group-directed communication directed to the at least one wireless communication device 14 being received at the communication control device (BSC/PCF 142). The establishment of at least one interface can establishing at least one interface (such as a broadcast A10 interface) for each registered wireless communication device 14,16,18.
Is so embodied, the method can include determining if the communication group (PTT Group 12) for the registered wireless communication device 14 is on the list, and wherein maintaining at least one interface is maintaining at least one interface for a listed communication group as long at least one wireless communication device 14 of the communication group (PTT group 12) is registered. Where the communication control device is a base station controller (BSC 142) and the other computer device is a broadcast serving node (BSN 144), establishing at least one interface can be establishing a broadcast A10 interface between the BSN 144 and the BSC 142.
In view of the methods being executable on a mobile device and other computer platforms, the method can accordingly be performed by a program resident in a computer readable medium, where the program directs the mobile device or other computer device having a computer platform to perform the steps of the method. The computer readable medium can be the memory of the server, or can be in a connective database. Further, the computer readable medium can be in a secondary storage media that is loadable onto a wireless communications device computer platform, such as a magnetic disk or tape, optical disk, hard disk, flash memory, or other storage media as is known in the art.
In one or more exemplary embodiments, the functions described may be implemented in hardware, software, firmware, or any combination thereof If implemented in software, the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium. Computer-readable media includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A storage media may be any available media that can be accessed by a computer. By way of example, and not limitation, such computer-readable media can comprise RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer. Also, any connection is properly termed a computer-readable medium. For example, if the software is transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of medium. Disk and disc, as used herein, includes compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk and blu-ray disc where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above should also be included within the scope of computer-readable media.
While the invention has been particularly shown and described with reference to a preferred embodiment thereof, it will be understood by those skilled in the art that various changes in form and detail may be made without departing from the scope of the present invention as set forth in the following claims. Furthermore, although elements of the invention may be described or claimed in the singular, the plural is contemplated unless limitation to the singular is explicitly stated.

Claims

1. A method for selectively maintaining an open multicast interface to a communication computer device that is controlling wireless communication to at least one of a plurality of wireless communication devices that are in a communication group, the method comprising:

registering at least one wireless communication device that is a member of the communication group at the communication computer device, the at least one wireless communication device configured to receive group-directed communications for the communication group, wherein the at least one wireless communication device is configured to selectively unregister itself from the communication computer device;

establishing at least one multicast interface between the communication computer device and another computer device on a wireless communication network, the at least one multicast interface permitting delivery of the group-directed communications to the at least one wireless communication device;

determining whether any wireless communication devices remain registered as members of the communication group; and

in response to the determining, maintaining the at least one multicast interface so long as any wireless communication device remains registered with the communication computer device as a member of the communication group after the group-directed communications have ended.

2. The method of claim 1, further comprising releasing the at least one multicast interface upon all wireless communication devices that were previously registered as members of the communication group becoming unregistered.

3. The method of claim 1, wherein the establishing at least one multicast interface comprises establishing at least one multicast interface for the communication group.

4. The method of claim 1, wherein the establishing at least one multicast interface comprises establishing at least one multicast interface for each registered wireless communication device.

5. The method of claim 1, further comprising maintaining, with the communication computer device, a list of currently registered wireless communication devices that are members of the communication group, wherein maintaining the list comprises removing any wireless communication device that selectively unregisters itself.

6. The method of claim 5, wherein the determining comprises determining, via the list of currently registered wireless communication devices, whether any wireless communication devices remain registered as members of the communication group.

7. The method of claim 5, wherein the list of currently registered wireless communication devices is updated upon a registration from at least one other wireless communication device being received at the communication computer device.

8. The method of claim 5, further comprising determining whether the communication group for a registered wireless communication device is on the list of currently registered wireless communication devices.

9. The method of claim 1, wherein the group-directed communications to the at least one wireless communication device comprise a push-to-talk (PTT) group call announcement to at least one PTT group member.

10. The method of claim 1, wherein the at least one multicast interface comprises a delay-sensitive, low-bandwidth call setup interface.

11. An apparatus for selectively maintaining an open multicast interface to a communication computer device that is controlling wireless communication to at least one of a plurality of wireless communication devices that are in a communication group, the apparatus comprising:

means for registering at least one wireless communication device that is a member of the communication group at the communication computer device, the at least one wireless communication device configured to receive group-directed communications for the communication group, wherein the at least one wireless communication device is configured to selectively unregister itself from the communication computer device;

means for establishing at least one multicast interface between the communication computer device and another computer device on a wireless communication network, the at least one multicast interface permitting delivery of the group-directed communications to the at least one wireless communication device;

means for determining whether any wireless communication devices remain registered as members of the communication group; and

means for maintaining, in response to the determining, the at least one multicast interface so long as any wireless communication device remains registered with the communication computer device as a member of the communication group after the group-directed communications have ended.

12. The apparatus of claim 11, further comprising means for releasing the at least one multicast interface upon all wireless communication devices that were previously registered as members of the communication group becoming unregistered.

13. The apparatus of claim 11, wherein the means for establishing at least one multicast interface comprises means for establishing at least one multicast interface for the communication group.

14. The apparatus of claim 11, wherein the means for establishing at least one multicast interface comprises means for establishing at least one multicast interface for each registered wireless communication device.

15. The apparatus of claim 11, further comprising means for maintaining, with the communication computer device, a list of currently registered wireless communication devices that are members of the communication group, wherein maintaining the list comprises removing any wireless communication device that selectively unregisters itself.

16. The apparatus of claim 15, wherein the means for determining comprises means for determining, via the list of currently registered wireless communication devices, whether any wireless communication devices remain registered as members of the communication group.

17. The apparatus of claim 15, wherein the list of currently registered wireless communication devices is updated upon a registration from at least one other wireless communication device being received at the communication computer device.

18. The apparatus of claim 15, further comprising means for determining whether the communication group for a registered wireless communication device is on the list of currently registered wireless communication devices.

19. The apparatus of claim 11, wherein the group-directed communications to the at least one wireless communication device comprise a push-to-talk (PTT) group call announcement to at least one PTT group member.

20. A non-transitory computer-readable medium for selectively maintaining an open multicast interface to a communication computer device that is controlling wireless communication to at least one of a plurality of wireless communication devices that are in a communication group, the non-transitory computer-readable medium comprising:

at least one instruction to register at least one wireless communication device that is a member of the communication group at the communication computer device, the at least one wireless communication device configured to receive group-directed communications for the communication group, wherein the at least one wireless communication device is configured to selectively unregister itself from the communication computer device;

at least one instruction to establish at least one multicast interface between the communication computer device and another computer device on a wireless communication network, the at least one multicast interface permitting delivery of the group-directed communications to the at least one wireless communication device;

at least one instruction to determine whether any wireless communication devices remain registered as members of the communication group; and

at least one instruction to maintain, in response to the determining, the at least one multicast interface so long as any wireless communication device remains registered with the communication computer device as a member of the communication group after the group-directed communications have ended.