阅读说明：本技术 视频解码方法、推流方法及系统 (Video decoding method, stream pushing method and system ) 是由 刘光亮 吴怡生 袁镇锋 于 2020-05-26 设计创作，主要内容包括：本发明提供了一种视频解码方法、推流方法及系统,方法应用于浏览器,其中,浏览器配置有HEVC解码器的支持信息,浏览器的WebRTC项目中配置有H265接口,通过ICE协议与云服务器建立WebRTC连接；接收云服务器发送的目标视频的SRTP流,SRTP流为云服务器将获取的目标视频的H265码流进行处理得到的数据流；解密SRTP流,得到RTP流；解析RTP流,确定RTP流的RTP负载类型为H265格式；调用预设的H265解码器对RTP流进行解码,得到目标视频对应的图片数据；H265解码器为基于HEVC解码器完成H265格式初始化后的解码器。本申请能够通过WebRTC传输H265视频并实现解码。(The invention provides a video decoding method, a stream pushing method and a system, wherein the method is applied to a browser, wherein the browser is configured with support information of an HEVC decoder, a WebRTC project of the browser is configured with an H265 interface, and WebRTC connection is established with a cloud server through an ICE protocol; receiving an SRTP (sequence request transport protocol) stream of a target video sent by a cloud server, wherein the SRTP stream is a data stream obtained by processing an H265 code stream of the acquired target video by the cloud server; decrypting the SRTP stream to obtain an RTP stream; analyzing the RTP stream, and determining that the RTP load type of the RTP stream is in an H265 format; calling a preset H265decoder to decode the RTP stream to obtain picture data corresponding to the target video; the H265decoder is a decoder that completes initialization of the H265 format based on HEVC decoder. The H265 video can be transmitted and decoded by WebRTC.)

1. A video decoding method is applied to a browser, wherein the browser is configured with support information of an HEVC decoder, and an H265 interface is configured in a WebRTC project of the browser, and the method comprises the following steps:

establishing WebRTC connection with a cloud server through an ICE protocol;

receiving an SRTP (sequence request transport protocol) stream of a target video sent by a cloud server, wherein the SRTP stream is a data stream obtained by processing an H265 code stream of the acquired target video by the cloud server;

decrypting the SRTP stream to obtain an RTP stream;

analyzing the RTP stream, and determining that the RTP load type of the RTP stream is in an H265 format;

calling a preset H265decoder to decode the RTP stream to obtain picture data corresponding to the target video; the H265decoder is a decoder after H265 format initialization is completed on the basis of an HEVC decoder.

2. The method according to claim 1, wherein before the step of receiving the SRTP stream of the target video sent by the cloud server, the method further comprises:

receiving a parameter negotiation request sent by the cloud server; the parameter negotiation request carries H265 format parameter information of the target video;

sending a response result corresponding to the parameter negotiation request to the cloud server; the response result is added with response support supporting the H265 format in advance;

initializing H265 format of HEVC decoder based on the parameter negotiation request and the response result.

3. The method according to claim 1, wherein the step of parsing the H265 code stream and determining that the load type of the H265 code stream is in an H265 format comprises:

analyzing the H265 code stream to obtain analysis information;

judging whether a load type value in an RTP represents a preset H265 load type or not based on the analysis information; the H265 load type is pre-agreed by the cloud server;

if so, determining the load type of the H265 code stream to be in an H265 format.

4. The method according to claim 1, further comprising, after the step of obtaining picture data corresponding to the target video:

rendering the picture data corresponding to the target video;

and displaying the rendered picture.

5. A video plug-flow method is applied to a cloud server, wherein plug-flow parameters of an H265 video are prestored in the cloud server, and the method comprises the following steps:

acquiring a video stream of a target video;

if the client of the video stream is a target browser, carrying out H265 video coding on the video stream to obtain an H265 code stream; the target browser is configured with support information of an HEVC decoder, and a H265 interface is configured in a WebRTC project of the browser;

converting the H265 code stream into an SRTP stream, and sending the SRTP stream to the target browser, so that the target browser calls a preset H265decoder to decode the H265 code stream based on the SRTP stream, and picture data corresponding to the target video is obtained; the H265decoder is a decoder after H265 format initialization is completed on the basis of an HEVC decoder.

