WO2014169828A1 - 一种监控视频播放的方法及设备、系统 - Google Patents

一种监控视频播放的方法及设备、系统 Download PDF

Info

Publication number
WO2014169828A1
WO2014169828A1 PCT/CN2014/075576 CN2014075576W WO2014169828A1 WO 2014169828 A1 WO2014169828 A1 WO 2014169828A1 CN 2014075576 W CN2014075576 W CN 2014075576W WO 2014169828 A1 WO2014169828 A1 WO 2014169828A1
Authority
WO
WIPO (PCT)
Prior art keywords
data
video
client device
link address
module
Prior art date
Application number
PCT/CN2014/075576
Other languages
English (en)
French (fr)
Inventor
王峰
宋立岩
Original Assignee
华为技术有限公司
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to EP14785139.8A priority Critical patent/EP2958321A4/en
Publication of WO2014169828A1 publication Critical patent/WO2014169828A1/zh
Priority to US14/880,515 priority patent/US9843775B2/en

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N7/00—Television systems
    • H04N7/16—Analogue secrecy systems; Analogue subscription systems
    • H04N7/173—Analogue secrecy systems; Analogue subscription systems with two-way working, e.g. subscriber sending a programme selection signal
    • H04N7/17309—Transmission or handling of upstream communications
    • H04N7/17318—Direct or substantially direct transmission and handling of requests
    • 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/236—Assembling of a multiplex stream, e.g. transport stream, by combining a video stream with other content or additional data, e.g. inserting a URL [Uniform Resource Locator] into a video stream, multiplexing software data into a video stream; Remultiplexing of multiplex streams; Insertion of stuffing bits into the multiplex stream, e.g. to obtain a constant bit-rate; Assembling of a packetised elementary stream
    • H04N21/2365—Multiplexing of several video streams
    • 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/238—Interfacing the downstream path of the transmission network, e.g. adapting the transmission rate of a video stream to network bandwidth; Processing of multiplex streams
    • H04N21/2387—Stream processing in response to a playback request from an end-user, e.g. for trick-play
    • 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/40—Client devices specifically adapted for the reception of or interaction with content, e.g. set-top-box [STB]; Operations thereof
    • H04N21/47—End-user applications
    • H04N21/472—End-user interface for requesting content, additional data or services; End-user interface for interacting with content, e.g. for content reservation or setting reminders, for requesting event notification, for manipulating displayed content
    • H04N21/47202—End-user interface for requesting content, additional data or services; End-user interface for interacting with content, e.g. for content reservation or setting reminders, for requesting event notification, for manipulating displayed content for requesting content on demand, e.g. video on demand
    • 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/47—End-user applications
    • H04N21/472—End-user interface for requesting content, additional data or services; End-user interface for interacting with content, e.g. for content reservation or setting reminders, for requesting event notification, for manipulating displayed content
    • H04N21/47217—End-user interface for requesting content, additional data or services; End-user interface for interacting with content, e.g. for content reservation or setting reminders, for requesting event notification, for manipulating displayed content for controlling playback functions for recorded or on-demand content, e.g. using progress bars, mode or play-point indicators or bookmarks
    • 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/633—Control signals issued by server directed to the network components or client
    • H04N21/6332—Control signals issued by server directed to the network components or client directed to client
    • H04N21/6334—Control signals issued by server directed to the network components or client directed to client for authorisation, e.g. by transmitting a key
    • 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/643—Communication protocols
    • H04N21/6437—Real-time Transport Protocol [RTP]
    • 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/80—Generation or processing of content or additional data by content creator independently of the distribution process; Content per se
    • H04N21/81—Monomedia components thereof
    • H04N21/8126—Monomedia components thereof involving additional data, e.g. news, sports, stocks, weather forecasts
    • H04N21/8133—Monomedia components thereof involving additional data, e.g. news, sports, stocks, weather forecasts specifically related to the content, e.g. biography of the actors in a movie, detailed information about an article seen in a video program
    • 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/80—Generation or processing of content or additional data by content creator independently of the distribution process; Content per se
    • H04N21/83—Generation or processing of protective or descriptive data associated with content; Content structuring
    • H04N21/845—Structuring of content, e.g. decomposing content into time segments
    • H04N21/8455—Structuring of content, e.g. decomposing content into time segments involving pointers to the content, e.g. pointers to the I-frames of the video stream
    • 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/80—Generation or processing of content or additional data by content creator independently of the distribution process; Content per se
    • H04N21/85—Assembly of content; Generation of multimedia applications
    • H04N21/858—Linking data to content, e.g. by linking an URL to a video object, by creating a hotspot
    • H04N21/8586—Linking data to content, e.g. by linking an URL to a video object, by creating a hotspot by using a URL
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N9/00—Details of colour television systems
    • H04N9/79—Processing of colour television signals in connection with recording
    • H04N9/87—Regeneration of colour television signals

