US20210127234A1

US20210127234A1 - Failure management in push to talk for the internet of things

Info

Publication number: US20210127234A1
Application number: US16/665,873
Authority: US
Inventors: Jin Hoe Phua; Chin Chuan YAP; Nur Amalina ROSLY; Kishokanna PARAMASIVAM
Original assignee: Motorola Solutions Inc
Current assignee: Motorola Solutions Inc
Priority date: 2019-10-28
Filing date: 2019-10-28
Publication date: 2021-04-29
Anticipated expiration: 2039-10-28
Also published as: US10999714B1

Abstract

A device, system and method for failure management in push to talk for the internet of things is provided. A Push-To-Talk (PTT) server receives, from a device, a control command for an Internet-of-Things (IoT) device, the IoT device and the device mapped to a talkgroup identifier identifying a talkgroup used by the device to send the control command; outputting, via the PTT server, to the IoT device, the control command. The PTT server determines that the control command has failed. The PTT server transmits, to the device, an indication that the control command has failed, the indication transmitted over the talkgroup identified by the talkgroup identifier.

Description

BACKGROUND

The Internet of Things (IoT) refers to the connection of every-day devices to the Internet. Devices such as cars, kitchen appliances, medical devices, doors, windows, HVAC systems, drones, . . . , etc. can all be connected through the IoT. Basically, anything that can be powered can be connected to the internet to control its functionality. The IoT allows objects to be sensed or controlled remotely across existing network infrastructure, creating opportunities for more direct integration of the physical world into computer-based systems, and resulting in improved efficiency, accuracy, and control.
Push-to-talk (PTT) devices are commonly employed by public safety personnel, air traffic controllers, emergency workers, construction site workers and others who need to be in constant and readily available voice communication. PTT, also known as press-to-transmit, is a method of communicating using half-duplex communication lines. A PTT button may be pressed to switch a device from a voice reception mode to a transmit-mode. For example, one operator may depress the PTT button on her device and speak into the device's microphone. The speech is converted into an appropriate format and transmitted to one or more other devices, where the operators of those other devices hear the first operator speak through their device's speaker.
In a two-way radio system, each PTT radio typically communicates with one group of radios (talkgroup) at a time. Even though a radio may switch between talkgroups, the radio may still only be able to communicate with a single talkgroup at a time. For example, a firefighter may be affiliated with or using a firefighter talkgroup and a police officer may be affiliated with or using a police talkgroup. Talkgroups outside of those currently listened to by a radio will not be heard by other radios or consoles. Thus, a radio speaker will only output audio from a talkgroup associated with the radio, and the radio's transmission will only be heard by those communicating on a same talkgroup.
Instead of assigning, for example, a radio channel to one particular organization (group) at a time, users are instead assigned to a logical grouping, a “talkgroup”. When any user in that group wishes to converse with another user in the talkgroup, a vacant radio channel is found automatically by the system and the conversation takes place on that channel. Many unrelated conversations can occur on a channel, making use of the otherwise idle time between conversations. A control channel coordinates all the activity of the radios in the system. The control channel sends packets of data to enable one talkgroup to talk together, regardless of frequency.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

The accompanying figures, where like reference numerals refer to identical or functionally similar elements throughout the separate views, together with the detailed description below, are incorporated in and form part of the specification, and serve to further illustrate embodiments of concepts that include the claimed invention, and explain various principles and advantages of those embodiments.

FIG. 1 illustrates a push-to-talk (PTT) radio.

FIG. 2 illustrates a push-to-talk (PTT) radio.

FIG. 3 illustrates a PTT to IoT server.

FIG. 4 depicts an example communication system that incorporates a PTT-to-Things server.

FIG. 5 is a block diagram of a PTT to IoT server.

FIG. 6 is a flow chart showing operation of the PTT to IoT server of FIG. 5 when managing a failure.

Skilled artisans will appreciate that elements in the figures are illustrated for simplicity and clarity and have not necessarily been drawn to scale. For example, the dimensions of some of the elements in the figures may be exaggerated relative to other elements to help to improve understanding of embodiments of the present invention.
The apparatus and method components have been represented where appropriate by conventional symbols in the drawings, showing only those specific details that are pertinent to understanding the embodiments of the present invention so as not to obscure the disclosure with details that will be readily apparent to those of ordinary skill in the art having the benefit of the description herein.

DETAILED DESCRIPTION

