Patent Description:
The invention is as set out in the independent claims. Preferable features of the invention are defined in the appended dependent claims.

As noted above, public safety personnel use electronic communication devices to communicate with each other. The personnel may be assigned to one or more talkgroups. A talkgroup is a defined group of communication devices that share communications with each other via one or more communication modalities. As explained below, each talkgroup may utilize particular types of applications, for example, based on a role of participants of the talkgroup. In one example, one talkgroup is established for a group for firefighting personnel, while another talkgroup is used by medical response personnel.

When a user is assigned to multiple talkgroups, the user may be associated with a different roles in each talkgroup. As a user switches communications between each talkgroup, it may become complicated for the user to navigate to necessary applications for the different talkgroups. Accordingly, systems and methods described herein provide, among other things, a graphical user interface for improved transition between talkgroup communications.

One example embodiment provides a communication device including a user input interface, a display, and an electronic processor communicatively coupled to the display. The electronic processor is configured to generate, on the display, a graphical user interface, generate, on the display, a first screen including a first plurality of applications related to a first talkgroup that the communication device is associated with, the first plurality of applications including applications related to an incident associated with the first talkgroup, receive, via the user input interface, a user input indicative of a request to change talkgroups, and generate on the display, in response to the user input, a second screen including a second plurality of applications related to a second talkgroup that the communication device is associated with, the second plurality of applications including applications related to an incident associated with the second talkgroup.

Another example embodiment provides a method of navigating between multiple talkgroups on a communication device. The method includes generating, on a display, a graphical user interface, generating, on the display, a first screen including a first plurality of applications related to a first talkgroup that the communication device is associated with, the first plurality of applications including applications related to an incident associated with the first talkgroup, receiving, via a user input interface, a user input indicative of a request to change talkgroups, and generating on the display, in response to the user input, a second screen including a second plurality of applications related to a second talkgroup that the communication device is associated with, the second plurality of applications including applications related to an incident associated with the second talkgroup.

For example, although the examples described herein are in terms of public safety personnel, in further embodiments, the methods described herein may be applied to different communication groups (for example, manufacturing personnel).

For ease of description, some or all of the example systems presented herein are illustrated with a single exemplar of each of its component parts. Some examples may not describe or illustrate all components of the systems. Other example embodiments may include more or fewer of each of the illustrated components, may combine some components, or may include additional or alternative components.

<FIG> is a diagram of a communication system <NUM> according to one example. In the example shown, the communication system <NUM> includes electronic communication devices <NUM>, <NUM>, and <NUM>. In the following description, when explaining how a single electronic communication device functions, a reference to electronic communication device <NUM> is used. The electronic communication devices <NUM> and <NUM> may be configured similarly. It is not necessary, however, that the electronic communication devices <NUM>, <NUM>, and <NUM> be identical. The electronic communication devices of the communication system <NUM> are merely examples. In some embodiments, the communication system <NUM> may include more or fewer communication devices than illustrated in <FIG>.

The electronic communication devices <NUM>, <NUM>, and <NUM> communicate with each other over a communication network <NUM>. The network <NUM> may be a wireless communication network. All or parts of the network <NUM> may be implemented using various existing networks, for example, a cellular network, the Internet, a land mobile radio (LMR) network, a Bluetooth™ network, a wireless local area network (for example, Wi-Fi), a wireless accessory Personal Area Networks (PAN), a Machine-to-machine (M2M) autonomous network, and a public switched telephone network. The network <NUM> may also include future developed networks. In some embodiments, the network <NUM> may also include a combination of the networks mentioned.

Each of the electronic communication devices <NUM>, <NUM>, and <NUM> is associated with one or more talkgroups. In the illustrated embodiment, devices <NUM> and <NUM> are associated with a first talkgroup 110A and devices <NUM> and <NUM> are associated with a second talkgroup 110B. A talkgroup may be defined or assigned based on various criteria. For example, a talkgroup may be established for devices associated with a particular public safety organization or department, a particular incident, a particular member role or designation, or a combination thereof. For example, a talkgroup may relate to an organization of first responders, a group of police officers, a fire incident, or a combination thereof. Similarly, a talkgroup may relate to members having the same role or designation (for example, police officer, detective, supervisor, paramedic, firefighter, and the like). As another example, paramedics and firefighters might be grouped into two different talkgroups even though they are responding to the same public safety incident.