6. The method of claim 5, wherein the cloud servers comprise a master cloud server and a media server; the main cloud server is used for acquiring an H265 code stream of a target video and sending the H265 code stream to the media server, and the media server is used for communicating with the target browser.

7. The method according to claim 6, wherein the video stream of the target video is a video stream of the target video acquired by the main cloud server; before the step of converting the H265 code stream into the SRTP stream, the method further includes:

and sending the H265 code stream to the media server through the main cloud server.

8. The method of claim 7, wherein the steps of converting the H265 bitstream into an SRTP stream and sending the SRTP stream to the target browser are the media server converting the H265 bitstream into an SRTP stream and sending the SRTP stream to the target browser.

9. A video decoding system, the system comprising: a cloud server and a browser;

the cloud server is connected with the browser through a WebRTC protocol through an ICE protocol;

the cloud server is used for executing the video plug flow method according to any one of claims 5-8;

the browser is adapted to perform the video decoding method of any of claims 1-4.

10. The system of claim 9, wherein the cloud server comprises: a master cloud server and a media server.

11. An electronic device comprising a processor and a memory, the memory storing computer-executable instructions executable by the processor, the processor executing the computer-executable instructions to implement the method of any of claims 1-4 or 5-8.

12. A computer-readable storage medium having stored thereon computer-executable instructions that, when invoked and executed by a processor, cause the processor to implement the method of any of claims 1-4 or 5-8.

Technical Field

The present invention relates to the field of encoding and decoding technologies, and in particular, to a video decoding method, a stream pushing method, and a system.

Background

The RTMP (Real Time Messaging Protocol) is based on a TCP (Transmission Control Protocol), has high Transmission cost, and has a significant problem in the case of a high packet loss rate in a weak network environment, and is an Adobe proprietary Protocol in which Adobe is not updated any more. However, for developing a private Protocol based on UDP (User Datagram Protocol), the development cost is high, the private Protocol cannot be evolved with a community, only a few developers of a company maintain the private Protocol, and the possibility of BUG existence is high. Due to the inherent drawbacks of the RTMP and UDP proprietary protocols, WebRTC (Web Real-Time Communication) is currently used to transmit video streams. However, currently, WebRTC only supports three codecs of H264, VP8, and VP9, and does not support H265 codec.

Disclosure of Invention

The invention aims to provide a video decoding method, a stream pushing method and a system, which can transmit H265 video through WebRTC and realize decoding.

The embodiment of the invention provides a video decoding method, which is applied to a browser, wherein the browser is configured with support information of an HEVC decoder, and a WebRTC project of the browser is configured with an H265 interface, and the method comprises the following steps: establishing WebRTC connection with a cloud server through an ICE protocol; receiving an SRTP (sequence request transport protocol) stream of a target video sent by a cloud server, wherein the SRTP stream is a data stream obtained by processing an H265 code stream of the acquired target video by the cloud server; decrypting the SRTP stream to obtain an RTP stream; analyzing the RTP stream, and determining that the RTP load type of the RTP stream is in an H265 format; calling a preset H265decoder to decode the RTP stream to obtain picture data corresponding to the target video; the H265decoder is a decoder that completes initialization of the H265 format based on HEVC decoder.

Further, before the step of receiving the SRTP stream of the target video sent by the cloud server, the method further includes: receiving a parameter negotiation request sent by a cloud server; the parameter negotiation request carries H265 format parameter information of the target video; sending a response result corresponding to the parameter negotiation request to the cloud server; response support supporting the H265 format is added in the response result in advance; initialization of the H265 format of the HEVC decoder is performed based on the parameter negotiation request and the response result.

Further, the step of analyzing the H265 code stream and determining that the load type of the H265 code stream is in the H265 format includes: analyzing the H265 code stream to obtain analysis information; judging whether a load type value in an RTP represents a preset H265 load type or not based on the analysis information; the H265 load type is predetermined by the cloud server; if so, determining the load type of the H265 code stream to be in an H265 format.

