User experience enhancements for controlling a group communication

USER EXPERIENCE ENHANCEMENTS FOR CONTROLLING A GROUP COMMUNICATION

<u>Related applications</u>

This application claims the benefit of priority to U.S. Provisional Patent Application Serial No. 61/554,876 entitled "User Experience Enhancements for Group Communication," the entire content of which is incorporated herein by reference in its entirety.

This application also relates to U.S. Patent Application No. ________, entitled "User Experience Enhancements for Limiting Calls in a Group Communication," filed concurrently with the above application.

<u>Field</u>

FIELD OF THE INVENTION The present invention relates generally to wireless communication systems. More particularly, the present invention relates to methods and devices that enable group communication, such as PTT communication, without requiring dedicated "Push-To-Talk" (PTT) hardware. .

In wireless communication devices, such as cellular telephones, PDAs, mini-laptops, and advanced pagers, devices are generally involved in bridging telephone calls through existing cellular telephone networks and passing data packets across the network. communicate over long distances by These wireless communication devices often have data processing and computing capabilities, and thus can transmit and receive voice and other types of data across a telephone network.

A wireless communication service exists that provides one-to-one and one-to-many communication, commonly referred to as "push-to-talk" (PTT) functionality. A specific PTT group of recipient devices with which the wireless communication device communicates is typically set up by a carrier. A PTT communication connection is typically initiated by a single hardware button-push on the wireless communication 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 will receive incoming PTT transmissions. can Existing PTT systems have advantages over conventional cellular systems, which in contrast to cellular voice channels, where they may take more than 5 seconds to establish, have faster call setup times, e.g., ideally of 1 second. This is because it has setup times in the range. In some arrangements, the PTT speaker will have a "floor" where no other group member can speak while the speaker is speaking. Once the speaker releases the PTT button, any other respective member of the group can engage his or her PTT button and he or she will have the floor. Generally speaking, a PTT system uses standard voice-over Internet protocol (VoIP) technologies. Voice information is transmitted in digital form over an IP-based data network. In PTT scenarios, instead of using standard cellular infrastructure, a call is formed by assembling individual point-to-point connections between each IP endpoint in the network. Initiating the PTT system creates a call to the target device. The call originator's voice may be transmitted to the target handset via the carrier's network.

A disadvantage to existing PTT services is that they generally require devices with dedicated PTT hardware components, such as a hardware PTT button, which means these services are not generally available to the majority of mobile devices currently in use. .

<p>Various embodiments include methods for managing group communication sessions on a wireless communication device, the methods comprising: establishing a group communication channel with one or more devices in a first mode of operation in response to a user input at a user interface. detecting activation of a target-based sliding lock mechanism by a user on a touchscreen user interface display of the wireless communication device, and maintaining the group communication channel in a second mode of operation while the locking mechanism is activated. . In various embodiments, the second mode of operation may be a hand-free mode, a priority lock mode, a media lock mode, a lockout mode, and/or a blocking mode.</p><p>Embodiment methods may further include initiating a group communication session in response to a user input and displaying on the display visual feedback indicating a status of the group communication. Embodiments may include requesting control of a floor in a group communication session, and displaying visual feedback on a display indicating a status of the floor in the group communication session. Embodiments include displaying on a display a visual representation of one or more members of a group in a group communication session, determining a participation status of each member of the group, and displaying visual feedback indicating a participation status of each member of the group It may further include displaying on the. Embodiments may also include displaying a reason for a non-attendance member of the group in the group communication.</p><p>Further embodiments include methods for managing a group communication session on a wireless communication device, the methods comprising: initiating a group communication session in response to a user input; detecting activation of a locking mechanism by a user on a user interface; sending a request for priority floor access to the server in response to the detected activation of the locking mechanism, and maintaining a group communication channel with one or more devices in a priority access mode while the locking mechanism is activated. It may include steps.</p><p>Further embodiments include methods for managing group communication sessions on a wireless communication device, the methods comprising: establishing a group media communication channel with one or more devices in response to a user input on a user interface; detecting activation of the locking mechanism by the user on the ., and maintaining the group media communication channel in a media lock mode while the locking mechanism is activated.</p><p>Further embodiments include methods of managing a group communication session on a wireless communication device, the methods comprising: displaying a quick contact group communication shortcut icon on a home screen of a wireless communication device display; displaying a group communication button associated with the quick contact group communication shortcut icon, detecting selection of the group communication button by the user on the user interface, and initiating group communication of the contact with the device. Additional embodiments may include displaying a locking mechanism associated with the quick contact group shortcut.</p><p>Further embodiments include methods of operating a server in a group communication session between a plurality of user devices, the methods comprising: receiving a request for priority floor access from a first user device; arbitrating control and providing priority access to the first user device.</p><p>Further embodiments include methods of operating a server in a group communication session between a plurality of user devices, the methods comprising: receiving a request for a media lock from a first user device; and responsive to the request, a first user locking control of the floor of the group communication session for transmission of the media file(s) to the device.</p><p>Various embodiments include wireless communication devices and servers that include processors configured to perform the operations of an embodiment disclosed herein. Various embodiments also include wireless communication devices and servers comprising means configured to perform the operations of an embodiment disclosed herein. Various embodiments also include non-transitory processor and server-readable storage media having stored thereon processor-executable instructions configured to cause a processor to perform operations of the embodiment methods disclosed herein.</p>

BRIEF DESCRIPTION OF THE DRAWINGS The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate exemplary embodiments of the present invention and, together with the foregoing general description and the following detailed description, serve to explain the features of the present invention. 1 illustrates a wireless communication device suitable for use with various embodiments; 2 is a diagram illustrating the software layers of a group application client that may include "push to talk" (PTT) functionality. 3 illustrates an example system for group communication between a plurality of wireless communication devices. 4 depicts an example wireless network suitable for use with various embodiments. 5 is a process flow diagram of an embodiment method of group communication in which visual feedback regarding the status of a group communication session is displayed on a display screen of a wireless communication device; 6A-6C are screenshots of a touchscreen user interface of an embodiment wireless communication device. 7 is a process flow diagram of an embodiment method of group communication including displaying visual feedback indicating control of a floor in a PTT communication session. 8A-8C are screenshots of a touchscreen display illustrating an embodiment PTT communication session. 9A is a process flow diagram of an embodiment method of group communication that includes displaying visual feedback indicating a status of a floor in a group communication session. 9B is a process flow diagram of an embodiment method of group communication using a server that may transmit a status of floor control. 10A is a process flow diagram of an embodiment method of group communication that includes displaying visual feedback of a participation status of one or more devices in a communication group. 10B is a process flow diagram of an embodiment method of group communication that includes displaying visual feedback of a participation status of one or more devices and reason(s) for absence of at least one non-attending device in a communication group. 10C is a process flow diagram of an embodiment method of group communication using a server that may indicate to devices in the group a participation status and/or reason for absence(s) of at least one device in the group. 11A-11D are screenshots of an embodiment touchscreen display having a sliding lock mechanism. 12 is a process flow diagram of an exemplary method of group communication using a "hands-free" mode. 13A is a process flow diagram of an exemplary method of group communication using a "priority lock" mode. 13B is a process flow diagram of an embodiment method of server operation in a group communication session in which a user device requests priority floor access. 14A is a process flow diagram of an exemplary method of group communication using a "media lock" mode. 14B is a process flow diagram of an embodiment method of server operation in a group communication session in which a user device requests a media lock. 15A is a process flow diagram of an exemplary method of group communication using a "lockout" mode. 15B is a process flow diagram of an embodiment method of server operation in a group communication session in which a user device initiates a lockout mechanism. 16A is a process flow diagram of an exemplary method of group communication using a "blocking" mode. 16B is a process flow diagram of an embodiment method of server operation in a group communication session in which a user device initiates a blocking mechanism; 17A-17C are screenshots of an embodiment touchscreen display with a "Rapid Contact" group communication shortcut on the home screen. 18A is a process flow diagram of an exemplary method of group communication using a "rapid contact" group communication shortcut. 18B is a process flow diagram illustrating an embodiment method of group communication using a "quick contact" shortcut and a sliding locking mechanism. 19 is a system block diagram of a wireless communication device for use with various embodiments. 20 is a system block diagram of a server suitable for use with various embodiments.

Various embodiments will be described in detail with reference to the accompanying drawings. Wherever possible, the same reference numbers will be used throughout the drawings to refer to the same or like parts. References to specific examples and implementations are for purposes of illustration and are not intended to limit the scope of the invention or claims.

The word "exemplary" is used herein to mean "serving as an embodiment, illustration, or illustration." Any implementation described herein as "exemplary" is not necessarily to be construed as preferred or advantageous over other implementations.

The terms "mobile device", "mobile computing device" and "wireless communication device" are used herein to refer to cellular phones, smartphones, personal or mobile multimedia players, personal digital assistants (PDAs), laptop computers, any one of tablet computers, smartbooks, palmtop computers, wireless e-mail receivers, multimedia Internet enabled cellular telephones, wireless gaming controllers, and similar personal electronic devices including programmable processor and memory; Used interchangeably to refer to both, may include software and/or hardware to enable functionality of group communications, such as push-to-talk (PTT).

In summary, various embodiments provide improved group communication, such as "push-to-talk" (PTT), in a wireless communication device using native device hardware and software, such as a touchscreen display. The various embodiments may be implemented on a wide range of devices, including most Internet-enabled mobile phones and other wireless communication devices, and do not require dedicated hardware, such as a PTT button, to provide group communication functionality.

Previously, push-to-talk services required dedicated hardware, such as a PTT button, to allow users to utilize the service. The various embodiments provide a user experience that combines many of the benefits of a conventional hardware-based PTT service with a number of improved features made possible through the use of a group communication service implemented primarily through software.