PTT and talkgroups are ubiquitous in the public-safety realm and, as described herein, may be used to control devices for the IoT, for example, via a PTT server. For example, each IoT device may be assigned to a talkgroup. Some talkgroups may have a single IoT device assigned, and other talkgroups may have multiple IoT devices assigned. During operation, an action command, which may interchangeably be referred to hereafter as a control command, may be received over a first talkgroup and a first command type may be issued to a first IoT device assigned to that talkgroup. A second action command may be received over a second talkgroup and a second command type may be issued to a second IoT device assigned to the second talkgroup.
It should be noted that the “action command” may simply be any transmission received over a particular talkgroup, even a simple keying of a microphone, with no other voice or data transmission (i.e., the received “action command” comprises an un-modulated carrier signal with no data or voice). In other words, sinusoidal signal that is used in the modulation is known as the carrier signal, or simply “the carrier”. The signal that is used in modulating the carrier signal (or sinusoidal signal) is known as the “data signal” or the “message signal”. It is important to notice that a simple sinusoidal carrier contains no information of its own, and may be used to control IoT devices as described.
However, in alternate embodiments, an “action command” may comprise information modulated on the carrier signal, for example, the utterance of specific words, for example, “unlock the door”, “turn on the lights”, . . . , etc. So for example, in a first embodiment, a radio tuned to a “door” talkgroup may unlock the door by simply tuning their radio to the “door talkgroup” and keying their microphone by pushing the PTT button on their radio. In a second embodiment, a radio tuned to a “door” talkgroup may unlock the door by simply tuning their radio to the “door talkgroup” and keying their microphone by pushing the PTT button on their radio, and uttering “unlock” into their radio.
As an example, consider a public-safety officer that is approaching a room with a locked door. The public-safety officer can initiate a PTT call to the talkgroup that include all actuators for the door and the door of the room can be opened. If a light for the room is in the same talkgroup, then the light can be switched on with the same PTT call.
However, when an action command fails to control an IoT device, for example to a network failure and/or a failure at an IoT device, presently a public-safety officer that initiated the command via a PTT radio and the like, is not informed of the failure.
Hence, an aspect of the present specification provides an apparatus comprising: a network interface; and logic circuitry coupled to the network interface, the logic circuitry configured to: receive, via the network interface, from a device, a control command for an Internet-of-Things (IoT) device, the IoT device and the device mapped to a talkgroup identifier identifying a talkgroup used by the device to send the control command; output, via the network interface, to the IoT device, the control command; determine that the control command has failed; and transmit, via the network interface, to the device, an indication that the control command has failed, the indication transmitted over the talkgroup identified by the talkgroup identifier. For example, the apparatus may be located at a PTT to Things server, described herein.
Another aspect of the present specification provides a method comprising: receiving, at a Push-To-Talk (PTT) server, from a device, a control command for an Internet-of-Things (IoT) device, the IoT device and the device mapped to a talkgroup identifier identifying a talkgroup used by the device to send the control command; outputting, via the PTT server, to the IoT device, the control command; determining, at the PTT server, that the control command has failed; and transmitting, via the PTT server, to the device, an indication that the control command has failed, the indication transmitted over the talkgroup identified by the talkgroup identifier.
FIG. 1 illustrates a push-to-talk (PTT) radio and/or device 100. As shown, device 100 comprises PTT button 101, knob 103, display screen 107, and speaker/microphone combination 108. PTT button 101 comprises a standard button, that when pressed, transitions device 100 from a listening state, to a transmit state, transmitting over a specific talkgroup. Display 107 comprises a way of conveying (e.g., displaying) PTT information to the user. In particular, in an embodiment, a talkgroup may be displayed to the user as an alpha-numeric output on display 107. Display 107 may simply comprise a liquid-crystal display (LCD), or may comprise additional types of displays (e.g., a light-emitting diode (LED) display). Display 107 may also comprise a touch-screen display that provides both an output interface and an input interface between the device and a user. Display 107 may also provide graphics, video, and any combination thereof.
Speaker/microphone combination 108 comprises a standard speaker for outputting audio and a standard microphone for receiving audio (voice). More particularly, speaker, of the speaker/microphone combination 108, converts an electrical signal generated from an active application to human-audible sound waves and microphone, of the speaker/microphone combination 108, converts sound waves to electrical signals for transmission.
Knob 103 serves as a way to control the volume of the speaker, of the speaker/microphone combination 108, and also serves as a means for switching between talkgroups. Knob 103 is approximately a cylindrical object. Knob 103 can alternatively be implemented as a variety of different objects, including conical shapes, spherical shapes, dials, cubical shapes, rods, etc., and may have a variety of different textures on their surfaces, including bumps, lines, or other grips, or projections or members extending from the circumferential surface.
User 201 (shown in FIG. 2) preferably grips or contacts the circumferential surface of knob 103 and rotates it a desired amount to scroll through menu items, for example, talkgroups that may be selected. Once knob 103 is rotated to highlight a particular talkgroup, any activation (pushing) of the PTT button 101 will cause device 100 to communicate over the highlighted talkgroup.
It should be noted that display 102 may display the names of the talkgroups, which include the names of IoT devices that are controlled by pushing the PTT button. For example, as shown in FIG. 2, the Police Talkgroup and the Fire ground talkgroup may be displayed, so when highlighted, communications to other police officers, or firemen take place upon the pushing of the PTT button 101. However, as shown, IoT devices may also be displayed, such as Front Door, Lights, Group of Things, Thing 2, Thing 3, . . . , etc. When an IoT device is highlighted, activation of the PTT button will cause the IoT device (or the group of devices) to function.
In order to accomplish the above, a PTT-to-Things Server is provided that is a member of all IoT talkgroups. Communication to the PTT-to-Things server over a particular talkgroup causes the PTT-to-Things server to map the talkgroup to a particular IoT device (or group of IoT devices), and potentially to a particular protocol to control an IoT device. The PTT-to-Things server then instructs the particular IoT device to perform an action.
As is known in the art, modern two-way radio systems comprise talkgroups, where it is possible for a radio to be a member of any combination of talkgroups. As a member of a talkgroup, a radio may receive transmissions from, as well as transmit to all members of the talkgroup. Transmission and reception of information to radios outside of an assigned talkgroup is generally not performed. Illustratively, a radio assigned to an ambulance may be a member of a Fire & Rescue talkgroup as well as a Law Enforcement talkgroup. Therefore, the radio may communicate with all members of the Fire & Rescue talkgroup as well as the Law Enforcement talkgroup. In the present invention, server 301 is provided that is a member of all talkgroups that are assigned to a “thing” connected to the IoT. This is illustrated in FIG. 3.
As shown in FIG. 3, PTT-to-Things server 301 is shown in communication with device 100. PTT-to-Things server 301 is a member of a plurality of talkgroups. When PTT-to-Things server 301 receives a PTT call over a particular talkgroup, PTT-to-Things server 301 will map the particular talkgroup to an IoT device, and potentially a particular IoT protocol. PTT-to-Things server 301 will then communicate with the IoT device to cause the IoT device to perform a particular action.
As is known in the art, a particular communication protocol (IoT protocol) may be used for each IoT device. For example, various proprietary protocols such as DNP, Various IEC**** protocols (IEC 61850 etc. . . . ), bacnet, EtherCat, CANOpen, Modbus/Modbus TCP, EtherNet/IP, PROFIBUS, PROFINET, DeviceNet, . . . , etc. can be used. Also a more generic protocol such as Coap, Mqtt, and RESTfull may also be used.
As mentioned above, an action command may be received by PTT-to-Things server 301 as part of the PTT call over the particular talkgroup. PTT-to-Things server 301 may analyze the action command (which in a preferred embodiment comprises a voice command) and additionally map the action command to an instruction given to the IoT device.
In a further embodiment, a first instruction may be provided to the IoT device upon detecting transmission upon the particular talkgroup, and a second instruction may be provided to the IoT device upon detecting that no further transmission is being received on the talkgroup. (It should be noted that “transmission” comprises simply opening up the channel (transmitting the carrier signal) by pushing the PTT button, no voice needs to be detected). As an example, a user may switch their radio to a talkgroup associated with lighting in a room. Pushing and holding the PTT button may cause the lights to go on, while un-pressing the PTT button may cause the lights to go off. This entails PTT-to-Things server 301 to send an instruction to the lights to turn on upon detecting any transmissions on a particular talkgroup (even the carrier), and then instructing the lights to go off upon detecting that transmissions on a particular talkgroup has ceased.
FIG. 4 depicts an example communication system 400 that incorporates PTT-to-Things server 301. It should be noted that the communication system depicted in FIG. 4 comprises a typical public-safety communication system modified with a PTT-to-Things server. However one of ordinary skill in the art would recognize that other system may be modified to encompass PTT-to-Things server 301 such as, but not limited to a cellular communication system, a cloud-based communication system, . . . , etc. System 400 includes one or more radio access networks (RANs) 402, a public-safety core network 404, PTT device 100, IoT devices 412, PTT-to-Things server 301, and communication links 418, 424, and 432.
RAN 402 includes typical RAN elements such as base stations, base station controllers (BSCs), routers, switches, and the like, arranged, connected, and programmed to provide wireless service to user equipment (e.g., device 100, and the like) in a manner known to those of skill in the relevant art. RAN 402 may implement a direct-mode, conventional, or trunked land mobile radio (LMR) standard or protocol such as European Telecommunications Standards Institute (ETSI) Digital Mobile Radio (DMR), a Project 25 (P25) standard defined by the Association of Public Safety Communications Officials International (APCO), Terrestrial Trunked Radio (TETRA), or other LMR radio protocols or standards. In other embodiments, RAN 402 may implement a Long Term Evolution (LTE), LTE-Advance, or 5G protocol including multimedia broadcast multicast services (MBMS) or single site point-to-multipoint (SC-PTM) over which an open mobile alliance (OMA) push to talk (PTT) over cellular (OMA-PoC), a voice over IP (VoIP), an LTE Direct or LTE Device to Device, or a PTT over IP (PoIP) application may be implemented. In still further embodiments, RAN 402 may implement a Wi-Fi protocol perhaps in accordance with an IEEE 802.11 standard (e.g., 802.11a, 802.11b, 802.11g) or a WiMAX protocol perhaps operating in accordance with an IEEE 802.16 standard.
Public-safety core network 404 may include one or more packet-switched networks and/or one or more circuit-switched networks, and in general provides one or more public-safety agencies with any necessary computing and communication needs, transmitting any necessary public-safety-related data and communications.
For narrowband LMR wireless systems, core network 404 operates in either a conventional or trunked configuration. In either configuration, a plurality of communication devices is partitioned into separate groups (talkgroups) of communication devices. In a conventional narrowband system, each communication device in a group is selected to a particular radio channel (frequency or frequency & time slot) for communications associated with that communication device's group. Thus, each group is served by one channel, and multiple groups may share the same single frequency (in which case, in some embodiments, group IDs may be present in the group data to distinguish between groups using the same shared frequency).
In contrast, a trunked radio system and its communication devices use a pool of traffic channels for virtually an unlimited number of groups of communication devices (e.g., talkgroups). Thus, all groups are served by all channels. The trunked radio system works to take advantage of the probability that not all groups need a traffic channel for communication at the same time.
Group calls may be made between wireless and/or wireline participants in accordance with either a narrowband or a broadband protocol or standard. Group members for group calls may be statically or dynamically defined. That is, in a first example, a user or administrator may indicate to the switching and/or radio network (perhaps at a call controller, PTT server, zone controller, or mobile management entity (MME), base station controller (BSC), mobile switching center (MSC), site controller, Push-to-Talk controller, or other network device) a list of participants of a group at the time of the call or in advance of the call. The group members (e.g., communication devices) could be provisioned in the network by the user or an agent, and then provided some form of group identity or identifier, for example. Then, at a future time, an originating user in a group may cause some signaling to be transmitted indicating that he or she wishes to establish a communication session (e.g., join a group call having a particular talkgroup ID) with each of the pre-designated participants in the defined group. In another example, communication devices may dynamically affiliate with a group (and also disassociate with the group) perhaps based on user input, and the switching and/or radio network may track group membership and route new group calls according to the current group membership.
Device 100 may be any suitable computing and communication device configured to engage in wireless communication with the RAN 402, and ultimately to PTT-to-Things server 301 over the air interface as is known to those in the relevant art. It should also be noted that any one or more of the communication links 418, 424, 432, and 434 could include one or more wireless-communication links and/or one or more wired-communication links.
Expanding on the above, each user of the system may possess a radio to communicate over many differing talkgroups. Communication on various talkgroups will be routed by RAN 402 and network 404 to PTT-to-Things server 301. When PTT-to-Things server 301 receives a communication over a particular talkgroup from any f100, PTT-to-Things server 301 will map the particular talkgroup to an IoT device 412. Communication to a particular IoT device 412 (or group of devices if multiple IoT devices 412 are associated with the same talkgroup) will take place via communication links 432/434 and intervening network 406.
Network 406 preferably comprises one of many networks used to transmit data, such as but not limited to a network employing one of the following protocols: a Long Term Evolution (LTE) protocol, LTE-Advance protocol, or 5G protocol including multimedia broadcast multicast services (MBMS) or single site point-to-multipoint (SC-PTM) protocol over which an open mobile alliance (OMA) push to talk (PTT) over cellular protocol (OMA-PoC), a voice over IP (VoIP) protocol, an LTE Direct or LTE Device to Device protocol, or a PTT over IP (PoIP) protocol, a Wi-Fi protocol perhaps in accordance with an IEEE 802.11 standard (e.g., 802.11a, 802.11b, 802.11g) or a WiMAX protocol perhaps operating in accordance with an IEEE 802.16 standard.
With the above in mind, PTT-to-Things server 301 may also configured with a natural language processing (NLP) engine (not shown in FIG. 4) configured to determine an “action command” from any over-the-air voice transmissions received by device 100. The NLP engine may also analyze oral queries and/or statements received by any user and provide responses to the oral queries and/or take other actions in response to the oral statements. It should be noted that any over-the-air communication between users (e.g., on the talkgroup) will be monitored by the NLP engine in order to determine the content of the over-the-air voice transmission.
FIG. 5 is a block diagram PTT to IoT server 301. In an embodiment, PTT to IoT server 301 is embodied within a dispatch center, however in alternate embodiments the device may be embodied within the public-safety core network 404, or more computing devices in a cloud compute cluster (not shown), or some other communication device not illustrated in FIG. 4, and/or may be a distributed communication device across two or more entities.
FIG. 5 shows those components (not all necessary) for PTT to IoT server 301 to receive a communication from a radio using a particular talkgroup, map the particular talkgroup to an IoT device(s), and send an appropriate command to the IoT device. For ease of illustration some components have been left out of FIG. 4. For example, a graphical user interface that provides the dispatch operator necessary information about public-safety officers is not shown since that component is not necessary for understanding the following discussion.
As shown, PTT to IoT server 301 may include a wide-area-network (WAN) transceiver 501 (e.g., a transceiver that utilizes a public-safety communication-system protocol), Natural Language Processor (NLP) 502, logic circuitry 503, database 504, and network interface 505. In other implementations, PTT to IoT server 301 may include more, fewer, or different components. Regardless, all components are connected via common data busses as known in the art.
WAN transceiver 501 may comprise well known long-range transceivers that utilize any number of network system protocols. (As one of ordinary skill in the art will recognize, a transceiver comprises both a transmitter and a receiver for transmitting and receiving data). For example, WAN transceiver 501 may be configured to utilize a next-generation cellular communications protocol operated by a cellular service provider, or any public-safety protocol such as an APCO 25 network or the FirstNet broadband network. WAN transceiver 501 receives communications from users over a particular talkgroup. It should be noted that WAN transceiver 501 is shown as part of PTT to IoT server 301, however, WAN transceiver 501 may be located in RAN 402 (e.g., a base station of RAN 402), with a direct link to PTT to IoT server 301.
NLP 502 may be a well known circuitry to analyze, understand, and derive meaning from human language in a smart and useful way. By utilizing NLP, automatic summarization, translation, named entity recognition, relationship extraction, sentiment analysis, speech recognition, and topic segmentation can take place.
Logic circuitry 503 comprises a digital signal processor (DSP), general purpose microprocessor, a programmable logic device, or application specific integrated circuit (ASIC) and is configured to map a talkgroup to an IoT device(s), and alternatively also map a talkgroup and potentially a received utterance to a command given to an IoT device. For example, consider a public-safety officer that is approaching a room with a locked door. The public-safety officer can initiate a PTT call using a particular talkgroup. WAN transceiver may detect the transmission and provide the transmission to logic circuitry 503. Logic circuitry 503 can (via mapping) determine that the talkgroup is associated with the locked door. Logic circuitry 503 then can instruct all actuators for the door to be opened.
The mapping process preferably comprises an operation that associates each element of a given set (the domain) with one or more elements of a second set (the range). The talkgroup and potentially an action command comprises the domain, while the IoT device and command the range. The mapping is preferably explicit based on predefined rules (e.g., a specific talkgroup is assigned to door lock 1).
Database 504 is provided. Database 504 comprises standard memory (such as RAM, ROM, . . . , etc.) and serves to store talkgroup/IoT device pairs, and may additionally store talkgroup/IoT device pairs along with action command/action taken pairs. This is illustrated in Tables 1 and 2 below:

TABLE 1

Mapping of talkgroup to device and instruction
when no verbal action command is used

Talkgroup			Address
device	Device Instruction	(control command)	of IoT

4320	Lock at the	Switch from lock to unlock,	10.66.123
	Police Station	or vice versa
4356	Light at the	Switch light from off to on	10.66.124
	Police Station	or vice versa
6748	Air conditioning at	Turn air conditioning from	10.66.125
	the Police Station	off to on or vice versa
. . .	. . .	. . .	. . .

TABLE 2

Mapping of talkgroup to device and instruction
when action command is used

	Device
Talk	Verbal Action	Instruction	Address of
group	Command	(control command)	IoT device

4320	Lock at the	unlock Switch from	10.66.124
	Police Station	lock to unlock
4320	Lock at the	lock Switch from	10.66.124
	Police Station	unlock to lock
4356	Light at the Police	off Turn light off	10.66.125
	Station
4356	Light at the Police	on Turn light on	10.66.125
	Station
. . .	. . .	. . .	. . .

Finally, network interface 505 provides processing, modulating, and transceiver elements that are operable in accordance with any one or more standard or proprietary wireless interfaces, wherein some of the functionality of the processing, modulating, and transceiver elements may be performed by means of logic circuitry 503 through programmed logic such as software. Examples of network interfaces (wired or wireless) include Ethernet, T1, USB interfaces, IEEE 802.11b, IEEE 802.11g, etc.
FIG. 5 illustrates an apparatus comprising logic circuitry receiving a talkgroup identification and mapping the talkgroup identification to an Internet-of-Things (IoT) device, the logic circuitry also determining a control command based on the IoT device. A network interface is provided that is coupled to the logic circuitry, the network interface outputs the control command to operate the IoT device.
As discussed, the logic circuitry may also receive a verbal action command and determines the control command based on both the IoT device and the verbal action command.
Additionally, a Natural-Language Processor (NLP) may be provided outputting the verbal action command to the logic circuitry.
Additionally, a Wide-Area-Network (WAN) transceiver may be provided for receiving transmissions over the talkgroup and outputting the talkgroup identification to the logic circuitry.
Finally, a database may be provided comprising the mapping of the talkgroup to the IoT device address.
In general, logic circuitry 503 receives a talkgroup identification from an over-the-air transmission of a radio. Logic circuitry 503 maps the talkgroup identification to an Internet-of-Things (IoT) device. The mapping is preferably done by accessing database 504 and retrieving the mappings as shown in Table 1 and Table 2. Logic circuitry 503 accesses database 504 and determines a control command based on the IoT device. Logic circuitry 503 also determines an address of the IoT device and outputs the control command to operate the IoT device via network interface 505.
As discussed above, a verbal action command may be received from the over-the-air transmission; and determining the control command may further comprise determining the control command based on both the IoT device and the verbal action command.
Finally, the talkgroup identification preferably is received from a push-to-talk transmission from the radio.
As discussed above, each IoT device may be mapped to a specific talkgroup, so that reception on a first talkgroup initiates an action to a first IoT device, and reception on a second talkgroup initiates an action on a second IoT device.
For example, logic circuitry 503 receives a first talkgroup identification from a first over-the-air transmission of a first radio. Logic circuitry 503 receives a second talkgroup identification from a second over-the-air transmission of a second radio. Logic circuitry 503 then maps the first talkgroup identification to a first Internet-of-Things (IoT) device and maps the second talkgroup identification to a second IoT device. Logic circuitry then determines a first control command based on the first IoT device and determines a second control command based on the second IoT device. The first control command is output to the first IoT device and the second control command is output to the second IoT device.
As discussed above, the first control command may comprise a control command from a first control protocol, and the second control command may comprise a control command from a second control protocol, differing from the first control protocol, with the first IoT device differing from the second IoT device.
Logic circuitry 503 may also receive a first verbal action command from the first over-the-air transmission of the first radio and a second verbal action command from the second over-the-air transmission of the second radio. When this occurs, determining the first control command may further comprise determining the first control command based on both the first IoT device and the first verbal action command, and determining the second control command may further comprise determining the second control command based on both the second IoT device and the second verbal action command.
However, in some examples, a control command may fail. Attention is now directed to FIG. 6 which depicts a flowchart representative of a method 600 showing operation of the server 301 when managing a failure of a control command. The operations of the method 600 of FIG. 6 correspond to machine readable instructions that are executed by the server 301, and specifically the logic circuitry 503 of the server 301. In the illustrated example, the instructions represented by the blocks of FIG. 6 may be stored at a memory of the server 301. The method 600 of FIG. 6 is one way in which the logic circuitry 503 and/or the server 301 and/or the system 400 may be configured. Furthermore, the following discussion of the method 600 of FIG. 6 will lead to a further understanding of the system 400, and its various components.
The method 600 of FIG. 6 need not be performed in the exact sequence as shown and likewise various blocks may be performed in parallel rather than in sequence. Accordingly, the elements of the method 600 are referred to herein as “blocks” rather than “steps.” The method 600 of FIG. 6 may be implemented on variations of the system 400, as well.
At a block 602, the logic circuitry 503 and/or the server 301 receives, via the network interface 505, from a device 100, a control command for an IoT device 412, the IoT device 412 and the device 100 mapped to a talkgroup identifier identifying a talkgroup used by the device to send the control command, as described above.
At a block 604, the logic circuitry 503 and/or the server 301 outputs, via the network interface 505, to the IoT device 412, the control command, as described above.
At a block 606, the logic circuitry 503 and/or the server 301 determines that the control command has failed.
In particular, various failure modes may when the logic circuitry 503 and/or the server 301 transmits the control command to the IoT device 412.
For example, the IoT device 412 may receive the control command and may be unable to execute the control command due to an apparatus failure, and the like, at the IoT device 412. In these examples, the IoT device 412 may transmit a failure indication to the server 301 in response to receiving the control command, for example when the IoT device 412 is unable to implement the control command. Hence, in some examples, the logic circuitry 503 and/or the server 301 determines that the control command has failed by receiving, from the IoT device 412, one or more of: a failure indication; and NAK (Negative Acknowledgement) data. For example, NAK data and/or a NAK may be a specific example of a failure indication transmitted by the IoT device 412 to one or more of reject the control command and indicate an error that occurred at the IoT device 412 when attempting to implement the control command, regardless of a reason for the failure.
In other examples, a failure may occur due to a network failure and/or a communication failure at the IoT device 412 (e.g. the IoT device 412 may be off and/or communication components of the IoT device 412 may have failed) and the like. For example, the server 301 may attempt to transmit the control command to the IoT device 412 but may not receive any acknowledgement from the IoT device 412 in response to transmitting the control command. Indeed, transmission of the control command to the IoT device 412 may include an attempt to establish a network connection with the IoT device 412 which may not occur due to a network failure and/or a failure of communication components at the IoT device 412. Hence, in some examples, the logic circuitry 503 and/or the server 301 determines that the control command has failed by failing to one or more of: establish a connection to the IoT device 412; receive ACK (Acknowledgement) data from the IoT device 412; receive NAK data from the IoT device 412; and receive a communication from the IoT device 412 in response to transmitting the control command. Indeed, a failure to receive a communication from the IoT device 412 in response to transmitting the control command may indicate to the server 301 that the control command failed.
At a block 608, the logic circuitry 503 and/or the server 301 transmits, via the network interface 505, to the device 100, an indication that the control command has failed, the indication transmitted over the talkgroup identified by the talkgroup identifier.
Hence, the device 100 receives, in response to transmitting the control command to the server 301 over the talkgroup identified by the talkgroup identifier, the indication that the control command has failed. The device 100 may provide an indication of the failure at a notification device, including, but not limited to, the display screen 107, and hence the user 201 may be notified of the failure. The user 201 may then operate the device 100 to control another the IoT device 412 accordingly. For example, when the user 201 operates the device 100 to attempt to unlock a door (e.g. a first IoT device 412) of a building, and a failure occurs, the user 201 may be notified of the failure (e.g. via text and/or graphic rendered at display screen 107) and the user 201 may operate the device 100 to attempt to unlock another door (e.g. a second IoT device 412) of the building.
Alternatively, the logic circuitry 503 and/or the server 301 may, in response to determining that the control command has failed (e.g. at the block 606): transmit a second control command to a second IoT device 412, the second IoT device 412 associated with the IoT device 412. For example, the database 504 may store a relationship between two (or more) IoT devices 412 and when the logic circuitry 503 and/or the server 301 determines that a failure at a first IoT device 412 has occurred (e.g., the logic circuitry 503 and/or the server 301 determines that a control command for the first IoT device 412 has failed) the logic circuitry 503 and/or the server 301 may transmit a second control command to an associated second IoT device 412. Hence, for example, when the control command received at the block 602 is to unlock a first door (e.g. a first IoT device 412) of a building and the logic circuitry 503 and/or the server 301 determines that the control command failed, the logic circuitry 503 and/or the server 301 may determine that a second door (e.g. a second IoT device 412) of the building is associated with the first door, as stored at the database 504, and transmit a second control command to the second door of the building. The logic circuitry 503 and/or the server 301 may transmit an indication of the failure of the control command of the first door to the device 100, and the logic circuitry 503 and/or the server 301 may further transmit, to the device 100, and indication of unlocking the second door, rather than the first door. Put another way, the logic circuitry 503 and/or the server 301 may, in response to determining that the control command has failed (e.g. at the block 606): transmit a second control command to a second IoT device 412, the second IoT device 412 associated with the IoT device 412 (e.g. of the block 602); and in response to determining that the second control command has succeeded (e.g. via receipt of ACK data, and the like, from the second IoT device 412), transmit, via the network interface 505, to the device 100, a second indication that the second control command has succeeded, the second indication transmitted over the talkgroup identified by the talkgroup identifier (e.g. identifying the talkgroup used by the device 100 to send the control command of the block 602). However, the logic circuitry 503 and/or the server 301 may alternatively determine that the second control command has also failed and, in response, transmit, via the network interface 505, to the device 100, a respective indication that the second control command has failed, the respective indication transmitted over the talkgroup identified by the talkgroup identifier (e.g. identifying the talkgroup used by the device 100 to send the control command of the block 602).
Furthermore, the second control command may be transmitted to the second IoT device 412 over a different and/or second talkgroup than that identified by the talkgroup identifier identifying the talkgroup used by the device 100 to send the control command of the block 602. For example, the second IoT device 412 may be mapped (e.g. at the database 504) to a second talkgroup identifier identifying the second talkgroup over which the second control command is transmitted. As such, the database 504 may store an association between the second talkgroup identifier (e.g. identifying the second talkgroup) and the talkgroup identifier (e.g. identifying the talkgroup used by the device 100 to send the control command of the block 602). Put another way, the logic circuitry 503 and/or the server 301 may, in response to determining that the control command has failed (e.g. at the block 606): transmit a second control command to a second IoT device 412, the second IoT device 412 mapped to a second talkgroup identifier associated with the talkgroup identifier (e.g. identifying the talkgroup used by the device 100 to send the control command of the block 602).
In yet further examples, the logic circuitry 503 and/or the server 301 may, in response to determining that the control command has failed (e.g. at the block 606), determine a second IoT device 412 to operate using any suitable process and/or method and/or procedure. For example, various IoT devices 412 may be mapped to talkgroup identifiers at the database 504, but the various IoT devices 412 and/or associated talkgroup identifiers, may not be related at the database 504. However, the logic circuitry 503 and/or the server 301 may use logical algorithms and/or machine learning algorithms, and the like, to determine a second IoT device 412 that may be operated when a first IoT device 412 fails, regardless to which talkgroup identifier an IoT device 412 is mapped. For example, types and/or locations of IoT devices 412 may be stored at the database 504 and the logic circuitry 503 and/or the server 301 may, in response to determining that a control command to a first IoT device 412 has failed: identify a second IoT device 412 (e.g. of a same and/or similar type at a same and/or similar location) to operate (e.g. transmit a second control command) instead of the first IoT device 412. In these examples, indications of failure and/or success of operation of the various IoT devices 412 may be transmitted to the device 100.
In some of these examples, the logic circuitry 503 and/or the server 301 may: transmit (e.g. with the indication transmitted at the block 608), to the device 100, a suggestion and/or a recommendation to operate the second IoT device 412 prior to transmitting the second control command to the second IoT device 412; receive, from the device 100, an acceptance of the suggestion and/or a recommendation to operate the second IoT device 412 (e.g. the user 201 may operate the device 100 to accept the suggestion and/or a recommendation); and, in response to receiving, from the device 100, the acceptance of the suggestion and/or recommendation, transmit the second control command to the second IoT device 412. Hence, the second IoT device 412 may not be operated until the user 201 operates the device 100 to specifically control the second IoT device 412. Such an acceptance may occur via the talkgroup used by the device 100 to send the control command at the block 602.
Furthermore, the method 600 may occur for groups of IoT devices 412 mapped to a talkgroup identifier. For example, at the block 602, the received control command may be received on a talkgroup having a talkgroup identifier mapped to the device 100 and a plurality of IoT devices 412, and, at the block 604, the control command may be transmitted to the plurality of IoT devices 412. Hence, at the block 606, the logic circuitry 503 and/or the server 301 may determine that the control command has failed when any of the above described conditions occur for one or more of the plurality of IoT devices 412 and, at the block 608, transmit to the device 100 the indication that the control command has failed for one or more of the plurality of IoT devices 412. In some of these examples, the indication that the control command has failed may indicate for which of the of the plurality of IoT devices 412 that the control command has failed.
Furthermore, in some of these examples, the logic circuitry 503 and/or the server 301 may, in response to determining that the control command has failed for one or more of the plurality of IoT devices 412: transmit a second control to one or more second IoT devices 412, similar to as described above, for example using relationships between IoT devices 412 and/or talkgroup identifiers stored at the database 504 and/or by determining one or more second IoT devices 412 to operate using logical algorithms and/or machine learning algorithms, and the like.
In the foregoing specification, specific embodiments have been described. However, one of ordinary skill in the art appreciates that various modifications and changes may be made without departing from the scope of the invention as set forth in the claims below. Accordingly, the specification and figures are to be regarded in an illustrative rather than a restrictive sense, and all such modifications are intended to be included within the scope of present teachings.
The benefits, advantages, solutions to problems, and any element(s) that may cause any benefit, advantage, or solution to occur or become more pronounced are not to be construed as a critical, required, or essential features or elements of any or all the claims. The invention is defined solely by the appended claims including any amendments made during the pendency of this application and all equivalents of those claims as issued.
In this document, language of “at least one of X, Y, and Z” and “one or more of X, Y and Z” may be construed as X only, Y only, Z only, or any combination of two or more items X, Y, and Z (e.g., XYZ, XY, YZ, XZ, and the like). Similar logic may be applied for two or more items in any occurrence of “at least one . . . ” and “one or more . . . ” language.
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”, “has . . . 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.
Those skilled in the art will further recognize that references to specific implementation embodiments such as “circuitry” may equally be accomplished via either on general purpose computing apparatus (e.g., CPU) or specialized processing apparatus (e.g., DSP) executing software instructions stored in non-transitory computer-readable memory. It will also be understood that the terms and expressions used herein have the ordinary technical meaning as is accorded to such terms and expressions by persons skilled in the technical field as set forth above except where different specific meanings have otherwise been set forth herein
It will be appreciated that some embodiments may be comprised of one or more generic or specialized processors (or “processing devices”) 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. Alternatively, some or all functions could be implemented by a state machine that has no stored program instructions, or in one or more application specific integrated circuits (ASICs), in which each function or some combinations of certain of the functions are implemented as custom logic. Of course, a combination of the two approaches could be used.
Moreover, an embodiment may 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. Further, it is expected that one of ordinary skill, notwithstanding possibly significant effort and many design choices motivated by, for example, available time, current technology, and economic considerations, when guided by the concepts and principles disclosed herein will be readily capable of generating such software instructions and programs and ICs with minimal experimentation.
The Abstract of the Disclosure is provided to allow the reader to quickly ascertain the nature of the technical disclosure. It is submitted with the understanding that it will not be used to interpret or limit the scope or meaning of the claims. In addition, in the foregoing Detailed Description, it may be seen that various features are grouped together in various embodiments for the purpose of streamlining the disclosure. This method of disclosure is not to be interpreted as reflecting an intention that the claimed embodiments require more features than are expressly recited in each claim. Rather, as the following claims reflect, inventive subject matter lies in less than all features of a single disclosed embodiment. Thus, the following claims are hereby incorporated into the Detailed Description, with each claim standing on its own as a separately claimed subject matter.