Definitions

  • the invention relates to a method, device and system for monitoring video playing.
  • the network video surveillance service is a value-added service based on broadband remote image monitoring, transmission, storage and management.
  • the network video surveillance service uses broadband networks to network distributed and independent image collection points to achieve unified monitoring, unified storage, unified management, and resource sharing across geographies and all areas.
  • a data collector can be connected to the front-end device to collect environmental data near the monitoring point.
  • the data collector can be a temperature and humidity collector, a wind speed collector, a noise collector, and the like. These collected data can be used for post-mortem queries and analysis, or directly during monitoring.
  • some monitoring devices superimpose and collect the collected data of the front-end data directly with the video data (ie, the video stream) and display it to the monitoring personnel.
  • the video data ie, the video stream
  • this method of superimposing the source makes it necessary for everyone to see the data, but not everyone needs to view the data, and the monitoring video is not flexible enough.
  • the technical problem to be solved by the present invention is to provide a method, device and system for monitoring video playing, so as to avoid that all people must see the collected data associated with the monitoring video data, and provide a more flexible monitoring video.
  • the method of superimposing the data and the collected data gives the user a better experience.
  • the embodiments of the present application provide a method, a device, and a system for monitoring video playback, which can superimpose and collect video data and video data only when the user has the right to view the collected data, so that the monitoring video playback is more flexible. Avoid everyone having to see the data collected.
  • a method for monitoring video playback including: receiving, by a video surveillance management device, a monitoring video browsing request from a client device, according to the request And the user that sends the monitoring video browsing request is authenticated by the client device; if the user who sends the monitoring video browsing request has the right to view the collected data, sending the first link address to the client device, the first The link address is a video play link address of the real-time streaming protocol carrying the video data and the data set identifier; sending the video data and the collected data to the location according to the data request that is returned by the client device and carrying the first link address
  • the client device is configured to enable the client device to superimpose the video data and the collected data to play.
  • the method before the step of sending video data and collecting data to the client device according to the first link address, the method further includes: The video monitoring management device receives the video data and the collected data transmitted from the front end device.
  • the step of the video monitoring management device receiving the video data and the data collected from the front-end device includes: The video monitoring management device receives video data transmitted from the front-end device through a real-time streaming protocol/real-time transmission protocol, and the collected data is brought in by the real-time transmission protocol header of the video data.
  • the method further includes: if the front-end device is recording, storing the video data and the collected data in different files respectively, and generating a video data index according to a temporal association between the collected data and the video data; An index pointer of the set data; or expanding the set data in an extended field of the video data.
  • the video monitoring management device receives a monitoring video browsing request from a client device, and sends the request by using the client device according to the request
  • the method further includes: if the user who sends the monitoring video browsing request does not view the number of sets Transmitting, according to the permission, the second link address to the client device, where the second link address is a video play link address of a real-time streaming protocol carrying only the video data tag, and carrying the second according to the return of the client device
  • the data request of the link address sends video data to the client device.
  • the second aspect provides a client device, including a request module, a receiving module, a data acquiring module, and a playing module, where: the requesting module is configured to send a monitoring video browsing request to the video monitoring management device;
  • the video monitoring management device determines, according to the monitoring video browsing request, that the user that sends the monitoring video browsing request by using the client device has the right to view the collected data, receiving the first returned by the video monitoring management device a link address, the first link address is a video play link address of a real-time streaming protocol carrying video data and a data set, and outputting the first link address to the data acquisition module;
  • the playing module is configured to: The video data and the collected data are superimposed and played.
  • the client device further includes: a determining module, configured to determine whether a selection instruction of the superimposed data is received, and output a determination result to the playing module
  • the playing module is configured to: after the determining module determines that the selection instruction of the superimposed data is received, superimpose the video data and the collected data to play; or determine that the determining module does not When the selection instruction of the superimposed data is received, the video data is played.
  • the receiving module is configured to: when the video monitoring management device determines, according to the monitoring video browsing request, that the sending, by the client device, The user who monitors the video browsing request does not have the right to view the collected data, and receives the second link address returned by the video monitoring management device, where the second link address is a video play link address of the real-time streaming protocol carrying only the video data tag. And outputting the second link address to the data acquisition module; the data acquisition module is configured to acquire video data from the video monitoring management device according to the second link address, and output the video to the play module Video data; the advertisement module is configured to play the video data.
  • a video monitoring management device including an authentication module and a sending module.
  • the authentication module is configured to receive a monitoring video browsing request from the client device, and perform authentication on the user that sends the monitoring video browsing request by using the client device according to the request, and send the module to the sending module.
  • the sending module is configured to send, when the authentication module obtains the permission to view the collected data by the user who sends the monitoring video browsing request by using the authentication, to send the first to the client device a link address, the first link address is a video play link address of a real-time streaming protocol carrying video data and a data set identifier, and the video is requested according to the data request that the client device returns to carry the first link address
  • Data and collection data are sent to the client device to enable the client device to overlay the video data and the collection data for playback.
  • the device further includes: a data acquiring module, configured to receive the video data and the collected data transmitted from the front end device.
  • the device further includes: a saving module, configured to: when the front end device is recording, the data acquiring module The received video data and the collected data are respectively stored in different files, and according to the temporal association of the collected data and the video data, an index pointer of the collected data is generated while generating the video data index; or The collection data extension received by the data acquisition module is saved together in an extension field of the video data.
  • a saving module configured to: when the front end device is recording, the data acquiring module The received video data and the collected data are respectively stored in different files, and according to the temporal association of the collected data and the video data, an index pointer of the collected data is generated while generating the video data index; or The collection data extension received by the data acquisition module is saved together in an extension field of the video data.
  • a fourth aspect a video surveillance system, comprising the client device of any one of the second aspect and the second aspect, and the third aspect, and the possible implementation manner of any one of the third aspect Video surveillance management device.
  • the present application manages the rights of the client device, and only the user who issues the monitoring video browsing request has the right to view the collected data, and then collects the data and the video data. Play together after stacking together. In this way, it is possible to flexibly control whether or not to play the collected data together according to the authority of the user who issues the monitoring video browsing request, so that the monitoring video is more flexible to play, and the person who does not need to view the collected data has to be seen. Collect data for a better experience.
  • FIG. 1 is a schematic structural diagram of an embodiment of a video monitoring system of the present application.
  • FIG. 2 is a schematic diagram of application of the video monitoring system of the present application
  • 3 is another schematic diagram of application of the video monitoring system of the present application
  • FIG. 4 is a flowchart of an embodiment of a method for monitoring video playback of the present application
  • FIG. 5 is a schematic diagram of an MP4 file package for collecting data in one embodiment of the method for monitoring video playback according to the present application
  • FIG. 6 is a schematic diagram of obtaining data collected in one embodiment of the method for monitoring video playback of the present application
  • FIG. 7 is a flow chart of another embodiment of a method for monitoring video playback of the present application.
  • FIG. 8 is a schematic diagram of RTP packing of data transmission in one embodiment of the method for monitoring video playback according to the present application.
  • FIG. 9 is a schematic diagram of data storage in one embodiment of a method for monitoring video playback according to the present application.
  • FIG. 10 is a schematic diagram of an implementation process of real-time monitoring video playback in one embodiment of the method for monitoring video playback of the present application
  • 11 is a schematic diagram of an implementation process of historical monitoring video playback in one embodiment of the method for monitoring video playback of the present application
  • FIG. 12 is a schematic structural diagram of an embodiment of a client device of the present application.
  • FIG. 13 is a schematic structural diagram of another embodiment of a client device of the present application.
  • FIG. 14 is a schematic structural diagram of an implementation manner of a video monitoring management device of the present application.
  • FIG. 15 is a schematic structural diagram of another embodiment of a video monitoring management device of the present application.
  • 16 is a schematic structural diagram of still another embodiment of a client device of the present application.
  • FIG. 17 is a schematic structural diagram of still another embodiment of a video monitoring management device of the present application.
  • FIG. 1 is a schematic structural diagram of an embodiment of a video surveillance system according to the present application.
  • the video surveillance system of the present embodiment includes a client device 100, a video surveillance management device 200, a front-end device 300, and a buffer 400.
  • the client device 100 is a specific entity device or a virtual device that carries a client function, and mainly implements a function of monitoring personnel to monitor video and collect data.
  • the video monitoring management device 200 communicates with the client device 100 and the front-end device 300 through the network, and mainly implements functions such as monitoring video data and managing data collection, and authority management of client device users.
  • the client device 100 and the video monitoring management device 200 may be separately set according to different application scenarios.
  • the physical device in the video monitoring system can also be integrated into the existing video monitoring device as a function module, for example, integrated on the user terminal device, and simultaneously implement the client device on the user terminal device.
  • the client device 100 can implement the client function in the form of software, and is installed in the user terminal device, possibly through a mobile phone terminal, a personal digital assistant (PDA), a PAD, a personal computer (PC), and monitoring. Central devices, etc. to implement client functions.
  • the loading client device 100 further includes a video decoder, a large screen, a monitoring keyboard, a server and other functional modules to jointly complete the user's monitoring tasks.
  • a video intelligent analysis unit is also needed to complete the intelligent analysis of the video and output the result if necessary.
  • the physical manifestation of the video intelligent analysis unit may be a server or a professional device, or belong to a server belonging to the video surveillance management device 200, or integrated in the front-end device 300, or may be included in the client in software form.
  • the device 100 software is installed on the user terminal device.
  • the client device 100 provides functions such as video monitoring, video query playback, cloud mirror control, alarm notification, and linkage.
  • the video surveillance management device 200 may include the following logical units in one of the functional divisions: a service management unit, a service control unit, an access gateway unit, a media distribution and forwarding unit, a media recording storage playback unit, and a database/disk storage unit.
  • the service management unit is mainly used for video surveillance management device and user management and user rights management;
  • the service control unit is mainly used to process the operation control of the front-end device, including requesting the front-end device video, controlling the front-end device cloud mirror, processing the front-end device alarm, and completing
  • the services such as the recording plan of the front-end device, and the login and logout of the processing user, receive the user request and processing from the client device 100, and notify the user side of the service such as the alarm linkage;
  • the access gateway unit is mainly used to process the front-end device and the client.
  • the function of registering the device and maintaining its online status; the media distribution and forwarding unit is mainly used to process the business function of the video distribution or forwarding to the corresponding destination in the front-end device or the storage; the media recording storage playback unit mainly processes the video on the disk.
  • the function of sending the recording on the disk to the client device 100 through the media distribution and forwarding unit; the database/disk storage unit is mainly a module for saving data, which may be a disk of the server itself, or may be an external storage disk array. .
  • the unit division here is only an example of logical function division. In actual implementation, there may be another multiple division methods. For example, multiple units can be combined with one functional module, and exist in one or more channels. Use separate or dedicated servers to implement their respective functions, or some features can be ignored, or not executed.
  • the front-end device 300 is a video collection device, such as a network video camera or an analog camera and a video encoder.
  • the front-end device 300 mainly performs the collection of video data, and transmits the video data to the video monitoring management device 200 through the network, and The control command transmitted by the video monitoring management device 200 is responded to.
  • the video monitoring management device 200 provides video data for real-time browsing and front-end recording, provides cloud mirror control capability, provides configuration capabilities for front-end parameters, and provides alarm capabilities for front-end devices.
  • the collector 400 is a device for collecting peripheral environment information of the front-end device 300.
  • the collector 400 of the embodiment of the present application may be an independent device connected to the front-end device through an RS232 or RS485 interface, which may be various The collection device, such as but not limited to, a temperature and humidity collector, a wind speed wind collector, a noise collector, and the like.
  • the collector 400 completes the collection of environmental data near the monitoring point to assist in monitoring decisions.
  • the collector 400 of the embodiment of the present application can also be integrated into the front-end device to provide the collection capability in the form of an internal module. For example, some camera devices have their own collection function, which completes the collection of the camera's own temperature.
  • FIG. 2 and FIG. 3 are respectively schematic diagrams of application of the video surveillance system of the present application, wherein the camera 11 is a specific implementation form of the front-end device, wherein the camera 11 includes all types of camera devices, including but It is not limited to ball machines, gun machines, dome machines, and network cameras and analog cameras. If the camera 11 is an analog camera, a video encoder is required, which is not shown in the figure, but it is also included.
  • the camera 11 can be connected to various collectors such as temperature and humidity collectors, wind speed and wind collectors, noise collectors, etc. through RS232 or RS485 interfaces (not shown).
  • the camera 11 can also be a camera device with its own collection function.
  • the network 12 in the figure is used to implement monitoring video and collecting data and the like.
  • Network 12 may include all of today's networks, possibly Internet, local area network, wide area network, storage area network, etc., or a suitable combination thereof.
  • the way to access the network may also be various current access methods, such as wired (network cable or fiber), wireless, wireless including WIFI (such as IEEE 802.11a, IEEE 802. lib, IEEE 802.11g, and / or IEEE 802.11 ⁇ ), GSM (EDGE), WCDMA, CDMA, TD-SCDMA, Bluetooth, LTE or any other suitable access method.
  • WIFI such as IEEE 802.11a, IEEE 802. lib, IEEE 802.11g, and / or IEEE 802.11 ⁇
  • GSM EDGE
  • WCDMA CDMA
  • TD-SCDMA Bluetooth
  • LTE Long Term Evolution
  • any other suitable access method such as Wi-Fi
  • the video monitoring server 13 is used to implement all the functions of the video monitoring management device in the above-described embodiment of FIG. 1, and may include all servers and/or dedicated servers that are possible on the market today.
  • the storage device 14 may be a server own disk or an external storage disk array device. Disk arrays can use storage methods such as NAS and SAN.
  • the client device 100 includes all terminal devices capable of implementing client functions, such as mobile terminals, PDAs, PADs, user PCs, and video surveillance center devices.
  • the video monitoring server 13 and the storage device 14 can be designed into the client device 100 in whole or in part.
  • the video monitoring server 13 and the storage device 14 are all integrated in the client device 100 to form a set of recommended video surveillance.
  • the system carries all the functional modules that implement video surveillance in software form through the hardware devices of the client device 100.
  • FIG. 4 is a flowchart of an embodiment of a method for monitoring video playback according to the present application. The implementation manner is described by using the client device mentioned above.
  • the method for monitoring video playback includes:
  • Step S101 The client device sends a monitoring video browsing request to the video monitoring management device.
  • the monitoring video browsing request is sent to the video monitoring management device, and the request may include the condition information of the video to be viewed.
  • User information may be included, such as a user account, a user identification, and the like. Users can send real-time monitoring video browsing requests or send historical monitoring video browsing requests.
  • the video monitoring management device After receiving the monitoring video browsing request, the video monitoring management device authenticates the requesting user, and determines whether the requesting user has the right to view the data of the collected data corresponding to the requested video data, and the application does not Make a limit.
  • the video monitoring management device determines that the requesting user has the right to view the collected data, according to the user's request condition, if the user requests the historical monitoring video browsing request, the qualified recording index file is found, according to the index file.
  • the pointer address actually finds related video data and collection data, and generates a first link address corresponding to the video data requested by the user and the associated collection data, and the first link address is real time carrying the video data and the data set of the collection data.
  • the video play link address of the streaming protocol, and the first link address may be a real-time streaming protocol uniform resource locator (Real Time Streaming) Protocol Uniform Resource Locator, rtsp url), and returns the first link address to the client device.
  • the client device performs the steps of step S102 and subsequent steps.
  • the video monitoring management device If the user request is a real-time monitoring video browsing request, the video monitoring management device generates a first link address according to the specific requesting front end device, and the first link address also carries the video data and the data set identifier, and sends the first link address To the client device.
  • the second link address is returned to the client device, and the second link address is a video play link address of the real-time streaming protocol carrying only the video data tag, the client The end device performs step S105.
  • Step S102 Receive a first link address returned by the video monitoring management device.
  • the authentication of the video monitoring management device passes, and receives the first link address returned by the video monitoring management device.
  • Step S103 Obtain video data and collection data from the video monitoring management device according to the first link address.
  • the video monitoring management device sends a request for acquiring the video data and the collected data, and the video monitoring management device finds the match according to the first link address.
  • the conditional video index file actually finds relevant video data and collection data according to the pointer address in the index file.
  • the video data and the collected data are sent to the client device, and the client device receives the video data and the collected data.
  • the video monitoring management device obtains the real-time video data of the corresponding front-end device according to the information in the first link address. Collect data and send it to the client device.
  • the client device can download the captured video data and the collected data and save the file format in the local machine.
  • the file format of the download data can be saved in the same file together with the data and the video data, or the data can be saved separately from the video data file in a similar subtitle file.
  • the method of saving together may be to extend the data in an extension field of a video data file format such as MP4, AVI, etc., and associate the time stamp with the video data (as shown in FIG. 5).
  • the method of saving separately can save the collected data in independent binary or text mode, and associate with the video data file by the same file name.
  • Step S104 The video data and the collected data are superimposed and played.
  • the client device decodes the video data, parses the collected data, superimposes the video data and the collected data, and superimposes the transparent subtitles on the video screen (On-Screen) Display, OSD) playback.
  • the client device can decide whether to superimpose the OSD for playback according to whether the user selects data overlay.
  • the implementation manner of the overlay play is: the client device receives the video data and the data collected by the data stream, caches the data stream of the video data, and collects the data stream of the data in the form of metadata (MetaData). Cache.
  • MetaData Metadata
  • the overlay data is to be played, when the video data is decoded and played, according to the timestamp information included in the data, the associated start frame of the video data or the video data in the video file is searched for. While decoding and playing the video, extract the specific data information contained in the data corresponding to the frame, generate corresponding characters, and render the overlay to display the video containing the data of the front end data.
  • the maximum dwell time of the collected data may be set in advance. If the new set data is not received after the maximum dwell time of the collected data, the collected data that has been displayed before the invalid is invalid (ie, Then superimpose the data in the video screen). If new data is received within the preset maximum dwell time, the original data is replaced with new data and superimposed with the current video data.
  • Step S105 Receive a second link address returned by the video monitoring management device, obtain video data from the video monitoring management device according to the second link address, and play the video data;
  • the video monitoring management device When the user who sends the monitoring video browsing request does not have the right to view the collected data, the video monitoring management device returns a second link address, and the second link address is a video playing link address of the real-time streaming protocol carrying only the video data tag, and the second link The address may be an rtsp url, and the video data is acquired from the video surveillance management device according to the second link address and played.
  • the implementation manner of the data collected by the client device to obtain the video data corresponding to the video data by the client device can be implemented by referring to the schematic diagram of FIG. 6 by:
  • the front-end device monitors in real time, and the corresponding video data is transmitted to the video monitoring management device. If the front-end device is recording, the video monitoring management device saves the video data through the video file format;
  • the collection device collects information in real time, and obtains corresponding data, which is transmitted to the front-end device.
  • the data is transmitted to the video monitoring management device, and if the front-end device is recording, the video monitoring management device separately stores the collected data in the form of metadata, and obtains the collected data file;
  • the video monitoring management device establishes an index of the video file and the data file
  • the video monitoring management device finds the video file and the data file index that meet the user condition, and then finds the video data and the collected data to be transmitted to the client device;
  • the client device decodes and superimposes the two information to play in the form of OSD.
  • the client device can also save the video data and the collected data on the local machine, and then need to browse the video again without requesting the video monitoring management device. That is, the superimposed video data and the episode data can be directly decoded locally.
  • the present application manages the rights of the client device, and only the user who sends the request through the client device has the right to view the collected data, and then sends the collected data and the video data to the client.
  • the device, and the video data and the collected data are superimposed and played together when the user selects the overlay play.
  • it is possible to flexibly control whether to send the data corresponding to the video data to the client device according to the user authority that issues the monitoring video browsing request, and determine whether to play the collected data together according to the user's selection, so that the monitoring video is Playback is more flexible, and people who don't need to view the collected data also have to see the data collected to minimize user rights and bring greater security.
  • the video data and the collected data are superimposed and played by the OSD method, so that when the data is not needed or the data is displayed for a certain period of time, the collected information is removed, and the key information in the recorded image is not blocked due to the collected data. A better experience.
  • FIG. 7 and FIG. 7 are flowcharts of another embodiment of a method for monitoring video playback according to the present application.
  • the embodiment is described by the above-mentioned video surveillance management device, and the method for monitoring video playback includes:
  • Step S201 The video monitoring management device receives the monitoring video browsing request from the client device, and performs authentication on the user that sends the monitoring video browsing request through the client device according to the request;
  • the monitoring video browsing request is sent to the video monitoring management device, and the request may include condition information of the video to be viewed, and may also include user information, such as a user account, a user identifier, and the like. Users can send real-time monitoring video browsing requests or send calendars History monitoring video browsing requests.
  • the video monitoring management device After receiving the monitoring video browsing request, the video monitoring management device authenticates the requesting user, and determines whether the requesting user has the right to view the data of the collected data corresponding to the requested video data, and the application does not Make a limit.
  • the authentication passes, and generates a first link address corresponding to the video data requested by the user and the associated collection data, and the first link address is carried.
  • the video play link address of the real-time streaming protocol having the video data and the data set is performed, and the steps S202 and subsequent steps are performed.
  • step S204 is performed.
  • Step S202 Send a first link address to the client device.
  • Step S203 Send the video data and the collected data to the client device according to the data request carrying the first link address returned by the client device, so that the client device can superimpose the video data and the collected data to play;
  • the client device when the client device needs to obtain the video data and the collected data corresponding to the request, the client sends a data request carrying the first link address to the video monitoring management device, and the video monitoring management device receives the request. After the data request, the matching video index file is found according to the first link address, and the related video data and the collected data are actually found according to the pointer address in the index file. Send video data and collection data to the client device.
  • the video monitoring management device acquires the real-time video data and the corresponding set of the front-end device according to the information in the first link address. Data, and sent to the client device.
  • the front-end device is connected to the collector and the video monitoring management device, and the front-end device acquires the collected data from the collector in real time, and transmits the collected data and the video data collected by itself to the video monitoring management device in real time.
  • An implementation manner of the front-end device transmitting the video data and the collected data to the video monitoring management device may be a Real-Time Streaming Protocol (Real-Time Transport Protocol) (RTSP/RTP) transmission.
  • RTSP/RTP Real-Time Transport Protocol
  • the data collected in synchronization with the video data is carried through the transmission channel of the video data, and the extended RTP header is brought in.
  • the incoming mode associates the first I frame of the data and video data at a unified time.
  • the data information is carried in the header of the first RTP packet of the I frame.
  • FIG. 8 At the time of t 2 and t n, there is a group of pictures (GOP), and there is a set period of time at the time of ⁇ and ⁇ , respectively, and the set is collected at the corresponding time. data.
  • the data of the collection period ⁇ is added to the extension field of the header of the first TP packet of the first I frame of the trt ⁇ time of the video data, and is sent to the video monitoring management device. .
  • the content format of the data is encapsulated in the RTP header extension field in a binary format in a key-value manner.
  • the partial definition examples of Key are shown in Table 1 below:
  • the data file is stored in binary mode for all the data records in a video segment.
  • the file name is defined as the camera number of the data collection + the initial collection time, and the suffix is cdata.
  • An example of the save format of a collection of data is shown in Table 2 below:
  • Table 2 Example of the save format of the stripe data 4 bytes set time 1 byte key 4 bytes value 3 bytes padding
  • the other way to implement the video data and data collection to the video surveillance management device is to transmit video data through RTSP/RTP.
  • the video data synchronization data is carried by the Transmission Control Protocol (TCP)/User Datagram Protocol (UDP) message. Based on the TCP/UDP bearer protocol, the data can be used.
  • TCP/UDP bearer protocol the data can be used.
  • the Message Method of the Session Initiation Protocol (SIP) sends the collected data to the video monitoring management device through the message interface.
  • SIP Session Initiation Protocol
  • the video surveillance management device After receiving the data sent by the front-end device, the video surveillance management device parses the data sent by the front-end device. If the front-end device is recording, the collected data and the video data are separately stored and associated. As shown in FIG. 9, when the video file index is created, it is judged according to whether the received data contains data (by whether the RTP header extension field contains the data set), if there is data collection, the video file index A pointer to the data file is created. Associate the collection data file with the video data file.
  • the method of sending the video data and the collected data to the client device may be an independent message mode, such as TCP, UDP, or Hypertext Transfer Protocol (HTTP), SIP, Simple Object Access Protocol (Simple Object Access Protocol). , SOAP), etc., may also be transmitted together with video data, such as RTP-based extension, based on the extension of the Program Stream/Transport Stream (PS/TS).
  • the message content format can be a binary, Extensible Markup Language (XML) format.
  • the data content when the data is transmitted and saved, the data content may be expressed in an XML manner.
  • Step S204 Send a second link address to the client device.
  • the video monitoring management device sends the second link address to the client device, and the second link address is the video playing link address of the real-time streaming protocol carrying only the video data tag.
  • the client device acquires video data from the video monitoring management device according to the second link address and plays the video data.
  • the method for monitoring video playback of the present application is specifically described below in a manner in which the client device interacts with the video surveillance management device.
  • FIG. 10 is a schematic diagram of an implementation process of real-time monitoring video playback, including:
  • the user sends a live (ie, real-time video data and collected data) browsing request to the service control unit of the video monitoring management device through the client device;
  • the service control unit authenticates the user's request, including determining whether the user has the right to view the data. If the authentication is passed, the first link address of the media distribution/storage unit of the video surveillance management device corresponding to the service is generated. The client device, at the same time, notifying the media distribution/storage unit of the authentication result, and returning the second link address of the client device if the authentication fails, wherein the first link address and the second link address are described in detail.
  • the client device where the user is located requests the media distribution/storage unit to request the live according to the first link address or the second link address;
  • the media distribution/storage unit requests the live video from the front camera
  • the set data is sent to the media distribution/storage unit
  • the media distribution/storage unit forwards the video media data carrying the collected data to the client device at the front end, and forwards the video media data only to the client device if the authentication fails;
  • the client device receives, caches, decodes, and renders the data, and determines whether to superimpose the OSD to play according to the superimposed data switch.
  • the superposition manner refer to the description of the foregoing implementation manner;
  • the media distribution/storage unit stores the video media data and the collected data, and generates a recording index file.
  • FIG. 11 is a schematic diagram of the implementation process of the historical monitoring video playback, including:
  • the user sends a video playback request (ie, historical video data and corresponding collection data) to the service control unit of the video monitoring management device through the client device;
  • a video playback request ie, historical video data and corresponding collection data
  • the service control unit authenticates the user's request, including determining whether the user has the right to view the data. If the authentication is passed, the first link address of the media distribution/storage unit of the video surveillance management device corresponding to the service is generated. The client, at the same time, notifying the media distribution/storage unit of the authentication result, and returning the second link address of the client device if the authentication fails;
  • the client device where the user is located requests historical video data and collection data from the media distribution/storage unit according to the first link address or the second link address;
  • the media distribution/storage unit queries the video index file according to the user request, and finds the video data and the collected data according to the location indicated in the index file;
  • the media distribution/storage unit packs and packs the data and video data and sends them to the client device. If the authentication fails, only the video data is sent;
  • the client device receives, caches, decodes, and renders the data, and determines whether to superimpose the OSD to play according to the superimposed data switch.
  • the specific superposition implementation refer to the description of the foregoing embodiment.
  • the downloading and collecting the collected information may be selected and saved to the local machine.
  • the downloaded data is stored in the extension field of the video file encapsulation format MP4, and the timestamp is associated with the video content as shown in FIG. 5.
  • FIG. 12 is a schematic structural diagram of an embodiment of a client device according to the present application.
  • the client device 100 includes a requesting module 21, a receiving module 22, a data acquiring module 23, and a playing module 24, where:
  • the requesting module 21 is configured to send a monitoring video browsing request to the video monitoring management device;
  • the requesting module 21 of the client device sends a monitoring video browsing request to the video monitoring management device, where the request may include condition information of the video to be viewed, and may also include user information, such as a user account. , user ID, and more.
  • the receiving module 22 is configured to: when the video monitoring management device determines, according to the monitoring video browsing request, that the user that sends the monitoring video browsing request by the client device has the right to view the collected data, receives the first link address returned by the video monitoring management device, and And outputting, to the data obtaining module 23, a first link address, where the first link address is a video play link address of a real-time streaming protocol carrying video data and a data set identifier;
  • the authentication of the video monitoring management device passes, the receiving module 22 receives the first link address returned by the video monitoring management device, and outputs the first to the data acquiring module 23. link address.
  • the data obtaining module 23 is configured to acquire video data and collected data from the video monitoring management device according to the first link address, and output the video data and the collected data to the playing module 24;
  • the data acquisition module 23 sends a request for acquiring video data and collecting data to the video monitoring management device according to the first link address returned by the video monitoring management device. If the user requests the historical monitoring video, the video monitoring management device according to the first link address Find the qualified video index file and actually find the relevant video data and collection data according to the pointer address in the index file. The video data and the collected data are transmitted to the client device, and the data acquisition module 23 of the client device receives the video data and the collected data.
  • the video monitoring management device obtains the real-time video data and the corresponding set of the front-end device according to the information in the first link address. Data, and sent to the client device.
  • the playing module 24 is configured to superimpose the video data and the collected data to play.
  • the client device After the client device receives the video data and the collected data for buffering, the video data is decoded by the playing module 24, and the collected data is parsed, and the video data and the collected data are superimposed and rendered. Play on the video screen by overlaying the on-screen display (OSD).
  • OSD on-screen display
  • FIG. 13 is a schematic structural diagram of another embodiment of a client device according to the present application.
  • the client device 100 includes a requesting module 21, a receiving module 22, a data acquiring module 23, a playing module 24, a determining module 25, and a saving module 26. , among them:
  • the requesting module 21 is configured to send a monitoring video browsing request to the video monitoring management device;
  • the user can send a real-time monitoring video browsing request through the request module 21 of the client device or send a historical monitoring video browsing request.
  • the receiving module 22 is configured to: when the video monitoring management device determines, according to the monitoring video browsing request, that the user that sends the monitoring video browsing request by the client device has the right to view the collected data, receives the first link address returned by the video monitoring management device, and The first link address is output to the data acquisition module 23; the receiving module 22 is further configured to receive the second link address returned from the video monitoring management device when the user who sends the monitoring video browsing request does not have the right to view the collected data, the second link The address is the video play link address of the real-time streaming protocol that only carries the video data tag.
  • the data obtaining module 23 is configured to acquire video data and collected data from the video monitoring management device according to the first link address, and output the video data and the collected data to the playing module 24;
  • the data obtaining module 23 is further configured to acquire the video data from the video monitoring management device according to the second link address.
  • the saving module 26 is configured to save the video data and the collected data data received by the data obtaining module 23 in different files, and associate with the same file name; or expand the data collected by the data acquiring module 23 to The extension of the video data is saved together.
  • the saving module 26 can download the acquired video data and collected data and save it in a file format on the local machine.
  • the file format of the download data can be saved in the same file as the data and video data, or the data can be saved separately from the video data file in a similar subtitle file.
  • the method of saving together may be to extend the data in an extension field of a video data file format such as MP4, AVI, etc., and associate the time stamp with the video data (as shown in FIG. 5).
  • Separate saves can save the data in a separate binary or text format, associated with the video data file with the same file name.
  • the saving module 26 is further configured to save the video data returned by the receiving module 22 from the video monitoring management device and save the local data when the requesting user does not view the data permission of the collection. Medium.
  • the playing module 24 is configured to superimpose the video data and the collected data to play.
  • the playing module 24 may decide whether to superimpose the OSD for playing according to whether the user selects data overlay.
  • the determining module 25 is configured to determine whether a selection instruction of the superimposed data is received, and output the determination result to the playing module 24;
  • the playing module 24 When the judging module 25 judges that there is a selection instruction for receiving the superimposed data, the playing module 24 superimposes the video data and the collected data to play in the form of OSD, and when the judging module 25 judges that the selection instruction of the superimposed data is not received, the playing module 24 plays Module 24 only plays video data.
  • the playing module 24 searches for the associated starting frame in the video data according to the timestamp information included in the collected data, and decodes and plays the video data, and extracts the set corresponding to the starting frame. Data, rendered in superimposed and played in OSD mode.
  • the maximum dwell time of the collected data may be set in advance. If the new set data is not received after the maximum dwell time of the collected data, the set data that is displayed until the play module 24 is invalid is displayed. (ie, the data is no longer superimposed on the video screen). If a new collection data is received within the preset maximum dwell time, the playback module 24 replaces the original collection data with the new collection data and superimposes it with the current video data.
  • the playing module 24 is used to play the video data.
  • FIG. 14 is a schematic structural diagram of an embodiment of a video surveillance management device according to the present application.
  • the video surveillance management device 200 includes an authentication module 31 and a sending module 32, where:
  • the authentication module 31 is configured to receive a monitoring video browsing request from the client device, perform authentication on the user that sends a monitoring video browsing request through the client device, and output an authentication result to the sending module 32.
  • the video surveillance management device When a user needs to view the surveillance video, the video surveillance management device sends a monitoring video browsing request, and the request may include condition information of the video to be viewed, and may also include user information, such as a user account, a user identifier, and the like. Users can send real-time monitoring video browsing requests or send historical monitoring video browsing requests.
  • the authentication module 31 of the video monitoring management device After receiving the monitoring video browsing request, the authentication module 31 of the video monitoring management device authenticates the requesting user, and determines whether the requesting user has the view corresponding to the requested video data. The right to set data.
  • the authentication module 31 can authenticate the user by using a preset user rights policy or other methods, which is not limited in this application.
  • the authentication module 31 determines that the requesting user has the right to view the collected data, the authentication passes, generates a first link address corresponding to the video data requested by the user and the associated collection data, and outputs the first link address to the sending module 32, if The authentication module 31 determines that the requesting user does not have permission to view the collected data, generates a second link address corresponding to the user request, and outputs the second link address to the sending module 32, so that the sending module sends the second link address to the client device.
  • the sending module 32 is configured to send, by the authentication module 31, the first link address to the client device when the user who sends the monitoring video browsing request has the right to view the collected data, and the first one is returned according to the return of the client device.
  • the data request of the link address sends the video data and the collected data to the client device, so that the client device can superimpose the video data and the collected data to play.
  • the sending module 32 sends the generated first user address of the video data corresponding to the user request and the associated data to the client device, so that the client device can A link address requests corresponding video data and collection data from the video surveillance management device.
  • the sending module 32 finds the qualified recording index file according to the first link address, according to the pointer address in the index file. Find relevant video data and collection data. Send video data and collection data to the client device.
  • the sending module 32 obtains the real-time video data and the collected data of the corresponding front-end device according to the information in the first link address. And sent to the client device.
  • the sending module 32 can send the video data and the collected data to the client device in an independent message manner, such as TCP, UDP, or HTTP, SIP, SOAP, etc., or can be transmitted together with the video data, such as based on RTP. Extension, based on PS/TS extensions.
  • the message content format can be binary or XML format.
  • FIG. 14 is a schematic structural diagram of another embodiment of a video surveillance management device according to the present application.
  • the video surveillance management device includes an authentication module 31, a sending module 32, a data obtaining module 33, and a saving module 34, where:
  • the authentication module 31 is configured to receive a monitoring video browsing request from the client device, perform authentication on the user that sends a monitoring video browsing request through the client device, and output an authentication result to the sending module 32.
  • the sending module 32 is configured to send, by the authentication module, the first link address to the client device when the user who sends the monitoring video browsing request by the authentication device has the right to view the collected data, and carries the first link according to the return of the client device.
  • the data request of the address sends the video data and the collected data to the client device, so that the client device can superimpose the video data and the collected data to play.
  • the video monitoring management device is connected to the front-end device and the collector, and the front-end device acquires the collected data from the collector in real time, and transmits the collected data and the collected video data to the video monitoring management device in real time.
  • the video monitoring management device receives the video data and the collected data transmitted from the front end device through the data acquisition module 33.
  • the data acquisition module 33 receives the video data and the collected data transmitted from the front end device through the RTSP/TP.
  • the saving module 34 saves the video data and the collected data received by the data acquiring module 33 in different files, and generates a video data index according to the time association of the collected data and the video data.
  • the index pointer of the data; or the data set received by the data acquisition module 33 is expanded and saved in the extension field of the video data.
  • the data obtaining module 33 parses and outputs the data to the saving module 34. If the front-end device is recording, the saving module 34 separately stores the collected data and the video data, and establishes an association (see FIG. 9). As shown in the figure), if the video data and the data are transmitted together, when the video file index is created, it is judged according to whether the received data contains the data (by whether the RTP header extension field contains the data) ), if there is data collection, a pointer to the data file is created in the video file index. Associate the collection data file with the video data file.
  • the video surveillance management device of the above embodiment has a module division, which is another division manner different from the functional unit in the embodiment of FIG. 1, and implements the same function as the video surveillance management device in the embodiment of FIG.
  • FIG. 15 is a schematic structural diagram of still another embodiment of a client device according to the present application.
  • the client device 100 includes a processor 41, a receiver 42, a transmitter 43, and a random access memory 44. Read only memory 45 and bus 46.
  • the processor 41 is coupled to the receiver 42, the transmitter 43, the random access memory 44, and the read only memory 45 via a bus 46, respectively.
  • the policy management device needs to be run, the basic input/output system in the read-only memory 45 or the bootloader boot system in the embedded system is booted to boot the client device into a normal running state. After the client device enters a normal operating state, the application and operating system are run in random access memory 44 and cause:
  • the sender 43 sends a monitoring video browsing request to the video monitoring management device, and the request may be a real-time monitoring video browsing request or a historical monitoring video browsing request.
  • the receiver 42 authenticates the requesting user in the video monitoring management device, and receives the first link address returned from the video monitoring management device when the requesting user has the right to view the collected data, and the first link address is carried.
  • the video data and the video play link address of the real-time streaming protocol of the data tag are collected; the transmitter 43 sends a data request to the video monitoring management device according to the first link address, and the receiver 42 further receives the content of the user response request returned by the video monitoring management device.
  • Video data and collection data are collected.
  • the receiver 42 receives the second link address returned from the video monitoring management device, and the second link address is a video play link address of the real-time streaming protocol carrying only the video data;
  • the device 43 sends a data request to the video monitoring management device according to the second link address, and the receiver 42 further manages the video data according to the user request condition returned by the video monitoring management device.
  • the processor 41 is configured to superimpose the video data and the collected data in an OSD format. For a user who has the right to view the data collection, the processor 41 can decide whether to superimpose the data playback according to whether the user selects an instruction to superimpose the data. This avoids users who have permission to view the data but do not need to view it. They also have to see the aggregated data, which minimizes user rights and provides greater security.
  • the processor 41 further plays only the video data returned by the video surveillance management device when the requesting user does not have permission to view the collected data.
  • the processor 41 may be a central processing unit CPU, or an application specific integrated circuit (ASIC), or one or more integrated circuits configured to implement the embodiments of the present application.
  • CPU central processing unit
  • ASIC application specific integrated circuit
  • FIG. 17 is a schematic structural diagram of still another embodiment of a video monitoring management device according to the present application.
  • the video monitoring management device 200 includes a processor 51, a receiver 52, a transmitter 53, and a random memory.
  • a memory 54, a read only memory 55, a bus 56, and a network interface unit 57 are taken.
  • the processor 51 is coupled to the receiver 52, the transmitter 53, the random access memory 54, the read only memory 55, and the network interface unit 57 via a bus 56.
  • the network traffic processing device needs to be run, the basic traffic input system in the read-only memory 55 or the bootloader booting system in the embedded system is booted to boot the network traffic processing device into a normal running state.
  • the application and operating system are run in the random access memory 54, receiving data from the network or transmitting data to the network, such that:
  • Receiver 52 receives a monitored video browsing request from the client device
  • the processor 51 authenticates the requesting user according to its own rights management policy or another manner, and generates video data and associated ⁇ corresponding to the user request when the requesting user has the right to view the collected data.
  • the first link address of the data is sent to the client device by the sender 53, and the first link address is a video play link address of the real-time streaming protocol carrying the video data and the collected data tag;
  • the client device sends a data request carrying the first link address
  • the video data and the collected data are searched according to the first link address, and the video data is collected by the transmitter 53.
  • the data is sent to the client device.
  • the client device requests data through the first link address
  • the real-time video data and the collected data of the corresponding front-end device are obtained according to the information in the first link address, and
  • the transmitter 53 transmits the video data and the collected data to the client device.
  • the processor 51 generates a second link address corresponding to the video data that meets the user request condition when the user who issued the request by the authentication does not have the right to view the collected data, and sends the second link address corresponding to the video data of the user to the client device, and the second link address is sent by the transmitter 53.
  • a video play link address for a live streaming protocol that only carries video data tags.
  • the video data is obtained according to the second link address, and the video data is sent to the client device by the transmitter 53.
  • the processor 51 may be a central processing unit CPU, or an application specific integrated circuit (ASIC), or one or more integrated circuits configured to implement the embodiments of the present application.
  • CPU central processing unit
  • ASIC application specific integrated circuit
  • the present application further provides a video.
  • the monitoring system includes the client device 100 and the video monitoring management device 200, wherein the communication between the client device 100 and the video monitoring management device 200 is implemented.
  • FIG. 1 for related description, the client device 100 and the video monitoring management device 200.
  • FIG. 12-17 For the specific function implementation, refer to the corresponding description of the implementation mode in Figure 12-17, and details are not described again.
  • the video data and the collected data are superimposed and played by the OSD method, so that when the data is not needed or the data is displayed for a certain period of time, the collected information is removed, and the key information in the recorded image is not blocked due to the collected data. A better experience.
  • the disclosed systems, devices, and methods may be implemented in other ways.
  • the device implementations described above are merely illustrative.
  • the division of the modules or units is only a logical function division.
  • there may be another division manner for example, multiple units or components may be used. Combined or can be integrated into another system, or some features can be ignored, or not executed.
  • the mutual coupling or direct connection or communication connection shown or discussed may be an indirect connection or communication connection through some interface, device or unit, and may be in electrical, mechanical or other form.
  • the components displayed by the unit may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the objectives of the embodiments of the present embodiment.
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
  • the above integrated unit can be implemented in the form of hardware or in the form of a software functional unit.
  • the integrated unit, if implemented in the form of a software functional unit and sold or used as a standalone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application, in essence or the contribution to the prior art, or all or part of the technical solution may be embodied in the form of a software product stored in a storage medium.
  • the instructions include a plurality of instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) or a processor to perform all or part of the steps of the methods described in various embodiments of the present application.
  • the foregoing storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM, a random access memory), a magnetic disk or an optical disk, and the like.
  • ROM read-only memory
  • RAM random access memory
  • magnetic disk or an optical disk and the like.