Further, after the step of obtaining the picture data corresponding to the target video, the method further includes: rendering picture data corresponding to the target video; and displaying the rendered picture.

In a second aspect, an embodiment of the present application further provides a video stream pushing method, where the method is applied to a cloud server, where a stream pushing parameter of an H265 video is prestored in the cloud server, and the method includes: acquiring a video stream of a target video; if the client of the video stream is the target browser, carrying out H265 video coding on the video stream to obtain an H265 code stream; the target browser is configured with support information of an HEVC decoder, and a H265 interface is configured in a WebRTC project of the target browser; converting the H265 code stream into an SRTP stream, and sending the SRTP stream to a target browser so that the target browser calls a preset H265decoder to decode the H265 code stream based on the SRTP stream to obtain picture data corresponding to a target video; the H265decoder is a decoder that completes initialization of the H265 format based on HEVC decoder.

Further, the cloud server includes a main cloud server and a media server; the main cloud server is used for acquiring the H265 code stream of the target video and sending the H265 code stream to the media server, and the media server is used for communicating with the target browser.

Further, the video stream for acquiring the target video is a video stream for acquiring the target video through the main cloud server; before the step of converting the H265 code stream into the SRTP stream, the method further includes: and sending the H265 code stream to a media server through the main cloud server.

Further, the step of converting the H265 code stream into the SRTP stream and sending the SRTP stream to the target browser is that the media server converts the H265 code stream into the SRTP stream and sends the SRTP stream to the target browser.

In a third aspect, an embodiment of the present application further provides a video decoding system, where the system includes: a cloud server and a browser; the cloud server is connected with the browser through a WebRTC protocol through an ICE protocol; the cloud server is used for executing the video plug flow method according to any one of claims 5 to 8; browser for performing the video decoding method according to any one of claims 1 to 4.

Further, the cloud server includes: a master cloud server and a media server.

In a fourth aspect, embodiments of the present application further provide an electronic device, including a processor and a memory, where the memory stores computer-executable instructions capable of being executed by the processor, and the processor executes the computer-executable instructions to implement the method of any one of the first aspect or the second aspect.

In a fifth aspect, embodiments of the present application further provide a computer-readable storage medium storing computer-executable instructions that, when invoked and executed by a processor, cause the processor to implement the method of any one of the first or second aspects.

In the video decoding method provided by the embodiment of the invention, a browser establishes WebRTC connection with a cloud server through an ICE protocol; then receiving an SRTP stream of the target video sent by the cloud server, wherein the SRTP stream is a data stream obtained by processing the acquired H265 code stream of the target video by the cloud server; obtaining an RTP stream by decrypting the SRTP stream; then, analyzing the RTP stream, and determining that the RTP load type of the RTP stream is in an H265 format; finally, a preset H265decoder is called to decode the RTP stream to obtain picture data corresponding to the target video; because the H265decoder is a decoder after H265 format initialization is completed based on an HEVC decoder, the browser is configured with support information of the HEVC decoder, and a WebRTC project of the browser is configured with an H265 interface, the H265 video can be transmitted by the WebRTC and the H265 video decoding is realized.

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 some embodiments of the present invention, and other drawings can be obtained by those skilled in the art without creative efforts.

Fig. 1 is a flowchart of a video decoding method according to an embodiment of the present invention;

fig. 2 is a flowchart of a video stream pushing method according to an embodiment of the present invention;

fig. 3 is a block diagram of a video decoding system according to an embodiment of the present invention;

fig. 4 is a structural diagram of an electronic device according to an embodiment of the present invention.

Detailed Description

The technical solutions of the present invention will be described clearly and completely with reference to the following embodiments, and it should be understood that the described embodiments are some, but not all, embodiments of the present invention. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.

The background art of the present application is first introduced: the cloud game is a game mode based on cloud computing, in a cloud game mode, all games run on a cloud server, and rendered game pictures are compressed and coded and then transmitted to a user for operation through a network. How to transmit the pictures to the client is the core technology which needs to be considered for realizing the cloud game. The picture compression coding is also called video coding, and the coded video is decoded to obtain the picture after reaching the client. The current video coding is in the MPEG series and h.26x series.