Various embodiments are directed to a novel group communication interface that can provide improved functionality over conventional hardware implemented PTT services. Because the present embodiments are implemented primarily in software, the user no longer needs to "push" a physical button to speak. In various embodiments, the user interface may allow the user to "lock" control of the floor in a hand-free mode, which makes it easier for the user to multitask and the device speakerphone and/or Use earphone mode in a more natural way. Additional functionality may also be added, such as the ability to lock the floor's control over the media content, as well as the ability to at least temporarily modify the criteria for floor control and arbitration, which allows the user to prioritize access to the floor for a limited time. It may be useful when you wish to Additional functionality may also include the ability to lock out other devices in the communication group from receiving outgoing communications from the user's device as well as the ability to block the user's device from receiving group communications from other users. Some or all of this added functionality may be provided via target-based sliding locks, which may be implemented in touchscreen user interface displays.

Various embodiments further allow a user to create a "quick contact" shortcut on their home screen or as a device widget. Choosing this shortcut also includes a "hands-free" lock, a "one-click" advantage that users benefit from traditional hardware-implemented PTT but on a wider range of devices that may provide software-implemented group communication services. Floats on the screen a modified PTT "button" that may effectively have a PTT experience. The quick contact shortcut avoids the problem of the user having to find, launch and navigate through the group communication application program to speak the user's contact.

Various embodiments may implement a more previously employed visual experience, and may utilize visual feedback cues to the user that may augment or replace existing audio cues for floor control and intervention. Visual feedback cues may be provided via graphic elements and colors on a display screen of the wireless device. In various embodiments, the feedback queues may indicate the status of a group communication session, eg, control of a floor for group communication. In various embodiments, the display screen displays visual features that say when the floor is open to the user, when the floor is requested by the user's device, when the floor is controlled by the user's device or by a different device. It can also be displayed. In some embodiments, the display screen may also display visual representations of members of the group in the group communication, and may further display the participation status(s) of each member of the group. For example, the device may display members of the group currently participating in the group communication session as well as members of the group not participating in the group communication session. In various embodiments, the device may further display reasons members are absent. These improved features may be implemented in software running on the user's wireless device, and may also be implemented partially in a server.

Referring now to FIG. 1 , software and/or hardware to provide a group communication (eg, "push-to-talk" (PTT)) function that opens direct communication to an endpoint associated with a target device, eg, an IP address. An example wireless communication device, which may be a wireless communication device 100 comprising a In various embodiments, the wireless communication device 100 provides group communication functionality using only software and existing device hardware (eg, a conventional user interface/display such as a keypad or touchscreen interface). The embodiment device 100 of FIG. 1 is shown having a touchscreen interface/display 104 . In previous embodiments, no dedicated PTT hardware, such as a PTT button or dedicated PTT circuitry, is required to provide PTT functionality.

In various embodiments, the wireless communication device 100 may include a computer platform 106 capable of handling voice and data packets, executing software applications, and transmitting information across a wireless network. . The computer platform 106 includes, inter alia, a processor 108 , such as an application specific integrated circuit ("ASIC"), or a RISC processor, such as those implementing an ARM architecture. Processor 108 is typically mounted at the time of manufacture of wireless communication device 100 and is generally not upgradeable. The processor 108 or other processor executes an application programming interface ("API") layer 110 , which includes a resident application environment and an operating system loaded on the processor 108 . may be The resident application environment interfaces with any resident programs in memory 112 , such as a computer-readable storage medium of wireless communication device 100 .

As shown herein, the wireless communication device 100 may be a wireless communication phone having a graphical display 104 , but also a computer platform 106 as is known in the art, such as a personal digital assistant (PDA). ), a pager with a graphical display 104 , or even a separate computer platform 106 with a wireless communication portal, alternatively having a wired connection to a network or the Internet. Memory 112 may also be comprised of read-only or random access memory (RAM, ROM), EPROM, EEPROM, flash cards, or any memory common to computer platforms. The computer platform 106 may also include a local database 114 for storage of software applications that are not actively used in the memory 112 . Local database 114 generally consists of one or more flash memory cells, but is any secondary or tertiary storage device as is known in the art, such as magnetic media, EPROM, EEPROM, optical media, tape or soft or It may be a hard disk. The graphical display 104 may present information about the group call in progress as well as information about the data package to generate a preview, which is more fully described herein.

The computer platform 106 also includes a direct communication interface 116 configured to open a direct communication channel. The direct communication interface 116 may also be part of a standard communication interface for the wireless communication device 100 that normally carries voice and data transmitted to and from the wireless communication device 100 . The direct communication interface 116 is generally comprised of hardware as is known in the art.

2 is a diagram of one embodiment of the software layers of a group application client, which may include, but is not limited to, PTT functionality and data package functionality. Although the embodiments shown herein are implemented in PTT sessions, the present system may be used substantially concurrently in any group communication session setup for transmission of voice and/or data between group members. In one embodiment, the computer platform 106 in a wireless communication device environment includes: QUALCOMM® may include a set of software "layers" developed on top of baseband chipsets and system software, such as a wireless communications station modem (MSM) 218 and advanced wireless communications subscriber software (AMSS) 220 developed by . In this example, the underlying MSM chipset may implement the software protocol stack for the entire CDMA communication technologies, including CDMA2000 1X and CDMA2000 1xEV-DO. In this example, AMSS 220 is, in one embodiment, also QUALCOMM® Developed by BREW® may be configured to support the wireless communication operating system layer 222 . The wireless communication operating system layer 222 may provide an application programming interface for chip or device specific operations, while providing a separation layer that eliminates direct contact to AMSS and any OEM software on the computer platform. The wireless communication operating system layer 222 may enable application development that utilizes wireless communication device features without the need to rewrite the application each time a new release of device specific software is released.

In this example, the wireless communication operating system 222 may include a PTT client 226 configured to provide access to PTT services via an external interface (shown here in a PTT aware UI 224 ). The PTT client 226 may include all functions required to enable wireless communication operating system 222 applications, such as the media client 228 . In an embodiment, the PTT client 226 may maintain access to PTT services, respond to communication requests, and process all PTT-aware wireless communication operating system application requests for PTT services; It may process all outgoing PTT requests, collect and package vocoder packets that send PTT talk spurs, and analyze packets of vocoder data for incoming PTT talk spurs.

In various embodiments, the computer platform 106 in a wireless communication device environment is a wireless communication operating system that extends PTT services for access to media types other than conventional half-duplex voice communications (VoIP-PTT media). It may include a media client 228, which may be an underlying application. The media client 228 provides access to media services through an external interface, such as the Media Aware API, which is an application that may be developed entirely as a wireless communication operating system based application or may be used in conjunction with the AMSS 220 interface. You may. Media client 228 may service requests from a user and may direct the user to the result of any group-oriented media request. The media client 228 may be further configured to handle incoming notifications indicating that there is a data package to download from the media server 316 of FIG. 3 , and may be described in more detail below. For example, the media client 228 may be configured to download data packages immediately in one embodiment, or in other embodiments, the media client 228 may be configured at a predetermined time period, such as at 10:00 every day. pm may be configured to download the data package, or may be configured to allow the user to determine whether to download the file and/or when to download the file via the PTT UI 224 . Other applications 230 , which may be push-to-talk or other applications capable of receiving and transmitting data over a group communication channel, may also reside on the platform.

In some embodiments, software that enables PTT functionality in wireless communication device 100 may be pre-installed on the device during device manufacturing. In other embodiments, at least a portion of the software that provides PTT functionality may be downloaded to device 100 by an end user. In some embodiments, the PTT software may be a downloadable application (eg, a mobile app).

3 illustrates one or more in a PTT group 302 , such as a wireless communication device 100 , a smartphone 301 , a tablet computer 303 , a smart pager 304 , and a personal digital assistant (PDA) 306 . An exemplary embodiment of a system 300 for sharing data packages among wireless communication devices with other wireless communication devices is shown. In system 300 , each wireless communication device 100 , 301 , 303 , 304 , 306 may optionally communicate directly with a target set of one or more other wireless communication devices over a wireless communication network 308 . For example, a set of targets for the wireless communication device 100 may be in a communication group 302 or a subset thereof, such as a smartphone 301 , a tablet computer 303 , a pager 304 , and a PDA 306 . It may be all devices.

In one embodiment, the wireless communication device 100 may send at least a flag to the communication server 310 , which resides across the wireless network 308 in the server-side LAN 312 . The flag in this example may be used by the server to determine that the wireless device is present on the wireless network 308 , ie, accessible. The communication server 310 may share this information with a set of target communication devices designated by the first wireless communication device, or it may also be on the server-side LAN 312 or across the wireless network 308 . It may also be shared with other accessible computer devices. The communication server 310 may have an attached or accessible database 314 that stores group identification data for wireless devices. In various embodiments, a media server 316 , which may further include circuitry for a file management server, may reside in the server-side LAN 312 . It should be appreciated that the number of computer components on the server side LAN 312 or across the wireless network 308 or in the Internet in general is limited. Further, some or all functions of several server-side components described herein, such as communication server 310 , database 314 , and media server 316 , may be combined in a single device.

In various embodiments, communication server 310 (which may also be referred to as a group communication server) may establish point-to-point IP PTT channels between devices in group 302 . A PTT channel may be established over a (real or virtual) half-duplex channel between the communicating wireless communication device 100 , 304 and/or 306 and one or more other wireless communications of the target set. Also, in various embodiments, the communication server 310 can make a request with the target set if at least one of the wireless communication devices of the target set has notified the communication server 310 of their presence on the wireless network 308 . You may want to bridge the established direct communication.

The communication server 310 is also configured to return to the target set 302 if no wireless communication devices (or at least one) of the target set have notified the group communication server 310 of their presence on the wireless network 308 . An inability to bridge direct communication may be notified to the wireless communication device 100 , 304 , 306 . Also, although the communication server 310 is shown herein as having an attached database 314 of group identification data, the group communication server 310 device may have group identity data residing there, as described herein. It is also possible to perform all storage functions.