Landscapes

  • Engineering & Computer Science (AREA)
  • Multimedia (AREA)
  • Signal Processing (AREA)
  • Databases & Information Systems (AREA)
  • Human Computer Interaction (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Computer Security & Cryptography (AREA)
  • Two-Way Televisions, Distribution Of Moving Picture Or The Like (AREA)
  • Closed-Circuit Television Systems (AREA)

Abstract

本发明公开了一种监控视频播放的方法及设备、系统。监控视频播放的方法包括：视频监控管理设备接收来自客户端设备的监控视频浏览请求，根据请求对通过客户端设备发出监控视频浏览请求的用户进行鉴权；若发出监控视频浏览请求的用户有查看采集数据的权限，向客户端设备发送对应用户请求的第一链接地址；根据客户端设备返回的携带第一链接地址的数据请求，将视频数据和采集数据发送给客户端设备，以使客户端设备能够将视频数据与所述采集数据叠加后播放。通过上述方式，本发明能够只在用户有查看采集数据权限时才将采集数据与视频数据叠加播放，使监控视频播放更加灵活，避免所有人不得不看到采集数据的问题。

Description

一种监控视频播放的方法及设备、 系统 本申请要求于 2013 年 4 月 17 日提交中国专利局、 申请号为 201310134227.0、 发明名称为"一种监控视频播放的方法及设备、 系统" 的中国专利申请的优先权， 其全部内容通过引用结合在本申请中。
技术领域
本发明涉及一种监控视频播放的方法及设备、 系统。
背景技术
网络视频监控业务是基于宽带的远程图像监控、 传输、 存储、 管理 的增值业务。 网络视频监控业务利用宽带网络将分散、 独立的图像釆集 点进行联网， 实现跨地域、 全范围内的统一监控、 统一存储、 统一管理、 资源共享。
为进一步辅助做监控决策， 可以在前端设备处连接数据釆集器， 用 于釆集监控点附近的环境数据。 数据釆集器可以是温度湿度釆集器、 风 向风速釆集器、 噪声釆集器等等。 这些釆集到的数据可以用来做事后的 查询和分析， 也可能直接在监控期间就调用。
一些监控设备在用户调用监控视频时， 将前端釆集的釆集数据直接 在源头编码时就与视频数据（即视频流）叠加并展示给监控人员。但是这种 釆用源头叠加的方式， 让所有人都必须看到这些数据， 但是并不是所有 人都需要查看釆集数据， 监控视频的播放方式不够灵活。
发明内容
本发明主要解决的技术问题是提供一种监控视频播放的方法及设 备、 系统， 用以避免所有人都必须看到跟监控视频数据相关联的釆集数 据， 提供一种更为灵活的监控视频数据和釆集数据叠加播放的方法， 给 用户更好的体验。
有鉴于此， 本申请实施方式提供一种监控视频播放的方法及设备、 系统， 能够只在用户有查看釆集数据权限时才将釆集数据与视频数据叠 加播放， 使监控视频播放更加灵活， 避免所有人不得不看到釆集数据。
第一方面， 提供一种监控视频播放的方法， 包括： 视频监控管理设 备接收来自客户端设备的监控视频浏览请求， 根据所述请求对通过所述 客户端设备发出所述监控视频浏览请求的用户进行鉴权； 若发出所述监 控视频浏览请求的用户有查看釆集数据的权限， 向所述客户端设备发送 第一链接地址， 所述第一链接地址为携带视频数据和釆集数据标记的实 时流协议的视频播放链接地址； 根据所述客户端设备返回的携带所述第 一链接地址的数据请求， 将视频数据和釆集数据发送给所述客户端设备， 以使所述客户端设备能够将所述视频数据与所述釆集数据叠加后播放。
结合第一方面， 在第一方面的第一种可能的实现方式中： 所述根据 所述第一链接地址向所述客户端设备发送视频数据和釆集数据的步骤之 前， 还包括： 所述视频监控管理设备接收从前端设备传输过来的视频数 据和釆集数据。
结合第一方面的第一种可能的实现方式， 在第一方面的第二种可能 的实现方式中： 所述视频监控管理设备接收从前端设备传输过来的视频 数据和釆集数据的步骤包括： 所述视频监控管理设备接收从前端设备通 过实时流传输协议 /实时传送协议传输过来的视频数据， 所述釆集数据由 所述视频数据的实时传送协议头一并带入。
结合第一方面的第一种可能的实现方式， 在第一方面的第三种可能 的实现方式中： 所述视频监控管理设备接收从前端设备传输过来的视频 数据和釆集数据的步骤之后， 还包括： 若前端设备正在录像， 将所述视 频数据与所述釆集数据分别保存在不同文件中， 根据所述釆集数据和所 述视频数据的时间关联， 生成视频数据索引的同时增加釆集数据的索引 指针； 或将所述釆集数据扩展在所述视频数据的扩展字段中一并保存。
结合第一方面， 在第一方面的第四种可能的实现方式中： 根据所述 第一链接地址， 将视频数据和釆集数据发送给所述客户端设备的步骤包 括： 根据所述第一链接地址， 将所述视频数据和所述釆集数据分别传输 给所述客户端设备； 或将所述视频数据和所述釆集数据合并后一起发送 给所述客户端设备。
结合第一方面， 在第一方面的第五种可能的实现方式中： 所述视频 监控管理设备接收来自客户端设备的监控视频浏览请求， 根据所述请求 对通过所述客户端设备发出所述监控视频浏览请求的用户进行鉴权的步 骤之后， 还包括： 若发出所述监控视频浏览请求的用户没有查看釆集数 据的权限， 向所述客户端设备发送第二链接地址， 所述第二链接地址为 只携带视频数据标记的实时流协议的视频播放链接地址， 并根据客户端 设备返回的携带所述第二链接地址的数据请求向所述客户端设备发送视 频数据。
第二方面， 提供一种客户端设备， 包括请求模块、 接收模块、 数据 获取模块以及播放模块， 其中： 所述请求模块用于向视频监控管理设备 发出监控视频浏览请求； 所述接收模块用于在所述视频监控管理设备根 据所述监控视频浏览请求判断到通过所述客户端设备发出所述监控视频 浏览请求的用户有查看釆集数据的权限时， 接收所述视频监控管理设备 返回的第一链接地址， 所述第一链接地址为携带视频数据和釆集数据标 记的实时流协议的视频播放链接地址， 并向所述数据获取模块输出所述 第一链接地址； 所述数据获取模块用于根据所述第一链接地址从所述视 频监控管理设备获取视频数据和釆集数据， 并向所述播放模块输出所述 视频数据和所述釆集数据； 所述播放模块用于将所述视频数据和所述釆 集数据叠加后播放。
结合第二方面， 在第二方面的第一种可能的实现方式中： 所述客户 端设备还包括判断模块， 用于判断是否接收到叠加数据的选择指令， 并 向所述播放模块输出判断结果； 所述播放模块用于在所述判断模块判断 到有接收到所述叠加数据的选择指令时， 将所述视频数据和所述釆集数 据叠加后播放； 或在所述判断模块判断到没有接收到所述叠加数据的选 择指令时， 将所述视频数据播放。
结合第三方面， 在第二方面的第二种可能的实现方式中： 所述接收 模块用于在所述视频监控管理设备根据所述监控视频浏览请求判断到通 过所述客户端设备发出所述监控视频浏览请求的用户没有查看釆集数据 的权限时， 接收所述视频监控管理设备返回的第二链接地址， 所述第二 链接地址为只携带视频数据标记的实时流协议的视频播放链接地址， 并 向所述数据获取模块输出所述第二链接地址； 所述数据获取模块用于根 据所述第二链接地址从所述视频监控管理设备获取视频数据， 并向所述 播放模块输出所述视频数据； 所述播发模块用于播放所述视频数据。
第三方面， 提供一种视频监控管理设备， 包括鉴权模块和发送模块， 其中： 所述鉴权模块用于接收来自客户端设备的监控视频浏览请求， 根 据所述请求对通过所述客户端设备发出所述监控视频浏览请求的用户进 行鉴权， 并向所述发送模块输出所述鉴权结果； 所述发送模块用于在所 述鉴权模块通过鉴权得到发出所述监控视频浏览请求的用户有查看釆集 数据的权限时， 向所述客户端设备发送第一链接地址， 所述第一链接地 址为携带视频数据和釆集数据标识的实时流协议的视频播放链接地址， 并根据所述客户端设备返回的携带所述第一链接地址的数据请求， 将视 频数据和釆集数据发送给所述客户端设备， 以使所述客户端设备能够将 所述视频数据与所述釆集数据叠加后播放。
结合第三方面， 在第三方面的第一种可能的实现方式中： 所述设备 还包括数据获取模块， 用于接收从前端设备传输过来的视频数据和釆集 数据。
结合第三方面的第一种可能的实现方式， 在第三方面的第二种可能 的实现方式中： 所述设备还包括保存模块， 用于在前端设备正在录像时， 将所述数据获取模块接收的所述视频数据与所述釆集数据分别保存在不 同文件中， 根据所述釆集数据和所述视频数据的时间关联， 生成视频数 据索引的同时增加釆集数据的索引指针； 或将所述数据获取模块接收的 所述釆集数据扩展在所述视频数据的扩展字段中一并保存。
第四方面， 提供一种视频监控系统， 包括第二方面以及第二方面的 任一种可能的实施方式所述的客户端设备以及第三方面以及第三方面任 一种可能的实现方式所述的视频监控管理设备。
本发明的有益效果是： 区别于现有技术的情况， 本申请通过对客户 端设备的权限进行管理， 只有发出监控视频浏览请求的用户具有查看釆 集数据权限时才将釆集数据和视频数据一起叠加后播放。 通过这种方式， 能够灵活的根据发出监控视频浏览请求的用户的权限， 控制是否一同播 放釆集数据， 使监控视频的播放更加灵活， 避免不需要查看釆集数据的 人也不得不看到釆集数据， 带来更好的体验效果。
附图说明
图 1是本申请视频监控系统一个实施方式的结构示意图；
图 2是本申请视频监控系统的应用示意图； 图 3是本申请视频监控系统的另一个应用示意图；
图 4是本申请监控视频播放的方法一个实施方式的流程图；
图 5是本申请监控视频播放的方法其中一个实施方式中釆集数据的 MP4 文件封装示意图；
图 6是本申请监控视频播放的方法其中一个实施方式中釆集数据的获取示 意图；
图 7是本申请监控视频播放的方法另一个实施方式的流程图；
图 8是本申请监控视频播放的方法其中一个实施方式中釆集数据传输的 RTP打包示意图；
图 9是本申请监控视频播放的方法其中一个实施方式中釆集数据存储示意 图；
图 10是本申请监控视频播放的方法其中一个实施方式中实时监控视频播 放的实现过程示意图；
图 11是本申请监控视频播放的方法其中一个实施方式中历史监控视频播 放的实现过程示意图；
图 12是本申请客户端设备一个实施方式的结构示意图；
图 13是本申请客户端设备另一个实施方式的结构示意图；
图 14是本申请视频监控管理设备一个实施方式的结构示意图；
图 15是本申请视频监控管理设备另一个实施方式的结构示意图；
图 16是本申请客户端设备又一个实施方式的结构示意图；
图 17是本申请视频监控管理设备又一个实施方式的结构示意图。
具体实施方式
参阅图 1， 图 1为本申请视频监控系统一个实施方式的结构示意图， 本实 施方式视频监控系统包括客户端设备 100、 视频监控管理设备 200、 前端设备 300以及釆集器 400。 其中， 客户端设备 100是承载客户端功能的具体实体设 备或虚拟设备， 主要实现监控人员查看监控视频以及釆集数据功能。视频监控 管理设备 200通过网络与客户端设备 100以及前端设备 300实现通信，主要实 现监控视频数据以及釆集数据的管理、客户端设备用户的权限管理等功能。根 据应用场景的不同，客户端设备 100和视频监控管理设备 200可以是单独设置 于视频监控系统中的实体设备，也可以作为一个功能模块集成于现有视频监控 设备中， 比如集成在用户终端设备上， 在用户终端设备上同时实现客户端设备
100以及视频监控管理设备 200的功能。
比如客户端设备 100可以以软件形式来实现客户端功能，安装于用户终端 设备内，可能是通过手机终端、掌上电脑 (Personal Digital Assistant, PDA), PAD, 个人计算机 (personal computer, PC), 监控中心设备等来实现客户端功能。 承 载客户端设备 100还包括视频解码器、 大屏、 监控键盘、 服务器等功能模块， 共同完成用户的监控任务。本申请实施方式中， 为实现更好地输出视频监控的 结果， 必要时还需要设置视频智能分析单元， 用来完成对视频的智能分析并输 出结果的工作。视频智能分析单元的物理表现形态可以是一台服务器或一台专 业设备， 或与视频监控管理设备 200同属一台服务器中， 或者集成在前端设备 300中， 亦或是以软件形态包含于客户端设备 100软件中安装在用户终端设备 上。 客户端设备 100提供用户一般的视频监控、 录像查询回放、 云镜控制、 告 警通知与联动等功能。
视频监控管理设备 200 按功能的其中一种划分方式可以包括以下逻辑单 元： 业务管理单元、 业务控制单元、 接入网关单元、 媒体分发转发单元、 媒体 录像存储回放单元、 数据库 /磁盘存储单元。
业务管理单元主要用于视频监控管理设备与用户管理以及用户的权限管 理；业务控制单元主要用来处理前端设备的运行控制，包括请求前端设备视频、 控制前端设备云镜、 处理前端设备告警、 完成前端设备的录像计划等业务， 以 及处理用户的登录注销，接收来自客户端设备 100的用户请求与处理， 将告警 联动通知到用户侧等业务；接入网关单元主要用来处理前端设备与客户端设备 的注册，保持其在线状态等功能； 媒体分发转发单元主要用来处理前端设备或 存储中的视频分发或转发到相应目的地去的业务功能；媒体录像存储回放单元 主要处理将视频存储在磁盘中，或将磁盘中录像通过媒体分发转发单元发送到 客户端设备 100的功能； 数据库 /磁盘存储单元主要是保存数据的模块， 其可 能是服务器本身的磁盘， 也可能是外接的存储磁盘阵列设备。
这里的单元划分只是一种逻辑功能划分举例，实际实现时可以有另外的多 种划分方式， 比如多个单元可以结合集成一个功能模块， 存在于一台或多台通 用或专用服务器中来实现各自的功能， 或一些特征可以忽略， 或不执行。
前端设备 300为视频釆集设备，比如可以是网络视频摄像机或模拟摄像机 和视频编码器， 前端设备 300主要完成视频数据的釆集工作，将视频数据通过 网络传送到视频监控管理设备 200中，并响应视频监控管理设备 200发送的控 制命令。 比如向视频监控管理设备 200提供实时浏览和前端录像的视频数据、 提供云镜控制能力、提供对前端各参数的配置能力、 以及提供前端设备的告警 能力等。
釆集器 400是用于釆集前端设备 300周边环境信息的设备，本申请实施方 式的釆集器 400可以是一个独立的设备， 通过 RS232或 RS485接口连接到前 端设备上， 其可能是各种釆集设备， 比如但不限于是温湿度釆集器、 风速风向 釆集器、 噪声釆集器等等。 釆集器 400完成釆集监控点附近的环境数据， 以辅 助做监控决策。 另一方面， 本申请实施方式的釆集器 400也可以合在前端设备 内， 以内部模块的方式提供釆集能力。 比如一些摄像机设备自带釆集功能， 完 成摄像机本身温度的釆集。
参阅图 2和图 3， 图 2和图 3分别是本申请视频监控系统的应用示意图， 其中，摄像机 11是上述前端设备的一种具体实现形式， 其中摄像机 11包括所 有类型的摄像机设备， 包括但不限于是球机、 枪机、 半球机， 以及网络摄像机 和模拟摄像机。 若摄像机 11为模拟摄像机， 需要接视频编码器， 在图中并未 体现， 但也包含其中。摄像机 11可以通过 RS232或 RS485接口连接各种釆集 器如温湿度釆集器、 风速风向釆集器、 噪声釆集器等等 (图未画出）。 另外， 摄 像机 11也可以是自带釆集功能的摄像机设备。
图中的网络 12用于实现监控视频以及釆集数据等的传输。网络 12可以包 括当今的所有网络， 可能是互联网、 局域网、 广域网、 存储局域网等， 或其适 当的组合。接入网络的方式也可能是当下各种接入方式，如有线（网线或光纤）、 无线， 无线包括 WIFI (例如 IEEE 802.11a、 IEEE 802. lib、 IEEE 802.11g和 / 或 IEEE 802.11η )、 GSM(EDGE), WCDMA、 CDMA, TD-SCDMA、蓝牙、 LTE 或其他任何适合接入方式。
视频监控服务器 13用于实现上述图 1所述实施方式中的视频监控管理设 备的所有功能， 可以包括当今市面上可能的所有服务器和 /或其专用服务器。 存储设备 14可能是服务器自有磁盘或外接的存储磁盘阵列设备。 磁盘阵 列可釆用 NAS、 SAN等存储方式。
客户端设备 100包括一切能够实现客户端功能的终端设备，比如可能包括 手机终端、 PDA、 PAD, 用户 PC和视频监控中心设备等等。
视频监控服务器 13以及存储设备 14可以全部或部分组合设计到客户端设 备 100中，图 3所示为视频监控服务器 13以及存储设备 14全部集成于客户端 设备 100中， 形成一套建议的视频监控系统，通过客户端设备 100的硬件设备 承载所有以软件形式实现视频监控的所有功能模块。
上述的视频监控系统的实施方式，只是本申请对视频监控系统的一个具体 举例说明，在以其他形式实现相同功能的视频监控系统也属于本申请的保护范 围， 在此不——列举说明。
请参阅图 4， 图 4为本申请监控视频播放的方法一个实施方式的流程图， 本实施方式是以上述提到的客户端设备角度来描述， 监控视频播放的方法包 括：
步骤 S101 : 客户端设备向视频监控管理设备发出监控视频浏览请求； 当有用户需要查看监控录像时，向视频监控管理设备发出监控视频浏览请 求， 请求中可以包括需要查看的录像的条件信息， 还可以包括用户信息， 比如 用户账号、用户标识等等。 用户可以发送实时监控视频浏览请求也可以发送历 史监控视频浏览请求。
视频监控管理设备接收到监控视频浏览请求后，对发出请求的用户进行鉴 权，判断发出请求的用户是否有查看跟请求的视频数据相对应的釆集数据的权 鉴权， 本申请对此不做限定。
当视频监控管理设备判断到发出请求的用户有查看釆集数据的权限时，根 据用户的请求条件， 若用户请求是历史监控视频浏览请求， 则找寻到符合条件 的录像索引文件，根据索引文件中的指针地址实际查找到相关的视频数据和釆 集数据， 生成对应用户请求的视频数据和相关联的釆集数据的第一链接地址， 第一链接地址为携带视频数据和釆集数据标记的实时流协议的视频播放链接 地址， 第一链接地址可以是实时流协议统一资源定位符 (Real Time Streaming Protocol Uniform Resource Locator， rtsp url)， 并将第一链接地址返回给客户端 设备。 客户端设备执行步骤 S102及之后的步骤。
若用户请求是实时监控视频浏览请求，则视频监控管理设备根据具体请求 的前端设备生成第一链接地址，该第一链接地址内也携带视频数据和釆集数据 标记， 将该第一链接地址发送给客户端设备。
当视频监控管理设备判断到发出请求的用户没有查看釆集数据的权限，向 客户端设备返回第二链接地址，第二链接地址为只携带视频数据标记的实时流 协议的视频播放链接地址， 客户端设备执行步骤 S 105。
步骤 S102: 接收视频监控管理设备返回的第一链接地址；
当发出监控视频浏览请求的用户有查看釆集数据的权限时，视频监控管理 设备端的鉴权通过， 接收视频监控管理设备返回的第一链接地址。
步骤 S103: 根据第一链接地址从视频监控管理设备获取视频数据和釆集 数据；
若用户请求的是历史监控视频浏览时，根据视频监控管理设备返回的第一 链接地址， 向视频监控管理设备发出获取视频数据和釆集数据的请求，视频监 控管理设备根据第一链接地址找到符合条件的录像索引文件，根据索引文件中 的指针地址实际查找到相关的视频数据和釆集数据。将视频数据和釆集数据发 送给客户端设备， 客户端设备接收视频数据和釆集数据。
若用户请求的是实时监控视频浏览时，当客户端设备通过此第一链接地址 来请求数据时，视频监控管理设备再根据此第一链接地址中的信息去获取对应 前端设备的实时视频数据和釆集数据， 并发送给客户端设备。
作为一种可选的方式，客户端设备可以将获取到的视频数据和釆集数据下 载， 以文件格式保存在本地机器中。 下载数据的文件格式保存可以是釆集数据 和视频数据一并保存在同一个文件中，也可以是将釆集数据以类似字幕文件一 般的与视频数据文件分开保存。一并保存的方式可以是将釆集数据扩展在视频 数据文件格式如 MP4、 AVI等的扩展字段中，以时间戳与视频数据建立关联 (如 图 5所示)。 分开保存的方式可以将釆集数据以独立二进制或文本方式保存， 通过相同的文件名与视频数据文件关联。
步骤 S104: 将视频数据和釆集数据叠加后播放。 客户端设备接收到视频数据和釆集数据进行緩存后， 对视频数据进行解 码，对釆集数据进行解析， 将视频数据和釆集数据叠加渲染后以视频画面叠加 透明字幕的方式 (On-Screen Display, OSD)播放。
作为一种更加优选的方式，客户端设备可以根据用户是否选择数据叠加决 定是否叠加 OSD进行播放。
一种叠加播放的实现方式为：客户端设备接收以数据流的方式传送过来的 视频数据和釆集数据，将视频数据的数据流进行緩存， 釆集数据的数据流以元 数据 (MetaData)形式緩存。 当需要叠加播放时，在对视频数据进行解码播放时， 根据釆集数据中包含的时间戳信息，对应查找到緩存的视频数据或录像文件中 视频数据的关联的起始帧。在解码并播放录像的同时，提取与帧相对应的釆集 数据中包含的具体釆集数据信息， 生成相应的字符， 渲染叠加即可显示包含前 端釆集数据信息的视频。
作为一种优选的方式， 可以预先设置釆集数据的最大停留时间， 若在釆集 数据的最大停留时间之后， 没有接收到新的釆集数据， 则无效之前一直显示的 釆集数据（即不再在视频画面中叠加釆集数据）。 如果在预设的最大停留时间 内，接收到新的釆集数据， 则以新的釆集数据替代原有的釆集数据并与当前视 频数据进行叠加后播放。
步骤 S105: 接收视频监控管理设备返回的第二链接地址， 根据第二链接 地址从视频监控管理设备获取视频数据并播放；
当发出监控视频浏览请求的用户没有查看釆集数据的权限时，视频监控管 理设备返回第二链接地址，第二链接地址为只携带视频数据标记的实时流协议 的视频播放链接地址，第二链接地址可以是 rtsp url,根据第二链接地址从视频 监控管理设备获取视频数据并播放。
其中，有查看釆集数据权限的用户通过客户端设备请求视频数据的同时获 取到与视频数据对应的釆集数据的其中一种实现方式可参阅图 6的示意图，通 过以下方式来实现：
前端设备实时监控，得到相应的视频数据传输给视频监控管理设备， 若前 端设备正在录像， 则视频监控管理设备通过录像文件格式保存视频数据；
釆集设备实时釆集信息， 得到相应的釆集数据， 传输给前端设备， 前端设 备将釆集数据传输给视频监控管理设备， 若前端设备正在录像， 则视频监控管 理设备以元数据形式单独存储釆集数据， 得到釆集数据文件；
视频监控管理设备建立录像文件和釆集数据文件索引；
当用户通过客户端设备向视频监控管理设备发送监控视频浏览请求时，视 频监控管理设备找到符合用户条件的录像文件和釆集数据文件索引，进而找到 视频数据和釆集数据传输给客户端设备；
客户端设备解码叠加两者信息以 OSD形式播放， 另外， 客户端设备也可 以将视频数据和釆集数据下载保存在本地机器上， 以后需要再次浏览该录像 时，无需通过向视频监控管理设备请求即可以直接在本地解码叠加视频数据和 釆集数据播放。
通过上述实施方式的阐述， 可以理解， 本申请通过对客户端设备的权限进 行管理，只有通过客户端设备发送请求的用户具有查看釆集数据权限时才将釆 集数据和视频数据发送给客户端设备，并且在用户选择叠加播放时才将视频数 据和釆集数据一起叠加后播放。通过这种方式， 能够灵活的根据发出监控视频 浏览请求的用户权限， 控制是否向客户端设备发送与视频数据相应的釆集数 据，根据用户的选择决定是否一同播放釆集数据，使监控视频的播放更加灵活， 避免不需要查看釆集数据的人也不得不看到釆集数据， 让用户权限最小化， 带 来更高的安全性。
另外， 通过 OSD方式将视频数据和釆集数据叠加播放， 方便在不需要时 或者釆集数据显示一定时间后去掉釆集信息，不会因釆集数据而遮挡录像画面 中的关键信息， 带来更好的体验效果。
请参阅图 7，图 7为本申请监控视频播放的方法另一个实施方式的流程图， 本实施方式是以上述的视频监控管理设备的角度来描述，监控视频播放的方法 包括：
步骤 S201 : 视频监控管理设备接收来自客户端设备的监控视频浏览请求， 根据请求对通过客户端设备发出监控视频浏览请求的用户进行鉴权；
当有用户需要查看监控视频时，向视频监控管理设备发出监控视频浏览请 求， 请求中可以包括需要查看的录像的条件信息， 还可以包括用户信息， 比如 用户账号、用户标识等等。 用户可以发送实时监控视频浏览请求也可以发送历 史监控视频浏览请求。
视频监控管理设备接收到监控视频浏览请求后，对发出请求的用户进行鉴 权，判断发出请求的用户是否有查看跟请求的视频数据相对应的釆集数据的权 鉴权， 本申请对此不做限定。
当视频监控管理设备判断到发出请求的用户有查看釆集数据的权限，鉴权 通过， 生成对应用户请求的视频数据和相关联的釆集数据的第一链接地址， 该 第一链接地址为携带有视频数据和釆集数据标记的实时流协议的视频播放链 接地址， 进行步骤 S202以及之后的步骤。
当视频监控管理设备判断到发出请求的用户没有查看釆集数据的权限，鉴 权没有通过， 执行步骤 S204。
步骤 S202: 向客户端设备发送第一链接地址；
将生成的对应用户请求的视频数据和相关联的釆集数据的第一链接地址 发送给客户端设备，以使客户端设备能够根据该第一链接地址向视频监控管理 设备请求相应的视频数据和釆集数据。
步骤 S203 : 根据客户端设备返回的携带第一链接地址的数据请求， 将视 频数据和釆集数据发送给客户端设备，以使客户端设备能够将视频数据与釆集 数据叠加后播放；
若用户请求的是历史监控视频浏览请求，当客户端设备需要获取请求对应 的视频数据和釆集数据时，向视频监控管理设备发送携带第一链接地址的数据 请求，视频监控管理设备接收到该数据请求后，根据第一链接地址找到符合条 件的录像索引文件，根据索引文件中的指针地址实际查找到相关的视频数据和 釆集数据。 将视频数据和釆集数据发送给客户端设备。
若用户请求的是实时监控视频浏览请求，当客户端设备通过第一链接地址 来请求数据时，视频监控管理设备再根据第一链接地址中的信息去获取对应前 端设备的实时视频数据和釆集数据， 并发送给客户端设备。
本申请实施方式中， 前端设备与釆集器和视频监控管理设备连接， 前端设 备实时从釆集器获取釆集数据，并将釆集数据和自身釆集的视频数据实时传输 给视频监控管理设备。 前端设备将视频数据和釆集数据传输给视频监控管理设备的一种实现方 式可以是通过实时流传输协议 /实时传送协议（Real-Time Streaming Protocol/Real-time Transport Protocol， RTSP/RTP)传输， 与视频数据同步的釆集 数据通过视频数据的传输通道， 扩展 RTP头一并带入。
带入方式釆集数据和视频数据统一时刻的第一个 I帧进行关联。在 I帧的 第一个 RTP分包的包头中携带釆集数据信息。 具体实现可以参阅图 8所示的 示意图， t2、 tn时刻都有一组画面组 (Group of Pictures, GOP)， 在 ^和^时 刻分别有一个釆集周期， 釆集到相应时刻的釆集数据。 在通过 RTP通道传输 时将釆集周期 ^的釆集数据加入到视频数据的 trt^时刻第一个 I帧的第一个 TP分包的头的扩展字段里面， 一并发送给视频监控管理设备。
釆集数据的内容格式釆用二进制格式以键-值 (Key- Value)方式封装在 RTP 头扩展字段中， Key的部分定义示例见下表 1 :
表 1 : Key的部分定义示例
Figure imgf000015_0001
若前端设备正在录像，釆集数据文件以二进制方式保存一段录像片段中的 所有釆集数据记录， 文件名定义为该釆集数据的摄像机编号 +起始釆集时间， 后缀名为 cdata。 一条釆集数据的保存格式示例见下表 2:
表 2: —条釆集数据的保存格式示例 4字节釆集时间 1字节 key 4字节 value 3字节填充符 前端设备将视频数据和釆集数据传输给视频监控管理设备的另一种实现 方式是通过 RTSP/RTP传输视频数据，与视频数据同步的釆集数据则通过传输 控制协议 (Transmission Control Protocol， TCP)/用户数据包协议 (User Datagram Protocol, UDP)的消息方式承载数据， 在 TCP/UDP的承载协议基础上， 可以 釆用信令控制协议 (Session Initiation Protocol, SIP)的 Message方法将釆集数据 通过消息接口发送给视频监控管理设备。
其中， SIP Message消息的消息格式定义示例可参见下表 3:
表 3： SIP Message的消息格式定义示例：
Figure imgf000016_0001
视频监控管理设备接收到前端设备发送过来的数据后，对其进行解析，如 果前端设备正在录像， 则将釆集数据和视频数据分开存储， 并建立关联。 如图 9所示，在创建录像文件索引时，根据收到的数据中是否含釆集数据的判断 (通 过 RTP包头扩展字段是否含釆集数据判断)， 若有釆集数据， 在录像文件索引 中建立釆集数据文件的指针。 将釆集数据文件与视频数据文件建立关联。
将视频数据和釆集数据发送给客户端设备的方式可以是独立的消息方式， 如 TCP、 UDP, 或超文本传输协议 (Hypertext transfer Protocol, HTTP), SIP, 简单对象访问协议 (Simple Object Access Protocol, SOAP)等，也可以是与视频数 据一并传输，如基于 RTP的扩展，基于传输流 /节目流 (Program Stream/Transport Stream,PS/TS)的扩展。消息内容格式可以是二进制、可扩展标记语言 (Extensible Markup Language, XML)格式。
另外， 本申请实施方式中， 釆集数据在传输和保存时， 可以以 XML方式 表述数据内容， XML格式定义的一种示例如下： <xs:complexType name="Collecting_data">
<xs:complexType name=" Cameralnfo " >
<xs: element name="DeviceID" type="xs:int"/>
<xs: element name="Date" type="xs:date"/>
<xs: element name="Time" type="xs:time"/>
</xs:complexType>
<xs:complexType name="CollectingInfo">
<xs: element name="temperature" type="xs:float"/>
<xs: element name="humidity" type="xs:float"/>
<xs: element name="windSpeed" type="xs:float"/>
<xs: element name="windDirection" type="xs:float"/>
</xs:complexType>
</xs:complexType>
步骤 S204: 向客户端设备发送第二链接地址；
当发出监控视频浏览请求的用户没有查看釆集数据的权限时，视频监控管 理设备向客户端设备发送第二链接地址，第二链接地址为只携带视频数据标记 的实时流协议的视频播放链接地址，客户端设备根据第二链接地址从视频监控 管理设备获取到视频数据并播放。
以下以客户端设备与视频监控管理设备交互的方式来具体描述本申请的 监控视频播放的方法。
当用户需要浏览实时监控视频时， 请参阅图 10， 图 10为实时监控视频播 放的实现过程示意图， 包括：
1、 用户通过所在客户端设备向视频监控管理设备的业务控制单元发送实 况 (即实时视频数据和釆集数据)浏览请求；
2、 业务控制单元对用户的请求进行鉴权， 包括判断其是否具备釆集数据 观看权限， 若鉴权通过， 则生成对应服务的视频监控管理设备的媒体分发 /存 储单元的第一链接地址给客户端设备， 同时， 将鉴权结果通知给媒体分发 /存 储单元， 若鉴权没通过， 返回客户端设备第二链接地址， 其中， 第一链接地址 和第二链接地址的具体描述请参阅前述实施方式；
3、 用户所在客户端设备根据第一链接地址或第二链接地址向媒体分发 / 存储单元请求实况；
4、 媒体分发 /存储单元向前端摄像机请求实况；
5、 如果前端摄像机外接了釆集器， 在传送实况视频媒体数据时一并将釆 集数据发送给媒体分发 /存储单元；
6、媒体分发 /存储单元将前端的携带釆集数据的视频媒体数据转发给客户 端设备， 若鉴权没有通过则只将视频媒体数据转发给客户端设备；
7、 客户端设备对数据进行接收、 緩存、 解码、 渲染、 并根据叠加数据开 关决定是否叠加 OSD进行播放， 叠加方式参阅前述实施方式的描述；
8、 若视频监控管理设备同时需要进行录像业务， 则媒体分发 /存储单元对 视频媒体数据和釆集数据进行存储， 并生成录像索引文件。
当用户需要浏览历史监控视频时， 请参阅图 11， 图 11为历史监控视频播 放的实现过程示意图， 包括：
1、 用户通过所在客户端设备向视频监控管理设备的业务控制单元发送录 像回放请求 (即历史视频数据和对应的釆集数据)；
2、 业务控制单元对用户的请求进行鉴权， 包括判断其是否具备釆集数据 观看权限， 若鉴权通过， 则生成对应服务的视频监控管理设备的媒体分发 /存 储单元的第一链接地址给客户端， 同时， 将鉴权结果通知给媒体分发 /存储单 元， 若鉴权没有通过， 返回客户端设备第二链接地址；
3、 用户所在客户端设备根据第一链接地址或第二链接地址向媒体分发 / 存储单元请求历史视频数据和釆集数据；
4、 媒体分发 /存储单元根据用户请求， 查询录像索引文件， 并根据索引文 件中指引的位置找到视频数据和釆集数据；
5、媒体分发 /存储单元将釆集数据和视频数据进行打包封装后发送给客户 端设备， 若鉴权没有通过， 只发送视频数据；
6、 客户端设备对数据进行接收、 緩存、 解码、 渲染、 并根据叠加数据开 关决定是否叠加 OSD进行播放， 具体叠加实现请参阅上述实施方式的描述。
在此实施例中，具有观看釆集信息权限的用户需要下载带釆集数据信息的 录像视频时， 可以选择一并下载釆集信息保存到本地机器上， 具体实现流程参 见前述实施方式的描述。 下载的釆集数据保存在视频文件封装格式 MP4的扩 展字段中， 以时间戳与视频内容进行关联如图 5所示。
当用户需要观看本地机器上带釆集数据信息的录像视频时，则客户端设备 播放器解析 MP4文件釆集数据信息， 以 OSD形式叠加在视频上展示给用户。 请参阅图 12， 图 12为本申请客户端设备一个实施方式的结构示意图， 客 户端设备 100包括请求模块 21、接收模块 22、数据获取模块 23以及播放模块 24， 其中：
请求模块 21用于向视频监控管理设备发出监控视频浏览请求；
当有用户需要查看监控录像时， 通过所在客户端设备的请求模块 21向视 频监控管理设备发出监控视频浏览请求，请求中可以包括需要查看的录像的条 件信息， 还可以包括用户信息， 比如用户账号、 用户标识等等。
接收模块 22用于在视频监控管理设备根据监控视频浏览请求判断到通过 客户端设备发出监控视频浏览请求的用户有查看釆集数据的权限时，接收视频 监控管理设备返回的第一链接地址，并向数据获取模块 23输出第一链接地址， 第一链接地址为携带视频数据和釆集数据标记的实时流协议的视频播放链接 地址；
当发出监控视频浏览请求的用户有查看釆集数据的权限时，视频监控管理 设备端的鉴权通过，接收模块 22接收视频监控管理设备返回的第一链接地址， 并向数据获取模块 23输出第一链接地址。
数据获取模块 23用于根据第一链接地址从视频监控管理设备获取视频数 据和釆集数据， 并向播放模块 24输出视频数据和釆集数据；
数据获取模块 23根据视频监控管理设备返回的第一链接地址， 向视频监 控管理设备发出获取视频数据和釆集数据的请求，若用户请求的是历史监控视 频，视频监控管理设备根据第一链接地址找到符合条件的录像索引文件，根据 索引文件中的指针地址实际查找到相关的视频数据和釆集数据。将视频数据和 釆集数据发送给客户端设备， 客户端设备的数据获取模块 23接收视频数据和 釆集数据。
若用户请求的是实时监控视频，当客户端设备通过此第一链接地址来请求 数据时，视频监控管理设备再根据此第一链接地址中的信息去获取对应前端设 备的实时视频数据和釆集数据， 并发送给客户端设备。
播放模块 24用于将视频数据和釆集数据叠加后播放。
客户端设备接收到视频数据和釆集数据进行緩存后， 通过播放模块 24对 视频数据进行解码，对釆集数据进行解析，将视频数据和釆集数据叠加渲染后 以视频画面叠加透明字幕的方式 (On-Screen Display, OSD)播放。
请参阅图 13， 图 13为本申请客户端设备另一个实施方式的结构示意图， 客户端设备 100包括请求模块 21、 接收模块 22、 数据获取模块 23、 播放模块 24、 判断模块 25以及保存模块 26， 其中：
请求模块 21用于向视频监控管理设备发出监控视频浏览请求；
用户通过客户端设备的请求模块 21可以发送实时监控视频浏览请求也可 以发送历史监控视频浏览请求。
接收模块 22用于在视频监控管理设备根据监控视频浏览请求判断到通过 客户端设备发出监控视频浏览请求的用户有查看釆集数据的权限时，接收视频 监控管理设备返回的第一链接地址，并向数据获取模块 23输出第一链接地址； 接收模块 22还用于在发出监控视频浏览请求的用户没有查看釆集数据的 权限时，接收从视频监控管理设备返回的第二链接地址， 第二链接地址为只携 带视频数据标记的实时流协议的视频播放链接地址。
数据获取模块 23用于根据第一链接地址从视频监控管理设备获取视频数 据和釆集数据， 并向播放模块 24输出视频数据和釆集数据；
当用户没有查看釆集数据的权限时， 数据获取模块 23还用于根据第二链 接地址从所述视频监控管理设备获取视频数据。
保存模块 26， 用于将数据获取模块 23接收的视频数据和釆集数据分布保 存在不同的文件中， 通过相同的文件名进行关联； 或用于将数据获取模块 23 接收的釆集数据扩展在视频数据的扩展字段中一并保存。
保存模块 26可以将获取到的视频数据和釆集数据下载， 以文件格式保存 在本地机器中。下载数据的文件格式保存可以是釆集数据和视频数据一并保存 在同一个文件中，也可以是将釆集数据以类似字幕文件一般的与视频数据文件 分开保存。 一并保存的方式可以是将釆集数据扩展在视频数据文件格式如 MP4、 AVI等的扩展字段中， 以时间戳与视频数据关联 (如图 5所示）。 分开保 存的方式可以将釆集数据以独立二进制或文本方式保存，通过相同的文件名与 视频数据文件关联。
保存模块 26还用于当发出请求的用户没有查看釆集数据权限的时候， 将 接收模块 22接收的从视频监控管理设备返回的视频数据并保存在本地机器 中。
播放模块 24用于将视频数据和釆集数据叠加后播放。
作为一种比较优选的实施方式， 播放模块 24可以根据用户是否选择数据 叠加决定是否叠加 OSD进行播放。
判断模块 25用于判断是否接收到叠加数据的选择指令， 并向播放模块 24 输出判断结果；
播放模块 24在判断模块 25判断有接收到叠加数据的选择指令时，将视频 数据和釆集数据叠加后以 OSD形式进行播放，当判断模块 25判断到没有接收 到叠加数据的选择指令时， 播放模块 24只播放视频数据。
叠加数据播放时， 播放模块 24根据釆集数据中包含的时间戳信息， 查找 到视频数据中的关联的起始帧， 对视频数据进行解码播放的同时，提取与起始 帧相对应的釆集数据， 渲染叠加后以 OSD方式播放。
作为一种优选的方式， 可以预先设置釆集数据的最大停留时间， 若在釆集 数据的最大停留时间之后， 没有接收到新的釆集数据， 则播放模块 24无效之 前一直显示的釆集数据 (即不再在视频画面中叠加釆集数据)。 如果在预设的最 大停留时间内， 接收到新的釆集数据， 播放模块 24以新的釆集数据替代原有 的釆集数据并与当前视频数据进行叠加后播放。
若用户没有查看釆集数据的权限， 播放模块 24用于播放视频数据。
请参阅图 14， 图 14为本申请视频监控管理设备一个实施方式的结构示意 图， 视频监控管理设备 200包括鉴权模块 31和发送模块 32， 其中：
鉴权模块 31用于接收来自客户端设备的监控视频浏览请求， 根据请求对 通过客户端设备发出监控视频浏览请求的用户进行鉴权， 并向发送模块 32输 出鉴权结果；
当有用户需要查看监控录像时，向视频监控管理设备发出监控视频浏览请 求， 请求中可以包括需要查看的录像的条件信息， 还可以包括用户信息， 比如 用户账号、用户标识等等。 用户可以发送实时监控视频浏览请求也可以发送历 史监控视频浏览请求。
视频监控管理设备的鉴权模块 31接收到监控视频浏览请求后， 对发出请 求的用户进行鉴权，判断发出请求的用户是否有查看跟请求的视频数据相对应 的釆集数据的权限。 鉴权模块 31可以通过预设的用户权限策略或者别的方式 对用户进行鉴权， 本申请对此不做限定。
当鉴权模块 31判断到发出请求的用户有查看釆集数据的权限，鉴权通过， 生成对应用户请求的视频数据和相关联的釆集数据的第一链接地址并输出给 发送模块 32，若鉴权模块 31判断到发出请求的用户没有查看釆集数据的权限， 生成对应用户请求的第二链接地址并输出给发送模块 32， 以使发送模块向客 户端设备发送第二链接地址。
发送模块 32用于在鉴权模块 31通过鉴权得到发出监控视频浏览请求的用 户有查看釆集数据的权限时， 向客户端设备发送第一链接地址， 并根据客户端 设备返回的携带第一链接地址的数据请求，将视频数据和釆集数据发送给客户 端设备， 以使客户端设备能够将视频数据与釆集数据叠加后播放。
发送模块 32在鉴权模块 31的鉴权通过时，将生成的对应用户请求的视频 数据和相关联的釆集数据的第一链接地址发送给客户端设备，以使客户端设备 能够根据该第一链接地址向视频监控管理设备请求相应的视频数据和釆集数 据。
当客户端设备发来携带第一链接地址的数据请求时，若用户请求的是历史 监控视频浏览，发送模块 32根据第一链接地址找到符合条件的录像索引文件， 根据索引文件中的指针地址实际查找到相关的视频数据和釆集数据。将视频数 据和釆集数据发送给客户端设备。
若用户请求的是实时监控视频浏览，当客户端设备通过此第一链接地址来 请求数据时， 发送模块 32根据此第一链接地址中的信息去获取对应前端设备 的实时视频数据和釆集数据， 并发送给客户端设备。
发送模块 32将视频数据和釆集数据发送给客户端设备的方式可以是独立 的消息方式， 如 TCP、 UDP, 或 HTTP、 SIP, SOAP等， 也可以是与视频数据 一并传输， 如基于 RTP的扩展， 基于 PS/TS的扩展。 消息内容格式可以是二 进制、 XML格式。
请进一步参阅图 14， 图 14为本申请视频监控管理设备另一个实施方式的 结构示意图， 视频监控管理设备包括鉴权模块 31、 发送模块 32、 数据获取模 块 33以及保存模块 34， 其中： 鉴权模块 31用于接收来自客户端设备的监控视频浏览请求， 根据请求对 通过客户端设备发出监控视频浏览请求的用户进行鉴权， 并向发送模块 32输 出鉴权结果；
发送模块 32用于在鉴权模块通过鉴权得到发出监控视频浏览请求的用户 有查看釆集数据的权限时， 向客户端设备发送第一链接地址， 并根据客户端设 备返回的携带第一链接地址的数据请求，将视频数据和釆集数据发送给客户端 设备， 以使客户端设备能够将视频数据与釆集数据叠加后播放。
本申请实施方式中，视频监控管理设备与前端设备和釆集器连接， 前端设 备实时从釆集器获取釆集数据，并将釆集数据和自身釆集的视频数据实时传输 给视频监控管理设备。
视频监控管理设备通过数据获取模块 33接收从前端设备传输过来的视频 数据和釆集数据。
数据获取模块 33接收从前端设备通过 RTSP/ TP传输过来的视频数据和 釆集数据。
当前端设备正在录像时，保存模块 34将数据获取模块 33接收的视频数据 与釆集数据分别保存在不同文件中，根据釆集数据和视频数据的时间关联， 生 成视频数据索引的同时增加釆集数据的索引指针； 或将数据获取模块 33接收 的釆集数据扩展在视频数据的扩展字段中一并保存。
数据获取模块 33接收到前端设备发送过来的数据后， 对其进行解析输出 给保存模块 34， 如果前端设备正在录像， 保存模块 34将釆集数据和视频数据 分开存储， 并建立关联（如图 9所示）， 若视频数据和釆集数据是合并一起传 输过来的， 在创建录像文件索引时，根据收到的数据中是否含釆集数据的判断 (通过 RTP包头扩展字段是否含釆集数据判断)， 若有釆集数据， 在录像文件索 引中建立釆集数据文件的指针。 将釆集数据文件与视频数据文件建立关联。
上述实施方式的视频监控管理设备， 其模块的划分，是区别于图 1实施方 式中功能单元的另一种划分方式，跟图 1实施方式中的视频监控管理设备实现 相同的功能。
请参阅图 15， 图 15为本申请客户端设备又一个实施方式的结构示意图， 客户端设备 100包括处理器 41、 接收器 42、 发送器 43、 随机存取存储器 44、 只读存储器 45以及总线 46。其中，处理器 41通过总线 46分别耦接接收器 42、 发送器 43、 随机存取存储器 44以及只读存储器 45。 其中， 当需要运行策略管 理设备时， 通过固化在只读存储器 45中的基本输入输出系统或者嵌入式系统 中的 bootloader引导系统进行启动， 引导客户端设备进入正常运行状态。 在客 户端设备进入正常运行状态后， 在随机存取存储器 44中运行应用程序和操作 系统， 并使得：
发送器 43向视频监控管理设备发送监控视频浏览请求， 该请求可以是实 时监控视频浏览请求也可以是历史监控视频浏览请求。
接收器 42在视频监控管理设备对发出请求的用户进行鉴权， 当发出请求 的用户有查看釆集数据的权限时，接收从视频监控管理设备返回的第一链接地 址，第一链接地址为携带视频数据和釆集数据标记的实时流协议的视频播放链 接地址； 发送器 43根据第一链接地址向视频监控管理设备发送数据请求， 接 收器 42进一步接收视频监控管理设备返回的符合用户请求条件的视频数据和 釆集数据。 若发出请求的用户没有查看釆集数据的权限时， 接收器 42接收从 视频监控管理设备返回的第二链接地址，第二链接地址为只携带视频数据的实 时流协议的视频播放链接地址； 发送器 43根据第二链接地址向视频监控管理 设备发出数据请求， 接收器 42进一步根据视频监控管理设备返回的符合用户 请求条件的视频数据。
处理器 41用于将视频数据和釆集数据叠加后以 OSD形式播放。对于有查 看釆集数据权限的用户， 处理器 41可以根据该用户是否选择叠加数据的指令 而决定是否叠加数据播放。这样可以避免有权限查看釆集数据但是不需要查看 的用户也不得不看到叠加的釆集数据，让用户权限最小化，带来更高的安全性。
处理器 41进一步在发出请求的用户没有查看釆集数据的权限时， 只播放 视频监控管理设备返回的视频数据。
本实施方式中， 处理器 41可能是一个中央处理器 CPU， 或者是特定集成 电路 ASIC ( Application Specific Integrated Circuit )， 或者是被配置成实施本申 请实施方式的一个或多个集成电路。
请参阅图 17， 图 17为本申请视频监控管理设备又一个实施方式的结构示 意图， 视频监控管理设备 200包括处理器 51、 接收器 52、 发送器 53、 随机存 取存储器 54、 只读存储器 55、 总线 56 以及网络接口单元 57。 其中， 处理器 51通过总线 56分别耦接接收器 52、 发送器 53、 随机存取存储器 54、 只读存 储器 55以及网络接口单元 57。 其中， 当需要运行网络流量处理设备时， 通过 固化在只读存储器 55 中的基本输入输出系统或者嵌入式系统中的 bootloader 引导系统进行启动， 引导网络流量处理设备进入正常运行状态。在网络流量处 理设备进入正常运行状态后， 在随机存取存储器 54中运行应用程序和操作系 统， 从网络接收数据或者向网络发送数据， 使得：
接收器 52接收来自客户端设备的监控视频浏览请求；
处理器 51根据自身的权限管理策略或者别的方式， 对发出请求的用户进 行鉴权，在发出请求的用户有查看釆集数据的权限时， 生成的对应用户请求的 视频数据和相关联的釆集数据的第一链接地址， 将第一链接地址通过发送器 53 发送给客户端设备， 第一链接地址为携带视频数据和釆集数据标记的实时 流协议的视频播放链接地址；
在客户端设备发来携带第一链接地址的数据请求时，若用户请求的是历史 监控视频浏览， 根据第一链接地址查找到视频数据和釆集数据， 通过发送器 53将视频数据和釆集数据发送给客户端设备。
若用户请求的是实时监控视频浏览，当客户端设备通过此第一链接地址来 请求数据时，根据此第一链接地址中的信息去获取对应前端设备的实时视频数 据和釆集数据， 并通过发送器 53将视频数据和釆集数据发送给客户端设备。
处理器 51在通过鉴权得到发出请求的用户没有查看釆集数据的权限时， 生成符合用户请求条件的视频数据对应的第二链接地址， 通过发送器 53发送 给客户端设备，第二链接地址为只携带视频数据标记的实时流协议的视频播放 链接地址。
在客户端设备发来携带第二链接地址的数据请求时，根据第二链接地址获 取视频数据， 通过发送器 53将视频数据发送给客户端设备。
本实施方式中， 处理器 51可能是一个中央处理器 CPU， 或者是特定集成 电路 ASIC ( Application Specific Integrated Circuit )， 或者是被配置成实施本申 请实施方式的一个或多个集成电路。
根据上述提供的客户端设备和视频监控管理设备，本申请还提供一种视频 监控系统，包括客户端设备 100和视频监控管理设备 200，其中客户端设备 100 和视频监控管理设备 200之间实现通信， 具体可以参见图 1以相关描述，客户 端设备 100以及视频监控管理设备 200的具体功能实现请参见图 12-17实施方 式的相应描述， 再次不再赘述。
上述技术方案，通过对客户端设备的权限进行管理， 只有通过客户端设备 发送请求的用户具有查看釆集数据权限时才将釆集数据和视频数据发送给客 户端设备，并且在用户选择叠加播放时才将视频数据和釆集数据一起叠加后播 放。 通过这种方式， 能够灵活的根据发出监控视频浏览请求的用户权限， 控制 是否向客户端设备发送与视频数据相应的釆集数据，根据用户的选择决定是否 一同播放釆集数据，使监控视频的播放更加灵活，避免不需要查看釆集数据的 人也不得不看到釆集数据， 让用户权限最小化， 带来更高的安全性。
另外， 通过 OSD方式将视频数据和釆集数据叠加播放， 方便在不需要时 或者釆集数据显示一定时间后去掉釆集信息，不会因釆集数据而遮挡录像画面 中的关键信息， 带来更好的体验效果。
在本申请所提供的几个实施方式中， 应该理解到， 所揭露的系统， 装置和 方法， 可以通过其它的方式实现。 例如， 以上所描述的装置实施方式仅仅是示 意性的， 例如， 所述模块或单元的划分， 仅仅为一种逻辑功能划分， 实际实现 时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一 个系统， 或一些特征可以忽略， 或不执行。 另一点， 所显示或讨论的相互之间 的耦合或直接辆合或通信连接可以是通过一些接口，装置或单元的间接辆合或 通信连接， 可以是电性， 机械或其它的形式。 单元显示的部件可以是或者也可以不是物理单元， 即可以位于一个地方， 或者 也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部 单元来实现本实施方式方案的目的。
另外， 在本申请各个实施方式中的各功能单元可以集成在一个处理单元 中，也可以是各个单元单独物理存在， 也可以两个或两个以上单元集成在一个 单元中。上述集成的单元既可以釆用硬件的形式实现，也可以釆用软件功能单 元的形式实现。 所述集成的单元如果以软件功能单元的形式实现并作为独立的产品销售 或使用时， 可以存储在一个计算机可读取存储介质中。 基于这样的理解， 本申 请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的全 部或部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储 介质中， 包括若干指令用以使得一台计算机设备（可以是个人计算机，服务器， 或者网络设备等）或处理器（processor )执行本申请各个实施方式所述方法的 全部或部分步骤。而前述的存储介质包括： U盘、移动硬盘、只读存储器（ ROM， Read-Only Memory ). 随机存取存 4诸器 ( RAM, Random Access Memory )、 磁 碟或者光盘等各种可以存储程序代码的介质。
以上所述仅为本申请的实施方式， 并非因此限制本申请的专利范围， 凡是 利用本申请说明书及附图内容所作的等效结构或等效流程变换，或直接或间接 运用在其他相关的技术领域， 均同理包括在本申请的专利保护范围内。