H.265 (High Efficiency Video Coding, HEVC) is a new generation of Video Coding technology. The method is around the existing video coding standard H.264, retains certain original technologies, improves and optimizes certain aspects such as code stream, coding quality, time delay and the like by using a new technology, improves compression efficiency, enhances robustness and error recovery capability, reduces real-time delay, reduces complexity and the like. The difference between H.265 and H.264 lies in that H.265 has higher compression efficiency, lower transmission code rate and better video image quality, and realizes that the transmission bandwidth, the storage and the cost of the monitoring video are halved, thereby bringing better experience to people.

WebRTC, namely Web Real-Time Communication, Web Real-Time Communication, realizes Real-Time Communication of audio and video in a browser and mobile application, has wide application range, and can conveniently realize Real-Time Communication through the browser without installing plug-ins and clients. WebRTC provides APIs on all platforms including Web, iOS, Android, Mac, Windows and Linux, and ensures the consistency of the APIs on all platforms. The wide versatility makes WebRTC the technology of creating real-time communication in the future the first choice.

Chrome is a Google-launched open source browser project, an engine behind the Google Chrome browser, with the purpose of creating a secure, stable, and fast general browsing. The new function is firstly realized on the Chrome and is applied to the Chrome after being verified, so that the function of the Chrome is relatively lagged but stable. The update speed of the Chromium is very fast, and a new development version is released every few hours. Meanwhile, a plurality of desktop applications take the chromosome as an inner core and utilize rich functions provided by the chromosome, such as Electron.

In view of the inherent drawbacks of the RTMP and UDP proprietary protocols, WebRTC is currently used to transmit video streams. However, WebRTC under a Chromium engine only supports three codecs of H264, VP8 and VP9, and does not support H265 codec. Based on this, the embodiment of the present invention provides a decoding method, a stream pushing method, a device and a system for an H265 video, so as to implement decoding of the H265 video based on WebRTC under a chroma engine.

To facilitate understanding of the present embodiment, a video decoding method disclosed in the embodiments of the present application will be described in detail first.

Fig. 1 shows a flowchart of a video decoding method provided by an embodiment of the present invention, where the method is applied to a browser, where the browser is configured with support information of an HEVC decoder, and a WebRTC project of the browser is configured with an H265 interface, and the method includes the following steps:

and step S102, establishing WebRTC connection with the cloud server through an ICE protocol.

Step S104, receiving the SRTP stream of the target video sent by the cloud server.

The SRTP stream is a data stream obtained by processing an obtained H265 code stream of the target video by the cloud server; the target video can be a cloud game video or a live video.

In a specific implementation, before the SRTP stream is transmitted, a WebRTC connection is established between the cloud server and the browser through an ICE protocol. On the basis of connection, the cloud server acquires a video stream of a target video, encodes the video stream into an H265 code stream, and sends the H265 code stream to the browser.

And step S106, decrypting the SRTP stream to obtain the RTP stream.

And after receiving the SRTP stream of the target video sent by the cloud server, the browser performs decryption operation to obtain an RTP stream.

Step S108, analyzing the RTP stream, and determining that the RTP load type of the RTP stream is in an H265 format.

During specific implementation, firstly analyzing the H265 code stream to obtain analysis information; judging whether a load type value in an RTP represents a preset H265 load type or not based on the analysis information; the H265 load type is predetermined by the cloud server; if so, determining the load type of the H265 code stream to be in an H265 format.

Since the H265 video specializes the RTP Payload Format, the RTP Payload Format may be processed by adding a judgment of if (Payload. code ()) to the onreceivedpayaddata of the key processing entry RTP _ video _ stream _ receiver.cc. This is a decision code in the chroma, and in RTP there is a field to identify what type of data is carried by the RTP stream. If the cloud server has set this field payload _ type value, and therefore, the browser parses this value, it can determine that the RTP payload type of the RTP stream is in the H265 format.

Step S110, a preset H265decoder is called to decode the RTP stream to obtain picture data corresponding to the target video; the H265decoder is a decoder that completes initialization of the H265 format based on HEVC decoder.