In various embodiments, communication server 310 may perform arbitration functions between competing requests of various wireless communication devices 100 , 304 , 306 for use of PTT communication channels across wireless network 308 . may be For example, in response to a request from the wireless communication device 100 to communicate with one or more other target devices in the PTT group 302 that includes all other devices in the group 302 , the communication server 310 may establish a PTT between the requesting device 100 and all or some of the requested target devices in the group 302 . Accordingly, the communication server 310 may grant control of the "floor" to the requesting wireless communication device 100 . When contention requests exist between devices in group 302 for control of a "floor," communication server 310 may arbitrate between the contention requests based on predetermined priority criteria. Priority criteria may be established at the time of PTT group 302 formation, such as by a group administrator, and may be stored in communication server 310 and/or database 314 . In various embodiments, the priority criteria may be default priority criteria stored in server 301 and/or database 314 . In some embodiments, the priority criteria may be established on an ad hoc basis by one or more of the wireless communication devices 100 , 304 , 306 in the PTT group 302 .

In overview, system 300 may include at least one wireless communication device, such as wireless communication device 100 , that may be a member of a PTT communication group 302 of wireless communication devices. The wireless communication devices in this example may be configured to communicate with each other or as a group across the wireless communication network 308 . Further, in various embodiments, at least one of the wireless communication devices may be configured to selectively transmit data packages to other members of the communication group 302 . The at least one communication server 310 may be configured to store information about the communication groups 302 in the wireless communication network 308 , the information including the identities of particular member wireless communication devices of the one or more communication groups. . The communication server 310 may be further configured to selectively receive data packages from a transmitting wireless communication group of the communication group 302 , such as the wireless communication device 100 .

In various embodiments, the media server 316 is configured to receive data packages from a wireless communication device (such as the wireless communication device 100 ) and to which members of the communication group 302 are stored across the wireless communication network 308 . It may be configured to selectively allow access to data packages. In an embodiment, data packages may include, but are not limited to, pictures such as JPEG, TIF, audio files such as MP3, MP4, WAV, etc., documents, and/or presentations. Data packages may further include streaming media such as multimedia applications (PowerPoint, MOV files, etc.). Data packages may also include half-duplex video conferencing between members of a communication group, wherein the speaker's video may be broadcast to other group members in substantially real time or delayed.

The size of the data package files can be very large, and because of a potential delay in transmitting the media or the inability of the receiving wireless communication device to handle the transmitted media, the system 300 is able to prevent the target members of the communication group 302 from receiving different PTTs. Media server 316 may be used to store data packages so that stored media can be selectively accessed without interrupting communications. Alternatively, in one embodiment, once the data packages are stored in the media server 316 , the media server 316 may be configured to transmit a hypertext link to the originating device or target wireless communication devices of the communication group 302 . have. The hypertext link in this example may provide a link to the stored group-oriented media at the media server 316 . Upon receipt of the data packages by at least one of the member wireless communication devices of the communication group 302 , the communication server 310 responds with an acknowledgment indicating that the at least one member wireless communication device of the communication group 302 has received the data package. may send to the wireless communication device 100 , 304 , 306 .

The wireless communication device 100 , 304 , 306 may transmit communication group identification data, such as a target list, to the communication server 310 at the time of transmitting the data package, such that the media server 316 is configured to transmit the data package based on various criteria. to be transmitted to or stored for member wireless communication devices identified in the communication group identification data. Alternatively, before the wireless communication device transmits the data packages, the wireless communication device 100 , 304 , 306 may request member data for the communication group 302 from the communication server 310 , the server 310 It may send one or more addresses or communication group addresses to the wireless communication device 100 , 304 , 306 . In an embodiment, the communication server 310 may filter the available potential communication groups based on the ability of member devices of the potential communication groups to receive data packages.

As further described herein, a wireless communication device 100 , 304 , 306 may participate in a communication group with member wireless communication devices of the communication group 302 , and during group communication in the same communication session, all members data packages may be sent to the s or a subset thereof. Alternatively, data packages may be transmitted independently in a group communication session.

4 illustrates an example wireless network in a common cellular communication configuration. The wireless network in this example includes a series of communication servers 310 that control communication between the wireless communication devices (devices 100-A-D) of the set group members in the PTT system. A wireless network is by way of example only and allows remote modules to communicate over-the-air (OTA) between components of a wireless network and to each other, including but not limited to wireless network carriers and/or servers. A series of communication servers 310 may be connected to a group communication server LAN 312 . Wireless devices 100 - A - D may request voice (eg, VoIP) and/or packet data sessions from group communication server(s) 310 .

With continued reference to the description of FIG. 4 , the communication server(s) 310 in this example is a wireless service provider's Packet Data Service Node (PDSN), such as a PDSN, shown herein as being in the carrier network 416 , 414) may be connected. When a wireless communication device accesses a wireless data network to obtain services, the PDSN 414 uses an authentication, verification, and accounting server ("AAA") to authenticate the wireless communication devices 100 , 304 , and/or 306 . ") 428 . The AAA 428 may be coupled to a database operable to store information such as user accounts and privileges. Each PDSN 414 may interface with the base station controller 418 of the base station 320 via a packet control function (PCF) 422 . PCF 422 may be located in base station 420 . The wireless network 308 may control messages (generally in the form of data packets) sent to a messaging service controller ("MSC") 424 . The carrier network 308 in this example may communicate with the MSC 424 by way of a network, the Internet, and/or a "plain ordinary telephone system" (POTS). In general, the network or Internet connection between the wireless network 308 and the MSC 424 carries data, and the POTS carries voice information. The MSC 424 may be connected to one or more base stations 420 . In a manner similar to a carrier network, the MSC 424 is generally connected to a branch-to-source (BTS) 426 by a network for data delivery and/or by both the Internet and a POTS for voice information, the BTS 426 transmits messages wirelessly to and from wireless devices, such as devices 100-A-D, which may be cellular telephones, via Short Message Service ("SMS") or other OTA methods known in the art. ultimately broadcast and receive by It should be noted that carrier boundaries and/or PTT operator network boundaries do not inhibit or prohibit sharing of data as described herein.

Wireless communication devices, such as mobile or cordless telephones, are being manufactured with increasing computing capabilities, as are personal computers and handheld PDAs. These "smart" cellular phones allow software developers to create downloadable and executable software applications on the processor of a wireless device. A wireless device, such as device 100, stores many types of "data packages" that are discrete segments of computer code such as applications, web pages, applets, MIDlets, multimedia, images, games, and simple data. You can download it. In wireless devices that have designated a communication group 302 (eg, represented by FIG. 3 ), the wireless communication device may connect directly with another member of the set and participate in voice and data communications. However, in various embodiments, such direct group communication may occur through or under the control of the group communication server 310 . Although not all data packets of the devices necessarily have to travel through the communication server 310 itself, in various embodiments, the communication server 310 can preferably ultimately control the communication, which is generally the case with the communication group. This is because it is a server-side component capable of recognizing and/or extracting the identities of the members of the communication group 302 or directing the identities of the members of the communication group 302 to another computer device.

5 is a process flow diagram illustrating an exemplary method 500 for communicating over a wireless network using a wireless communication device having group communication functionality, such as "push-to-talk" (PTT) functionality. Although various exemplary methods may be described herein as using a "push-to-talk: function, it will be understood that the exemplary methods may be applicable to other types of group communication. FIGS. 6A-6C . are screenshots of a touchscreen user interface 104 of an exemplary wireless communication device 100 suitable for practicing the method 500 in accordance with one embodiment. In various embodiments, the wireless communication device 100 includes software , and native hardware such as touchscreen display 104 and/or other user interfaces such as keypad interfaces to provide group communication such as PTT. In various embodiments, the PTT methods described herein may be implemented on a wide variety of devices, including most Internet-enabled mobile phones and other wireless communication devices. In various embodiments, the methods may be implemented using a wireless communication device that does not include dedicated PTT hardware, such as a PTT button or PTT specific circuitry.

As shown in method 500 , wireless communication device 100 may download group communication application software, such as PTT application software, in select block 502 . The group communication application software may include all or part of the group communication client software as described above with respect to FIGS. 1 and 2 . In various embodiments, the downloadable version of the group communication application software allows devices capable of supporting group communication to download and run the group communication application to provide group communication functionality to the wireless device. In other embodiments, the wireless device 100 may have factory-installed group communication application software, in which case the selection block 502 may not be performed.

The wireless communication device 100 may establish a group of one or more other wireless communication devices for group communication (eg, a "group communication group") at select block 504 . It will be appreciated that a group communication group may include one other device. A group communication group may also include a plurality of other devices that enable "multicast" or "broadcast" communication with a plurality of devices over a wireless network using the group communication function. As shown in FIGS. 6A-6C , a group communication group ("University Friends") is established comprising, for example, 6 devices, namely the user's own wireless device 100 and 5 other devices. .

In various embodiments, a group communication group may be established by a user or users of various wireless devices, eg, in an ad hoc process. The establishment of a group communication group may be performed through or under the control of a server, such as the communication group server 310 described above with respect to FIGS. 3 and 4 . A plurality of different group communication groups may be established, and a single wireless communication device 100 may be included in a plurality of different group communication groups, and may communicate with devices in any one of the groups using the group communication function. can also communicate. In some embodiments, one or more group communication groups may have been previously established on wireless communication device 100 , such as by a system administrator, in which case selection block 504 may not be performed.

At block 506 , the wireless communication device 100 may cause the group communication function to be initiated in response to an input from a user of the device 100 . For example, a user may select from a menu and launch a group communication application on the wireless device 100 using a suitable user interface, such as the touchscreen display 104 of FIGS. 6A-6C . Initiating the group communication function may also include selection of a group communication group to establish group communication with, where the group communication group may consist of one or more wireless communication devices.

At block 508 , the wireless communication device 100 may display the status of the group communication session using visual feedback on the display screen 104 of the device 100 . As described in more detail below, in various embodiments the display screen 104, which is configured as a touchscreen, can be configured to display a floor state (ie, an open floor, an approved floor, etc.), a state of other group member(s), Visual feedback cues including graphical elements and/or colors may be displayed to indicate various states of the group communication session, such as the presence of long connection times, and the like.