Claims

权利要求
1.一种监控视频播放的方法， 其特征在于， 包括：
视频监控管理设备接收来自客户端设备的监控视频浏览请求，根据所述请 求对通过所述客户端设备发出所述监控视频浏览请求的用户进行鉴权；
若发出所述监控视频浏览请求的用户有查看釆集数据的权限，向所述客户 端设备发送对应用户请求的第一链接地址，所述第一链接地址为携带视频数据 和釆集数据标记的实时流协议的视频播放链接地址；
根据所述客户端设备返回的携带所述第一链接地址的数据请求，将视频数 据和釆集数据发送给所述客户端设备，以使所述客户端设备能够将所述视频数 据与所述釆集数据叠加后播放。
2.根据权利要求 1所述的方法， 其特征在于，
所述根据所述第一链接地址向所述客户端设备发送视频数据和釆集数据 的步骤之前， 还包括：
所述视频监控管理设备接收从前端设备传输过来的视频数据和釆集数据。
3.根据权利要求 2所述的方法， 其特征在于，
所述视频监控管理设备接收从前端设备传输过来的视频数据和釆集数据 的步骤包括： 所述视频监控管理设备接收从前端设备通过实时流传输协议 /实 时传送协议传输过来的视频数据，所述釆集数据由所述视频数据的实时传送协 议头一并带入。
4.根据权利要求 2所述的方法， 其特征在于，
所述视频监控管理设备接收从前端设备传输过来的视频数据和釆集数据 的步骤之后， 还包括：
若所述前端设备正在录像，则所述视频监控管理设备将所述视频数据与所 述釆集数据分别保存在不同文件中，根据所述釆集数据和所述视频数据的时间 关联， 生成视频数据索引的同时增加釆集数据的索引指针； 或将所述釆集数据 扩展在所述视频数据的扩展字段中一并保存。
5.根据权利要求 1所述的方法， 其特征在于，
根据所述第一链接地址，将视频数据和釆集数据发送给所述客户端设备的 步骤包括： 根据所述第一链接地址，将所述视频数据和所述釆集数据分别传输给所述 客户端设备；或将所述视频数据和所述釆集数据合并后一起发送给所述客户端 设备。
6.根据权利要求 1所述的方法， 其特征在于，
所述视频监控管理设备接收来自客户端设备的监控视频浏览请求，根据所 述请求对通过所述客户端设备发出所述监控视频浏览请求的用户进行鉴权的 步骤之后， 还包括：
若发出所述监控视频浏览请求的用户没有查看釆集数据的权限，向所述客 户端设备发送第二链接地址，所述第二链接地址为只携带视频数据标记的实时 流协议的视频播放链接地址。
7.—种客户端设备， 其特征在于， 包括请求模块、 接收模块、 数据获取模 块以及播放模块， 其中：
所述请求模块用于向视频监控管理设备发出监控视频浏览请求； 所述接收模块用于在所述视频监控管理设备根据所述监控视频浏览请求 判断到通过所述客户端设备发出所述监控视频浏览请求的用户有查看釆集数 据的权限时，接收所述视频监控管理设备返回的第一链接地址， 所述第一链接 地址为携带视频数据和釆集数据标记的实时流协议的视频播放链接地址，并向 所述数据获取模块输出所述第一链接地址；
所述数据获取模块用于根据所述第一链接地址从所述视频监控管理设备 获取视频数据和釆集数据，并向所述播放模块输出所述视频数据和所述釆集数 据；
所述播放模块用于将所述视频数据和所述釆集数据叠加后播放。
8.根据权利要求 7所述的客户端设备， 其特征在于，
所述客户端设备还包括判断模块，用于判断是否接收到叠加数据的选择指 令， 并向所述播放模块输出判断结果；
所述播放模块用于在所述判断模块判断到有接收到所述叠加数据的选择 指令时，将所述视频数据和所述釆集数据叠加后播放； 或在所述判断模块判断 到没有接收到所述叠加数据的选择指令时， 将所述视频数据播放。
9.根据权利要求 7所述的客户端设备， 其特征在于， 所述接收模块用于在所述视频监控管理设备根据所述监控视频浏览请求 判断到通过所述客户端设备发出所述监控视频浏览请求的用户没有查看釆集 数据的权限时，接收所述视频监控管理设备返回的第二链接地址， 所述第二链 接地址为只携带视频数据标记的实时流协议的视频播放链接地址，并向所述数 据获取模块输出所述第二链接地址；
所述数据获取模块用于根据所述第二链接地址从所述视频监控管理设备 获取视频数据， 并向所述播放模块输出所述视频数据；
所述播发模块用于播放所述视频数据。
10.—种视频监控管理设备， 其特征在于， 包括鉴权模块和发送模块， 其 中：
所述鉴权模块用于接收来自客户端设备的监控视频浏览请求，根据所述请 求对通过所述客户端设备发出所述监控视频浏览请求的用户进行鉴权，并向所 述发送模块输出所述鉴权结果；
所述发送模块用于在所述鉴权模块通过鉴权得到发出所述监控视频浏览 请求的用户有查看釆集数据的权限时， 向所述客户端设备发送第一链接地址， 所述第一链接地址为携带视频数据和釆集数据标记的实时流协议的视频播放 链接地址， 并根据所述客户端设备返回的携带所述第一链接地址的数据请求， 将视频数据和釆集数据发送给所述客户端设备，以使所述客户端设备能够将所 述视频数据与所述釆集数据叠加后播放。
11.根据权利要求 10所述的设备， 其特征在于，
所述设备还包括数据获取模块，用于接收从前端设备传输过来的视频数据 和釆集数据。
12.根据权利要求 10所述的设备， 其特征在于，
所述设备还包括保存模块，用于将所述数据获取模块接收的所述视频数据 与所述釆集数据分别保存在不同文件中，根据所述釆集数据和所述视频数据的 时间关联， 生成视频数据索引的同时增加釆集数据的索引指针； 或将所述数据 获取模块接收的所述釆集数据扩展在所述视频数据的扩展字段中一并保存。
13.—种视频监控系统，其特征在于， 包括权利要求 7-9任一项所述的客户 端设备和权利要求 10-12任一项所述的视频监控管理设备。
PCT/CN2014/075576 2013-04-17 2014-04-17 一种监控视频播放的方法及设备、系统 WO2014169828A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP14785139.8A EP2958321A4 (en) 2013-04-17 2014-04-17 METHOD, DEVICE AND SYSTEM FOR READING A SURVEILLANCE VIDEO
US14/880,515 US9843775B2 (en) 2013-04-17 2015-10-12 Surveillance video playback method, device, and system

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201310134227.0 2013-04-17
CN201310134227.0A CN104113727B (zh) 2013-04-17 2013-04-17 一种监控视频播放的方法及设备、系统

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US14/880,515 Continuation US9843775B2 (en) 2013-04-17 2015-10-12 Surveillance video playback method, device, and system