If the RTP load type of the RTP stream is determined to be in the H265 format after the parsing, the RTP stream may be decoded by a preset H265decoder to obtain the picture data corresponding to the target video. The H265decoder preset here is a decoder after H265 format initialization is completed based on HEVC decoder. For initialization of the H265 format, first, an answer and an offer are exchanged between the cloud server and the browser. Codec formats have been agreed by answer and offer, and a browser is configured with support information of an HEVC decoder, and a WebRTC project of the browser is configured with an H265 interface, so that the HEVC decoder can be called, and decoding of an H265 video is realized through the H265 video decoder.

In the video decoding method provided by the embodiment of the application, a browser establishes WebRTC connection with a cloud server through an ICE protocol; then receiving an SRTP stream of the target video sent by the cloud server, wherein the SRTP stream is a data stream obtained by processing the acquired H265 code stream of the target video by the cloud server; obtaining an RTP stream by decrypting the SRTP stream; then, analyzing the RTP stream, and determining that the RTP load type of the RTP stream is in an H265 format; finally, a preset H265decoder is called to decode the RTP stream to obtain picture data corresponding to the target video; because the H265decoder is a decoder after H265 format initialization is completed based on an HEVC decoder, the browser is configured with support information of the HEVC decoder, and a WebRTC project of the browser is configured with an H265 interface, the H265 video can be transmitted by the WebRTC and the H265 video decoding is realized.

According to the setting of webrtc, before transmitting the video stream, the browser and the cloud server need to exchange an answer and an offer once, that is, a Session Description Protocol (SDP) is completed. The following describes in detail the exchange answer and offer and decoder initialization process between the browser and the cloud server.

(1) Receiving a parameter negotiation request sent by a cloud server; the parameter negotiation request carries the H265 format parameter information of the target video.

Specifically, the cloud server sends an offer to the browser, where the offer includes information related to audio and video in the media, and the offer includes related information in an H265 format, such as rtp map.

offfer: the session description object describes the request/response of the first handshake. The session process goes from the sender to the receiver. Important here is the codec capability in the response, such as:

a＝rtpmap:96H264/90000；

a＝fmtp:96；

packetization-mode＝1；level-asymmetry-allowed＝1；profile-level-id＝42e01f；

so add H265 format to offer:

a＝rtpmap:100H265/90000；

(2) sending a response result corresponding to the parameter negotiation request to the cloud server; response support supporting the H265 format is added in the response result in advance;

specifically, after receiving the offer, the browser records the information and sends back the answer SDP. an answer: the SDP protocol requests that the content is contained in an attribute SDP. In other words, this session description describes the agreed-upon configuration and will be sent to complete the negotiation.

(3) Initialization of the H265 format of the HEVC decoder is performed based on the parameter negotiation request and the response result. I.e. the H265 related decoder is initialized based on the information negotiated in the first two steps.

In another embodiment, after the step of obtaining the picture data corresponding to the target video, the method further includes the following steps: rendering picture data corresponding to the target video; and displaying the rendered picture.

In a preferred embodiment, the browser is a browser with a chrome engine installed therein, and the following description of the video decoding process is performed by taking the browser with the chrome engine installed therein as an example:

in a browser provided with a Chromium engine, recompiling a support electron source code of the Chromium engine in advance, for example, configuring support information of an HEVC decoder in an ffmpeg project of the Chromium engine; the H265 interface is configured in the WebRTC project of the chrome engine.

Specifically, an H265 directory is added under a module/video _ coding/codes/directory in a WebRTC project, a WebRTC interface is realized, and an H265DecoderImpl class is realized. Since the third-party library ffmpeg in the chroma does not turn on the HEVC support by default, the construction configuration of ffmpeg under the chroma is modified, and the support of HEVC is added. Specifically, an ff _ hevc _ decoder is added in a codec _ list array in the codec _ list.c, and a make file is modified to add a hevc decoding function file.

