COPYRIGHT NOTIFICATION
A portion of the disclosure of this patent document and its attachments contain material which is subject to copyright protection. The copyright owner has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure, as it appears in the Patent and Trademark Office patent files or records, but otherwise reserves all copyrights whatsoever.
BACKGROUND
Video data can waste network resources. For example, some security systems route the video data into a cellular network for delivery to some destination. This video data, though, often unnecessarily consumes bandwidth in the cellular network.
BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS
The features, aspects, and advantages of the exemplary embodiments are understood when the following Detailed Description is read with reference to the accompanying drawings, wherein:
FIGS. 1-8 are simplified schematics illustrating an environment in which exemplary embodiments may be implemented;
FIG. 9 is a more detailed block diagram illustrating the operating environment, according to exemplary embodiments;
FIG. 10 illustrates an electronic database of events, according to exemplary embodiments;
FIGS. 11-13 illustrate video data, according to exemplary embodiments;
FIGS. 14-15 illustrate memory allocation, according to exemplary embodiments;
FIG. 16 further illustrates the electronic database of events, according to exemplary embodiments;
FIG. 17 illustrates packet priorities, according to exemplary embodiments;
FIG. 18 illustrates cellular communication, according to exemplary embodiments;
FIGS. 19-20 are flowcharts illustrating an algorithm or method for alarm reporting, according to exemplary embodiments; and
FIGS. 21-25 depict still more operating environments for additional aspects of the exemplary embodiments.
DETAILED DESCRIPTION
The exemplary embodiments will now be described more fully hereinafter with reference to the accompanying drawings. The exemplary embodiments may, however, be embodied in many different forms and should not be construed as limited to the embodiments set forth herein. These embodiments are provided so that this disclosure will be thorough and complete and will fully convey the exemplary embodiments to those of ordinary skill in the art. Moreover, all statements herein reciting embodiments, as well as specific examples thereof, are intended to encompass both structural and functional equivalents thereof. Additionally, it is intended that such equivalents include both currently known equivalents as well as equivalents developed in the future (i.e., any elements developed that perform the same function, regardless of structure).
Thus, for example, it will be appreciated by those of ordinary skill in the art that the diagrams, schematics, illustrations, and the like represent conceptual views or processes illustrating the exemplary embodiments. The functions of the various elements shown in the figures may be provided through the use of dedicated hardware as well as hardware capable of executing associated software. Those of ordinary skill in the art further understand that the exemplary hardware, software, processes, methods, and/or operating systems described herein are for illustrative purposes and, thus, are not intended to be limited to any particular named manufacturer.
As used herein, the singular forms “a,” “an,” and “the” are intended to include the plural forms as well, unless expressly stated otherwise. It will be further understood that the terms “includes,” “comprises,” “including,” and/or “comprising,” when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof. It will be understood that when an element is referred to as being “connected” or “coupled” to another element, it can be directly connected or coupled to the other element or intervening elements may be present. Furthermore, “connected” or “coupled” as used herein may include wirelessly connected or coupled. As used herein, the term “and/or” includes any and all combinations of one or more of the associated listed items.
It will also be understood that, although the terms first, second, etc. may be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another. For example, a first device could be termed a second device, and, similarly, a second device could be termed a first device without departing from the teachings of the disclosure.
FIGS. 1-8 are simplified illustrations of an operating environment, according to exemplary embodiments. While exemplary embodiments may be implemented in many environments, FIG. 1 illustrates a common operating environment that most readers will understand. A security system 20 is installed in a building 22, such as a home or business. The security system 20 may have many sensors 24 that protect occupants from fire, intrusion, and other security conditions. For example, a wireless or wired camera 26 captures video data 28 of some area inside or outside the building 22. Other sensors 30 (such as motion detectors, carbon monoxide and fire sensors, water sensors, and any other sensory devices) may also monitor areas and generate sensory data 32. The video data 28 and any other sensory data 32 may be sent to a security controller 34. The security controller 34 may use or evaluate the video data 28 and the sensory data 32 and generates various events 40. Some of the events 40 may be categorized as benign events 42, while other events 40 may be categorized as alarm events 44. That is, some of the sensory data 32 may indicate a health or safety concern 46 that requires emergency reporting (such as a fire, intrusion, or other alarm event 44). The security controller 34 may thus generate an alarm message 48 that summons emergency personnel (such as a central monitoring station 50, as is known). However, the benign events 42 may be comparatively routine or minor tasks having little or no urgency, consequence, or importance.
FIG. 2 illustrates video confirmation. When the security controller 34 determines any event 40, the security controller 34 may also retrieve the video data 28 as documentary evidence. That is, the security controller 34 sends a command to the network address associated with the video camera 26. The command instructs the video camera 26 to generate and send the video data 28 in response to the corresponding event 40. Presumptively the video camera 26 is aimed in the general direction associated with the event 40, thus capturing documentary evidence. For example, suppose the alarm event 44 indicates heat, smoke, or other indication of fire. The security controller 34 may thus instruct the video camera 26 to send the video data 28 of the area experiencing the smoke or heat. The video data 26 may be sent to the central monitoring station 50 for confirmation. If the video data 28 confirms the alarm event 44, emergency personnel may be summoned, as is generally known. The video data 26 may also be sent to other notification addresses, such as an address associated with a mobile smartphone 60. A user of the smartphone 60 may also view the video data 26 to confirm the alarm event 44.
FIG. 3 illustrates the benign events 42. As the reader may understand, there may be many other situations in which the video data 28 is desired from the video camera 26. These events 40 are not associated with an imminent health and safety concern. For example, suppose the video camera 26 aims toward a front door of a home. When a human visitor activates a doorbell, the security controller 34 may instruct the video camera 26 to capture the video data 28 of the visitor at the door. The video data 28 may thus be sent to any destination for confirmation of the visitor. The user of the smartphone 60 may thus remotely see the human visitor that activated the doorbell. Activation of the doorbell, in other words, triggered one of the benign events 42 that required remote notification and monitoring of the video camera 26 aimed toward the front door. Other benign events 42 may include periodically or randomly requested videos or snapshots of rooms or occupants. Some security customers, for example, may configure the security system 20 to require periodic video sweeps of the home or business. That is, the security controller 34 may execute a schedule 62 that periodically or randomly generates the video data 28 for remote notification and monitoring. The security controller 34 may thus send even more video data 28 according to any scheduled task or operation.
FIG. 4 illustrates routing strategies 70. Here exemplary embodiments may treat the alarm events 44 differently from the benign events 42. The reader may now understand that some video data 28 is more important than others. The alarm events 44, for example, generally indicate the potential health or safety concern 46 and should be reported with priority 72. The benign events 42, though, are comparatively unimportant and may be reported with less priority 72. Exemplary embodiments may thus route the video data 28 based on the priority 72 associated with the event 40. That is, the alarm events 44 and/or their corresponding video data 28 may have a routing strategy 70 that escalates their priority 72. Because the alarm events 44 may indicate life or property is in jeopardy, exemplary embodiments may immediately or nearly immediately send the corresponding video data 28 for routing and delivery to a destination address 74. The video data 28 may even have the priority 72 over less important traffic to further ensure faster/shorter routing with less delay, jitter, and other ill-effects.
The benign events 42, however, may have a different routing strategy 70. The benign events 42 are comparatively routine or minor with little or no urgency, consequence, or importance. The corresponding video data 28 is similarly of a lesser concern. Exemplary embodiments may thus judiciously route the video data 28 associated with the benign events 42. For example, the security controller 34 may implement a delay 76 before sending the video data 28 representing the benign events 42. That is, the security controller 34 may locally cache or store the video data 28 representing the benign events 42 until some condition 78 is satisfied. There may be many conditions 78 depending on the circumstances. Regardless, when the conditions 78 are satisfied, the security controller 34 may then release the video data 28 for routing and delivery to the destination address 74. In simple words, the video data 28 representing the benign events 42 may have a lesser priority 72 that the alarm events 44.
FIGS. 5-6 illustrate network connectivity 80. two different communications paths 82 when routing the video data 28. The security controller 34, for example, may have a wireline broadband connection 84 to a data network 86. The security controller 34 may thus interface with a modem 88 (such as cable or DSL) to send the video data 28 along the wireline broadband connection 84 and into the data network 86 for routing to the destination address 74. Moreover, the security controller 34 may also have a second wireless connection 90 to a wireless network 92. For example, the security controller 34 may have a cellular transceiver (“TX/RX”) 94 that wirelessly sends the video data 28 into a private cellular network 96 for routing to the data network 86. Whenever the security controller 34 determines any event 40, the security controller 34 may send the corresponding video data 28 into or over one of the two different communications paths 84 and/or 90.
FIG. 6 illustrates cellular routing. Here exemplary embodiments may utilize the wireless connection 90 only when urgent. That is, the private cellular network 96 may be reserved for when the wireline broadband connection 84 is down or otherwise unavailable. As the reader may understand, the performance of wireless networks may be affected by traffic. As more and more of the video data 28 is wirelessly sent into the wireless network 92, bandwidth (e.g., speed or bitrate) and other performance parameters may suffer or degrade. Exemplary embodiments may thus only select the private cellular network 96 for only the most urgent of the events 40 and/or when the security controller 34 lacks the network connectivity 80 to the wireline broadband connection 84. That is, if the security controller 34 determines the alarm event 44 and determines the wireline broadband connection 84 is unavailable, then one of the routing strategies 70 may route the video data 28 associated with the alarm event 44 via the wireless connection 90 to the private cellular network 96.
FIG. 7 illustrates benign routing. Here the benign events 42 may have a different routing strategy 70. The benign events 42 are comparatively routine or minor. Their corresponding video data 28, likewise, may also have a lesser concern. So, when the wireline broadband connection 84 is unavailable, the benign events 42 (and their associated video data 28) may be delayed until restoration. That is, the security controller 34 may decline to route the video data 28 via the wireless connection 90 into the private cellular network 96. The security controller 34, instead, may implement the delay 76 and store the video data 28 (representing the benign events 42) in a local memory 100. The security controller 34, for example, may hold the benign events 42 and/or their associated video data 28 until the network connectivity 80 indicates the wireline broadband connection 84 is available. The lesser-important video data 28, in other words, may thus be later routed in time via the wireline broadband connection 84. Here, then, the delay 76 conserves bandwidth in the private cellular network 96 for only the urgent alarm events 44.
Exemplary embodiments reduce congestion. All the different events 40, and their associated video data 28, may generate significant cellular data usage. Exemplary embodiments may thus upload only the most urgent video data 28 associated with the alarm events 44. This routing strategy 70 minimizes cellular traffic, reduces operational costs, and decreases cellular congestion. The video data 28 associated with the benign events 42 (such as routine or scheduled tasks and “snapshots”) may be cached until broadband service is restored. Should cache memory 100 become full, exemplary embodiments may allocate more memory 100 for storing additional video data 28. Exemplary embodiments may optionally begin utilizing the wireless connection 90, even for the benign events 42, in response to the cache memory 100 approaching a maximum byte size. This intelligent “store and forward” routing strategy 70 may be managed by a software application and/or by firmware (such as the security controller 34). Exemplary embodiments thus smartly prioritize alarm traffic over the 3G/4G/LTE wireless connection 90.
FIG. 8 expands the routing strategies 70. Here each different event 40 may have its own routing strategy 70. The security controller 34 generates many different events 40, depending on its programming and configuration (as earlier explained). As there may be many different events 40, each one of the events 40 may have an associated event identifier (or “event ID”) 110. The event identifier 110 may be any alphanumeric combination or other symbolic representation of the corresponding event 40. Each event identifier 110 may thus correspond to the sensor 24 and/or the sensory data 32 responsible for the event 40 (such as the camera 26 generating the video data 28). For example, some event identifiers 110 may be associated with the alarm events 44 that indicate heat or smoke or fire. Other event identifiers 110 may be associated with the alarm events 44 that indicate intrusion (infrared, motion, open contact, or glass breakage). Indeed, there may be many event identifiers 110 that are associated with the different alarm events 44. Similarly, more event identifiers 110 may be associated with the different benign events 42 that are not so important.
Exemplary embodiments may consult an electronic database 112 of events. The database 112 of events is illustrated as being locally stored in the security controller 34, but the database 112 of events may be remotely stored and accessed. Once the security controller 34 assigns or determines the event identifier 110, the security controller 34 may query the database 112 of events for the event identifier 110 and retrieve its corresponding priority 72 and routing strategy 70. Each event 40, in other words, may have an electronic database association with its corresponding event identifier 110, its corresponding priority 72, and its corresponding routing strategy 70. Whenever the security controller 34 generates or determines one of the events 40, the security controller 34 may query the electronic database 112 of events and retrieve the corresponding event identifier 110, its priority 72, and its routing strategy 70.
Exemplary embodiments may thus perform a database lookup. Suppose all the benign events 42 have the same routing strategy 70. That is, as earlier explained, perhaps all the benign events 42 are reserved for the wireline broadband connection 84. The electronic database 112 of events may thus have entries specifying the wireline broadband connection 84 for any event identifier 110 having the “benign” priority 72. The security controller 34 may cache or hold back the video data 28 associated with any benign event 42 until the wireline broadband connection 84 is available (e.g., its network connectivity 80 is confirmed or verified). Indeed, exemplary embodiments may command or enforce a general rule 114 that the wireline broadband connection 84 is preferred for all events 40, regardless of the priority 72. However, if the event identifier 110 indicates the “alarm” priority 72, and the wireline broadband connection 84 is down (e.g., its network connectivity 80 indicates unavailable), the routing strategy 70 may authorize or permit routing the video data 28 via the wireless connection 90 into the private cellular network 96. The routing strategy 70, in other words, may override or supersede the general rule 114 that prefers the wireline broadband connection 84. Exemplary embodiments thus ensure that the alarm events 44 are urgently relayed.
Wireless resources are thus conserved. Exemplary embodiments judiciously reserve the private cellular network 96 for perhaps only the urgent situations (e.g., the alarm events 44). The general routing rule 114 may thus force all messages and packets of data (such as the video data 28) via the wireline broadband connection 84, even if the wireless connection 90 is simultaneously available. Exemplary embodiments may thus prefer the wireline broadband connection 84 that has perhaps a substantially greater bitrate and can accommodate more packet traffic. However, when the security controller 34 determines an error with the wireline broadband connection 84, the routing strategy 70 may permit an alternative routing via the wireless connection 90 into the private cellular network 96. The alarm events 44, for example, may be wirelessly sent to ensure reporting and summons.
FIG. 9 is a more detailed block diagram illustrating the operating environment, according to exemplary embodiments. The security controller 34 communicates with the data network 86 via the wireline broadband connection 84. The security controller 34 communicates with the wireless network 92 via the wireless connection 90. The security controller 34 has a processor 120 (e.g., “μP”), application specific integrated circuit (ASIC), or other component that executes a controller application 122 stored in the memory device 100. The controller application 122 instructs the processor 120 to perform operations, such as determining the network connectivity 80 associated with the wireline broadband connection 84 and the wireless connection 90. As FIG. 9 illustrates, the security controller 34 may have multiple network interfaces to multiple networks. A wireline network interface (or “WireNI”) 124, for example, allows the security controller 34 to communicate via the wireline broadband connection 84 with the data network 86. A wireless network interface (“WirelessNI”) 126 allows the security controller 34 to communicate via the wireless connection 90 with the private cellular network 96. The controller application 122 may thus instruct the processor 120 to evaluate the network connectivity 80 associated with either or both the wireline network interface 124 and the wireless network interface 126.
Any connectivity scheme may be used. There are many known connectivity schemes, such as polling or “ping” messages to determine a status of the corresponding connection 84 and 90. If no response is received, or if an error code indicates an operational concern or unavailability, the security controller 34 may infer or conclude that the corresponding connection 84 or 90 is down. Regardless, exemplary embodiments may utilize any other scheme for determining the network connectivity 80.
The security controller 34 may generate the events 40. The controller application 122 may assign the event identifier 110 to each event 40. While there may be hundreds or perhaps thousands of different events 40, in actual practice the events 40 may be generally categorized or grouped based on some common criterion or criteria. Exemplary embodiments may thus map all the different events 40 to a lesser or more manageable number by assigning a common one of the different event identifiers 110.
Exemplary embodiments may be applied regardless of networking environment. Exemplary embodiments may be easily adapted to stationary or mobile devices having cellular, WI-FI®, near field, and/or BLUETOOTH® capability. Exemplary embodiments may be applied to mobile devices utilizing any portion of the electromagnetic spectrum and any signaling standard (such as the IEEE 802 family of standards, GSM/CDMA/TDMA or any cellular standard, and/or the ISM band). Exemplary embodiments, however, may be applied to any processor-controlled device operating in the radio-frequency domain and/or the Internet Protocol (IP) domain. Exemplary embodiments may be applied to any processor-controlled device utilizing a distributed computing network, such as the Internet (sometimes alternatively known as the “World Wide Web”), an intranet, a local-area network (LAN), and/or a wide-area network (WAN). Exemplary embodiments may be applied to any processor-controlled device utilizing power line technologies, in which signals are communicated via electrical wiring. Indeed, exemplary embodiments may be applied regardless of physical componentry, physical configuration, or communications standard(s).
Exemplary embodiments may utilize any processing component, configuration, or system. Any processor could be multiple processors, which could include distributed processors or parallel processors in a single machine or multiple machines. The processor can be used in supporting a virtual processing environment. The processor could include a state machine, application specific integrated circuit (ASIC), and/or a programmable gate array (PGA) including a Field PGA. When any of the processors execute instructions to perform “operations”, this could include the processor performing the operations directly and/or facilitating, directing, or cooperating with another device or component to perform the operations.
FIG. 10 illustrates the electronic database 112 of events, according to exemplary embodiments. Once the event identifier 110 is assigned, the controller application 122 may consult the electronic database 112 of events. The controller application 122 queries for the event identifier 110 and retrieves the matching database entries. FIG. 10 illustrates the electronic database 112 of events as a table 130 that maps, relates, or associates the event 40 and/or the event identifier 110 to its corresponding routing strategy 70 and the priority 72. One of the routing strategies 70, for example, may require all benign events 42 to utilize the wireline network interface 124. That is, as earlier explained, perhaps all the benign events 42 are reserved for the wireline broadband connection (illustrated as reference numeral 84 in FIG. 9). The electronic database 112 of events may thus have entries specifying the wireline broadband connection 84 for any event identifier 110 associated with a “benign” level of the priority 72. The security controller 34 may cache or hold back the video data 28 associated with any benign event 42 until the wireline broadband connection 84 is available (e.g., its network connectivity 80 is confirmed or verified, again as FIG. 9 illustrated). Indeed, exemplary embodiments may command or enforce the general rule 114 (illustrated in FIG. 8) that the wireline broadband connection 84 is preferred for all events 40, regardless of the priority 72. However, if the event identifier 110 indicates the “alarm” priority 72, and the wireline broadband connection 84 is down (e.g., its network connectivity 80 indicates unavailable), the routing strategy 70 may authorize or permit routing the video data 28 via the wireless connection 90 into the private cellular network 96. The routing strategy 70, in other words, may override or supersede the general rule 114 that prefers the wireline broadband connection 84. Exemplary embodiments thus ensure that the alarm events 44 are urgently relayed. The electronic database 112 of events may thus have electronic database associations between the different events 40 and/or the different event identifiers 110 and the different routing strategies 70 and the different priorities 72.
FIGS. 11-13 illustrate the video data 28, according to exemplary embodiments. When the security controller 34 determines the event 40, exemplary embodiments may also capture and/or retrieve the corresponding video data 28. As FIG. 11 illustrates, the controller application 122 may query a database 140 of video data. The database 140 of video data stores or indicates the video data 28 that is generated by the cameras 26. The video data 28 may be streamed in real-time or archived. However, because there may be multiple cameras 26 in the home or business, exemplary embodiments may select the camera 26 that best provides video of the event 40. FIG. 11 illustrates the database 140 of video data as a table 142 that maps, relates, or associates the different events 40 and/or the different event identifiers 110 to different camera addresses 144. The database 140 of video data may thus define relationships that best capture the video data 28 that corresponds to the event 40. When the controller application 122 determines the event 40 and/or the event identifier 110, the controller application 122 may query the database 140 of video data and retrieve the corresponding camera address 144 having an electronic database association with the query search term. The controller application 122 may then send a video request to the camera address 144 (such as a public or private Internet Protocol address). Once the camera address 144 is known, exemplary embodiments may obtain the corresponding video data 28 to further verify the event 40.
FIG. 12 further illustrates the video data 28. Once the video data 28 is determined, the controller application 122 may consult the database 112 of events and retrieve the routing strategy 70. The routing strategy 70, as earlier explained, may be based on the event 40 and/or the event identifier 110. Again, as one example, the general routing rule 114 may prefer the wireline broadband connection 84 for all the different events 40. All the corresponding video data 28 may thus be sent over the wireline broadband connection 84 to conserve resources in the cellular network 96. However, when the network connectivity 80 indicates the wireline broadband connection 84 is unavailable, the routing strategy 70 may authorize or permit wireless routing for alarm events 44. The routing strategy 70 may thus override or supersede the general routing rule 114 to permit sending the associated video data 28 via the wireless connection 90 into the private cellular network 96. The routing strategy 70 thus ensures that video confirmation of the alarm events 44 is performed with concomitant concern.
FIG. 13 illustrates queuing of the video data 28. When the routing strategy 70 implements the delay 76, the corresponding video data 28 may be queued until the network connectivity 80 indicates the wireline broadband connection 84 is restored and thus available. The controller application 122 may thus establish or store a video queue 150 in its local memory 100. The video queue 150 maintains an ordered arrangement or listing of the video data 26 that has been delayed and cached (per the delay 76). That is, the video queue 150 may hold the corresponding video data 28 until the wireline broadband connection 84 is restored. The controller application 122 may thus release the video data 28 in turn, such as according to position and/or chronological time (e.g., FIFO or FILO).
Exemplary embodiments, though, may release according to the priority 72. This disclosure previously explained how each different event 40, and thus its associated video data 28, may be associated with the corresponding priority 72. So, even though the event 40 may have the “benign” priority 72 and be delayed for queuing, there may still be a hierarchy according to the different priorities 72. For example, if the alarm events 44 have the highest priorities 72 (such as “1” and “2” on a numeric scale), other events 40 may have lesser priorities 72 (such as “3” through “10”). The video queue 150 may thus continually rearrange the video queue 150 according to the priority 72 retrieved from the electronic database 112 of events. The video data 28 associated with the lowest priority 72 event 40 (e.g., “10”) may thus be shuffled or demoted to a bottom position in the video queue 150. Other video data 28 may be promoted to upper positions in the video queue 150 according to their corresponding priority 72. The controller application 122 may thus release the video data 28 according to its corresponding priority 72.
FIGS. 14-15 illustrate memory allocation, according to exemplary embodiments. Here exemplary embodiments may allocate different storage locations 152 associated with the video queue 150. That is, a first portion 154 of the memory 100 may be allocated for the video data 28 that corresponds to the alarm events 44. A different second portion 156 of the memory 100, though, may be allocated for the video data 28 that is queued in the video queue 150. FIG. 15 thus illustrates the electronic database 112 of events having additional database entries for a storage position 158. Once the controller application 122 determines the event 40 and/or its corresponding event identifier 110, the controller application 122 may also retrieve the corresponding storage position 158. The storage position 158 may thus be a pointer where the corresponding video data 28 may be stored. Exemplary embodiments may thus allocate the storage position 158 based on the event 40 generated by the security controller 34.
FIG. 16 further illustrates the electronic database 112 of events, according to exemplary embodiments. Here exemplary embodiments may specify parameters associated with the video data 28 that corresponds to the event 40. That is, the electronic database 112 of events may have additional database entries for a video clip size 160. The video clip size 160 may be a permissible amount (perhaps in bytes) of the video data 28 that is collected and sent for the corresponding event 40. For example, the important or urgent alarm events 44 may be permitted a larger amount of the video data 28 (such as 100 MB or even more). That is, if a fire or intrusion is detected, the security controller 34 may be permitted to send a greater amount of the video data 28 to ensure the emergency is fully documented. Events with higher priority 72, in other words, may be permitted a greater amount of the video data 28. Events 40 with lower priority 72 may be confined or reduced to a smaller amount of the video data 28. The video clip size 160 may of course depend on resolution, as higher definition video data 28 consumes more memory space than low definition. Regardless, the video clip size 160 may be any value representing a maximum value. Once the video data 28 attains the permissible video clip size 160 for the corresponding event identifier 110, the security controller 34 may truncate or stop further collection of the video data 28. The video clip size 160 may thus be another scheme for conserving network resources (especially for the video data 28 sent into the cellular network 96). Exemplary embodiments may thus determine the event identifier 110 and then query for the permissible video clip size 160.
Exemplary embodiments may further implement a video clip time 170. The electronic database 112 of events may have even more database entries that associate each event 40 to its corresponding video clip time 170. The video clip time 170 may be a permissible amount in time (perhaps seconds or even minutes) associated with the video data 28 that is collected and sent for the corresponding event 40. For example, the important or urgent alarm events 44 may be permitted a longer time for the video data 28. That is, if a fire or intrusion is detected, the security controller 34 may be permitted to send a longer time of the video data 28 to ensure the emergency is fully documented. Events with higher priority 72, in other words, may be permitted longer times for the video data 28. Events 40 with lower priority 72 may be trimmed in length to ensure the maximum permissible video clip time 170. Once the time length of the video data 28 attains the permissible video clip time 170 for the corresponding event identifier 110, the security controller 34 may edit or stop further collection of the video data 28. The video clip time 170 may thus be another scheme for conserving network resources (especially for the video data 28 sent into the cellular network 96). Exemplary embodiments may thus determine the event identifier 110 and then query for the permissible video clip time 170.
FIG. 17 illustrates packet priorities, according to exemplary embodiments. Here the video data 28 transmitted into either the private cellular network 96 and/or the data network 86 may be prioritized over other traffic. For example, each alarm event 44 has its corresponding priority 72 (determined from the electronic database 112 of events). When the documentary video data 28 is sent via the wireless connection 90 into the private cellular network 96, for example, the video data 28 may indicate or include its associated priority 72. That is, once the priority 72 is known, the priority 72 may be added to the video data 28 associated with the alarm event 44 and the event identifier 110. The priority 72, for example, added to a packet 180 containing at least a portion of the video data 28. When the security controller 34 sends the video data 28, the wireless network interface (illustrated as reference numeral 126 in FIG. 9) may packetize communications or messages into packets of data according to a packet protocol, such as the Internet Protocol. The packets of data contain bits or bytes of data describing the contents, or payload, of a message. A header of each packet 180 of data may contain routing information identifying an origination address and/or a destination address. There are many different known packet protocols, and the Internet Protocol is widely used, so no detailed explanation is needed. For example, exemplary embodiments may add the priority 72 as a bit or byte to the header of the packet 180. The packet 180 may thus have a designated field or position reserved for the priority 72 retrieved from the electronic database 112 of events. As the packet 180 is processed by components in the private cellular network 96 and/or the data network 86, any component may retrieve/read the priority 72 in the header and route or process ahead of other packets, thus again ensuring that video confirmation of the alarm events 44 is performed with concomitant concern.
FIG. 18 illustrates cellular communication, according to exemplary embodiments. As the security controller 34 may have cellular transmission capabilities, the security controller 34 allows device-to-device communication using cellular frequencies and standards. When the security controller 34 sends the video data 28, the video data 28 may also include a cellular identifier 190 that uniquely identifies the security controller 34. For example, each packet 180 containing the video data 28 may also include a cellular telephone number (“CTN”), International Mobile Subscriber Identity (or “IMSI”), or Mobile Station International Subscriber Directory Number (“MSISDN”). Exemplary embodiments may thus identify the security controller 34 transmitting the video data 28 having the priority 72.
FIGS. 19-20 are flowcharts illustrating an algorithm or method for alarm reporting, according to exemplary embodiments. The event 40 is generated (Block 200) and the event identifier 110 is determined (Block 202). The video data 28 is retrieved (Block 204). The electronic database 112 of events is queried (Block 206) and the routing strategy 70, the priority 72, the video clip size 160 and/or the video clip time 170 may be retrieved (Block 208). If the event 40 and/or the event identifier 110 is associated with one of the alarm events 44 (Block 210), then the network connectivity 80 is determined (Block 212). The wireline network interface (“WireNI”) 124 may be selected when available (e.g., no error code) (Block 214). The video data 28 is sent via the wireline broadband connection 84 (Block 216). However, the wireless network interface (“WirelessNI”) 126 may be selected when an error code associated with the wireline network interface 124 is determined (Block 218). The video data 28 is sent via the wireless connection 90 (Block 220).
The flowchart continues with FIG. 20. If the event 40 and/or the event identifier 110 is not associated with one of the alarm events 44 (see Block 210 of FIG. 19), then the wireline network interface (“WireNI”) 124 may be preferred as the general rule 114 (Block 222). The network connectivity 80 associated with the wireline network interface (“WireNI”) 124 is determined (Block 224). If no error code is determined (Block 226), then the wireline network interface (“WireNI”) is selected and the video data 28 is sent via the wireline broadband connection 84 (Block 228). However, if an error code is determined (Block 226), then the delay 76 is implemented (Block 230) and the video data 28 is queued in the video queue 150 (Block 232). The network connectivity 80 may then be randomly or periodically re-evaluated or re-determined (Block 224) until no error code is determined (Block 226). The video data 28 may thus be sent via the wireline broadband connection 84 (Block 228).
FIG. 21 depicts other possible operating environments for additional aspects of the exemplary embodiments. FIG. 21 illustrates the controller application 122 operating within various other processor-controlled devices 300. FIG. 21, for example, illustrates a set-top box (“STB”) (302), a personal/digital video recorder (PVR/DVR) 304, a Global Positioning System (GPS) device 306, an interactive television 308, a tablet computer 310, or any computer system, communications device, or processor-controlled device utilizing the processor and/or a digital signal processor (DP/DSP) 312. The device 300 may also include watches, radios, vehicle electronics, clocks, printers, gateways, mobile/implantable medical devices, and other apparatuses and systems. Because the architecture and operating principles of the various devices 300 are well known, the hardware and software componentry of the various devices 300 are not further shown and described.
FIGS. 22-24 are schematics further illustrating the processor-controlled device 300, according to exemplary embodiments. FIG. 22 is a block diagram of a Subscriber Identity Module 320, while FIGS. 23 and 24 illustrate, respectively, the Subscriber Identity Module 320 embodied in a plug 322 and in a card 324. As those of ordinary skill in the art recognize, the Subscriber Identity Module 320 may be used in conjunction with many devices (such as the security controller 34 and the smartphone 60 illustrated in FIGS. 1-3). The Subscriber Identity Module 320 stores user information (such as the cellular identifier 190 illustrated in FIG. 18) and any portion of the controller application 122. As those of ordinary skill in the art also recognize, the plug 322 and the card 324 each may interface with any mobile or stationary device.
FIG. 22 is a block diagram of the Subscriber Identity Module 320, whether embodied as the plug 322 of FIG. 23 or as the card 324 of FIG. 24. Here the Subscriber Identity Module 320 comprises a microprocessor 326 (μP) communicating with memory modules 328 via a data bus 330. The memory modules 328 may include Read Only Memory (ROM) 332, Random Access Memory (RAM) and or flash memory 334, and Electrically Erasable-Programmable Read Only Memory (EEPROM) 336. The Subscriber Identity Module 320 stores some or all of the controller application 122 in one or more of the memory modules 328. An Input/Output module 338 handles communication between the Subscriber Identity Module 320 and a host device. Because Subscriber Identity Modules are well known in the art, this patent will not further discuss the operation and the physical/memory structure of the Subscriber Identity Module 320.
FIG. 25 is a schematic further illustrating the operating environment, according to exemplary embodiments. FIG. 25 is a block diagram illustrating more possible componentry of the security controller 34. The componentry may include one or more radio transceiver units 352, an antenna 354, a digital baseband chipset 356, and a man/machine interface (MMI) 358. The transceiver unit 352 includes transmitter circuitry 360 and receiver circuitry 362 for receiving and transmitting radio-frequency (RF) signals. The transceiver unit 352 couples to the antenna 354 for converting electrical current to and from electromagnetic waves. The digital baseband chipset 356 contains a digital signal processor (DSP) 364 and performs signal processing functions for audio (voice) signals and RF signals. As FIG. 25 shows, the digital baseband chipset 356 may also include an on-board microprocessor 366 that interacts with the man/machine interface (MMI) 358. The man/machine interface (MMI) 358 may comprise a display device 368, a keypad 370, and the Subscriber Identity Module 320. The on-board microprocessor 366 may also interface with the Subscriber Identity Module 320.
Exemplary embodiments may be applied to any signaling standard. As those of ordinary skill in the art recognize, FIGS. 20-25 may illustrate a Global System for Mobile (GSM) communications device. That is, the communications device may utilize the Global System for Mobile (GSM) communications signaling standard. Those of ordinary skill in the art, however, also recognize that exemplary embodiments are equally applicable to any communications device utilizing the Time Division Multiple Access signaling standard, the Code Division Multiple Access signaling standard, the “dual-mode” GSM-ANSI Interoperability Team (GAIT) signaling standard, or any variant of the GSM/CDMA/TDMA signaling standard. Exemplary embodiments may also be applied to other standards, such as the I.E.E.E. 802 family of standards, the Industrial, Scientific, and Medical band of the electromagnetic spectrum, BLUETOOTH®, and any other.
Exemplary embodiments may be physically embodied on or in a computer-readable memory device or other storage media/medium. This computer-readable medium, for example, may include CD-ROM, DVD, tape, cassette, floppy disk, optical disk, memory card, memory drive, and large-capacity disks. This computer-readable medium, or media, could be distributed to end-subscribers, licensees, and assignees. A computer program product comprises processor-executable instructions for alarm reporting, as the above paragraphs explained.
While the exemplary embodiments have been described with respect to various features, aspects, and embodiments, those skilled and unskilled in the art will recognize the exemplary embodiments are not so limited. Other variations, modifications, and alternative embodiments may be made without departing from the spirit and scope of the exemplary embodiments.
Patent Grant
10565840