Claims

1. An apparatus comprising:

a network interface; and logic circuitry coupled to the network interface, the logic circuitry configured to:

receive, via the network interface, from a device, a control command for an Internet-of-Things (IoT) device, the IoT device and the device mapped to a talkgroup identifier identifying a talkgroup used by the device to send the control command;

output, via the network interface, to the IoT device, the control command;

determine that the control command has failed; and

in response to determining that the control command has failed,

transmit, via the network interface, to the device, an indication that the control command has failed, the indication transmitted over the talkgroup identified by the talkgroup identifier; and

transmit a second control command to a second IoT device, the second IoT device one or more of associated with the IoT device; and mapped to a second talkgroup identifier associated with the talkgroup identifier.

2. The apparatus of claim 1, wherein the logic circuitry is further configured to determine that the control command has failed by receiving, from the IoT device, one or more of:

a failure indication; and

NAK (Negative Acknowledgement) data.

3. The apparatus of claim 1, wherein the logic circuitry is further configured to determine that the control command has failed by failing to one or more of:

establish a connection to the IoT device;

receive ACK (Acknowledgement) data from the IoT device;

receive NAK data from the IoT device; and

receive a communication from the IoT device in response to transmitting the control command.

4. (canceled)

5. (canceled)

6. (canceled)