Based on the modification, the browser provided with the chrome engine firstly establishes WebRTC connection with the cloud server through an ICE protocol; then receiving an SRTP stream of a target video sent by a cloud server; then, the SRTP stream is decrypted to obtain an RTP stream; further, analyzing the RTP stream, and calling a preset H265decoder to decode the RTP stream to obtain picture data corresponding to the target video when the RTP load type of the RTP stream is determined to be in an H265 format; since the H265decoder is a decoder that completes initialization of the H265 format based on HEVC decoder. Therefore, through the recompiling of the electron source code and the initialization of the decoder, the H265 video stream can be transmitted and decoded through WebRTC under a Chromium engine.

Based on the method embodiment of the browser side, the embodiment of the present application further provides a video plug-streaming method, where the method is applied to a cloud server, and a plug-streaming parameter of an H265 video is prestored in the cloud server, and the video plug-streaming method includes the following steps, as shown in fig. 2:

step S202, acquiring a video stream of a target video;

step S204, if the client of the video stream is a target browser, carrying out H265 video coding on the video stream to obtain an H265 code stream; the target browser is configured with support information of an HEVC decoder, and a H265 interface is configured in a WebRTC project of the target browser;

here, the H265 video coding of the video stream can be implemented by software or hardware, such as: the video stream is H265 video encoded by ffmpeg or GPU graphics processor.

Step S206, converting the H265 code stream into an SRTP stream, and sending the SRTP stream to a target browser so that the target browser calls a preset H265decoder to decode the H265 code stream based on the SRTP stream to obtain picture data corresponding to a target video; the H265decoder is a decoder that completes initialization of the H265 format based on HEVC decoder.

After receiving the encrypted SRTP stream sent by the cloud server, the target browser may further perform operations such as decryption, parsing, decoding, and the like, and for a specific implementation process, reference may be made to the above method embodiment, which is not described herein again.

According to the video stream pushing method provided by the embodiment of the application, the stream pushing process of the H265 video can be realized by modifying or setting parameters in the cloud server in advance.

In a preferred embodiment, the cloud server may include a main cloud server and a media server; the main cloud server is used for acquiring the H265 code stream of the target video and sending the H265 code stream to the media server, and the media server is used for communicating with the browser. The video stream for acquiring the target video may be: acquiring a video stream of a target video through a main cloud server; before the step of converting the H265 code stream into the SRTP stream, the method further includes: and sending the H265 code stream to a media server through the main cloud server. The step of converting the H265 code stream into the SRTP stream and sending the SRTP stream to the target browser may be: converting the H265 code stream into an SRTP stream through the media server, and sending the SRTP stream to the target browser.

In specific implementation, firstly, the main cloud server obtains a video stream of a target video, then encodes the video stream into an H265 code stream, and sends the H265 code stream to the media server. After the media server receives the H265 code stream of the target video, it is further packaged as an SRTP stream, that is, it is encrypted, so that the security of the data is improved, and finally the packaged SRTP stream is sent to a target browser, for example, a browser with a chrome engine is installed, so that the stream pushing process of the cloud server is completed, and then the browser performs a decoding process again, which may refer to the above-mentioned embodiment of the video decoding method, and is not described herein again.

Based on the foregoing method embodiment, an embodiment of the present application further provides a video decoding system, referring to a structural block diagram of the video decoding system shown in fig. 3, where the system includes: cloud server 32 and browser 34; the cloud server 32 is in WebRTC connection with the browser 34 through the ICE protocol; the cloud server 32 is configured to execute the video plug flow method; the browser 34 is used to perform the video decoding method described above.

In a preferred embodiment, the cloud server 32 includes: a master cloud server 322 and a media server 324. The main cloud server 322 is configured to obtain an H265 code stream of the target video and send the H265 code stream to the media server 324, and the media server 324 is configured to communicate with the browser 34.

In order to enable the WebRTC to support decoding rendering of the H265, an encoding stream pushing part of a cloud server, an SDP response part in WebRTC ICE establishment, an RTP load analysis part, a Chromium H265 soft decoding part and electronic recompilation are modified, and the H265 video stream can be transmitted and decoded through the WebRTC under a Chromium engine through the modifications.

The system provided by the embodiment of the present application has the same implementation principle and the same technical effect as the foregoing method embodiment, and for the sake of brief description, no mention is made in the embodiment of the system, and reference may be made to the corresponding contents in the foregoing method embodiment.