Publications (1)

Publication Number Publication Date
WO2014169828A1 true WO2014169828A1 (zh) 2014-10-23

Family

ID=51710347

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2014/075576 WO2014169828A1 (zh) 2013-04-17 2014-04-17 一种监控视频播放的方法及设备、系统

Country Status (4)

Country Link
US (1) US9843775B2 (zh)
EP (1) EP2958321A4 (zh)
CN (1) CN104113727B (zh)
WO (1) WO2014169828A1 (zh)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3236629A4 (en) * 2014-12-19 2018-05-16 Xiaomi Inc. Method and apparatus for processing surveillance video
CN108401135A (zh) * 2018-01-11 2018-08-14 蔚来汽车有限公司 充换电站监控视频数据处理方法和装置
DE112016006981B4 (de) 2016-08-31 2023-04-06 Hitachi High-Tech Corporation Probe zum Messen von Teilchen, Verfahren zum Messen von Teilchen undVorrichtung zum Messen von Teilchen

Families Citing this family (23)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10083584B2 (en) * 2015-12-30 2018-09-25 Honeywell International Inc. Video surveillance system with selectable operating scenarios and system training for improved situational awareness
US11368753B2 (en) * 2016-01-06 2022-06-21 LiveView Technologies, LLC Managing live video stream connections and data usage
CN106330886B (zh) * 2016-08-18 2020-05-26 浙江大华技术股份有限公司 一种在远程监控中保护视频隐私的方法和设备
CN106375793B (zh) * 2016-08-29 2019-12-13 东方网力科技股份有限公司 一种视频结构化信息的叠加方法、用户终端及叠加系统
CN106454416B (zh) * 2016-10-21 2019-12-13 浙江宇视科技有限公司 一种同步回放方法及设备
AU2016277697A1 (en) * 2016-12-22 2018-07-12 Canon Kabushiki Kaisha Method, system and apparatus for providing access to videos
CN106899875A (zh) * 2017-02-06 2017-06-27 合网络技术（北京）有限公司 外挂字幕的显示控制方法及装置
CN108809939B (zh) * 2018-04-25 2021-08-24 安克创新科技股份有限公司 音视频的处理方法、播放方法及基站
CN110536077B (zh) * 2018-05-25 2020-12-25 杭州海康威视系统技术有限公司 一种视频合成和播放方法、装置及设备
US10820053B2 (en) 2018-12-05 2020-10-27 Hulu, LLC Extension bundle generation for recording extensions in video delivery
CN110536120A (zh) * 2019-09-11 2019-12-03 成都千立网络科技有限公司 远程监控数据流的获取系统
CN111314629B (zh) * 2020-03-20 2022-12-06 上海依图网络科技有限公司 一种osd信息叠加方法及装置
CN111586066B (zh) * 2020-05-12 2022-08-12 上海依图网络科技有限公司 一种多媒体数据加密处理的方法及装置
CN112202786B (zh) * 2020-09-30 2022-05-20 武汉中科通达高新技术股份有限公司 一种违法数据识别方法及装置、电子设备
CN112911349A (zh) * 2021-01-27 2021-06-04 北京翔云颐康科技发展有限公司 视频发送方法及装置、存储介质、电子装置
US20220335795A1 (en) * 2021-04-16 2022-10-20 Dice Corporation Hyperlinked digital video alarm electronic document
CN113038169B (zh) * 2021-05-24 2021-07-23 天津所托瑞安汽车科技有限公司 视频流推送方法和系统
CN113518260B (zh) * 2021-09-14 2022-05-03 腾讯科技（深圳）有限公司 视频播放方法、装置、电子设备及计算机可读存储介质
CN114051120A (zh) * 2021-10-26 2022-02-15 远光软件股份有限公司 视频告警方法、装置、存储介质及电子设备
CN114007045A (zh) * 2021-10-29 2022-02-01 上海蜜罐信息科技有限公司 快递柜监控视频本地调取方法及系统
CN114302073A (zh) * 2021-12-31 2022-04-08 吉林建龙信息科技有限公司 动态视频叠加图表文字的处理方法、装置、设备及介质
CN114500940A (zh) * 2022-01-14 2022-05-13 成都数字家园科技有限公司 基于本地部署的视频硬件编解码和视频转发方法
CN116258310A (zh) * 2022-11-18 2023-06-13 广西交通投资集团南宁高速公路运营有限公司 提升公路应急救援效率的多方联合调度指挥系统及方法

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101282450A (zh) * 2007-04-02 2008-10-08 厦门瑞科技术有限公司 一种可快速访问和管理网络摄像机的方法
US20080252722A1 (en) * 2007-04-11 2008-10-16 Yuan-Kai Wang System And Method Of Intelligent Surveillance And Analysis
CN201197180Y (zh) * 2008-02-21 2009-02-18 上海迅特电子科技有限公司 网络视频处理装置
CN102036058A (zh) * 2010-12-20 2011-04-27 南京中兴新软件有限责任公司 视频监控系统中视频切换的方法、服务器、终端及系统

