WO2016180029A1 - 直播媒体数据的方法、设备和*** - Google Patents

直播媒体数据的方法、设备和*** Download PDF

Info

Publication number
WO2016180029A1
WO2016180029A1 PCT/CN2015/099546 CN2015099546W WO2016180029A1 WO 2016180029 A1 WO2016180029 A1 WO 2016180029A1 CN 2015099546 W CN2015099546 W CN 2015099546W WO 2016180029 A1 WO2016180029 A1 WO 2016180029A1
Authority
WO
WIPO (PCT)
Prior art keywords
ott
multicast
channel
proxy server
server
Prior art date
Application number
PCT/CN2015/099546
Other languages
English (en)
French (fr)
Inventor
魏启坤
张锦辉
夏晋伟
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to ES15891722T priority Critical patent/ES2732226T3/es
Priority to SG11201709036XA priority patent/SG11201709036XA/en
Priority to EP15891722.9A priority patent/EP3285430B1/en
Priority to CA2985217A priority patent/CA2985217C/en
Publication of WO2016180029A1 publication Critical patent/WO2016180029A1/zh
Priority to US15/809,074 priority patent/US10205971B2/en

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/21—Server components or server architectures
    • H04N21/222—Secondary servers, e.g. proxy server, cable television Head-end
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/56—Provisioning of proxy services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/16—Arrangements for providing special services to substations
    • H04L12/18—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/70—Admission control; Resource allocation
    • H04L47/80—Actions related to the user profile or the type of traffic
    • H04L47/806—Broadcast or multicast traffic
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/10—Architectures or entities
    • H04L65/1045—Proxies, e.g. for session initiation protocol [SIP]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/60—Network streaming of media packets
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/60—Network streaming of media packets
    • H04L65/61—Network streaming of media packets for supporting one-way streaming services, e.g. Internet radio
    • H04L65/611—Network streaming of media packets for supporting one-way streaming services, e.g. Internet radio for multicast or broadcast
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/60—Network streaming of media packets
    • H04L65/75—Media network packet handling
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/60—Network streaming of media packets
    • H04L65/75—Media network packet handling
    • H04L65/756—Media network packet handling adapting media to device capabilities
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/40—Network security protocols
    • 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, manipulating MPEG-4 scene graphs
    • H04N21/2343—Processing of video elementary streams, e.g. splicing of video streams, manipulating MPEG-4 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/60—Network structure or processes for video distribution between server and client or between remote clients; Control signalling between clients, server and network components; Transmission of management data between server and client, e.g. sending from server to client commands for recording incoming content stream; Communication details between server and client 
    • H04N21/63—Control signaling related to video distribution between client, server and network components; Network processes for video distribution between server and clients or between remote clients, e.g. transmitting basic layer and enhancement layers over different transmission paths, setting up a peer-to-peer communication via Internet between remote STB's; Communication protocols; Addressing
    • H04N21/64—Addressing
    • H04N21/6405—Multicasting
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/60—Network structure or processes for video distribution between server and client or between remote clients; Control signalling between clients, server and network components; Transmission of management data between server and client, e.g. sending from server to client commands for recording incoming content stream; Communication details between server and client 
    • H04N21/63—Control signaling related to video distribution between client, server and network components; Network processes for video distribution between server and clients or between remote clients, e.g. transmitting basic layer and enhancement layers over different transmission paths, setting up a peer-to-peer communication via Internet between remote STB's; Communication protocols; Addressing
    • H04N21/643—Communication protocols
    • H04N21/64322—IP
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/16—Arrangements for providing special services to substations
    • H04L12/18—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast
    • H04L12/185—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast with management of multicast group membership
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/1066—Session management
    • H04L65/1073—Registration or de-registration