An electronic device is further provided in the embodiment of the present application, as shown in fig. 4, which is a schematic structural diagram of the electronic device, where the electronic device includes a processor 41 and a memory 40, the memory 40 stores computer-executable instructions that can be executed by the processor 41, and the processor 41 executes the computer-executable instructions to implement the method.

In the embodiment shown in fig. 4, the electronic device further comprises a bus 42 and a communication interface 43, wherein the processor 41, the communication interface 43 and the memory 40 are connected by the bus 42.

The Memory 40 may include a high-speed Random Access Memory (RAM) and may also include a non-volatile Memory (non-volatile Memory), such as at least one disk Memory. The communication connection between the network element of the system and at least one other network element is realized through at least one communication interface 43 (which may be wired or wireless), and the internet, a wide area network, a local network, a metropolitan area network, etc. may be used. The bus 42 may be an ISA (Industry Standard Architecture) bus, a PCI (Peripheral Component Interconnect) bus, an EISA (Extended Industry Standard Architecture) bus, or the like. The bus 42 may be divided into an address bus, a data bus, a control bus, etc. For ease of illustration, only one double-headed arrow is shown in FIG. 4, but that does not indicate only one bus or one type of bus.

The processor 41 may be an integrated circuit chip having signal processing capabilities. In implementation, the steps of the above method may be performed by integrated logic circuits of hardware or instructions in the form of software in the processor 41. The Processor 41 may be a general-purpose Processor, and includes a Central Processing Unit (CPU), a Network Processor (NP), and the like; the device can also be a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other Programmable logic device, a discrete Gate or transistor logic device, or a discrete hardware component. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of the method disclosed in connection with the embodiments of the present application may be directly implemented by a hardware decoding processor, or implemented by a combination of hardware and software modules in the decoding processor. The software module may be located in ram, flash memory, rom, prom, or eprom, registers, etc. storage media as is well known in the art. The storage medium is located in a memory, and the processor 41 reads information in the memory and performs the steps of the method of the previous embodiment in combination with hardware thereof.

Embodiments of the present application further provide a computer-readable storage medium, where computer-executable instructions are stored, and when the computer-executable instructions are called and executed by a processor, the computer-executable instructions cause the processor to implement the method, and specific implementation may refer to the foregoing method embodiments, and is not described herein again.

The method, the apparatus, and the computer program product of the electronic device provided in the embodiments of the present application include a computer-readable storage medium storing a program code, where instructions included in the program code may be used to execute the method described in the foregoing method embodiments, and specific implementation may refer to the method embodiments, and will not be described herein again.

Unless specifically stated otherwise, the relative steps, numerical expressions, and values of the components and steps set forth in these embodiments do not limit the scope of the present application.

The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a non-volatile computer-readable storage medium executable by a processor. Based on such understanding, the technical solution of the present invention may be embodied in the form of a software product, which is stored in a storage medium and includes instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present invention. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and other various media capable of storing program codes.

In the description of the present invention, it should be noted that the terms "center", "upper", "lower", "left", "right", "vertical", "horizontal", "inner", "outer", etc., indicate orientations or positional relationships based on the orientations or positional relationships shown in the drawings, and are only for convenience of description and simplicity of description, but do not indicate or imply that the device or element being referred to must have a particular orientation, be constructed and operated in a particular orientation, and thus, should not be construed as limiting the present invention. Furthermore, the terms "first," "second," and "third" are used for descriptive purposes only and are not to be construed as indicating or implying relative importance.

Finally, it should be noted that: the above-mentioned embodiments are only specific embodiments of the present invention, which are used for illustrating the technical solutions of the present invention and not for limiting the same, and the protection scope of the present invention is not limited thereto, although the present invention is described in detail with reference to the foregoing embodiments, those skilled in the art should understand that: any person skilled in the art can modify or easily conceive the technical solutions described in the foregoing embodiments or equivalent substitutes for some technical features within the technical scope of the present disclosure; such modifications, changes or substitutions do not depart from the spirit and scope of the embodiments of the present invention, and they should be construed as being included therein. Therefore, the protection scope of the present invention shall be subject to the protection scope of the claims.