EP3884652A1 - Multiple talkgroup navigation management - Google Patents
Multiple talkgroup navigation managementInfo
- Publication number
- EP3884652A1 EP3884652A1 EP19828499.4A EP19828499A EP3884652A1 EP 3884652 A1 EP3884652 A1 EP 3884652A1 EP 19828499 A EP19828499 A EP 19828499A EP 3884652 A1 EP3884652 A1 EP 3884652A1
- Authority
- EP
- European Patent Office
- Prior art keywords
- talkgroup
- applications
- communication device
- user input
- display
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
- H04L65/40—Support for services or applications
- H04L65/4061—Push-to services, e.g. push-to-talk or push-to-video
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/01—Input arrangements or combined input and output arrangements for interaction between user and computer
- G06F3/048—Interaction techniques based on graphical user interfaces [GUI]
- G06F3/0481—Interaction techniques based on graphical user interfaces [GUI] based on specific properties of the displayed interaction object or a metaphor-based environment, e.g. interaction with desktop elements like windows or icons, or assisted by a cursor's changing behaviour or appearance
- G06F3/0483—Interaction with page-structured environments, e.g. book metaphor
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/01—Input arrangements or combined input and output arrangements for interaction between user and computer
- G06F3/048—Interaction techniques based on graphical user interfaces [GUI]
- G06F3/0487—Interaction techniques based on graphical user interfaces [GUI] using specific features provided by the input device, e.g. functions controlled by the rotation of a mouse with dual sensing arrangements, or of the nature of the input device, e.g. tap gestures based on pressure sensed by a digitiser
- G06F3/0488—Interaction techniques based on graphical user interfaces [GUI] using specific features provided by the input device, e.g. functions controlled by the rotation of a mouse with dual sensing arrangements, or of the nature of the input device, e.g. tap gestures based on pressure sensed by a digitiser using a touch-screen or digitiser, e.g. input of commands through traced gestures
- G06F3/04883—Interaction techniques based on graphical user interfaces [GUI] using specific features provided by the input device, e.g. functions controlled by the rotation of a mouse with dual sensing arrangements, or of the nature of the input device, e.g. tap gestures based on pressure sensed by a digitiser using a touch-screen or digitiser, e.g. input of commands through traced gestures for inputting data by handwriting, e.g. gesture or text
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
- H04L65/10—Architectures or entities
- H04L65/1059—End-user terminal functionalities specially adapted for real-time communication
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
- H04L65/1066—Session management
- H04L65/1083—In-session procedures
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
- H04L65/1066—Session management
- H04L65/1083—In-session procedures
- H04L65/1093—In-session procedures by adding participants; by removing participants
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M1/00—Substation equipment, e.g. for use by subscribers
- H04M1/72—Mobile telephones; Cordless telephones, i.e. devices for establishing wireless links to base stations without route selection
- H04M1/724—User interfaces specially adapted for cordless or mobile telephones
- H04M1/72403—User interfaces specially adapted for cordless or mobile telephones with means for local support of applications that increase the functionality
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M1/00—Substation equipment, e.g. for use by subscribers
- H04M1/72—Mobile telephones; Cordless telephones, i.e. devices for establishing wireless links to base stations without route selection
- H04M1/724—User interfaces specially adapted for cordless or mobile telephones
- H04M1/72403—User interfaces specially adapted for cordless or mobile telephones with means for local support of applications that increase the functionality
- H04M1/7243—User interfaces specially adapted for cordless or mobile telephones with means for local support of applications that increase the functionality with interactive means for internal management of messages
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M1/00—Substation equipment, e.g. for use by subscribers
- H04M1/72—Mobile telephones; Cordless telephones, i.e. devices for establishing wireless links to base stations without route selection
- H04M1/724—User interfaces specially adapted for cordless or mobile telephones
- H04M1/72469—User interfaces specially adapted for cordless or mobile telephones for operating the device by selecting functions from two or more displayed items, e.g. menus or icons
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/06—Selective distribution of broadcast services, e.g. multimedia broadcast multicast service [MBMS]; Services to user groups; One-way selective calling services
- H04W4/08—User group management
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/06—Selective distribution of broadcast services, e.g. multimedia broadcast multicast service [MBMS]; Services to user groups; One-way selective calling services
- H04W4/10—Push-to-Talk [PTT] or Push-On-Call services
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/40—Connection management for selective distribution or broadcast
- H04W76/45—Connection management for selective distribution or broadcast for Push-to-Talk [PTT] or Push-to-Talk over cellular [PoC] services
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M2250/00—Details of telephonic subscriber devices
- H04M2250/22—Details of telephonic subscriber devices including a touch pad, a touch sensor or a touch detector
Definitions
- Public safety personnel that provide services in emergency situations often use communication devices.
- communication devices for example, two-way radios or converged devices (for example, a combination of a smart telephone and a two-way radio).
- public safety personnel may need to quickly access and use functionality provided by one or more software applications.
- FIG. 1 is a block diagram of a communication system in accordance with some embodiments.
- FIG. 2 is a block diagram of an electronic communication device included in the communication system of FIG. 1 in accordance with some embodiments.
- FIG. 3A is flowchart illustrating a method of navigating between talkgroups implemented by the electronic communication device of FIG. 2 in accordance with some embodiments.
- FIG. 3B is flowchart illustrating a method of navigating between talkgroups implemented by the electronic communication device of FIG. 2 in accordance with some embodiments.
- FIG. 4A is a graphical display of the communication device of FIG. 2 performing the method of FIG. 3 in accordance to some embodiments.
- FIG. 4B is a graphical display of the communication device of FIG. 2 performing the method of FIG. 3 in accordance with some embodiments.
- FIG. 4C is a graphical display of the communication device of FIG. 2 performing the method of FIG. 3 in accordance to some embodiments.
- a talkgroup is a defined group of communication devices that share communications with each other via one or more communication modalities.
- each talkgroup may utilize particular types of applications, for example, based on a role of participants of the talkgroup.
- one talkgroup is established for a group for firefighting personnel, while another talkgroup is used by medical response personnel.
- 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 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, associate the communication device with a first talkgroup, present, on the display, a first application related to the first talkgroup, receive, via the user input interface, a user input indicative of a request to change talkgroups, associate, in response to the user input, the communication device with a second talkgroup, and present, on the display, a second application related to 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.
- 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, associating the communication device with a first talkgroup, presenting, on the display, a first application related to the first talkgroup, receiving, via a user input interface, a user input indicative of a request to change talkgroups, associating, in response to the user input, the communication device with a second talkgroup, and presenting, on the display, a second application related to the second talkgroup.
- FIG. 1 is a diagram of a communication system 100 according to one example.
- the communication system 100 includes electronic
- the electronic communication devices 102, 104, and 106 may be configured similarly. It is not necessary, however, that the electronic communication devices 102, 104, and 106 be identical.
- the electronic communication devices of the communication system 100 are merely examples. In some embodiments, the communication system 100 may include more or fewer communication devices than illustrated in FIG. 1.
- the electronic communication devices 102, 104, and 106 communicate with each other over a communication network 108.
- the network 108 may be a wireless communication network. All or parts of the network 108 may be implemented using various existing networks, for example, a cellular network, the Internet, a land mobile radio (LMR) network, a BluetoothTM 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 108 may also include future developed networks. In some embodiments, the network 108 may also include a combination of the networks mentioned.
- Each of the electronic communication devices 102, 104, and 106 is associated with one or more talkgroups.
- devices 102 and 104 are associated with a first talkgroup 110A and devices 102 and 106 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.
- a talkgroup may relate to an organization of first responders, a group of police officers, a fire incident, or a combination thereof.
- a talkgroup may relate to members having the same role or designation (for example, police officer, detective, supervisor, paramedic, firefighter, and the like).
- 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 112.
- the communications controller 112 may be a server that is centrally maintained, for example, at a call center or public safety command center.
- the communications controller 112 may control communication between the devices 102, 104, and 106 over the network 108 in accordance with talkgroup affiliation.
- the system 100 includes more than one communications controller.
- one or more of the communication devices of the system 100 may be configured to manage and monitor one or more talkgroups and communications thereof.
- the electronic communication device 102 (described in more detail below in regard to FIG.
- the communication device 102 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 108.
- the communication device 102 is configured to communicate via one or more communication modalities, for example text messaging and push-to- talk (PTT) communications.
- PTT push-to- talk
- the electronic communication device 102 may be distributed over more than one device.
- the communication device 102 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).
- the electronic communication device 102 is a mobile communication device mounted in or on a vehicle (for example, a police vehicle).
- the electronic communication device 102 may be a device maintained, for example, at a call center or public safety command center.
- FIG. 2 is a block diagram of a communication device 102.
- the communication device 102 includes an electronic processor 205, a memory 210, and an input/output interface 215.
- 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 electronic processor 205 obtains and provides information (for example, from the memory 210 and/or the input/output interface 215), 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 210 or a read only memory (“ROM”) of the memory 210 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 205 is configured to retrieve from the memory 210 and execute, among other things, software related to the control processes and methods described herein.
- the memory 210 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 210 may take the form of any non- transitory computer-readable medium.
- the memory 210 stores, among other things, one or more applications 211. 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 205. 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 220).
- the input/output interface 215 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 215 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 102.
- the input/output interface 215 includes an audio sensor 216, an audio speaker 217, and a display 218.
- the display 218 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 217.
- LCD liquid crystal display
- OLED organic light-emitting diode
- the audio speaker 217 is a transducer that produces sound from electrical signals (for example, generated from an audio stream) received from the electronic processor 205.
- 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 216.
- the audio sensor 216 is configured to capture audio.
- the audio sensor 216 may be, for example, a microphone.
- input is also provided by a rotary knob 219.
- the rotary knob 219 is a mechanical knob interface.
- the rotary knob 219 is rotatable through a plurality of positions, wherein each of the plurality of positions is associated with a particular transmission channel.
- user input received through the rotary knob 219 includes selection of one of the plurality of positions (e.g., through clockwise rotation or counter-clockwise rotation of the rotary knob 219).
- the rotary knob 219 provides input for a primary function independent of a software application of the device 102. For example, when the display 218 is displaying an application screen generated by the processor 205 and the rotary knob 219 receives user input (i.e., is rotated), the operation of the rotary knob 219 does not modify the operation or output of the application.
- the rotary knob 219 may be, for example, (when the device 102 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 217. As explained in more detail below, the rotary knob 219 may be utilized by a user of the device 102 to navigate between talkgroups and pluralities of applications associated with each talkgroup. In some embodiments, the rotary knob 219 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 215 includes a graphical user interface (GUI) (for example, generated by the electronic processor 205, from instructions and data stored in the memory 210, and presented on the display 218) that enables a user to interact with the communication device 102 (for example, to execute one or more of the applications 211).
- GUI graphical user interface
- the transceiver 220 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 Special Mobile (GSM)) networks, Code Division Multiple Access (CDMA) networks, Evolution- Data Optimized (EV-DO) networks, Enhanced Data Rates for GSM Evolution (EDGE) networks, 3G networks, 4G networks, combinations or derivatives thereof, and other suitable networks, including future-developed networks.
- wireless networks for example, land mobile radio (LMR) networks, Long Term Evolution (LTE) networks, Global System for Mobile Communications (or Groupe Special Mobile (GSM)) networks, Code Division Multiple Access (CDMA) networks, Evolution- Data Optimized (EV-DO) networks, Enhanced Data Rates for GSM Evolution (EDGE) networks, 3G networks, 4G networks, combinations or derivatives thereof, and other suitable networks, including future-developed networks.
- wireless networks for example, land mobile radio (LMR) networks, Long Term Evolution (LTE) networks, Global
- the electronic processor 205 is configured to operate the transceiver 220 to receive input from and to provide system output, or a combination of both.
- the transceiver 220 obtains information and signals from, and provides information and signals to,
- the electronic processor 205 obtains and provides information (for example, from the memory 210 and/or the transceiver 220), 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 210 or a read only memory (“ROM”) of the memory 210 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 205 is configured to retrieve from the memory 210 and execute, among other things, software related to the control processes and methods described herein.
- FIG. 3A is a flowchart illustrating an example method 300A of navigating between multiple talkgroups on a communication device.
- the method 300A is described as being performed by the electronic communication device 102 and, in particular, the electronic processor 205. 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 112.
- the electronic processor 205 generates, on the display 218, a graphical user interface and, at block 304A, associates (or assigns) the communication device 102 with a first talkgroup (for example, talkgroup 110A).
- a first talkgroup for example, talkgroup 110A
- the electronic processor 205 presents, on the display 218, 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 110 A.
- the electronic processor 205 receives, via a user input interface (an input device or interface of the input/output interface 215), a user input indicative of a request to change talkgroups.
- the user input may be, for example, a gesture on the display 218 (in embodiments where the display 218 is a touchscreen) or an actuation of a particular mechanical input of the device 102 (for example, a rotation of the rotary knob 219).
- the rotary knob 219 provides input for a primary function independent of software
- the rotary knob 219 provides input for a secondary function (as described above, switching between talkgroups).
- a user input via the rotary knob 219 is indicative of a request to change talkgroups when an additional input is received (for example, while a user of the device 102 is touching the display 218).
- the electronic processor 205 in response to the user input, associates (or assigns) the communication device 102 with a second talkgroup (for example, the talkgroup 110B) at block 310A and presents, on the display 218, 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.
- the second application is the same as the first application.
- 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.
- each talkgroup may be associated with an incident. In such
- the first and second application may each be based on the incident associated with the first and second talkgroup respectively.
- 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.
- 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. 3B is a flowchart illustrating an example method 300B of operating a communication device associated with multiple talkgroups.
- the method 300B is described as being performed by the electronic communication device 102 and, in particular, the electronic processor 205. 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 112.
- 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.
- the electronic processor 205 generates, on the display 218, a graphical user interface.
- the electronic processor 205 generates, on the display 218, a first screen including a first plurality of applications related to a first talkgroup that the communication device 102 is associated with (for example, the talkgroup 110A).
- the first plurality of applications include applications related to an incident associated with the first talkgroup 110 A.
- FIG. 4A illustrates the electronic communication device 102.
- a first screen 402 is shown on the display 218.
- the first screen 402 includes a plurality of applications 404 related to the talkgroup 110A.
- the plurality of applications 404 include applications related to an incident associated with the first talkgroup 110A.
- 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 102, and information regarding the incident associated with the first talkgroup 110A.
- the first screen 402 includes applications related to the robbery (an incident identifier 406 A, a map of the robbery location 406B, and captured media or video of the robbery 406C).
- 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 102), external databases and resources (for example, webpages and files online) for information based on one or more entered terms.
- 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 404, or both.
- the suggested search terms may be generated based on previously searched terms performed.
- the electronic processor 205 receives, via a user input interface (an input device or interface of the input/output interface 215), a user input indicative of a request to change talkgroups.
- a user input interface an input device or interface of the input/output interface 215.
- the user input may be a gesture (for example, a swipe 408A) on the display 218.
- the user input may be an actuation (a rotation 408B) of the rotary knob 219.
- the electronic processor 205 generates on the display 218, in response to the user input, a second screen including a second plurality of applications related to a second talkgroup that the communication device 102 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. 4C illustrates the electronic communication device 102.
- a second screen 410 is shown on the display 218.
- the second screen 410 includes a plurality of applications 412 related to the talkgroup 110B.
- the plurality of applications 412 include applications related to an incident associated with the second talkgroup 110B.
- the talkgroup 110B is associated with a robbery investigation.
- the second screen 410 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 412 may include one or more applications similar to those described above in regard to the first plurality of applications 404.
- the first plurality of applications 404 may include one of more applications that are included in the second plurality of applications 412.
- the first talkgroup 110A and the second talkgroup 110B may be associated with the same incident.
- 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.
- 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.
- the arrangement (the positions of each of the applications on the display 218) of the first plurality of applications 404, the arrangement of the second plurality of applications 412, 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 218.
- the priority is automatically set by the electronic processor 205. 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).
- 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 10%, in another embodiment within 5%, in another embodiment within 1% and in another embodiment within 0.5%.
- 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.
- processors such as microprocessors, digital signal processors, customized processors and field programmable gate arrays (FPGAs) and unique stored program instructions (including both software and firmware) that control the one or more processors to implement, in conjunction with certain non-processor circuits, some, most, or all of the functions of the method and/or apparatus described herein.
- processors such as microprocessors, digital signal processors, customized processors and field programmable gate arrays (FPGAs) and unique stored program instructions (including both software and firmware) that control the one or more processors to implement, in conjunction with certain non-processor circuits, some, most, or all of the functions of the method and/or apparatus described herein.
- FPGAs field programmable gate arrays
- unique stored program instructions including both software and firmware
- an embodiment can be implemented as a computer-readable storage medium having computer readable code stored thereon for programming a computer (e.g., comprising a processor) to perform a method as described and claimed herein.
- Examples of such computer-readable storage mediums include, but are not limited to, a hard disk, a CD-ROM, an optical storage device, a magnetic storage device, a ROM (Read Only Memory), a PROM (Programmable Read Only Memory), an EPROM (Erasable Programmable Read Only Memory), an EEPROM (Electrically Erasable Programmable Read Only Memory) and a Flash memory.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Multimedia (AREA)
- Human Computer Interaction (AREA)
- General Business, Economics & Management (AREA)
- Business, Economics & Management (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Telephone Function (AREA)
- Telephonic Communication Services (AREA)
Abstract
Description
Claims
Applications Claiming Priority (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| US16/232,274 US10951753B2 (en) | 2018-12-26 | 2018-12-26 | Multiple talkgroup navigation management |
| PCT/US2019/065272 WO2020139545A1 (en) | 2018-12-26 | 2019-12-09 | Multiple talkgroup navigation management |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| EP3884652A1 true EP3884652A1 (en) | 2021-09-29 |
| EP3884652B1 EP3884652B1 (en) | 2025-05-07 |
Family
ID=69024725
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| EP19828499.4A Active EP3884652B1 (en) | 2018-12-26 | 2019-12-09 | Multiple talkgroup navigation management |
Country Status (5)
| Country | Link |
|---|---|
| US (1) | US10951753B2 (en) |
| EP (1) | EP3884652B1 (en) |
| AU (1) | AU2019417173B2 (en) |
| CA (1) | CA3122398C (en) |
| WO (1) | WO2020139545A1 (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US12056332B2 (en) * | 2020-12-23 | 2024-08-06 | Snap Inc. | Chat interface with dynamically populated menu element |
| US12200027B2 (en) * | 2022-11-29 | 2025-01-14 | Prodcom LLC | Selective channel live production system and method |
Family Cites Families (24)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6583797B1 (en) | 1997-01-21 | 2003-06-24 | International Business Machines Corporation | Menu management mechanism that displays menu items based on multiple heuristic factors |
| US8225407B1 (en) | 2003-08-21 | 2012-07-17 | Symantec Corporation | Incident prioritization and adaptive response recommendations |
| US20060276200A1 (en) * | 2005-05-17 | 2006-12-07 | Sridhar Radhakrishnan | Mobile and wireless network architecture for law enforcement |
| US8314683B2 (en) * | 2008-05-09 | 2012-11-20 | The Israelife Foundation | Incident response system |
| US8359643B2 (en) * | 2008-09-18 | 2013-01-22 | Apple Inc. | Group formation using anonymous broadcast information |
| US8972878B2 (en) | 2009-09-21 | 2015-03-03 | Avaya Inc. | Screen icon manipulation by context and frequency of Use |
| US20120144305A1 (en) | 2010-12-07 | 2012-06-07 | Motorola, Inc. | Method and apparatus for simultaneously presenting at least two multimedia content on a processing device |
| WO2014085605A2 (en) * | 2012-11-28 | 2014-06-05 | Intrepid Networks, Llc | Integrated systems and methods providing situational awareness of operations in an organization |
| US20140257897A1 (en) * | 2013-03-05 | 2014-09-11 | Page-Out, LLC | Responder personnel on-call availability system |
| US20140278046A1 (en) * | 2013-03-12 | 2014-09-18 | Mobius Exchange, Inc. | Fire Hydrant Locator for EMT Personnel |
| US10949080B2 (en) * | 2013-03-12 | 2021-03-16 | Gerald Douglas Hosier, JR. | Online systems and methods for advancing information organization sharing and collective action |
| US9740825B2 (en) | 2013-12-31 | 2017-08-22 | Cerner Innovation, Inc. | Dynamic presentation of actionable content items |
| US9336675B2 (en) | 2014-04-28 | 2016-05-10 | Motorola Solutions, Inc. | Methods and systems for presenting prioritized incident content |
| US9578470B2 (en) * | 2015-02-05 | 2017-02-21 | Iridium Satellite Llc | Priority talkgroups |
| US9787940B2 (en) * | 2015-10-05 | 2017-10-10 | Mutualink, Inc. | Video management defined embedded voice communication groups |
| US9584987B1 (en) * | 2015-11-24 | 2017-02-28 | Motorola Solutions, Inc. | Methods and systems for selecting a talkgroup associated with a mission for a portable communications device |
| US10021540B2 (en) | 2016-05-19 | 2018-07-10 | Mutualink, Inc. | Voice connectivity of push-to-talk clients |
| US10142454B2 (en) | 2017-02-24 | 2018-11-27 | Motorola Solutions, Inc. | Method for providing a customized user interface for group communication at a communication device |
| US20180357073A1 (en) | 2017-06-13 | 2018-12-13 | Motorola Solutions, Inc | Method, device, and system for electronic digital assistant for natural language detection of a user status change and corresponding modification of a user interface |
| US10824615B2 (en) | 2017-07-05 | 2020-11-03 | Motorola Solutions, Inc. | Methods and systems for updating information in a timeline of a public safety incident |
| US10129711B1 (en) | 2017-09-18 | 2018-11-13 | Motorola Solutions, Inc. | Push to talk for the internet of things |
| US20190121497A1 (en) * | 2017-10-19 | 2019-04-25 | Motorola Solutions, Inc | Contact list for the internet of things |
| US20190149959A1 (en) * | 2017-11-16 | 2019-05-16 | Motorola Solutions, Inc | Method for controlling a virtual talk group memeber to perform an assignment |
| US10499202B1 (en) * | 2018-10-29 | 2019-12-03 | Motorola Solutions, Inc. | Contact list for the internet of things |
-
2018
- 2018-12-26 US US16/232,274 patent/US10951753B2/en active Active
-
2019
- 2019-12-09 EP EP19828499.4A patent/EP3884652B1/en active Active
- 2019-12-09 AU AU2019417173A patent/AU2019417173B2/en active Active
- 2019-12-09 CA CA3122398A patent/CA3122398C/en active Active
- 2019-12-09 WO PCT/US2019/065272 patent/WO2020139545A1/en not_active Ceased
Also Published As
| Publication number | Publication date |
|---|---|
| US10951753B2 (en) | 2021-03-16 |
| EP3884652B1 (en) | 2025-05-07 |
| US20200213442A1 (en) | 2020-07-02 |
| CA3122398C (en) | 2022-06-14 |
| AU2019417173A1 (en) | 2021-07-08 |
| AU2019417173B2 (en) | 2021-08-12 |
| CA3122398A1 (en) | 2020-07-02 |
| WO2020139545A1 (en) | 2020-07-02 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CA3053902C (en) | Method for providing a customized user interface for group communication at a communication device | |
| EP3029889B1 (en) | Method for instant messaging and device thereof | |
| US9456327B2 (en) | Location-based emergency application providing efficient response | |
| CN105577532B (en) | Application message processing method and device based on keywords and mobile terminal | |
| US20220014938A1 (en) | Method and device for using network slice | |
| KR101871833B1 (en) | Method and apparatus for providing Push-To-Talk Service | |
| CA3122398C (en) | Multiple talkgroup navigation management | |
| EP3695296B1 (en) | Device, system and method for correcting operational device errors | |
| US10812540B2 (en) | Forwarding a communication transmitted to a portable communications device based on talkgroup affiliation and override settings | |
| US10447842B1 (en) | Push-to-talk to messaging application graphical interface | |
| US11582175B2 (en) | System, device and method for secure message thread communication | |
| KR101810464B1 (en) | Mobile terminal and service capability discovery method thereof | |
| US11330403B2 (en) | System and method for crowd-oriented application synchronization | |
| WO2019143465A1 (en) | Device and method for locking in button context based on a source contact of an electronic communication | |
| US10637988B2 (en) | System, device and method for generating common actuatable options that initiate a plurality of actions | |
| CN118202645A (en) | A method and device for transmitting AI model |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: UNKNOWN |
|
| STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: THE INTERNATIONAL PUBLICATION HAS BEEN MADE |
|
| PUAI | Public reference made under article 153(3) epc to a published international application that has entered the european phase |
Free format text: ORIGINAL CODE: 0009012 |
|
| STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: REQUEST FOR EXAMINATION WAS MADE |
|
| 17P | Request for examination filed |
Effective date: 20210625 |
|
| AK | Designated contracting states |
Kind code of ref document: A1 Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR |
|
| DAV | Request for validation of the european patent (deleted) | ||
| DAX | Request for extension of the european patent (deleted) | ||
| STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: EXAMINATION IS IN PROGRESS |
|
| 17Q | First examination report despatched |
Effective date: 20230413 |
|
| GRAP | Despatch of communication of intention to grant a patent |
Free format text: ORIGINAL CODE: EPIDOSNIGR1 |
|
| STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: GRANT OF PATENT IS INTENDED |
|
| RIC1 | Information provided on ipc code assigned before grant |
Ipc: G06F 3/0488 20130101ALI20241218BHEP Ipc: G06F 3/0483 20130101ALI20241218BHEP Ipc: H04W 4/10 20090101ALI20241218BHEP Ipc: H04W 4/08 20090101ALI20241218BHEP Ipc: H04M 1/725 20210101AFI20241218BHEP |
|
| INTG | Intention to grant announced |
Effective date: 20250120 |
|
| GRAS | Grant fee paid |
Free format text: ORIGINAL CODE: EPIDOSNIGR3 |
|
| GRAA | (expected) grant |
Free format text: ORIGINAL CODE: 0009210 |
|
| STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: THE PATENT HAS BEEN GRANTED |
|
| AK | Designated contracting states |
Kind code of ref document: B1 Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR |
|
| P01 | Opt-out of the competence of the unified patent court (upc) registered |
Free format text: CASE NUMBER: APP_16055/2025 Effective date: 20250402 |
|
| REG | Reference to a national code |
Ref country code: GB Ref legal event code: FG4D |
|
| REG | Reference to a national code |
Ref country code: CH Ref legal event code: EP |
|
| REG | Reference to a national code |
Ref country code: DE Ref legal event code: R096 Ref document number: 602019069730 Country of ref document: DE |
|
| REG | Reference to a national code |
Ref country code: IE Ref legal event code: FG4D |
|
| REG | Reference to a national code |
Ref country code: NL Ref legal event code: MP Effective date: 20250507 |
|
| PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: FI Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20250507 Ref country code: ES Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20250507 Ref country code: PT Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20250908 |
|
| REG | Reference to a national code |
Ref country code: LT Ref legal event code: MG9D |
|
| PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: NO Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20250807 Ref country code: GR Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20250808 |
|
| PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: PL Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20250507 Ref country code: NL Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20250507 |
|
| REG | Reference to a national code |
Ref country code: AT Ref legal event code: MK05 Ref document number: 1793767 Country of ref document: AT Kind code of ref document: T Effective date: 20250507 |
|
| PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: BG Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20250507 |
|
| PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: HR Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20250507 |
|
| PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: AT Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20250507 |
|
| PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: RS Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20250807 |
|
| PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: IS Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20250907 |
|
| PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: LV Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20250507 |
|
| PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: DE Payment date: 20251126 Year of fee payment: 7 |
|
| PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: GB Payment date: 20251120 Year of fee payment: 7 |
|
| PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: DK Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20250507 Ref country code: SM Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20250507 |
|
| PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: CZ Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20250507 |
|
| PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: EE Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20250507 |
|
| PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: RO Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20250507 Ref country code: SK Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20250507 |
|
| PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: IT Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20250507 |
|
| REG | Reference to a national code |
Ref country code: DE Ref legal event code: R097 Ref document number: 602019069730 Country of ref document: DE |
|
| PLBE | No opposition filed within time limit |
Free format text: ORIGINAL CODE: 0009261 |
|
| STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: NO OPPOSITION FILED WITHIN TIME LIMIT |
|
| REG | Reference to a national code |
Ref country code: CH Ref legal event code: L10 Free format text: ST27 STATUS EVENT CODE: U-0-0-L10-L00 (AS PROVIDED BY THE NATIONAL OFFICE) Effective date: 20260318 |
|
| 26N | No opposition filed |
Effective date: 20260210 |