Referring to the exemplary embodiments of the touchscreen display 104 shown in FIGS. 6A and 6B , there is shown a touchscreen display 104 in which a group communication application, specifically a PTT application, is disclosed. The display 104 identifies the group 602 with which the PTT communication session has been established, and further displays a plurality of icons 604 representing individual members of the group 602 . A virtual PTT button 606 is displayed on the screen 104 . In various embodiments, the virtual PTT button 606 may function much like a conventional hardware PTT button. When the device 100 detects a touch event on the virtual button 606 , the device 100 sends a request to open a communication channel from the wireless device 100 to the other device(s) in the PTT group to the communication server 310 . can also be sent to 6B shows a PTT session in which a PTT session is initiated, such as by a user's finger 610 touching the virtual PTT button 606 but no communication channel is currently established (ie, a "floor" is open). Illustrated an exemplary embodiment of a display 104 indicating a neutral state of 6C shows that a user's finger 610 is touching the virtual button and a communication channel from the wireless device 100 to other devices in the group is established and open (ie, the "floor" is a wireless communication device). Illustrated display 104 (approved for 100 ). In this state, the wireless communication device 100 may transmit voice and/or other data to other device(s) across the wireless network in the PTT group. As shown in FIG. 6C , this state (ie, the floor approved for device 100 ) may be indicated by a change in color across a portion 608 of the display 104 .

7 is a process flow diagram illustrating an embodiment method 700 of group communication, such as PTT communication, using visual feedback of the status of the group communication session. At block 702 , the wireless communication device 100 may initiate a group communication session as described above. At block 704 , device 100 may display the status of the group communication session using visual feedback on display screen 104 , which may be a touchscreen display. At block 706 , device 100 may detect initiation of a group communication by a user on a user interface of device 100 . In various embodiments, this may include detection of a touch event in a "virtual" PTT button as described in connection with FIG. 6A . In other embodiments, as in devices that do not have a touchscreen interface, this may include detection of a key input on a keypad interface. At block 708 , the device 100 may send a request for a "floor" for group communication to a server, such as the communication server 310 described above. At block 710 , the device 100 may display a visual feature(s) indicating the group communication status of the requested but not granted floor. In various embodiments, the visual characteristics for this state may correspond to the "neutral" state shown in FIG. 6B . In other embodiments, this status may be indicated by a color coding, such as a red or yellow screen, when the floor has been requested but not granted, which is a different color such as green when the device 100 has granted to the floor. can be changed to While the floor has been requested but not yet granted (ie, decision block 712 = No), device 100 may continue to display visual features indicative of this status. When the floor is approved (ie, decision block 712 = Yes), the device 100 may display visual features indicating that the floor is approved for the user's device 100 . As noted above, these visual features may include a color change (such as from red or yellow to green) of all or a portion of the display screen 104, or it may include display of other graphical feedback cues. . In addition to the visual feedback cues described herein, audio or haptic cues may also be employed to indicate the status of group communication.

8A-8C are additional screenshots of a touchscreen display 104 illustrating an embodiment group communication session, in particular a PTT communication session. FIG. 8A shows a screen displaying visual features indicating that the floor is authorized for the user's device 100 described above with respect to FIG. 6C . In this embodiment, the device 100 displays a color change across the portion 608 of the screen when the floor is approved. A user's thumb 610 is shown touching the screen. 8B shows a screen replaying visual features indicating a neutral state with the floor open. In this embodiment, the display 104 indicates that the floor is open, and that a touch event (eg, "push to talk") on the display 104 or portion 804 thereof causes the device 100 to group It may indicate that it will request control of the floor for communication. 8C shows a screen displaying visual features indicating that another user's device has control of the floor. This condition may be indicated by a graphic and/or color change on the display screen 104 . In this embodiment, this status is indicated by displaying a contact icon 802 (eg, a photographer) of a user having a device currently controlling the floor (eg, the person speaking) in the group communication session.

9A is a process flow diagram illustrating an embodiment method 900 of group communication, using visual feedback of the status of a group communication session. At block 902 , the user's wireless communication device 100 may receive, from a server, such as the group communication server 310 described above, a communication indicating a status of floor control in the group communication session. When the floor is approved for the user's device (ie, determination block 904 = Yes), the device 100 indicates at block 906 the group communication status of the floor approved for the user's device 100 . Temporal features may be displayed on a display screen. Visual features may include graphical elements and/or changes in color as described above. An example of a device screen in a group communication state of a floor approved for a user's device according to an embodiment is shown in FIG. 8A . When the floor is controlled by another device in the group communication group (ie, decision block 908 = yes), the device 100 determines at block 910 the group communication state that the floor is authorized for a different user's device. may be displayed on the display screen 104 . Visual features may include graphical elements and/or changes in color as described above. An example of the device screen in this state is shown in FIG. 8C . In this embodiment, the visual feature may include the user's contact icon with the device controlling the floor in group communication as shown in FIG. 8C . When the floor is not controlled by the user's device (ie, decision block 906 = No), and when the floor is not controlled by any other device in the group communication group (ie, decision block 908 = No) No), the device 100 may display visual features on the display screen 104 indicating a neutral state with the floor open at block 912 . Visual features may include graphical elements and/or changes in color as described above. An example of a screen in a neutral state according to an embodiment is shown in FIG. 8B .

The device 100 maintains various visual feedback characteristics corresponding to the group communication state at blocks 906 , 910 , 912 , respectively, respectively, until the device 100 receives the floor state communication from the server at block 902 . Alternatively, the above process may be repeated.

9B is a process flow diagram illustrating an exemplary method 901 of group communication using a server, such as group communication server 310 shown in FIGS. 3 and 4 . The server 310 may receive requests from user devices in the group communication group for control of a floor in the group communication session at block 914 . The server 310 may determine control of the floor based on predetermined criteria, as described above, at block 916 . The server 310 may transmit messages to the devices in the group indicating the device having control of the floor at block 918 . The server 310 may also transmit media content and/or other data to the devices in select block 920 . The transmitted data may be usable by the devices in displaying visual feedback of the status of floor control in the group communication session. For example, server 310 may send image file(s) or other information that may be displayed by devices in the group while the particular device has control of the floor. In various embodiments, devices may determine whether to use the transmitted data in displaying a visual indication of the status of floor control.

Referring back to FIGS. 8A-8C , in various embodiments, the wireless communication device 100 may include a display 104 that displays visual feedback of the participation status of one or more devices in a group communication, such as a PTT communication. can In various embodiments, device 100 may display visual feedback indicating users not available from the group as well as users available to participate in group communication from the group. In various embodiments, device 100 may also display the reason(s) for one or more users not being available to participate in the group communication. As shown in FIG. 8A , display screen 104 of device 100 may display an identification of the group in which the group communication session was initiated, which may include a group name (eg, "College Friends"), a list of members of the group. number as well as group members currently participating in the group communication session (eg, "you + 3/5"). Display screen 104 may also display icons 810 , 812 , 814 representing each of the members of the group. Display screen 104 may only display a limited number of icons, and may include a separate icon 816 that allows the user to view icons of additional group members. Icons may include group members' photos 810 when available, and may include a default icon 812 when a photographer is not available. Icon 814 represents a member of a group that is not participating in a group communication session. In various embodiments, the icon 814 of the absent group member may include different visual characteristics than the icons 810 , 812 of the participating group members. In the embodiment illustrated in FIG. 8A , for example, icon 814 has a darker color than other icons 810 , 812 and also partially fades out. Any suitable graphical features may be used to indicate the participation state(s) of the various members. In various embodiments, the display 104 may include visual features indicating the reason for the absence of one or more group members. In some embodiments, the user indicates that the member is busy (eg, on another call), unreachable (eg, the member's device is outside the coverage area or is not enabled for group communication), is unavailable (eg, , the user's device is turned off), or clicks on the absent member's icon 814 to display a reason for absence, such as , the user's device is turned off), or alternatively is not participating in the call (eg, the member "silences his/her device"). " has been set). In various embodiments, the user may set the status of his or her wireless device (eg, "I am in a meeting and cannot speak until 2 pm"), and the reason for non-attendance is that of other members of the group. It may be displayed on devices.

10A is a process flow diagram illustrating an embodiment method 1000 of group communication that includes visual feedback of the participation status of one or more devices in the communication group. At block 1002 , the wireless communication device 100 may receive a request to initiate and/or participate in a group communication session with a group consisting of one or more member devices. The request may be received from a user of device 100 on a user interface or keypad interface, such as a touchscreen display. The request may also be received from another device in the communication group or from a server, such as group communication server 310 . At block 1004 , the device 100 may display a visual representation of one or more members of the communication group on a display screen. The visual representation of one or more members may include icons representing each of the members of the group, as shown in FIG. 8A . In various embodiments, various members of a communication group may be accessed from memory on device 100 . In some embodiments, members of a communication group may be determined through communication with a server, such as group communication server 310 , or through communication with one or more other devices on a wireless network. At block 1006 , the device 100 may determine the participation status of each member of the group. Determining the participation status may include determining whether each member device is participating in or not participating in a group communication session. In various embodiments, the participation status of various members may be determined via communication with a server, such as group communication server 310 , or via one or more other devices on a wireless network. At block 1008 , the device 100 may display visual features indicative of a participation status of each of one or more members of the group. In various embodiments, the icon representing the absent group member may include different visual characteristics than the icon of the participating group members, as shown in FIG. 8A . When the group member's participation status changes (ie, determination block 1010 = YES), the device 100 may determine updated participation states at block 1006 , indicating the updated participation states at block 1008 . Visual features may be displayed. This may continue while the session is active (ie, decision block 1012 = no). The session may end at block 1014 (ie, decision block 1012 = yes).

10B is an embodiment of a group communication including visual feedback of the participation status of one or more group member devices in the group communication and additional display of reason(s) for non-attendance by one or more non-attending group member devices in a communication session. A flowchart illustrating a method 1001 . Blocks 1016 - 1020 are similar to blocks 1002 - 1006 of method 1000 shown in FIG. 10A , and initiate a group communication session with a group of one or more devices in block 1016 , and/or receiving a request to participate in such a group communication session, displaying a visual representation of one or more members of the communication group at block 1018 , and determining the participation status of each member of the group at block 1020 . includes doing The wireless communication device 100 may determine reason(s) for absences for one or more absent group members at block 1022 . In various embodiments, reasons for absence may include, for example, that a particular member is busy, the member's communication device is unreachable, or otherwise the member's device is unavailable. The user's device 100 may display visual features indicative of the participation status of each member of the group at block 1024 . In various embodiments, the user's device 100 may receive, in optional block 1028 , a request from the user on the user interface to display one or more reason(s) for non-attendance by one or more non-attendance members. A request to display the reason(s) for non-attendance may be made, for example, by clicking on the icon of the non-attending member. In response to the request, the device 100 may display the reason(s) for non-attendance on the display screen 104 at block 1028 . In some embodiments, optional block 1028 may be omitted, and device 100 may automatically display one or more reason(s) for absence at block 1028 . When the participation status of one or more group members changes (ie, determination block 1030 = Yes), device 100 determines the updated participation status at block 1020 and any new non-attendance members at block 1022 . may determine the reason for non-attendance by , and display the updated participation status and non-attendance reasons in blocks 1024 and 1028, respectively. Likewise, if the reason for absence of one or more members changes (ie, determination block 1032 = Yes), device 100 may proceed to block 1020 to update the participation status and reasons for absence, and blocks 1024, 1028) may display the updated status and reasons. This may continue until the group communication session ends at block 1036 (ie, decision block 1034 = yes) (ie, decision block 1034 = no).