The talkgroups and communications therebetween may be managed by a communications controller <NUM>. The communications controller <NUM> may be a server that is centrally maintained, for example, at a call center or public safety command center. The communications controller <NUM> may control communication between the devices <NUM>, <NUM>, and <NUM> over the network <NUM> in accordance with talkgroup affiliation. In some embodiments, the system <NUM> includes more than one communications controller. Alternatively, in some embodiments one or more of the communication devices of the system <NUM> may be configured to manage and monitor one or more talkgroups and communications thereof.

The electronic communication device <NUM> (described in more detail below in regard to <FIG>) may be a handheld communication device, for example, a mobile telephone or other portable communication device, smart watch or other smart wearable, or other device configured to communicate over the network <NUM>. In the illustrated embodiment, the communication device <NUM> is configured to communicate via one or more communication modalities, for example text messaging and push-to-talk (PTT) communications.

In some embodiments, the electronic communication device <NUM> may be distributed over more than one device. For example, the communication device <NUM> may be a portable touchscreen display device paired to a portable /handheld radio carried by a public safety officer or first responder, such as a police officer via a personal area network (for example, via a Bluetooth network, Zigbee network, and other network or connection). In some embodiments, the electronic communication device <NUM> is a mobile communication device mounted in or on a vehicle (for example, a police vehicle). In some embodiments, the electronic communication device <NUM> may be a device maintained, for example, at a call center or public safety command center.

<FIG> is a block diagram of a communication device <NUM>. In the example shown, the communication device <NUM> includes an electronic processor <NUM>, a memory <NUM>, and an input/output interface <NUM>. The illustrated components, along with other various modules and components are coupled to each other by or through one or more connections including, for example, control or data buses that enable communication therebetween. The use of control and data buses for the interconnection between and exchange of information among the various modules and components would be apparent to a person skilled in the art in view of the description provided herein.

The electronic processor <NUM> obtains and provides information (for example, from the memory <NUM> and/or the input/output interface <NUM>), and processes the information by executing one or more software instructions or modules, capable of being stored, for example, in a random access memory ("RAM") area of the memory <NUM> or a read only memory ("ROM") of the memory <NUM> or another non-transitory computer readable medium (not shown). The software can include firmware, one or more applications, program data, filters, rules, one or more program modules, and other executable instructions. The electronic processor <NUM> is configured to retrieve from the memory <NUM> and execute, among other things, software related to the control processes and methods described herein.

The memory <NUM> can include one or more non-transitory computer-readable media, and includes a program storage area and a data storage area. The program storage area and the data storage area can include combinations of different types of memory, as described herein. The memory <NUM> may take the form of any non-transitory computer-readable medium. In the embodiment illustrated, the memory <NUM> stores, among other things, one or more applications <NUM>. Each of the applications are configured to perform a particular function and/or provide access to features of the device when executed by the electronic processor <NUM>. Functions and features include, for example, texting, audio communications, retrieving and displaying information from a public and/or private database (for example, weather, dispatch control, etc.), video/camera capture, and the like. Such applications may include, for example, a messaging application that provides features to support the composition and sending of electronic messages that include alphabetic and numeric characters, for example, a cellular text messaging application, an instant messaging application, and the like. Another application may provide features to support the reception and transmission of PTT calls. Such calls may be one-to-one calls or group calls and may be transmitted over cellular networks, data networks, radio networks and the like (for example, those described above in regard to the transceiver <NUM>).

The input/output interface <NUM> is configured to receive input, via one or more user input devices or interfaces, and to provide system output via one or more user output devices. The input/output interface <NUM> obtains information and signals from, and provides information and signals to (for example, over one or more wired and/or wireless connections) devices both internal and external to the communication device <NUM>. In the illustrated embodiment, the input/output interface <NUM> includes an audio sensor <NUM>, an audio speaker <NUM>, and a display <NUM>. The display <NUM> may be, for example, a liquid crystal display (LCD) touch screen, or an organic light-emitting diode (OLED) touch screen. Output may also be provided via an audio speaker <NUM>. The audio speaker <NUM> is a transducer that produces sound from electrical signals (for example, generated from an audio stream) received from the electronic processor <NUM>. Alternative embodiments may include additional output mechanisms, for example, haptic feedback motors and light sources (not shown). Input may be provided via the audio sensor <NUM>. The audio sensor <NUM> is configured to capture audio. The audio sensor <NUM> may be, for example, a microphone.

