US20200099961A1 - Networked video management system - Google Patents
Networked video management system Download PDFInfo
- Publication number
- US20200099961A1 US20200099961A1 US16/542,693 US201916542693A US2020099961A1 US 20200099961 A1 US20200099961 A1 US 20200099961A1 US 201916542693 A US201916542693 A US 201916542693A US 2020099961 A1 US2020099961 A1 US 2020099961A1
- Authority
- US
- United States
- Prior art keywords
- network
- video
- cameras
- computer
- set forth
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N7/00—Television systems
- H04N7/18—Closed-circuit television [CCTV] systems, i.e. systems in which the video signal is not broadcast
- H04N7/181—Closed-circuit television [CCTV] systems, i.e. systems in which the video signal is not broadcast for receiving images from a plurality of remote sources
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/20—Servers specifically adapted for the distribution of content, e.g. VOD servers; Operations thereof
- H04N21/23—Processing of content or additional data; Elementary server operations; Server middleware
- H04N21/231—Content storage operation, e.g. caching movies for short term storage, replicating data over plural servers, prioritizing data for deletion
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/02—Network architectures or network communication protocols for network security for separating internal from external traffic, e.g. firewalls
- H04L63/0272—Virtual private networks
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/02—Network architectures or network communication protocols for network security for separating internal from external traffic, e.g. firewalls
- H04L63/0281—Proxies
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
- H04L65/10—Architectures or entities
- H04L65/102—Gateways
- H04L65/1023—Media gateways
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
- H04L65/10—Architectures or entities
- H04L65/1045—Proxies, e.g. for session initiation protocol [SIP]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
- H04L65/1066—Session management
- H04L65/1069—Session establishment or de-establishment
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
- H04L65/1066—Session management
- H04L65/1101—Session protocols
-
- H04L65/4069—
-
- H04L65/608—
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
- H04L65/60—Network streaming of media packets
- H04L65/61—Network streaming of media packets for supporting one-way streaming services, e.g. Internet radio
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
- H04L65/60—Network streaming of media packets
- H04L65/65—Network streaming protocols, e.g. real-time transport protocol [RTP] or real-time control protocol [RTCP]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/12—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
-
- H04L67/28—
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/51—Discovery or management thereof, e.g. service location protocol [SLP] or web services
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/56—Provisioning of proxy services
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/20—Servers specifically adapted for the distribution of content, e.g. VOD servers; Operations thereof
- H04N21/21—Server components or server architectures
- H04N21/218—Source of audio or video content, e.g. local disk arrays
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/20—Servers specifically adapted for the distribution of content, e.g. VOD servers; Operations thereof
- H04N21/27—Server based end-user applications
- H04N21/274—Storing end-user multimedia data in response to end-user request, e.g. network recorder
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/40—Client devices specifically adapted for the reception of or interaction with content, e.g. set-top-box [STB]; Operations thereof
- H04N21/41—Structure of client; Structure of client peripherals
- H04N21/414—Specialised client platforms, e.g. receiver in car or embedded in a mobile appliance
- H04N21/4147—PVR [Personal Video Recorder]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/40—Client devices specifically adapted for the reception of or interaction with content, e.g. set-top-box [STB]; Operations thereof
- H04N21/41—Structure of client; Structure of client peripherals
- H04N21/422—Input-only peripherals, i.e. input devices connected to specially adapted client devices, e.g. global positioning system [GPS]
- H04N21/4223—Cameras
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/60—Network structure or processes for video distribution between server and client or between remote clients; Control signalling between clients, server and network components; Transmission of management data between server and client, e.g. sending from server to client commands for recording incoming content stream; Communication details between server and client
- H04N21/63—Control signaling related to video distribution between client, server and network components; Network processes for video distribution between server and clients or between remote clients, e.g. transmitting basic layer and enhancement layers over different transmission paths, setting up a peer-to-peer communication via Internet between remote STB's; Communication protocols; Addressing
- H04N21/647—Control signaling between network components and server or clients; Network processes for video distribution between server and clients, e.g. controlling the quality of the video stream, by dropping packets, protecting content from unauthorised alteration within the network, monitoring of network load, bridging between two different networks, e.g. between IP and wireless
- H04N21/64715—Protecting content from unauthorized alteration within the network
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/60—Network structure or processes for video distribution between server and client or between remote clients; Control signalling between clients, server and network components; Transmission of management data between server and client, e.g. sending from server to client commands for recording incoming content stream; Communication details between server and client
- H04N21/63—Control signaling related to video distribution between client, server and network components; Network processes for video distribution between server and clients or between remote clients, e.g. transmitting basic layer and enhancement layers over different transmission paths, setting up a peer-to-peer communication via Internet between remote STB's; Communication protocols; Addressing
- H04N21/647—Control signaling between network components and server or clients; Network processes for video distribution between server and clients, e.g. controlling the quality of the video stream, by dropping packets, protecting content from unauthorised alteration within the network, monitoring of network load, bridging between two different networks, e.g. between IP and wireless
- H04N21/64723—Monitoring of network processes or resources, e.g. monitoring of network load
- H04N21/64738—Monitoring network characteristics, e.g. bandwidth, congestion level
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N23/00—Cameras or camera modules comprising electronic image sensors; Control thereof
- H04N23/60—Control of cameras or camera modules
- H04N23/63—Control of cameras or camera modules by using electronic viewfinders
- H04N23/631—Graphical user interfaces [GUI] specially adapted for controlling image capture or setting capture parameters
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N23/00—Cameras or camera modules comprising electronic image sensors; Control thereof
- H04N23/60—Control of cameras or camera modules
- H04N23/64—Computer-aided capture of images, e.g. transfer from script file into camera, check of taken image quality, advice or proposal for image composition or decision on when to take image
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N23/00—Cameras or camera modules comprising electronic image sensors; Control thereof
- H04N23/60—Control of cameras or camera modules
- H04N23/66—Remote control of cameras or camera parts, e.g. by remote control devices
- H04N23/661—Transmitting camera control signals through networks, e.g. control via the Internet
Abstract
Description
- This application claims the benefit of U.S. Provisional Application No. 62/735,631 (DICE 0166 PRV) filed Sep. 24, 2018.
- This technology relates to a networked video management system, and more specifically, a networked video management system including a web service proxy protocol.
- Networked video management systems exist to facilitate the streaming, recording and viewing of video data over a network. Many of these systems may include a network video recorder (NVR) or a digital video recorder (DVR). An NVR may be a software application that records video data on a digital medium. NVRs may be typically executed on a dedicated computer device embedded with a digital medium configured to store the NVR and recorded video data, and a processor to execute the NVR. A DVR may be a hardware device that records video data on a digital medium included on the hardware device. While NVRs connected directly to a video capture camera or tuner, a DVR may be connected to a network. A DVR encodes video data while an NVR receives processed and encoded video data for a network camera device. NVRs and DVRs may be commonly deployed in video surveillance systems. There exists a need to develop hardware and/or software solutions for networked video management systems that may be cost effective and flexible with high performance.
-
FIG. 1 depicts a computer architecture for a video management system according to one variation. -
FIG. 2 depicts a sequence diagram of a web service proxy protocol according to one variation. -
FIG. 3 depicts a graphical user interface (“GUI”) for registering, organizing and updated network cameras installed on a video management system according to one variation. -
FIG. 4 depicts a GUI for viewing video data streams from network cameras installed on a video management system according to one variation. -
FIG. 5 depicts a GUI for conducting a timeline search of video data streams from network cameras installed on a video management system according to one variation. -
FIG. 6 depicts a GUI for viewing applicable client sites and installed network cameras via a map screen. -
FIG. 7 depicts a GUI for displaying a dashboard including information to analyze and restore installed network cameras and monitor access to installed video cameras. -
FIG. 8 depicts a GUI for displaying bandwidth information to identify potential network traffic issues on the video management system and to manage data usage on the video management system. - NVRs and DVRs may be commonly used in network video management systems. These systems may be commonly deployed in video surveillance systems. As part of the deployment, the NVRs and/or DVRs (with associated hardware) may be installed at the surveillance site and may be configured to store video data on the devices at the site. On-site storage of video data may be relatively expensive because of infrastructure and maintenance costs associated with NVRs and DVRs. Moreover, there may be difficulties viewing the stored video data remotely from NVRs and DVRs.
- The following variations may be drawn to a networked video management system that may include a video client application that may be executed from a video gateway device, typically residing at a client site, such as, a video surveillance site. The video client application may be configured to transmit video data from the video gateway device to a cloud instance. The video data may be transmitted to the cloud instance through a secure hypertext transfer protocol (HTTPS) connection.
-
FIG. 1 depicts a computer architecture for a networkedvideo management system 10 according to one variation. Thevideo management system 10 may include aclient network 12 residing at aclient site 14. Thevideo management system 10 also may includeserver network 16 virtually residing on acloud instance 18.Server network 16 may also reside on a bare or a virtual machine. Client andserver network external communication network 20. - As shown
FIG. 1 ,client network 12 may include first and secondvideo gateway devices video gateway device client network 12 andserver network 16 to enable network traffic, including streaming video data traffic, to flow in and out of eachnetwork video gateway devices FIG. 1 , the number of video gateway devices may be significantly scalable. In certain variations, the number of video gateway devices may be only limited by the available provisioned cloud resources. The number may be about 10,000. The number may be exceeded with the implementation of network load balancing. - Each
video gateway device networks video gateway device 22 a. Network cameras 26b 1, 26b 2 and 26 bn may be connected tovideo gateway device 22 b. While three network cameras may be shown connected to each ofvideo gateway devices FIG. 1 may be configured to transmit video data to video gateway devices 24 a and 24 b, respectively. -
Video gateway modules video client applications 8. Thevideo client application 8 may be programmed in a run-time environment. The run-time environment may be JavaScript, for example, node.js. respectively.Video client application 8 28 a and 28 b include instructions when executed by a processor included in eachvideo gateway modules -
Server network 16 may include application containers. The application containers may be used to deploy and run distributed applications without launching an entire virtual machine for each application within the container. Each of the containerized applications may be executed on a single host and may be configured to access the same operating system (OS) kernel. Each application container may include a set of runtime components, e.g., files, environment variables and libraries, to perform application functions upon execution of the runtime components. In one or more variations, the set of runtime components to execute in an application container may be an image. A container engine deploys these images onserver network 16 or another host. In one or more variations, the engines may be Kubernetes engines. - Web
service proxy container 30 may be in communication with webservice client containers Virtual camera containers service client containers Virtual camera container 34 a may be in communication withrecorder container 36 a,thumbnails container 38 a, andanalytics container 40 a.Virtual camera container 34 b may be in communication withrecorder container 36 b,thumbnails container 38 b, andanalytics container 40 b.Data storage medium 42 stores recorded video data received fromrecorder containers thumbnails containers video transcoding container 44 may be in communication withvirtual camera container 34 a.Video encoders data storage medium 42. Application programming interface (API)container 48 may be in communication withvideo encoders video transcoding container 44 andAPI container 48 may be incommunication user computers external communication network 50. - Web
server proxy container 30 may include a container engine configured to execute a container image to connectuser computers user computers video gateway devices User computers server proxy container 30 may be configured to support RTSP, as well as other protocols, such as real time transport protocol (RTP) or HTTPS. In one or more variations, components of the container image may be programmed in a run-time environment. The run-time environment may be JavaScript, for example, node.js. -
FIG. 2 depicts a sequence diagram of a webservice proxy protocol 100 that may be executed by the engine of the webservice proxy container 30 andvideo gateway devices arrow 102,video client application 8 initiates a connection to webserver proxy container 30. The connection may be established through HTTPS by checking the certificate of thevideo client application 8, as shown byarrow 104. Once the connection may be established, it may be upgraded to a websocket connection. This initial connection may stay open during the entire sequence of the web service proxy protocol. The initial connection may be used by webserver proxy container 30 to send requests for tunnels tovideo client applications 8. The initial connection may also be used byvideo client applications 8 to notify webserver proxy container 30 thatvideo client applications 8 have detected one or more network cameras onclient network 12. - At
arrow 106, webservice proxy container 30 assigns a scan for network cameras tovideo gateway devices 22 a and/or 22 b. Atarrow 108,video gateway devices 22 a and/or 22 b perform a scan ofclient network 12 to determine the presence of any network cameras (e.g., network cameras 24 a and 24 b). The results of the network scan may be transmitted byvideo gateway devices 22 a and/or 22 b to webservice proxy container 30, as depicted byarrow 110. Webservice proxy container 30 adds available network cameras to awork queue 112 as depicted byarrow 114. - As depicted by
arrow 116,recorder containers 36 a and/or 36 b may be configured to checkwork queue 112 for available network cameras. In response,work queue 112 transmits a message torecorder containers 36 a and/or 36 b including a list of available network cameras, as depicted byarrow 118. After the available network cameras may be transmitted,recorder containers 36 a and/or 36 b transmits a video request to webservice client containers 38 a and/or 38 b, respectively, as represented byarrow 120. Upon receiving the video data request,recorder containers 36 a and/or 36 b request a tunnel from webservice proxy container 30, as depicted byarrow 122. Upon the webservice proxy container 30 receiving the tunnel request, the webservice proxy container 30 requests the tunnel from thevideo gateway devices 22 a and/or 22 b, respectively, as depicted inarrow 124. In turn,gateway devices arrow 126. - As depicted by
arrow 128, the tunnel may be opened between one or more network cameras andvideo gateway devices 22 a and/or 22 b. The tunnel may be then offered to webservice proxy container 30 byvideo gateway devices arrow 130. In turn, as depicted byarrow 132, webservice proxy container 30 offers the tunnel to webservice client containers 32 a and/or 32 b. As shown byarrow 134, RTSP traffic may be established between one or more network cameras andrecorder containers 36 a and/or 36 b. - In certain variations, when web
service proxy container 30 may be notified of a network camera at client site 14 (e.g., at arrow 110), webservice proxy container 30 sends a tunnel request to thevideo gateway devices 22 a and/or 22 b (e.g., at arrow 124). This tunnel request may be made using the initial connection.Video gateway devices 22 a and/or 22 b determine if the tunnel request may be valid. If the tunnel request may be valid, thenvideo gateway devices 22 a and/or 22 b open a second secure protocol connection (e.g., HTTPS connection) to the webservice proxy container 30. In one or more variations, the second connection may be upgraded to a websocket connection. This second connection may be used to transmit network traffic between the network camera(s) andrecorder containers 36 a and/or 36 b (e.g., arrow 134). - After the second connection has been opened, a listening port may be opened on
server network 16 at webservice client containers virtual camera containers client site 14. In one or more variations, only Internet connectivity may be necessary to transmit traffic between network camera(s) andrecorder containers 36 a and/or 36 b. No other network considerations (e.g., firewalls) may be necessary because thevideo management system 10 only initiates Internet connections (e.g., HTTPS connection) toserver network 16, e.g., webservice proxy container 30. The process associated with webservice proxy protocol 100 shown inFIG. 2 may be transparent to client applications executed on the cloud. Webservice client containers recorder containers -
FIG. 3 may be a graphical user interface (“GUI”) 200 for registering, organizing and updated network cameras installed on a video management system according to one variation. In one variation,API container 48 may include an image that may be configured to be executed by an engine to perform queries to obtain the video data streams displayed throughGUI 200.GUI 200 may include alist 202 of network cameras and encoders for a subscriber or client ofvideo management system 10. The network cameras and/or encoders may be connected tovideo gateway devices server network 16 to facilitate the subscriber's or client's viewing of video streams from a user computer.Serial number 204,brand name 206,model 208,username 210,description 212, and live thumbnaillive stream 214 may be displayed inGUI 200 for each camera or encoder inlist 202. -
FIG. 4 may be aGUI 300 for viewing video data streams from network cameras installed on a video management system according to one variation. In one variation,API container 48 may include an image that may be configured to be executed by an engine to retrieve a list of cameras and transcodingcontainer 44 may include an image that may be configured to be executed by an engine to view the video data streams throughGUI 300.GUI 300 may include amatrix 302 ofthumbnail windows 304. Eachthumbnail window 304 may include a video data stream from a network camera. The video data stream may be a live video data stream so that the user may react to situations developing in real-time. The video data stream may also be a recorded video data stream. Alabel 306 may be situated above each window and may include a description of the video data stream at aclient site 14. Non-limiting examples include “front drive,” “semi dock,” “diesel generator,” and “roof generator.” Atime stamp 308, including date and time in HH:MM:SS format, may be situated below eachwindow 304. While a 6 by 3 matrix ofwindows 304 may be shown inFIG. 4 the number ofwindows 304, including the number of rows and columns, may be customizable by the user.GUI 300 may be configured such that eachthumbnail window 304 may be expanded so that the user may obtain a more detailed view of the video data stream. -
FIG. 5 may be aGUI 400 for conducting a timeline search of video data streams from network cameras installed on a video management system according to one variation. In one variation,API container 48 may include an image that may be configured to be executed by an engine to querydata storage medium 42 for a list of thumbnails and to submit a video encoding request to encodercontainers GUI 400 may includetimeline search window 402 and datastream windows matrix 404.Timeline search window 402 may include data input fields foraccount 406, device 408,stream number 410, start date andtime 412, end date andtime 414, and size 416.Timeline search window 402 also may include submitbutton 418 and back button 420. A user inputs the account name in accountdata input field 406. The user inputs the device number in device data input field 408. The user inputs the stream (e.g., that correlates to one of the network cameras) into streamdata input field 410. The user inputs a start date and time in HH:MM am/pm format in start date andtime input field 412. The user inputs an end date and time in HH:MM am/pm format in start date andtime input field 414. The user inputs size in size data input field 416. In the example shown inFIG. 5 , the difference between the start and end time may be 1 hour and the size may be 6. Once all the data may be input into data input fields 406 through 416, the user clicks the submitbutton 418 to perform a timeline search. Accordingly, the datastream windows matrix 404 shows six window with a time slice every ten (10) minutes within between the start and stop times (e.g., sixty (60) minutes divided by 6). Each window 422 withinmatrix 404 may include atime stamp portion 424 including a download link configured to download the associated thumbnail image and streaming, and window portion 426 configured to display a thumbnail image and a video data stream starting at the start time identified in thetime stamp portion 424. Advantageously, the timeline search window enables the user to pinpoint the exact timeframes of events and narrow a user's search with interactive thumbnail slices. -
FIG. 6 may be aGUI 500 for viewing applicable client sites and installed network cameras via a map screen. In one variation,API container 48 may include an image that may be configured to be executed by an engine to query a database to retrieve and plot the latitude and longitude as entered by the user and associated with the video data stream.GUI 500 may include network cameradigital map 502 including the locations 504 of network cameras at aclient site 14.GUI 500 also may include anaccount information window 506 including account information for the user.GUI 500 may include a matrix 508 ofthumbnail windows 510. Eachthumbnail window 510 may include a video data stream from a network camera. The video data stream may be a live video data stream so that the user may react to situations developing in real-time. The video data stream may also be a recorded video data stream. Alabel 512 may be situated above each window and may include a description of the video data stream at aclient site 14. Non-limiting examples include “front drive,” “semi dock,” “diesel generator,” and “roof generator.” A time stamp 514, including date and time in HH:MM:SS format, may be situated below eachwindow 510. While a 3 by 3 matrix ofwindows 510 may be shown inFIG. 6 the number ofwindows 510, including the number of rows and columns, may be customizable by the user.GUI 500 may be configured such that eachthumbnail window 510 may be expanded so that the user may obtain a more detailed view of the video data stream. Advantageously,map GUI 500 enables the user to view satellite images ofdifferent client sites 14 and stream real time thumbnail videos of all network camera at each location. -
FIG. 7 may be a GUI 600 for displaying a dashboard including information to analyze and restore installed network cameras and monitor access to installed video cameras. In one variation,API container 48 may include an image that may be configured to be executed by an engine to query a database, a work queue, embedded APIs inrecorder containers service proxy container 30, and transcodingcontainer 44. The queried data may be displayed through GUI 600. GUI 600 may includeaccount number window 602,status window 604, live stream 606, andrecorder window 608.Account number window 602 may include a data entry field 610 for an account number of a user.Status window 604 may include statistics regarding streams recording, cameras reporting and registered cameras. Live streams window may include a list 612 of live streams for a user. Each live stream may include the following non-limiting information: user, account number, edge, camera, stream and stream started date and time.Recorders window 608 may include alist 614 of recorders or other network cameras. Each recorder listed may include the following non-limiting information: account number, edge, camera, stream recorder started, recording started, tags, and thumbnail. Advantageously, dashboard GUI 600 enables users to analyze and restore devices and monitor employee access. -
FIG. 8 may be aGUI 700 for displaying a bandwidth information to identify potential network traffic issues on the video management system and to manage data usage on the video management system. In one variation,API container 48 may include an image that may be configured to be executed by an engine to query bandwidth data recorded invirtual camera containers GUI 700.GUI 700 may includeselect subscriber window 702, bandwidth selector window 704,bandwidth usage window 706, andgateway bandwidth window 708.Select subscriber window 702 may be configured to enable a user to input an account number through account number data input field 710.Bandwidth selector window 706 may include data input fields for selector type 712 (e.g., account number),time unit 714,start date 716, andend date 718.Bandwidth selector window 706 also may include a submitbutton 720. After the user inputs date into data input fields 712 through 718, then user selects submitbutton 720 so that the data meeting the data input fields 712 through 718 may be displayedbandwidth usage window 706 andgateway bandwidth window 708.Bandwidth usage window 706 displays agraph 722 that plots the amount of bandwidth used by each network camera versus time from the start time to end time.Gateway bandwidth window 708 displays a list 724 of network cameras. For each network camera, the network camera name and bandwidth used on the start and ends dates may be displayed.Bandwidth GUI 700 enables users to identify potential network issues and manage data issues as needed. - A computer system for networked video management is disclosed. The computer system may include a computer having non-transitory memory for storing machine instructions that may be to be executed by the computer. The machine instructions when executed by the computer implement the following functions: scanning a network for network cameras connected to the network to obtain a list of connected network cameras; transmitting the list of connected network cameras; receiving a tunnel request between the connected network cameras on the list and a video recorder application; establishing a tunnel with each connected network camera; and offering the tunnel to applications on the network.
- A computer system for networked video management is disclosed. The computer system may include a computer having non-transitory memory for storing machine instructions that may be to be executed by the computer. The machine instructions when executed by the computer implement the following functions: requesting a scan of a network for network cameras connected to the network; receiving a list of connected network cameras; transmitting a tunnel request between the connected network cameras on the list and a video recorder application; receiving a tunnel offer in response to transmitting the tunnel request; and offering the tunnel to applications on the network.
- A computer readable medium having non-transitory memory for storing machine instructions that may be to be executed by the computer may be disclosed. The machine instructions when executed by the computer implements the following functions: scanning a network for network cameras connected to the network to obtain a list of connected network cameras; transmitting the list of connected network cameras; receiving a tunnel request between the connected network cameras on the list and a video recorder application; establishing a tunnel with each connected network camera; and offering the tunnel to applications on the network.
- A method for networked video management is disclosed. The method may include scanning a network for network cameras connected to the network to obtain a list of connected network cameras; transmitting the list of connected network cameras; receiving a tunnel request between the connected network cameras on the list and a video recorder application; establishing a tunnel with each connected network camera; and offering the tunnel to applications on the network.
-
Variation 1 may include a product comprising a computer system for networked video management, the computer system comprising at least one computer having non-transitory memory for storing machine instructions that may be executed by the computer, the machine instructions when executed by the computer may implement functions. The functions may include scanning a network for network cameras connected to the network to obtain a list of connected network cameras; transmitting the list of connected network cameras; receiving a tunnel request between the connected network cameras on the list and a video recorder application; establishing a tunnel with each connected network camera; and offering the tunnel to applications on the network. -
Variation 2 may include a product as set forth invariation 1, and may further include initiating a connection to a web server proxy container established through a secure hypertext transfer protocol prior to scanning a network for network cameras connected to the network to obtain a list of connected network cameras. - Variation 3 may include a product as set forth in any of
variations - Variation 4 may include a product as set forth in any of variations 1-3, wherein the websocket connection may be constructed and arranged to transmit network traffic between the network cameras and at least one recorder container.
- Variation 5 may include a product as set forth in any of variations 1-4, wherein the network for network cameras may further include a client-side network; a server network virtually residing on a cloud instance; and wherein the client-side network and the server network may be in communication with one another over the network for network cameras.
- Variation 6 may include a product as set forth in any of variations 1-5 and may further include opening a listening port on the server network at at least one web service client container and transmitting all traffic the listening port receives from at least one virtual camera containers to the corresponding network camera.
- Variation 7 may include a product as set forth in any of variations 1-6 wherein the at least one computer having non-transitory memory for storing machine instructions may be at least one server side computer.
-
Variation 8 may include a product as set forth in any of variations 1-7 and may further comprise at least one video gateway device constructed and arranged to act as a gate between a client network and a server network to enable network traffic flow between the client network and the server network. - Variation 9 may include a product as set forth in any of variations 1-8 may further comprise establishing real time streaming protocol traffic between the connected network cameras and the video recorder application.
-
Variation 10 may include a computer system for networked video management, the computer system comprising at least one computer having non-transitory memory for storing machine instructions that are to be executed by the computer, the machine instructions when executed by the at least one computer implement functions. The functions may include requesting a scan of a network for network cameras connected to the network; receiving a list of connected network cameras; transmitting a tunnel request between the connected network cameras on the list and a video recorder application; receiving a tunnel offer in response to transmitting the tunnel request; and offering the tunnel to applications on the network. - Variation 11 may include a product as set forth in
variation 10, and may further include initiating a connection to a web server proxy container established through a secure hypertext transfer protocol prior to scanning a network for network cameras connected to the network to obtain a list of connected network cameras, -
Variation 12 may include a product as set forth in variations 10-11, wherein initiating a connection to a web server proxy container established through a secure hypertext transfer protocol may further comprise checking a certificate of a video client application and upgrading the connection to a websocket connection. - Variation 13 may include a product as set forth in variations 10-12, may further include establishing real time streaming protocol traffic between the connected network cameras and the video recorder application.
-
Variation 14 may include a product as set forth in variations 10-13, wherein the network for network cameras may further comprise a client-side network; a server network virtually residing on a cloud instance; and wherein the client-side network and the server network may be in communication with one another over the network for network cameras. - Variation 15 may include a product as set forth in variations 10-14, wherein the at least one computer having non-transitory memory for storing machine instructions may be at least one server side computer.
-
Variation 16 may include providing at least one computer having non-transitory memory for storing machine instructions that are to be executed by the at least one computer, the machine instructions when executed by the at least one computer implements functions. The functions may include initiating a connection to a web server proxy container via a video client application; scanning a network for network cameras connected to the network to obtain a list of connected network cameras; transmitting the list of connected network cameras to the web server proxy container; requesting a tunnel from the web service proxy container via the at least one recorder container and from at least one video gateway device via the web service proxy container; establishing the tunnel with the network of network cameras via the at least one video gateway device; offering the tunnel to the web service proxy container via the at least one video gateway device; offering the tunnel to the web service client container via the web service proxy container; and establishing real time streaming protocol traffic. - Variation 17 may include a method as set forth in
variation 16 and may further comprise initiating a connection to a web server proxy container established through a secure hypertext transfer protocol prior to scanning a network for network cameras connected to the network to obtain a list of connected network cameras. -
Variation 18 may include a product as set forth in variations 16-17, wherein initiating a connection to a web server proxy container established through a secure hypertext transfer protocol may further comprise checking a certificate of a video client application and upgrading the connection to a websocket connection. - Variation 19 may include a product as set forth in variations 16-18, wherein the at least one computer having non-transitory memory for storing machine instructions may be at least one server side computer.
-
Variation 20 may include a product as set forth in variations 16-19, wherein the network for network cameras may further comprise a client-side network; a server network virtually residing on a cloud instance; and wherein the client-side network and the server network may be in communication with one another over the network for network cameras. - As required, detailed variations of the present invention are disclosed herein; however, it may be to be understood that the disclosed variations may be merely exemplary of the invention that may materialize in various and alternative forms. The figures may be not necessarily to scale; some features may be exaggerated or minimized to show details of particular components. Therefore, specific structural and functional details disclosed herein may be not to be interpreted as limiting, but merely as a representative basis for teaching one skilled in the art to variously employ the present invention.
- While exemplary variations may be described above, it may be not intended that these variations describe all possible forms of the invention. Rather, the words used in the specification may be words of description rather than limitation, and it may be understood that various changes may be made without departing from the spirit and scope of the invention. Additionally, the features of various implementing variations may be combined to form further variations of the invention.
Claims (20)
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US16/542,693 US20200099961A1 (en) | 2018-09-24 | 2019-08-16 | Networked video management system |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US201862735631P | 2018-09-24 | 2018-09-24 | |
US16/542,693 US20200099961A1 (en) | 2018-09-24 | 2019-08-16 | Networked video management system |
Publications (1)
Publication Number | Publication Date |
---|---|
US20200099961A1 true US20200099961A1 (en) | 2020-03-26 |
Family
ID=69883757
Family Applications (3)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US16/542,693 Pending US20200099961A1 (en) | 2018-09-24 | 2019-08-16 | Networked video management system |
US16/576,919 Active US11363313B2 (en) | 2018-09-24 | 2019-09-20 | Networked video management and recording system |
US16/578,552 Active US11496779B2 (en) | 2018-09-24 | 2019-09-23 | Gateway for networked video management system |
Family Applications After (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US16/576,919 Active US11363313B2 (en) | 2018-09-24 | 2019-09-20 | Networked video management and recording system |
US16/578,552 Active US11496779B2 (en) | 2018-09-24 | 2019-09-23 | Gateway for networked video management system |
Country Status (1)
Country | Link |
---|---|
US (3) | US20200099961A1 (en) |
Cited By (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US11363313B2 (en) * | 2018-09-24 | 2022-06-14 | Dice Corporation | Networked video management and recording system |
US11595350B2 (en) * | 2020-05-08 | 2023-02-28 | Ribbon Communications Operating Company, Inc. | Networking as a service |
US11652890B1 (en) * | 2022-07-13 | 2023-05-16 | Oxylabs, Uab | Methods and systems to maintain multiple persistent channels between proxy servers |
US11777790B2 (en) * | 2020-04-16 | 2023-10-03 | Ribbon Communications Operating Company, Inc. | Communications methods and apparatus for migrating a network interface and/or IP address from one Pod to another Pod in a Kubernetes system |
Family Cites Families (38)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6954859B1 (en) | 1999-10-08 | 2005-10-11 | Axcess, Inc. | Networked digital security system and methods |
US6980526B2 (en) * | 2000-03-24 | 2005-12-27 | Margalla Communications, Inc. | Multiple subscriber videoconferencing system |
AU2001257256A1 (en) | 2000-05-03 | 2001-11-12 | Perceptual Robotics, Inc. | Camera network management system |
CA2390621C (en) * | 2002-06-13 | 2012-12-11 | Silent Witness Enterprises Ltd. | Internet video surveillance camera system and method |
US6768726B2 (en) * | 2002-08-06 | 2004-07-27 | Motorola, Inc. | Method and apparatus for effecting a seamless handoff between IP connections |
US10237237B2 (en) * | 2007-06-12 | 2019-03-19 | Icontrol Networks, Inc. | Communication protocols in integrated systems |
US10200504B2 (en) | 2007-06-12 | 2019-02-05 | Icontrol Networks, Inc. | Communication protocols over internet protocol (IP) networks |
US7944470B2 (en) | 2005-03-04 | 2011-05-17 | Armida Technologies Corporation | Wireless integrated security controller |
US7685292B1 (en) * | 2005-04-07 | 2010-03-23 | Dell Marketing Usa L.P. | Techniques for establishment and use of a point-to-point tunnel between source and target devices |
US8280978B2 (en) * | 2006-12-29 | 2012-10-02 | Prodea Systems, Inc. | Demarcation between service provider and user in multi-services gateway device at user premises |
US8170037B2 (en) * | 2008-05-21 | 2012-05-01 | Polcha Andrew J | Devices and methods for a virtual internet protocol television (VIPTV) |
US20170070361A1 (en) * | 2008-08-11 | 2017-03-09 | Ken Sundermeyer | Data model for home automation |
US8606073B2 (en) * | 2010-05-12 | 2013-12-10 | Woodman Labs, Inc. | Broadcast management system |
US8928756B2 (en) * | 2010-10-22 | 2015-01-06 | Alcatel Lucent | Surveillance video router |
KR20120071121A (en) | 2010-12-22 | 2012-07-02 | 한국전자통신연구원 | Virtual tunnel router, ip camera management server and ip camera service method based on position information |
US20130198829A1 (en) * | 2011-08-08 | 2013-08-01 | Advanced Video Communications, Inc. | System to retrieve and distribute images in real time |
US9722972B2 (en) * | 2012-02-26 | 2017-08-01 | Oracle International Corporation | Methods and apparatuses for secure communication |
US9350644B2 (en) | 2012-04-13 | 2016-05-24 | Zscaler. Inc. | Secure and lightweight traffic forwarding systems and methods to cloud based network security systems |
US9986209B2 (en) | 2013-02-15 | 2018-05-29 | Steven Philip Meyer | Method and system for managing data from digital network surveillance cameras |
WO2014144628A2 (en) | 2013-03-15 | 2014-09-18 | Master Lock Company | Cameras and networked security systems and methods |
US20150022666A1 (en) | 2013-07-22 | 2015-01-22 | Intellivision Technologies Corp. | System and method for scalable video cloud services |
WO2015103338A1 (en) | 2013-12-31 | 2015-07-09 | Lookout, Inc. | Cloud-based network security |
US11146637B2 (en) | 2014-03-03 | 2021-10-12 | Icontrol Networks, Inc. | Media content management |
US9356895B2 (en) * | 2014-05-07 | 2016-05-31 | Mitake Information Corporation | Message transmission system and method for a structure of a plurality of organizations |
US20150326513A1 (en) * | 2014-05-07 | 2015-11-12 | Mitake Information Corporation | Message transmission system and method suitable for individual and organization |
US10268492B2 (en) * | 2014-05-20 | 2019-04-23 | Amazon Technologies, Inc. | Low latency connections to workspaces in a cloud computing environment |
US9349054B1 (en) * | 2014-10-29 | 2016-05-24 | Behavioral Recognition Systems, Inc. | Foreground detector for video analytics system |
US20160127691A1 (en) * | 2014-11-04 | 2016-05-05 | WOW Insites LLP | Method, computer program, and system for adjusting cameras |
US10002507B2 (en) * | 2015-08-05 | 2018-06-19 | Securenet Technologies | Integrated security network |
MX2018003708A (en) | 2015-09-25 | 2018-09-21 | Genetec Inc | Secure enrolment of security device for communication with security server. |
US20170118127A1 (en) * | 2015-10-22 | 2017-04-27 | Cox Communications, Inc. | Systems and Methods of Virtualized Services |
US11314546B2 (en) * | 2016-11-18 | 2022-04-26 | Data Accelerator Ltd | Method and system for executing a containerized stateful application on a stateless computing platform using machine learning |
US10491964B2 (en) * | 2017-01-23 | 2019-11-26 | Cisco Technology, Inc. | Assisted acceleration for video streaming clients |
WO2019043687A2 (en) | 2017-08-28 | 2019-03-07 | Luminati Networks Ltd. | System and method for improving content fetching by selecting tunnel devices |
US10785511B1 (en) * | 2017-11-14 | 2020-09-22 | Amazon Technologies, Inc. | Catch-up pacing for video streaming |
US10585745B2 (en) * | 2017-11-28 | 2020-03-10 | International Business Machines Corporation | Prevention of application container failure between replicated containers |
US20200099961A1 (en) * | 2018-09-24 | 2020-03-26 | Dice Corporation | Networked video management system |
EP4236263A3 (en) | 2019-02-25 | 2023-09-06 | Bright Data Ltd. | System and method for url fetching retry mechanism |
-
2019
- 2019-08-16 US US16/542,693 patent/US20200099961A1/en active Pending
- 2019-09-20 US US16/576,919 patent/US11363313B2/en active Active
- 2019-09-23 US US16/578,552 patent/US11496779B2/en active Active
Cited By (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US11363313B2 (en) * | 2018-09-24 | 2022-06-14 | Dice Corporation | Networked video management and recording system |
US11496779B2 (en) | 2018-09-24 | 2022-11-08 | Dice Corporation | Gateway for networked video management system |
US11777790B2 (en) * | 2020-04-16 | 2023-10-03 | Ribbon Communications Operating Company, Inc. | Communications methods and apparatus for migrating a network interface and/or IP address from one Pod to another Pod in a Kubernetes system |
US11595350B2 (en) * | 2020-05-08 | 2023-02-28 | Ribbon Communications Operating Company, Inc. | Networking as a service |
US20230239269A1 (en) * | 2020-05-08 | 2023-07-27 | Ribbon Communications Operating Company, Inc. | Networking as a Service |
US11652890B1 (en) * | 2022-07-13 | 2023-05-16 | Oxylabs, Uab | Methods and systems to maintain multiple persistent channels between proxy servers |
Also Published As
Publication number | Publication date |
---|---|
US11496779B2 (en) | 2022-11-08 |
US20200099849A1 (en) | 2020-03-26 |
US20200099727A1 (en) | 2020-03-26 |
US11363313B2 (en) | 2022-06-14 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US11363313B2 (en) | Networked video management and recording system | |
US9838753B2 (en) | Monitoring individual viewing of television events using tracking pixels and cookies | |
US20180048944A1 (en) | Monitoring Individual Viewing of Television Events Using Tracking Pixels and Cookies | |
US10491936B2 (en) | Sharing video in a cloud video service | |
US10645459B2 (en) | Devices, systems, and methods for remote video retrieval | |
CN113923518A (en) | Tracking pixels and COOKIE for television event viewing | |
JP2017509204A (en) | Storage management of data streamed from video source devices | |
CN104639905B (en) | A kind of wireless video monitoring method thereof suitable in iOS system live broadcast of mobile terminal | |
HUE034498T2 (en) | Reception device, reception method, transmission device, and transmission method | |
US10516856B2 (en) | Network video recorder cluster and method of operation | |
CN102843442A (en) | Method for configuring networked cameras | |
US20230224487A1 (en) | Transmission device, communication system, transmission method, and computer program product | |
US20210400114A1 (en) | Methods and apparatus for census and panel matching using http headers | |
KR101562297B1 (en) | Image streaming system for minimizing use of resource for one or more Network Video Recoder | |
US20140002645A1 (en) | Server and video surveillance method of target place | |
JP2017509193A (en) | Providing information about objects in digital video sequences | |
CN114173087A (en) | Video data acquisition and processing method, edge gateway and storage medium | |
US11463651B2 (en) | Video frame-based media stream bandwidth reduction | |
CN108632644B (en) | Preview display method and device | |
KR100792240B1 (en) | Multi vision materialization method and system for the same | |
CN109587141B (en) | System and method for obtaining evidence by remote server | |
TWI731579B (en) | Transmission device, communication system, transmission method, and computer program product | |
US10728438B1 (en) | Distributed video and network camera management | |
US11495102B2 (en) | Devices, systems, and methods for remote video retrieval | |
JP2022125359A (en) | Transmission device, server device, transmission method, and program |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: DICE CORPORATION, MICHIGAN Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:DICE, CLIFFORD;CORRION, GERALD;SIGNING DATES FROM 20190815 TO 20190816;REEL/FRAME:050074/0515 |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: NON FINAL ACTION MAILED |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: RESPONSE TO NON-FINAL OFFICE ACTION ENTERED AND FORWARDED TO EXAMINER |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: FINAL REJECTION MAILED |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: DOCKETED NEW CASE - READY FOR EXAMINATION |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: NON FINAL ACTION MAILED |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: RESPONSE TO NON-FINAL OFFICE ACTION ENTERED AND FORWARDED TO EXAMINER |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: FINAL REJECTION MAILED |
|
STCV | Information on status: appeal procedure |
Free format text: NOTICE OF APPEAL FILED |
|
STCV | Information on status: appeal procedure |
Free format text: APPEAL BRIEF (OR SUPPLEMENTAL BRIEF) ENTERED AND FORWARDED TO EXAMINER |
|
STCV | Information on status: appeal procedure |
Free format text: EXAMINER'S ANSWER TO APPEAL BRIEF MAILED |