10C is a process flow diagram illustrating an embodiment method 1003 of operation of server 310 in a group communication session. In some embodiments, method 1003 of FIG. 10 may be performed in conjunction with method 1000 and/or method 1001 of FIGS. 10A and 10B , respectively. The server 310 may receive a request to initiate a group communication session sent from a wireless communication device at block 1038 . The server 310 may determine the participation status of each member of the group at block 1040 . For non-attendance group members, server 310 may determine reason(s) for non-attendance at block 1042 . The server 310 may send a communication to the at least one participating group member device indicating the participating status of the at least one other group member and/or the reason(s) for the at least one non-attending member, at block 1044 . When the participation status of one or more group members changes (ie, decision block 1046 = Yes), or when the reason for non-attendance changes (ie, decision block 1048 = Yes), the server 310 at block 1022 Proceed to block 1020 to determine updated participation statuses and reasons, and at block 1044 may send a communication to the at least one participating group member to update the participation status and reasons for non-attendance. This may continue until the group communication session ends at block 1052 (ie, decision block 1050 = yes) (ie, decision block 1050 = no).

11A-11D illustrate a user-actuated locking mechanism that may be used to secure control of a floor in a group communication (eg, PTT) enabled device 100 device for "hands-free" operation. ) are screenshots of the touchscreen display 104 illustrating In FIG. 11A , display 104 includes a virtual PTT button 1102 . In various embodiments, the virtual PTT button 1102 may function much like a conventional hardware PTT button. When the device 100 detects a touch event on the virtual button 1102, the device 100 sends a request to open a communication channel from the wireless device 100 to the other device(s) in the PTT group to the communication server 310 can also be sent to 11B illustrates the display screen 104 indicating that the user's finger 610 is touching the display screen 104 and that the floor has been approved for the user's device 100 . As described above, the display screen 104 may use graphical elements or visual feedback, such as color coding, to indicate to the user that the floor has been approved.

In some embodiments, in a conventional mode of operation, device 100 may maintain floor control while the device detects a touch event on screen 104 or a portion thereof. Thus, the device may operate like a conventional PTT enabled device with a dedicated PTT button that the user must hold the PTT button depressed while communicating with the group. Accordingly, in order to communicate with at least one other member of the communication group, the user must maintain constant touch contact with the screen 104 . Even if the user maintains touch contact with the screen, the user's device may have control of the floor by another device having a higher priority than the original user's device in the group, for example as determined by the server 310 . You may still lose control of the floor if you request them at the same time.

In various embodiments, in addition to the conventional mode described above, device 100 may further include a "hands-free" mode, in which the user is required to maintain constant contact with the screen. It is also possible to activate a locking mechanism that maintains control of the floor (ie, "locks" the floor) without need. A user initiated locking mechanism may take various forms, such as a virtual button on a touchscreen interface/display or key entry on a conventional keypad interface. 11B , the locking mechanism 1104 may be a sliding lock on the touchscreen display 104 . The sliding lock may be a "target-based" lock, which is locked by a user touching the screen at a first position and then sliding his or her finger 610 towards a second "target" position on the screen. This means that it can also be activated. Device 100 may detect a touch event on the first location and sliding movement of finger 610 towards a second "target" location. When device 100 detects finger 610 within a predetermined proximity to a target location, device 100 may enter a "hands-free" mode, in which device 100 It maintains an open communication channel without requiring continuous user contact with the user interface. In the example shown in FIGS. 11A and 11B , the first position may be the virtual PTT button 1102 in FIG. 11A , and the second or "target" position is the "slide to lock" bar in FIG. 11B . (bar) can also be The user may activate the "hands-free" mode by sliding his or her finger 610 from the virtual PTT button 1102 to the "slide lock" bar 1104 . This triggers the sliding lock mechanism. Device 100 may provide visual and/or audible feedback of entering "hands-free" mode. For example, as shown in FIG. 11C , upon entering the "hands-free" mode, the "fixed slide" bar 1104 may disappear, and the "slide to unlock" bar 1106 may disappear. may be displayed at different positions. In various embodiments, a "hands-free" mode may allow the user to maintain an open PTT communication channel without physically contacting the user interface or even holding the device. 11C , in "hands free" mode, the device may retain control of the "floor" for group communication when the user's finger 610 is removed from the screen 104 . Device 100 may use a speakerphone option. In certain embodiments, as shown in FIG. 11D , the hand-free mode is BLUETOOTH® It may be used in conjunction with an earphone device 1110 , such as a headset, which may be connected to device 100 via a suitable link, which may be a wireless link 1108 , such as a wireless link.

The device 100 determines that the device 100 loses control of the floor (eg, the server 301 grants control of the floor to another device based on server floor arbitration priority rules), or the user unlocks It may remain in hand-free mode until activating the king mechanism. In various embodiments, the unlocking mechanism may be the same mechanism as the locking mechanism, and the user may toggle between a locked state and an unlocked state. Thus, to deactivate the locking mechanism, the user may slide the locking mechanism (eg, a virtual display on the touchscreen interface) in the opposite direction to the locking movement to activate the locking mechanism to deactivate the locking mechanism. The unlocking mechanism may be a virtual button on a touchscreen interface/display or a keystroke on a conventional keypad interface. 11C , the unlocking mechanism 1106 may be a sliding lock on the touchscreen display 104 . A sliding lock may be a "target-based" lock, as described above. In the example shown in FIG. 11C , the user may touch a first location, which may be in the central area of display 104 , and move his or her finger to "slide unlock" bar 1106 , which may be You can also slide to the "target" position. When device 100 detects a user's finger within a predetermined proximity of "slide unlock" bar 1106, the device may exit "hands-free" mode, disarm the lock mechanism, It is also possible to return to the conventional mode of operation.

12A is a process flow diagram illustrating an embodiment method 1200 of group communication, such as PTT communication, with a wireless communication device 100 using a "hands-free" mode. The device 100 may begin a group communication session at block 1202 , and may determine a state of the group communication at block 1203 . The device 100 may display the status of the group communication session on the display screen 104 using virtual feedback at block 1204 . Device 100 may receive a user input on a user interface to cause group communication to be initiated at block 1206 . The user input may be a touch event on a touchscreen, such as a touch event on a virtual PTT button, as described with respect to FIGS. 11A-11D . In other embodiments, the user input may be an input on a keypad interface. Device 100 may send a request for control of a "floor" in a group communication session to a server, such as communication server 310 , at block 1208 . If control of the floor is not granted (ie, decision block 1210 = No), the device may proceed to block 1203 to determine a status of group communication. If control of the floor is granted (ie, determination block 1210 = YES), then device 100 may establish an open group communication channel with one or more devices in the communication group at block 1212 . The device 100 may display on the display screen 104 virtual feedback indicating the group communication status of the floor approved for the user's device at block 1214 .

The device may display an indication that the user has the ability to lock the floor at block 1215 . This may include displaying a locking mechanism on the screen, such as the "Slide Lock" indication in FIG. 11B . Device 100 may detect activation of the locking mechanism by a user on the user interface at block 1216 . In various embodiments, the user initiated locking mechanism may be, for example, a virtual button on a touchscreen interface/display or key input on a conventional keypad interface. In some embodiments as shown in FIGS. 11A-11D , the locking mechanism 1104 may be a sliding lock on the touchscreen display 104 . A sliding lock may be a "target-based" lock, in which a user activates the lock by touching the screen at a first position and then sliding his or her finger toward a second "target" position on the screen. means it may be

While the locking mechanism is activated, device 100 may maintain the opened group communication channel in "hands-free" mode at block 1218 . As noted above, the "hands-free" mode of device 100 allows the device to remain on the floor, without the need for the user to constantly maintain contact with the user interface, as is the case with conventional PTT-enabled devices. maintain control of (ie, "lock" the floor). The device 100 may provide an indication of the group communication status of the locked floor to the user's device at block 1220 . For example, device 100 may provide audible feedback to indicate that the floor is locked relative to the user's device in a "hands-free" mode and/or display visual feedback on display screen 104 . You may. Device 100 may remain in a "hands-free" mode while the locking mechanism remains activated (ie, decision block 1222 = yes). A user may unlock device 100 by activating an unlocking mechanism, which, in various embodiments, may be the same as a locking mechanism, for moving the indicator in the opposite direction to locking. It may involve unlocking the locking mechanism by means of a virtual button on a touchscreen interface or a keystroke on a keypad interface. 11A-11D , the unlocking mechanism 1106 may be a sliding lock on the touchscreen display 104 . A sliding lock may be a "target based" lock, in which the user unlocks the device by touching the screen at a first location and then sliding his or her finger towards a second "target" location on the screen. It means you can