In the illustrated embodiment, input is also provided by a rotary knob <NUM>. The rotary knob <NUM> is a mechanical knob interface. In particular, the rotary knob <NUM> is rotatable through a plurality of positions, wherein each of the plurality of positions is associated with a particular transmission channel. Accordingly, user input received through the rotary knob <NUM> includes selection of one of the plurality of positions (e.g., through clockwise rotation or counter-clockwise rotation of the rotary knob <NUM>). In some embodiments, the rotary knob <NUM> provides input for a primary function independent of a software application of the device <NUM>. For example, when the display <NUM> is displaying an application screen generated by the processor <NUM> and the rotary knob <NUM> receives user input (i.e., is rotated), the operation of the rotary knob <NUM> does not modify the operation or output of the application. The rotary knob <NUM> may be, for example, (when the device <NUM> is a converged radio device) a channel selection knob provided for selecting a transmission channel (e.g., for radio transmissions) or a volume knob for adjusting an output volume of the audio speaker <NUM>. As explained in more detail below, the rotary knob <NUM> may be utilized by a user of the device <NUM> to navigate between talkgroups and pluralities of applications associated with each talkgroup. In some embodiments, the rotary knob <NUM> is a virtual knob, for example, presented via a graphical user interface or using touch-sensitive surfaces.

Input may also be provided, for example, via a keypad, soft keys, icons, or soft buttons on the display, a scroll ball, buttons, and the like. The input/output interface <NUM> includes a graphical user interface (GUI) (for example, generated by the electronic processor <NUM>, from instructions and data stored in the memory <NUM>, and presented on the display <NUM>) that enables a user to interact with the communication device <NUM> (for example, to execute one or more of the applications <NUM>).

