WO2017101370A1 - 直播视频的处理方法及装置 - Google Patents

直播视频的处理方法及装置 Download PDF

Info

Publication number
WO2017101370A1
WO2017101370A1 PCT/CN2016/088876 CN2016088876W WO2017101370A1 WO 2017101370 A1 WO2017101370 A1 WO 2017101370A1 CN 2016088876 W CN2016088876 W CN 2016088876W WO 2017101370 A1 WO2017101370 A1 WO 2017101370A1
Authority
WO
WIPO (PCT)
Prior art keywords
video
player
format
requested
requested video
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.)
Ceased
Application number
PCT/CN2016/088876
Other languages
English (en)
French (fr)
Inventor
刘凤玉
魏立志
徐潇
凌中华
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Le Holdings Beijing Co Ltd
LeCloud Computing Co Ltd
Original Assignee
Le Holdings Beijing Co Ltd
LeCloud Computing Co Ltd
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 Le Holdings Beijing Co Ltd, LeCloud Computing Co Ltd filed Critical Le Holdings Beijing Co Ltd
Priority to US15/246,511 priority Critical patent/US20170171568A1/en
Publication of WO2017101370A1 publication Critical patent/WO2017101370A1/zh
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • 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/239—Interfacing the upstream path of the transmission network, e.g. prioritizing client content requests
    • H04N21/2393—Interfacing the upstream path of the transmission network, e.g. prioritizing client content requests involving handling client requests
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/20—Servers specifically adapted for the distribution of content, e.g. VOD servers; Operations thereof
    • H04N21/21—Server components or server architectures
    • H04N21/218—Source of audio or video content, e.g. local disk arrays
    • H04N21/2187—Live feed
    • 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/234—Processing of video elementary streams, e.g. splicing of video streams or manipulating encoded video stream scene graphs
    • H04N21/2343—Processing of video elementary streams, e.g. splicing of video streams or manipulating encoded video stream scene graphs involving reformatting operations of video signals for distribution or compliance with end-user requests or end-user device requirements
    • 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/234—Processing of video elementary streams, e.g. splicing of video streams or manipulating encoded video stream scene graphs
    • H04N21/2343—Processing of video elementary streams, e.g. splicing of video streams or manipulating encoded video stream scene graphs involving reformatting operations of video signals for distribution or compliance with end-user requests or end-user device requirements
    • H04N21/234336—Processing of video elementary streams, e.g. splicing of video streams or manipulating encoded video stream scene graphs involving reformatting operations of video signals for distribution or compliance with end-user requests or end-user device requirements by media transcoding, e.g. video is transformed into a slideshow of still pictures or audio is converted into text
    • 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/239—Interfacing the upstream path of the transmission network, e.g. prioritizing client content requests
    • 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/25—Management operations performed by the server for facilitating the content distribution or administrating data related to end-users or client devices, e.g. end-user or client device authentication, learning user preferences for recommending movies
    • H04N21/262—Content or additional data distribution scheduling, e.g. sending additional data at off-peak times, updating software modules, calculating the carousel transmission frequency, delaying a video stream transmission, generating play-lists
    • 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/25—Management operations performed by the server for facilitating the content distribution or administrating data related to end-users or client devices, e.g. end-user or client device authentication, learning user preferences for recommending movies
    • H04N21/262—Content or additional data distribution scheduling, e.g. sending additional data at off-peak times, updating software modules, calculating the carousel transmission frequency, delaying a video stream transmission, generating play-lists
    • H04N21/26208—Content or additional data distribution scheduling, e.g. sending additional data at off-peak times, updating software modules, calculating the carousel transmission frequency, delaying a video stream transmission, generating play-lists the scheduling operation being performed under constraints
    • 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
    • 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/8456—Structuring of content, e.g. decomposing content into time segments by decomposing the content in the time domain, e.g. in time segments