When the locking mechanism is deactivated or no longer activated (ie, decision block 1222 = No), the device 100 may exit the "hands-free" mode at block 1224 and the floor is no longer activated. It may also provide an indication that it is not locked to the user's device. Device 100 may continue group communication (ie, decision block 1227 = yes), and in block 1229 , in response to a user input (eg, the user is continuously touching the touchscreen), the communication channel or the device may not continue to communicate at block 1231 (ie, decision block 1227 = no) and may close the communication channel. In various embodiments, a locking mechanism as described above with respect to FIGS. 11A-11D and 12 may be used to cause other PTT modes to be initiated as an alternative to or in addition to the "hands-free" mode described above. may be In some embodiments, device 100 may include a plurality of user initiated locking mechanisms, such as, for example, virtual buttons on a touchscreen interface/display and/or keystrokes on a conventional keypad interface. may be In some embodiments, device 100 may include a sliding lock on touchscreen display 104 as shown in FIGS. 11A-11D . A sliding lock may be a "target based" lock having a plurality of different "target" positions on the screen. The user may activate and deactivate different locks by touching the screen in a first position and then sliding his or her finger towards different "target" positions on the screen. Different target locations may correspond to different PTT modes according to various embodiments.

13A is a process flow diagram illustrating an embodiment method 1300 of group communication, such as PTT communication, with a wireless communication device 100 using a "priority lock" mode. The priority lock mode may be used when a user desires priority access to a "floor" in group communications. In various embodiments, initiation of a "priority lock" mode may provide the device uninterrupted control of the floor in group communication while the priority lock is activated. In various embodiments, initiation of a priority lock by the user's device may temporarily change the priority rules used by server 310 in arbitrating among different devices in the group for control of the floor. may be In various embodiments, the priority lock mode sets the device ( 100) can also be used to provide

In the exemplary method 1300 shown in FIG. 13A , the device 100 may determine a state of a group communication session at block 1302 . The device 100 may display the status of the group session on the display screen 104 using virtual feedback at block 1304 . Device 100 may receive a user input on a user interface to initiate group communication at block 1306 . The user input may be a touch event on a touchscreen, such as a touch event on a virtual PTT button, as described with respect to FIGS. 11A-11D . In other embodiments, the user input may be an input on a keypad interface. The device 100 may send a request for control of a "floor" in the group communication session to a server, such as the communication server 310 , at block 1308 . If control of the floor is not granted (ie, determination block 1310 = No), the device may determine an updated status of the group communication at block 1302 and display the updated status at block 1304 . . If control of the floor is granted (ie, determination block 1310 = YES), the device 100 may establish an open group communication channel with one or more devices in the communication group at block 1312 . The device 100 may display on the display screen 104 virtual feedback indicating the group communication status of the floor approved for the user's device at block 1314 . Device 100 may further provide an indication to the user that a priority locked mode is available.

The device 100 may detect activation of the priority locking mechanism by a user on the user interface at block 1316 . In various embodiments, the user initiated locking mechanism may be, for example, a virtual button on a touchscreen interface/display or key input on a conventional keypad interface. In some embodiments, the locking mechanism may be a sliding lock on the touchscreen display 104, such as the sliding locking mechanism shown in FIGS. 11A-11D . A sliding lock may be a "target-based" lock, in which a user activates the lock by touching the screen at a first position and then sliding his or her finger toward a second "target" position on the screen. means it may be In various embodiments, the sliding lock may include a plurality of target locations on the display screen, where each target location initiates a different group communication of the device. For example, a first target location may correspond to a "priority lock" mode, and a second target location may correspond to another mode, such as the "hands-free" mode described above with respect to FIG. 12 .

Upon detection of user initiation of the priority locking mechanism at block 1316 , the device 100 may send a request for priority floor access to a server, such as the communication server 310 , at block 1318 . If the request is not granted (ie, decision block 1320 = No), the device 100 may communicate over the group communication channel in a non-priority locked mode at block 1332 . If the request is granted (ie, decision block 1320 = yes), the device 100 may maintain the group communication channel in a "priority locked" mode at block 1322 , and at block 1324 the user's The device 100 may display the status of the locked floor priority. In various embodiments, priority lock mode may provide device 100 with control of the floor, which may not generally be interrupted by another device in the group. While the priority locking mechanism is activated (ie, decision block 1326 = yes), the device may keep the group communication channel in a "priority lock" mode at block 1322 . If the priority locking mechanism is no longer activated (ie, determination block 1326 = No), the device 100 may exit the priority locking mode at block 1328 indicating that the floor is no longer priority locked. An indication may also be provided. Device 100 may notify server 310 at block 1330 that priority floor access is no longer requested. The device 100 may continue to communicate over the group communication channel in a non-priority locked mode at block 1332 .

In some embodiments, the priority locking mechanism may allow a user to lock the device to one of a plurality of different priority levels. This may be similar to an automotive transmission gearshift, where different priority levels are similar to different gears of the transmission (eg, first gear, second gear, third gear, etc.). it is possible that the first priority locking level provides a first level of priority access to the floor control, the second priority level provides a second progressively higher level of priority access to the floor control, etc. do. The various priority levels may be activated using a target based sliding lock mechanism as described above, wherein the user may activate priority locking of progressive levels using the locking mechanism.