7. The apparatus of claim 1, wherein the logic circuitry is further configured to, in response to determining that the control command has failed:

transmit, to the device, a suggestion that the second IoT device be operated;

receive, from the device, an acceptance of the suggestion; and

in response to receiving the acceptance, transmit a second control command to the second IoT device.

8. A method comprising:

receiving, at a Push-To-Talk (PTT) server, from a device, a control command for an Internet-of-Things (IoT) device, the IoT device and the device mapped to a talkgroup identifier identifying a talkgroup used by the device to send the control command; outputting, via the PTT server, to the IoT device, the control command;

determining, at the PTT server, that the control command has failed; and

in response to determining that the control command has failed:

transmitting, via the PTT server, to the device, an indication that the control command has failed, the indication transmitted over the talkgroup identified by the talkgroup identifier; and

transmitting a second control command to a second IoT device, the second IoT device one or more of, associated with the IoT device, and mapped to a second talkgroup identifier associated with the talkgroup identifier.

9. The method of claim 8, wherein determining that the control command has failed comprises receiving, from the IoT device, one or more of:

a failure indication; and

NAK (Negative Acknowledgement) data.

10. The method of claim 8, wherein determining that the control command has failed comprises failing to one or more of:

establish a connection to the IoT device;

receive ACK (Acknowledgement) data from the IoT device;

receive NAK data from the IoT device; and

11. (canceled)

12. (canceled)

13. (canceled)

14. The method of claim 8, further comprising, in response to determining that the control command has failed:

transmitting, to the device, a suggestion that the second IoT device be operated;

receiving, from the device, an acceptance of the suggestion; and

in response to receiving the acceptance, transmitting a second control command to the second IoT device.