Definitions

  • the embodiments of the present invention relate to the field of computer technologies, and in particular, to a method and an apparatus for processing live video.
  • the live webcast is mainly implemented by the anchor user to generate streaming media data for live video broadcast, and then uploading the streaming media data to the live broadcast platform through the network.
  • the resource server in the live broadcast platform is used. The streaming media data of the live video is sent to the user to be viewed.
  • the live video upload request in different formats sent by the live broadcast user is first received, and then the same live video in different formats is obtained by the resource server to the source server of the anchor user. This way of processing is equivalent to repeatedly acquiring data for transmission, thus wasting system resources.
  • the embodiment of the invention provides a method and a device for processing live video.
  • the main purpose is to convert the format of the live video through the CDN server to solve the system resource waste generated by storing the live video in multiple formats in the resource server.
  • the present invention mainly provides the following technical solutions:
  • an embodiment of the present invention provides a method for processing a live video, where the method includes:
  • the CDN server receives a video play request sent by the player, where the video play request carries the video format supported by the player and the identification information of the requested video;
  • a request video supporting playback of the player is sent to the player.
  • the method Before converting the format of the requested video to the video format supported by the player, the method further includes:
  • the converting the format of the requested video into a video format supported by the player for playing includes:
  • the sending the request video that supports the player to the player to the player includes:
  • the request video is sent directly to the player.
  • the converting the format of the requested video into the video format supported by the player includes:
  • the requested video of the FLV format is cached.
  • the obtaining the request video from the resource server corresponding to the access path includes:
  • the slice video of the requested video is obtained from a resource server corresponding to the access path.
  • the method further includes:
  • the sending the request video that supports the player to the player to the player includes:
  • the receiving, by the CDN server, a video play request sent by the player includes:
  • the CDN server receives a video play request sent by the DNS server of the domain name resolution system corresponding to the player, and the DNS server is configured to receive the video play request sent by the player and configure a CDN server corresponding to the client.
  • the obtaining an access path of the request video according to the identifier information of the request video includes:
  • an embodiment of the present invention provides a CDN server, where the apparatus includes:
  • a receiving unit configured to receive a video play request sent by the player, where the video play request carries a video format supported by the player and identifier information of the requested video;
  • An obtaining unit configured to acquire an access path of the requested video according to the identification information of the requested video
  • the obtaining unit is further configured to acquire the request video from a resource server corresponding to the access path;
  • a converting unit configured to convert a format of the requested video into a video format supported by the player
  • a sending unit configured to send a request video that supports player playback to the player.
  • the device further includes: a determining unit;
  • the determining unit is configured to determine whether the video format supported by the player is an RTMP format
  • the converting unit is specifically configured to convert the format of the requested video into a video format supported by the player if the video format supported by the player is not the RTMP format;
  • the sending unit is specifically configured to directly send the requested video to the player if the video format supported by the player is an RTMP format.
  • the converting unit includes:
  • a conversion module configured to convert the format of the requested video into the FLV format when a video format supported by the player is in an FLV format
  • a cache module configured to cache the requested video in the FLV format.
  • the obtaining unit includes:
  • a judging module configured to determine whether the video format supported by the player is in an HLS format
  • the acquiring module is specifically configured to: if the video format supported by the player is an HLS format, obtain a slice video of the requested video from a resource server corresponding to the access path.
  • the device further includes: a cache unit;
  • the buffer unit is configured to cache a slice video of the requested video
  • the sending unit is specifically configured to send a slice video of the requested video to the player.
  • the receiving unit is specifically configured to receive a video play request sent by a DNS server of a domain name resolution system corresponding to the player, where the DNS server is configured to receive the video play request sent by the player and configure the client The corresponding CDN server.
  • the obtaining unit further includes:
  • a sending module configured to send the identification information of the requested video to the scheduling server, so that the scheduling server acquires an access path corresponding to the identification information of the requested video;
  • a receiving module configured to receive the access path sent by the scheduling server.
  • An embodiment of the present invention provides another CDN server, where the apparatus includes:
  • One or more processors are One or more processors.
  • the memory stores instructions that are configured to be executed by the one or more processors, and the one or more processors can perform the following operations by executing the instructions:
  • a request video supporting playback of the player is sent to the player.
  • a CDN server receives a video play request sent by a player, where the video play request carries a video format supported by the player and identification information of the requested video. Obtaining an access path of the requested video according to the identification information of the requested video, acquiring the requested video from a resource server corresponding to the access path, and converting the format of the requested video into a video supported by the player. Format, and finally send a request video that supports player playback to the player.
  • the present invention firstly obtains the video resource corresponding to the video play request from the resource server according to the received video play request.
  • the format of the video resource is converted into a video format supported by the player, and finally the video resource supporting the player is sent to the player, thereby realizing the requirement of the live video format by different playing players. Therefore, only one type of live video can be saved in the resource server of the present invention to meet the requirements of multiple players for the video format, so that the number of times the resource server can obtain the video resource from the source server of the anchor user can be reduced, thereby saving System resources.
  • FIG. 1 is a flowchart of a method for processing live video according to an embodiment of the present invention
  • FIG. 2 is a flowchart of another method for processing live video according to an embodiment of the present invention.
  • FIG. 3 is a structural block diagram of a CDN server according to an embodiment of the present invention.
  • FIG. 4 is a structural block diagram of another CDN server according to an embodiment of the present invention.
  • FIG. 5 is a schematic structural diagram of a server according to an embodiment of the present invention.
  • An embodiment of the present invention provides a method for processing a live video. As shown in FIG. 1 , the method is applied to a CDN server, and the specific steps include:
  • the CDN server receives a video play request sent by the player.
  • the video play request carries a video format and a request view supported by the player.
  • the frequency identification information, CDN Content Delivery Network
  • CDN Content Delivery Network
  • the frequency identification information, CDN is to avoid the bottlenecks and links on the Internet that may affect the speed and stability of data transmission, so that the content transmission is faster and more stable.
  • CDN Content Delivery Network
  • the player of the client since the player of the client has various forms, and the video formats required by the respective players are different, the player needs to specify the playback supported by the player in the request when sending the video playback request.
  • the format is such that the live video requested back can be played on the local player.
  • the video format supported by the player may be FLV (Flash Video, streaming media format), HLS (HTTP Live Streaming, Apple's dynamic rate adaptive technology), and RTMP (Real Time Messaging).
  • FLV Flash Video
  • HLS HTTP Live Streaming, Apple's dynamic rate adaptive technology
  • RTMP Real Time Messaging
  • the protocol, the real-time message transmission protocol, and the like are not specifically limited in the embodiment of the present invention.
  • the CDN server receives a video play request sent by a DNS (Domain Name System) server corresponding to the player, and the DNS server is configured to receive the video play request sent by the player and configure the The CDN server corresponding to the client.
  • the DNS server parses the IP address corresponding to the player, and then assigns a player to the player according to the analysis result and the corresponding operator of the player, and belongs to the same operation.
  • the CDN server with a small load and then receives the video play request sent by the player by the CDN server.
  • the live video data can be transmitted through the CDN server, thereby improving the transmission efficiency of the live video.
  • the identification information of the request video is used to identify a video that the player wants to request.
  • the CDN server after receiving the video play request sent by the player, obtains the access path of the requested video according to the identification information of the requested video in the video play request.
  • the specific steps include: the CDN server sends the identification information of the requested video to the scheduling server, and after receiving the identification information of the requested video sent by the CDN server, the scheduling server acquires an access path corresponding to the identification information of the requested video, and then schedules The server sends an access path corresponding to the identification information of the requested video to the CDN server.
  • the CDN server may find the corresponding resource server through the access path, and then obtain the requested video from the resource server.
  • the format of the requested video obtained by the CDN server is RTMP
  • the player supports the video format FLV, so that the format of the requested video and the format that the player can support playing are different, so the format of the requested video needs to be
  • the RTMP format is converted to the FLV format to satisfy the request that the video can be played normally on the player.
  • the video resource corresponding to the video play request is first obtained from the resource server, and then the format of the video resource is converted into a video format supported by the player, and finally the playback is supported.
  • the video resources played by the player are sent to the player, so as to realize the requirement of the live video format of different playback players. Therefore, only one type of live video can be saved in the resource server of the present invention to meet the requirements of multiple players for the video format, so that the number of times the resource server can obtain the video resource from the source server of the anchor user can be reduced, thereby saving System resources.
  • the embodiment of the present invention further provides a method for processing a live video. As shown in FIG. 2, the method is applied to a scheduling server, and the specific steps include:
  • the CDN server receives a video play request sent by the player.
  • the video play request carries the video format supported by the player and the identification information of the requested video.
  • the obtaining an access path of the request video according to the identification information of the requested video includes: sending the identification information of the requested video to a scheduling server, so that the scheduling server acquires the request An access path corresponding to the identification information of the video; receiving the access path sent by the scheduling server.
  • the HLS format is Apple's dynamic rate adaptive technology, which is mainly used for audio and video services of PCs and Apple terminals, including an m3u (8) index file, TS media slice file and key encryption string file.
  • the live video playback supported by the HLS format needs to be broadcasted.
  • the TS media fragmentation of the video is implemented. Therefore, if the format supported by the player is HLS format, the slice video of the requested video needs to be obtained from the resource server corresponding to the access path.
  • the request video of the RTMP format needs to be split in the resource server, which may be The requested video is divided into one TS media slice every 6 seconds, that is, a slice video of the requested video.
  • the CDN server caches the slice video of the requested video in the CDN server, so that when there is a new user When the live video is obtained, the video resource can be directly obtained through the CDN server without the need to convert the video format again, thereby improving the efficiency of the player to obtain the live video.
  • the step 204b is a parallel step of the step 204a. If the video format supported by the player is not the HLS format, the video resource is obtained from the resource server corresponding to the access path.
  • the converting the format of the requested video into the video format supported by the player includes: formatting the requested video. Converting to the FLV format; caching the requested video of the FLV format.
  • 207b1 Send a request video that supports player playback to the player.
  • Step 206b2 is a parallel step of step 206b1. If the video format supported by the player is RTMP format, it indicates that the video format supported by the player and the default format of the requested video obtained from the resource server are consistent. Therefore, the video format is not required to be converted, and the requested video is directly sent to the player, and the player can directly play the video.
  • the CDN server after receiving the video play request sent by the player, obtains the access path of the requested video according to the identification information of the requested video in the video play request, and then determines whether the video format supported by the player supports playing For the HLS format, if the video format supported by the player is the HLS format, the slice video of the requested video is obtained from the resource server corresponding to the access path, and then the slice video of the requested video is cached. The slice video of the requested video is sent to the player. Conversely, if the video format supported by the player is not the HLS format, the request video is obtained from the resource server corresponding to the access path, and then it is determined whether the video format supported by the player is in the RTMP format.
  • the video format supported by the player is RTMP format, and the requested video is directly sent to the player; if the video format supported by the player is not the RTMP format, the format of the requested video is converted into the player.
  • an embodiment of the present invention provides a CDN server.
  • the apparatus includes: a receiving unit, an obtaining unit, a converting unit, and a sending unit.
  • the receiving unit 31 is configured to receive a video play request sent by the player, where the video play request carries a video format supported by the player and identification information of the requested video.
  • the video format supported by the player may be FLV (Flash Video, streaming media format), HLS (HTTP Live Streaming, Apple's dynamic rate adaptive technology), and RTMP (Real Time Messaging Protocol).
  • FLV Flash Video
  • HLS HTTP Live Streaming, Apple's dynamic rate adaptive technology
  • RTMP Real Time Messaging Protocol
  • the obtaining unit 32 is configured to acquire an access path of the requested video according to the identification information of the request video received by the receiving unit 31.
  • the obtaining an access path of the request video according to the identification information of the request video includes: sending the identification information of the requested video to a scheduling server, so that the scheduling server acquires an access corresponding to the identification information of the requested video. a path; receiving the access path sent by the scheduling server.
  • the obtaining unit 32 is further configured to acquire the requested video from a resource server corresponding to the access path. After obtaining the access path of the requested video, the CDN server may find the corresponding resource server through the access path, and then obtain the requested video from the resource server.
  • the converting unit 33 is configured to convert the format of the requested video acquired by the acquiring unit 32 into a video format supported by the player.
  • the sending unit 34 is configured to send the request video converted by the conversion unit 33 to support the player to the player. In order for the player to play the requested video.
  • the apparatus further includes: a determining unit 35.
  • the determining unit 35 is configured to determine whether the video format supported by the player is an RTMP format.
  • the converting unit 33 is specifically configured to convert the format of the requested video into a video format supported by the player if the video format supported by the player is not the RTMP format.
  • the sending unit 34 is specifically configured to directly send the requested video to the player if the video format supported by the player is an RTMP format.
  • the converting unit 33 includes:
  • the conversion module 331 is configured to convert the format of the requested video into the FLV format when the video format supported by the player is FLV format.
  • the cache module 332 is configured to cache the requested video in the FLV format.
  • the obtaining unit 32 includes:
  • the determining module 321 is configured to determine whether the video format supported by the player is in the HLS format.
  • the HLS format is Apple's dynamic rate adaptation technology, which is mainly used for audio and video services of PCs and Apple terminals, including an m3u (8) index file, TS media fragment file and key encryption string file.
  • the obtaining module 322 is specifically configured to: if the determining module 321 determines that the video format supported by the player is the HLS format, obtain the slice video of the requested video from the resource server corresponding to the access path. Since the default format of the requested video in the resource server is the RTMP format, when the video format supported by the player is HLS, the request video of the RTMP format needs to be segmented in the resource server, and is divided into one every 6 seconds. TS media fragmentation, which is a slice video requesting video.
  • the device further includes: a cache unit 36;
  • the buffer unit 36 is configured to cache the slice video of the requested video acquired by the obtaining unit 32.
  • the slice video of the requested video is entered in the CDN server.
  • the line buffer can make the video resource directly available to the CDN server directly when the new user obtains the live video, without the need to convert the video format again, thereby improving the efficiency of the player to obtain the live video.
  • the sending unit 34 is specifically configured to send a slice video of the requested video acquired by the obtaining unit 32 to the player.
  • the receiving unit 31 is configured to receive a video play request sent by a DNS server of a domain name resolution system corresponding to the player, where the DNS server is configured to receive the video play request sent by the player, and configure the The CDN server corresponding to the client.
  • the obtaining unit 32 further includes:
  • the sending module 323 is configured to send the identifier information of the request video received by the receiving unit 31 to the scheduling server, so that the scheduling server acquires an access path corresponding to the identifier information of the requested video.
  • the receiving module 324 is configured to receive the access path sent by the sending module 323 to the scheduling server.
  • the CDN server first receives a video play request sent by the player, where the video play request carries the video format supported by the player and the identification information of the requested video, and then obtains the request according to the identification information of the requested video.
  • the access path of the video the request video is obtained from the resource server corresponding to the access path, the format of the requested video is converted into a video format supported by the player, and finally the request video supported by the player is supported. Sent to the player.
  • the present invention first obtains a video playback request from a resource server according to the received video playback request.
  • the video resource is then converted into a video format supported by the player, and finally the video resource supported by the player is sent to the player, thereby realizing the requirement of the live video format of different playback players. Therefore, only one type of live video can be saved in the resource server of the present invention to meet the requirements of multiple players for the video format, so that the number of times the resource server can obtain the video resource from the source server of the anchor user can be reduced, thereby saving System resources.
  • FIG. 5 shows a server provided by an embodiment of the present invention.
  • the server may include: a processor 51, a communication interface 52, a memory 53 and a bus 54, wherein the processor 51, the communication interface 52, and the memory 53 complete each other through the bus 54. Communication between. Communication interface 52 can be used for information transfer between the server and the client.
  • the processor 51 can call the logic instruction in the memory 53 to perform the following method: the CDN server receives the video play request sent by the player, where the video play request carries the video format supported by the player and the identification information of the requested video; Acquiring an access path of the requested video according to the identification information of the requested video; acquiring the requested video from a resource server corresponding to the access path; converting the format of the requested video into a video format supported by the player Sending a request video that supports player playback to the player.
  • the logic instructions in the memory 53 described above may be implemented in the form of a software functional unit and sold or used as a stand-alone product, and may be stored in a computer readable storage medium.
  • the technical solution of the present invention which is essential or contributes to the prior art, or a part of the technical solution, may be embodied in the form of a software product, which is stored in a storage medium, including
  • the instructions are used to cause a computer device (which may be a personal computer, server, or network device, etc.) to perform all or part of the steps of the methods described in various embodiments of the present invention.
  • the foregoing storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk, and the like. .
  • the device embodiments described above are merely illustrative, wherein the units described as separate components may or may not be physically separate, and the components displayed as units may or may not be physical units, ie may be located A place, or it can be distributed to multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of the embodiment. Those of ordinary skill in the art can understand and implement without deliberate labor.

Landscapes

  • Engineering & Computer Science (AREA)
  • Multimedia (AREA)
  • Signal Processing (AREA)
  • Databases & Information Systems (AREA)
  • Two-Way Televisions, Distribution Of Moving Picture Or The Like (AREA)

Abstract

本发明实施例提供的一种直播视频的处理方法及装置，涉及计算机技术领域，主要目的在于解决为满足不同播放器对视频格式的要求所产生的系统资源浪费。本发明实施例采用的技术方案为：CDN服务器接收播放器发送的视频播放请求，所述视频播放请求中携带有播放器支持播放的视频格式和请求视频的标识信息；根据所述请求视频的标识信息获取请求视频的访问路径；从与所述访问路径对应的资源服务器中获取所述请求视频；将所述请求视频的格式转换成所述播放器支持播放的视频格式；将支持播放器播放的请求视频发送给所述播放器。本发明主要用于获取特定格式的直播视频。

Description

直播视频的处理方法及装置
本申请基于申请号为2015109262220、申请日为2015年12月14日的中国专利申请提出，并要求该中国专利申请的优先权，该中国专利申请的全部内容在此引入本申请作为参考。
技术领域
本发明实施例涉及计算机技术领域，尤其涉及一种直播视频的处理方法及装置。
背景技术
网络直播由于是通过互联网平台展开，相对于传统直播来说，让大众有了更好的主动操作性，也就是说有了更好的和更自由的选择空间。例如目前流行的球赛直播、体育直播等，婚礼直播，开业直播等直播是为了方便广大群众，将这些信号在互联网上发布，观众就可以很方便选择自己所需要的直播线路，全球任何有网络的地方都能看到在线直播的视频。网络直播的实现方式主要是通过主播用户制作用于视频直播的流媒体数据，然后将流媒体数据通过网络上传到直播平台中，当有用户要求观看该直播视频时，由直播平台中的资源服务器将该直播视频的流媒体数据发送给要观看的用户。
目前，为了支持不同观看用户对直播视频格式的要求，则需要在资源服务器中存储多种格式的直播视频。然而为了在资源服务器中存储多种格式的直播视频，则首先需要接收直播用户发送的不同格式的直播视频上传请求，然后由资源服务器到主播用户的源服务器中分别获取不同格式的同一直播视频。这样处理方式相当于重复获取数据进行传输，因此浪费了系统资源。
发明内容
本发明实施例提供一种直播视频的处理方法及装置，主要目的在于通过CDN服务器转换直播视频的格式以解决在资源服务器中存储多种格式的直播视频所产生的系统资源浪费。
为达到上述目的，本发明主要提供如下技术方案：
一方面，本发明实施例提供一种直播视频的处理方法，该方法包括：
CDN服务器接收播放器发送的视频播放请求，所述视频播放请求中携带有播放器支持播放的视频格式和请求视频的标识信息；
根据所述请求视频的标识信息获取请求视频的访问路径；
从与所述访问路径对应的资源服务器中获取所述请求视频；
将所述请求视频的格式转换成所述播放器支持播放的视频格式；
将支持播放器播放的请求视频发送给所述播放器。
在将所述请求视频的格式转换成所述播放器支持播放的视频格式之前，所述方法还包括：
判断所述播放器支持播放的视频格式是否为RTMP格式；
具体的，所述将所述请求视频的格式转换成所述播放器支持播放的视频格式包括：
若否，则将所述请求视频的格式转换成所述播放器支持播放的视频格式；
具体的，所述将支持播放器播放的请求视频发送给所述播放器包括：
若是，则直接将所述请求视频发送给所述播放器。
进一步地，当所述播放器支持播放的视频格式为FLV格式时，所述将所述请求视频的格式转换成所述播放器支持播放的视频格式包括：
将所述请求视频的格式转换成所述FLV格式；
对所述FLV格式的请求视频进行缓存。
具体的，所述从与所述访问路径对应的资源服务器中获取所述请求视频包括：
判断所述播放器支持播放的视频格式是否为HLS格式；
若是，则从与所述访问路径对应的资源服务器中获取所述请求视频的切片视频。
进一步地，从所述从与所述访问路径对应的资源服务器中获取所述请求视频之后，所述方法还包括；
将所述请求视频的切片视频进行缓存；
具体的，所述将支持播放器播放的请求视频发送给所述播放器包括：
将所述请求视频的切片视频发送给所述播放器。
具体的，所述CDN服务器接收播放器发送的视频播放请求包括：
CDN服务器接收播放器对应的域名解析系统DNS服务器发送的视频播放请求，所述DNS服务器用于接收所述播放器发送的所述视频播放请求并配置所述客户端对应的CDN服务器。
具体的，所述根据所述请求视频的标识信息获取请求视频的访问路径包括：
将所述请求视频的标识信息求发送给调度服务器，以使得所述调度服务器获取与所述请求视频的标识信息对应的访问路径；
接收所述调度服务器发送的所述访问路径。
另一方面，本发明实施例提供一种CDN服务器，该装置包括：
接收单元，用于接收播放器发送的视频播放请求，所述视频播放请求中携带有播放器支持播放的视频格式和请求视频的标识信息；
获取单元，用于根据所述请求视频的标识信息获取请求视频的访问路径；
所述获取单元，还用于从与所述访问路径对应的资源服务器中获取所述请求视频；
转换单元，用于将所述请求视频的格式转换成所述播放器支持播放的视频格式；
发送单元，用于将支持播放器播放的请求视频发送给所述播放器。
进一步地，所述装置还包括：判断单元；
所述判断单元，用于判断所述播放器支持播放的视频格式是否为RTMP格式；
所述转换单元，具体用于若所述播放器支持播放的视频格式不是RTMP格式，则将所述请求视频的格式转换成所述播放器支持播放的视频格式；
所述发送单元，具体用于若所述播放器支持播放的视频格式是RTMP格式，则直接将所述请求视频发送给所述播放器。
具体的，所述转换单元包括：
转换模块，用于当所述播放器支持播放的视频格式为FLV格式时，将所述请求视频的格式转换成所述FLV格式；
缓存模块，用于对所述FLV格式的请求视频进行缓存。
具体的，所述获取单元包括：
判断模块，用于判断所述播放器支持播放的视频格式是否为HLS格式；
获取模块，具体用于若所述播放器支持播放的视频格式为HLS格式，则从与所述访问路径对应的资源服务器中获取所述请求视频的切片视频。
进一步地，所述装置还包括：缓存单元；
所述缓存单元，用于将所述请求视频的切片视频进行缓存；
所述发送单元，具体用于将所述请求视频的切片视频发送给所述播放器。
具体的，所述接收单元，具体用于接收播放器对应的域名解析系统DNS服务器发送的视频播放请求，所述DNS服务器用于接收所述播放器发送的所述视频播放请求并配置所述客户端对应的CDN服务器。
具体的，所述获取单元还包括：
发送模块，用于将所述请求视频的标识信息求发送给调度服务器，以使得所述调度服务器获取与所述请求视频的标识信息对应的访问路径；
接收模块，用于接收所述调度服务器发送的所述访问路径。
本发明实施例提供另一种CDN服务器，该装置包括：
一个或多个处理器；和
存储器；
其中所述存储器中存储有指令，经配置所述指令由所述一个或多个处理器执行，所述一个或多个处理器通过执行所述指令能进行如下操作：
接收播放器发送的视频播放请求，所述视频播放请求中携带有播放器支持播放的视频格式和请求视频的标识信息；
根据所述请求视频的标识信息获取请求视频的访问路径；
从与所述访问路径对应的资源服务器中获取所述请求视频；
将所述请求视频的格式转换成所述播放器支持播放的视频格式；
将支持播放器播放的请求视频发送给所述播放器。
本发明实施例提供的一种直播视频的处理方法及装置，首先CDN服务器接收播放器发送的视频播放请求，所述视频播放请求中携带有播放器支持播放的视频格式和请求视频的标识信息，然后根据所述请求视频的标识信息获取请求视频的访问路径，从与所述访问路径对应的资源服务器中获取所述请求视频，将所述请求视频的格式转换成所述播放器支持播放的视频格式，最后将支持播放器播放的请求视频发送给所述播放器。与目前通过在资源服 务器中存储多种格式的直播视频以实现支持不同播放器对视频格式的需求相比，本发明根据接收到的视频播放请求，首先从资源服务器中获取与该视频播放请求对应的视频资源，然后将视频资源的格式转换成播放器支持播放的视频格式，最后将支持播放器播放的视频资源发送给播放器，以此实现不同播放播放器对直播视频格式的需求。因此本发明的资源服务器中仅保存一种格式的直播视频就可以满足多种播放器对视频格式的需求，从而通过本发明可以减少资源服务器到主播用户的源服务器获取视频资源的次数，进而节省了系统资源。
附图说明
为了更清楚地说明本发明实施例或现有技术中的技术方案，下面将对实施例或现有技术描述中所需要使用的附图作以简单地介绍，显而易见地，下面描述中的附图是本发明的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动的前提下，还可以根据这些附图获得其他的附图。
图1为本发明实施例提供的一种直播视频的处理方法流程图；
图2为本发明实施例提供的另一种直播视频的处理方法流程图；
图3为本发明实施例提供的一种CDN服务器的结构组成框图；
图4为本发明实施例提供的另一种CDN服务器的结构组成框图；
图5为本发明实施例提供的一种服务器的结构示意图。
具体实施方式
为使本发明实施例的目的、技术方案和优点更加清楚，下面将结合本发明实施例中的附图，对本发明实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例是本发明一部分实施例，而不是全部的实施例。基于本发明中的实施例，本领域普通技术人员在没有作出创造性劳动前提下所获得的所有其他实施例，都属于本发明保护的范围。
本发明实施例提供了一种直播视频的处理方法，如图1所示，该方法应用于CDN服务器，具体步骤包括：
101、CDN服务器接收播放器发送的视频播放请求。
其中，所述视频播放请求中携带有播放器支持播放的视频格式和请求视 频的标识信息，CDN(Content Delivery Network，内容分发网络)是尽可能避开互联网上有可能影响数据传输速度和稳定性的瓶颈和环节，使内容传输的更快、更稳定。对于本发明实施例，由于客户端的播放器有多种形式，且各个播放器所要求的视频格式不尽相同，因此播放器在发送视频播放请求时，需要在请求当中指定播放器所支持的播放格式，以使得请求回来的直播视频能够在本地播放器上播放。在本发明实施例中，所述播放器支持播放的视频格式具体可以为FLV(Flash Video，流媒体格式)、HLS(HTTP Live Streaming，Apple的动态码率自适应技术)、RTMP(Real Time Messaging Protocol，实时消息传输协议)等，本发明实施例不做具体限定。
需要说明的是，CDN服务器接收播放器对应的DNS(Domain Name System，域名系统)服务器发送的视频播放请求，所述DNS服务器用于接收所述播放器发送的所述视频播放请求并配置所述客户端对应的CDN服务器。DNS服务器在接收到播放器发送的视频播放请求后，对播放器对应的IP地址进行解析，然后根据解析结果和播放器对应的运营商为播放器分配一个与之距离最近、隶属于同一个运营商且负载较小的CDN服务器，然后由该CDN服务器接收播放器发送的视频播放请求。对于本发明实施例，由于隶属于同一个运营商且距离较近的两个服务器之间数据传输效率高，因此通过该CDN服务器传输直播视频数据，可以提高直播视频的传输效率。
102、根据所述请求视频的标识信息获取请求视频的访问路径。
其中，所述请求视频的标识信息用于标识播放器所要请求的视频。在本发明实施例中，CDN服务器在接收到播放器发送的视频播放请求后，根据视频播放请求中的请求视频的标识信息获取请求视频的访问路径。具体的步骤包括：CDN服务器将请求视频的标识信息发送给调度服务器，调度服务器在接收到CDN服务器发送的请求视频的标识信息后，获取与所述请求视频的标识信息对应的访问路径，然后调度服务器将与请求视频的标识信息对应的访问路径发送给CDN服务器。
103、从与所述访问路径对应的资源服务器中获取所述请求视频。
在本发明实施例中，CDN服务器在获取到请求视频的访问路径后，可以通过所述访问路径找到对应的资源服务器，然后再从资源服务器中获取所述请求视频。
104、将所述请求视频的格式转换成所述播放器支持播放的视频格式。
例如，CDN服务器获取到的请求视频的格式为RTMP，而播放器支持播放的视频格式FLV，由此可见请求视频的格式和播放器所能够支持播放的格式不同，因此需要将请求视频的格式从RTMP格式转换为FLV格式，以此满足请求视频能够在播放器上正常播放。
105、将支持播放器播放的请求视频发送给所述播放器。
对于本发明实施例，根据接收到的视频播放请求，首先从资源服务器中获取与该视频播放请求对应的视频资源，然后将视频资源的格式转换成播放器支持播放的视频格式，最后将支持播放器播放的视频资源发送给播放器，以此实现不同播放播放器对直播视频格式的需求。因此本发明的资源服务器中仅保存一种格式的直播视频就可以满足多种播放器对视频格式的需求，从而通过本发明可以减少资源服务器到主播用户的源服务器获取视频资源的次数，进而节省了系统资源。
与上述方法相对应地，本发明实施例还提供了一种直播视频的处理方法，如图2所示，该方法应用于调度服务器，具体步骤包括：
201、CDN服务器接收播放器发送的视频播放请求。
其中，所述视频播放请求中携带有播放器支持播放的视频格式和请求视频的标识信息。
202、根据所述请求视频的标识信息获取请求视频的访问路径。
在本发明实施例中，所述根据所述请求视频的标识信息获取请求视频的访问路径包括：将所述请求视频的标识信息求发送给调度服务器，以使得所述调度服务器获取与所述请求视频的标识信息对应的访问路径；接收所述调度服务器发送的所述访问路径。
203、判断所述播放器支持播放的视频格式是否为HLS格式。
其中，HLS格式为Apple的动态码率自适应技术，主要用于PC和Apple终端的音视频服务，包括一个m3u(8)的索引文件，TS媒体分片文件和key加密串文件。
204a、若是，则从与所述访问路径对应的资源服务器中获取所述请求视频的切片视频。
对于本发明实施例，由于HLS格式支持的直播视频播放，需要通过直播 视频的TS媒体分片实现，因此若播放器支持播放的格式为HLS格式，则需要从与访问路径对应的资源服务器中获取请求视频的切片视频。需要说明的是，由于资源服务器中的请求视频的默认格式为RTMP格式，因此当播放器支持播放的视频格式为HLS时，则需要在资源服务器中将RTMP格式的请求视频进行切分，可对请求视频按照每6秒切分成一个TS媒体分片，即请求视频的切片视频。
205a、将所述请求视频的切片视频进行缓存。
在本发明实施例中，CDN服务器从与所述访问路径对应的资源服务器中获取所述请求视频的切片视频后，将请求视频的切片视频在CDN服务器中进行缓存，可以使得当有新的用户获取该直播视频时，则可以直接通过CDN服务器直接获取该视频资源，而无需再次进行视频格式的转换，从而提高了播放器获取直播视频的效率。
206a、将所述请求视频的切片视频发送给所述播放器。
204b、若否，从与所述访问路径对应的资源服务器中获取所述请求视频。
其中，步骤204b为步骤204a的并列步骤，若播放器支持播放的视频格式不是HLS格式，则从与所述访问路径对应的资源服务器中获取所述视频资源。
205b、判断所述播放器支持播放的视频格式是否为RTMP格式。
206b1、若否，则将所述请求视频的格式转换成所述播放器支持播放的视频格式。
对于本发明实施例，当所述播放器支持播放的视频格式为FLV格式时，所述将所述请求视频的格式转换成所述播放器支持播放的视频格式包括：将所述请求视频的格式转换成所述FLV格式；对所述FLV格式的请求视频进行缓存。
207b1、将支持播放器播放的请求视频发送给所述播放器。
206b2、若是，则直接将所述请求视频发送给所述播放器。
其中，步骤206b2为步骤206b1的并列步骤，若播放器支持播放的视频格式是否为RTMP格式，则说明播放器支持播放的视频格式和从资源服务器中获取的请求视频的默认的格式是一致的，因此无需进行视频格式的转换，直接将请求的视频发送给播放器，播放器可直接进行播放视频。
对于本发明实施例，在CDN服务器接收到播放器发送的视频播放请求后，根据视频播放请求中的请求视频的标识信息获取请求视频的访问路径，然后判断所述播放器支持播放的视频格式是否为HLS格式，若播放器支持播放的视频格式为HLS格式，则从与所述访问路径对应的资源服务器中获取所述请求视频的切片视频，接着将所述请求视频的切片视频进行缓存，将所述请求视频的切片视频发送给所述播放器。相反的，若播放器支持播放的视频格式不是HLS格式，从与所述访问路径对应的资源服务器中获取所述请求视频，然后接着判断所述播放器支持播放的视频格式是否为RTMP格式，若播放器支持播放的视频格式为RTMP格式，直接将所述请求视频发送给所述播放器；若播放器支持播放的视频格式不是RTMP格式，则将所述请求视频的格式转换成所述播放器支持播放的视频格式，将支持播放器播放的请求视频发送给所述播放器。因此本发明的资源服务器中仅保存一种格式的直播视频就可以满足多种播放器对视频格式的需求，从而通过本发明可以减少资源服务器到主播用户的源服务器获取视频资源的次数，进而节省了系统资源。
进一步的，作为对上述方法的实现，本发明实施例提供了一种CDN服务器，如图3所示，该装置包括：接收单元，获取单元，转换单元，发送单元。
接收单元31，用于接收播放器发送的视频播放请求，所述视频播放请求中携带有播放器支持播放的视频格式和请求视频的标识信息。所述播放器支持播放的视频格式具体可以为FLV(Flash Video，流媒体格式)、HLS(HTTP Live Streaming，Apple的动态码率自适应技术)、RTMP(Real Time Messaging Protocol，实时消息传输协议)等，本发明实施例不做具体限定。
获取单元32，用于根据所述接收单元31接收的请求视频的标识信息获取请求视频的访问路径。所述根据所述请求视频的标识信息获取请求视频的访问路径包括：将所述请求视频的标识信息求发送给调度服务器，以使得所述调度服务器获取与所述请求视频的标识信息对应的访问路径；接收所述调度服务器发送的所述访问路径。
所述获取单元32，还用于从与所述访问路径对应的资源服务器中获取所述请求视频。CDN服务器在获取到请求视频的访问路径后，可以通过所述访问路径找到对应的资源服务器，然后再从资源服务器中获取所述请求视频。
转换单元33，用于将所述获取单元32获取的请求视频的格式转换成所述播放器支持播放的视频格式。
发送单元34，用于将转换单元33转换的支持播放器播放的请求视频发送给所述播放器。以使得播放器播放该请求视频。
进一步的，如图4所示，所述装置还包括：判断单元35。
所述判断单元35，用于判断所述播放器支持播放的视频格式是否为RTMP格式。
所述转换单元33，具体用于若所述播放器支持播放的视频格式不是RTMP格式，则将所述请求视频的格式转换成所述播放器支持播放的视频格式。
所述发送单元34，具体用于若所述播放器支持播放的视频格式是RTMP格式，则直接将所述请求视频发送给所述播放器。
具体的，所述转换单元33包括：
转换模块331，用于当所述播放器支持播放的视频格式为FLV格式时，将所述请求视频的格式转换成所述FLV格式。
缓存模块332，用于对所述FLV格式的请求视频进行缓存。
具体的，所述获取单元32包括：
判断模块321，用于判断所述播放器支持播放的视频格式是否为HLS格式。HLS格式为Apple的动态码率自适应技术，主要用于PC和Apple终端的音视频服务，包括一个m3u(8)的索引文件，TS媒体分片文件和key加密串文件。
获取模块322，具体用于若所述判断模块321判断出播放器支持播放的视频格式为HLS格式，则从与所述访问路径对应的资源服务器中获取所述请求视频的切片视频。由于资源服务器中的请求视频的默认格式为RTMP格式，因此当播放器支持播放的视频格式为HLS时，则需要在资源服务器中将RTMP格式的请求视频进行切分，按照每6秒切分成一个TS媒体分片，即请求视频的切片视频。
进一步地，所述装置还包括：缓存单元36；
所述缓存单元36，用于将所述获取单元32获取的请求视频的切片视频进行缓存。对于本发明实施例中，将请求视频的切片视频在CDN服务器中进 行缓存，可以使得当有新的用户获取该直播视频时，则可以直接通过CDN服务器直接获取该视频资源，而无需再次进行视频格式的转换，从而提高了播放器获取直播视频的效率。
所述发送单元34，具体用于将所述获取单元32获取的请求视频的切片视频发送给所述播放器。
具体的，所述接收单元31，具体用于接收播放器对应的域名解析系统DNS服务器发送的视频播放请求，所述DNS服务器用于接收所述播放器发送的所述视频播放请求并配置所述客户端对应的CDN服务器。
具体的，所述获取单元32还包括：
发送模块323，用于将所述接收单元31接收的请求视频的标识信息求发送给调度服务器，以使得所述调度服务器获取与所述请求视频的标识信息对应的访问路径。
接收模块324，用于接收所述发送模块323调度服务器发送的所述访问路径。
综上所述，首先CDN服务器接收播放器发送的视频播放请求，所述视频播放请求中携带有播放器支持播放的视频格式和请求视频的标识信息，然后根据所述请求视频的标识信息获取请求视频的访问路径，从与所述访问路径对应的资源服务器中获取所述请求视频，将所述请求视频的格式转换成所述播放器支持播放的视频格式，最后将支持播放器播放的请求视频发送给所述播放器。与目前通过在资源服务器中存储多种格式的直播视频以实现支持不同播放器对视频格式的需求相比，本发明根据接收到的视频播放请求，首先从资源服务器中获取与该视频播放请求对应的视频资源，然后将视频资源的格式转换成播放器支持播放的视频格式，最后将支持播放器播放的视频资源发送给播放器，以此实现不同播放播放器对直播视频格式的需求。因此本发明的资源服务器中仅保存一种格式的直播视频就可以满足多种播放器对视频格式的需求，从而通过本发明可以减少资源服务器到主播用户的源服务器获取视频资源的次数，进而节省了系统资源。
需要说明的是，针对上述CDN服务器，凡是本发明实施例中使用到的各个单元模块的功能都可以通过硬件处理器(hardware processor)来实现。
示例性的，如图5所示，图5示出了本发明实施例提供的一种服务器的 实体结构示意图，该服务器可以包括：处理器(processor)51、通信接口(Communications Interface)52、存储器(memory)53和总线54，其中，处理器51、通信接口52、存储器53通过总线54完成相互间的通信。通信接口52可以用于服务器与客户端之间的信息传输。处理器51可以调用存储器53中的逻辑指令，以执行如下方法：CDN服务器接收播放器发送的视频播放请求，所述视频播放请求中携带有播放器支持播放的视频格式和请求视频的标识信息；根据所述请求视频的标识信息获取请求视频的访问路径；从与所述访问路径对应的资源服务器中获取所述请求视频；将所述请求视频的格式转换成所述播放器支持播放的视频格式；将支持播放器播放的请求视频发送给所述播放器。
此外，上述的存储器53中的逻辑指令可以通过软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本发明的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本发明各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(ROM，Read-Only Memory)、随机存取存储器(RAM，Random Access Memory)、磁碟或者光盘等各种可以存储程序代码的介质。
以上所描述的装置实施例仅仅是示意性的，其中所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部模块来实现本实施例方案的目的。本领域普通技术人员在不付出创造性的劳动的情况下，即可以理解并实施。
通过以上的实施方式的描述，本领域的技术人员可以清楚地了解到各实施方式可借助软件加必需的通用硬件平台的方式来实现，当然也可以通过硬件。基于这样的理解，上述技术方案本质上或者说对现有技术做出贡献的部分可以以软件产品的形式体现出来，该计算机软件产品可以存储在计算机可读存储介质中，如ROM/RAM、磁碟、光盘等，包括若干指令用以使得一台 计算机设备(可以是个人计算机，服务器，或者网络设备等)执行各个实施例或者实施例的某些部分所述的方法。
最后应说明的是：以上实施例仅用以说明本发明的技术方案，而非对其限制；尽管参照前述实施例对本发明进行了详细的说明，本领域的普通技术人员应当理解：其依然可以对前述各实施例所记载的技术方案进行修改，或者对其中部分技术特征进行等同替换；而这些修改或者替换，并不使相应技术方案的本质脱离本发明各实施例技术方案的精神和范围。

Claims (15)

  1. 一种直播视频的处理方法，其特征在于，所述方法包括：
    CDN服务器接收播放器发送的视频播放请求，所述视频播放请求中携带有播放器支持播放的视频格式和请求视频的标识信息；
    根据所述请求视频的标识信息获取请求视频的访问路径；
    从与所述访问路径对应的资源服务器中获取所述请求视频；
    将所述请求视频的格式转换成所述播放器支持播放的视频格式；
    将支持播放器播放的请求视频发送给所述播放器。
  2. 根据权利要求1所述方法，其特征在于，在将所述请求视频的格式转换成所述播放器支持播放的视频格式之前，所述方法还包括：
    判断所述播放器支持播放的视频格式是否为RTMP格式；
    所述将所述请求视频的格式转换成所述播放器支持播放的视频格式包括：
    若否，则将所述请求视频的格式转换成所述播放器支持播放的视频格式；
    所述将支持播放器播放的请求视频发送给所述播放器包括：
    若是，则直接将所述请求视频发送给所述播放器。
  3. 根据权利要求2所述方法，其特征在于，当所述播放器支持播放的视频格式为FLV格式时，所述将所述请求视频的格式转换成所述播放器支持播放的视频格式包括：
    将所述请求视频的格式转换成所述FLV格式；
    对所述FLV格式的请求视频进行缓存。
  4. 根据权利要求2所述方法，其特征在于，所述从与所述访问路径对应的资源服务器中获取所述请求视频包括：
    判断所述播放器支持播放的视频格式是否为HLS格式；
    若是，则从与所述访问路径对应的资源服务器中获取所述请求视频的切片视频。
  5. 根据权利要求4所述方法，其特征在于，从所述从与所述访问路径对应的资源服务器中获取所述请求视频之后，所述方法还包括；
    将所述请求视频的切片视频进行缓存；
    所述将支持播放器播放的请求视频发送给所述播放器包括：
    将所述请求视频的切片视频发送给所述播放器。
  6. 根据权利要求1所述方法，其特征在于，所述CDN服务器接收播放器发送的视频播放请求包括：
    CDN服务器接收播放器对应的域名解析系统DNS服务器发送的视频播放请求，所述DNS服务器用于接收所述播放器发送的所述视频播放请求并配置所述客户端对应的CDN服务器。
  7. 根据权利要求1所述方法，其特征在于，所述根据所述请求视频的标识信息获取请求视频的访问路径包括：
    将所述请求视频的标识信息求发送给调度服务器，以使得所述调度服务器获取与所述请求视频的标识信息对应的访问路径；
    接收所述调度服务器发送的所述访问路径。
  8. 一种CDN服务器，其特征在于，所述装置包括：
    接收单元，用于接收播放器发送的视频播放请求，所述视频播放请求中携带有播放器支持播放的视频格式和请求视频的标识信息；
    获取单元，用于根据所述请求视频的标识信息获取请求视频的访问路径；
    所述获取单元，还用于从与所述访问路径对应的资源服务器中获取所述请求视频；
    转换单元，用于将所述请求视频的格式转换成所述播放器支持播放的视频格式；
    发送单元，用于将支持播放器播放的请求视频发送给所述播放器。
  9. 根据权利要求8所述的CDN服务器，其特征在于，所述装置还包括：判断单元；
    所述判断单元，用于判断所述播放器支持播放的视频格式是否为RTMP格式；
    所述转换单元，具体用于若所述播放器支持播放的视频格式不是RTMP格式，则将所述请求视频的格式转换成所述播放器支持播放的视频格式；
    所述发送单元，具体用于若所述播放器支持播放的视频格式是RTMP格式，则直接将所述请求视频发送给所述播放器。
  10. 根据权利要求9所述的CDN服务器，其特征在于，所述转换单元包括：
    转换模块，用于当所述播放器支持播放的视频格式为FLV格式时，将所述请求视频的格式转换成所述FLV格式；
    缓存模块，用于对所述FLV格式的请求视频进行缓存。
  11. 根据权利要求9所述的CDN服务器，其特征在于，所述获取单元包括：
    判断模块，用于判断所述播放器支持播放的视频格式是否为HLS格式；
    获取模块，具体用于若所述播放器支持播放的视频格式为HLS格式，则从与所述访问路径对应的资源服务器中获取所述请求视频的切片视频。
  12. 根据权利要求10所述的CDN服务器，其特征在于，所述装置还包括：缓存单元；
    所述缓存单元，用于将所述请求视频的切片视频进行缓存；
    所述发送单元，具体用于将所述请求视频的切片视频发送给所述播放器。
  13. 根据权利要求8所述的CDN服务器，其特征在于，
    所述接收单元，具体用于接收播放器对应的域名解析系统DNS服务器发送的视频播放请求，所述DNS服务器用于接收所述播放器发送的所述视频播放请求并配置所述客户端对应的CDN服务器。
  14. 根据权利要求8所述的CDN服务器，其特征在于，所述获取单元还包括：
    发送模块，用于将所述请求视频的标识信息求发送给调度服务器，以使得所述调度服务器获取与所述请求视频的标识信息对应的访问路径；
    接收模块，用于接收所述调度服务器发送的所述访问路径。
  15. 一种CDN服务器，其特征在于，所述装置包括：
    一个或多个处理器；和
    存储器；
    其中所述存储器中存储有指令，经配置所述指令由所述一个或多个处理器执行，所述一个或多个处理器通过执行所述指令能进行如下操作：
    接收播放器发送的视频播放请求，所述视频播放请求中携带有播放器支持播放的视频格式和请求视频的标识信息；
    根据所述请求视频的标识信息获取请求视频的访问路径；
    从与所述访问路径对应的资源服务器中获取所述请求视频；
    将所述请求视频的格式转换成所述播放器支持播放的视频格式；
    将支持播放器播放的请求视频发送给所述播放器。
PCT/CN2016/088876 2015-12-14 2016-07-06 直播视频的处理方法及装置 Ceased WO2017101370A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US15/246,511 US20170171568A1 (en) 2015-12-14 2016-08-24 Method and device for processing live video

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201510926222.0A CN105872572A (zh) 2015-12-14 2015-12-14 直播视频的处理方法及装置
CN201510926222.0 2015-12-14

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US15/246,511 Continuation US20170171568A1 (en) 2015-12-14 2016-08-24 Method and device for processing live video

Publications (1)

Publication Number Publication Date
WO2017101370A1 true WO2017101370A1 (zh) 2017-06-22

Family

ID=56624549

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2016/088876 Ceased WO2017101370A1 (zh) 2015-12-14 2016-07-06 直播视频的处理方法及装置

Country Status (2)

Country Link
CN (1) CN105872572A (zh)
WO (1) WO2017101370A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114339325A (zh) * 2021-12-30 2022-04-12 珠海豹趣科技有限公司 一种基于安卓系统的多引擎动态壁纸播放方法及装置

Families Citing this family (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106454418A (zh) * 2016-10-11 2017-02-22 山东浪潮商用系统有限公司 播放非hls媒体文件的方法和装置
CN107707926A (zh) * 2017-03-09 2018-02-16 贵州白山云科技有限公司 一种直播流传输方法、装置和系统
CN108737848B (zh) * 2017-04-18 2021-04-02 杭州海康威视数字技术股份有限公司 一种视频处理方法、装置及云存储系统
CN113938714A (zh) * 2020-06-29 2022-01-14 阿里巴巴集团控股有限公司 播放控制方法、装置、电子设备和存储介质
CN113923502B (zh) * 2021-11-04 2023-03-21 上海哔哩哔哩科技有限公司 直播视频播放方法及装置
CN119814883A (zh) * 2024-12-04 2025-04-11 天翼云科技有限公司 请求处理方法、装置、电子设备及可读介质

Citations (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101697549A (zh) * 2009-10-23 2010-04-21 中兴通讯股份有限公司 流媒体的展示方法、系统以及流媒体管理服务器
CN102035852A (zh) * 2010-12-28 2011-04-27 乐视网信息技术（北京）股份有限公司 实现多种媒体格式流输出的装置和方法
CN102883216A (zh) * 2011-07-14 2013-01-16 上海聚力传媒技术有限公司 一种视频直播方法与设备
CN102883185A (zh) * 2011-07-14 2013-01-16 上海聚力传媒技术有限公司 一种视频点播方法与设备
CN103036889A (zh) * 2012-12-19 2013-04-10 常州中流电子科技有限公司 一种自适应的流媒体播放方法及其播放系统
US20130339474A1 (en) * 2011-05-26 2013-12-19 Vodafone Ip Licensing Limited Media sharing
CN103780925A (zh) * 2012-10-26 2014-05-07 深圳市快播科技有限公司 一种基于移动平台的在线视频点播方法和系统
CN103916679A (zh) * 2014-03-10 2014-07-09 百度在线网络技术（北京）有限公司 一种用于提供视频信息的方法、设备与系统

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101005369A (zh) * 2006-01-19 2007-07-25 深圳市瑞福特信息技术有限公司 一种分布式内容分发网及分布式内容分发和上传的方法
CN101582919A (zh) * 2009-04-14 2009-11-18 冯俊秋 网络电视播放方法及系统
US8751677B2 (en) * 2009-10-08 2014-06-10 Futurewei Technologies, Inc. System and method to support different ingest and delivery schemes for a content delivery network
CN103475901A (zh) * 2013-09-05 2013-12-25 乐视网信息技术（北京）股份有限公司 一种统一源的网络视频系统和设计方法
CN103957469B (zh) * 2014-05-21 2017-09-15 百视通网络电视技术发展有限责任公司 基于实时转封装的互联网视频点播方法及系统

Patent Citations (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101697549A (zh) * 2009-10-23 2010-04-21 中兴通讯股份有限公司 流媒体的展示方法、系统以及流媒体管理服务器
CN102035852A (zh) * 2010-12-28 2011-04-27 乐视网信息技术（北京）股份有限公司 实现多种媒体格式流输出的装置和方法
US20130339474A1 (en) * 2011-05-26 2013-12-19 Vodafone Ip Licensing Limited Media sharing
CN102883216A (zh) * 2011-07-14 2013-01-16 上海聚力传媒技术有限公司 一种视频直播方法与设备
CN102883185A (zh) * 2011-07-14 2013-01-16 上海聚力传媒技术有限公司 一种视频点播方法与设备
CN103780925A (zh) * 2012-10-26 2014-05-07 深圳市快播科技有限公司 一种基于移动平台的在线视频点播方法和系统
CN103036889A (zh) * 2012-12-19 2013-04-10 常州中流电子科技有限公司 一种自适应的流媒体播放方法及其播放系统
CN103916679A (zh) * 2014-03-10 2014-07-09 百度在线网络技术（北京）有限公司 一种用于提供视频信息的方法、设备与系统

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114339325A (zh) * 2021-12-30 2022-04-12 珠海豹趣科技有限公司 一种基于安卓系统的多引擎动态壁纸播放方法及装置
CN114339325B (zh) * 2021-12-30 2023-12-19 珠海豹趣科技有限公司 一种基于安卓系统的多引擎动态壁纸播放方法及装置

Also Published As

Publication number Publication date
CN105872572A (zh) 2016-08-17

Similar Documents

Publication Publication Date Title
WO2017101370A1 (zh) 直播视频的处理方法及装置
JP6915027B2 (ja) ライブストリーミングセグメント化方法、装置及びシステム
US10616301B2 (en) Request-based encoding for streaming content portions
US8738736B2 (en) Scalable content streaming system with server-side archiving
CN102611945B (zh) 一种流媒体切片方法、切片服务器及流媒体点播系统
WO2019128800A1 (zh) 一种内容服务的实现方法、装置及内容分发网络节点
WO2017101369A1 (zh) 直播视频的转码方法及装置
US20100241757A1 (en) System and Method for Storing Streaming Media File
WO2017088381A1 (zh) 一种直播视频的播放方法、装置及系统
WO2017088384A1 (zh) 一种直播视频的上传方法、装置及系统
CN103813185B (zh) 一种分段节目快速分发的方法、服务器及客户端
CN105100961A (zh) 视频缩略图生成方法及生成装置
WO2017096841A1 (zh) 一种拉流控制的方法、装置及系统
WO2015196590A1 (zh) 桌面云视频的播放处理方法及装置
WO2016015419A1 (zh) 流媒体的播放方法与播放装置
CN105872607A (zh) 提供多媒体内容的方法、服务器和终端设备
CN108200444B (zh) 一种视频直播的方法、装置和系统
WO2017080427A1 (zh) 一种媒体播放方法、终端、系统及计算机存储介质
US20170171568A1 (en) Method and device for processing live video
WO2017166496A1 (zh) 一种下载视频文件和提供视频文件的方法及装置
WO2024032363A1 (zh) 回源处理方法、装置、计算设备及存储介质
US11356716B2 (en) System for inserting supplemental content within a media stream
US10750248B1 (en) Method and apparatus for server-side content delivery network switching
CN112243136B (zh) 内容播放方法、视频存储方法和设备
US10298984B2 (en) Network PVR

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: 16874432

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 16874432

Country of ref document: EP

Kind code of ref document: A1