13B is a process flow diagram illustrating an embodiment method 1301 of operation of server 310 in a group communication session, such as a PTT communication session, in which a user device requests priority floor access. In some embodiments, the method 1301 of FIG. 13B may be performed in conjunction with the method 1300 of FIG. 13A . The server 310 may receive a request for priority floor access from the first user device 100 at block 1334 . The server 310 may determine whether to grant or deny the request at decision block 1336 . The server 310 may deny the request (ie, decision block 1336 = "no"), for example, if the priority request feature is not authorized or otherwise not available to the requesting user device 100 ). . The server 310 may then send a message to the first user device 100 that the request for priority floor access is denied at block 1346 , according to the general priority rules at block 1344 ( That is, it may arbitrate floor control of the group communication session (without providing priority access to the first user device 100 ). If server 310 approves the request for priority access (ie, decision block 1336 = "Yes"), server 310 sends a message at block 1338 that priority floor access is granted to the first user It may transmit to device 100 . At block 1340 , the server 310 may arbitrate floor control of the group communication session, and priority floor access is provided to the first user device 100 . In various embodiments, the server 310 may grant the first user device 100 priority floor access by granting the floor immediately, regardless of whether another device currently has the floor, and , may grant uninterrupted control of the floor to the first user device 100 until the first user device 100 indicates that priority floor access is no longer requested. The server 310 may receive a message from the first user device 100 that priority floor access is no longer requested at block 1342 . The server 310 may then arbitrate floor control of the group communication session (ie, without providing priority access to the first user device 100 ) according to the general priority rules at block 1344 . have.

In various embodiments, the server 310 may grant priority access to the user device for a predetermined maximum period of time, and if no message is received from the user device 100 within that period of time, the server ( 310 may release user device 100 from priority floor access. Server 310 may also implement priority rule(s) to handle floor control in cases where more than one user device simultaneously requests priority floor access.

14A is a process flow diagram illustrating an embodiment method 1400 of group communication, such as PTT communication, with a wireless communication device 100 using a "media lock" mode. Media lock mode allows a user to wish priority access to a "floor" to send media file(s) to one or more members of a group in group communication, while still allowing other devices to send voice data to the group. It can also be used when Media files may include, for example, image files, video files, audio files, documents and presentations, and the like. In certain embodiments, initiation of a "media lock" mode may provide the device uninterrupted control of the floor to transmit media files in group communication while the media lock is activated. In various embodiments, initiation of a media lock by a user's device overrides the priority rules used by server 310 in arbitrating floor control for transmitting media files among different devices in a communication group. It may be changed temporarily.

In the embodiment method 1400 shown in FIG. 14A , the device 100 may determine a status of the group communication session at block 1402 , and use the visual feedback at block 1404 to determine the determined status of the group communication session. may be displayed on the display screen 104 . The device 100 may detect activation of the media locking mechanism by a user on the user interface at block 1406 . In various embodiments, the user initiated media locking mechanism may be, for example, a virtual button on a touchscreen interface/display or keystroke on a conventional keypad interface. In some embodiments, the media locking mechanism may be a sliding lock on the touchscreen display 104, such as the sliding locking mechanism shown in FIGS. 11A-11D . A sliding lock may be a "target-based" lock, in which a user activates the lock by touching the screen at a first position and then sliding his or her finger toward a second "target" position on the screen. means it may be In various embodiments, the sliding lock may include a plurality of target locations on the display screen, where each target location initiates a different group communication of the device. For example, a first target location may correspond to a "media lock" mode, and one or more additional target location(s) may be in another mode, such as the "hands-free" mode described above with respect to FIG. 12 and/or FIG. 13A . It may correspond to the "priority lock" mode described above in relation to .

Upon detection of user initiation of the media locking mechanism at block 1406 , the device 100 may send a request for a media lock to a server, such as the communication server 310 , at block 1408 . If the request is not granted (ie, determination block 1410 = No), the device 100 may transmit media in the normal manner over the non-"media-locked" channel at block 1428 . If the request is granted (ie, determination block 1410 = YES), the device 100 may establish the group media communication channel at block 1412 , and select the group media communication channel as "media locked" at block 1414 . You can keep it in " mode. The device 100 may display on the display screen 104 visual features indicative of the group communication status of the approved media lock at block 1416 . While the media locking mechanism is activated (ie, determination block 1418 = Yes), the device 100 may maintain the group media communication channel in a media locked mode at block 1414 . When the media locking mechanism is no longer active (ie, decision block 1418 = No), the device 100 may send a message to the server 310 to terminate the media lock at block 1422 . Device 100 may cease the media communication (ie, decision block 1424 = No), and may close the group media communication channel at block 1426 . The device may, alternatively, continue with the media communication (ie, determination block 1424 = YES) and transmit the media over the non-"media locked" channel at block 1428 .

14B is a process flow diagram illustrating an embodiment method 1401 of operation of server 310 in a group communication session, such as a PTT communication session, wherein the user device "media locks" for transmission of media file(s). to request In some embodiments, the method 1401 of FIG. 14B may be performed in conjunction with the method 1400 of FIG. 14A . The server 310 may receive a request for a media lock from the first user device 100 at block 1430 . The server 310 may determine whether to grant or deny the request at decision block 1432 . Server 310 may deny the request (ie, decision block 1432 = "No"), for example, if the media lock feature is not authorized or otherwise available to the requesting user device 100 . The server 310 may then send a message to the first user device 100 that the request for media lock is denied at block 1442 , and according to the general priority rules at block 1440 (ie, may arbitrate floor control of a group communication session for transmission of media files (without providing a media lock to the first user device 100 ). If server 310 approves the request for priority access (ie, decision block 1432 = "Yes"), server 310 sends a message at block 1434 that priority floor access is granted to the first user It may transmit to device 100 . At block 1336 , the server 310 may lock control of a floor for transmission of the media file(s) to the device 100 of the first user. In various embodiments, once the floor is "locked" to the first user's device 100 for transmission of media files, the server 310 is configured to use the floor for voice communication among the various user devices in the communication group. Control may still be arbitrated. The server 310 may receive a message from the first user device 100 that priority floor access is no longer requested at block 1438 . The server 310 may then arbitrate floor control for transmission of the media files (ie, without providing the media lock to the first user device 100 ) according to the general priority rules at block 1440 . may be

In various embodiments, server 310 may grant a media lock to user device 100 for a predetermined maximum period of time, within which time no message is received from user device 100 , Server 310 may release the media lock. Server 310 may also implement priority rule(s) to handle floor control in cases where more than one user device simultaneously requests a media lock.

15A is a process flow diagram illustrating an exemplary method 1205 of PTT communication with a wireless communication device 100 using a "lockout" mode. The lockout mode may be used by a user to temporarily exclude one or more members of the group communication group from receiving communications from the user's device 100 during a group communication session.

In the exemplary method 1500 shown in FIG. 15A , the device 100 may initiate a group communication session, such as a PTT communication, at block 1502 . The device 100 may display the status of the group communication session on the display screen 104 using virtual feedback at block 1504 . The device 100 may detect activation of the locking mechanism by a user on the user interface at block 1506 . In various embodiments, the user initiated lockout mechanism may be, for example, a virtual button on a touchscreen interface/display or a keystroke on a conventional keypad interface. In some embodiments, the media locking mechanism may be a sliding lock on the touchscreen display 104, such as the sliding locking mechanism shown in FIGS. 11A-11D . A sliding lock may be a "target-based" lock, in which a user activates the lock by touching the screen at a first position and then sliding his or her finger toward a second "target" position on the screen. means it may be In various embodiments, the sliding lock may include a plurality of target locations on the display screen, where each target location initiates a different group communication of the device. For example, a first target location may correspond to a "lockout" mode, and the one or more additional target location(s) may be in another group communication mode, such as the "hands-free" mode described above with respect to FIG. 12 and/or It may correspond to the "media lock" mode described above with respect to FIG. 14A .

In various embodiments, the user may select one or more members of the group to "lock out" from the group communication. The user may, for example, select a contact icon representing a particular group member and may activate a lockout mechanism that locks out the group member from group communication. In some embodiments, the contact icon of the group member to be locked out may be a "target" in a target-based sliding lock mechanism. The user may slide his or her finger to the specific contact icon(s) to lock out each user(s) from group communication. In some embodiments, the user may drag contact icons to an additional target location, such as a "lockout" icon, to initiate lockout mode for that group member. In other embodiments, device 100 may display a locking mechanism (eg, a slide lock bar, "virtual" switch, toggle, button, etc.) associated with each contact icon. The locking mechanism may be displayed, for example, after the user first touches the contact icon. Activating the locking mechanism may invoke a lockout mode for the selected group member.

Upon detection of user initiation of the lockout mechanism at block 1506 , the device 100 communicates with one or more devices in the group, excluding the device(s) of the group member(s) locked out at block 1508 . A group communication channel may be established. This may involve temporary reconfiguration of the group communication session, which may be performed by or in conjunction with the group communication server 310 , as described below. The user device 100 may exclude the device(s) of the group member(s) locked out from the outgoing group communication at block 1510 . Device 100 may display visual features on display screen 104 indicating that a lockout is activated for the group member(s) selected at block 1512 . While the lockout is activated (ie, decision block 1514 = yes), the device 100 sends the device 100 of the group member(s) locked out from the outgoing group communication from the user's device 100 to the device ( ) can be excluded further. When the lockout mechanism is no longer activated (ie, decision block 1514 = No), device 100 determines at block 1516 the device(s) of the previously locked out group member(s) in the outgoing group communication. ) may be included. In other words, the group communication session may revert to its original configuration.

15B is a process flow diagram illustrating an embodiment method 1501 of operation of a server 310 in a group communication session, such as a PTT communication session, wherein lockout on a user device for at least one other user device in the communication group. The mechanism is activated. In some embodiments, the method 1501 of FIG. 15B may be performed in conjunction with the method 1500 of FIG. 15A . At block 1518 , the server 310 may configure group communication among the plurality of user devices in a general manner. The server 310 may receive an indication from the first user device 100 that a lockout mechanism has been activated for at least one second user device in the communication group at block 1520 . The server 310 may (temporarily) reconfigure the group communication session to exclude communication from the first user device 100 from being received by "locked out" devices at block 1522 . The server 310 waits at block 1526 for the reconfigured group until the server 310 receives an indication from the first user device 100 that the lockout is no longer invoked for the at least one second user device. A communication session may be maintained (block 1526). The server 310 may revert to the initial configuration of the group communication session at block 1528 .

16A is a process flow diagram illustrating an embodiment method 1600 of group communication, such as PTT communication, with a wireless communication device 100 using a "blocking" mode. The blocking mode may be used during the group communication session to temporarily block the user's device 100 from receiving communications from the device(s) of one or more selected members of the group communication session.

In the exemplary method 1600 shown in FIG. 16A , the device 100 may initiate a group communication session at block 1602 . The device 100 may display the status of the group session on the display screen 104 using virtual feedback at block 1604 . Device 100 may detect activation of a blocking mechanism by a user on the user interface at block 1606 . In various embodiments, the user initiated blocking mechanism may be, for example, a virtual button on a touchscreen interface/display or key input on a conventional keypad interface. In some embodiments, the media locking mechanism may be a sliding lock on the touchscreen display 104, such as the sliding locking mechanism shown in FIGS. 11A-11C . A sliding lock may be a "target-based" lock, in which a user activates the lock by touching the screen at a first position and then sliding his or her finger toward a second "target" position on the screen. means it may be In various embodiments, the sliding lock may include a plurality of target locations on the display screen, where each target location initiates a different group communication of the device. For example, a first target location may correspond to a "blocking" mode, and the one or more additional target location(s) may be in another mode, such as the "hands-free" mode described above with respect to FIG. 12 , with respect to FIG. 13A . may correspond to the "priority lock" mode described above, the "media lock" mode described above with respect to FIG. 14A , and/or the "lockout" mode described with respect to FIG. 15A .

In various embodiments, the user may select one or more members of the group to "block" from receiving the group communication by the user's device 100 . The user may, for example, select a contact icon representing a particular group member, and may initiate a blocking mechanism that blocks communication from the selected group member. In some embodiments, the contact icon of a group member to be blocked may be a "target" in a target-based sliding lock mechanism. The user may slide his or her finger to the specific contact icon(s) to block each user(s). In some embodiments, the user may drag a specific group member's contact icon to a target area, such as a "blocking" icon, to effect blocking. In other embodiments, device 100 may display a locking mechanism (eg, slide lock bar, "virtual" switch, toggle, button, etc.) associated with each contact icon. The blocking mechanism may be displayed, for example, after the user first touches the contact icon. Activating the blocking mechanism may effect blocking of the selected group member.

Upon detection of user initiation of the blocking mechanism at block 1606 , the device 100 may block communication from the selected blocked group member(s) from being received by the user's device 100 at block 1608 . have. Device 100 may display visual features on display screen 104 indicating that blocking is activated for the group member(s) selected at block 1610 . While blocking is in effect (ie, decision block 1612 = yes), the device 100 may continue to block communication of the group member(s) blocked at block 1608 . When the blocking mechanism is no longer activated (ie, determination block 1612 = No), device 100 may receive a communication from previously blocked group members at block 1614 .

In some embodiments, the blocking mode is in that the user does not hear or see communication from the blocked group member(s) but other users in the group may still receive communication from the blocked member(s). , similar to the "silent" button. In some embodiments, the blocking function may be implemented on the user device 100 without the knowledge or intervention of the server. In other embodiments, user device 100 may signal a server, such as group communication server 310 , to a server, such as group communication server 310 , when a blocking mechanism is activated, which server 310 indicates that communication from the blocked device is blocked by the blocking device ( 100) may reconfigure the communication session so that it is not transmitted to . In some embodiments, activating a blocking mechanism for a device of a group member may block the selected device from sending any communication to the group (eg, it may cause the blocked device to gain control of the "floor") may be prevented). In this embodiment, upon activation of the blocking mechanism, device 100 may send a request to a server, such as group communication server 310 , to block the specified device from communicating with the group. The server 310 may be stored in the server 301 , for example, the priority status of the user requesting blocking, the priority status of the user requesting to be blocked, the number of different blocking requests received for a particular user. It may determine whether to block the device based on predetermined blocking criteria, which may include, etc.

16B is a process flow diagram illustrating an embodiment method 1601 of operation of a server 310 in a group communication session, such as a PTT communication session, wherein a blocking mechanism on a user device for at least one other user device in the communication group this is triggered In some embodiments, the method 1601 of FIG. 16B may be performed in conjunction with the method 1600 of FIG. 16A . At block 1616 , the server 310 may configure group communication among the plurality of user devices in a general manner. The server 310 may receive an indication from the first user device 100 that a blocking mechanism has been activated for at least one second user device (ie, a "blocked" device) in the communication group at block 1618 . have. The server 310 may (temporarily) reconfigure the group communication session to exclude communications from "blocked" devices from being received from the first user device 100 at block 1620 . As noted above, in various embodiments, server 310 may reconfigure the group communication session such that communication from a "blocked" device is not received at any other devices in the communication group. The server 310 waits in block 1624 for the reconfigured group until the server 310 receives an indication from the first user device 100 that the blocking mechanism is no longer activated for the at least one second user device. A communication session may be maintained (block 1622). The server 310 may revert to the initial configuration of the group communication session at block 1626 .

17A-17C are screenshots of a touchscreen display 104 of a wireless communication device 100 having a "quick contact" PTT shortcut on a desktop/home screen of the device 100 . 17A , device 100 may cause a user to display one or more shortcut icons 1704 for a PTT contact on home screen 1702 . A PTT contact may be an individual PTT user or a group of PTT users. Selection of the shortcut icon 1704 may bring up a modified PTT button 1706 , as shown in FIG. 17B . Device 100 may detect a touch event on PTT button 1706 and, in response, may establish a PTT communication channel with the device of the contact represented by icon 1704 . As shown in FIG. 17C , the modified PTT button may also support a slide lock feature 1708 in certain embodiments. The slide lock feature 1708 may cause a "hands-free" mode of operation and/or any of the modes of operation described above with respect to FIGS. 12-16B to be initiated. This is an improvement over existing non-dedicated hardware solutions in that the user does not need to find/launch/navigate to the PTT application to speak their contact quickly.

18A is a process flow diagram illustrating an exemplary method 1800 for group communication, such as PTT communication, using the "rapid contact" shortcut. The wireless communication device 100 may display the at least one quick contact group communication shortcut on the home screen of the device display 104 at block 1806 . Display 104 may be a touchscreen display. The quick contact shortcut icon(s) may be set up by a user, or may be automatically generated by device 100, for example, based on contact information stored in the device.

Device 100 may detect a user selection of a quick contact group communication shortcut on the user interface at selection block 1806 , and in step 1808 , associated with the quick contact shortcut icon, a group communication button (eg, a PTT button) ) can be displayed and played. In some embodiments, the optional step 1806 may be omitted, and the device 100 may automatically display a group communication button in connection with the quick contact shortcut at step 1808 . In some embodiments, the group communication button may include all or part of a quick access group communication shortcut icon. Device 100 may detect selection of a group communication button by a user on the user interface at block 1808 . In various embodiments using a touchscreen display, device 100 may detect a touch event on a group communication button. Device 100 may initiate group communication with the device of the selected contact at block 1810 .

18B is a process flow diagram illustrating an embodiment method 1801 of group communication, such as PTT communication, using a "quick contact" shortcut and sliding locking mechanism. Blocks 1812-1816 are similar to blocks 1802-1806 of method 1800 shown in FIG. 18A , in block 1812 at least one quick click on the home screen of wireless communication device display 100 . displaying the contact group communication shortcut icon, detecting selection of the rapid contact group communication shortcut icon by the user on the user interface at optional block 1814, and the rapid contact group communication shortcut at block 1816 and displaying a group communication button (eg, a PTT button) in association with the icon. Device 100 may detect activation of the locking mechanism by a user on the user interface at block 1820 . The locking mechanism may be a sliding lock displayed in response to a user selection of a group communication button as shown in FIGS. 17A-17C . Activation of the sliding lock may cause a "hands-free" mode of operation to be initiated. Device 100 may initiate group communication with the device of the selected contact in "hands-free" mode at block 1822 . In alternative embodiments, the sliding lock mechanism may initiate any of the modes of operation described above with respect to FIGS. 12-16B .

19 is a system block diagram of a wireless communication device for use with any of the embodiments. The embodiments may be implemented in various mobile wireless communication devices, particularly mobile computing devices. One example of a wireless communication device that may implement various embodiments is the smartphone 2800 illustrated in FIG. 19 . A wireless communication device, such as a smartphone 2800 , may include a processor 2801 coupled to a memory 2808 and to a radio frequency data modem 2805 . The modem 2805 may be coupled to an antenna 2804 that receives and transmits radio frequency signals. The smartphone 2800 may also include a display 2803 , such as a touchscreen display. Mobile device 2800 may also include user input devices, such as buttons 2806 for receiving user inputs. In various embodiments, the smartphone 2800 may be positioned (eg, using E-Sense technology) on the display 2803 , on the back side 2812 , or on another surface of the mobile device 2800 . and a tactile output surface that may be The mobile device processor 2801 is any programmable microprocessor, microcomputer, or number that can be configured by software instructions (applications) to perform various functions, including the functions of the various embodiments described herein. may be a processor chip or chips of In general, software applications may be stored in the internal memory 2802 before they are accessed and loaded into the processor 2801 . In some mobile computing devices, additional memory chips (eg, a secure data (SD) card) may be plugged into the mobile device and coupled to the processor 2801 . The internal memory 2802 may be volatile or non-volatile memory, such as flash memory, or a mixture of both. For purposes of this description, general reference to memory refers to all memory accessible by the processor 2801 , including internal memory 2802 , removable memory that plugs into a mobile device, and memory within the processor 2801 . do.

The various embodiments may be implemented in any of a variety of commercially available server devices, such as the server 2900 illustrated in FIG. 20 . Such a server 2900 generally includes a processor 2901 coupled to a volatile memory 2902 , and a large capacity non-volatile memory, such as a disk drive 2903 . The server 2900 may also include a floppy disk drive, compact disk (CD), or DVD disk drive 2906 coupled to the processor 2901 . Server 2900 also has network access ports 2904 coupled to processor 2901 to establish data connections with a network 2905, such as a local area network, coupled to other broadcast system computers and servers. may include Processors 2801 and 2901 are any programmable microprocessor, microcomputer, or number of processors that can be configured by software instructions (applications) to perform various functions, including those of the various embodiments described above. It may be a chip or chips. In some devices, multiple processors 2801 , 2901 may be provided, such as a processor dedicated to wireless communication functions and one processor dedicated to running other applications. In general, software applications may be stored in internal memory 2802 , 2902 , 2903 before they are accessed and loaded into the processor 2801 , 2901 .

Processors 2801 and 2901 may include internal memory sufficient to store application software instructions. In many devices, the internal memory may be volatile or non-volatile memory, such as flash memory, or a mixture of both. For purposes of this description, generic reference to memory refers to all memory accessible by the processors 2801, 2901, including internal memory or removable memory that plugs into the device, and memory within the processors 2801, 2901 itself. refers to

The foregoing method descriptions and process flow diagrams are provided by way of illustration only, and are not intended to require or imply that the steps of the various embodiments must be performed in the order presented. As will be appreciated by one of ordinary skill in the art, the order of steps in the embodiments described above may be performed in any order. Words such as "then", "after", "then", etc. are not intended to limit the order of the steps; These words are simply used to guide the reader through the description of the methods. Also, any reference to claim elements in the singular, for example, using the articles "a", "an" or "the" is not intended to limit the element to the singular.

Those skilled in the art may implement the various illustrative logical blocks, modules, circuits, and algorithm steps described in connection with the embodiments disclosed herein as electronic hardware, computer software, or combinations of both. To clearly illustrate this interchangeability of hardware and software, various illustrative components, blocks, modules, circuits, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system. Skilled artisans may implement the above-described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present invention.

The various illustrative logical blocks, modules, and circuits described in connection with the embodiments disclosed herein include a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), may be implemented or performed by a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination of those designed to perform the functions disclosed herein. have. A general purpose processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. A processor may also be implemented in a combination of computing devices, eg, a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in association with a DSP core, or any other such configuration. Alternatively, some steps or methods may be performed by circuitry specific to a given function.

