CN112866199B - Method for viewing GB/T28181 protocol-supporting equipment in Chrome browser - Google Patents
Method for viewing GB/T28181 protocol-supporting equipment in Chrome browser Download PDFInfo
- Publication number
- CN112866199B CN112866199B CN202011632751.7A CN202011632751A CN112866199B CN 112866199 B CN112866199 B CN 112866199B CN 202011632751 A CN202011632751 A CN 202011632751A CN 112866199 B CN112866199 B CN 112866199B
- Authority
- CN
- China
- Prior art keywords
- video stream
- protocol
- flv
- video
- information
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 36
- VYZAMTAEIAYCRO-UHFFFAOYSA-N Chromium Chemical compound [Cr] VYZAMTAEIAYCRO-UHFFFAOYSA-N 0.000 title claims abstract description 26
- 238000012544 monitoring process Methods 0.000 claims description 12
- 238000006243 chemical reaction Methods 0.000 claims description 11
- 238000004806 packaging method and process Methods 0.000 claims description 6
- 230000000977 initiatory effect Effects 0.000 claims description 5
- 230000005540 biological transmission Effects 0.000 claims description 4
- 238000012545 processing Methods 0.000 abstract description 5
- 238000012423 maintenance Methods 0.000 description 3
- 238000004891 communication Methods 0.000 description 2
- 210000001503 joint Anatomy 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
- H04L65/60—Network streaming of media packets
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
- H04L65/1066—Session management
- H04L65/1073—Registration or de-registration
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
- H04L65/1066—Session management
- H04L65/1101—Session protocols
- H04L65/1104—Session initiation protocol [SIP]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
- H04L65/60—Network streaming of media packets
- H04L65/65—Network streaming protocols, e.g. real-time transport protocol [RTP] or real-time control protocol [RTCP]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
- H04L65/60—Network streaming of media packets
- H04L65/70—Media network packetisation
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
- H04L67/025—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP] for remote control or remote monitoring of applications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/16—Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]
- H04L69/161—Implementation details of TCP/IP or UDP/IP stack architecture; Specification of modified or new header fields
- H04L69/162—Implementation details of TCP/IP or UDP/IP stack architecture; Specification of modified or new header fields involving adaptations of sockets based mechanisms
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L2212/00—Encapsulation of packets
Abstract
The invention provides a method for viewing a device supporting a GB/T28181 protocol in a Chrome browser, which comprises the following steps: the LiveServer end realizes an SIP protocol through node. js, establishes a session with GB/T28181 equipment, calls a video stream, and receives and processes a Web request; the TranscodeServer end acquires a video stream, converts the video stream into FLV through FFmpeg and pushes the FLV to a mediaServer end; the MediaServer end receives RTMP video stream, packages the RTMP video stream into FLV and distributes the FLV to the Web end; and the Web end acquires the video stream from the MediaServer end and plays the video. The invention carries out data processing by the mutual cooperation of a plurality of servers and converts the GB/T28181 protocol into a protocol which can be transmitted by HTTP, thereby realizing the video viewing and control of the browser.
Description
Technical Field
The invention relates to the technical field of computers, in particular to a method for viewing equipment supporting a GB/T28181 protocol in a Chrome browser.
Background
Generally, a Chrome browser plays videos through a Video tag and supports H264 encoded MP4, but does not support H265 encoded MP4, Chrome can also transfer sliced H264 videos and AAC audio to Video for Video playing through an mse (media Source extensions) interface, and FLV. The disadvantage of this scheme is that H265 coded video is not supported.
The Chrome Web page supports HTTP protocol but does not support TCP/UDP protocol, and GB28181 protocol is based on TCP/UDP protocol, so GB28181 equipment can not be directly connected with browser.
FFmpeg is a program library for recording, converting and transmitting video and audio, supports codec H264 and H265 video, supports coding AAC audio, supports RTP transmission protocol, supports RTSP and RTMP multimedia protocol, and does not support GB/T28181 protocol because it is mainly maintained by foreigners and GB/T28181 is a Chinese standard.
The communication between GB/T28181 equipment is realized by an SIP (Session Initiation protocol) protocol, open source libraries are arranged on the network and mainly written by C + +, so that the problems of difficult maintenance, difficult field debugging and the like exist, and especially the problems of compatibility often occur when domestic manufacturers realize different GB/T28181 protocols, and the problems are more obvious.
The scheme for playing GB/T28181 video by using Chrome browser is known at present as follows:
the first method comprises the following steps: the SIP protocol and the RTP protocol are converted into the HTTP protocol through the server agent, and are directly transmitted to the Web end, and the Web end analyzes and is in butt joint, so that the performance is low, and more importantly, the problem that the H265 video cannot be played by the Web end cannot be solved.
And the second method comprises the following steps: the server is in butt joint with GB/T28181 equipment, the server side processes data and forwards the data to the Web side, but the server side cannot cross platforms, and has the problems of poor maintainability, poor stability and the like.
Disclosure of Invention
The invention aims to provide a method for viewing GB/T28181 protocol-supporting equipment in a Chrome browser, which can solve the problems of poor performance, difficult cross-platform and poor stability of the existing GB/T28181 equipment docked by a server.
The invention provides a method for viewing a device supporting a GB/T28181 protocol in a Chrome browser, which comprises the following steps:
the LiveServer end realizes an SIP protocol through node. js, establishes a session with GB/T28181 equipment, calls a video stream, and receives and processes a Web request;
the TranscodeServer end acquires a video stream, converts the video stream into FLV through FFmpeg and pushes the FLV to a mediaServer end;
the MediaServer end receives RTMP video stream, packages the RTMP video stream into HTTP-FLV and WebSocket-FLV and distributes the HTTP-FLV and the WebSocket-FLV to the Web end;
and the Web end acquires the video stream from the MediaServer end and plays the video.
Preferably, the method further comprises the following steps:
the Web end monitors the dragging of a user to a video picture;
after a dragging event is received, analyzing corresponding cradle head operation data;
transmitting the holder operation data to a LiveServer end;
and the LiveServer end receives the cradle head operation data, encapsulates the cradle head operation data into a format of a GB/T28181 protocol, and sends the cradle head operation data to the corresponding GB/T28181 equipment to complete cradle head control.
Preferably, the LiveServer terminal establishes a session with the GB/T28181 device by implementing the SIP protocol over node.
Realizing SIP protocol through TCP/UDP protocol in node.js, and packaging interface;
establishing a connection with a GB/T28181 device by using a SIP protocol;
acquiring GB/T28181 equipment information and channel information through an SIP protocol, and recording the information and the channel information into a file;
acquiring a monitoring real-time video stream through an SIP (session initiation protocol);
starting a TranscodeServer, and transmitting GB/T28181 equipment information and video stream information to a TranscodeServer end;
controlling GB/T28181 equipment through a SIP protocol;
a front-end Web request is received.
Preferably, the SIP protocol is implemented by a TCP/UDP protocol in node.js, and the encapsulating interface includes:
starting to monitor SIP information;
stopping receiving the SIP message;
receiving SIP message, formatting the message and informing a monitor in JavaScript;
the SIP message is sent.
Preferably, the establishing of the connection with the GB/T28181 device using the SIP protocol includes:
monitoring a local port through an SIP protocol, and waiting for registration of GB/T28181 equipment;
the registration message is received and authenticated.
Preferably, the acquiring the monitoring real-time video stream through the SIP protocol includes:
calling video stream information of GB/T28181 equipment through a SIP protocol;
receiving video stream information of GB/T28181 equipment through a SIP protocol;
analyzing video stream information, starting a TranscodeServer end, transmitting parameters to the TranscodeServer end, starting monitoring by the TranscodeServer end, and waiting for the video stream information;
and informing the GB/T28181 equipment to transmit the video stream.
Preferably, the transcoding server side acquires the video stream through FFmpeg, converts the video stream into FLV and pushes the FLV to the MediaServer side, and comprises:
acquiring equipment information and video stream information transmitted by a LiveServer end through a pipeline;
starting an acquisition thread according to the parameters, acquiring video stream information through a TCP (transmission control protocol) protocol or a UDP (user datagram protocol), caching the acquired video stream information into a circular queue, and waiting for a conversion thread to use;
and starting a conversion thread, and analyzing audio and video data information through FFmpeg.
Preferably, the starting of the conversion thread, analyzing the audio/video data information by FFmpeg includes:
judging whether the video data is directly used if the H264 coding is adopted, or else, converting the video data into the H264 coding;
judging whether the audio data are directly used if AAC coding is adopted, or else, converting the audio data into AAC coding or discarding the audio data;
and after the audio and video data conversion is finished, packaging the audio and video data into an FLV format, and pushing the FLMpeg to a mediaServer end through an RTMP protocol.
Preferably, the MediaServer end receives the RTMP video stream, encapsulates the RTMP video stream into HTTP-FLV and WebSocket-FLV, and distributes the HTTP-FLV and WebSocket-FLV to the Web end, and includes:
receiving video stream information of an RTMP protocol, and converting the video stream information into an HTTP-FLV protocol or a WebSocket-FLV protocol;
and simultaneously forwarding the same video stream to a plurality of Web terminals.
Preferably, the acquiring, by the Web end, the video stream from the MediaServer end, and performing video playing includes:
connecting a LiveServer end through a WebScoket to obtain HTTP-FLV and WebSocket-FLV addresses of a corresponding video stream at a MediaServer end;
and connecting the MediaServer terminal through the acquired address to acquire a video stream, decoding an H264 video and an AAC audio through flv.js, and then playing the corresponding video stream through an MSE interface of a browser.
Compared with the prior art, the method for viewing the device supporting the GB/T28181 protocol in the Chrome browser has the following beneficial effects:
1. the invention adopts a multi-process architecture and has stable performance. Because the video streams have compatibility problems, each video stream correspondingly starts a TranscodeServer process, so that if one video stream is wrong, the normal playing of other video streams is not influenced, and meanwhile, the other video streams can be normally converted.
2. The SIP protocol in the invention is written by JavaScript, and since JavaScript is easy to debug, if problems occur, the system is easy to locate, thereby being convenient for system maintenance.
3. In the invention, as the server is developed by using JavaScript and C + +, the service can be deployed to Windows and Linux platforms, thereby realizing cross-platform data processing.
4. The invention can realize that the browsers of the PC end and the mobile end are simultaneously supported to view the video, so that the browser can view the GB28181 video.
5. The invention carries out data processing by the mutual cooperation of a plurality of servers, converts the GB/T28181 protocol into a protocol (HTTP-FLV, WebSocket-FLV) which can be transmitted by HTTP, thereby realizing the video viewing and control of a browser end.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, and it is obvious that the drawings in the following description are only used for explaining the concept of the present invention.
FIG. 1 is a schematic flow chart of a method for viewing a device supporting the GB/T28181 protocol in a Chrome browser according to the present invention.
Detailed Description
Hereinafter, an embodiment of a method for viewing a device supporting the GB/T28181 protocol in a Chrome browser according to the present invention will be described with reference to the accompanying drawings.
The examples described herein are specific embodiments of the present invention, are intended to be illustrative and exemplary in nature, and are not to be construed as limiting the scope of the invention. In addition to the embodiments described herein, those skilled in the art will be able to employ other technical solutions which are obvious based on the disclosure of the claims and the specification of the present application, and these technical solutions include any obvious replacement or modification of the embodiments described herein.
As shown in FIG. 1, the present invention provides a method for viewing in Chrome browser by a device supporting GB/T28181 protocol, including the following steps:
step S1: the LiveServer end realizes an SIP protocol through node. js, establishes a session with GB/T28181 equipment, calls a video stream, and receives and processes a Web request;
step S2: the TranscodeServer end acquires a video stream, converts the video stream into FLV through FFmpeg and pushes the FLV to a mediaServer end;
step S3: the MediaServer end receives RTMP video stream, packages the RTMP video stream into HTTP-FLV and WebSocket-FLV and distributes the HTTP-FLV and the WebSocket-FLV to the Web end;
step S4: and the Web end acquires the video stream from the MediaServer end and plays the video.
Preferably, the method further comprises the following steps:
step S5: the Web end monitors the dragging of a user to a video picture;
step S6: after a dragging event is received, analyzing corresponding cradle head operation data;
step S7: transmitting the holder operation data to a LiveServer end;
step S8: and the LiveServer end receives the cradle head operation data, encapsulates the cradle head operation data into a format of a GB/T28181 protocol, and sends the cradle head operation data to the corresponding GB/T28181 equipment to complete cradle head control.
The invention adopts a multi-process architecture and has stable performance. Because the video streams have compatibility problems, each video stream correspondingly starts a TranscodeServer process, so that if one video stream is wrong, the normal playing of other video streams is not influenced, and meanwhile, the other video streams can be normally converted.
The invention carries out data processing by the mutual cooperation of a plurality of servers, converts the GB/T28181 protocol into a protocol (HTTP-FLV, WebSocket-FLV) which can be transmitted by HTTP, thereby realizing the video viewing and control of a browser end.
The above step S1: the LiveServer end realizes an SIP protocol through node. js, establishes a session with GB/T28181 equipment, calls a video stream, and receives and processes a Web request, wherein the step of receiving and processing the Web request comprises the following steps:
step S11: realizing SIP protocol through TCP/UDP protocol in node.js, and packaging interface;
starting to monitor SIP information;
stop receiving SIP message;
OnMessage receives SIP message, formats the message and informs the monitor in JavaScript;
send sends SIP message.
Step S12: establishing a connection with a GB/T28181 device by using a SIP protocol;
monitoring a local port by SIP protocol, and waiting for registration of GB/T28181 equipment;
OnMessage receives the registration message and authenticates.
Step S13: acquiring GB/T28181 equipment information and channel information through an SIP protocol, and recording the information and the channel information into a file;
send obtains the equipment information and channel information through SIP protocol;
and caching the acquired device information and channel information data into a file so as to continue to use the data next time.
Step S14: acquiring a monitoring real-time video stream through an SIP (session initiation protocol);
calling video stream information of GB/T28181 equipment through a SIP protocol;
receiving video stream information of GB/T28181 equipment through SIP (session initiation protocol) OnMessage;
analyzing video stream information, starting a TranscodeServer end, transmitting parameters to the TranscodeServer end, starting monitoring by the TranscodeServer end, and waiting for the video stream information;
and informing the GB/T28181 equipment to transmit the video stream.
Step S15: starting a TranscodeServer, and transmitting GB/T28181 equipment information and video stream information to a TranscodeServer end;
newly building a PIPE pipeline (an interprocess communication mechanism), starting a TranscodeServer, and waiting for a TranscodeServer end to be connected to the pipeline;
and after the TranscodeServer end is connected, transmitting the equipment information and GB/T28181 video stream information to the TranscodeServer end.
Step S16: controlling GB/T28181 equipment through a SIP protocol;
receiving a request of a web end, and encapsulating data into a format of a GB/T28181 protocol;
send sends message (SIP) to GB/T28181 equipment to realize control equipment.
Step S17: receiving a front-end Web request;
receiving information requesting to return to the GB/T28181 equipment;
and receiving the request to return the video stream information.
The SIP protocol in the invention is written by JavaScript, and since JavaScript is easy to debug, if problems occur, the system is easy to locate, thereby being convenient for system maintenance.
In a further embodiment of the present invention, the step S2: the method includes that a TranscodeServer end obtains a video stream through FFmpeg, converts the video stream into FLV and pushes the FLV to a mediaServer end, and comprises the following steps:
step S21: acquiring equipment information and video stream information transmitted by a LiveServer end through a pipeline;
step S22: starting an acquisition thread according to the parameters, acquiring video stream information through a TCP (transmission control protocol) protocol or a UDP (user datagram protocol), caching the acquired video stream information into a circular queue, and waiting for a conversion thread to use;
step S23: starting a conversion thread, and analyzing audio and video data information through FFmpeg;
judging whether the video data is directly used if the H264 coding is adopted, or else, converting the video data into the H264 coding;
judging whether the audio data are directly used if AAC coding is adopted, or else, converting the audio data into AAC coding or discarding the audio data;
and after the audio and video data conversion is finished, packaging the audio and video data into an FLV format, and pushing the FLMPEG format to a mediaServer end through an RTMP protocol (real-time transport protocol).
In a further embodiment of the present invention, the step S3: the method for encapsulating the RTMP video stream into the HTTP-FLV and the WebSocket-FLV and distributing the HTTP-FLV and the WebSocket-FLV to the Web end comprises the following steps:
receiving video stream information of an RTMP protocol, and converting the video stream information into an HTTP-FLV protocol or a WebSocket-FLV protocol;
the same video stream can be forwarded to a plurality of Web terminals at the same time, so that server resources are saved.
The invention can realize that the browsers of the PC end and the mobile end are simultaneously supported to view the video, so that the browser can view the GB28181 video.
In a further embodiment of the present invention, the step S4: the Web end acquires the video stream from the MediaServer end, and the video playing comprises the following steps:
connecting a LiveServer end through a WebScoket to obtain HTTP-FLV and WebSocket-FLV addresses of a corresponding video stream at a MediaServer end;
connecting a MediaServer terminal through the acquired address to acquire a video stream, decoding an H264 video and an AAC audio through flv.js, and then playing the corresponding video stream through an MSE (media Source extensions) interface of a browser.
By the method for viewing the GB/T28181 protocol-supporting equipment in the Chrome browser, the monitoring video and the historical video of the GB/T28181 equipment can be viewed through the Chrome browser such as Chrome and the like on operating systems such as Windows, Linux, Android, Mac and IOS, and further the GB/T28181 equipment is controlled.
The method for viewing the device supporting the GB/T28181 protocol in the Chrome browser is described above. Moreover, the technical features disclosed above are not limited to the combinations with other features disclosed, and other combinations between the technical features can be performed by those skilled in the art according to the purpose of the present invention, so as to achieve the purpose of the present invention.
Claims (8)
1. A method for viewing a device supporting GB/T28181 protocol in a Chrome browser is characterized by comprising the following steps:
the LiveServer end realizes an SIP protocol through node. js, establishes a session with GB/T28181 equipment, calls a video stream, and receives and processes a Web request;
the TranscodeServer end acquires a video stream, converts the video stream into FLV through FFmpeg and pushes the FLV to a mediaServer end;
the MediaServer end receives RTMP video stream, packages the RTMP video stream into HTTP-FLV and WebSocket-FLV and distributes the HTTP-FLV and the WebSocket-FLV to the Web end;
the Web end acquires a video stream from the MediaServer end and plays the video;
wherein, the TranscodeServer end obtains the video stream through FFmpeg, converts the video stream into FLV and pushes the FLV to the mediaServer end, and comprises:
acquiring equipment information and video stream information transmitted by a LiveServer end through a pipeline;
starting an acquisition thread according to the parameters, acquiring video stream information through a TCP (transmission control protocol) protocol or a UDP (user datagram protocol), caching the acquired video stream information into a circular queue, and waiting for a conversion thread to use;
starting a conversion thread, and analyzing audio and video data information through FFmpeg;
the starting of the conversion thread, and the analysis of the audio and video data information through FFmpeg comprises the following steps:
judging whether the video data is directly used if the H264 coding is adopted, or else, converting the video data into the H264 coding;
judging whether the audio data are directly used if AAC coding is adopted, or else, converting the audio data into AAC coding or discarding the audio data;
and after the audio and video data conversion is finished, packaging the audio and video data into an FLV format, and pushing the FLMpeg to a mediaServer end through an RTMP protocol.
2. The method for viewing in Chrome browser of claim 1, wherein said device supporting GB/T28181 protocol further comprises the following steps:
the Web end monitors the dragging of a user to a video picture;
after a dragging event is received, analyzing corresponding cradle head operation data;
transmitting the holder operation data to a LiveServer end;
and the LiveServer end receives the cradle head operation data, encapsulates the cradle head operation data into a format of a GB/T28181 protocol, and sends the cradle head operation data to the corresponding GB/T28181 equipment to complete cradle head control.
3. The method for viewing in Chrome browser by device supporting GB/T28181 protocol according to claim 1, wherein said LiveServer end implements SIP protocol by node.
Realizing SIP protocol through TCP/UDP protocol in node.js, and packaging interface;
establishing a connection with a GB/T28181 device by using a SIP protocol;
acquiring GB/T28181 equipment information and channel information through an SIP protocol, and recording the information and the channel information into a file;
acquiring a monitoring real-time video stream through an SIP (session initiation protocol);
starting a TranscodeServer, and transmitting GB/T28181 equipment information and video stream information to a TranscodeServer end;
controlling GB/T28181 equipment through a SIP protocol;
a front-end Web request is received.
4. The method for viewing in Chrome browser of claim 3, wherein said device supporting GB/T28181 protocol implements SIP protocol by TCP/UDP protocol in node.js, and encapsulating interfaces includes:
starting to monitor SIP information;
stopping receiving the SIP message;
receiving SIP message, formatting the message and informing a monitor in JavaScript;
the SIP message is sent.
5. The method for viewing in a Chrome browser of a device supporting GB/T28181 protocol according to claim 3, wherein said establishing a connection with a GB/T28181 device using SIP protocol includes:
monitoring a local port through an SIP protocol, and waiting for registration of GB/T28181 equipment;
the registration message is received and authenticated.
6. The method for viewing in Chrome browser of claim 3, wherein said obtaining and monitoring real-time video stream through SIP protocol includes:
calling video stream information of GB/T28181 equipment through a SIP protocol;
receiving video stream information of GB/T28181 equipment through a SIP protocol;
analyzing video stream information, starting a TranscodeServer end, transmitting parameters to the TranscodeServer end, starting monitoring by the TranscodeServer end, and waiting for the video stream information;
and informing the GB/T28181 equipment to transmit the video stream.
7. The method for viewing in Chrome browser of claim 1, wherein said MediaServer end receives RTMP video stream, encapsulates it into HTTP-FLV and WebSocket-FLV, and distributes it to Web end includes:
receiving video stream information of an RTMP protocol, and converting the video stream information into an HTTP-FLV protocol or a WebSocket-FLV protocol;
and simultaneously forwarding the same video stream to a plurality of Web terminals.
8. The method for viewing in Chrome browser of claim 1, wherein the Web end obtaining video stream from MediaServer end and playing video includes:
connecting a LiveServer end through a WebScoket to obtain HTTP-FLV and WebSocket-FLV addresses of a corresponding video stream at a MediaServer end;
and connecting the MediaServer terminal through the acquired address to acquire a video stream, decoding an H264 video and an AAC audio through flv.js, and then playing the corresponding video stream through an MSE interface of a browser.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011632751.7A CN112866199B (en) | 2020-12-31 | 2020-12-31 | Method for viewing GB/T28181 protocol-supporting equipment in Chrome browser |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011632751.7A CN112866199B (en) | 2020-12-31 | 2020-12-31 | Method for viewing GB/T28181 protocol-supporting equipment in Chrome browser |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112866199A CN112866199A (en) | 2021-05-28 |
| CN112866199B true CN112866199B (en) | 2021-11-05 |
Family
ID=76000155
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011632751.7A Active CN112866199B (en) | 2020-12-31 | 2020-12-31 | Method for viewing GB/T28181 protocol-supporting equipment in Chrome browser |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112866199B (en) |
Families Citing this family (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113329040B (en) * | 2021-08-03 | 2021-11-02 | 江苏怀业信息技术股份有限公司 | Protocol conversion method and device in media stream forwarding process |
| CN114071242A (en) * | 2021-11-16 | 2022-02-18 | 重庆赛迪奇智人工智能科技有限公司 | Video playing method, video pushing device and electronic equipment |
| CN114745229B (en) * | 2022-02-15 | 2024-04-12 | 成都臻识科技发展有限公司 | Embedded AI video gateway and implementation method thereof |
| CN115174545A (en) * | 2022-06-29 | 2022-10-11 | 广州鲁邦通物联网科技股份有限公司 | Plug flow web playing method and system based on national standard GB28181 |
| CN116032922A (en) * | 2022-12-27 | 2023-04-28 | 浪潮云信息技术股份公司 | Cloud deck control method, device and system and computer readable storage medium |
Family Cites Families (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US10412130B2 (en) * | 2016-04-04 | 2019-09-10 | Hanwha Techwin Co., Ltd. | Method and apparatus for playing media stream on web browser |
| CN109088887A (en) * | 2018-09-29 | 2018-12-25 | 北京金山云网络技术有限公司 | A kind of decoded method and device of Streaming Media |
| CN111050225A (en) * | 2019-12-03 | 2020-04-21 | 安徽四创电子股份有限公司 | Network architecture and method for playing real-time video in web browser |
| CN111683293A (en) * | 2020-05-31 | 2020-09-18 | 杭州视在数科信息技术有限公司 | Method for playing H.265 video across browsers based on HTTP-FLV protocol |
| CN111711870B (en) * | 2020-06-09 | 2022-03-25 | 杭州当虹科技股份有限公司 | Real-time streaming transmission method across network boundary |
-
2020
- 2020-12-31 CN CN202011632751.7A patent/CN112866199B/en active Active
Also Published As
| Publication number | Publication date |
|---|---|
| CN112866199A (en) | 2021-05-28 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN112866199B (en) | Method for viewing GB/T28181 protocol-supporting equipment in Chrome browser | |
| CN110661752A (en) | Plug-in-free real-time video playing system and method | |
| CN102263959B (en) | Direct broadcast transfer method and system | |
| US10015221B2 (en) | Content server media stream management | |
| KR102540459B1 (en) | Method and Device for media streaming between server and client using RTP/RTSP standard protocol | |
| CN108769616A (en) | A kind of real-time video based on RTSP agreements is without plug-in unit method for previewing and system | |
| WO2009128515A1 (en) | Gateway device, method, and program | |
| CN102065339A (en) | Method and system for playing audio and video media stream | |
| CN103581699A (en) | Video playing method, streaming media server and streaming media playing system | |
| JP2006525693A (en) | Signaling method of client speed function in multimedia streaming | |
| CN103916678A (en) | Multimedia data transcoding method, transcoding device and multimedia data play system | |
| KR101821123B1 (en) | Method and apparatus for playing media stream on web-browser | |
| EP2827596A1 (en) | Transmitting and receiving method of multimedia video data and corresponding device | |
| CN102065269A (en) | Method for carrying out video session, video session system and set top boxes (STBs) | |
| CN102347947A (en) | Streaming media adaptor, streaming media network interaction system and method | |
| KR101821124B1 (en) | Method and apparatus for playing media stream on web-browser | |
| CN103873948A (en) | Streaming media self-adaption matching transmission method, system and server | |
| CN115334273A (en) | Protocol conversion audio and video communication method and system | |
| KR101164746B1 (en) | System and method for compensating consecutive palyback delay of video playback service based on real-time streaming protocol | |
| CN112312221A (en) | Audio and video playing method, storage medium and device | |
| CN106790030B (en) | Multi-screen cooperative audio transmission server, client, system and processing method thereof | |
| WO2018129758A1 (en) | Monitor video distribution method and device thereof | |
| CN102378064A (en) | Method and device for realizing traversal of network address translators (NAT) in internet protocol television (IPTV) network | |
| CN114339146B (en) | Audio and video monitoring method and device, electronic equipment and computer readable storage medium | |
| CN115865884A (en) | Network camera data access device and method, network camera and medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| CB02 | Change of applicant information |
Address after: 100015 floor 105, floor 1, building 82, No. 10, Jiuxianqiao Road, Chaoyang District, Beijing Applicant after: BEIJING YOUNUO TECHNOLOGY Co.,Ltd. Address before: 100102 No.308, 3rd floor, building 14, Huajiadi Beili, Chaoyang District, Beijing Applicant before: BEIJING YOUNUO TECHNOLOGY Co.,Ltd. |
|
| CB02 | Change of applicant information | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant | ||
| CP03 | Change of name, title or address |
Address after: 100015 floor 105, floor 1, building 82, No. 10, Jiuxianqiao Road, Chaoyang District, Beijing Patentee after: Beijing Youhao Technology Co.,Ltd. Country or region after: China Address before: 100015 floor 105, floor 1, building 82, No. 10, Jiuxianqiao Road, Chaoyang District, Beijing Patentee before: BEIJING YOUNUO TECHNOLOGY Co.,Ltd. Country or region before: China |