Family Cites Families (16)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
AU2003286491A1 (en) * 2002-10-18 2004-05-04 Global Epoint, Inc. Video and telemetry apparatus and methods
AU2003900137A0 (en) * 2003-01-14 2003-01-30 Canon Kabushiki Kaisha Process and format for reliable storage of data
US8819178B2 (en) * 2005-03-16 2014-08-26 Icontrol Networks, Inc. Controlling data routing in integrated security systems
CN1786422A (zh) * 2005-11-29 2006-06-14 李铁顺 矿用瓦斯监控方法与系统
CN101035268A (zh) * 2007-03-30 2007-09-12 西安科汇科技发展有限公司 一种赛鸽用移动视频监控方法及设备
CN201134889Y (zh) * 2007-11-23 2008-10-15 浙江弘申信息技术有限公司 视频叠加数据采集仪
CN101287003B (zh) * 2008-05-23 2011-04-20 中兴通讯股份有限公司 一种实现移动终端监控视频浏览的系统及方法
US9035768B2 (en) * 2008-05-23 2015-05-19 Leverage Information Systems Peer to peer surveillance architecture
CN101448072A (zh) * 2008-12-29 2009-06-03 北京中星微电子有限公司 网络视频监控系统的视频查看方法及系统
CN102045540A (zh) * 2009-10-20 2011-05-04 华为软件技术有限公司 视频监控方法、系统及设备
CN201892999U (zh) * 2010-10-27 2011-07-06 公安部上海消防研究所 一种基于视频处理技术的消防安防一体化系统
CN102006456A (zh) * 2010-10-28 2011-04-06 北京中星微电子有限公司 一种云台摄像机、云台监控系统及进行方向定位的方法
CN102196248B (zh) * 2011-05-04 2013-06-12 杭州海康威视系统技术有限公司 一种移动视频监控系统及方法
CN202168161U (zh) * 2011-07-20 2012-03-14 成都锐达智诚科技有限责任公司 一种视频监控与数据采集融合的系统
CN102594884B (zh) * 2012-02-09 2015-01-21 成都三零凯天通信实业有限公司 基于b/s架构多级数据自动分发与同步的方法与系统
US20130286211A1 (en) * 2012-04-26 2013-10-31 Jianhua Cao Method and apparatus for live capture image-live streaming camera utilizing personal portable device

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101282450A (zh) * 2007-04-02 2008-10-08 厦门瑞科技术有限公司 一种可快速访问和管理网络摄像机的方法
US20080252722A1 (en) * 2007-04-11 2008-10-16 Yuan-Kai Wang System And Method Of Intelligent Surveillance And Analysis
CN201197180Y (zh) * 2008-02-21 2009-02-18 上海迅特电子科技有限公司 网络视频处理装置
CN102036058A (zh) * 2010-12-20 2011-04-27 南京中兴新软件有限责任公司 视频监控系统中视频切换的方法、服务器、终端及系统

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP2958321A4 *

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3236629A4 (en) * 2014-12-19 2018-05-16 Xiaomi Inc. Method and apparatus for processing surveillance video
US10193875B2 (en) 2014-12-19 2019-01-29 Xiaomi Inc. Method and apparatus for controlling access to surveillance video
DE112016006981B4 (de) 2016-08-31 2023-04-06 Hitachi High-Tech Corporation Probe zum Messen von Teilchen, Verfahren zum Messen von Teilchen undVorrichtung zum Messen von Teilchen
CN108401135A (zh) * 2018-01-11 2018-08-14 蔚来汽车有限公司 充换电站监控视频数据处理方法和装置