In one or more exemplary aspects, the functions described above may be implemented in hardware, software, firmware, or any combination thereof. If implemented in software, the functions may be stored on a tangible computer-readable medium as one or more instructions or code. The steps of a method or algorithm disclosed herein may be embodied in a processor-executable software module, which may reside or be stored on a non-transitory computer-readable storage medium or processor-readable medium. Non-transitory computer-readable and processor-readable storage media may be any available media that may be accessed by a computer or processor. By way of non-limiting example, such computer readable medium may contain RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or required program code in the form of instructions or data structures. may include any other medium that can be used for storage as a computer and that can be accessed by a computer. As used herein, disk and disk include compact disk (CD), laser disk, optical disk, digital versatile disk (DVD), floppy disk and Blu-ray disk, where disk is Usually, data is reproduced magnetically, and a disc optically reproduces data using a laser. Combinations of the above should also be included within the scope of non-transitory computer-readable media. Additionally, the operations of a method or algorithm may include one or any combination or set of codes and/or instructions in a non-transitory processor-readable medium and/or computer-readable medium, which may be included in a computer program product. may reside as

The previous description of the disclosed aspects is provided to enable any person skilled in the art to make or use the present invention. Various modifications to these aspects will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments without departing from the spirit and scope of the invention. Accordingly, the present invention is not intended to be limited to the exemplary embodiments shown herein but is to be accorded the broadest scope consistent with the principles and novel features disclosed herein.