The transceiver <NUM> is configured for wireless coupling to wireless networks (for example, land mobile radio (LMR) networks, Long Term Evolution (LTE) networks, Global System for Mobile Communications (or Groupe Spécial Mobile (GSM)) networks, Code Division Multiple Access (CDMA) networks, Evolution-Data Optimized (EV-DO) networks, Enhanced Data Rates for GSM Evolution (EDGE) networks, <NUM> networks, <NUM> networks, combinations or derivatives thereof, and other suitable networks, including future-developed networks. Alternatively, or in addition, the electronic communication device <NUM> may include a connector or port (not shown) for receiving a connection to a wired network (for example, Ethernet). The electronic processor <NUM> is configured to operate the transceiver <NUM> to receive input from and to provide system output, or a combination of both. The transceiver <NUM> obtains information and signals from, and provides information and signals to, (for example, over one or more wired and/or wireless connections) devices (including, in some embodiments, from the communication controller) both internal and external to the electronic communication device <NUM>.

The electronic processor <NUM> obtains and provides information (for example, from the memory <NUM> and/or the transceiver <NUM>), and processes the information by executing one or more software instructions or modules, capable of being stored, for example, in a random access memory ("RAM") area of the memory <NUM> or a read only memory ("ROM") of the memory <NUM> or another non-transitory computer readable medium (not shown). The software can include firmware, one or more applications, program data, filters, rules, one or more program modules, and other executable instructions. The electronic processor <NUM> is configured to retrieve from the memory <NUM> and execute, among other things, software related to the control processes and methods described herein.

<FIG> is a flowchart illustrating an example method 300A of navigating between multiple talkgroups on a communication device. As an example, the method 300A is described as being performed by the electronic communication device <NUM> and, in particular, the electronic processor <NUM>. However, it should be understood that in some embodiments, portions of the method 300A may be performed by other devices, including, for example, the communications controller <NUM>.

At block 302A, the electronic processor <NUM> generates, on the display <NUM>, a graphical user interface and, at block 304A, associates (or assigns) the communication device <NUM> with a first talkgroup (for example, talkgroup 110A). At block 306A, the electronic processor <NUM> presents, on the display <NUM>, a first application related to the first talkgroup. The first application may be, for example, a PTT communications application for communicating with the users of the devices of the first talkgroup via a PTT call. The first application may be a particular application common to each of the devices of the first talkgroup 110A.

At block 308A, the electronic processor <NUM> receives, via a user input interface (an input device or interface of the input/output interface <NUM>), a user input indicative of a request to change talkgroups. As described below in regard to <FIG>, the user input may be, for example, a gesture on the display <NUM> (in embodiments where the display <NUM> is a touchscreen) or an actuation of a particular mechanical input of the device <NUM> (for example, a rotation of the rotary knob <NUM>). In embodiments where the rotary knob <NUM> provides input for a primary function independent of software, the rotary knob <NUM> provides input for a secondary function (as described above, switching between talkgroups). In some embodiments, a user input via the rotary knob <NUM> is indicative of a request to change talkgroups when an additional input is received (for example, while a user of the device <NUM> is touching the display <NUM>).

The electronic processor <NUM>, in response to the user input, associates (or assigns) the communication device <NUM> with a second talkgroup (for example, the talkgroup 110B) at block 310A and presents, on the display <NUM>, a second application related to the second talkgroup. The second application may be, for example, a messaging communications application for communicating with the users of the devices of the second talkgroup. In some embodiments, the second application is the same as the first application. In such embodiments, content of the applications may differ based on the talkgroup. For example, when both the first and second application are a group messaging application, a conversation thread of the first talkgroup is displayed within the first application while a conversation thread of the second talkgroup is displayed within the second application. As explained in more detail below, each talkgroup may be associated with an incident. In such embodiments, the first and second application may each be based on the incident associated with the first and second talkgroup respectively.

Although the method 300A above is described in terms of a single application being associated with each talkgroup, as mentioned previously, each talkgroup may utilize multiple applications when handling an incident. Accordingly, it may be particularly complicated for a user to navigate to the necessary application(s) when switching between talkgroups. In some embodiments, the method 300A is further configured to provide quick access to multiple applications associated with the multiple talkgroups in addition to simple transitioning between talkgroups.

<FIG> is a flowchart illustrating an example method 300B of operating a communication device associated with multiple talkgroups. As an example, the method 300B is described as being performed by the electronic communication device <NUM> and, in particular, the electronic processor <NUM>. However, it should be understood that in some embodiments, portions of the method 300B may be performed by other devices, including, for example, the communications controller <NUM>. The method 300B may be considered a particular embodiment of the method 300A. As such, portions of the method 300B are similar to those of the method 300A described above.

At block 302B, the electronic processor <NUM> generates, on the display <NUM>, a graphical user interface. At block 304B, the electronic processor <NUM> generates, on the display <NUM>, a first screen including a first plurality of applications related to a first talkgroup that the communication device <NUM> is associated with (for example, the talkgroup 110A). The first plurality of applications include applications related to an incident associated with the first talkgroup 110A.

<FIG> illustrates the electronic communication device <NUM>. A first screen <NUM> is shown on the display <NUM>. The first screen <NUM> includes a plurality of applications <NUM> related to the talkgroup 110A. As mentioned above, the plurality of applications <NUM> include applications related to an incident associated with the first talkgroup 110A. For example, in the illustrated embodiment, the talkgroup 110A is associated with an ongoing robbery incident. The plurality of applications may include, for example, a summary of the first talkgroup 110A (a role type of the talkgroup or participants of the talkgroup, a list of the participants of the talkgroup, and the like), a summary of recently accessed talkgroups of the device <NUM>, and information regarding the incident associated with the first talkgroup 110A. In the illustrated embodiment, the first screen <NUM> includes applications related to the robbery (an incident identifier 406A, a map of the robbery location 406B, and captured media or video of the robbery 406C). In some embodiments, the first plurality of applications may include a search bar (for example, search bar 406D). The search bar is configured to search local databases and resources (for example, applications and files stored on the device <NUM>), external databases and resources (for example, webpages and files online) for information based on one or more entered terms. As shown in the illustrated embodiment, the search bar 406D may include one or more suggested search terms. The search terms may be related to the incident associated with the first talkgroup 110A. The suggested search terms may be generated automatically based on the incident, one or more terms detected within the plurality of applications <NUM>, or both. The suggested search terms may be generated based on previously searched terms performed.

Returning to <FIG>, at block 306B, the electronic processor <NUM> receives, via a user input interface (an input device or interface of the input/output interface <NUM>), a user input indicative of a request to change talkgroups. As illustrated in <FIG>, the user input may be a gesture (for example, a swipe 408A) on the display <NUM>. Alternatively or additionally, the user input may be an actuation (a rotation 408B) of the rotary knob <NUM>.

Returning to <FIG>, at block 308B, the electronic processor <NUM> generates on the display <NUM>, in response to the user input, a second screen including a second plurality of applications related to a second talkgroup that the communication device <NUM> is associated with (for example, the second talkgroup 110B). The second plurality of applications include applications related to an incident associated with the second talkgroup 110B.

<FIG> illustrates the electronic communication device <NUM>. A second screen <NUM> is shown on the display <NUM>. The second screen <NUM> includes a plurality of applications <NUM> related to the talkgroup 110B. As mentioned above, the plurality of applications <NUM> include applications related to an incident associated with the second talkgroup 110B. For example, in the illustrated embodiment, the talkgroup 110B is associated with a robbery investigation. Accordingly, the second screen <NUM> includes applications related to the robbery investigation (an incident identifier 414A, a case summary 414B, and a timeline of the robbery 414C). The second plurality of applications <NUM> may include one or more applications similar to those described above in regard to the first plurality of applications <NUM>.

In some embodiments, the first plurality of applications <NUM> may include one of more applications that are included in the second plurality of applications <NUM>. In some embodiments, the first talkgroup 110A and the second talkgroup 110B may be associated with the same incident. In such embodiments, the first talkgroup 110A may be associated with a first role while the second talkgroup 110B is associated with a second role different from the first. For example, when the incident is a fire incident, the first role of the first talkgroup 110A may be a firefighter role while the second role of the second talkgroup 110B is a medical responder role.

In some embodiments, the arrangement (the positions of each of the applications on the display <NUM>) of the first plurality of applications <NUM>, the arrangement of the second plurality of applications <NUM>, or both is based on a priority associated with each of the applications. For example, applications of higher priority are positioned at the top of the screen of the display <NUM>. In some embodiments, the priority is automatically set by the electronic processor <NUM>. For example, an application may be set to a high priority when a change or new information has become available in the application (for example, when a new message is received or when new media has been uploaded).

Moreover in this document, relational terms such as first and second, top and bottom, and the like may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. The terms "comprises," "comprising," "has", "having," "includes", "including," "contains", "containing" or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises, has, includes, contains a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. An element proceeded by "comprises. a", "includes. a", "contains. a" does not, without more constraints, preclude the existence of additional identical elements in the process, method, article, or apparatus that comprises, has, includes, contains the element. The terms "a" and "an" are defined as one or more unless explicitly stated otherwise herein. The terms "substantially", "essentially", "approximately", "about" or any other version thereof, are defined as being close to as understood by one of ordinary skill in the art, and in one non-limiting embodiment the term is defined to be within <NUM>%, in another embodiment within <NUM>%, in another embodiment within <NUM>% and in another embodiment within <NUM>%. The term "coupled" as used herein is defined as connected, although not necessarily directly and not necessarily mechanically. A device or structure that is "configured" in a certain way is configured in at least that way, but may also be configured in ways that are not listed.

Claim 1:
A communication device (<NUM>) assigned to a first talkgroup of a trunked radio system and a second talkgroup of the trunked radio system, the communication device including:
a user input interface;
a display (<NUM>);
an electronic processor (<NUM>) communicatively coupled to the display and configured to:
generate, on the display, a graphical user interface;
generate, on the display, a first screen (<NUM>) associated with the first talkgroup, the first screen including a first plurality of applications related to the first talkgroup that the communication device is assigned to, the first plurality of applications including applications related to an incident associated with the first talkgroup;
receive, via the user input interface, a user input requesting to change talkgroups; and
generate on the display, in response to the user input, a second screen (<NUM>) including a second plurality of applications related to the second talkgroup that the communication device is assigned to, the second plurality of applications including applications related to an incident associated with the second talkgroup.