Also Published As

Publication number Publication date
US9843775B2 (en) 2017-12-12
CN104113727A (zh) 2014-10-22
US20160094805A1 (en) 2016-03-31
EP2958321A1 (en) 2015-12-23
EP2958321A4 (en) 2016-03-30
CN104113727B (zh) 2017-09-12

Similar Documents

Publication Publication Date Title
WO2014169828A1 (zh) 一种监控视频播放的方法及设备、系统
CN108989264B (zh) 一种直播方法、系统以及相关设备
US9026668B2 (en) Real-time and retargeted advertising on multiple screens of a user watching television
US11212334B2 (en) Mechanisms to support adaptive constrained application protocol (CoAP) streaming for Internet of Things (IoT) systems
US10034057B2 (en) Message processing method, device, gateway, STB and IPTV
EP4084483A1 (en) Media presentation description
US9549010B2 (en) Method and apparatus for media session identification, tracking, and analysis
WO2008061416A1 (fr) Procédé et système permettant d&#39;accepter des données media de divers formats de codage
WO2015090095A1 (zh) 一种信息推送方法、设备和系统
JP2019508790A (ja) 情報処理方法、第１の端末、第２の端末、サーバ、およびシステム
US20200213682A1 (en) Content exposure attribution based on renderings of related content across multiple devices
CA2743949A1 (en) System and method of local resource delivery
WO2010045793A1 (zh) 一种实现数字家庭环境下远程视频监控的系统及其方法
US8850496B2 (en) Dynamic provisioning of closed captioning to user devices
CN102484686B (zh) 用于提供补充信息的方法和设备
US11196691B2 (en) Method and apparatus for distributing content to communication devices
US20230045876A1 (en) Video Playing Method, Apparatus, and System, and Computer Storage Medium
KR20160004377A (ko) Ott 비디오의 품질을 모니터링하는 방법, 장치, 및 시스템
CN108810475B (zh) 一种基于Onvif标准及Sip协议的Android视频监控装置
JP6530820B2 (ja) マルチメディア情報再生方法及びシステム、採集デバイス、標準サーバ
CN112235592B (zh) 直播方法、直播处理方法、装置、计算机设备
TW200926700A (en) Method and apparatus for the aggregation and indexing of message parts in multipart mime objects
CN109859826A (zh) 一种病理图像加载方法和装置
WO2014015489A1 (zh) 一种用户接入业务系统或网络的方法、系统及装置
US20220360853A1 (en) Mmt based drm operation for atsc 3.0

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 14785139

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 2014785139

Country of ref document: EP

NENP Non-entry into the national phase

Ref country code: DE