Definitions

  • Embodiments of the present invention relate to the field of computer networks and, more particularly, to methods, devices, and systems for streaming media data.
  • the video on the over the top (OTT) video website is divided into video on demand (VOD) and video on live (VOL) according to the viewing form.
  • VOD video on demand
  • VOL video on live
  • On-demand Watch the source stored on the video server. Because the source of the film has been completely completed, you can stop, fast forward and rewind, and drag back and forth at any time while watching.
  • Live broadcast Play live video, usually the content of each TV channel or the live broadcast of sports events and concerts. You cannot drag the playback progress back and forth. Viewers watching the same live media data see exactly the same content.
  • the OTT server belongs to the OTT service provider (the company that provides the OTT video website service). It can be placed in the data center of the carrier's city or in the OTT service provider's own computer room.
  • the OTT server can provide services such as registration, login, presentation program interface, and streaming media delivery to the OTT user.
  • multiple physical servers are generally provided to provide external functions.
  • An OTT client refers to a terminal used by an OTT user to view an OTT video.
  • desktop clients on desktop or laptop computers There are three common forms: desktop clients on desktop or laptop computers, mobile apps on mobile phones or tablets, and OTT set-top boxes.
  • HTTP HyperText Transfer Protocol
  • UDP User Datagram Protocol
  • the embodiment of the invention provides a method, a device and a system for playing live media data, which can avoid a large number of repeated live streams traversing the backbone network and reduce the bandwidth occupation of the live broadcast media data to the bearer network.
  • an OTT live proxy server including: a multicast resource allocation unit, configured for root Allocating a multicast resource to the designated channel according to the multicast resource allocation indication of the specified channel and the media description of the designated channel, where the multicast resource allocation indication is used to notify the OTT live proxy server to allocate a multicast resource for the designated channel,
  • the media description of the specified channel includes at least one resolution of the specified channel and a URL corresponding to the media data of the at least one resolution, where the multicast resource includes a multicast group corresponding to the designated channel or a corresponding channel a multicast group and a port corresponding to the at least one resolution; an obtaining unit, configured to obtain the media data corresponding to the at least one resolution from the OTT server to which the specified channel belongs in a unicast manner according to the media description of the specified channel;
  • the multicast unit is configured to convert the media data corresponding to the at least one resolution into multicast media data, and multicast the multicast media data to the multicast group.
  • the acquiring unit is further configured to obtain, by the OTT server, a media description of the specified channel; or, the media description of the specified channel is pre-stored in the OTT live proxy server. middle.
  • the specific implementation is: the multicast resource allocation indication is sent by the OTT server; or, the multicast The resource allocation indication is sent by the multicast replication point of the metropolitan area network where the OTT live proxy server is located.
  • the method further includes: a forwarding unit, configured to receive the OTT The channel join indication sent by the server, and the channel join indication is sent to the multicast replication point of the metropolitan area network where the OTT live proxy server is located, so that the multicast replication point adds the OTT client to the legitimate user of the designated channel.
  • a forwarding unit configured to receive the OTT The channel join indication sent by the server, and the channel join indication is sent to the multicast replication point of the metropolitan area network where the OTT live proxy server is located, so that the multicast replication point adds the OTT client to the legitimate user of the designated channel.
  • the channel join indication is used to notify the OTT client to join the specified channel.
  • the method further includes: The registration unit is configured to register, with the OTT server, an Internet Protocol IP network segment of the metropolitan area network where the OTT live proxy server is located and an IP address of the OTT live proxy server.
  • the multicast The resource allocation unit is further configured to feed back the allocated multicast resource to the OTT server, so that the OTT server sends the multicast resource to the OTT client, so that the OTT client can join the multicast group.
  • the multicast The resource allocation unit is further configured to send the correspondence between the designated channel and the multicast group of the designated channel to the OTT live agent service.
  • the multicast replication point in the metropolitan area network is located, so that the multicast replication point determines the multicast group corresponding to the designated channel according to the request sent by the OTT client to join the designated channel.
  • the multicast resource allocation unit is further configured to: perform the multicast according to the request sent by the OTT client to join the designated channel.
  • the resource is sent to the OTT client, so that the OTT client requests the media data of the specified channel from the multicast replication point.
  • the method further includes:
  • the multicast group management unit is configured to add the multicast replication point to the multicast group according to the multicast join request of the multicast replication point, and add the multicast replication to the multicast forwarding entry of the multicast group.
  • the corresponding egress port; or, according to the multicast egress request of the multicast replication point, the multicast replication point is deleted from the multicast group, and the multicast is deleted in the multicast forwarding entry of the multicast group.
  • the outbound port corresponding to the copy point.
  • the multicast resource allocation unit is further configured to: when the number of outgoing ports in the multicast forwarding entry of the multicast group is zero, delete the multicast group of the multicast group. Publish the item and disconnect the link to download the media data for the specified channel from the OTT server.
  • an OTT server including: a multicast resource allocation indication unit, configured to send a multicast resource allocation indication to an OTT live proxy server registered in the OTT server, where the multicast resource allocation indication is used for notification
  • the OTT live proxy server allocates a multicast resource to the specified channel
  • the media description management unit is configured to send the media description of the specified channel to the OTT live broadcast according to the request for obtaining the media description of the specified channel sent by the OTT live proxy server.
  • a proxy server wherein the media description of the specified channel includes at least one resolution of the specified channel and a URL corresponding to the media data of the at least one resolution; and a media resource management unit configured to perform, according to the OTT live proxy server
  • the media data acquisition request of the specified channel, the media data of the at least one resolution of the specified channel is sent to the OTT live broadcast server in a unicast manner.
  • the method further includes: a registration unit, configured to record, according to the registration request sent by the OTT live proxy server, an Internet Protocol IP network of the metropolitan area network where the OTT live proxy server is located And an IP address of the OTT live proxy server, where the registration request carries an IP network segment of the metropolitan area network where the OTT live proxy server is located and an IP address of the OTT live proxy server.
  • a registration unit configured to record, according to the registration request sent by the OTT live proxy server, an Internet Protocol IP network of the metropolitan area network where the OTT live proxy server is located And an IP address of the OTT live proxy server, where the registration request carries an IP network segment of the metropolitan area network where the OTT live proxy server is located and an IP address of the OTT live proxy server.
  • the method further includes: an authentication unit, configured to join according to an OTT client in the metropolitan area network where the OTT is located Determining, by the request of the designated channel, whether the OTT client is allowed to join the designated channel; the multicast resource allocation indication unit is specifically configured to: when the authentication unit determines that the OTT client is allowed to join the designated channel, and the OTT server does not exist When the multicast resource of the specified channel is sent by the OTT live proxy server, the multicast resource allocation indication is sent to the OTT live proxy server.
  • the authentication unit is further configured to send the channel to the OTT live proxy server after allowing the OTT client to join the designated channel.
  • the indication is added, the channel join indication is used to notify the OTT live proxy server to allow the OTT client to join the designated channel.
  • the authentication unit is further configured to send, by the OTT live proxy server, the multicast resource allocated for the designated channel to the multicast resource.
  • the OTT client so that the OTT client requests the media data of the specified channel to the multicast replication point, where the multicast resource includes the multicast group corresponding to the designated channel or the multicast group corresponding to the designated channel, and the designated channel At least one resolution corresponds to the port.
  • the method further includes: a relocation indication unit, configured to use the OTT client to join the specified channel, and the designated channel
  • the multicast resource indicates that the OTT client relocates the join request of the specified channel to the OTT live proxy server.
  • the third aspect provides a multicast replication point, including: a multicast management unit, configured to request, by the OTT live proxy server of the metropolitan area network, to join the multicast group allocated by the OTT live proxy server for the designated channel;
  • the acquiring unit is configured to receive the media data of the specified channel that is sent by the OTT live proxy server in a multicast manner, and the media data management unit is configured to send the media data of the specified channel to the OTT in a multicast manner or a unicast manner.
  • the method further includes: a rights management unit, configured to add the OTT client to the designated channel according to a channel joining indication sent by an OTT live proxy server of the metropolitan area network The legal user list, wherein the channel join indication is used to notify the multicast replication point that the OTT client is allowed to join the designated channel.
  • a rights management unit configured to add the OTT client to the designated channel according to a channel joining indication sent by an OTT live proxy server of the metropolitan area network The legal user list, wherein the channel join indication is used to notify the multicast replication point that the OTT client is allowed to join the designated channel.
  • the multicast management unit is further configured to: according to the multicast sent by the OTT client to join the specified channel Adding a request or a media data request, adding the OTT client to the multicast forwarding table of the multicast replication point, and requesting the OTT live proxy server to join the multicast group; or, according to the OTT client sending the exit request The request of the channel deletes the OTT client from the multicast forwarding table of the multicast replication point.
  • a fourth aspect provides a method for playing live media data, including: allocating multicast resources according to a specified channel And indicating, by the media description of the designated channel, a multicast resource, where the multicast resource allocation indication is used to notify the OTT live proxy server to allocate a multicast resource for the designated channel, where the media description of the designated channel includes the Specifying at least one resolution of the channel and a URL corresponding to the media data of the at least one resolution, the multicast resource includes a multicast group corresponding to the designated channel or a multicast group corresponding to the designated channel, and the at least one a media port corresponding to the resolution; the media data corresponding to the at least one resolution is obtained from the OTT server to which the specified channel belongs by using the media description of the specified channel; and the media data corresponding to the at least one resolution is converted into Multicast media data, and multicast the multicast media data to the multicast group.
  • the method further includes: Obtaining a media description of the specified channel; or, the media description of the designated channel is pre-stored in the OTT live proxy server.
  • the group is allocated to the designated channel according to the multicast resource allocation indication of the specified channel and the media description of the designated channel.
  • the method further includes: receiving a multicast resource allocation indication of the specified channel, where the multicast resource allocation indication is sent by the OTT server, or the multicast resource allocation indication is performed by the OTT live agent The multicast replication point of the metropolitan area network where the server is located is sent.
  • the method further includes: receiving a channel join sent by the OTT server Instructing, and adding the channel to the multicast replication point of the metropolitan area network where the OTT live proxy server is located, so that the multicast replication point adds the OTT client to the legal user list of the designated channel, where
  • the channel join indication is used to notify the OTT client to join the designated channel.
  • the method further includes: Register with the OTT server the Internet Protocol IP network segment of the metropolitan area network where the OTT live proxy server is located and the IP address of the OTT live proxy server.
  • the fifth possible implementation manner further includes: The allocated multicast resource is fed back to the OTT server, so that the OTT server sends the multicast resource to the OTT client, so that the OTT client can join the multicast group.
  • the method further includes: sending a correspondence between the designated channel and the multicast group of the designated channel to the OTT live proxy server A multicast replication point in the domain network, so that the multicast replication point determines the multicast group corresponding to the designated channel according to the request sent by the OTT client to join the designated channel.
  • the method further includes: sending, by the OTT client, the multicast resource to the OTT client according to the request for joining the designated channel So that the OTT client requests the media data of the specified channel from the multicast replication point.
  • the method further includes: Adding the multicast replication point to the multicast group according to the multicast join request of the multicast replication point, and adding the egress port corresponding to the multicast replication point in the multicast forwarding entry of the multicast group; or, according to The multicast exit request of the multicast replication point is deleted from the multicast group, and the egress port corresponding to the multicast replication point is deleted in the multicast forwarding entry of the multicast group.
  • the method further includes: deleting the multicast forwarding entry of the multicast group when the number of outgoing ports in the multicast forwarding entry of the multicast group is zero, and disconnecting A link to the media data of the specified channel is downloaded from the OTT server.
  • the fifth aspect provides a method for transmitting live media data, including: the OTT server sends a multicast resource allocation indication to the OTT live proxy server registered in the OTT server, where the multicast resource allocation indication is used to notify the OTT live agent.
  • the server allocates a multicast resource to the specified channel; the OTT server sends the media description of the specified channel to the OTT live proxy server according to the request of the OTT live proxy server to obtain the media description of the specified channel, where the designated channel
  • the media description includes at least one resolution of the specified channel and a URL corresponding to the media data of the at least one resolution; the OTT server obtains a request according to the media data of the specified channel by the OTT live proxy server, and specifies the The media data of the at least one resolution of the channel is sent to the OTT live proxy server in a unicast manner.
  • the method further includes: the OTT server records, according to the registration request sent by the OTT live proxy server, an Internet Protocol IP network segment of the metropolitan area network where the OTT live proxy server is located and The IP address of the OTT live proxy server, where the registration request carries the IP network segment of the metropolitan area network where the OTT live proxy server is located and the IP address of the OTT live proxy server.
  • the method further includes: the OTT server joining the designated channel according to the OTT client in the metropolitan area network where the OTT is located of Determining whether to allow the OTT client to join the designated channel; the sending, by the OTT server, the multicast resource allocation indication to the OTT live proxy server registered in the OTT server includes: when the OTT server determines to allow the OTT client to join the designation After the channel, and the OTT server does not have the multicast resource of the specified channel sent by the OTT live proxy server, the OTT server sends the multicast resource allocation indication to the OTT live proxy server.
  • the OTT server sends the channel join to the OTT live proxy server after allowing the OTT client to join the designated channel.
  • the channel join indication is used to notify the OTT live proxy server to allow the OTT client to join the designated channel.
  • the method further includes: sending, by the OTT server, the multicast resource that is sent by the OTT live proxy server for the specified channel to the OTT a client, so that the OTT client requests media data of the specified channel to the multicast replication point, where the multicast resource includes a multicast group corresponding to the designated channel or a multicast group corresponding to the designated channel and the designated channel At least one port corresponding to the resolution.
  • the method further includes: the OTT server, according to the request that the OTT client joins the designated channel, and the multicast resource of the designated channel, Instructing the OTT client to relocate the join request of the specified channel to the OTT live proxy server.
  • the sixth aspect provides a method for broadcasting live media data, including: requesting, by a OTT live proxy server of a metropolitan area network, a multicast group that is allocated by the OTT live proxy server to a designated channel; and receiving the OTT live proxy server to a group.
  • the media data of the specified channel sent by the broadcast mode; the media data of the designated channel is sent to the OTT client in a multicast manner or a unicast manner.
  • the method further includes: adding, according to the channel joining indication sent by the OTT live proxy server, the OTT client to the legal user list of the designated channel, where the channel joins The indication is used to notify the OTT client to join the specified channel.
  • the method further includes: receiving, according to the OTT client, a multicast join request or a media data request that joins the specified channel Adding the OTT client to the multicast forwarding table of the multicast replication point, and requesting the OTT live proxy server to join the multicast group; or, according to the request sent by the OTT client to exit the designated channel, The OTT client is deleted from the multicast forwarding table of the multicast replication point.
  • the method, device and system for playing live media data in the embodiment of the present invention firstly specify the frequency by the OTT server
  • the media data of the channel is transmitted to the OTT live proxy server of the metropolitan area network through unicast, and then the OTT live proxy server multicasts the media data to the multicast group, so that the multicast replication point in the multicast group is receiving.
  • the packets transmitted repeatedly between the OTT server and the metropolitan area network can be greatly reduced, thereby avoiding a large number of repeated live streams traversing the backbone network and reducing live broadcast media data to the bearer network. Bandwidth usage.
  • FIG. 1 is a network architecture diagram of an OTT system for broadcasting media data according to an embodiment of the present invention
  • FIG. 2 is a flowchart of a method for broadcasting media data according to an embodiment of the present invention
  • FIG. 3 is a flow chart of another method for broadcasting media data according to an embodiment of the present invention.
  • FIG. 4 is a flowchart of still another method for broadcasting media data according to an embodiment of the present invention.
  • FIG. 5 is an interaction flowchart of live media data according to an embodiment of the present invention.
  • FIG. 6 is another flow chart of interaction of live media data in an embodiment of the present invention.
  • FIG. 7 is another flow chart of interaction of live media data according to an embodiment of the present invention.
  • FIG. 8 is another flow chart of interaction of live media data according to an embodiment of the present invention.
  • FIG. 9 is another flow chart of interaction of live media data according to an embodiment of the present invention.
  • FIG. 10 is another flow chart of interaction of live media data according to an embodiment of the present invention.
  • FIG. 11 is another flow chart of interaction of live media data according to an embodiment of the present invention.
  • FIG. 12 is a schematic structural diagram of an OTT live broadcast proxy server according to an embodiment of the present invention.
  • FIG. 13 is another schematic structural diagram of an OTT live broadcast proxy server according to an embodiment of the present invention.
  • FIG. 14 is a schematic structural diagram of an OTT server according to an embodiment of the present invention.
  • FIG. 15 is another schematic structural diagram of an OTT server according to an embodiment of the present invention.
  • 16 is a schematic structural diagram of a multicast copy point according to an embodiment of the present invention.
  • FIG. 17 is a schematic structural diagram of still another OTT live broadcast proxy server according to an embodiment of the present invention.
  • FIG. 18 is a schematic structural diagram of still another embodiment of an OTT server according to an embodiment of the present invention.
  • FIG. 19 is a schematic diagram of still another structure of a multicast copy point according to an embodiment of the present invention.
  • Multicast transmission A point-to-multipoint network connection is implemented between the sender and each receiver. If a sender transmits the same data to multiple recipients at the same time, only one copy of the same data packet is required. It improves data transfer efficiency and reduces the possibility of congestion in the backbone network.
  • the Internet Group Management Protocol is a multicast protocol in the Internet Protocol family.
  • the protocol runs between the host and the multicast router to establish and maintain multicast group membership between the IP host and the multicast router directly adjacent to it.
  • the intra-domain multicast routing protocol uses a certain multicast routing algorithm to construct a multicast distribution tree for multicast packet forwarding based on the multicast group membership information maintained by IGMP.
  • the inter-domain multicast routing protocol advertises multicast routing information and multicast source information between the autonomous domains to enable multicast data to be forwarded between domains.
  • the OTT system may include: an OTT server, an OTT live proxy server, a multicast replication point, and an OTT client.
  • the OTT server may be located in the data center of a certain city of the operator, or in the own equipment room of the OTT service provider; the OTT live proxy server, the multicast replication point, and the OTT client are in the same metropolitan area network.
  • the media stream of the channel in the OTT server is transmitted to the OTT live proxy server of the metropolitan area network through the backbone network in a unicast manner.
  • the OTT live proxy server sends the media stream of the channel to the multicast group in a multicast manner, and then the multicast media in the multicast group sends the media stream of the channel to the OTT in unicast or multicast mode.
  • Client the OTT live proxy server sends the media stream of the channel to the multicast group in a multicast manner, and then the multicast media in the multicast group sends the media stream of the channel to the OTT in unicast or multicast mode.
  • the following describes the execution method of the OTT system shown in FIG. 1 from the perspectives of the OTT live proxy server, the OTT server, and the multicast replication point.
  • FIG. 2 is a flow chart of a method for broadcasting media data according to an embodiment of the present invention.
  • the method of Figure 2 is performed by an OTT live proxy server.
  • the method includes:
  • the multicast resource allocation indication is used to notify the OTT live proxy server to allocate a multicast resource for the designated channel, where the media description of the designated channel includes at least one resolution of the specified channel and the media of the at least one resolution.
  • a Uniform Resort Locator (URL) corresponding to the data, the multicast resource includes a multicast group corresponding to the designated channel or a multicast group corresponding to the designated channel, and a port port corresponding to the at least one resolution.
  • the OTT live broadcast proxy server also needs to receive the multicast resource allocation indication.
  • the multicast resource allocation indication is sent by the OTT server of the OTT live proxy server, or the multicast resource allocation indication is a multicast replication point of the metropolitan area network where the OTT live proxy server is located.
  • the OTT live proxy server may obtain the media data corresponding to the URL in a unicast manner according to the URL in the media description.
  • the OTT live proxy server allocates the multicast resource of the channel according to the channel allocation indication of the OTT server, and obtains the media data of the channel from the OTT server, and then multicasts the media data of the channel to the multicast group corresponding to the channel. Therefore, the multicast replication point in the multicast group can transmit the media data of the channel to the OTT client that joins the channel, which can avoid a large number of repeated live streams from crossing the backbone network, thereby greatly reducing the repeated transmission between the OTT server and the metropolitan area network.
  • the packet reduces the bandwidth occupied by the live media data on the bearer network.
  • the OTT client obtains the audio or video program of the channel from the nearest network device (multicast copy point), and can shorten the video startup delay compared to the audio or video program that obtains the channel from the OTT server. , to reduce the packet loss rate / jitter, thus providing users with a better experience.
  • the method before step S201, further includes: obtaining, by the OTT server, a media description of the specified channel.
  • the media description of the designated channel is pre-stored in the OTT live proxy server.
  • the OTT service provider may pre-store the relevant media descriptions of some or all of the channels on the OTT proxy server to reduce the information interaction caused by the media description request.
  • the method further includes: receiving a channel joining indication sent by the OTT server, and sending the channel joining indication to a multicast replication point of the metropolitan area network where the OTT live proxy server is located, so that the multicast replication point is Adding an OTT client to the list of legitimate users of the designated channel, wherein the channel join indication is used for notification Allow the OTT client to join the specified channel.
  • the method further includes: registering, by the OTT server, an Internet Protocol (IP) network segment of the metropolitan area network where the OTT live proxy server is located, and an IP address of the OTT live proxy server.
  • IP Internet Protocol
  • the method further includes: feeding back the allocated multicast resource to the OTT server, so that the OTT server sends the multicast resource to the OTT client, so that the OTT client can join The multicast group.
  • the method further includes: sending a correspondence between the designated channel and the multicast group of the designated channel to a multicast replication point in the metropolitan area network where the OTT live proxy server is located,
  • the multicast replication point determines the multicast group corresponding to the designated channel according to the request sent by the OTT client to join the designated channel.
  • the method further includes: sending the multicast resource to the OTT client according to the request that the OTT client sends the specified channel, so that the OTT client requests the media data of the specified channel from the multicast replication point. .
  • the method further includes: adding the multicast replication point to the multicast group according to the multicast join request of the multicast replication point, and performing multicast forwarding entries in the multicast group. Add the egress port corresponding to the multicast replication point.
  • the method further includes: deleting the multicast replication point from the multicast group according to the multicast exit request of the multicast replication point, and performing multicast in the multicast group.
  • the forwarding entry deletes the egress port corresponding to the multicast replication point.
  • the method further includes deleting the multicast forwarding entry of the multicast group when the number of outgoing ports in the multicast forwarding entry of the multicast group is zero, and disconnecting the specified channel from the OTT server. Link to the media data.
  • FIG. 3 is a flow chart of another method for broadcasting media data according to an embodiment of the present invention.
  • the method of Figure 3 is performed by an OTT live proxy server.
  • the method includes:
  • the OTT server sends a multicast resource allocation indication to the OTT live proxy server registered in the OTT server.
  • the multicast resource allocation indication is used to notify the OTT live proxy server to allocate multicast resources to the designated channel.
  • the OTT server sends the media description of the specified channel to the OTT live proxy server according to the request of the OTT live proxy server to obtain the media description of the specified channel.
  • the media description of the designated channel includes at least one resolution of the designated channel and the at least one resolution The URL corresponding to the media data.
  • the OTT server sends the media data of the at least one resolution of the specified channel to the OTT live proxy server in a unicast manner according to the media data acquisition request of the specified channel by the OTT live proxy server.
  • the OTT server instructs the OTT live proxy server to establish a multicast resource of the multicast group allocation channel, and sends the media data of the channel to the OTT live proxy server in a unicast manner, so that the OTT live proxy server sets the media data of the channel.
  • the OTT client that is added to the multicast group through the multicast replication point can prevent a large number of duplicate live streams from traversing the backbone network, thereby greatly reducing the number of repeated transmissions between the OTT server and the metropolitan area network, and reducing the live broadcast data to the bearer. The bandwidth occupied by the network.
  • the method further includes: the OTT server records, according to the registration request sent by the OTT live proxy server, an Internet Protocol IP network segment of the metropolitan area network where the OTT live proxy server is located, and an IP address of the OTT live proxy server.
  • the registration request carries the IP network segment of the metropolitan area network where the OTT live proxy server is located and the IP address of the OTT live proxy server.
  • the method further includes: determining, by the OTT server, that the OTT client is allowed to join the designated channel according to the request that the OTT client in the metropolitan area network where the OTT is located joins the designated channel. Further, the OTT server sends the multicast resource allocation indication to the OTT live proxy server registered in the OTT server, where the OTT server determines that the OTT client is allowed to join the designated channel, and the OTT server does not When there is a multicast resource of the specified channel sent by the OTT live proxy server, the OTT server sends the multicast resource allocation indication to the OTT live proxy server.
  • the method further includes: after allowing the OTT client to join the designated channel, sending, by the OTT server, a channel join indication to the OTT live proxy server, where the channel join indication is used to notify the OTT live proxy server to allow the OTT The client joins the specified channel.
  • the method further includes: sending, by the OTT server, the multicast resource that is allocated by the OTT live proxy server for the specified channel to the OTT client, so that the OTT client sends a multicast copy point to the multicast Requesting the media data of the specified channel, where the multicast resource includes a multicast group corresponding to the designated channel or a multicast group corresponding to the designated channel and a port corresponding to at least one resolution of the designated channel.
  • the method further includes: the OTT server instructing the OTT client to specify the channel according to the request that the OTT client joins the specified channel and the multicast resource of the designated channel The join request is relocated to the OTT live proxy server.
  • FIG. 4 is a flow chart of still another method for broadcasting media data according to an embodiment of the present invention.
  • the method of Figure 4 is performed by the multicast replication point. Row.
  • the method includes:
  • the OTT live proxy server located in the metropolitan area network is requested to join the multicast group allocated by the OTT live proxy server for the designated channel.
  • the media data of the specified channel is sent to the OTT client in a multicast mode or a unicast manner.
  • the multicast replication point obtains the media data of the channel from the multicast group established by the OTT live proxy server, and sends the media data of the channel to the OTT client, so that the OTT client does not need to directly obtain the media data of the channel from the OTT server.
  • a large number of repeated live streams are traversed through the backbone network, which greatly reduces the number of repeated transmissions between the OTT server and the metropolitan area network, and reduces the bandwidth occupied by the live media data to the bearer network.
  • the method further includes: adding the OTT client to the multicast replication point according to the multicast join request or the media data request sent by the OTT client to join the specified channel. Publish and request to join the multicast group to the OTT live proxy server.
  • the method further includes deleting the OTT client from the multicast forwarding table of the multicast replication point according to the request sent by the OTT client to exit the specified channel.
  • the method further includes: adding, according to the channel joining indication sent by the OTT live proxy server, the OTT client to the legal user list of the designated channel, where the channel joining indication is used to notify the OTT client. Join the specified channel.
  • the method may further include: receiving a channel joining indication sent by the OTT live proxy server.
  • the method further includes: when the OTT client of the multicast forwarding table of the multicast replication point is zero, sending a multicast exit request to the OTT live proxy server, requesting to quit the multicast group.
  • the method may further include: authenticating the right of the OTT client to join the designated channel according to the media data request sent by the OTT client, and the legal user list of the designated channel, and authenticating the right of the OTT client to join the designated channel, and After the authentication, the OTT live injection proxy server is requested to join the multicast group.
  • FIG. 5 is a flow chart of interaction of live media data in an embodiment of the present invention.
  • the OTT live proxy server has not allocated the multicast resource of channel 1, and the multicast replication point is not added to the multicast group of channel 1.
  • the media data is transmitted in multicast mode.
  • the OTT live proxy server sends a registration request to the OTT server.
  • the OTT live proxy server sends a registration request to the OTT server, where the registration request carries registration information for requesting registration of the IP network segment of the metropolitan area network and the IP address of the OTT live proxy server.
  • an OTT live proxy server that is already registered with the OTT server exists in the metropolitan area network where the OTT client is located, which is a precondition for implementing the method of the present invention.
  • the OTT client 1 sends a channel join request to the OTT server.
  • the OTT client 1 sends a channel join request to the OTT server, requesting to join channel 1.
  • the OTT server sends a multicast resource allocation indication to the OTT live proxy server.
  • the OTT server obtains the IP address of the OTT client 1 and the channel 1 to be joined according to the channel joining request sent by the OTT client 1, and then obtains the city to which the IP address belongs from the already registered OTT live proxy server according to the IP address.
  • the WAN live proxy server (hereinafter referred to as the OTT live proxy server) corresponding to the OTT client 1 is obtained.
  • the OTT live proxy server finds that the OTT live proxy server has not joined the channel 1, the OTT live proxy server sends a multicast resource allocation indication to the OTT live proxy server to allocate the multicast resource to the channel 1.
  • the OTT live proxy server sends a media description request to the OTT server.
  • the OTT live proxy server After receiving the multicast resource allocation indication, the OTT live proxy server sends a media description request to the OTT server, requesting the media description of channel 1.
  • the OTT server sends a media description to the OTT live proxy server.
  • the OTT server returns the media description of channel 1 according to the media description request.
  • the media description may include channel basic information, channel resolution (possibly several different resolutions), URLs corresponding to each resolution media stream, and the like.
  • S506 The OTT live proxy server allocates multicast resources and creates a multicast group.
  • steps S504 and S505 are not necessarily steps that must be performed.
  • the OTT service provider may pre-store the relevant media descriptions of some or all channels on the OTT live proxy server to reduce the information interaction caused by the media description request.
  • the OTT live proxy server allocates the multicast resource of channel 1 according to the media description of channel 1 according to the multicast resource allocation indication of channel 1.
  • the multicast resource of channel 1 may include the multicast group Group1 of channel 1, or the multicast group Group1 of channel 1, and the port corresponding to each code stream (or each resolution).
  • the OTT live proxy server can determine the multicast group Group1 through the IP address of the multicast group Group1; or the OTT live proxy server can pass the IP address and multicast source of the multicast group Group1 (ie, OTT live broadcast) The IP address of the proxy server to determine the multicast group Group1.
  • the embodiment of the present invention takes the multicast group Group1 as an example by using the IP address of the multicast group Group1.
  • each resolution of channel 1 corresponds to one code stream
  • the OTT live proxy server needs to allocate at least one separate port for each code stream (or each resolution). For example, if channel 1 has two kinds of resolutions (resolution 1 and resolution 2), the code stream corresponding to resolution 1 should be allocated 1 port separately, and the code stream corresponding to resolution 2 should be allocated 1 port separately. Of course, you can also assign more ports to resolution 1 and resolution 2.
  • the OTT live proxy server can only determine the multicast group Group1 of channel 1, and the multicast resource allocation of channel 1 can be completed.
  • the OTT live proxy server may also pre-promote the port corresponding to each resolution with the multicast replication point or the OTT client, without configuring the corresponding port for each channel different resolution.
  • the OTT live proxy server sends the allocated multicast resource to the OTT server.
  • the OTT live proxy server may send the allocated multicast resources to the OTT server.
  • the multicast resource may include the multicast group Group1 of the channel 1 or the multicast group Group1 of the channel 1 and a port corresponding to the code stream of each resolution.
  • the OTT server sends a channel join indication to the OTT live proxy server.
  • the OTT server may authenticate the OTT client 1 to determine whether the OTT client 1 has the right to join channel 1.
  • the OTT server may send a channel join indication to the OTT live proxy server to notify the OTT live proxy server that the IP of the OTT client 1 can join the multicast group Group1.
  • the authentication operation may be performed immediately after receiving the channel joining request, or may be performed after the multicast resource is allocated to the channel 1.
  • the embodiment of the present invention is not limited herein.
  • the OTT live proxy server sends a channel join indication to the multicast replication point.
  • the OTT live proxy server receives the channel join indication, and may send the channel join indication to the multicast replication point to which the OTT client 1 belongs, so that the OTT client 1 belongs to the multicast replication point to the OTT client.
  • the playback request of terminal 1 is authenticated.
  • the OTT server sends a media description to the OTT client 1.
  • the OTT server notifies the OTT client 1 of the media description.
  • the media description includes the resolution of channel 1 (possibly several different resolutions), Group1 (multicast group IP), the port corresponding to each resolution media stream, and the like.
  • the OTT live proxy server sends a media data acquisition request to the OTT server.
  • the OTT live proxy server sends a media data acquisition request to the OTT server to request to acquire all the media data of the channel 1 (for example, multiple resolutions, it is necessary to acquire media data of all resolutions).
  • the OTT server sends the media data to the OTT live proxy server in a unicast manner.
  • the OTT server sends the media data to the OTT live proxy server in a unicast manner.
  • step S511 and step S512 reference may be made to the process flow of the OTT client requesting media data and the OTT server unicasting to the OTT client in the OTT server-OTT client mode in the prior art, the present invention.
  • the examples are not described here.
  • the OTT live proxy server converts the unicast media data into multicast media data, and multicasts the media data in the multicast group.
  • the OTT live proxy server After receiving the unicast media data sent by the OTT server, the OTT live proxy server converts the data into a multicast packet.
  • the multicast packet is multicast in the multicast group Group1.
  • the multicast replication point located in the multicast group Group1 can receive the multicast packet sent by the OTT live proxy server.
  • the OTT live broadcast proxy server After the OTT live broadcast proxy server receives the unicast packet, it does not immediately convert to a multicast packet, but caches a certain amount of packets, and performs FEC encoding. Then, the media multicast packet is sent in the multicast group, and the FEC packet is sent by another port. If a channel has multiple streams, each stream has a corresponding FEC packet, which is transmitted in a multicast group by a separate port. After receiving the multicast packet, the OTT client will use the FEC to restore the correct data packet if it finds that there is a packet loss/error packet.
  • a certain sequence number is added to the packet to uniquely represent a certain packet.
  • This sequence number can use the IP extension header; it can also use the UDP extension header; it can also add the RTP header and use the RTP sequence number; or add a field of a certain byte length to the front of the payload as the sequence number.
  • the OTT live proxy server sends these multicast packets and simultaneously caches multicast packets for a certain length of time. When the OTT client finds that there is a packet loss/error packet, the OTT live proxy server is required to retransmit the packet of the corresponding sequence number.
  • OTT live proxy server may also transmit the multicast packet in other manners, which is not limited herein.
  • the code stream of OTT unicast is generally VBR, that is, the code stream will change. If the code stream is too small and small, it will be easier to drop packets, but because OTT unicast is generally based on TCP bearer, the TCP/IP protocol stack will implement packet loss by itself. pass. In our solution, we need to change the TCP-based unicast to UDP-based multicast transmission, and UDP has no mechanism for packet loss retransmission. If it is found that the current unicast code stream fluctuates greatly (for example, exceeds 20% of the average code stream), the code stream is smoothed. The specific method is to buffer a part of the message to delay sending, avoiding the peak period.
  • the OTT client 1 After receiving the media description fed back in step S510, the OTT client 1 knows that it needs to join the multicast group Group1 to join the audio or video program of the channel 1, and then the OTT client 1 sends an IGMP join Group1 message to the associated multicast replication point. Request to join the multicast group Group1.
  • the multicast replication point requests to join the multicast group to the OTT live proxy server.
  • the multicast replication point After receiving the IGMP join Group1 message, the multicast replication point first authenticates the OTT client 1, and determines whether the OTT client 1 can join the audio or video program of channel 1.
  • step S509 Since the channel join indication in step S509 indicates that the multicast copy point allows the OTT client 1 to join the audio or video program of channel 1, this indicates that the authentication of the OTT client 1 is successful.
  • the multicast replication point needs to confirm whether it has already joined the multicast group Group1.
  • the multicast replication point can confirm that it has not joined the multicast group Group1.
  • the multicast replication point needs to send a PIM join Group1 message to the OTT live proxy server to request to join the multicast group Group1.
  • the multicast replication point receives the multicast media data in the multicast group.
  • the media data of the channel 1 multicast by the OTT live proxy server in the multicast group Group1 can be received.
  • the multicast replication point multicasts the media data to the OTT client 1.
  • the multicast replication point After receiving the data of the Group1 multicast group, the multicast replication point queries the multicast forwarding table record and finds that the OTT client 1 joins the group1 and forwards the multicast media packet to the OTT client 1. At this time, the OTT client 1 can normally join the audio or video program of channel 1.
  • the OTT server allocates the multicast resource to the OTT live proxy server of the MAN of the OTT client according to the channel join request sent by the OTT client, and then passes the media data of the channel of the OTT server through the unicast mode. It is transmitted to the OTT live proxy server, and then sent to the multicast replication point by the OTT live proxy server in multicast mode. Finally, the multicast replication point multicasts the media data of the channel to the OTT client, so that the same metropolitan area network The OTT client in the same network can share the media data resources of the same channel, thereby saving a large amount of bandwidth for the OTT server and improving the channel bandwidth resource utilization of the OTT server.
  • IGMP join multicast group IP addresses some of which are IGMP joins (multicast group IP address + multicast source IP address). That is, some are in multicast groups.
  • An IP address is used to indicate a multicast group, and some are represented by a multicast group IP address + a multicast source IP address.
  • the OTT client sends a channel join request to the OTT server to request to join channel 1, thereby triggering the OTT server to send a multicast resource allocation indication to the OTT live proxy server.
  • the OTT client may directly send a channel join request to the multicast replication point, request to join the channel 1, and then send a multicast resource allocation indication to the OTT live proxy server through the multicast replication point, indicating the OTT live agent.
  • the server allocates multicast resources to channel 1.
  • the remaining steps may be similar to the steps of the embodiment of the present invention, and the embodiments of the present invention are not described herein again.
  • FIG. 6 is a flow chart of interaction of live media data in an embodiment of the present invention.
  • the OTT live proxy server has allocated the multicast resource of channel 1, and the multicast replication point has also joined the multicast group of channel 1.
  • the media data is transmitted in multicast mode.
  • the OTT client 2 sends a channel join request to the OTT server.
  • the OTT client 2 sends a channel join request to the OTT server, requesting to join channel 1.
  • the OTT server sends a channel join indication to the OTT live proxy server.
  • the OTT server may authenticate the OTT client 2 to determine whether the OTT client 2 has the right to join channel 1.
  • the OTT server determines the OTT live proxy server of the metropolitan area network where the OTT client 2 is located according to the channel join request of the OTT client 2, and further knows that the OTT live proxy server has allocated the multicast resource of the channel 1.
  • the OTT server may send a channel join indication to the OTT live proxy server to notify the OTT live proxy server that the IP of the OTT client 2 can join the multicast group Group1.
  • the OTT live proxy server sends a channel join indication to the multicast replication point.
  • the OTT live proxy server receives the channel join indication, and may send the channel join indication to the multicast replication point to which the OTT client 2 belongs, so that the OTT client 2 belongs to the multicast replication point to the OTT client. End 2's play request is authenticated.
  • the OTT server sends a media description to the OTT client 2.
  • the OTT server notifies the OTT client 2 of the media description.
  • the media description includes the resolution of channel 1 (possibly several different resolutions), Group1 (multicast group IP), the port corresponding to each resolution media stream, and the like.
  • the OTT client 2 After receiving the media description fed back in step S510, the OTT client 2 knows that it needs to join the multicast group Group1 to join the audio or video program of the channel 1, and the OTT client 2 sends an IGMP join Group1 message to the multicast copy point to which it belongs. Request to join the multicast group Group1.
  • the multicast replication point multicasts and sends the media data to the OTT client 2.
  • the multicast replication point has joined the multicast group Group1, and receives the multicast media data in the multicast group.
  • the multicast replication point After receiving the IGMP join Group1 message, the multicast replication point first authenticates the OTT client 2 to determine whether the OTT client 2 can join the audio or video program of channel 1. Since the channel join indication in step S603 indicates that the multicast copy point allows the OTT client 2 to join the audio or video program of channel 1, this indicates that the authentication of the OTT client 2 is successful.
  • the multicast replication point can forward the multicast media packet to the OTT client 2, and the OTT client 2 can normally join the audio or video program of the channel 1.
  • FIG. 7 is a flow chart of interaction of live media data in an embodiment of the present invention.
  • the OTT live proxy server has not allocated the multicast resource of channel 1, and the multicast replication point is not added to the multicast group of channel 1.
  • the media data is transmitted in unicast mode.
  • the OTT live proxy server sends a registration request to the OTT server.
  • the OTT client 1 sends a channel join request to the OTT server.
  • the OTT server sends a multicast resource allocation indication to the OTT live proxy server.
  • the OTT live proxy server sends a media description request to the OTT server.
  • the OTT server sends a media description to the OTT live proxy server.
  • S706 The OTT live proxy server allocates multicast resources and creates a multicast group.
  • steps S701-S706 For the specific implementation of the steps S701-S706, reference may be made to the steps S501-S506 of FIG. 5, and details are not described herein again.
  • the OTT live proxy server sends the allocated multicast resource to the OTT server.
  • the OTT live proxy server After the OTT live proxy server allocates the multicast resource (the multicast group Group1 of the channel 1 or the multicast group Group1 of the channel 1 and the port corresponding to the code stream of each resolution) to the channel 1, the OTT live proxy server can send the allocated group to the OTT server. Broadcast resources.
  • the OTT live proxy server sends a correspondence between the channel and the multicast group to the multicast replication point.
  • the OTT live proxy server sends the correspondence between the channel and the multicast group to the multicast replication point.
  • the multicast replication point receives the request of the OTT client to join the channel 1, the multicast IP address to be joined can be known.
  • the OTT live proxy server sends a media data acquisition request to the OTT server.
  • the OTT live proxy server sends a media data acquisition request to the OTT server to request to acquire all the media data of the channel 1 (for example, multiple resolutions, it is necessary to acquire media data of all resolutions).
  • the OTT server sends the media data to the OTT live proxy server in a unicast manner.
  • the OTT server sends the media data to the OTT live proxy server in a unicast manner.
  • step S709 and step S710 reference may be made to the process flow of the OTT client requesting media data in the OTT server-OTT client mode and the OTT server transmitting the media data to the OTT client in the OTT server-OTT client mode.
  • the examples are not described here.
  • the OTT live proxy server converts the unicast media data into multicast media data.
  • step S711 For the specific implementation of the step S711, reference may be made to the step S513 of FIG. 5, and details are not described herein again.
  • the OTT server sends a channel join indication to the OTT live proxy server.
  • step S712 For the specific implementation of the step S712, reference may be made to the step S508 of FIG. 5, which is not described herein again.
  • the OTT server instructs the OTT client 1 to redirect to the OTT live proxy server.
  • the OTT server sends a redirect command to the OTT client 1, requesting the OTT client 1 to obtain a media description from the OTT live proxy server.
  • the IP address of the OTT live proxy server is included in this command.
  • the OTT client 1 sends a channel join request to the OTT live proxy server.
  • the OTT client 1 After receiving the redirect command, the OTT client 1 sends a channel join request to the OTT live proxy server to request to join channel 1.
  • the OTT live proxy server changes the video URL in the media description to point to the multicast replication point.
  • the OTT live proxy server modifies the URL of the video to the IP address of the multicast replication point to which the OTT client 1 belongs according to the media description downloaded in step S705.
  • S716 The OTT live proxy server sends a channel join indication to the multicast replication point.
  • the OTT live proxy server receives the channel join indication, and may send the channel join indication to the multicast replication point to which the OTT client 1 belongs, so that the OTT client 1 belongs to the multicast replication point to the OTT client.
  • the playback request of terminal 1 is authenticated.
  • S717 The OTT live proxy server multicasts media data in the multicast group.
  • step S717 For the specific implementation of the step S717, reference may be made to the step S513 of FIG. 5, which is not described herein again.
  • the OTT live proxy server sends the modified media description to the OTT client 1.
  • the OTT live proxy server sends the media description of channel 1 to the OTT client 1, where the URL of the video has been modified to the IP of the multicast replication point to which the OTT client 1 belongs.
  • the OTT client 1 sends a media data acquisition request to the multicast replication point.
  • the OTT client 1 requests to join the multicast group to the associated multicast replication point according to the video URL in the media description.
  • the multicast replication point requests to join the multicast group to the OTT live proxy server.
  • the multicast replication point learns that the OTT client 1 is to join the channel 1 video according to the request, and determines that the OTT client 1 is allowed to join the channel 1, and then queries the channel 1 corresponding to the multicast group Group1.
  • the multicast replication point can send a PIM join Group1 message to join the multicast group Group1.
  • the multicast replication point receives the multicast media data in the multicast group, and caches and converts the data into unicast media data.
  • the multicast media data sent by the multicast group Group1 is received.
  • the multicast replication point caches the multicast media data and converts it into unicast media data.
  • the multicast replication point unicasts the media data to the OTT client 1.
  • OTT client 1 can join the video of channel 1.
  • FIG. 8 is a flow chart of interaction of live media data in an embodiment of the present invention.
  • the OTT live proxy server has allocated the multicast resource of channel 1, and the multicast replication point has also joined the multicast group of channel 1.
  • the media data is transmitted in unicast mode.
  • the OTT client 2 sends a channel join request to the OTT server.
  • the OTT client 2 sends a channel join request to the OTT server, requesting to join channel 1.
  • the OTT server sends a channel join indication to the OTT live proxy server.
  • the OTT server may authenticate the OTT client 2 to determine whether the OTT client 2 has the right to join channel 1.
  • the OTT server determines the OTT live proxy server of the metropolitan area network where the OTT client 2 is located according to the channel join request of the OTT client 2, and further knows that the OTT live proxy server has allocated the multicast resource of the channel 1.
  • the OTT server may send a channel join indication to the OTT live proxy server to notify the OTT live proxy server that the IP of the OTT client 2 can join the multicast group Group1.
  • the OTT server instructs the OTT client 2 to redirect to the OTT live proxy server.
  • the OTT server sends a redirect command to the OTT client 2, and requests the OTT client 2 to obtain a media description from the OTT live proxy server.
  • the IP address of the OTT live proxy server is included in this command.
  • the OTT client 21 sends a channel join request to the OTT live proxy server.
  • the OTT client 2 After receiving the redirect command, the OTT client 2 sends a channel join request to the OTT live proxy server to request to join channel 1.
  • the OTT live proxy server sends a channel join indication to the multicast replication point.
  • the OTT live proxy server receives the channel join indication, and may send the channel join indication to the multicast replication point to which the OTT client 2 belongs, so that the OTT client 2 belongs to the multicast replication point to the OTT client. End 2's play request is authenticated.
  • the OTT live proxy server sends the modified media description to the OTT client 2.
  • the OTT live proxy server modifies the URL of the video to the IP address of the multicast replication point to which the OTT client 2 belongs according to the media description of channel 1.
  • the OTT live proxy server sends the media description of channel 1 to the OTT client 2, wherein the URL of the video has been modified to the IP of the multicast replication point to which the OTT client 2 belongs.
  • the OTT client 2 requests downloading media data from the associated multicast copy point according to the video URL in the media description.
  • the multicast replication point has been added to the multicast group. At this time, the multicast replication point receives the multicast media data in the multicast group, and caches and converts the data into unicast packets.
  • the multicast replication point may unicast the media data to the OTT client 2 according to the media data acquisition request of the OTT client 2.
  • OTT client 2 can join the channel 1 video.
  • FIG. 9 is a flow chart of interaction of live media data in an embodiment of the present invention.
  • the OTT client 1 has joined the video program of channel 1 through the multicast copy point.
  • the IGMP leaveGroup1 message may be sent to the uplink device (multicast replication point) to request to exit the Group1 multicast group.
  • the multicast replication point deletes the OTT client 1 from the multicast forwarding table.
  • the multicast replication point After the multicast replication point receives the IGMP leave Group1 message from the OTT client, the multicast replication point removes the OTT client from the Group1 multicast forwarding table.
  • the multicast replication point requests the OTT live proxy server to adjust the multicast group.
  • the multicast replication point finds that there is no OTT client in the Group1 multicast forwarding table, the multicast table is used. The item is deleted, and the IGMP leave group1 message is sent to the upstream device (OTT Live Proxy Server) to request to adjust the multicast group.
  • OTT Live Proxy Server the upstream device
  • S904 The OTT live proxy server deletes the corresponding egress port in the multicast entry of the multicast group.
  • the OTT live proxy server After receiving the IGMP leave group1 message sent by a downlink port, the OTT live proxy server deletes the egress port of the corresponding downlink port in the multicast forwarding entry of the group.
  • the multicast group corresponds to channel 1.
  • the OTT live proxy server can delete the Group1 multicast entry, disconnect the channel 1 from the media download connection of the OTT server, release the multicast resource allocated for channel 1, and notify the OTT server.
  • the multicast replication point by recycling resources, the multicast replication point, the OTT live proxy server, or the OTT server can be reduced, and the resource utilization efficiency is improved.
  • FIG. 10 is a flow chart of interaction of live media data in an embodiment of the present invention.
  • the OTT live proxy server has not allocated the multicast resource of channel 1, and the multicast replication point is not added to the multicast group of channel 1.
  • the media data is transmitted in multicast mode.
  • the OTT live proxy server sends a registration to the OTT server.
  • the OTT client 1 sends a channel join request to the OTT server.
  • the OTT server sends a multicast resource allocation indication to the OTT live proxy server.
  • the OTT live proxy server sends a media description request to the OTT server.
  • the OTT server sends a media description to the OTT live proxy server.
  • S1006 The OTT live proxy server allocates multicast resources and creates a multicast group.
  • the OTT live proxy server sends the allocated multicast resource to the OTT server.
  • the OTT server sends a channel join indication to the OTT live proxy server.
  • the OTT live proxy server sends a channel join indication to the multicast replication point.
  • steps S1001-S1009 For the specific implementation of the steps S1001-S1009, reference may be made to the steps S501-S505 of FIG. 5, and details are not described herein again.
  • the OTT server instructs the OTT client 1 to redirect to the OTT live proxy server.
  • the OTT server sends a redirect command to the OTT client 1, requesting the OTT client 1 to obtain a media description from the OTT live proxy server.
  • the IP address of the OTT live proxy server is included in this command.
  • the OTT client 1 sends a channel join request to the OTT live proxy server.
  • the OTT client 1 After receiving the redirect command, the OTT client 1 sends a channel join request to the OTT live proxy server to request to join channel 1.
  • the OTT live proxy server sends the modified media description to the OTT client 1.
  • the OTT live proxy server modifies the URL of the video to the IP address of the multicast replication point to which the OTT client 1 belongs according to the media description downloaded in step S1005.
  • the OTT live proxy server sends the media description of channel 1 to the OTT client 1, where the URL of the video has been modified to the IP of the multicast replication point to which the OTT client 1 belongs.
  • the OTT server sends a media description to the OTT client 1.
  • the OTT live proxy server sends a media data acquisition request to the OTT server.
  • steps S1013-S1014 For the specific implementation of the steps S1013-S1014, reference may be made to the steps S510-S511 of FIG. 5, and details are not described herein again.
  • 11 is a flow chart of interaction of live media data in an embodiment of the present invention.
  • the OTT live proxy server sends a registration to the OTT server.
  • the OTT live proxy server sends a registration to the OTT server, requesting to register the IP network segment of the metropolitan area network and the IP address of the OTT live proxy server.
  • the OTT server sends a multicast resource allocation indication of channel x to the OTT live proxy server.
  • the OTT live proxy server sends a media description request of the channel x to the OTT server.
  • S1104 The OTT server sends a media description of channel x to the OTT live proxy server.
  • S1105 The OTT live proxy server allocates the multicast resource of channel x, and creates a multicast group Groupx of channel x.
  • the OTT live proxy server sends the multicast resource allocated by the channel x to the OTT server.
  • the OTT live proxy server sends a channel x media data acquisition request to the OTT server.
  • S1108 The OTT server unicasts the media data of the channel x to the OTT live proxy server.
  • steps S1102-S1108 For the specific implementation of the steps S1102-S1108, reference may be made to the steps S502-S506 and the steps S511-S512 of FIG. 5, which are not described herein again.
  • steps S1102-S1108 may be repeatedly performed. That is, the OTT server may instruct the OTT live proxy server to create multicast resources for multiple channels.
  • the OTT client 1 sends a join request of channel n to the OTT server.
  • the OTT client 1 sends a join request for channel n to the OTT server, requesting to join channel n.
  • the OTT server sends a channel join indication of channel n to the OTT live proxy server.
  • the OTT server authenticates the OTT client 1 according to the join request of the channel n. If the OTT client 1 is allowed to join the channel n, and the OTT live proxy server of the metropolitan area network where the OTT client 1 is located has allocated the multicast resource (multicast group Groupnn) to the channel n, the OTT server may send the OTT live proxy server to the OTT live proxy server.
  • the channel join indication notifies the OTT live proxy server that the IP of the OTT client 1 can join the multicast group Groupn.
  • S1111 The OTT live proxy server sends a channel join indication of channel n to the multicast replication point.
  • the OTT live proxy server may send the channel join indication to the multicast copy point to which the OTT client 1 belongs, so that the multicast copy point to which the OTT client 1 belongs can perform the play request of the OTT client 1. Authentication.
  • FIG. 12 is a schematic structural diagram of an OTT live broadcast proxy server 1200 according to an embodiment of the present invention.
  • the OTT live broadcast proxy server 1200 may include: an obtaining unit 1201, a multicast resource allocating unit 1202, and a multicast unit 1203. among them,
  • the multicast resource allocating unit 1202 is configured to allocate a multicast resource to the designated channel according to the multicast resource allocation indication of the specified channel and the media description of the designated channel.
  • the multicast resource allocation indication is used to notify the OTT live proxy server to allocate a multicast resource for the designated channel, where the media description of the designated channel includes at least one resolution of the specified channel and the media of the at least one resolution.
  • a Uniform Resort Locator (URL) corresponding to the data, the multicast resource includes a multicast group corresponding to the designated channel or a multicast group corresponding to the designated channel, and a port port corresponding to the at least one resolution.
  • the obtaining unit 1201 is configured to obtain the media data corresponding to the at least one resolution from the OTT server to which the specified channel belongs in a unicast manner according to the media description of the specified channel;
  • the multicast unit 1203 is configured to convert the media data corresponding to the at least one resolution into multicast media data, and multicast the multicast media data to a multicast replication point that has joined the multicast group.
  • the OTT live proxy server 1200 allocates the multicast resource of the channel according to the channel allocation indication of the OTT server, and obtains the media data of the channel from the OTT server, and then multicasts the media data of the channel to the multicast corresponding to the channel.
  • the multicast replication point in the multicast group can transmit the media data of the channel to the OTT client that joins the channel, which can avoid a large number of repeated live streams from crossing the backbone network, thereby greatly reducing the repetition between the OTT server and the metropolitan area network.
  • the transmitted packets reduce the bandwidth occupied by the live media data on the bearer network.
  • the OTT live broadcast proxy server may further include a receiving unit, configured to receive the multicast resource allocation indication.
  • the multicast resource allocation indication is sent by the OTT server of the OTT live proxy server, or the group
  • the broadcast resource allocation indication is a multicast replication point of the metropolitan area network where the OTT live proxy server is located.
  • FIG. 13 is another schematic structural diagram of an OTT live broadcast proxy server 1200 according to an embodiment of the present invention.
  • the obtaining unit 1201 is further configured to obtain, by the OTT server, a media description of the specified channel.
  • the media description of the designated channel is pre-stored in the OTT live proxy server.
  • the OTT service provider may pre-store the relevant media descriptions of some or all of the channels on the OTT proxy server to reduce the information interaction caused by the media description request.
  • the OTT live proxy server 1200 may further include: a forwarding unit 1204, configured to receive a channel join indication sent by the OTT server, and send the channel join indication to the OTT live proxy server.
  • a forwarding unit 1204 configured to receive a channel join indication sent by the OTT server, and send the channel join indication to the OTT live proxy server.
  • the multicast replication point of the metropolitan area network so that the multicast replication point adds the OTT client to the list of authorized users of the designated channel, wherein the channel join indication is used to notify the OTT client to join the designated channel.
  • the OTT live proxy server 1200 may further include: a registration unit 1205, configured to register, with the OTT server, an Internet Protocol IP network segment of the metropolitan area network where the OTT live proxy server is located, and the OTT live broadcast The IP address of the proxy server.
  • a registration unit 1205 configured to register, with the OTT server, an Internet Protocol IP network segment of the metropolitan area network where the OTT live proxy server is located, and the OTT live broadcast The IP address of the proxy server.
  • the multicast resource allocating unit 1202 is further configured to feed back the allocated multicast resource to the OTT server, so that the OTT server sends the multicast resource to the OTT client, so that the OTT client The end can join the multicast group.
  • the multicast resource allocating unit 1202 is further configured to send the correspondence between the designated channel and the multicast group of the designated channel to the group in the metropolitan area network where the OTT live proxy server is located.
  • the multicast point is broadcasted, so that the multicast replication point determines the multicast group corresponding to the designated channel according to the request sent by the OTT client to join the designated channel.
  • the multicast resource allocating unit 1202 is further configured to send the multicast resource to the OTT client according to the request that the OTT client sends the specified channel, so that the OTT client requests the multicast replication point. Specify the media data for the channel.
  • the OTT live broadcast proxy server 1200 may further include: a multicast group management unit 1206, configured to:
  • the multicast forwarding entry of the broadcast group deletes the egress port corresponding to the multicast replication point.
  • the multicast group management unit 1206 is further configured to: when the number of outgoing ports in the multicast forwarding entry of the multicast group is zero, delete the multicast forwarding entry of the multicast group, and disconnect the OTT server from the OTT server. Download a link to the media data for that channel.
  • the OTT live proxy server 1200 can also perform the method of FIG. 2 and implement the functions of the OTT live proxy server in the embodiment shown in FIG. 5 to FIG.
  • FIG. 14 is a schematic structural diagram of an OTT server 1400 according to an embodiment of the present invention.
  • the OTT server 1400 may include a multicast resource allocation indication unit 1401, a media description management unit 1402, and a media resource management unit 1403.
  • the multicast resource allocation indication unit 1401 is configured to send a multicast resource allocation indication to the OTT live broadcast proxy server registered in the OTT server 1400.
  • the multicast resource allocation indication is used to notify the OTT live proxy server to allocate multicast resources to the designated channel.
  • the media description management unit 1402 is configured to send, according to the request for acquiring the media description of the specified channel, the media description of the specified channel to the OTT live proxy server.
  • the media description of the designated channel includes at least one resolution of the specified channel and a URL corresponding to the media data of the at least one resolution.
  • the media resource management unit 1403 is configured to send the media data of the at least one resolution of the specified channel to the OTT live broadcast proxy server in a unicast manner according to the media data acquisition request of the OTT live broadcast proxy server for the specified channel.
  • the OTT server 1400 instructs the OTT live proxy server to establish a multicast resource of the multicast group allocation channel, and sends the media data of the channel to the OTT live proxy server in a unicast manner, so that the OTT live proxy server will media the channel.
  • the data is sent to the OTT client that joins the multicast group through the multicast replication point. This prevents large number of duplicate live streams from passing through the backbone network. This greatly reduces the number of repeated transmissions between the OTT server and the metropolitan area network. The bandwidth occupied by the bearer network.
  • FIG. 15 is another schematic structural diagram of an OTT server 1400 according to an embodiment of the present invention.
  • the OTT server 1400 may further include: a registration unit 1404, configured to record, according to the registration request sent by the OTT live proxy server, an Internet Protocol IP network of the metropolitan area network where the OTT live proxy server is located.
  • the registration request carries the IP network segment of the metropolitan area network where the OTT live proxy server is located and the IP address of the OTT live proxy server.
  • the OTT server 1400 may further include: an authentication unit 1405, configured to determine whether to allow the OTT client according to the request that the OTT client in the metropolitan area network where the OTT is located joins the designated channel. The end joins the specified channel.
  • the multicast resource allocation indication unit 1401 is specifically configured to: when the authentication unit 1405 determines that the OTT client is allowed to join the designated channel, and the OTT server does not have the multicast resource of the designated channel sent by the OTT live proxy server. The multicast resource allocation indication is sent to the OTT live proxy server.
  • the authenticating unit 1405 is further configured to: after allowing the OTT client to join the designated channel, send a channel joining indication to the OTT live proxy server, where the channel joining indication is used to notify the OTT live agent.
  • the server allows the OTT client to join the designated channel.
  • the authentication unit 1405 is further configured to send, by the OTT live proxy server, the multicast resource allocated for the designated channel to the OTT client, so that the OTT client sends the group to the group.
  • the broadcast copy point requests the media data of the specified channel.
  • the multicast resource includes a multicast group corresponding to the designated channel and a port corresponding to at least one resolution of the designated channel.
  • the OTT server 1400 may further include: a relocation indication unit 1406, configured to indicate the OTT client according to the request that the OTT client joins the designated channel, and the multicast resource of the designated channel.
  • the terminal relocates the join request of the specified channel to the OTT live proxy server.
  • the OTT server 1400 can also perform the method of FIG. 3 and implement the functions of the OTT server in the embodiment shown in FIG. 5-11, and details are not described herein again.
  • FIG. 16 is a schematic structural diagram of a multicast replication point 1600 according to an embodiment of the present invention.
  • the multicast replication point 1600 may include a multicast management unit 1601, a media data acquisition unit 1602, and a media data management unit 1603. among them,
  • the multicast management unit 1601 is configured to request the OTT live broadcast proxy server of the metropolitan area network to join the multicast group allocated by the OTT live proxy server for the designated channel.
  • the media data obtaining unit 1602 is configured to receive media data of the designated channel that is sent by the OTT live proxy server in a multicast manner.
  • the media data management unit 1603 is configured to send the media data of the specified channel to the OTT client in a multicast manner or a unicast manner.
  • the multicast replication point 1600 obtains the media data of the channel from the multicast group established by the OTT live proxy server, and sends the media data of the channel to the OTT client, so that the OTT client does not need to directly obtain the media data of the channel from the OTT server.
  • a large number of repeated live streams can be avoided to traverse the backbone network, thereby greatly reducing the number of repeated transmissions between the OTT server and the metropolitan area network, and reducing the bandwidth occupied by the live media data to the bearer network.
  • the multicast replication point 1600 may further include: a rights management unit 1604, configured to add the OTT client to the legal channel of the designated channel according to the channel joining indication sent by the OTT live proxy server of the metropolitan area network.
  • the channel join indication is used to notify the OTT client to join the designated channel.
  • the multicast management unit 1601 is further configured to: join the OTT client to the multicast forwarding table of the multicast replication point according to the multicast join request or the media data request sent by the OTT client to join the specified channel. And requesting to join the multicast group to the OTT live proxy server; or deleting the OTT client from the multicast forwarding table of the multicast replication point according to the request sent by the OTT client to exit the designated channel.
  • the multicast management unit 1601 is further configured to: when the OTT client of the multicast forwarding table of the multicast replication point is zero, send a multicast exit request to the OTT live proxy server to request to exit the multicast group.
  • the multicast management unit 1601 is further configured to: according to the media data request sent by the OTT client, and the legal user list of the designated channel, authenticate the right of the OTT client to join the designated channel, and After the OTT client authenticates, the OTT live injection proxy server is requested to join the multicast group.
  • multicast replication point 1600 can also perform the method of FIG. 4 and implement the functions of the multicast replication point in the embodiment shown in FIG. 5-11, and details are not described herein again.
  • FIG. 17 is a schematic structural diagram of an OTT live broadcast proxy server 1700 according to an embodiment of the present invention.
  • the OTT Live Agent Server 1700 can include a channel interface 1701, a processor 1702, and a memory 1703.
  • Channel interface 1701, processor 1702, and memory 1703 are interconnected by a bus 1704 system.
  • the bus 1704 can be an ISA bus, a PCI bus, or an EISA bus.
  • the bus can be divided into an address bus, a data bus, a control bus, and the like. For ease of representation, only one double-headed arrow is shown in Figure 17, but it does not mean that there is only one bus or one type of bus.
  • the memory 1703 is configured to store a program.
  • the program can include program code, the program code including computer operating instructions.
  • Memory 1703 can include read only memory and random access memory and provides instructions and data to processor 1702.
  • the memory 1703 may include a high speed RAM memory and may also include a non-volatile memory such as at least one disk memory.
  • the processor 1702 executes the program stored in the memory 1703, and is specifically configured to perform the following operations:
  • the multicast resource Assigning, according to the multicast resource allocation indication sent by the OTT server, the multicast resource according to the multicast resource allocation indication of the specified channel and the media description of the designated channel, where the multicast resource allocation indication is used to notify the OTT broadcast
  • the proxy server allocates a multicast resource to the specified channel, where the media description of the specified channel includes at least one resolution of the specified channel and a URL corresponding to the media data of the at least one resolution, where the multicast resource includes the designated channel a corresponding multicast group or a multicast group corresponding to the specified channel and a port corresponding to the at least one resolution;
  • the OTT server acquires media data corresponding to the at least one resolution
  • the method performed by the OTT live proxy server disclosed in any of the embodiments of FIG. 2 and FIG. 5-11 of the present invention may be applied to the processor 1702 or implemented by the processor 1702.
  • the processor 1702 may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method may be completed by an integrated logic circuit of hardware in the processor 1702 or an instruction in a form of software.
  • the processor 1702 may be a general-purpose processor, including a central processing unit (CPU), a network processor (Network Processor, NP for short, etc.; or a digital signal processor (DSP), an application specific integrated circuit.
  • CPU central processing unit
  • NP Network Processor
  • DSP digital signal processor
  • ASIC application-the-shelf programmable gate array
  • FPGA off-the-shelf programmable gate array
  • the methods, steps, and logical block diagrams disclosed in the embodiments of the present invention may be implemented or carried out.
  • the general purpose processor may be a microprocessor or the processor or any conventional processor or the like.
  • the steps of the method disclosed in the embodiments of the present invention may be directly implemented by the hardware decoding processor, or may be performed by a combination of hardware and software modules in the decoding processor.
  • the software module can be located in a conventional storage medium such as random access memory, flash memory, read only memory, programmable read only memory or electrically erasable programmable memory, registers, and the like.
  • the storage medium is located in the memory 1703, and the processor 1702 reads the information in the memory 1703 and completes the steps of the above method in combination with its hardware.
  • the OTT live proxy server allocates the multicast resource of the channel according to the channel allocation indication of the OTT server, and obtains the media data of the channel from the OTT server, and then multicasts the media data of the channel to the multicast group corresponding to the channel. Therefore, the multicast replication point in the multicast group can transmit the media data of the channel to the OTT client that joins the channel, which can avoid a large number of repeated live streams from crossing the backbone network, thereby greatly reducing the repeated transmission between the OTT server and the metropolitan area network.
  • the packet reduces the bandwidth occupied by the live media data on the bearer network.
  • the processor 1702 is further configured to: obtain, by using the channel interface 1701, the media description of the specified channel from the OTT server.
  • the media description of the designated channel is pre-stored in the OTT live proxy server.
  • the OTT service provider may pre-store the relevant media descriptions of some or all of the channels on the OTT proxy server to reduce the information interaction caused by the media description request.
  • the processor 1702 is further configured to: receive the multicast resource allocation indication by using the channel interface 1701.
  • the multicast resource allocation indication is sent by the OTT server of the OTT live proxy server, or the multicast resource allocation indication is a multicast replication point of the metropolitan area network where the OTT live proxy server is located.
  • the processor 1702 is further configured to: receive, by using the channel interface 1701, a channel join indication sent by the OTT server, and send the channel join indication to a multicast replication point of the metropolitan area network where the OTT live proxy server is located, to And causing the multicast replication point to add the OTT client to the legal user list of the designated channel, wherein the channel join indication is used to notify the OTT client to join the designated channel.
  • the processor 1702 is further configured to: register, by the channel interface 1701, the IP network segment of the metropolitan area network where the OTT live proxy server is located and the IP address of the OTT live proxy server to the OTT server.
  • the processor 1702 is further configured to: feed back, by the channel interface 1701, the allocated multicast resource to the OTT server, so that the OTT server sends the multicast resource to the OTT client, so that The OTT client can join the multicast group.
  • the processor 1702 is further configured to: send, by using the channel interface 1701, the correspondence between the designated channel and the multicast group of the designated channel to the metropolitan area network where the OTT live proxy server is located.
  • the multicast replication point so that the multicast replication point determines the multicast group corresponding to the designated channel according to the request sent by the OTT client to join the designated channel.
  • the processor 1702 is further configured to send the multicast resource to the OTT client by using the channel interface 1701 according to the request that the OTT client sends the specified channel, so that the OTT client requests the multicast replication point.
  • the media data of the specified channel is further configured to send the multicast resource to the OTT client by using the channel interface 1701 according to the request that the OTT client sends the specified channel, so that the OTT client requests the multicast replication point.
  • the processor 1702 is further configured to: join the multicast replication point to the multicast group according to the multicast join request of the multicast replication point, and perform multicast forwarding in the multicast group.
  • the publication item adds the egress port corresponding to the multicast replication point.
  • the processor 1702 is further configured to: delete, according to the multicast exit request of the multicast replication point, the multicast replication point from the multicast group, and in the multicast group The multicast forwarding entry deletes the egress port corresponding to the multicast replication point.
  • the processor 1702 is further configured to: when the number of outgoing ports in the multicast forwarding entry of the multicast group is zero, delete the multicast forwarding entry of the multicast group, and disconnect the download from the OTT server. A link to the media data for the specified channel.
  • the OTT live broadcast proxy server 1700 can also perform the method of FIG. 2 and implement the functions of the OTT live broadcast proxy server in the embodiment shown in FIG. 5 to FIG.
  • FIG. 18 is a schematic structural diagram of an OTT server 1800 according to an embodiment of the present invention.
  • the OTT server 1800 can include a channel interface 1801, a processor 1802, and a memory 1803.
  • Bus 1804 It can be an ISA bus, a PCI bus or an EISA bus.
  • the bus can be divided into an address bus, a data bus, a control bus, and the like. For ease of representation, only one double-headed arrow is shown in Figure 18, but it does not mean that there is only one bus or one type of bus.
  • the memory 1803 is configured to store a program.
  • the program can include program code, the program code including computer operating instructions.
  • the memory 1803 can include read only memory and random access memory and provides instructions and data to the processor 1802.
  • the memory 1803 may include a high speed RAM memory and may also include a non-volatile memory such as at least one disk memory.
  • the processor 1802 executes the program stored in the memory 1803, and is specifically configured to perform the following operations:
  • the media description of the specified channel includes the designated channel At least one resolution and a URL corresponding to the media data of the at least one resolution
  • the media data of the at least one resolution of the specified channel is sent to the OTT live proxy server in a unicast manner through the channel interface 1801.
  • the method performed by the OTT server disclosed in any of the embodiments of FIG. 3 and FIG. 5-11 of the present invention may be applied to the processor 1802 or implemented by the processor 1802.
  • the processor 1802 may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method may be completed by an integrated logic circuit of hardware in the processor 1802 or an instruction in a form of software.
  • the processor 1802 may be a general-purpose processor, including a central processing unit (CPU), a network processor (NP Processor, etc.), or a digital signal processor (DSP), an application specific integrated circuit. (ASIC), off-the-shelf programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware component.
  • the general purpose processor may be a microprocessor or the processor or any conventional processor or the like.
  • the steps of the method disclosed in the embodiments of the present invention may be directly implemented by the hardware decoding processor, or may be performed by a combination of hardware and software modules in the decoding processor.
  • the software module can be located in a conventional storage medium such as random access memory, flash memory, read only memory, programmable read only memory or electrically erasable programmable memory, registers, and the like.
  • the storage medium Located in the memory 1803, the processor 1802 reads the information in the memory 1803 and completes the steps of the above method in combination with its hardware.
  • the OTT server 1800 instructs the OTT live proxy server to establish a multicast resource of the multicast group allocation channel, and sends the media data of the channel to the OTT live proxy server in a unicast manner, so that the OTT live proxy server will media the channel.
  • the data is sent to the OTT client that joins the multicast group through the multicast replication point. This prevents large number of duplicate live streams from passing through the backbone network. This greatly reduces the number of repeated transmissions between the OTT server and the metropolitan area network. The bandwidth occupied by the bearer network.
  • the processor 1802 is further configured to: record, according to the registration request sent by the OTT live proxy server, an Internet Protocol IP network segment of the metropolitan area network where the OTT live proxy server is located, and an IP address of the OTT live proxy server, where The registration request carries the IP network segment of the metropolitan area network where the OTT live proxy server is located and the IP address of the OTT live proxy server.
  • the processor 1802 is further configured to: determine, according to the request that the OTT client in the metropolitan area network where the OTT is located to join the designated channel, whether to allow the OTT client to join the designated channel. Further, in the process of sending the multicast resource allocation indication to the OTT live proxy server registered in the OTT server, the processor 1802 is specifically configured to: when the processor 1802 determines that the OTT client is allowed to join the designated channel, And when the multicast resource of the specified channel sent by the OTT live proxy server does not exist on the OTT server, the multicast resource allocation indication is sent to the OTT live proxy server.
  • the processor 1802 is further configured to: after allowing the OTT client to join the designated channel, send a channel join indication to the OTT live proxy server, where the channel join indication is used to notify the OTT live proxy server to allow the OTT client The end joins the specified channel.
  • the processor 1802 is further configured to: send, by the OTT live proxy server, the multicast resource allocated for the specified channel to the OTT client, so that the OTT client requests the multicast replication point.
  • the processor 1802 is further configured to: according to the request that the OTT client joins the designated channel, and the multicast resource of the designated channel, instruct the OTT client to join the designated channel Request to relocate to the OTT live proxy server.
  • the OTT server 1800 can also perform the method of FIG. 3 and implement the functions of the OTT server in the embodiment shown in FIG. 5-11, and details are not described herein again.
  • FIG. 19 is a schematic structural diagram of a multicast replication point 1900 according to an embodiment of the present invention.
  • Multicast replication point 1900 can include Channel interface 1901, processor 1902, and memory 1903.
  • Channel interface 1901, processor 1902, and memory 1903 are interconnected by a bus 1904 system.
  • the bus 1904 can be an ISA bus, a PCI bus, or an EISA bus.
  • the bus can be divided into an address bus, a data bus, a control bus, and the like. For ease of representation, only one double-headed arrow is shown in Figure 19, but it does not mean that there is only one bus or one type of bus.
  • the memory 1903 is configured to store a program.
  • the program can include program code, the program code including computer operating instructions.
  • Memory 1903 can include read only memory and random access memory and provides instructions and data to processor 1902.
  • the memory 1903 may include a high speed RAM memory and may also include a non-volatile memory such as at least one disk memory.
  • the processor 1902 executes the program stored in the memory 1903, and is specifically configured to perform the following operations:
  • the channel interface 1901 requests the OTT live proxy server of the metropolitan area network to join the multicast group allocated by the OTT live proxy server for the designated channel;
  • the media data of the specified channel is sent to the OTT client in a multicast manner or a unicast manner through the channel interface 1901.
  • Processor 1902 may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method may be completed by an integrated logic circuit of hardware in the processor 1902 or an instruction in a form of software.
  • the processor 1902 may be a general-purpose processor, including a central processing unit (CPU), a network processor (NP Processor, etc.), or a digital signal processor (DSP), an application specific integrated circuit. (ASIC), off-the-shelf programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware component.
  • the general purpose processor may be a microprocessor or the processor or any conventional processor or the like.
  • the steps of the method disclosed in the embodiments of the present invention may be directly implemented by the hardware decoding processor, or may be performed by a combination of hardware and software modules in the decoding processor.
  • the software module can be located in a conventional storage medium such as random access memory, flash memory, read only memory, programmable read only memory or electrically erasable programmable memory, registers, and the like.
  • the storage medium is located in the memory 1903, and the processor 1902 reads the information in the memory 1903 and completes the steps of the above method in combination with its hardware.
  • the multicast replication point 1900 obtains a channel from a multicast group established by the OTT live proxy server.
  • the media data is sent to the OTT client, so that the OTT client does not need to directly obtain the media data of the channel from the OTT server, thereby avoiding a large number of repeated live streams traversing the backbone network, thereby greatly reducing the repetition between the OTT server and the metropolitan area network.
  • the transmitted packets reduce the bandwidth occupied by the live media data on the bearer network.
  • the processor 1902 is further configured to: join the OTT client to the group of the multicast replication point according to the multicast join request or the media data request sent by the OTT client to join the specified channel.
  • the forwarding table is broadcasted, and the OTT live proxy server is requested to join the multicast group.
  • the processor 1902 is further configured to: remove the OTT client from the multicast forwarding table of the multicast replication point according to the request for the OTT client to exit the specified channel.
  • the processor 1902 is further configured to: add the OTT client to the legal user list of the designated channel according to the channel joining indication sent by the OTT live proxy server, where the channel joining indication is used to notify that the OTT is allowed.
  • the client joins the specified channel.
  • the processor 1902 is further configured to: receive, by using the channel interface 1901, the OTT live proxy server to send. Channel join instructions.
  • the processor 1902 is further configured to: when the OTT client of the multicast forwarding table of the multicast replication point is zero, send a multicast exit request to the OTT live proxy server, requesting to quit the multicast group.
  • the processor 1902 is further configured to: according to the media data request sent by the OTT client, and the legal user list of the designated channel, authenticate the right of the OTT client to join the designated channel, and perform authentication on the OTT client. After the authentication, the OTT live injection proxy server is requested to join the multicast group.
  • the multicast replication point 1900 can also perform the method of FIG. 4 and implement the function of the multicast replication point in the embodiment shown in FIG. 5-11, which is not described herein again.
  • the OTT system may include: an OTT server, an OTT live proxy server, a multicast replication point, and an OTT client.
  • the OTT server may be the OTT server in the embodiment shown in FIG. 14, FIG. 15, or the OTT
  • the OTT live proxy server may be the OTT live proxy server in the embodiment shown in FIG. 12, FIG. 13, or FIG.
  • the point may be a multicast copy point in the embodiment shown in Figure 16 or Figure 19.
  • the OTT client can be an OTT client with unicast or multicast receiving capabilities.
  • the disclosed systems, devices, and methods may be implemented in other manners.
  • the device embodiments described above are merely illustrative.
  • the division of the unit is only a logical function division.
  • there may be another division manner for example, multiple units or components may be combined or Can be integrated into another system, or some features can be ignored or not executed.
  • the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, and may be in an electrical, mechanical or other form.
  • the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of the embodiment.
  • each functional unit in each embodiment of the present invention may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
  • the functions may be stored in a computer readable storage medium if implemented in the form of a software functional unit and sold or used as a standalone product.
  • 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. .

Abstract

提供了一种直播媒体数据的方法、设备和***。设备中的OTT直播代理服务器包括：组播资源分配单元，用于根据指定频道的组播资源分配指示及该指定频道的媒体描述为该指定频道分配组播资源，其中，该组播资源分配指示用于通知该OTT直播代理服务器为该指定频道分配组播资源；获取单元，用于根据该指定频道的媒体描述通过单播方式从该指定频道所属的OTT服务器获取该至少一种分辨率对应的媒体数据；组播单元，用于将该至少一种分辨率对应的媒体数据转换为组播媒体数据，并将该组播媒体数据组播发送给该组播组。

Description

直播媒体数据的方法、设备和***
本申请要求于2015年5月12日提交中国专利局、申请号为201510240782.0、发明名称为“直播媒体数据的方法、设备和***”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本发明实施例涉及计算机网络领域，并且更具体地，涉及直播媒体数据的方法、设备和***。
背景技术
在线服务(over the top，OTT)视频网站上的视频，按照观看形式，分为点播(video on demand，VOD)和直播(Video on Live，VOL)两种。
点播：观看存储在视频服务器上片源。因为片源已经全部制作完成，所以在观看时可以随时停止、快进快退、前后拖动。
直播：播放实时视频，一般是各个电视频道的内容或者体育赛事、音乐会的实况转播。不能前后拖动播放进度。观看同一直播媒体数据的观众，看到的内容是完全相同的。
OTT服务器属于OTT业务提供商(提供OTT视频网站服务的公司)所有，可以放置在运营商某个城市的数据中心内，也可以放置在OTT业务提供商自己的机房内。OTT服务器可以给OTT用户提供注册、登陆、呈现节目界面、流媒体发送等服务。OTT服务器具体部署时一般由多台物理服务器协同对外提供功能。
OTT客户端指OTT用户用于观看OTT视频的终端。常见的有三种形式：台式电脑或者笔记本电脑上的桌面客户端、手机或者平板电脑上的移动应用、OTT机顶盒。
当前OTT视频网站传输视频大多是基于超文本传输协议(HyperText Transfer Protocol，HTTP)的单播，也有一部分是基于用户数据报协议(User Datagram Protocol，UDP)的单播，这意味着观看直播媒体数据的OTT用户，在网络中传输了大量重复的数据报文。直播媒体数据的大量重复的报文严重挤占了承载网的带宽。
发明内容
本发明实施例提供一种直播媒体数据的方法、设备和***，能够避免大量重复的直播流穿越骨干网，减少直播媒体数据对承载网的带宽占用。
第一方面，提供了一种OTT直播代理服务器，包括：组播资源分配单元，用于根 据指定频道的组播资源分配指示及该指定频道的媒体描述为该指定频道分配组播资源，其中，该组播资源分配指示用于通知该OTT直播代理服务器为该指定频道分配组播资源，该指定频道的媒体描述包括该指定频道的至少一种分辨率及该至少一种分辨率的媒体数据所对应的URL，该组播资源包括该指定频道对应的组播组或该指定频道对应的组播组及该至少一种分辨率对应的端口；获取单元，用于根据该指定频道的媒体描述通过单播方式从该指定频道所属的OTT服务器获取该至少一种分辨率对应的媒体数据；组播单元，用于将该至少一种分辨率对应的媒体数据转换为组播媒体数据，并将该组播媒体数据组播发送给该组播组。
结合第一方面，在第一种可能的实现方式中，该获取单元还用于从该OTT服务器获取该指定频道的媒体描述；或者，该指定频道的媒体描述是预先存储在该OTT直播代理服务器中的。
结合第一方面或第一方面的第一种可能的实现方式，在第二种可能的实现方式中，具体实现为：该组播资源分配指示是由该OTT服务器发送的；或者，该组播资源分配指示是由该OTT直播代理服务器所在的城域网的组播复制点发送的。
结合第一方面或第一方面的第一种可能的实现方式或第一方面的第二种可能的实现方式，在第三种可能的实现方式中，还包括：转发单元，用于接收该OTT服务器发送的频道加入指示，并将该频道加入指示发送给该OTT直播代理服务器所在的城域网的组播复制点，以使该组播复制点将OTT客户端加入到该指定频道的合法用户列表中，其中，该频道加入指示用于通知允许该OTT客户端加入该指定频道。
结合第一方面或第一方面的第一种可能的实现方式至第一方面的第三种可能的实现方式中任一种可能的实现方式，在第四种可能的实现方式中，还包括：注册单元，用于向该OTT服务器注册该OTT直播代理服务器所在的城域网的互联网协议IP网段及该OTT直播代理服务器的IP地址。
结合第一方面或第一方面的第一种可能的实现方式至第一方面的第四种可能的实现方式中任一种可能的实现方式，在第五种可能的实现方式中，该组播资源分配单元还用于将该分配的组播资源反馈给该OTT服务器，以便该OTT服务器将该组播资源发送给该OTT客户端，使得该OTT客户端能够加入该组播组。
结合第一方面或第一方面的第一种可能的实现方式至第一方面的第五种可能的实现方式中任一种可能的实现方式，在第六种可能的实现方式中，该组播资源分配单元还用于将该指定频道与该指定频道的组播组之间的对应关系发送给该OTT直播代理服务 器所在城域网内的组播复制点，以便该组播复制点根据该OTT客户端发送的加入该指定频道的请求，确定该指定频道对应的组播组。
结合第一方面的第六种可能的实现方式，在第七种可能的实现方式中，该组播资源分配单元还用于根据该OTT客户端发送的加入该指定频道的请求，将该组播资源发送给该OTT客户端，以便该OTT客户端向组播复制点请求该指定频道的媒体数据。
结合第一方面或第一方面的第一种可能的实现方式至第一方面的第七种可能的实现方式中任一种可能的实现方式，在第八种可能的实现方式中，还包括：组播组管理单元，用于：根据该组播复制点的组播加入请求，将该组播复制点加入该组播组，并在该组播组的组播转发表项添加该组播复制点对应的出端口；或者，根据该组播复制点的组播退出请求，将该组播复制点从该组播组中删除，并在该组播组的组播转发表项删除该组播复制点对应的出端口。
结合第一方面的第八种可能的实现方式，该组播资源分配单元还用于当该组播组的组播转发表项中出端口数为零时，删除该组播组的组播转发表项，并断开从该OTT服务器下载该指定频道的媒体数据的链接。
第二方面，提供了一种OTT服务器，包括：组播资源分配指示单元，用于向在该OTT服务器中注册的OTT直播代理服务器发送组播资源分配指示，该组播资源分配指示用于通知该OTT直播代理服务器对指定频道分配组播资源；媒体描述管理单元，用于根据该OTT直播代理服务器发送的获取该指定频道的媒体描述的请求，将该指定频道的媒体描述发送给该OTT直播代理服务器，其中，该指定频道的媒体描述包括该指定频道的至少一种分辨率及该至少一种分辨率的媒体数据所对应的URL；媒体资源管理单元，用于根据该OTT直播代理服务器对该指定频道的媒体数据获取请求，将该指定频道的至少一种分辨率的媒体数据以单播方式发送给该OTT直播代理服务器。
结合第二方面，在第一种可能的实现方式中，还包括：注册单元，用于根据该OTT直播代理服务器发送的注册请求，记录该OTT直播代理服务器所在的城域网的互联网协议IP网段及该OTT直播代理服务器的IP地址，其中，该注册请求携带该OTT直播代理服务器所在的城域网的IP网段及该OTT直播代理服务器的IP地址。
结合第二方面或第二方面的第一种可能的实现方式，在第二种可能的实现方式中，还包括：鉴权单元，用于根据该OTT所在的城域网中的OTT客户端加入该指定频道的请求，确定是否允许该OTT客户端加入该指定频道；该组播资源分配指示单元具体用于当该鉴权单元确定允许该OTT客户端加入该指定频道后，且该OTT服务器上不存在 该OTT直播代理服务器发送的该指定频道的组播资源时，向该OTT直播代理服务器发送该组播资源分配指示。
结合第二方面的第二种可能的实现方式，在第三种可能的实现方式中，该鉴权单元还用于在允许该OTT客户端加入该指定频道后，向该OTT直播代理服务器发送频道加入指示，该频道加入指示用于通知该OTT直播代理服务器允许该OTT客户端加入该指定频道。
结合第二方面的第二种可能的实现方式，在第四种可能的实现方式中，该鉴权单元还用于将该OTT直播代理服务器反馈的为该指定频道分配的组播资源发送给该OTT客户端，以便该OTT客户端向组播复制点请求该指定频道的媒体数据，其中，该组播资源包括该指定频道对应的组播组或该指定频道对应的组播组及该指定频道的至少一种分辨率对应的端口。
结合第二方面的第二种可能的实现方式，在第五种可能的实现方式中，还包括：重定位指示单元，用于根据该OTT客户端加入该指定频道的请求，以及该指定频道的组播资源，指示该OTT客户端将该指定频道的加入请求重定位到该OTT直播代理服务器上。
第三方面，提供了一种组播复制点，包括：组播管理单元，用于向所在城域网的OTT直播代理服务器请求加入该OTT直播代理服务器为指定频道分配的组播组；媒体数据获取单元，用于接收该OTT直播代理服务器以组播方式发送的该指定频道的媒体数据；媒体数据管理单元，用于将该指定频道的媒体数据以组播方式或单播方式发送给该OTT客户端。
结合第三方面，在第一种可能的实现方式中，还包括：权限管理单元，用于根据所在城域网的OTT直播代理服务器发送的频道加入指示，将该OTT客户端加入到该指定频道的合法用户列表中，其中，该频道加入指示用于通知该组播复制点允许该OTT客户端加入该指定频道。
结合第三方面或第三方面的第一种可能的实现方式，在第二种可能的实现方式中，该组播管理单元还用于：根据该OTT客户端发送的加入该指定频道的组播加入请求或媒体数据请求，将该OTT客户端加入该组播复制点的组播转发表，并向该OTT直播代理服务器请求加入该组播组；或者，根据该OTT客户端发送的退出该指定频道的请求，将该OTT客户端从该组播复制点的组播转发表中删除。
第四方面，提供了一种直播媒体数据的方法，包括：根据指定频道的组播资源分配 指示及该指定频道的媒体描述为该指定频道分配组播资源，其中，该组播资源分配指示用于通知该OTT直播代理服务器为该指定频道分配组播资源，该指定频道的媒体描述包括该指定频道的至少一种分辨率及该至少一种分辨率的媒体数据所对应的URL，该组播资源包括该指定频道对应的组播组或该指定频道对应的组播组及该至少一种分辨率对应的端口；根据该指定频道的媒体描述通过单播方式从该指定频道所属的OTT服务器获取该至少一种分辨率对应的媒体数据；将该至少一种分辨率对应的媒体数据转换为组播媒体数据，并将该组播媒体数据组播发送给该组播组。
结合第四方面，在第一种可能的实现方式中，在根据指定频道的组播资源分配指示及该指定频道的媒体描述为该指定频道分配组播资源之前，该方法还包括从该OTT服务器获取该指定频道的媒体描述；或者，该指定频道的媒体描述是预先存储在该OTT直播代理服务器中的。
结合第四方面或第四方面的第一种可能的实现方式，在第二种可能的实现方式中，在根据指定频道的组播资源分配指示及该指定频道的媒体描述为该指定频道分配组播资源之前，该方法还包括：接收该指定频道的组播资源分配指示；其中，该组播资源分配指示是由该OTT服务器发送的，或者，该组播资源分配指示是由该OTT直播代理服务器所在的城域网的组播复制点发送的。
结合第四方面或第四方面的第一种可能的实现方式或第四方面的第二种可能的实现方式，在第三种可能的实现方式中，还包括：接收该OTT服务器发送的频道加入指示，并将该频道加入指示发送给该OTT直播代理服务器所在的城域网的组播复制点，以使该组播复制点将OTT客户端加入到该指定频道的合法用户列表中，其中，该频道加入指示用于通知允许该OTT客户端加入该指定频道。
结合第四方面或第四方面的第一种可能的实现方式至第四方面的第三种可能的实现方式中任一种可能的实现方式，在第四种可能的实现方式中，还包括：向该OTT服务器注册该OTT直播代理服务器所在的城域网的互联网协议IP网段及该OTT直播代理服务器的IP地址。
结合第四方面或第四方面的第一种可能的实现方式至第四方面的第四种可能的实现方式中任一种可能的实现方式，在第五种可能的实现方式中，还包括：将该分配的组播资源反馈给该OTT服务器，以便该OTT服务器将该组播资源发送给该OTT客户端，使得该OTT客户端能够加入该组播组。
结合第四方面或第四方面的第一种可能的实现方式至第四方面的第五种可能的实 现方式中任一种可能的实现方式，在第六种可能的实现方式中，还包括：将该指定频道与该指定频道的组播组之间的对应关系发送给该OTT直播代理服务器所在城域网内的组播复制点，以便该组播复制点根据OTT客户端发送的加入该指定频道的请求，确定该指定频道对应的组播组。
结合第四方面的第六种可能的实现方式，在第七种可能的实现方式中，还包括：根据OTT客户端发送的加入该指定频道的请求，将该组播资源发送给该OTT客户端，以便该OTT客户端向组播复制点请求该指定频道的媒体数据。
结合第四方面或第四方面的第一种可能的实现方式至第四方面的第七种可能的实现方式中任一种可能的实现方式，在第八种可能的实现方式中，还包括：根据该组播复制点的组播加入请求，将该组播复制点加入该组播组，并在该组播组的组播转发表项添加该组播复制点对应的出端口；或者，根据该组播复制点的组播退出请求，将该组播复制点从该组播组中删除，并在该组播组的组播转发表项删除该组播复制点对应的出端口。
结合第四方面的第一种可能的实现方式，还包括：当该组播组的组播转发表项中出端口数为零时，删除该组播组的组播转发表项，并断开从该OTT服务器下载该指定频道的媒体数据的链接。
第五方面，提供了一种直播媒体数据的方法，包括：OTT服务器向在该OTT服务器中注册的OTT直播代理服务器发送组播资源分配指示，该组播资源分配指示用于通知该OTT直播代理服务器对指定频道分配组播资源；该OTT服务器根据该OTT直播代理服务器发送的获取该指定频道的媒体描述的请求，将该指定频道的媒体描述发送给该OTT直播代理服务器，其中，该指定频道的媒体描述包括该指定频道的至少一种分辨率及该至少一种分辨率的媒体数据所对应的URL；该OTT服务器根据该OTT直播代理服务器对该指定频道的媒体数据获取请求，将该指定频道的至少一种分辨率的媒体数据以单播方式发送给该OTT直播代理服务器。
结合第五方面，在第一种可能的实现方式中，还包括：该OTT服务器根据该OTT直播代理服务器发送的注册请求，记录该OTT直播代理服务器所在的城域网的互联网协议IP网段及该OTT直播代理服务器的IP地址，其中，该注册请求携带该OTT直播代理服务器所在的城域网的IP网段及该OTT直播代理服务器的IP地址。
结合第五方面或第五方面的第一种可能的实现方式，在第二种可能的实现方式中，还包括：该OTT服务器根据该OTT所在的城域网中的OTT客户端加入该指定频道的 请求，确定是否允许该OTT客户端加入该指定频道；该OTT服务器向在该OTT服务器中注册的OTT直播代理服务器发送组播资源分配指示包括：当该OTT服务器确定允许该OTT客户端加入该指定频道后，且该OTT服务器上不存在该OTT直播代理服务器发送的该指定频道的组播资源时，该OTT服务器向该OTT直播代理服务器发送该组播资源分配指示。
结合第五方面的第二种可能的实现方式，在第三种可能的实现方式中，还包括：该OTT服务器在允许该OTT客户端加入该指定频道后，向该OTT直播代理服务器发送频道加入指示，该频道加入指示用于通知该OTT直播代理服务器允许该OTT客户端加入该指定频道。
结合第五方面的第二种可能的实现方式，在第四种可能的实现方式中，还包括：该OTT服务器将该OTT直播代理服务器反馈的为该指定频道分配的组播资源发送给该OTT客户端，以便该OTT客户端向组播复制点请求该指定频道的媒体数据，其中，该组播资源包括该指定频道对应的组播组或该指定频道对应的组播组及该指定频道的至少一种分辨率对应的端口。
结合第五方面的第二种可能的实现方式，在第五种可能的实现方式中，还包括：该OTT服务器根据该OTT客户端加入该指定频道的请求，以及该指定频道的组播资源，指示该OTT客户端将该指定频道的加入请求重定位到该OTT直播代理服务器上。
第六方面，提供了一种直播媒体数据的方法，包括：向所在城域网的OTT直播代理服务器请求加入该OTT直播代理服务器为指定频道分配的组播组；接收该OTT直播代理服务器以组播方式发送的该指定频道的媒体数据；将该指定频道的媒体数据以组播方式或单播方式发送给该OTT客户端。
结合第六方面，在第一种可能的实现方式中，还包括：根据该OTT直播代理服务器发送的频道加入指示，将OTT客户端加入到该指定频道的合法用户列表中，其中，该频道加入指示用于通知允许该OTT客户端加入该指定频道。
结合第六方面或第六方面的第一种可能的实现方式，在第二种可能的实现方式中，还包括：根据该OTT客户端发送的加入该指定频道的组播加入请求或媒体数据请求，将该OTT客户端加入该组播复制点的组播转发表，并向该OTT直播代理服务器请求加入该组播组；或者，根据该OTT客户端发送的退出该指定频道的请求，将该OTT客户端从该组播复制点的组播转发表中删除。
本发明实施例的直播媒体数据的方法、设备和***，首先由OTT服务器将指定频 道的媒体数据通过单播方式传输到城域网的OTT直播代理服务器，再由OTT直播代理服务器以组播方式将媒体数据发送给组播组，使得组播组内的组播复制点在接收到媒体数据后将媒体数据传输给OTT客户端，能够大大减少OTT服务器到城域网之间重复传输的报文，从而能够避免大量重复的直播流穿越骨干网，减少直播媒体数据对承载网的带宽占用。
附图说明
为了更清楚地说明本发明实施例的技术方案，下面将对实施例或现有技术描述中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本发明的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动的前提下，还可以根据这些附图获得其他的附图。
图1是本发明实施例直播媒体数据的OTT***的网络架构图；
图2是本发明实施例直播媒体数据的方法流程图；
图3是本发明实施例直播媒体数据的另一方法流程图；
图4是本发明实施例直播媒体数据的再一方法流程图；
图5是本发明实施例直播媒体数据的一种交互流程图；
图6是本发明实施例直播媒体数据的另一种交互流程图；
图7是本发明实施例直播媒体数据的再一种交互流程图；
图8是本发明实施例直播媒体数据的再一种交互流程图；
图9是本发明实施例直播媒体数据的再一种交互流程图；
图10是本发明实施例直播媒体数据的再一种交互流程图；
图11是本发明实施例直播媒体数据的再一种交互流程图；
图12是本发明实施例OTT直播代理服务器的结构示意图；
图13是本发明实施例OTT直播代理服务器的另一结构示意图；
图14是本发明实施例OTT服务器的结构示意图；
图15是本发明实施例OTT服务器的另一结构示意图；
图16是本发明实施例组播复制点的结构示意图；
图17是本发明实施例OTT直播代理服务器的再一结构示意图；
图18是本发明实施例OTT服务器的再一结构示意图；
图19是本发明实施例组播复制点的再一结构示意图。
具体实施方式
下面将结合本发明实施例中的附图，对本发明实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例是本发明一部分实施例，而不是全部的实施例。基于本发明中的实施例，本领域普通技术人员在没有作出创造性劳动前提下所获得的所有其他实施例，都属于本发明保护的范围。
为了方便理解本发明实施例，首先在此介绍本发明实施例描述中会引入的几个要素。
组播(Multicast)传输：在发送者和每一接收者之间实现点对多点网络连接。如果一台发送者同时给多个的接收者传输相同的数据，只需复制一份的相同数据包。它提高了数据传送效率，减少了骨干网络出现拥塞的可能性。
Internet组管理协议(Internet Group Management Protocol，IGMP)，是因特网协议家族中的一个组播协议。该协议运行在主机和组播路由器之间，用来在IP主机和与其直接相邻的组播路由器之间建立、维护组播组成员关系。域内组播路由协议根据IGMP维护的这些组播组成员关系信息，运用一定的组播路由算法构造组播分发树进行组播数据包转发。域间组播路由协议在各自治域间发布具有组播能力的路由信息以及组播源信息，以使组播数据在域间进行转发。
图1是本发明实施例直播媒体数据的OTT***的网络架构图。如图1所示，OTT***可包括：OTT服务器、OTT直播代理服务器、组播复制点及OTT客户端。其中，OTT服务器可能位于运营商某个城市的数据中心内，或者是在OTT业务提供商自己的机房内；OTT直播代理服务器、组播复制点以及OTT客户端在同一个城域网内。当用户通过OTT客户端请求观看OTT服务器中某个频道的音频或视频节目时，OTT服务器中的该频道的媒体流，以单播的方式通过骨干网传输到城域网的OTT直播代理服务器，所述OTT直播代理服务器以组播的方式将该频道的媒体流发给组播组，再由组播组中的组播复制点将频道的媒体流以单播或组播的方式发送给OTT客户端。
下面，分别从OTT直播代理服务器、OTT服务器及组播复制点的角度，对图1所示的OTT***的执行方法进行描述。
图2是本发明实施例直播媒体数据的一种方法流程图。图2的方法由OTT直播代理服务器执行。该方法包括：
S201，根据指定频道的组播资源分配指示及该指定频道的媒体描述为该指定频道分配组播资源。
其中，该组播资源分配指示用于通知该OTT直播代理服务器为该指定频道分配组播资源，该指定频道的媒体描述包括该指定频道的至少一种分辨率及该至少一种分辨率的媒体数据所对应的统一资源定位符(Uniform Resoure Locator，URL)，该组播资源包括该指定频道对应的组播组或该指定频道对应的组播组及该至少一种分辨率对应的端口port。
当然，应理解，在步骤S201之前，OTT直播代理服务器还需要接收该组播资源分配指示。其中，该组播资源分配指示是OTT直播代理服务器的OTT服务器发送的，或者，该组播资源分配指示是OTT直播代理服务器所在的城域网的组播复制点。
S202，根据该指定频道的媒体描述通过单播方式从该指定频道所属的OTT服务器获取OTT服务器获取该至少一种分辨率对应的媒体数据。
具体地，OTT直播代理服务器可根据媒体描述中的URL，以单播方式获取该URL对应的媒体数据。
S203，将该至少一种分辨率对应的媒体数据转换为组播媒体数据，并将该组播媒体数据组播发送给该组播组。
本发明实施例中，OTT直播代理服务器根据OTT服务器的频道分配指示分配频道的组播资源，并从OTT服务器获取频道的媒体数据，再将频道的媒体数据组播发送到频道对应的组播组，以便组播组内的组播复制点能够将频道的媒体数据传输给加入频道的OTT客户端，能够避免大量重复的直播流穿越骨干网，从而大大减少OTT服务器到城域网之间重复传输的报文，减少直播媒体数据对承载网的带宽占用。
此外，本发明实施例的方法，OTT客户端从最近的网络设备(组播复制点)获取频道的音频或视频节目，相比于从OTT服务器获取频道的音频或视频节目，能够缩短视频启动延迟，降低丢包率/抖动，从而给用户提供了更好的体验。
可选地，作为一个实施例，在步骤S201之前，该方法还包括：从该OTT服务器获取该指定频道的媒体描述。
可选地，作为另一个实施例，该指定频道的媒体描述是预先存储在该OTT直播代理服务器中的。OTT服务厂商可预先在OTT代理服务器上存储部分或全部频道的相关媒体描述，以减少因媒体描述请求引起的信息交互。
可选地，该方法还包括：接收该OTT服务器发送的频道加入指示，并将该频道加入指示发送给该OTT直播代理服务器所在的城域网的组播复制点，以使该组播复制点将OTT客户端加入到该指定频道的合法用户列表中，其中，该频道加入指示用于通知 允许该OTT客户端加入该指定频道。
可选地，该方法还包括：向该OTT服务器注册该OTT直播代理服务器所在的城域网的互联网协议(Internet Protocol，IP)网段及该OTT直播代理服务器的IP地址。
可选地，作为一个实施例，该方法还包括：将该分配的组播资源反馈给该OTT服务器，以便该OTT服务器将该组播资源发送给该OTT客户端，使得该OTT客户端能够加入该组播组。
可选地，作为另一个实施例，该方法还包括：将该指定频道与该指定频道的组播组之间的对应关系发送给该OTT直播代理服务器所在城域网内的组播复制点，以便该组播复制点根据OTT客户端发送的加入该指定频道的请求，确定该指定频道对应的组播组。
进一步地，该方法还包括：根据OTT客户端发送的加入该指定频道的请求，将该组播资源发送给该OTT客户端，以便该OTT客户端向组播复制点请求该指定频道的媒体数据。
可选地，作为一个实施例，该方法还包括：根据该组播复制点的组播加入请求，将该组播复制点加入该组播组，并在该组播组的组播转发表项添加该组播复制点对应的出端口。
可选地，作为另一个实施例，该方法还包括：根据该组播复制点的组播退出请求，将该组播复制点从该组播组中删除，并在该组播组的组播转发表项删除该组播复制点对应的出端口。
进一步地，该方法还包括：当该组播组的组播转发表项中出端口数为零时，删除该组播组的组播转发表项，并断开从该OTT服务器下载该指定频道的媒体数据的链接。
图3是本发明实施例直播媒体数据的另一方法流程图。图3的方法由OTT直播代理服务器执行。该方法包括：
S301，OTT服务器向在该OTT服务器中注册的OTT直播代理服务器发送组播资源分配指示。
其中，该组播资源分配指示用于通知该OTT直播代理服务器对指定频道分配组播资源。
S302，该OTT服务器根据该OTT直播代理服务器发送的获取该指定频道的媒体描述的请求，将该指定频道的媒体描述发送给该OTT直播代理服务器。
其中，该指定频道的媒体描述包括该指定频道的至少一种分辨率及该至少一种分辨 率的媒体数据所对应的URL。
S303，该OTT服务器根据该OTT直播代理服务器对该指定频道的媒体数据获取请求，将该指定频道的至少一种分辨率的媒体数据以单播方式发送给该OTT直播代理服务器。
本发明实施例中，OTT服务器指示OTT直播代理服务器建立组播组分配频道的组播资源，并以单播方式向OTT直播代理服务器发送频道的媒体数据，使得OTT直播代理服务器将频道的媒体数据经组播复制点发送给加入组播组的OTT客户端，能够避免大量重复的直播流穿越骨干网，从而大大减少OTT服务器到城域网之间重复传输的报文，减少直播媒体数据对承载网的带宽占用。
可选地，该方法还包括：该OTT服务器根据该OTT直播代理服务器发送的注册请求，记录该OTT直播代理服务器所在的城域网的互联网协议IP网段及该OTT直播代理服务器的IP地址，其中，该注册请求携带该OTT直播代理服务器所在的城域网的IP网段及该OTT直播代理服务器的IP地址。
可选地，作为一个实施例，该方法还包括：该OTT服务器根据该OTT所在的城域网中的OTT客户端加入该指定频道的请求，确定是否允许该OTT客户端加入该指定频道。进一步地，该OTT服务器向在该OTT服务器中注册的OTT直播代理服务器发送组播资源分配指示具体实现为：当该OTT服务器确定允许该OTT客户端加入该指定频道后，且该OTT服务器上不存在该OTT直播代理服务器发送的该指定频道的组播资源时，该OTT服务器向该OTT直播代理服务器发送该组播资源分配指示。
可选地，该方法还包括：该OTT服务器在允许该OTT客户端加入该指定频道后，向该OTT直播代理服务器发送频道加入指示，该频道加入指示用于通知该OTT直播代理服务器允许该OTT客户端加入该指定频道。
进一步地，作为一个实施例，该方法还包括：该OTT服务器将该OTT直播代理服务器反馈的为该指定频道分配的组播资源发送给该OTT客户端，以便该OTT客户端向组播复制点请求该指定频道的媒体数据，其中，该组播资源包括该指定频道对应的组播组或该指定频道对应的组播组及该指定频道的至少一种分辨率对应的端口。
或者，进一步地，作为另一个实施例，该方法还包括：该OTT服务器根据该OTT客户端加入该指定频道的请求，以及该指定频道的组播资源，指示该OTT客户端将该指定频道的加入请求重定位到该OTT直播代理服务器上。
图4是本发明实施例直播媒体数据的再一方法流程图。图4的方法由组播复制点执 行。该方法包括：
S401，向所在城域网的OTT直播代理服务器请求加入该OTT直播代理服务器为指定频道分配的组播组。
S402，接收该OTT直播代理服务器以组播方式发送的该指定频道的媒体数据。
S403，将该指定频道的媒体数据以组播方式或单播方式发送给该OTT客户端。
本发明实施例中，组播复制点从OTT直播代理服务器建立的组播组获取频道的媒体数据并发送给OTT客户端，使得OTT客户端不需要再从OTT服务器直接获取频道的媒体数据，能够避免大量重复的直播流穿越骨干网，从而大大减少OTT服务器到城域网之间重复传输的报文，减少直播媒体数据对承载网的带宽占用。
可选地，作为一个实施例，该方法还包括：根据该OTT客户端发送的加入该指定频道的组播加入请求或媒体数据请求，将该OTT客户端加入该组播复制点的组播转发表，并向该OTT直播代理服务器请求加入该组播组。
可选地，作为另一个实施例，该方法还包括：根据该OTT客户端发送的退出该指定频道的请求，将该OTT客户端从该组播复制点的组播转发表中删除。
可选地，该方法还包括：根据该OTT直播代理服务器发送的频道加入指示，将OTT客户端加入到该指定频道的合法用户列表中，其中，该频道加入指示用于通知允许该OTT客户端加入该指定频道。
应理解，在根据该OTT直播代理服务器发送的频道加入指示，将OTT客户端加入到该指定频道的合法用户列表中之前，该方法还可包括：接收该OTT直播代理服务器发送的频道加入指示。
进一步地，该方法还包括：当该组播复制点的组播转发表的OTT客户端为零时，向该OTT直播代理服务器发送组播退出请求，请求退出该组播组。
当然，应理解，上述方法还可以结合在一起使用。例如，该方法还可包括：根据该OTT客户端发送的媒体数据请求，以及该指定频道的合法用户列表，对该OTT客户端加入该指定频道的权限进行鉴权，并在该OTT客户端通过鉴权后，向该OTT直播注入代理服务器请求加入该组播组。
下面，将结合具体的实施例，对本发明图2-图4所示实施例的方法做进一步的描述。
图5是本发明实施例直播媒体数据的一种交互流程图。本发明实施例中，OTT直播代理服务器尚未分配频道1的组播资源，组播复制点也未加入频道1的组播组。在组播复制点到OTT客户端1的数据传输过程中，媒体数据以组播方式传输。
S501，OTT直播代理服务器向OTT服务器发送注册请求。
OTT直播代理服务器向OTT服务器发送注册请求，该注册请求携带注册信息，用于请求注册本城域网的IP网段以及所述OTT直播代理服务器的IP地址。
本发明实施例中，OTT客户端所在的城域网内存在一个已经在OTT服务器注册的OTT直播代理服务器，是本发明方法实施的前置条件。
S502，OTT客户端1向OTT服务器发送频道加入请求。
OTT客户端1向OTT服务器发送频道加入请求，请求加入频道1。
S503，OTT服务器向OTT直播代理服务器发送组播资源分配指示。
OTT服务器根据OTT客户端1发送的频道加入请求，获取OTT客户端1的IP地址及所要加入的频道1，进而根据该IP地址获取从已经注册的OTT直播代理服务器中查询该IP地址所属的城域网，进而得到OTT客户端1对应的OTT直播代理服务器(以下简称OTT直播代理服务器)。
如果OTT服务器发现OTT直播代理服务器尚未加入频道1，则向OTT直播代理服务器发送组播资源分配指示，指示OTT直播代理服务器为频道1分配组播资源。
S504，OTT直播代理服务器向OTT服务器发送媒体描述请求。
OTT直播代理服务器在接收到组播资源分配指示后，向OTT服务器发送媒体描述请求，请求频道1的媒体描述。
S505，OTT服务器向OTT直播代理服务器发送媒体描述。
OTT服务器根据媒体描述请求，返回频道1的媒体描述。
具体地，媒体描述可能包括频道基本信息、频道的分辨率(可能是几种不同的分辨率)、每种分辨率媒体流对应的URL，等等。
S506，OTT直播代理服务器分配组播资源，创建组播组。
应理解，步骤S504和步骤S505并不是必须执行的步骤。在实际的应用中，OTT服务厂商可在OTT直播代理服务器上预先存储部分或全部频道的相关媒体描述，以减少因媒体描述请求引起的信息交互。
OTT直播代理服务器按照频道1的组播资源分配指示，根据频道1的媒体描述，分配频道1的组播资源。频道1的组播资源，可包括频道1的组播组Group1，或者是频道1的组播组Group1和每种码流(或每种分辨率)对应的端口(port)。
OTT直播代理服务器可以通过组播组Group1的IP地址，来确定组播组Group1；或者，OTT直播代理服务器可以通过组播组Group1的IP地址及组播源(即OTT直播 代理服务器)的IP地址，来确定组播组Group1。本发明实施例以通过组播组Group1的IP地址确定组播组Group1为例。
由于频道1的每种分辨率会分别对应一种码流，OTT直播代理服务器需要为每种码流(或每种分辨率)至少要分配一个单独的port。例如，频道1存在2种分辨率(分辨率1和分辨率2)，则分辨率1对应的码流要单独分配1个port，分辨率2对应的码流要单独分配1个port。当然，也可以为分辨率1和分辨率2分配更多的端口。
如果只有一种分辨率，OTT直播代理服务器可只确定频道1的组播组Group1，即可完成频道1的组播资源分配。
或者，OTT直播代理服务器也可预先与组播复制点或OTT客户端约定每种分辨率对应的端口，而不需要每次为频道的不同分辨率配置对应的端口。
S507，OTT直播代理服务器向OTT服务器发送分配的组播资源。
OTT直播代理服务器在分配完频道1的组播资源后，可向OTT服务器发送分配的组播资源。
其中，该组播资源可包括频道1的组播组Group1或频道1的组播组Group1及每种分辨率的码流对应的port。
S508，OTT服务器向OTT直播代理服务器发送频道加入指示。
OTT服务器在接收到频道加入请求之后，可对OTT客户端1进行鉴权，判断OTT客户端1是否有权加入频道1。
如果OTT客户端1通过鉴权，则OTT服务器可向OTT直播代理服务器发送频道加入指示，通知OTT直播代理服务器：OTT客户端1的IP可以加入组播组Group1。
应理解，该鉴权操作可在接收到频道加入请求之后立即进行，也可在对频道1分配组播资源后进行，本发明实施例在此不作限制。
S509，OTT直播代理服务器向组播复制点发送频道加入指示。
本发明实施例中，OTT直播代理服务器在接收到频道加入指示，可将该频道加入指示发给OTT客户端1所属的组播复制点，以便OTT客户端1所属的组播复制点对OTT客户端1的播放请求进行鉴权。
S510，OTT服务器向OTT客户端1发送媒体描述。
OTT服务器把媒体描述通知OTT客户端1。媒体描述包括频道1的分辨率(可能是几种不同的分辨率)、Group1(组播组IP)、每种分辨率媒体流对应的port等。
S511，OTT直播代理服务器向OTT服务器发送媒体数据获取请求。
OTT直播代理服务器向OTT服务器发送媒体数据获取请求，请求获取频道1的所有媒体数据(例如，多个分辨率，则需要获取所有分辨率的媒体数据)。
S512，OTT服务器以单播方式向OTT直播代理服务器发送媒体数据。
OTT服务器以单播方式向OTT直播代理服务器发送媒体数据。
应理解，步骤S511和步骤S512的处理流程，可参考现有技术中OTT服务器-OTT客户端模式下OTT客户端请求媒体数据及OTT服务器单播向OTT客户端发送媒体数据的处理流程，本发明实例在此不再赘述。
S513，OTT直播代理服务器把单播媒体数据转换为组播媒体数据，并在组播组中组播所述媒体数据。
OTT直播代理服务器收到OTT服务器下发的单播媒体数据后，转换为组播包。
OTT直播代理服务器将单播媒体数据转为组播包后，将组播包在本组播组Group1内组播。
此时，位于组播组Group1内的组播复制点都能够接收到OTT直播代理服务器发送的组播包。
本发明实施例的一种实现方式，当OTT直播代理服务器收到单播包后，不是马上转化为组播包发送，而是缓存一定量的包后，做FEC编码。然后在组播组内发送媒体组播包，再用另一Port发送FEC包。如果某个频道有多种码流，则每种码流都有对应的一路FEC包，各用独立的port在组播组内传送。OTT客户端收到组播包后，如果发现当前有丢包/错包，则优先使用FEC还原出正确的数据包。
本发明实施例的另一种实现方式，当OTT直播代理服务器收到单播包后，在包内加上某个序号，来唯一表示某个包。这个序号可以使用IP扩展头；也可以使用UDP扩展头；也可以加上RTP头，使用其中的RTP序号；或者在负荷前部新增一定字节长度的字段来作为序号。OTT直播代理服务器发送这些组播包，同时缓存一定时间长度内的组播包。当OTT客户端发现当前有丢包/错包，则要求OTT直播代理服务器重传相应序号的包。
上述两种方式，可以选择一种方式使用，或结合使用，本发明实施例在此不作限制。
当然，应理解，OTT直播代理服务器还可能采用其它方式传输组播包，本发明实施例在此不作限制。
此外，OTT单播的码流一般是VBR的，即码流会变化的。码流忽大忽小会更容易丢包，但是因为OTT单播一般是基于TCP承载，所以TCP/IP协议栈会自己实现丢包重 传。而在我们的方案中，要把基于TCP的单播改成基于UDP的组播传输，而UDP没有丢包重传的机制。如果发现当前单播码流波动较大(例如，超过平均码流20％)，则对码流做平滑处理。具体方法是缓存一部分报文延迟发送，避开高峰期。
S514，OTT客户端向组播复制点请求加入组播组。
OTT客户端1收到步骤S510反馈的媒体描述后，获知需要加入组播组Group1才能加入到频道1的音频或视频节目，于是OTT客户端1向所属的组播复制点发出IGMP join Group1消息，请求加入组播组Group1。
S515，组播复制点向OTT直播代理服务器请求加入组播组。
组播复制点收到IGMP join Group1消息后，首先对OTT客户端1进行鉴权，判断OTT客户端1是否可以加入频道1的音频或视频节目。
由于步骤S509中的频道加入指示指示组播复制点允许OTT客户端1加入频道1的音频或视频节目，这表明对OTT客户端1的鉴权成功。
此时，组播复制点需要确认自身当前是否已经加入到组播组Group1中。
本发明实施例中，组播复制点可确认自身尚未加入到组播组Group1中。组播复制点需要向OTT直播代理服务器发送PIM join Group1消息，请求加入组播组Group1。
S516，组播复制点在组播组中接收组播的媒体数据。
当组播复制点加入到组播组Group1后，即可收到OTT直播代理服务器在组播组Group1中组播的频道1的媒体数据。
S517，组播复制点向OTT客户端1组播发送媒体数据。
组播复制点收到Group1组播组的数据之后，查询组播转发表记录，发现OTT客户端1加入了Group1，则转发组播媒体包给OTT客户端1。此时，OTT客户端1就能正常加入到频道1的音频或视频节目。
本发明实施例中，OTT服务器根据OTT客户端发送的频道加入请求，在OTT客户端所属的城域网的OTT直播代理服务器分配组播资源，然后将OTT服务器的频道的媒体数据通过单播方式传输到OTT直播代理服务器，再由OTT直播代理服务器以组播方式发送给组播复制点，最后由组播复制点以组播方式将频道的媒体数据传输给OTT客户端，使得同一城域网内的OTT客户端能够共享同一频道的媒体数据资源，从而为OTT服务器节省了大量的带宽，提高了OTT服务器的频道带宽资源利用率。
应理解，不同城域网采用的组播协议可能不同。在加入组播组时，有的IGMP join组播组IP地址，有的是IGMP join(组播组IP地址+组播源IP地址)。即，有的以组播组 IP地址来表示组播组，有的以组播组IP地址+组播源IP地址来表示组播组。此时，需要对上述实施例中的组播组相关作适应性的调整。下面实施例中涉及组播组的部分与此类似，不再赘述。
应理解，本发明实施例中，步骤S502及步骤S503，OTT客户端向OTT服务器发送频道加入请求，请求加入频道1，从而触发OTT服务器向OTT直播代理服务器发送组播资源分配指示。在具体的应用中，也可能是OTT客户端直接向组播复制点发送频道加入请求，请求加入频道1，再通过组播复制点向OTT直播代理服务器发送组播资源分配指示，指示OTT直播代理服务器对频道1分配组播资源。其余步骤可与本发明实施例的步骤类似，本发明实施例在此不再赘述。
图6是本发明实施例直播媒体数据的一种交互流程图。本发明实施例中，OTT直播代理服务器已经分配频道1的组播资源，组播复制点也已经加入频道1的组播组。在组播复制点到OTT客户端2的数据传输过程中，媒体数据以组播方式传输。
S601，OTT客户端2向OTT服务器发送频道加入请求。
OTT客户端2向OTT服务器发送频道加入请求，请求加入频道1。
S602，OTT服务器向OTT直播代理服务器发送频道加入指示。
OTT服务器在接收到频道加入请求之后，可对OTT客户端2进行鉴权，判断OTT客户端2是否有权加入频道1。
此外，OTT服务器根据OTT客户端2的频道加入请求，确定OTT客户端2所在城域网的OTT直播代理服务器，进而可获知OTT直播代理服务器已经分配频道1的组播资源。
如果OTT客户端2通过鉴权，则OTT服务器可向OTT直播代理服务器发送频道加入指示，通知OTT直播代理服务器：OTT客户端2的IP可以加入组播组Group1。
S603，OTT直播代理服务器向组播复制点发送频道加入指示。
本发明实施例中，OTT直播代理服务器在接收到频道加入指示，可将该频道加入指示发给OTT客户端2所属的组播复制点，以便OTT客户端2所属的组播复制点对OTT客户端2的播放请求进行鉴权。
S604，OTT服务器向OTT客户端2发送媒体描述。
OTT服务器把媒体描述通知OTT客户端2。媒体描述包括频道1的分辨率(可能是几种不同的分辨率)、Group1(组播组IP)、每种分辨率媒体流对应的port等。
S605，OTT客户端向组播复制点请求加入组播组。
OTT客户端2收到步骤S510反馈的媒体描述后，获知需要加入组播组Group1才能加入到频道1的音频或视频节目，于是OTT客户端2向所属的组播复制点发出IGMP join Group1消息，请求加入组播组Group1。
S606，组播复制点向OTT客户端2组播发送媒体数据。
此外，本发明实施例中，组播复制点已经加入组播组Group1，并在组播组中接收组播的媒体数据。
组播复制点收到IGMP join Group1消息后，首先对OTT客户端2进行鉴权，判断OTT客户端2是否可以加入频道1的音频或视频节目。由于步骤S603中的频道加入指示指示组播复制点允许OTT客户端2加入频道1的音频或视频节目，这表明对OTT客户端2的鉴权成功。
此时，组播复制点可转发组播媒体包给OTT客户端2，OTT客户端2就能正常加入到频道1的音频或视频节目。
图7是本发明实施例直播媒体数据的一种交互流程图。本发明实施例中，OTT直播代理服务器尚未分配频道1的组播资源，组播复制点也未加入频道1的组播组。在组播复制点到OTT客户端1的数据传输过程中，媒体数据以单播方式传输。
S701，OTT直播代理服务器向OTT服务器发送注册请求。
S702，OTT客户端1向OTT服务器发送频道加入请求。
S703，OTT服务器向OTT直播代理服务器发送组播资源分配指示。
S704，OTT直播代理服务器向OTT服务器发送媒体描述请求。
S705，OTT服务器向OTT直播代理服务器发送媒体描述。
S706，OTT直播代理服务器分配组播资源，创建组播组。
步骤S701-S706的具体实现可参考图5的步骤S501-S506，本发明实施例在此不再赘述。
S707，OTT直播代理服务器向OTT服务器发送分配的组播资源。
OTT直播代理服务器在为频道1分配组播资源(频道1的组播组Group1或频道1的组播组Group1及每种分辨率的码流对应的port)后，可向OTT服务器发送分配的组播资源。
S708，OTT直播代理服务器向组播复制点发送频道和组播组的对应关系。
OTT直播代理服务器向组播复制点发送频道和组播组的对应关系，这样，当组播复制点接到OTT客户端要加入频道1的请求，就可以知道需要加入的组播IP地址。
S709，OTT直播代理服务器向OTT服务器发送媒体数据获取请求。
OTT直播代理服务器向OTT服务器发送媒体数据获取请求，请求获取频道1的所有媒体数据(例如，多个分辨率，则需要获取所有分辨率的媒体数据)。
S710，OTT服务器以单播方式向OTT直播代理服务器发送媒体数据。
OTT服务器以单播方式向OTT直播代理服务器发送媒体数据。
应理解，步骤S709和步骤S710的处理流程，可参考现有技术中OTT服务器-OTT客户端模式下OTT客户端请求媒体数据及OTT服务器单播向OTT客户端发送媒体数据的处理流程，本发明实例在此不再赘述。
S711，OTT直播代理服务器把单播媒体数据转换为组播媒体数据。
步骤S711的具体实现可参考图5的步骤S513，本发明实施例在此不再赘述。
S712，OTT服务器向OTT直播代理服务器发送频道加入指示。
步骤S712的具体实现可参考图5的步骤S508，本发明实施例在此不再赘述。
S713，OTT服务器指示OTT客户端1重定向到OTT直播代理服务器。
OTT服务器向OTT客户端1发送重定向命令，要求OTT客户端1向OTT直播代理服务器获取媒体描述。在本命令内包含了OTT直播代理服务器的IP地址。
S714，OTT客户端1向OTT直播代理服务器发送频道加入请求。
OTT客户端1收到重定向命令后，向OTT直播代理服务器发送频道加入请求，请求加入频道1。
S715，OTT直播代理服务器将媒体描述中的视频URL改为指向组播复制点。
OTT直播代理服务器上根据步骤S705下载的媒体描述，把其中视频的URL修改为OTT客户端1所属的组播复制点的IP地址。
S716，OTT直播代理服务器向组播复制点发送频道加入指示。
本发明实施例中，OTT直播代理服务器在接收到频道加入指示，可将该频道加入指示发给OTT客户端1所属的组播复制点，以便OTT客户端1所属的组播复制点对OTT客户端1的播放请求进行鉴权。
S717，OTT直播代理服务器在组播组中组播媒体数据。
步骤S717的具体实现可参考图5的步骤S513，本发明实施例在此不再赘述。
S718，OTT直播代理服务器向OTT客户端1发送修改后的媒体描述。
OTT直播代理服务器发送频道1的媒体描述给OTT客户端1，其中视频的URL已经修改为OTT客户端1所属的组播复制点的IP。
S719，OTT客户端1向组播复制点发送媒体数据获取请求。
OTT客户端1根据媒体描述中的视频URL，向所属的组播复制点请求加入组播组。
S720，组播复制点向OTT直播代理服务器请求加入组播组。
组播复制点根据请求获知OTT客户端1要加入的是频道1的视频，并判断出OTT客户端1被允许加入频道1，进而查询出频道1对应组播组Group1。
由于组播复制点当前尚未加入Group1，组播复制点可发出PIM join Group1消息，请求加入组播组Group1。
S721，组播复制点在组播组中接收组播的媒体数据，缓存并转换为单播媒体数据。
组播复制点加入组播组Group1成功后，就会收到组播组Group1下发的组播媒体数据。
组播复制点缓存组播媒体数据并转化为单播媒体数据。
S722，组播复制点向OTT客户端1单播媒体数据。
此时，OTT客户端1就可以加入频道1的视频了。
图8是本发明实施例直播媒体数据的一种交互流程图。本发明实施例中，OTT直播代理服务器已经分配频道1的组播资源，组播复制点也已经加入频道1的组播组。在组播复制点到OTT客户端2的数据传输过程中，媒体数据以单播方式传输。
S801，OTT客户端2向OTT服务器发送频道加入请求。
OTT客户端2向OTT服务器发送频道加入请求，请求加入频道1。
S802，OTT服务器向OTT直播代理服务器发送频道加入指示。
OTT服务器在接收到频道加入请求之后，可对OTT客户端2进行鉴权，判断OTT客户端2是否有权加入频道1。
此外，OTT服务器根据OTT客户端2的频道加入请求，确定OTT客户端2所在城域网的OTT直播代理服务器，进而可获知OTT直播代理服务器已经分配频道1的组播资源。
如果OTT客户端2通过鉴权，则OTT服务器可向OTT直播代理服务器发送频道加入指示，通知OTT直播代理服务器：OTT客户端2的IP可以加入组播组Group1。
S803，OTT服务器指示OTT客户端2重定向到OTT直播代理服务器。
OTT服务器向OTT客户端2发送重定向命令，要求OTT客户端2向OTT直播代理服务器获取媒体描述。在本命令内包含了OTT直播代理服务器的IP地址。
S804，OTT客户端21向OTT直播代理服务器发送频道加入请求。
OTT客户端2收到重定向命令后，向OTT直播代理服务器发送频道加入请求，请求加入频道1。
S805，OTT直播代理服务器向组播复制点发送频道加入指示。
本发明实施例中，OTT直播代理服务器在接收到频道加入指示，可将该频道加入指示发给OTT客户端2所属的组播复制点，以便OTT客户端2所属的组播复制点对OTT客户端2的播放请求进行鉴权。
S806，OTT直播代理服务器向OTT客户端2发送修改后的媒体描述。
OTT直播代理服务器上根据频道1的媒体描述，把其中视频的URL修改为OTT客户端2所属的组播复制点的IP。
OTT直播代理服务器发送频道1的媒体描述给OTT客户端2，其中视频的URL已经修改为OTT客户端2所属的组播复制点的IP。
S807，OTT客户端2向组播复制点请求加入组播组。
OTT客户端2根据媒体描述中的视频URL，向所属的组播复制点请求下载媒体数据。
S808，组播复制点向OTT客户端2单播媒体数据。
本发明实施例中，组播复制点已经加入组播组。此时，组播复制点在组播组中接收组播的媒体数据，缓存并转换为单播报文。
组播复制点可根据OTT客户端2的媒体数据获取请求，向OTT客户端2单播媒体数据。
此时，OTT客户端2就可以加入频道1的视频了。
图9是本发明实施例直播媒体数据的一种交互流程图。本发明实施例中，OTT客户端1已经通过组播复制点加入频道1的视频节目。
S901，OTT客户端1向组播复制点请求离开组播组。
当OTT客户端1不再加入频道1时，可向上行设备(组播复制点)发送IGMP leaveGroup1消息，请求退出Group1组播组。
S902，组播复制点将OTT客户端1从组播转发表中删除。
当组播复制点收到了OTT客户端的IGMP leave Group1消息后，组播复制点把OTT客户端从Group1组播转发表中去除。
S903，组播复制点向OTT直播代理服务器请求调整组播组。
如果组播复制点发现Group1组播转发表中没有任何OTT客户端时，就把该组播表 项删除，并且向上行设备(OTT直播代理服务器)发送IGMP leave Group1消息，请求调整组播组。
S904，OTT直播代理服务器在组播组的组播表项中删除对应的出端口。
OTT直播代理服务器收到某下行端口发送的IGMP leave Group1消息后，则在Group1组播转发表项中删除对应下行端口的出端口。
S905，OTT直播代理服务器释放组播组对应的频道资源。
本发明实施例中，该组播组对应于频道1。
如果该组播组的组播表项没有剩余出端口，则说明本城域网已经没有用户在加入频道1。
此时，OTT直播代理服务器可删除Group1组播表项，断开频道1从OTT服务器的媒体下载连接，释放为频道1分配的组播资源，同时，通知OTT服务器。
本发明实施例中，通过回收资源，可减少组播复制点、OTT直播代理服务器或OTT服务器的傅干，提高资源的利用效率。
图10是本发明实施例直播媒体数据的一种交互流程图。本发明实施例中，OTT直播代理服务器尚未分配频道1的组播资源，组播复制点也未加入频道1的组播组。在组播复制点到OTT客户端的数据传输过程中，媒体数据以组播方式传输。
S1001，OTT直播代理服务器向OTT服务器发送注册。
S1002，OTT客户端1向OTT服务器发送频道加入请求。
S1003，OTT服务器向OTT直播代理服务器发送组播资源分配指示。
S1004，OTT直播代理服务器向OTT服务器发送媒体描述请求。
S1005，OTT服务器向OTT直播代理服务器发送媒体描述。
S1006，OTT直播代理服务器分配组播资源，创建组播组。
S1007，OTT直播代理服务器向OTT服务器发送分配的组播资源。
S1008，OTT服务器向OTT直播代理服务器发送频道加入指示。
S1009，OTT直播代理服务器向组播复制点发送频道加入指示。
步骤S1001-S1009的具体实现可参考图5的步骤S501-S505，本发明实施例在此不再赘述。
S1010，OTT服务器指示OTT客户端1重定向到OTT直播代理服务器。
OTT服务器向OTT客户端1发送重定向命令，要求OTT客户端1向OTT直播代理服务器获取媒体描述。在本命令内包含了OTT直播代理服务器的IP地址。
S1011，OTT客户端1向OTT直播代理服务器发送频道加入请求。
OTT客户端1收到重定向命令后，向OTT直播代理服务器发送频道加入请求，请求加入频道1。
S1012，OTT直播代理服务器向OTT客户端1发送修改后的媒体描述。
OTT直播代理服务器上根据步骤S1005下载的媒体描述，把其中视频的URL修改为OTT客户端1所属的组播复制点的IP。
OTT直播代理服务器发送频道1的媒体描述给OTT客户端1，其中视频的URL已经修改为OTT客户端1所属的组播复制点的IP。
S1013，OTT服务器向OTT客户端1发送媒体描述。
S1014，OTT直播代理服务器向OTT服务器发送媒体数据获取请求。
步骤S1013-S1014的具体实现可参考图5的步骤S510-S511，本发明实施例在此不再赘述。
图11是本发明实施例直播媒体数据的一种交互流程图。
S1101，OTT直播代理服务器向OTT服务器发送注册。
OTT直播代理服务器向OTT服务器发送注册，请求注册本城域网的IP网段以及所述OTT直播代理服务器的IP地址。
S1102，OTT服务器向OTT直播代理服务器发送频道x的组播资源分配指示。
S1103，OTT直播代理服务器向OTT服务器发送频道x的媒体描述请求。
S1104，OTT服务器向OTT直播代理服务器发送频道x的媒体描述。
S1105，OTT直播代理服务器分配频道x的组播资源，创建频道x的组播组Groupx。
S1106，OTT直播代理服务器向OTT服务器发送频道x分配的组播资源。
S1107，OTT直播代理服务器向OTT服务器发送频道x媒体数据获取请求。
S1108，OTT服务器向OTT直播代理服务器单播频道x的媒体数据。
步骤S1102-S1108的具体实现可参考图5的步骤S502-S506及步骤S511-S512，本发明实施例在此不再赘述。
此外，应理解，本发明实施例中，步骤S1102-S1108可反复执行。也就是说，OTT服务器可指示OTT直播代理服务器为多个频道创建组播资源。
S1109，OTT客户端1向OTT服务器发送频道n的加入请求。
OTT客户端1向OTT服务器发送频道n的加入请求，请求加入频道n。
S1110，OTT服务器向OTT直播代理服务器发送频道n的频道加入指示。
OTT服务器根据频道n的加入请求，对OTT客户端1进行鉴权。如果OTT客户端1被允许加入频道n，且OTT客户端1所在城域网的OTT直播代理服务器已经为频道n分配组播资源(组播组Groupnn)，则OTT服务器可向OTT直播代理服务器发送频道加入指示，通知OTT直播代理服务器：OTT客户端1的IP可以加入组播组Groupn。
S1111，OTT直播代理服务器向组播复制点发送频道n的频道加入指示。
OTT直播代理服务器在接收到频道加入指示，可将该频道加入指示发给OTT客户端1所属的组播复制点，以便OTT客户端1所属的组播复制点对OTT客户端1的播放请求进行鉴权。
之后的操作可与图5或图7所示实施例类似，本发明实施例在此不再赘述。
图12是本发明实施例OTT直播代理服务器1200的结构示意图。如图12所示，OTT直播代理服务器1200可包括：获取单元1201，组播资源分配单元1202，组播单元1203。其中，
组播资源分配单元1202，用于根据指定频道的组播资源分配指示及该指定频道的媒体描述为该指定频道分配组播资源。
其中，该组播资源分配指示用于通知该OTT直播代理服务器为该指定频道分配组播资源，该指定频道的媒体描述包括该指定频道的至少一种分辨率及该至少一种分辨率的媒体数据所对应的统一资源定位符(Uniform Resoure Locator，URL)，该组播资源包括该指定频道对应的组播组或该指定频道对应的组播组及该至少一种分辨率对应的端口port。
获取单元1201，用于根据该指定频道的媒体描述通过单播方式从该指定频道所属的OTT服务器获取该至少一种分辨率对应的媒体数据；
组播单元1203，用于将该至少一种分辨率对应的媒体数据转换为组播媒体数据，并将该组播媒体数据组播发送给已经加入该组播组的组播复制点。
本发明实施例中，OTT直播代理服务器1200根据OTT服务器的频道分配指示分配频道的组播资源，并从OTT服务器获取频道的媒体数据，再将频道的媒体数据组播发送到频道对应的组播组，以便组播组内的组播复制点能够将频道的媒体数据传输给加入频道的OTT客户端，能够避免大量重复的直播流穿越骨干网，从而大大减少OTT服务器到城域网之间重复传输的报文，减少直播媒体数据对承载网的带宽占用。
可选地，OTT直播代理服务器还可包括接收单元，用于接收该组播资源分配指示。其中，该组播资源分配指示是OTT直播代理服务器的OTT服务器发送的，或者，该组 播资源分配指示是OTT直播代理服务器所在的城域网的组播复制点。
图13是本发明实施例OTT直播代理服务器1200的另一结构示意图。
可选地，作为一个实施例，获取单元1201还用于从该OTT服务器获取该指定频道的媒体描述。
可选地，作为另一个实施例，该指定频道的媒体描述是预先存储在该OTT直播代理服务器中的。OTT服务厂商可预先在OTT代理服务器上存储部分或全部频道的相关媒体描述，以减少因媒体描述请求引起的信息交互。
可选地，如图13所示，OTT直播代理服务器1200还可包括：转发单元1204，用于接收该OTT服务器发送的频道加入指示，并将该频道加入指示发送给该OTT直播代理服务器所在的城域网的组播复制点，以使该组播复制点将OTT客户端加入到该指定频道的合法用户列表中，其中，该频道加入指示用于通知允许该OTT客户端加入该指定频道。
可选地，如图13所示，OTT直播代理服务器1200还可包括：注册单元1205，用于向该OTT服务器注册该OTT直播代理服务器所在的城域网的互联网协议IP网段及该OTT直播代理服务器的IP地址。
可选地，作为一个实施例，组播资源分配单元1202还用于将该分配的组播资源反馈给该OTT服务器，以便该OTT服务器将该组播资源发送给OTT客户端，使得该OTT客户端能够加入该组播组。
可选地，作为另一个实施例，组播资源分配单元1202还用于将该指定频道与该指定频道的组播组之间的对应关系发送给该OTT直播代理服务器所在城域网内的组播复制点，以便该组播复制点根据OTT客户端发送的加入该指定频道的请求，确定该指定频道对应的组播组。
进一步地，该组播资源分配单元1202还用于根据OTT客户端发送的加入该指定频道的请求，将该组播资源发送给该OTT客户端，以便该OTT客户端向组播复制点请求该指定频道的媒体数据。
可选地，如图13所示，OTT直播代理服务器1200还可包括：组播组管理单元1206，用于：
根据该组播复制点的组播加入请求，将该组播复制点加入该组播组，并在该组播组的组播转发表项添加该组播复制点对应的出端口；或者
根据该组播复制点的组播退出请求，将该组播复制点从该组播组中删除，并在该组 播组的组播转发表项删除该组播复制点对应的出端口。
进一步地，组播组管理单元1206还用于当该组播组的组播转发表项中出端口数为零时，删除该组播组的组播转发表项，并断开从该OTT服务器下载该指定频道的媒体数据的链接。
此外，OTT直播代理服务器1200还可执行图2的方法，并实现OTT直播代理服务器在图5-图11所示实施例中的功能，本发明实施例在此不再赘述。
图14是本发明实施例OTT服务器1400的结构示意图。OTT服务器1400可包括组播资源分配指示单元1401、媒体描述管理单元1402和媒体资源管理单元1403。
组播资源分配指示单元1401，用于向在该OTT服务器1400中注册的OTT直播代理服务器发送组播资源分配指示。其中，该组播资源分配指示用于通知该OTT直播代理服务器对指定频道分配组播资源。
媒体描述管理单元1402，用于根据该OTT直播代理服务器发送的获取该指定频道的媒体描述的请求，将该指定频道的媒体描述发送给该OTT直播代理服务器。其中，该指定频道的媒体描述包括该指定频道的至少一种分辨率及该至少一种分辨率的媒体数据所对应的URL。
媒体资源管理单元1403，用于根据该OTT直播代理服务器对该指定频道的媒体数据获取请求，将该指定频道的至少一种分辨率的媒体数据以单播方式发送给该OTT直播代理服务器。
本发明实施例中，OTT服务器1400指示OTT直播代理服务器建立组播组分配频道的组播资源，并以单播方式向OTT直播代理服务器发送频道的媒体数据，使得OTT直播代理服务器将频道的媒体数据经组播复制点发送给加入组播组的OTT客户端，能够避免大量重复的直播流穿越骨干网，从而大大减少OTT服务器到城域网之间重复传输的报文，减少直播媒体数据对承载网的带宽占用。
图15是本发明实施例OTT服务器1400的另一结构示意图。
可选地，如图15所示，OTT服务器1400还可包括：注册单元1404，用于根据该OTT直播代理服务器发送的注册请求，记录该OTT直播代理服务器所在的城域网的互联网协议IP网段及该OTT直播代理服务器的IP地址。其中，该注册请求携带该OTT直播代理服务器所在的城域网的IP网段及该OTT直播代理服务器的IP地址。
可选地，如图15所示，OTT服务器1400还可包括：鉴权单元1405，用于根据该OTT所在的城域网中的OTT客户端加入该指定频道的请求，确定是否允许该OTT客户 端加入该指定频道。该组播资源分配指示单元1401具体用于当该鉴权单元1405确定允许该OTT客户端加入该指定频道后，且该OTT服务器上不存在该OTT直播代理服务器发送的该指定频道的组播资源时，向该OTT直播代理服务器发送该组播资源分配指示。
进一步地，作为一个实施例，该鉴权单元1405还用于在允许该OTT客户端加入该指定频道后，向该OTT直播代理服务器发送频道加入指示，该频道加入指示用于通知该OTT直播代理服务器允许该OTT客户端加入该指定频道。
或者，进一步地，作为另一个实施例，该鉴权单元1405还用于将该OTT直播代理服务器反馈的为该指定频道分配的组播资源发送给该OTT客户端，以便该OTT客户端向组播复制点请求该指定频道的媒体数据。其中，该组播资源包括该指定频道对应的组播组及该指定频道的至少一种分辨率对应的port。
可选地，如图15所示，OTT服务器1400还可包括：重定位指示单元1406，用于根据该OTT客户端加入该指定频道的请求，以及该指定频道的组播资源，指示该OTT客户端将该指定频道的加入请求重定位到该OTT直播代理服务器上。
此外，OTT服务器1400还可执行图3的方法，并实现OTT服务器在图5-11所示实施例的功能，本发明实施例在此不再赘述。
图16是本发明实施例组播复制点1600的结构示意图。组播复制点1600可包括组播管理单元1601、媒体数据获取单元1602和媒体数据管理单元1603。其中，
组播管理单元1601，用于向所在城域网的OTT直播代理服务器请求加入该OTT直播代理服务器为指定频道分配的组播组。
媒体数据获取单元1602，用于接收该OTT直播代理服务器以组播方式发送的该指定频道的媒体数据。
媒体数据管理单元1603，用于将该指定频道的媒体数据以组播方式或单播方式发送给该OTT客户端。
本发明实施例中，组播复制点1600从OTT直播代理服务器建立的组播组获取频道的媒体数据并发送给OTT客户端，使得OTT客户端不需要再从OTT服务器直接获取频道的媒体数据，能够避免大量重复的直播流穿越骨干网，从而大大减少OTT服务器到城域网之间重复传输的报文，减少直播媒体数据对承载网的带宽占用。
可选地，组播复制点1600还可包括：权限管理单元1604，用于根据所在城域网的OTT直播代理服务器发送的频道加入指示，将OTT客户端加入到该指定频道的合法用 户列表中，其中，该频道加入指示用于通知允许该OTT客户端加入该指定频道。
可选地，组播管理单元1601还用于：根据该OTT客户端发送的加入该指定频道的组播加入请求或媒体数据请求，将该OTT客户端加入该组播复制点的组播转发表，并向该OTT直播代理服务器请求加入该组播组；或者，根据该OTT客户端发送的退出该指定频道的请求，将该OTT客户端从该组播复制点的组播转发表中删除。
进一步地，组播管理单元1601还用于：当该组播复制点的组播转发表的OTT客户端为零时，向该OTT直播代理服务器发送组播退出请求，请求退出该组播组。
可选地，组播管理单元1601还用于：根据该OTT客户端发送的媒体数据请求，以及该指定频道的合法用户列表，对该OTT客户端加入该指定频道的权限进行鉴权，并在该OTT客户端通过鉴权后，向该OTT直播注入代理服务器请求加入该组播组。
此外，组播复制点1600还可执行图4的方法，并实现组播复制点在图5-11所示实施例的功能，本发明实施例在此不再赘述。
图17是本发明实施例OTT直播代理服务器1700的结构示意图。OTT直播代理服务器1700可包括通道接口1701、处理器1702和存储器1703。
通道接口1701、处理器1702和存储器1703通过总线1704***相互连接。总线1704可以是ISA总线、PCI总线或EISA总线等。所述总线可以分为地址总线、数据总线、控制总线等。为便于表示，图17中仅用一个双向箭头表示，但并不表示仅有一根总线或一种类型的总线。
存储器1703，用于存放程序。具体地，程序可以包括程序代码，所述程序代码包括计算机操作指令。存储器1703可以包括只读存储器和随机存取存储器，并向处理器1702提供指令和数据。存储器1703可能包含高速RAM存储器，也可能还包括非易失性存储器(non-volatile memory)，例如至少一个磁盘存储器。
处理器1702，执行存储器1703所存放的程序，并具体用于执行以下操作：
根据OTT服务器发送的组播资源分配指示，根据指定频道的组播资源分配指示及该指定频道的媒体描述为该指定频道分配组播资源，其中，该组播资源分配指示用于通知该OTT直播代理服务器为该指定频道分配组播资源，该指定频道的媒体描述包括该指定频道的至少一种分辨率及该至少一种分辨率的媒体数据所对应的URL，该组播资源包括该指定频道对应的组播组或该指定频道对应的组播组及该至少一种分辨率对应的port；
根据该指定频道的媒体描述，通过通道接口1701以单播方式从该指定频道所属的 OTT服务器获取该至少一种分辨率对应的媒体数据；
将该至少一种分辨率对应的媒体数据转换为组播媒体数据，并通过通道接口1701将该组播媒体数据组播发送给已经加入该组播组的组播复制点。
上述如本发明图2、图5-11中任一实施例揭示的OTT直播代理服务器执行的方法可以应用于处理器1702中，或者由处理器1702实现。处理器1702可能是一种集成电路芯片，具有信号的处理能力。在实现过程中，上述方法的各步骤可以通过处理器1702中的硬件的集成逻辑电路或者软件形式的指令完成。上述的处理器1702可以是通用处理器，包括中央处理器(Central Processing Unit，简称CPU)、网络处理器(Network Processor，简称NP)等；还可以是数字信号处理器(DSP)、专用集成电路(ASIC)、现成可编程门阵列(FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件。可以实现或者执行本发明实施例中的公开的各方法、步骤及逻辑框图。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。结合本发明实施例所公开的方法的步骤可以直接体现为硬件译码处理器执行完成，或者用译码处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存储器，闪存、只读存储器，可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质中。该存储介质位于存储器1703，处理器1702读取存储器1703中的信息，结合其硬件完成上述方法的步骤。
本发明实施例中，OTT直播代理服务器根据OTT服务器的频道分配指示分配频道的组播资源，并从OTT服务器获取频道的媒体数据，再将频道的媒体数据组播发送到频道对应的组播组，以便组播组内的组播复制点能够将频道的媒体数据传输给加入频道的OTT客户端，能够避免大量重复的直播流穿越骨干网，从而大大减少OTT服务器到城域网之间重复传输的报文，减少直播媒体数据对承载网的带宽占用。
可选地，作为一个实施例，处理器1702还用于：通过通道接口1701从该OTT服务器获取该指定频道的媒体描述。
可选地，作为另一个实施例，该指定频道的媒体描述是预先存储在该OTT直播代理服务器中的。OTT服务厂商可预先在OTT代理服务器上存储部分或全部频道的相关媒体描述，以减少因媒体描述请求引起的信息交互。
可选地，处理器1702还用于：通过通道接口1701接收该组播资源分配指示。其中，该组播资源分配指示是OTT直播代理服务器的OTT服务器发送的，或者，该组播资源分配指示是OTT直播代理服务器所在的城域网的组播复制点。
可选地，处理器1702还用于：通过通道接口1701接收该OTT服务器发送的频道加入指示，并将该频道加入指示发送给该OTT直播代理服务器所在的城域网的组播复制点，以使该组播复制点将OTT客户端加入到该指定频道的合法用户列表中，其中，该频道加入指示用于通知允许该OTT客户端加入该指定频道。
可选地，处理器1702还用于：通过通道接口1701向该OTT服务器注册该OTT直播代理服务器所在的城域网的IP网段及该OTT直播代理服务器的IP地址。
可选地，作为一个实施例，处理器1702还用于：通过通道接口1701将该分配的组播资源反馈给该OTT服务器，以便该OTT服务器将该组播资源发送给该OTT客户端，使得该OTT客户端能够加入该组播组。
可选地，作为另一个实施例，处理器1702还用于：通过通道接口1701将该指定频道与该指定频道的组播组之间的对应关系发送给该OTT直播代理服务器所在城域网内的组播复制点，以便该组播复制点根据OTT客户端发送的加入该指定频道的请求，确定该指定频道对应的组播组。
进一步地，处理器1702还用于：根据OTT客户端发送的加入该指定频道的请求，通过通道接口1701将该组播资源发送给该OTT客户端，以便该OTT客户端向组播复制点请求该指定频道的媒体数据。
可选地，作为一个实施例，处理器1702还用于：根据该组播复制点的组播加入请求，将该组播复制点加入该组播组，并在该组播组的组播转发表项添加该组播复制点对应的出端口。
可选地，作为另一个实施例，处理器1702还用于：根据该组播复制点的组播退出请求，将该组播复制点从该组播组中删除，并在该组播组的组播转发表项删除该组播复制点对应的出端口。
进一步地，处理器1702还用于：当该组播组的组播转发表项中出端口数为零时，删除该组播组的组播转发表项，并断开从该OTT服务器下载该指定频道的媒体数据的链接。
此外，OTT直播代理服务器1700还可执行图2的方法，并实现OTT直播代理服务器在图5-图11所示实施例中的功能，本发明实施例在此不再赘述。
图18是本发明实施例OTT服务器1800的结构示意图。OTT服务器1800可包括通道接口1801、处理器1802和存储器1803。
通道接口1801、处理器1802和存储器1803通过总线1804***相互连接。总线1804 可以是ISA总线、PCI总线或EISA总线等。所述总线可以分为地址总线、数据总线、控制总线等。为便于表示，图18中仅用一个双向箭头表示，但并不表示仅有一根总线或一种类型的总线。
存储器1803，用于存放程序。具体地，程序可以包括程序代码，所述程序代码包括计算机操作指令。存储器1803可以包括只读存储器和随机存取存储器，并向处理器1802提供指令和数据。存储器1803可能包含高速RAM存储器，也可能还包括非易失性存储器(non-volatile memory)，例如至少一个磁盘存储器。
处理器1802，执行存储器1803所存放的程序，并具体用于执行以下操作：
通过通道接口1801向在OTT服务器1800中注册的OTT直播代理服务器发送组播资源分配指示，其中，该组播资源分配指示用于通知该OTT直播代理服务器对指定频道分配组播资源；
根据该OTT直播代理服务器发送的获取该指定频道的媒体描述的请求，通过通道接口1801将该指定频道的媒体描述发送给该OTT直播代理服务器，其中，该指定频道的媒体描述包括该指定频道的至少一种分辨率及该至少一种分辨率的媒体数据所对应的URL；
根据该OTT直播代理服务器对该指定频道的媒体数据获取请求，通过通道接口1801将该指定频道的至少一种分辨率的媒体数据以单播方式发送给该OTT直播代理服务器。
上述如本发明图3、图5-11中任一实施例揭示的OTT服务器执行的方法可以应用于处理器1802中，或者由处理器1802实现。处理器1802可能是一种集成电路芯片，具有信号的处理能力。在实现过程中，上述方法的各步骤可以通过处理器1802中的硬件的集成逻辑电路或者软件形式的指令完成。上述的处理器1802可以是通用处理器，包括中央处理器(Central Processing Unit，简称CPU)、网络处理器(Network Processor，简称NP)等；还可以是数字信号处理器(DSP)、专用集成电路(ASIC)、现成可编程门阵列(FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件。可以实现或者执行本发明实施例中的公开的各方法、步骤及逻辑框图。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。结合本发明实施例所公开的方法的步骤可以直接体现为硬件译码处理器执行完成，或者用译码处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存储器，闪存、只读存储器，可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质中。该存储介质 位于存储器1803，处理器1802读取存储器1803中的信息，结合其硬件完成上述方法的步骤。
本发明实施例中，OTT服务器1800指示OTT直播代理服务器建立组播组分配频道的组播资源，并以单播方式向OTT直播代理服务器发送频道的媒体数据，使得OTT直播代理服务器将频道的媒体数据经组播复制点发送给加入组播组的OTT客户端，能够避免大量重复的直播流穿越骨干网，从而大大减少OTT服务器到城域网之间重复传输的报文，减少直播媒体数据对承载网的带宽占用。
可选地，处理器1802还用于：根据该OTT直播代理服务器发送的注册请求，记录该OTT直播代理服务器所在的城域网的互联网协议IP网段及该OTT直播代理服务器的IP地址，其中，该注册请求携带该OTT直播代理服务器所在的城域网的IP网段及该OTT直播代理服务器的IP地址。
可选地，作为一个实施例，处理器1802还用于：根据该OTT所在的城域网中的OTT客户端加入该指定频道的请求，确定是否允许该OTT客户端加入该指定频道。进一步地，在用于向在该OTT服务器中注册的OTT直播代理服务器发送组播资源分配指示的过程中，处理器1802具体用于：当处理器1802确定允许该OTT客户端加入该指定频道后，且该OTT服务器上不存在该OTT直播代理服务器发送的该指定频道的组播资源时，向该OTT直播代理服务器发送该组播资源分配指示。
可选地，处理器1802还用于：在允许该OTT客户端加入该指定频道后，向该OTT直播代理服务器发送频道加入指示，该频道加入指示用于通知该OTT直播代理服务器允许该OTT客户端加入该指定频道。
进一步地，作为一个实施例，处理器1802还用于：将该OTT直播代理服务器反馈的为该指定频道分配的组播资源发送给该OTT客户端，以便该OTT客户端向组播复制点请求该指定频道的媒体数据，其中，该组播资源包括该指定频道对应的组播组或该指定频道对应的组播组及该指定频道的至少一种分辨率对应的端口。
或者，进一步地，作为另一个实施例，处理器1802还用于：根据该OTT客户端加入该指定频道的请求，以及该指定频道的组播资源，指示该OTT客户端将该指定频道的加入请求重定位到该OTT直播代理服务器上。
此外，OTT服务器1800还可执行图3的方法，并实现OTT服务器在图5-11所示实施例的功能，本发明实施例在此不再赘述。
图19是本发明实施例组播复制点1900的结构示意图。组播复制点1900可包括通 道接口1901、处理器1902和存储器1903。
通道接口1901、处理器1902和存储器1903通过总线1904***相互连接。总线1904可以是ISA总线、PCI总线或EISA总线等。所述总线可以分为地址总线、数据总线、控制总线等。为便于表示，图19中仅用一个双向箭头表示，但并不表示仅有一根总线或一种类型的总线。
存储器1903，用于存放程序。具体地，程序可以包括程序代码，所述程序代码包括计算机操作指令。存储器1903可以包括只读存储器和随机存取存储器，并向处理器1902提供指令和数据。存储器1903可能包含高速RAM存储器，也可能还包括非易失性存储器(non-volatile memory)，例如至少一个磁盘存储器。
处理器1902，执行存储器1903所存放的程序，并具体用于执行以下操作：
通过通道接口1901向所在城域网的OTT直播代理服务器请求加入该OTT直播代理服务器为指定频道分配的组播组；
通过通道接口1901接收该OTT直播代理服务器以组播方式发送的该指定频道的媒体数据；
通过通道接口1901将该指定频道的媒体数据以组播方式或单播方式发送给该OTT客户端。
上述如本发明图4-11中任一实施例揭示的组播复制点执行的方法可以应用于处理器1902中，或者由处理器1902实现。处理器1902可能是一种集成电路芯片，具有信号的处理能力。在实现过程中，上述方法的各步骤可以通过处理器1902中的硬件的集成逻辑电路或者软件形式的指令完成。上述的处理器1902可以是通用处理器，包括中央处理器(Central Processing Unit，简称CPU)、网络处理器(Network Processor，简称NP)等；还可以是数字信号处理器(DSP)、专用集成电路(ASIC)、现成可编程门阵列(FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件。可以实现或者执行本发明实施例中的公开的各方法、步骤及逻辑框图。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。结合本发明实施例所公开的方法的步骤可以直接体现为硬件译码处理器执行完成，或者用译码处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存储器，闪存、只读存储器，可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质中。该存储介质位于存储器1903，处理器1902读取存储器1903中的信息，结合其硬件完成上述方法的步骤。
本发明实施例中，组播复制点1900从OTT直播代理服务器建立的组播组获取频道 的媒体数据并发送给OTT客户端，使得OTT客户端不需要再从OTT服务器直接获取频道的媒体数据，能够避免大量重复的直播流穿越骨干网，从而大大减少OTT服务器到城域网之间重复传输的报文，减少直播媒体数据对承载网的带宽占用。
可选地，作为一个实施例，处理器1902还用于：根据该OTT客户端发送的加入该指定频道的组播加入请求或媒体数据请求，将该OTT客户端加入该组播复制点的组播转发表，并向该OTT直播代理服务器请求加入该组播组。
可选地，作为另一个实施例，处理器1902还用于：根据该OTT客户端发送的退出该指定频道的请求，将该OTT客户端从该组播复制点的组播转发表中删除。
可选地，处理器1902还用于：根据该OTT直播代理服务器发送的频道加入指示，将OTT客户端加入到该指定频道的合法用户列表中，其中，该频道加入指示用于通知允许该OTT客户端加入该指定频道。
应理解，在根据该OTT直播代理服务器发送的频道加入指示，将OTT客户端加入到该指定频道的合法用户列表中之前，处理器1902还用于：通过通道接口1901接收该OTT直播代理服务器发送的频道加入指示。
进一步地，处理器1902还用于：当该组播复制点的组播转发表的OTT客户端为零时，向该OTT直播代理服务器发送组播退出请求，请求退出该组播组。
当然，应理解，上述方法还可以结合在一起使用。例如，处理器1902还用于：根据该OTT客户端发送的媒体数据请求，以及该指定频道的合法用户列表，对该OTT客户端加入该指定频道的权限进行鉴权，并在该OTT客户端通过鉴权后，向该OTT直播注入代理服务器请求加入该组播组。
此外，组播复制点1900还可执行图4的方法，并实现组播复制点在图5-11所示实施例的功能，本发明实施例在此不再赘述。
如图1所示，OTT***可包括：OTT服务器、OTT直播代理服务器、组播复制点和OTT客户端。其中，OTT服务器可以是图14、图15或图所示实施例中的OTT服务器，OTT直播代理服务器可以是图12、图13或图17所示实施例中的OTT直播代理服务器，组播复制点可以是图16或图19所示实施例中的组播复制点。OTT客户端可以是具备单播或组播接收能力的OTT客户端。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术 人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本发明的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的***、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的***、装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个***，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本发明各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。
所述功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本发明的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本发明各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(ROM，Read-Only Memory)、随机存取存储器(RAM，Random Access Memory)、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述，仅为本发明的具体实施方式，但本发明的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本发明揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本发明的保护范围之内。因此，本发明的保护范围应所述以权利要求的保护范围为准。

Claims (38)

  1. 一种在线服务OTT直播代理服务器，其特征在于，包括：
    组播资源分配单元，用于根据指定频道的组播资源分配指示及所述指定频道的媒体描述为所述指定频道分配组播资源，其中，所述组播资源分配指示用于通知所述OTT直播代理服务器为所述指定频道分配组播资源，所述指定频道的媒体描述包括所述指定频道的至少一种分辨率及所述至少一种分辨率的媒体数据所对应的统一资源定位符URL，所述组播资源包括所述指定频道对应的组播组或所述指定频道对应的组播组及所述至少一种分辨率对应的端口port；
    获取单元，用于根据所述指定频道的媒体描述通过单播方式从所述指定频道所属的OTT服务器获取所述至少一种分辨率对应的媒体数据；
    组播单元，用于将所述至少一种分辨率对应的媒体数据转换为组播媒体数据，并将所述组播媒体数据组播发送给所述组播组。
  2. 如权利要求1所述的OTT直播代理服务器，其特征在于，
    所述获取单元还用于从所述OTT服务器获取所述指定频道的媒体描述；或者
    所述指定频道的媒体描述是预先存储在所述OTT直播代理服务器中的。
  3. 如权利要求1或2所述的OTT直播代理服务器，其特征在于，其特征在于，
    所述组播资源分配指示是由所述OTT服务器发送的；或者
    所述组播资源分配指示是由所述OTT直播代理服务器所在的城域网的组播复制点发送的。
  4. 如权利要求1至3中任意一项所述的OTT直播代理服务器，其特征在于，还包括：
    转发单元，用于接收所述OTT服务器发送的频道加入指示，并将所述频道加入指示发送给所述OTT直播代理服务器所在的城域网的组播复制点，以使所述组播复制点将OTT客户端加入到所述指定频道的合法用户列表中，其中，所述频道加入指示用于通知允许所述OTT客户端加入所述指定频道。
  5. 如权利要求4所述的OTT直播代理服务器，其特征在于，还包括：
    注册单元，用于向所述OTT服务器注册所述OTT直播代理服务器所在的城域网的互联网协议IP网段及所述OTT直播代理服务器的IP地址。
  6. 如权利要求4或5所述的OTT直播代理服务器，其特征在于，所述组播资源分配单元还用于将所述分配的组播资源反馈给所述OTT服务器，以便所述OTT服务器将 所述组播资源发送给所述OTT客户端，使得所述OTT客户端能够加入所述组播组。
  7. 如权利要求4至6中任意一项所述的OTT直播代理服务器，其特征在于，所述组播资源分配单元还用于将所述指定频道与所述指定频道的组播组之间的对应关系发送给所述OTT直播代理服务器所在城域网内的组播复制点，以便所述组播复制点根据所述OTT客户端发送的加入所述指定频道的请求，确定所述指定频道对应的组播组。
  8. 如权利要求7所述的OTT直播代理服务器，其特征在于，所述组播资源分配单元还用于根据所述OTT客户端发送的加入所述指定频道的请求，将所述组播资源发送给所述OTT客户端，以便所述OTT客户端向组播复制点请求所述指定频道的媒体数据。
  9. 如权利要求1至8中任意一项所述的OTT直播代理服务器，其特征在于，还包括：组播组管理单元，用于：
    根据所述组播复制点的组播加入请求，将所述组播复制点加入所述组播组，并在所述组播组的组播转发表项添加所述组播复制点对应的出端口；或者
    根据所述组播复制点的组播退出请求，将所述组播复制点从所述组播组中删除，并在所述组播组的组播转发表项删除所述组播复制点对应的出端口。
  10. 如权利要求9所述的OTT直播代理服务器，其特征在于，所述组播资源分配单元还用于当所述组播组的组播转发表项中出端口数为零时，删除所述组播组的组播转发表项，并断开从所述OTT服务器下载所述指定频道的媒体数据的链接。
  11. 一种在线服务OTT服务器，其特征在于，包括：
    组播资源分配指示单元，用于向在所述OTT服务器中注册的OTT直播代理服务器发送组播资源分配指示，所述组播资源分配指示用于通知所述OTT直播代理服务器对指定频道分配组播资源；
    媒体描述管理单元，用于根据所述OTT直播代理服务器发送的获取所述指定频道的媒体描述的请求，将所述指定频道的媒体描述发送给所述OTT直播代理服务器，其中，所述指定频道的媒体描述包括所述指定频道的至少一种分辨率及所述至少一种分辨率的媒体数据所对应的统一资源定位符URL；
    媒体资源管理单元，用于根据所述OTT直播代理服务器对所述指定频道的媒体数据获取请求，将所述指定频道的至少一种分辨率的媒体数据以单播方式发送给所述OTT直播代理服务器。
  12. 如权利要求11所述的OTT服务器，其特征在于，还包括：
    注册单元，用于根据所述OTT直播代理服务器发送的注册请求，记录所述OTT直 播代理服务器所在的城域网的互联网协议IP网段及所述OTT直播代理服务器的IP地址，其中，所述注册请求携带所述OTT直播代理服务器所在的城域网的IP网段及所述OTT直播代理服务器的IP地址。
  13. 如权利要求11或12所述的OTT服务器，其特征在于，还包括：鉴权单元，用于根据所述OTT所在的城域网中的OTT客户端加入所述指定频道的请求，确定是否允许所述OTT客户端加入所述指定频道；
    所述组播资源分配指示单元具体用于当所述鉴权单元确定允许所述OTT客户端加入所述指定频道后，且所述OTT服务器上不存在所述OTT直播代理服务器发送的所述指定频道的组播资源时，向所述OTT直播代理服务器发送所述组播资源分配指示。
  14. 如权利要求13所述的OTT服务器，其特征在于，所述鉴权单元还用于在允许所述OTT客户端加入所述指定频道后，向所述OTT直播代理服务器发送频道加入指示，所述频道加入指示用于通知所述OTT直播代理服务器允许所述OTT客户端加入所述指定频道。
  15. 如权利要求13所述的OTT服务器，其特征在于，所述鉴权单元还用于将所述OTT直播代理服务器反馈的为所述指定频道分配的组播资源发送给所述OTT客户端，以便所述OTT客户端向组播复制点请求所述指定频道的媒体数据，其中，所述组播资源包括所述指定频道对应的组播组或所述指定频道对应的组播组及所述指定频道的至少一种分辨率对应的端口port。
  16. 如权利要求13所述的OTT服务器，其特征在于，还包括：
    重定位指示单元，用于根据所述OTT客户端加入所述指定频道的请求，以及所述指定频道的组播资源，指示所述OTT客户端将所述指定频道的加入请求重定位到所述OTT直播代理服务器上。
  17. 一种组播复制点，其特征在于，包括：
    组播管理单元，用于向所在城域网的OTT直播代理服务器请求加入所述OTT直播代理服务器为指定频道分配的组播组；
    媒体数据获取单元，用于接收所述OTT直播代理服务器以组播方式发送的所述指定频道的媒体数据；
    媒体数据管理单元，用于将所述指定频道的媒体数据以组播方式或单播方式发送给OTT客户端。
  18. 如权利要求17所述的组播复制点，其特征在于，还包括：
    权限管理单元，用于根据所在城域网的OTT直播代理服务器发送的频道加入指示，将所述OTT客户端加入到所述指定频道的合法用户列表中，其中，所述频道加入指示用于通知所述组播复制点允许所述OTT客户端加入所述指定频道。
  19. 如权利要求17所述的组播复制点，其特征在于，所述组播管理单元还用于：
    根据所述OTT客户端发送的加入所述指定频道的组播加入请求或媒体数据请求，将所述OTT客户端加入所述组播复制点的组播转发表，并向所述OTT直播代理服务器请求加入所述组播组；或者
    根据所述OTT客户端发送的退出所述指定频道的请求，将所述OTT客户端从所述组播复制点的组播转发表中删除。
  20. 一种直播媒体数据的方法，其特征在于，包括：
    根据指定频道的组播资源分配指示及所述指定频道的媒体描述为所述指定频道分配组播资源，其中，所述组播资源分配指示用于通知所述OTT直播代理服务器为所述指定频道分配组播资源，所述指定频道的媒体描述包括所述指定频道的至少一种分辨率及所述至少一种分辨率的媒体数据所对应的统一资源定位符URL，所述组播资源包括所述指定频道对应的组播组或所述指定频道对应的组播组及所述至少一种分辨率对应的端口port；
    根据所述指定频道的媒体描述通过单播方式从所述指定频道所属的OTT服务器获取所述至少一种分辨率对应的媒体数据；
    将所述至少一种分辨率对应的媒体数据转换为组播媒体数据，并将所述组播媒体数据组播发送给所述组播组。
  21. 如权利要求20所述的方法，其特征在于，
    在所述根据指定频道的组播资源分配指示及所述指定频道的媒体描述为所述指定频道分配组播资源之前，所述方法还包括：从所述OTT服务器获取所述指定频道的媒体描述；或者
    所述指定频道的媒体描述是预先存储在所述OTT直播代理服务器中的。
  22. 如权利要求20或21所述的方法，其特征在于，
    在所述根据指定频道的组播资源分配指示及所述指定频道的媒体描述为所述指定频道分配组播资源之前，所述方法还包括：接收所述指定频道的组播资源分配指示；
    其中，所述组播资源分配指示是由所述OTT服务器发送的；或者
    所述组播资源分配指示是由所述OTT直播代理服务器所在的城域网的组播复制点 发送的。
  23. 如权利要求20至22中任意一项所述的方法，其特征在于，还包括：
    接收所述OTT服务器发送的频道加入指示，并将所述频道加入指示发送给所述OTT直播代理服务器所在的城域网的组播复制点，以使所述组播复制点将OTT客户端加入到所述指定频道的合法用户列表中，其中，所述频道加入指示用于通知允许所述OTT客户端加入所述指定频道。
  24. 如权利要求23所述的方法，其特征在于，还包括：
    向所述OTT服务器注册所述OTT直播代理服务器所在的城域网的互联网协议IP网段及所述OTT直播代理服务器的IP地址。
  25. 如权利要求23或24所述的方法，其特征在于，还包括：
    将所述分配的组播资源反馈给所述OTT服务器，以便所述OTT服务器将所述组播资源发送给所述OTT客户端，使得所述OTT客户端能够加入所述组播组。
  26. 如权利要求24至25中任意一项所述的方法，还包括：
    将所述指定频道与所述指定频道的组播组之间的对应关系发送给所述OTT直播代理服务器所在城域网内的组播复制点，以便所述组播复制点根据所述OTT客户端发送的加入所述指定频道的请求，确定所述指定频道对应的组播组。
  27. 如权利要求26所述的方法，还包括：
    根据所述OTT客户端发送的加入所述指定频道的请求，将所述组播资源发送给所述OTT客户端，以便所述OTT客户端向组播复制点请求所述指定频道的媒体数据。
  28. 如权利要求20至27中任意一项所述的方法，还包括：
    根据所述组播复制点的组播加入请求，将所述组播复制点加入所述组播组，并在所述组播组的组播转发表项添加所述组播复制点对应的出端口；或者
    根据所述组播复制点的组播退出请求，将所述组播复制点从所述组播组中删除，并在所述组播组的组播转发表项删除所述组播复制点对应的出端口。
  29. 如权利要求28所述的方法，还包括：
    当所述组播组的组播转发表项中出端口数为零时，删除所述组播组的组播转发表项，并断开从所述OTT服务器下载所述指定频道的媒体数据的链接。
  30. 一种直播媒体数据的方法，其特征在于，包括：
    在线服务OTT服务器向在所述OTT服务器中注册的OTT直播代理服务器发送组播资源分配指示，所述组播资源分配指示用于通知所述OTT直播代理服务器对指定频 道分配组播资源；
    所述OTT服务器根据所述OTT直播代理服务器发送的获取所述指定频道的媒体描述的请求，将所述指定频道的媒体描述发送给所述OTT直播代理服务器，其中，所述指定频道的媒体描述包括所述指定频道的至少一种分辨率及所述至少一种分辨率的媒体数据所对应的统一资源定位符URL；
    所述OTT服务器根据所述OTT直播代理服务器对所述指定频道的媒体数据获取请求，将所述指定频道的至少一种分辨率的媒体数据以单播方式发送给所述OTT直播代理服务器。
  31. 如权利要求30所述的方法，其特征在于，还包括：
    所述OTT服务器根据所述OTT直播代理服务器发送的注册请求，记录所述OTT直播代理服务器所在的城域网的互联网协议IP网段及所述OTT直播代理服务器的IP地址，其中，所述注册请求携带所述OTT直播代理服务器所在的城域网的IP网段及所述OTT直播代理服务器的IP地址。
  32. 如权利要求30或31所述的方法，其特征在于，还包括：
    所述OTT服务器根据所述OTT所在的城域网中的OTT客户端加入所述指定频道的请求，确定是否允许所述OTT客户端加入所述指定频道；
    所述OTT服务器向在所述OTT服务器中注册的OTT直播代理服务器发送组播资源分配指示包括：当所述OTT服务器确定允许所述OTT客户端加入所述指定频道后，且所述OTT服务器上不存在所述OTT直播代理服务器发送的所述指定频道的组播资源时，所述OTT服务器向所述OTT直播代理服务器发送所述组播资源分配指示。
  33. 如权利要求32所述的方法，其特征在于，还包括：
    所述OTT服务器在允许所述OTT客户端加入所述指定频道后，向所述OTT直播代理服务器发送频道加入指示，所述频道加入指示用于通知所述OTT直播代理服务器允许所述OTT客户端加入所述指定频道。
  34. 如权利要求32所述的方法，其特征在于，还包括：
    所述OTT服务器将所述OTT直播代理服务器反馈的为所述指定频道分配的组播资源发送给所述OTT客户端，以便所述OTT客户端向组播复制点请求所述指定频道的媒体数据，其中，所述组播资源包括所述指定频道对应的组播组或所述指定频道对应的组播组及所述指定频道的至少一种分辨率对应的端口port。
  35. 如权利要求32所述的方法，其特征在于，还包括：
    所述OTT服务器根据所述OTT客户端加入所述指定频道的请求，以及所述指定频道的组播资源，指示所述OTT客户端将所述指定频道的加入请求重定位到所述OTT直播代理服务器上。
  36. 一种直播媒体数据的方法，其特征在于，包括：
    向所在城域网的在线服务OTT直播代理服务器请求加入所述OTT直播代理服务器为指定频道分配的组播组；
    接收所述OTT直播代理服务器以组播方式发送的所述指定频道的媒体数据；
    将所述指定频道的媒体数据以组播方式或单播方式发送给OTT客户端。
  37. 如权利要求36所述的方法，其特征在于，还包括：
    根据所述OTT直播代理服务器发送的频道加入指示，将所述OTT客户端加入到所述指定频道的合法用户列表中，其中，所述频道加入指示用于通知允许所述OTT客户端加入所述指定频道。
  38. 如权利要求36所述的方法，其特征在于，还包括：
    根据所述OTT客户端发送的加入所述指定频道的组播加入请求或媒体数据请求，将所述OTT客户端加入所述组播复制点的组播转发表，并向所述OTT直播代理服务器请求加入所述组播组；或者
    根据所述OTT客户端发送的退出所述指定频道的请求，将所述OTT客户端从所述组播复制点的组播转发表中删除。
PCT/CN2015/099546 2015-05-12 2015-12-29 直播媒体数据的方法、设备和*** WO2016180029A1 (zh)

Priority Applications (5)

Application Number Priority Date Filing Date Title
ES15891722T ES2732226T3 (es) 2015-05-12 2015-12-29 Método, dispositivo y sistema para datos de contenido multimedia en directo
SG11201709036XA SG11201709036XA (en) 2015-05-12 2015-12-29 Media data live broadcast method, device, and system
EP15891722.9A EP3285430B1 (en) 2015-05-12 2015-12-29 Method, device and system for live media data
CA2985217A CA2985217C (en) 2015-05-12 2015-12-29 Media data live broadcast method, device, and system
US15/809,074 US10205971B2 (en) 2015-05-12 2017-11-10 Media data live broadcast method, device, and system

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201510240782.0A CN106302566B (zh) 2015-05-12 2015-05-12 直播媒体数据的方法、设备和***
CN201510240782.0 2015-05-12

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US15/809,074 Continuation US10205971B2 (en) 2015-05-12 2017-11-10 Media data live broadcast method, device, and system

Publications (1)

Publication Number Publication Date
WO2016180029A1 true WO2016180029A1 (zh) 2016-11-17

Family

ID=57248596

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2015/099546 WO2016180029A1 (zh) 2015-05-12 2015-12-29 直播媒体数据的方法、设备和***

Country Status (7)

Country Link
US (1) US10205971B2 (zh)
EP (1) EP3285430B1 (zh)
CN (1) CN106302566B (zh)
CA (1) CA2985217C (zh)
ES (1) ES2732226T3 (zh)
SG (1) SG11201709036XA (zh)
WO (1) WO2016180029A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018121584A1 (zh) * 2016-12-30 2018-07-05 中兴通讯股份有限公司 一种数据流传输方法、装置、相关设备及存储介质
EP3451609A1 (en) * 2017-08-31 2019-03-06 Wipro Limited A method and a system to deliver multimedia content in a downstream network

Families Citing this family (16)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105049954B (zh) * 2015-07-02 2020-07-10 中兴通讯股份有限公司 Ott媒体的组播传输方法、装置及***
CN105119778B (zh) * 2015-09-09 2018-09-07 华为技术有限公司 测量时延的方法和设备
US20180020251A1 (en) * 2016-07-15 2018-01-18 Comcast Cable Communications, Llc Programming Insight And Analysis
CN108632646B (zh) * 2017-03-20 2021-12-10 腾讯科技（深圳）有限公司 一种视频直播方法、装置及服务器
CN108668178B (zh) * 2017-03-31 2020-12-04 华为技术有限公司 一种组播实现方法及相关网络设备
CN109963203B (zh) * 2017-12-25 2021-12-07 ***通信集团福建有限公司 视频流转换及自适应切换方法及装置、设备及介质
CN108271083A (zh) * 2017-12-26 2018-07-10 中兴通讯股份有限公司 一种媒体处理架构及方法
CA3126006A1 (en) 2019-01-07 2020-07-16 Arris Enterprises Llc Stateful igmp fastleave
CN111836059B (zh) * 2019-04-23 2022-03-29 华为技术有限公司 一种媒体流发送方法、装置和设备
CN111835697B (zh) * 2019-04-23 2021-10-01 华为技术有限公司 一种媒体流发送方法、装置、设备和***
CN112822499B (zh) * 2019-11-15 2023-03-07 北京金山云网络技术有限公司 用于网络直播的数据通信方法、装置、***及电子设备
CN111343469B (zh) * 2020-02-19 2021-09-28 腾讯科技（深圳）有限公司 一种数据处理方法、装置、电子设备及存储介质
CN111669610B (zh) * 2020-05-27 2022-08-05 北京奇艺世纪科技有限公司 直播视频的传输方法、***、装置、服务器、电子设备及存储介质
FR3128842A1 (fr) * 2021-10-28 2023-05-05 Orange procédé de gestion de l’accès à une contenu a lecture d’un contenu multimédia.
CN114339439A (zh) * 2021-12-31 2022-04-12 上海掌门科技有限公司 一种基于社交群聊的直播方法与设备
CN115941795A (zh) * 2022-03-15 2023-04-07 中移***集成有限公司 数据传输方法、装置、电子设备及存储介质

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101001197A (zh) * 2006-12-31 2007-07-18 华为技术有限公司 媒体流传输方法、***及相关设备
CN101340305A (zh) * 2008-08-07 2009-01-07 中兴通讯股份有限公司 一种源特定的组播方法、***及其接入设备
CN103841453A (zh) * 2014-03-13 2014-06-04 烽火通信科技股份有限公司 Iptv非智能机顶盒实现ott播放的方法
US20150049762A1 (en) * 2013-08-13 2015-02-19 Imvision Software Technologies Ltd. Method and system for self-detection and efficient transmission of real-time popular recorded over-the-top streams over network communications

Family Cites Families (25)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7028071B1 (en) * 2000-01-28 2006-04-11 Bycast Inc. Content distribution system for generating content streams to suit different users and facilitating e-commerce transactions using broadcast content metadata
US7656908B1 (en) * 2005-09-30 2010-02-02 At&T Corp. System and method for delivering content in a unicast/multicast manner
JP4428934B2 (ja) * 2003-03-24 2010-03-10 富士通株式会社 映像選択サーバ、映像配信システム、および映像選択方法
US8054849B2 (en) * 2005-05-27 2011-11-08 At&T Intellectual Property I, L.P. System and method of managing video content streams
US7817672B2 (en) * 2006-02-01 2010-10-19 Bigband Networks Inc. Method and device for providing programs to multiple end user devices
US8627390B2 (en) * 2006-02-01 2014-01-07 Arris Solutions, Inc. Method and device for providing programs to multiple end user devices
US20070280230A1 (en) * 2006-05-31 2007-12-06 Motorola, Inc Method and system for service discovery across a wide area network
WO2008111921A1 (en) * 2007-03-15 2008-09-18 Maindata, Spol. S R.O. The way of bandwidth efficient distribution of multiple transport streams with partially same content
CN101060617B (zh) * 2007-05-22 2010-07-28 华为技术有限公司 一种视频点播控制方法、客户端设备和切换控制装置
US8549575B2 (en) * 2008-04-30 2013-10-01 At&T Intellectual Property I, L.P. Dynamic synchronization of media streams within a social network
US8752100B2 (en) * 2008-08-29 2014-06-10 At&T Intellectual Property Ii, Lp Systems and methods for distributing video on demand
US20120023533A1 (en) * 2010-07-22 2012-01-26 Alcatel-Lucent Usa Inc. Method and apparatus for delivery of internet protocol television service
US8826349B2 (en) * 2011-02-01 2014-09-02 Verizon Patent And Licensing Inc. Multicast adaptive stream switching for delivery of over the top video content
WO2012148442A1 (en) * 2011-04-29 2012-11-01 Intel Corporation Techniques to manage energy savings for interoperable radio access technology networks
EP2717540B1 (en) * 2011-06-30 2015-04-15 Huawei Technologies Co., Ltd. Method, apparatus, and system for transmitting media data based on over the top (ott)
US8887222B2 (en) * 2011-09-14 2014-11-11 Qualcomm Incorporated Multicasting in a wireless display system
WO2013043918A1 (en) * 2011-09-21 2013-03-28 General Instrument Corporation Adaptive streaming to multicast and constrained-fidelity constant bit rate encoding
US9225762B2 (en) * 2011-11-17 2015-12-29 Google Technology Holdings LLC Method and apparatus for network based adaptive streaming
CN104066125B (zh) * 2013-03-19 2018-03-09 华为技术有限公司 减少业务时延的方法及控制器
US9374410B2 (en) * 2013-07-24 2016-06-21 Imvision Software Technologies Ltd. System and method for seamless switchover between unicast and multicast sources of over-the-top streams
WO2015013595A2 (en) * 2013-07-25 2015-01-29 Imvision Software Technologies Ltd. Method and apparatus for efficient transmission of unmanaged over-the-top streams over cellular communication networks
US20150036526A1 (en) * 2013-07-30 2015-02-05 Imvision Software Technologies Ltd. Method and system for efficient transmission of over-the-top streams over fixed-line networks
US20150046568A1 (en) * 2013-08-11 2015-02-12 Imvision Software Technologies Ltd. Method and system for playing multicast over-the-top (ott) content streams
WO2015023655A1 (en) * 2013-08-12 2015-02-19 Imvision Software Technologies Ltd. Method and system for managing the delivery of over-the-top streams
US9674564B2 (en) * 2014-12-15 2017-06-06 Arris Enterprises, Inc. System and methods for multicast delivery of internet protocol video content

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101001197A (zh) * 2006-12-31 2007-07-18 华为技术有限公司 媒体流传输方法、***及相关设备
CN101340305A (zh) * 2008-08-07 2009-01-07 中兴通讯股份有限公司 一种源特定的组播方法、***及其接入设备
US20150049762A1 (en) * 2013-08-13 2015-02-19 Imvision Software Technologies Ltd. Method and system for self-detection and efficient transmission of real-time popular recorded over-the-top streams over network communications
CN103841453A (zh) * 2014-03-13 2014-06-04 烽火通信科技股份有限公司 Iptv非智能机顶盒实现ott播放的方法

Non-Patent Citations (1)

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

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018121584A1 (zh) * 2016-12-30 2018-07-05 中兴通讯股份有限公司 一种数据流传输方法、装置、相关设备及存储介质
EP3451609A1 (en) * 2017-08-31 2019-03-06 Wipro Limited A method and a system to deliver multimedia content in a downstream network
US10701126B2 (en) 2017-08-31 2020-06-30 Wipro Limited Method and a system to deliver multimedia content in a downstream network

Also Published As

Publication number Publication date
EP3285430B1 (en) 2019-05-08
US20180077431A1 (en) 2018-03-15
CN106302566A (zh) 2017-01-04
US10205971B2 (en) 2019-02-12
EP3285430A1 (en) 2018-02-21
ES2732226T3 (es) 2019-11-21
CN106302566B (zh) 2019-07-23
CA2985217A1 (en) 2016-11-17
EP3285430A4 (en) 2018-03-21
CA2985217C (en) 2020-10-20
SG11201709036XA (en) 2017-12-28

Similar Documents

Publication Publication Date Title
WO2016180029A1 (zh) 直播媒体数据的方法、设备和***
JP5930429B2 (ja) ファイル配信方式を使用したｉｐブロードキャストストリーミングサービスの配信
US9380079B2 (en) Content multicasting
US20130114597A1 (en) Proxy server, relay method, communication system, relay control program, and recording medium
US11277456B2 (en) System and method for delivering an audio-visual con tent to a client device
US20180034875A1 (en) Placeshifting of adaptive media streams
CN107948762B (zh) 直播视频的传输方法、装置和***
US20110302604A1 (en) Methods and arrangements for system providing media via multicast distribution
JP2010504652A (ja) ビデオネットワークを管理する方法及びシステム
WO2011017982A1 (zh) 媒体业务处理***、方法及终端
CN106817629B (zh) 一种媒体信息传输方法、装置及***
KR20190015521A (ko) 인기 있는 라이브 방송 비디오를 결정하는 방법 및 디바이스
US20220345508A1 (en) Content delivery - setting the unicast rate
WO2013127423A1 (en) Apparatus and method for streaming content
US8295200B2 (en) Discovering multicast routing capability of an access network
KR101375182B1 (ko) 수신기/디코더 연결의 관리를 위한 메커니즘
KR100621328B1 (ko) 멀티캐스팅에 관한 정보를 이용한 멀티미디어 스트리밍서비스 제공 방법 및 시스템
US20110093611A1 (en) Network unit, a central distribution control unit and a computer program product
WO2024081765A1 (en) Systems and methods for capturing and distributing a live audio or multi-media stream of a live event in real-time
Haems et al. Enabling adaptive and reliable video delivery over hybrid unicast/broadcast networks
KR20110034902A (ko) 스케일러블 비디오 부호화에서 인터넷 그룹 관리 프로토콜 보고 메시지를 억제하기 위한 네트워크 장치, 보고 메시지 억제 방법, 보고 메시지 크기 감소 방법 및 보고 메시지 처리 방법
JP2017092580A (ja) 放送受信装置、放送受信方法および放送受信プログラム
WO2013152489A1 (zh) 一种跨域提供直播节目的***及方法

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

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 11201709036X

Country of ref document: SG

ENP Entry into the national phase

Ref document number: 2985217

Country of ref document: CA

NENP Non-entry into the national phase

Ref country code: DE