WO2018068727A1 - 直播视频的传输方法、装置和系统 - Google Patents
直播视频的传输方法、装置和系统 Download PDFInfo
- Publication number
- WO2018068727A1 WO2018068727A1 PCT/CN2017/105693 CN2017105693W WO2018068727A1 WO 2018068727 A1 WO2018068727 A1 WO 2018068727A1 CN 2017105693 W CN2017105693 W CN 2017105693W WO 2018068727 A1 WO2018068727 A1 WO 2018068727A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- live
- multicast
- video data
- live channel
- address
- Prior art date
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
- H04L65/60—Network streaming of media packets
- H04L65/61—Network streaming of media packets for supporting one-way streaming services, e.g. Internet radio
-
- 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/61—Network streaming of media packets for supporting one-way streaming services, e.g. Internet radio
- H04L65/612—Network streaming of media packets for supporting one-way streaming services, e.g. Internet radio for unicast
-
- 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/765—Media network packet handling intermediate
-
- 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/80—Responding to QoS
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/16—Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]
-
- 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/238—Interfacing the downstream path of the transmission network, e.g. adapting the transmission rate of a video stream to network bandwidth; Processing of multiplex streams
- H04N21/2381—Adapting the multiplex stream to a specific network, e.g. an Internet Protocol [IP] network
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/20—Servers specifically adapted for the distribution of content, e.g. VOD servers; Operations thereof
- H04N21/25—Management operations performed by the server for facilitating the content distribution or administrating data related to end-users or client devices, e.g. end-user or client device authentication, learning user preferences for recommending movies
- H04N21/266—Channel or content management, e.g. generation and management of keys and entitlement messages in a conditional access system, merging a VOD unicast channel into a multicast channel
- H04N21/26616—Channel or content management, e.g. generation and management of keys and entitlement messages in a conditional access system, merging a VOD unicast channel into a multicast channel for merging a unicast channel into a multicast channel, e.g. in a VOD application, when a client served by unicast channel catches up a multicast channel to save bandwidth
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/60—Network structure or processes for video distribution between server and client or between remote clients; Control signalling between clients, server and network components; Transmission of management data between server and client, e.g. sending from server to client commands for recording incoming content stream; Communication details between server and client
- H04N21/63—Control signaling related to video distribution between client, server and network components; Network processes for video distribution between server and clients or between remote clients, e.g. transmitting basic layer and enhancement layers over different transmission paths, setting up a peer-to-peer communication via Internet between remote STB's; Communication protocols; Addressing
- H04N21/633—Control signals issued by server directed to the network components or client
-
- 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/637—Control signals issued by the client directed to the server or network components
- H04N21/6373—Control signals issued by the client directed to the server or network components for rate control, e.g. request to the server to modify its transmission rate
-
- 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/64—Addressing
- H04N21/6408—Unicasting
-
- 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
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/60—Network structure or processes for video distribution between server and client or between remote clients; Control signalling between clients, server and network components; Transmission of management data between server and client, e.g. sending from server to client commands for recording incoming content stream; Communication details between server and client
- H04N21/63—Control signaling related to video distribution between client, server and network components; Network processes for video distribution between server and clients or between remote clients, e.g. transmitting basic layer and enhancement layers over different transmission paths, setting up a peer-to-peer communication via Internet between remote STB's; Communication protocols; Addressing
- H04N21/643—Communication protocols
- H04N21/6437—Real-time Transport Protocol [RTP]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/80—Generation or processing of content or additional data by content creator independently of the distribution process; Content per se
- H04N21/83—Generation or processing of protective or descriptive data associated with content; Content structuring
- H04N21/84—Generation or processing of descriptive data, e.g. content descriptors
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/80—Generation or processing of content or additional data by content creator independently of the distribution process; Content per se
- H04N21/85—Assembly of content; Generation of multimedia applications
- H04N21/858—Linking data to content, e.g. by linking an URL to a video object, by creating a hotspot
- H04N21/8586—Linking data to content, e.g. by linking an URL to a video object, by creating a hotspot by using a URL
Definitions
- the embodiments of the present invention relate to the Internet technology, and in particular, to a method, an apparatus, and a system for transmitting live video.
- over-the-top (English: over-the-top, OTT) video sites provide live video services.
- live video is characterized by users watching the same channel.
- Duplicate content that is, for users who watch live channels, a large number of duplicate data packets are transmitted in the network, which occupies a large amount of network bandwidth, and also brings a large amount of network settlement fees to operators.
- a multicast bearer OTT technology is proposed to reduce network traffic and reduce the load of the video source server through the multicast bearer network.
- Unicast to multicast (English: unicast to multicast, U2M) device obtains video data from the video source server in unicast mode, and then multicasts the video data to multiple multicast to unicast (English: multicast to unicast)
- the M2U device's central processing unit (English: central processing unit, CPU for short) receives the multicast group and corresponding channel information notified by the live management platform, joins the multicast group, and receives multicast packets.
- APP application, abbreviation: APP
- HTTP Hyper Text Transfer Protocol
- the process of converting the video data into the HTTP packet by the M2U device needs to be implemented by the CPU.
- the CPU has limited ability to process HTTP traffic.
- the live video service cannot be implemented.
- the embodiment of the invention provides a method, a device and a system for transmitting live video.
- the process for re-converting video data into HTTP packets by the M2U device needs to be implemented by the CPU.
- the CPU has limited ability to process HTTP traffic. When there are many users, the problem of live video service cannot be realized.
- a first aspect of the present invention provides a method for transmitting a live video, which is applied to an M2U device, and the method includes:
- UDP User Datagram Protocol
- the UDP request includes a live channel identifier, and is used to request video data of a live channel corresponding to the live channel identifier;
- the live channel identifier is generally a multicast address or a uniform resource locator (English: Uniform)
- the Resource Locator (referred to as the URL)
- the M2U device obtains the video data of the live channel of the UDP protocol corresponding to the live channel identifier from the U2M multicast according to the live channel identifier in the UDP request sent by the client, and does not require the CPU to perform protocol conversion.
- the video data is directly sent to the client in UDP unicast mode through hardware forwarding, thereby effectively improving the throughput of the M2U device.
- the sending, by using the source IP address and the source port, the video data to the client in UDP unicast mode includes:
- the M2U device obtains the multicast packet in the video data, and the destination IP address of the multicast packet is modified to the source IP address of the client through the hardware forwarding module, and the destination port is modified to be the source port of the client sending the DUP request.
- the video data is directly forwarded to the client for parsing and playing in a UDP unicast message.
- the CPU does not need to perform data protocol conversion. When there are many users, the time-frequency live broadcast can be realized, and the throughput of the M2U device is improved.
- the live channel identifier includes a multicast address
- a specific implementation manner of the M2U device acquiring the video data of the live channel corresponding to the live channel identifier includes:
- the live channel identifier includes a multicast address
- the method further includes: forwarding the multicast to the unicast before receiving the user datagram protocol UDP request sent by the client.
- the U2M device sends a multicast join message, where the multicast join message is used to request video data of multiple live channels corresponding to multiple multicast addresses;
- the M2U device obtains the video data of the live channel corresponding to the live channel identifier, and obtains the live broadcast corresponding to the multicast address from the video data of the multiple live channels according to the multicast address. Video data for the channel.
- the foregoing solution provides a method for the M2U device to obtain the video data of the live channel corresponding to the multicast address, and the other is to directly send the multicast join message including the multicast address, so that the U2M device will correspond to the live channel according to the multicast address.
- the video data is returned to the M2U device; the other method is to send a multicast join message including multiple multicast addresses, and simultaneously acquire data of the live channel corresponding to the multiple multicast addresses, and the M2U device according to the request sent by the client.
- the multicast address in the medium obtains video data corresponding to the multicast address from the local video data.
- the live channel identifier includes a URL
- the acquiring the video data of the live channel corresponding to the live channel identifier includes:
- the live channel identifier includes a URL
- the user datagram protocol UDP sent by the receiving client is received.
- the method further includes:
- the acquiring the video data of the live channel corresponding to the live channel identifier including:
- the obtaining the multicast address corresponding to the URL according to the URL includes:
- the UDP request further includes a user identifier.
- the method further includes: determining a user corresponding to the user identifier. Whether it has the right to view the live channel corresponding to the live channel identifier,
- the step of acquiring the video data of the live channel corresponding to the live channel identifier is performed.
- the meaning of the solution is that before the video data of the live channel corresponding to the multicast address is obtained, whether the user logged in to the client has the right to view the live channel, if the user does not have the right to view the live channel, If the user does not respond to the UDP request, if the user has the right to watch the live channel, the video data is acquired according to any of the above methods.
- the determining whether the user corresponding to the user identifier has the right to view the live channel corresponding to the live channel identifier includes:
- the verification result is used to indicate that the user identifier corresponds to Whether the user has the right to view the live channel corresponding to the live channel identifier;
- the verification result is used to indicate whether the user corresponding to the user identifier is The right to view the channel corresponding to the live channel identifier.
- a second aspect of the present invention provides a method for transmitting a live video, which is applied to a client, and the method includes:
- the UDP request includes a live channel identifier, and is used to request video data of a live channel corresponding to the live channel identifier;
- the M2U device Receiving, by the M2U device, the video data of the live channel; the video data is obtained by the M2U device according to the live channel identifier; the video data is carried in a UDP unicast packet;
- the client in the solution After receiving the UDP packet unicast by the M2U device, the client in the solution performs parsing processing to obtain the video of the live channel and plays the video.
- the UDP request further includes: authorization information; and/or user identification and verification information.
- An M2U device includes:
- a receiving module configured to receive a UDP request sent by the client, where the UDP request includes a live channel identifier, and is used to request video data of a live channel corresponding to the live channel identifier;
- a processing module configured to acquire video data of a live channel corresponding to the live channel identifier
- the processing module is further configured to obtain a source IP address and a source port included in the UDP request, where the source IP address is an IP address of the client, and the source port sends the UDP to the client Requested port;
- a sending module configured to send the video data to the client in a UDP unicast manner according to the source IP address and the source port.
- the sending module is specifically configured to:
- the live channel identifier includes a multicast address
- the sending module is further configured to send a multicast join message to the U2M device corresponding to the multicast address, where the multicast join message includes the multicast address ;
- the receiving module is further configured to receive the video data of a live channel corresponding to the multicast address returned by the U2M device.
- the live channel identifier includes a multicast address
- the receiving module receives the UDP request sent by the client
- the sending module is further configured to send a multicast join message to the U2M device, where the multicast join message is used to request video data of multiple live channels corresponding to multiple multicast addresses;
- the receiving module is further configured to receive video data of the multiple live channels sent by the U2M device;
- the processing module is configured to acquire, according to the multicast address, video data of a live channel corresponding to the multicast address from video data of the multiple live channels.
- the live channel identifier includes a URL
- the processing module is further configured to acquire, according to the URL, a multicast address corresponding to the URL;
- the sending module is further configured to send a multicast join message to the U2M device corresponding to the multicast address, where the multicast join message includes the multicast address;
- the receiving module is further configured to receive the video data of a live channel corresponding to the multicast address returned by the U2M device.
- the live channel identifier includes a URL
- the sending module is further configured to send a multicast join message to the U2M device, where the multicast join message is used to request Video data of multiple live channels corresponding to multiple multicast addresses;
- the receiving module is further configured to receive video data of the multiple live channels sent by the U2M device;
- the processing module is specifically configured to:
- the processing module is further configured to query a correspondence between the pre-acquired multicast address and the URL, and obtain a multicast address corresponding to the URL.
- the sending module is further configured to send a multicast address query message including the URL to the live broadcast management platform, where the receiving module is further configured to receive a multicast address corresponding to the URL returned by the live broadcast management platform.
- the UDP request further includes a user identifier
- the processing module is further configured to determine whether the user corresponding to the user identifier has the right to view the live channel corresponding to the live channel identifier
- the step of acquiring the video data of the live channel corresponding to the live channel identifier is performed.
- the sending module is further configured to send the user identifier and the verification information carried in the UDP request and the live channel identifier to the live management platform for verification;
- the receiving module is further configured to receive the live management platform and return The verification result is used to indicate whether the user corresponding to the user identifier has the right to view the live channel corresponding to the live channel identifier;
- the sending module is further configured to send the authorization information carried by the UDP request and the live channel identifier to the live broadcast management platform for verification; the receiving module is further configured to receive the verification result returned by the live broadcast management platform, where The verification result is used to indicate whether the user corresponding to the user identifier has the right to view the channel corresponding to the live channel identifier.
- a fourth aspect of the present invention provides a client, including:
- a sending module configured to send a UDP request to the M2U device, where the UDP request includes a live channel identifier, and is used to request video data of a live channel corresponding to the live channel identifier;
- a receiving module configured to receive video data of the live channel sent by the M2U device; the video data is obtained by the M2U device according to the live channel identifier; the video data is carried in a UDP unicast packet;
- the processing module is configured to parse the UDP unicast message to play the video of the live channel.
- the UDP request sent by the sending module further includes: authorization information; and/or user identifier and verification information.
- a fifth aspect of the present invention provides an M2U device, including: a memory for storing program code and configuration information, a processor, and a hardware forwarding module;
- the processor is used to:
- the UDP request includes a live channel identifier, and is used to request video data of a live channel corresponding to the live channel identifier;
- the hardware forwarding module is configured to send the video data to the client in UDP unicast mode according to the source IP address and the source port.
- the hardware forwarding module is specifically configured to:
- the live channel identifier includes a multicast address
- the processor is further configured to send a multicast join message to the U2M device corresponding to the multicast address, where the multicast join message includes the multicast address ;
- the hardware forwarding module is further configured to receive the video data of a live channel corresponding to the multicast address returned by the U2M device.
- the live channel identifier includes a multicast address
- the processor is further configured to send a multicast join message to the U2M device, where the multicast join message is used to request multiple live channels corresponding to multiple multicast addresses.
- Video data ;
- the processor is further configured to acquire, according to the multicast address, video data of a live channel corresponding to the multicast address from video data of the multiple live channels.
- the live channel identifier includes a URL
- the processor is further configured to:
- the live channel identifier includes a URL
- the processor before the processor receives the user datagram protocol UDP request sent by the client, the processor is further configured to:
- the processor is specifically used to:
- the processor is specifically configured to:
- the UDP request further includes a user identifier.
- the processor is further configured to determine whether the user corresponding to the user identifier has a viewing location. The rights of the live channel corresponding to the live channel identifier,
- the step of acquiring the video data of the live channel corresponding to the live channel identifier is performed.
- the processor is further configured to send the user identifier and the verification information carried in the UDP request and the live channel identifier to the live management platform for verification, and receive the verification result returned by the live management platform;
- the verification result is used to indicate whether the user corresponding to the user identifier has the right to view the live channel corresponding to the live channel identifier;
- the processor is further configured to send the authorization information carried by the UDP request and the live channel identifier to the live management platform for verification, and receive the verification result returned by the live management platform; the verification result is used to indicate the location Whether the user corresponding to the user identifier has the right to view the channel corresponding to the live channel identifier.
- a sixth aspect of the present invention provides a user equipment, including: a memory, a transceiver, and a processor for storing program codes and configuration information;
- the transceiver is configured to send a user datagram protocol UDP request to the M2U device, where the UDP request includes a group live channel identifier, and is used to request video data of a live channel corresponding to the live channel identifier;
- the transceiver is further configured to receive video data of the live channel sent by the M2U device; the video data is obtained by the M2U device according to the live channel identifier; and the video data is carried in a UDP unicast packet. ;
- the processor is configured to parse the UDP unicast message to play the video of the live channel.
- the optional UDP request sent by the transceiver further includes: authorization information; and/or user identification and verification information.
- a seventh aspect of the present invention provides a live video transmission system, including: the M2U device provided by any one of the third aspects, and the client provided by any one of the fourth aspects.
- system further includes a U2M device; the U2M device is configured to:
- the M2U device receives a UDP request, which is sent by the client, including a live channel identifier, and is used to request video data corresponding to the live channel of the live channel identifier, and then obtains the live channel identifier.
- the video data of the corresponding live channel the M2U device obtains the source IP address of the client and the source port of the client sending the UDP request according to the UDP request, and sends the video data to the client by using UDP unicast according to the source IP address and the source port.
- the CPU does not need to perform protocol conversion on the video data, and directly transmits the video data to the UDP mode through hardware forwarding through the source IP address and source port of the packet, and directly transmits the video data by using hardware forwarding, which can effectively improve.
- the throughput of the M2U device can also implement live video services when there are many users.
- FIG. 1 is an architectural diagram of a live video transmission system of the present invention
- Embodiment 1 is a flowchart of Embodiment 1 of a method for transmitting a live video according to the present invention
- Embodiment 3 is an interaction flowchart of Embodiment 2 of a method for transmitting a live video according to the present invention
- FIG. 4 is a schematic diagram of interaction of a live video transmission system according to the present invention.
- 5a is an interaction flowchart of an example of a method for transmitting a live video according to the present invention
- Figure 5b is a schematic diagram of a transmission protocol
- FIG. 6 is a schematic structural diagram of an embodiment of an M2U device according to the present invention.
- FIG. 7 is a schematic structural diagram of an embodiment of a client according to the present invention.
- FIG. 8 is a schematic structural diagram of an embodiment of an M2U device entity according to the present invention.
- FIG. 9 is a schematic structural diagram of an embodiment of a user equipment entity according to the present invention.
- the video live broadcast system mainly includes a client on the user side, for example, a live application (English: application, referred to as APP), an M2U device, and a U2M.
- APP live application
- M2U device M2U device
- U2M U2M device
- the U2M device obtains video data from the OTT server in a unicast manner, and then distributes the video data to different M2U devices through multicast mode (each U2M device connects multiple M2U devices), and the M2U device The video data is then sent to the client to play to the user according to the request of the client.
- the physical implementation of the M2U device in the network may be an independent server, a router service board, a router forwarding board, etc., and the client may run on a terminal device such as a user's mobile phone, computer, or tablet computer.
- the system further includes a live management platform for verifying the live permission of the user.
- the forwarding function of the forwarding board is very high.
- This solution proposes the forwarding function of the forwarding board to implement the M2U function.
- the basic idea is that after the hardware forwarding module receives the multicast packet, Change the destination Internet protocol (English: Internet Protocol, IP address) of the multicast packet to the IP address of the client, and change the destination port of the multicast packet to the port of the client.
- Change the destination Internet protocol English: Internet Protocol, IP address
- FIG. 2 is a flowchart of Embodiment 1 of a method for transmitting a live video according to the present invention.
- the live video transmission method is mainly applied to an M2U device, and specifically includes The following steps:
- S101 Receive a UDP request sent by the client; the UDP request includes a live channel identifier, and is used to request video data of the live channel corresponding to the live channel identifier.
- the client determines that the video data of a live channel needs to be obtained through the operation of the user, and sends a UDP request to the M2U device, where the UDP request includes a live channel identifier, and the live channel identifier may be a multicast of the live channel.
- the address or URL so that the M2U device can obtain corresponding video data according to the multicast address or the URL.
- the M2U device needs to obtain the multicast address corresponding to the URL according to the correspondence between the URL and the multicast address, that is, the M2U device first queries the pre-acquisition.
- the multicast address and the URL are associated with each other, and the query obtains the multicast address corresponding to the URL; or the M2U device sends the URL to the live broadcast management platform, and the multicast management platform queries the multicast address corresponding to the URL, and then according to the The multicast address acquires corresponding video data.
- the UDP request further includes: authorization information; and/or user identification and verification information.
- S102 Obtain video data of a live channel corresponding to the live channel identifier.
- the specific implementation manner of the M2U device acquiring the video data of the live channel corresponding to the multicast address includes:
- the video data can be obtained in the following two ways.
- the M2U device sends a multicast join message to the U2M device corresponding to the multicast address.
- the multicast join message includes the multicast address, and receives the video data of the live channel corresponding to the multicast address returned by the U2M device.
- the M2U device directly sends a multicast join message including a multicast address to the U2M device, so that the U2M device returns the video data of the corresponding live channel to the M2U device according to the multicast address, that is, the U2M device needs to be based on the multicast address.
- the video data corresponding to the multicast address is queried from the video data that is drained to the local device, and then returned to the M2U device.
- the M2U device sends a multicast join message to the U2M device before receiving the UDP request sent by the client, where the multicast join message is used to request video data of multiple live channels corresponding to multiple multicast addresses.
- the meaning is that the M2U device sends a multicast join message including multiple multicast addresses to the U2M device, and acquires data of the live channel corresponding to the multiple multicast addresses, and the M2U device obtains the multicast address in the request sent by the client.
- the video data corresponding to the multicast address is obtained from the local video data.
- the M2U obtains the corresponding multicast address according to the URL before obtaining the video data in the above two manners.
- the specific manner of obtaining the multicast address according to the URL includes: querying the pre-acquired multicast address. Corresponding relationship with the URL, the query obtains the multicast address corresponding to the URL; or
- the step of obtaining the multicast address corresponding to the URL is generally before sending a multicast join message to the unicast-to-multicast U2M device corresponding to the multicast address or from the video of the multiple live channels according to the multicast address.
- the data is not specifically limited.
- the multicast address corresponding to the URL is obtained before the multicast address is used.
- S103 Obtain a source IP address and a source port included in the UDP request, where the source IP address is a client IP address, and the source port is a port on which the client sends a UDP request.
- the M2U device has obtained the video data requested by the client, and then needs to forward the video data to the client.
- the M2U device obtains the source IP address of the client according to the UDP request, and sends the UDP request. Port, as the destination address and destination port for forwarding video data.
- S104 Send the video data to the client by using UDP unicast according to the source IP address and the source port.
- the M2U device obtains the source IP address of the client and the source port that sends the UDP request according to the UDP request, and then sends the obtained video data to the client directly through the hardware forwarding module. Protocol conversion.
- UDP packets can be sent directly to the UDP receiver. Therefore, the M2U device can use the router to forward the hardware forwarding capability of the board and convert it into UDP unicast mode to return the video data to the client.
- the specific implementation process is:
- the M2U device obtains the multicast packet in the video data.
- the hardware forwarding module of the M2U device modifies the destination IP address of the multicast packet to the source IP address of the UDP request, and the multicast packet is The destination port is modified to be the source port of the UDP request, and the UDP unicast packet is obtained, and then the UDP unicast packet is sent to the client.
- the client sends a UDP request to the M2U device, and the M2U device obtains the video data corresponding to the live channel corresponding to the live channel identifier according to the live channel identifier in the UDP request, and obtains the video data.
- the M2U modifies the multicast destination IP address and the destination port to the unicast destination IP address and destination port of the obtained client, and directly uses the video data as The UDP unicast packet is forwarded to the client for parsing and playback.
- the CPU does not need to perform data protocol conversion. When there are many users, the time-frequency live broadcast can be realized to improve the throughput of the M2U device.
- FIG. 3 is an interaction flowchart of Embodiment 2 of a method for transmitting a live video according to the present invention. As shown in FIG. 3, the interaction process of the live broadcast video transmission method is as follows:
- S201 Send a UDP request to the M2U device; the UDP request includes a multicast address.
- the device on the user side sends a UDP request to the M2U device to request video data of the live channel through the operation of the user on the client.
- S202 Determine whether the user corresponding to the user identifier has the right to view the live channel corresponding to the multicast address.
- the UDP request further includes a user identifier (or a user identifier and a login password), and the M2U device needs to verify the authority of the user, and determine whether the user has the right to view the live channel corresponding to the multicast address.
- the verification method includes at least the following two methods:
- the M2U device sends the user identifier and the authentication information carried in the UDP request (that is, the registered user name and login password) and the live channel identifier to the live broadcast management platform for verification, and receives the live management platform to return.
- the verification result is used to indicate whether the user corresponding to the user identifier has the right to view the live channel corresponding to the live channel identifier.
- the M2U device sends the authorization information carried by the UDP request and the live channel identifier to the live management platform for verification, and receives the verification result returned by the live management platform; the verification result is used to indicate the location. Whether the user corresponding to the user identifier has the right to view the channel corresponding to the live channel identifier.
- the identifier of the live channel may be a multicast address or a URL that uniquely identifies the client, the URL is an OTT server notifying the client, and the URL is carried in the UDP request and sent to the M2U device;
- the UDP request may also carry the authorization information.
- the authorization information may be sent to the live management platform for verification.
- S203 Obtain video data of a live channel corresponding to the multicast address.
- the M2U obtains the verification result returned by the live management platform, and determines that the user has the video of the live channel corresponding to the multicast address
- the M2U obtains the video data of the live channel corresponding to the multicast address, and obtains the specific data.
- S205 Obtain the multicast packet in the video data, modify the destination IP address of the multicast packet to the source IP address of the UDP request, and modify the destination port of the multicast packet to the source port of the UDP request to obtain the UDP unicast report. Text.
- the M2U device requests the IP address of the client according to the UDP, that is, the source IP address, and the port through which the client sends the UDP request, that is, the source port.
- the data forwarding is implemented by the hardware forwarding module. Therefore, the hardware forwarding module can modify the destination address and the destination port of the multicast packet to the source IP address and the source port to obtain a unicast packet.
- the hardware forwarding module of the M2U device sends the video data directly to the client in the form of unicast packets. After receiving the packet, the client combines and parses the packet. And will get the video of the live channel to play.
- the M2U device obtains the multicast address corresponding to the URL according to the correspondence between the URL and the multicast address after receiving the UDP request, or The M2U device sends a multicast address query message including the URL to the live management platform, and receives the multicast address corresponding to the URL returned by the live management platform, and then obtains the video data according to the obtained multicast address according to the obtained multicast address and passes the UDP The broadcast method is sent to the client.
- the M2U device before the M2U device obtains the video data of the live channel corresponding to the multicast address according to the UDP request sent by the client, the M2U device also needs to view the live channel of the user who logs in to the client. Permission, if the user does not have the right to view the live channel, the UDP request is not responded. If the user has the right to watch the live channel, the U2M multicast obtains the video data of the live channel of the UDP protocol, The CPU needs to perform protocol conversion, and directly sends the video data to the client in UDP unicast mode through hardware forwarding, thereby effectively improving the throughput of the M2U device.
- FIG. 4 is a schematic diagram of interaction of a live video transmission system according to the present invention.
- a client that is, an APP on a user equipment side
- the signaling interaction between the devices is performed by the processor (ie, the CPU) of the M2U device, and the data interaction between the M2U device and the APP and the U2M is completed by the hardware forwarding module.
- the CPU mainly includes client management, live channel information, and multicast joining several modules.
- the U2M is used to multicast video data to the M2U device, including: Transmitting, by the M2U device, a multicast join message including a multicast address, and returning, to the M2U device, the video data of the live channel corresponding to the multicast address; or receiving the M2U device for requesting multiple A multicast join message of the video data of the live channel corresponding to the multicast address, and the M2U device returns the video data of the plurality of live channels.
- the multicast address is generally referred to as a multicast IP address
- FIG. 5a is an interaction flowchart of an example of a method for transmitting live video according to the present invention; as shown in FIG. 5, shown in FIG. Based on the system interaction diagram, a specific implementation process of the live video transmission method is:
- S301 The user logs in and authenticates through the APP, and requests to watch a live channel.
- the OTT server returns live channel information (multicast IP address) and authorization information.
- the OTT server returns the live channel identifier (such as a multicast IP address or URL) and the user's authorization information.
- the authorization information is generally a string of characters indicating that the user has the right to view the channel; for some free channels that the user can watch at will, there is no authorization information.
- the APP sends a UDP request, requesting video data (multicast IP address) and authorization information of a live channel.
- the APP sends a UDP request (video request) to the multicast source by using UDP unicast packets.
- the content of the request includes the identifier of the live channel (such as the multicast IP address) and the authorization information.
- S304 The M2U device forwards the live channel and the authorization information to the live management platform.
- the M2U device After the M2U device captures the UDP request packet, in order to determine whether the user has the right to view the channel, the M2U device forwards the identifier of the live channel (also referred to as live channel information) and the authorization information of the user to the live management platform.
- live channel information also referred to as live channel information
- S305 The live management platform returns the authentication result to the M2U device.
- the live management platform verifies whether the user has the right to view the live channel.
- the verification method may be that the live management platform directly judges according to the authorization information, or may forward the user name and password to the OTT server for verification. After the verification is completed, the verification result is returned to the M2U device.
- the M2U device does not process the UDP request; if the APP has the right to view, the M2U device records the multicast group viewed by the APP, the IP address and port of the received video.
- the M2U device determines that the APP (on behalf of the user) does not have the right to view the channel, and then does not process the request of the channel. If the APP has the right to view, the source IP address and source port of the UDP request packet are used as the destination IP address and destination port of the video data received by the APP.
- the M2U device sends a network group management protocol (English: Internet Group Management Protocol, IGMP for short) to join the message.
- IGMP Internet Group Management Protocol
- the M2U device sends an IGMP join message to the U2M device to join the multicast address requested by the APP.
- S308 The U2M device sends multicast video traffic to the M2U device.
- the M2U device modifies the destination IP address and the destination port of the corresponding multicast packet to the IP address and port of the received video of the APP, and forwards the unicast traffic to the APP.
- S310 The M2U device sends UDP unicast video traffic to the APP.
- the U2M device sends multicast video data (that is, a video stream) to the M2U device.
- the M2U device modifies the destination IP address and destination port to the IP address and port of the received video of the APP.
- the M2U device forwards UDP unicast video traffic to the APP.
- the APP combines the received packets to obtain a live video and plays it.
- the OTT server may actively notify the APP of the multicast address corresponding to the channel.
- the OTT server may only send a URL to the APP that can identify the live channel, and then the M2U obtains the UDP carrying the URL. After the request, go to the live management platform to query the multicast address corresponding to the URL. This query process can be performed concurrently with the viewing rights verification process.
- the OTT server may not return the authorization information, and the APP carries its own user and password in the UDP request, and then the M2U forwards the verification to the live management platform, and the solution is not limited.
- FIG. 5b is a schematic diagram of a transmission protocol.
- the U2M device downloads the index file and the fragment in a unicast manner, and then cuts into a real-time transmission protocol (English: Real).
- -time Transport Protocol RTP
- RTP -time Transport Protocol
- the UDP packet includes an IP header, a UDP header, an RTP header, and an RTP payload.
- the RTP header also includes a synchronization source (English: synchronization source, short for: SSRC) identifier and a contribution source (English: contributing source, CSRC for short).
- the length indicates the length of the valid data
- the length of the URL indicates the length of the fragment or index file URL
- the HAS data part is the data of the media slice or index file.
- RTP redundancy The remaining data is used for forward error correction.
- the terminal device side of the user receives the UDP unicast packet through the APP to detect whether there is a packet loss. If there is a packet loss, the forward error correction (English: forward error correction, FEC) and the initiative are adopted. Request retransmission (English: retransmission, abbreviation: RET) to complete the packet loss reduction.
- the specific execution process on the client side is as follows:
- the APP determines whether there is any packet loss according to the RTP sequence number. If the RTP sequence number is not continuous, it is considered that a packet loss has occurred, then the process proceeds to step 2; otherwise, the process proceeds to step 4.
- the APP restores the packet according to the FEC. If all the packets are successfully restored, go to step 4; otherwise, go to step 3.
- the APP requests the RET server to retransmit the lost RTP packet. After receiving the RTP packet retransmitted by the RET server, the APP reorders the RTP packets by the sequence number to fill the holes caused by the packet loss.
- the APP checks the timestamp of the received RTP packet. If it is different from the timestmap of the previous RTP packet, it goes to step 5; otherwise, it goes to step 7.
- Timestamp is different, indicating that this RTP package begins to transfer a new file object.
- the APP parses the file type (index file or media slice) and parses the file name.
- the APP notifies the decoder of the new file object information.
- Timestamp is the same, indicating that this RTP package and the previous RTP package are the same file object.
- the file object data is parsed from the RTP packet load and sent to the decoder for processing.
- the decoder then decodes the received data packet to obtain video data corresponding to the UDP request, and plays it.
- FIG. 6 is a schematic structural diagram of an embodiment of an M2U device according to the present invention. As shown in FIG. 6, the M2U device 10 includes:
- the receiving module 11 is configured to receive a UDP request sent by the client, where the UDP request includes a live channel identifier, and is used to request video data of a live channel corresponding to the live channel identifier;
- the processing module 12 is configured to acquire video data of a live channel corresponding to the live channel identifier.
- the processing module 12 is further configured to obtain a source IP address and a source port included in the UDP request, where the source IP address is an IP address of the client, and the source port sends the The port of the UDP request;
- the sending module 13 is configured to send the video data to the client in UDP unicast mode according to the source IP address and the source port.
- the M2U device provided in this embodiment is used to perform the technical solution of the M2U device in any of the foregoing method embodiments, and the implementation principle and technical effects are similar, and details are not described herein again.
- the sending module 13 is specifically configured to:
- the live channel identifier includes a multicast address
- the sending module 13 is further configured to send a multicast join message to the U2M device corresponding to the multicast address, where the multicast join message includes the multicast Address
- the receiving module 11 is further configured to receive the video data of a live channel corresponding to the multicast address returned by the U2M device.
- the live channel identifier includes a multicast address
- the receiving module 11 receives the user datagram protocol UDP request sent by the client
- the sending module 13 is further configured to send a multicast join message to the U2M device, where the multicast join message is used to request video data of multiple live channels corresponding to multiple multicast addresses;
- the receiving module 11 is further configured to receive video data of the multiple live channels sent by the U2M device;
- the processing module 12 is configured to acquire, according to the multicast address, video data of a live channel corresponding to the multicast address from video data of the multiple live channels.
- the live channel identifier includes a multicast address
- the sending module 13 is further configured to send a multicast join message to the U2M device corresponding to the multicast address, where the multicast join message includes the multicast address;
- the receiving module 11 is further configured to receive the video data of a live channel corresponding to the multicast address returned by the U2M device.
- the live channel identifier includes a multicast address
- the receiving module 11 receives the UDP request sent by the client
- the sending module 13 is further configured to send a multicast join message to the U2M device, where the multicast join message is used to request video data of multiple live channels corresponding to multiple multicast addresses;
- the receiving module 11 is further configured to receive video data of the multiple live channels sent by the U2M device;
- the processing module 12 is configured to acquire, according to the multicast address, video data of a live channel corresponding to the multicast address from video data of the multiple live channels.
- the live channel identifier includes a URL
- the processing module 12 is further configured to acquire, according to the URL, a multicast address corresponding to the URL;
- the sending module 13 is further configured to send a multicast join message to the U2M device corresponding to the multicast address, where the multicast join message includes the multicast address;
- the receiving module 11 is further configured to receive the video data of a live channel corresponding to the multicast address returned by the U2M device.
- the live channel identifier includes a URL
- the sending module 13 is further configured to send a multicast join message to the U2M device, where the multicast join message is used. Requesting video data of multiple live channels corresponding to multiple multicast addresses;
- the receiving module 11 is further configured to receive video data of the multiple live channels sent by the U2M device;
- the processing module 12 is specifically configured to:
- the processing module 12 is further configured to query a correspondence between the pre-acquired multicast address and the URL, and obtain a multicast address corresponding to the URL.
- the sending module 13 is further configured to send a multicast address query message including the URL to the live broadcast management platform, and the receiving module 11 is further configured to receive a multicast address corresponding to the URL returned by the live broadcast management platform.
- the UDP request further includes a user identifier.
- the processing module 12 is further configured to determine whether the user corresponding to the user identifier has the right to view the live channel corresponding to the live channel identifier.
- the sending module 13 is further configured to send the user identifier and the verification information carried in the UDP request and the live channel identifier to the live broadcast management platform for verification;
- the receiving module 11 is further configured to receive the live broadcast management. a verification result returned by the platform, where the verification result is used to indicate whether the user corresponding to the user identifier has the right to view the live channel corresponding to the live channel identifier;
- the sending module 13 is further configured to send the authorization information carried by the UDP request and the live channel identifier to the live broadcast management platform for verification; the receiving module 11 is further configured to receive the verification result returned by the live broadcast management platform, The verification result is used to indicate whether the user corresponding to the user identifier has the right to view the channel corresponding to the live channel identifier.
- the M2U device provided in this embodiment is used to perform the technical solution of the M2U device in any of the foregoing method embodiments, and the implementation principle and technical effects are similar, and details are not described herein again.
- FIG. 7 is a schematic structural diagram of a client embodiment of the present invention. As shown in FIG. 7, the client 20 includes:
- the sending module 21 is configured to send a UDP request to the M2U device, where the UDP request includes a live channel identifier, and is used to request video data of a live channel corresponding to the live channel identifier;
- the receiving module 22 is configured to receive the video data of the live channel sent by the M2U device; the video data is obtained by the M2U device according to the live channel identifier; the video data is carried in a UDP unicast packet;
- the processing module 23 is configured to parse the UDP unicast message to play the video of the live channel.
- the UDP request sent by the sending module 21 further includes: authorization information; and/or user identifier and verification information.
- the client provided in this embodiment is used to perform the technical solution of the client in any of the foregoing method embodiments, and the implementation principle and technical effects are similar, and details are not described herein again.
- FIG 8 is a schematic structural diagram of an embodiment of an M2U device entity according to the present invention.
- the M2U device 30 includes: a memory 31 for storing program code and configuration information, a processor 32, and a hardware forwarding module 33;
- the processor 32 is configured to:
- the UDP request includes a live channel identifier, and is used to request video data of a live channel corresponding to the live channel identifier;
- the hardware forwarding module 33 is configured to send the video data to the client in UDP unicast mode according to the source IP address and the source port.
- the hardware forwarding module 33 is specifically configured to:
- the live channel identifier includes a multicast address
- the processor 32 is further configured to send a multicast join message to the U2M device corresponding to the multicast address, where the multicast join message includes the multicast address;
- the hardware forwarding module 33 is further configured to receive the video data of the live channel corresponding to the multicast address returned by the U2M device.
- the live channel identifier includes a multicast address
- the processor 32 is further configured to send a multicast join message to the unicast-to-multicast U2M device, where the multicast join message is used to request multiple multicast addresses.
- the hardware forwarding module 33 is further configured to receive video data of the multiple live channels sent by the U2M device;
- the processor 32 is further configured to acquire, according to the multicast address, video data of a live channel corresponding to the multicast address from video data of the multiple live channels.
- the live channel identifier includes a URL
- the processor 32 is further configured to:
- the live channel identifier includes a URL
- the processor 32 is further configured to: before the processor 32 receives the user datagram protocol UDP request sent by the client:
- the processor 32 is specifically configured to:
- the processor 32 is specifically configured to:
- the UDP request further includes a user identifier.
- the processor 32 is further configured to determine whether the user corresponding to the user identifier has the view. The right of the live channel corresponding to the live channel identifier,
- the step of acquiring the video data of the live channel corresponding to the live channel identifier is performed.
- the processor 32 is further configured to send the user identifier and the verification information carried in the UDP request and the live channel identifier to the live management platform for verification, and receive the verification result returned by the live management platform;
- the verification result is used to indicate whether the user corresponding to the user identifier has the right to view the live channel identifier. Permission to broadcast channels;
- the processor 32 is further configured to send the authorization information carried by the UDP request and the live channel identifier to the live management platform for verification, and receive the verification result returned by the live management platform; the verification result is used to indicate Whether the user corresponding to the user identifier has the right to view the channel corresponding to the live channel identifier.
- the M2U device provided in this embodiment, where the processor is configured to complete all signaling interactions with other device entities, and the hardware forwarding module is configured to complete a data interaction process with other device entities, where the M2U device is configured to perform any of the foregoing methods.
- the technical solution of the client in the embodiment is similar to the technical solution, and details are not described herein again.
- FIG. 9 is a schematic structural diagram of an embodiment of a user equipment entity according to the present invention.
- the user equipment 40 is used to carry a client, and specifically includes: a memory 41, a transceiver 42 and a processing for storing program codes and configuration information. 43
- the transceiver 42 is configured to send a UDP request to the M2U device, where the UDP request includes a live channel identifier, and is used to request video data of a live channel corresponding to the multicast address;
- the transceiver 42 is further configured to receive video data of the live channel sent by the M2U device; the video data is obtained by the M2U device according to the live channel identifier; and the video data is carried in a UDP unicast report.
- the video data is carried in a UDP unicast report.
- the processor 43 is configured to parse the UDP unicast message to play the video of the live channel.
- the UDP request sent by the transceiver 42 further includes: authorization information; and/or user identification and verification information.
- the user equipment provided in this embodiment is used to perform the technical solution of the client in any of the foregoing method embodiments, and the implementation principle and technical effects are similar, and details are not described herein again.
- the processor may be a central processing unit (English: central processing unit, CPU for short), or other general-purpose processor, digital signal processor (English: digital Signal processor (referred to as: DSP), application-specific integrated circuit (English: application-specific integrated circuit, referred to as: ASIC).
- 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 as a hardware processor, or may be performed by a combination of hardware and software modules in the processor.
- the aforementioned program can be stored in a computer readable memory.
- the steps including the foregoing method embodiments are performed; and the foregoing memory (storage medium) includes: read-only memory (English: read-only memory, abbreviation: ROM), random access memory (English: random access memory) , abbreviations: RAM), flash memory, hard disk, solid state drive, magnetic tape (English: magnetic tape), floppy disk (English: floppy disk), optical disc (English: optical disc) and any combination thereof.
Landscapes
- Engineering & Computer Science (AREA)
- Multimedia (AREA)
- Signal Processing (AREA)
- Computer Networks & Wireless Communication (AREA)
- Databases & Information Systems (AREA)
- Computer Security & Cryptography (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
- Two-Way Televisions, Distribution Of Moving Picture Or The Like (AREA)
Abstract
Description
Claims (24)
- 一种直播视频的传输方法,其特征在于,应用于组播转单播M2U设备,所述方法包括:接收客户端发送的用户数据报协议UDP请求;所述UDP请求包括直播频道标识,用于请求所述直播频道标识对应的直播频道的视频数据;获取所述直播频道标识对应的直播频道的视频数据;获取所述UDP请求中包括的源IP地址和源端口,其中,所述源IP地址为所述客户端的IP地址,所述源端口为所述客户端发送所述UDP请求的端口;根据所述源IP地址和所述源端口,将所述视频数据以UDP单播方式发送至所述客户端。
- 根据权利要求1所述的方法,其特征在于,所述根据所述源IP地址和所述源端口,将所述视频数据以UDP单播方式发送至所述客户端,包括:获取所述视频数据中的组播报文;将所述组播报文的目的IP地址修改为所述UDP请求的源IP地址,将所述组播报文的目的端口修改为所述UDP请求的源端口,得到UDP单播报文;向所述客户端发送所述UDP单播报文。
- 根据权利要求2所述的方法,其特征在于,所述直播频道标识包括组播地址,则所述获取所述直播频道标识对应的直播频道的视频数据,包括:向所述组播地址对应的单播转组播U2M设备发送组播加入消息,所述组播加入消息包括所述组播地址;接收所述U2M设备返回的所述组播地址对应的直播频道的所述视频数据。
- 根据权利要求2所述的方法,其特征在于,所述直播频道标识包括组播地址,所述接收客户端发送的用户数据报协议UDP请求之前,所述方法还包括:向单播转组播U2M设备发送组播加入消息,所述组播加入消息用于请求多个组播地址对应的多个直播频道的视频数据;接收所述U2M设备发送的所述多个直播频道的视频数据;则所述获取所述直播频道标识对应的直播频道的视频数据,包括:根据所述组播地址从所述多个直播频道的视频数据中获取所述组播地址对应的直播频道的视频数据。
- 根据权利要求2所述的方法,其特征在于,所述直播频道标识包括统一资源定位符URL,则所述获取所述直播频道标识对应的直播频道的视频数据,包括:根据所述URL获取与所述URL对应的组播地址;向所述组播地址对应的单播转组播U2M设备发送组播加入消息,所述组播加入消息包括所述组播地址;接收所述U2M设备返回的所述组播地址对应的直播频道的所述视频数据。
- 根据权利要求2所述的方法,其特征在于,所述直播频道标识包括统一资源定位符URL,所述接收客户端发送的用户数据报协议UDP请求之前,所述方法还包括:向单播转组播U2M设备发送组播加入消息,所述组播加入消息用于请求多个组播地址对应的多个直播频道的视频数据;接收所述U2M设备发送的所述多个直播频道的视频数据;则所述获取所述直播频道标识对应的直播频道的视频数据,包括:根据所述URL获取与所述URL对应的组播地址;根据所述组播地址从所述多个直播频道的视频数据中获取所述组播地址对应的直播频道的视频数据。
- 根据权利要求5或6所述的方法,其特征在于,所述根据所述URL获取与所述URL对应的组播地址,包括:查询预先获取的组播地址和URL的对应关系,查询获取与所述URL对应的组播地址;或者,向直播管理平台发送包括所述URL的组播地址查询消息,并接收所述直播管理平台返回的与所述URL对应的组播地址。
- 根据权利要求1至7中任一项所述的方法,其特征在于,所述UDP请求还包括用户标识;则所述获取所述直播频道标识对应的直播频道的视频数据之前,所述方法还包括:确定所述用户标识对应的用户是否具备观看所述直播频道标识对应的直播频道的权限,若确定出所述用户标识对应的用户具备观看所述直播频道标识对应的直播频道的权限,则执行所述获取所述直播频道标识对应的直播频道的视频数据的步骤。
- 根据权利要求8所述的方法,其特征在于,所述确定所述用户标识对应的用户是否具备观看所述直播频道标识对应的直播频道的权限,包括:将UDP请求中携带的用户标识和验证信息以及所述直播频道标识发送给直播管理平台进行验证,并接收所述直播管理平台返回的验证结果;所述验证结果用于指示所述用户标识对应的用户是否具备观看所述直播频道标识对应的直播频道的权限;或者,将所述UDP请求携带的授权信息以及所述直播频道标识发送给直播管理平台进行验证,并接收所述直播管理平台返回的验证结果;所述验证结果用于指示所述用户标识对应的用户是否具备观看所述直播频道标识对应的频道的权限。
- 一种直播视频的传输方法,其特征在于,应用于客户端,所述方法包括:向组播转单播M2U设备发送用户数据报协议UDP请求;所述UDP请求包括直播频道标识,用于请求所述直播频道标识对应的直播频道的视频数据;接收所述M2U设备发送的所述直播频道的视频数据;所述视频数据为所述M2U设备根据所述直播频道标识获取的;所述视频数据承载在UDP单播报文中;解析所述UDP单播报文以播放所述直播频道的视频。
- 根据权利要求10所述的方法,其特征在于,所述UDP请求还包括:授权信息;和/或,用户标识和验证信息。
- 一种组播转单播M2U设备,其特征在于,包括:接收模块,用于接收客户端发送的用户数据报协议UDP请求;所述UDP请求包括直播频道标识,用于请求所述直播频道标识对应的直播频道的视频数据;处理模块,用于获取所述直播频道标识对应的直播频道的视频数据;所述处理模块还用于获取所述UDP请求中包括的源IP地址和源端口,其中,所述源IP地址为所述客户端的IP地址,所述源端口为所述客户端发送所述UDP请求的端口;发送模块,用于根据所述源IP地址和所述源端口,将所述视频数据以UDP单播方式发送至所述客户端。
- 根据权利要求12所述的M2U设备,其特征在于,所述发送模块具体用于:获取所述视频数据中的组播报文;将所述组播报文的目的IP地址修改为所述UDP请求的源IP地址,将所述组播报文的目的端口修改为所述UDP请求的源端口,得到UDP单播报文;向所述客户端发送所述UDP单播报文。
- 根据权利要求13所述的M2U设备,其特征在于,所述直播频道标识包括组播地址,则所述发送模块还用于向所述组播地址对应的单播转组播U2M设备发送组播加入消息,所述组播加入消息包括所述组播地址;所述接收模块还用于接收所述U2M设备返回的所述组播地址对应的直播频道的所述视频数据。
- 根据权利要求13所述的M2U设备,其特征在于,所述直播频道标识包括组播地址,所述接收模块接收客户端发送的用户数据报协议UDP请求之前,所述发送模块还用于向单播转组播U2M设备发送组播加入消息,所述组播加入消息用于请求多个组播地址对应的多个直播频道的视频数据;所述接收模块还用于接收所述U2M设备发送的所述多个直播频道的视频数据;所述处理模块具体用于根据所述组播地址从所述多个直播频道的视频数据中获取所述组播地址对应的直播频道的视频数据。
- 根据权利要求13所述的M2U设备,其特征在于,所述直播频道标识包括统一资源定位符URL,则所述处理模块还用于根据所述URL获取与所述URL对应的组播地址;所述发送模块还用于向所述组播地址对应的单播转组播U2M设备发送组播加入消息,所述组播加入消息包括所述组播地址;所述接收模块还用于接收所述U2M设备返回的所述组播地址对应的直播频道的所述视频数据。
- 根据权利要求13所述的M2U设备,其特征在于,所述直播频道标识包括统一资源定位符URL,所述接收模块接收客户端发送的用户数据报协议UDP请求之前,所述发送模块还用于向单播转组播U2M设备发送组播加入消息,所述组播加入消息用于请求多个组播地址对应的多个直播频道的视频数据;所述接收模块还用于接收所述U2M设备发送的所述多个直播频道的视频数据;则所述处理模块具体用于:根据所述URL获取与所述URL对应的组播地址;根据所述组播地址从所述多个直播频道的视频数据中获取所述组播地址对应的直播频道的视频数据。
- 根据权利要求16或17所述的M2U设备,其特征在于,所述处理模块还用于查询预先获取的组播地址和URL的对应关系,查询获取与所述URL对应的组播地址;或者,所述发送模块还用于向直播管理平台发送包括所述URL的组播地址查询消息,所述接收模块还用于接收所述直播管理平台返回的与所述URL对应的组播地址。
- 根据权利要求12至18中任一项所述的M2U设备,其特征在于,所述UDP请求还包括用户标识;则所述处理模块还用于确定所述用户标识对应的用户是否具备观看所述直播频道标识对应的直播频道的权限,若所述用户标识对应的用户具备观看所述直播频道标识对应的直播频道的权限,则执行所述获取所述直播频道标识对应的直播频道的视频数据的步骤。
- 根据权利要求19所述的M2U设备,其特征在于,所述发送模块还用于将UDP请求中携带的用户标识和验证信息以及所述直播频道标识发送给直播管理平台进行验证;所述接收模块还用于接收所述直播管理平台返回的验证结果,所述验证结果用于指示所述用户标识对应的用户是否具备观看所述直播频道标识对应的直播频道的权限;或者,所述发送模块还用于将所述UDP请求携带的授权信息以及所述直播频道标识发送给直播管理平台进行验证;所述接收模块还用于接收所述直播管理平台返回的验证结果,所述验证结果用于指示所述用户标识对应的用户是否具备观看所述直播频道标识对应的频道的权限。
- 一种客户端,其特征在于,包括:发送模块,用于向组播转单播M2U设备发送用户数据报协议UDP请求;所述UDP请求包括直播频道标识,用于请求直播频道标识对应的直播频道的视频数据;接收模块,用于接收所述M2U设备发送的所述直播频道的视频数据;所述视频数据为所述M2U设备根据所述直播频道标识获取的;所述视频数据承载在UDP单播报文中;处理模块,用于解析所述UDP单播报文以播放所述直播频道的视频。
- 根据权利要求21所述的客户端,其特征在于,所述发送模块发送的所述UDP请求还包括:授权信息;和/或,用户标识和验证信息。
- 一种直播视频的传输系统,其特征在于,包括:权利要求12至20任一项所述的组播转单播M2U设备以及权利要求21或22所述的客户端。
- 根据权利要求23所述的系统,其特征在于,所述系统还包括单播转组播U2M设备;所述U2M设备用于:接收所述M2U设备发送的包括组播地址的组播加入消息,并向所述M2U设备返回所述组播地址对应的直播频道的所述视频数据;或者,接收所述M2U设备发送的用于请求多个组播地址对应的直播频道的视频数据的组播加入消息,并将所述M2U设备返回所述多个直播频道的视频数据。
Priority Applications (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
EP17860949.1A EP3518551A4 (en) | 2016-10-13 | 2017-10-11 | METHOD, APPARATUS AND SYSTEM FOR LIVE VIDEO TRANSMISSION |
JP2019520440A JP6966542B2 (ja) | 2016-10-13 | 2017-10-11 | ライブビデオ送信方法およびシステムならびに装置 |
KR1020197013434A KR20190066046A (ko) | 2016-10-13 | 2017-10-11 | 라이브 비디오 송신 방법, 시스템 및 장치 |
US16/382,211 US11019367B2 (en) | 2016-10-13 | 2019-04-12 | Live video transmission method and system, and apparatus |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201610896179.2A CN107948762B (zh) | 2016-10-13 | 2016-10-13 | 直播视频的传输方法、装置和系统 |
CN201610896179.2 | 2016-10-13 |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US16/382,211 Continuation US11019367B2 (en) | 2016-10-13 | 2019-04-12 | Live video transmission method and system, and apparatus |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2018068727A1 true WO2018068727A1 (zh) | 2018-04-19 |
Family
ID=61905186
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2017/105693 WO2018068727A1 (zh) | 2016-10-13 | 2017-10-11 | 直播视频的传输方法、装置和系统 |
Country Status (6)
Country | Link |
---|---|
US (1) | US11019367B2 (zh) |
EP (1) | EP3518551A4 (zh) |
JP (1) | JP6966542B2 (zh) |
KR (1) | KR20190066046A (zh) |
CN (1) | CN107948762B (zh) |
WO (1) | WO2018068727A1 (zh) |
Families Citing this family (10)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN110891183B (zh) * | 2018-09-11 | 2022-11-01 | 中兴通讯股份有限公司 | 频道共享方法、设备和计算机可读存储介质 |
CN110505500A (zh) * | 2019-08-06 | 2019-11-26 | 咪咕视讯科技有限公司 | 一种缓存数据发送处理方法及装置 |
CN110557655B (zh) * | 2019-09-06 | 2021-10-26 | 卓米私人有限公司 | 一种视频画面显示方法、装置、电子设备及存储介质 |
CN111314303B (zh) * | 2020-01-17 | 2022-11-22 | 网易(杭州)网络有限公司 | 直播系统、直播系统的数据处理方法及装置 |
DK180823B1 (en) * | 2020-03-02 | 2022-05-03 | Mediathand Aps | System and method for providing multicast to unicast services |
CN111669610B (zh) * | 2020-05-27 | 2022-08-05 | 北京奇艺世纪科技有限公司 | 直播视频的传输方法、系统、装置、服务器、电子设备及存储介质 |
CN112104905B (zh) * | 2020-07-06 | 2022-10-11 | 聚好看科技股份有限公司 | 服务器、显示设备及数据传输方法 |
US20220132211A1 (en) * | 2020-10-27 | 2022-04-28 | Circle Computer Resources, Inc. | Low-latency content delivery over a public network |
TWI813120B (zh) * | 2021-12-30 | 2023-08-21 | 日商17Live股份有限公司 | 用於串流資料存取之系統、方法及電腦可讀媒體 |
CN115460470B (zh) * | 2022-08-19 | 2024-03-26 | 烽火通信科技股份有限公司 | 组播数据转发方法、装置、设备及可读存储介质 |
Citations (8)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN1961590A (zh) * | 2004-11-05 | 2007-05-09 | 鲁库斯无线公司 | 通信网络中用于改进数据吞吐量的系统及方法 |
CN102449954A (zh) * | 2009-05-26 | 2012-05-09 | 阿尔卡特朗讯公司 | 用于将单播客户机请求转换为多播客户机请求的系统和方法 |
US20140282784A1 (en) * | 2013-03-15 | 2014-09-18 | Time Warner Cable Enterprises Llc | Apparatus and methods for multicast delivery of content in a content delivery network |
CN104426681A (zh) * | 2013-08-24 | 2015-03-18 | Nicira股份有限公司 | 端点的分布式多播 |
US20150106477A1 (en) * | 2000-06-29 | 2015-04-16 | Khanh Mai | Virtual multicasting |
CN104954313A (zh) * | 2015-05-19 | 2015-09-30 | 鼎点视讯科技有限公司 | 一种分布式ipqam系统 |
CN105657534A (zh) * | 2016-01-07 | 2016-06-08 | 烽火通信科技股份有限公司 | 基于Android的网络电视播放切换系统及方法 |
CN106487690A (zh) * | 2016-09-23 | 2017-03-08 | 乐视控股(北京)有限公司 | 数据发送方法及装置 |
Family Cites Families (26)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JPH034348A (ja) * | 1989-05-31 | 1991-01-10 | Nec Corp | 入出力装置制御アダプタ |
US6259701B1 (en) * | 1997-09-11 | 2001-07-10 | At&T Corp. | Method and system for a unicast endpoint client to access a multicast internet protocol (IP) session |
JPH11205312A (ja) * | 1998-01-08 | 1999-07-30 | Fujitsu Ltd | マルチキャスト通信システム及びマルチキャスト通信システムにおけるマルチキャスト通信方法並びにマルチキャスト通信システムに使用される発信端末及びマルチキャスト通信装置 |
US6233618B1 (en) * | 1998-03-31 | 2001-05-15 | Content Advisor, Inc. | Access control of networked data |
JP2002185528A (ja) * | 2000-12-11 | 2002-06-28 | Nippon Telegr & Teleph Corp <Ntt> | Ipマルチキャスト通信装置及びコンテンツ提供方法 |
US7549160B1 (en) * | 2000-12-21 | 2009-06-16 | Cisco Technology, Inc. | Method and system for authenticated access to internet protocol (IP) multicast traffic |
US7724744B2 (en) * | 2001-04-30 | 2010-05-25 | At&T Corp. | Method and system for a unicast endpoint client to access a multicast internet protocol (IP) session |
US7107609B2 (en) * | 2001-07-20 | 2006-09-12 | Hewlett-Packard Development Company, L.P. | Stateful packet forwarding in a firewall cluster |
GB2414360B (en) * | 2004-05-18 | 2006-10-18 | Motorola Inc | Data communication system,router and method for routeing data |
US20070019645A1 (en) * | 2005-07-05 | 2007-01-25 | Deepthy Menon | Method and system for multicasting data in a communication network |
US20070280232A1 (en) * | 2006-05-31 | 2007-12-06 | Wojciech Dec | Dynamic delivery of multicast service notification messages |
CN101473616B (zh) * | 2006-06-27 | 2011-12-14 | 汤姆森特许公司 | 用于可靠地传递多播数据的方法和装置 |
JP4886500B2 (ja) * | 2006-12-20 | 2012-02-29 | 株式会社日立製作所 | データ転送装置、及びそのシステム |
US20080198771A1 (en) * | 2007-02-21 | 2008-08-21 | Iyengar Ranganath Gorur | Method, Apparatus or Software for a Multicast Network for Providing Indications of Active Multicast Groups to one or more Multicast Receivers |
CN100551044C (zh) * | 2007-04-06 | 2009-10-14 | 华为技术有限公司 | 实现视频直播的方法、设备及系统 |
US10264029B2 (en) * | 2009-10-30 | 2019-04-16 | Time Warner Cable Enterprises Llc | Methods and apparatus for packetized content delivery over a content delivery network |
US8817684B2 (en) * | 2010-12-17 | 2014-08-26 | Verizon Patent And Licensing Inc. | Adaptive mobile multicasting for wireless networks |
CN102523098B (zh) * | 2011-11-21 | 2014-12-10 | 华为技术有限公司 | 一种业务接入的方法、装置及系统 |
US9402107B2 (en) * | 2013-03-15 | 2016-07-26 | Time Warner Cable Enterprises Llc | Apparatus and methods for delivery of multicast and unicast content in a content delivery network |
WO2015035622A1 (zh) * | 2013-09-13 | 2015-03-19 | 华为技术有限公司 | 流媒体传输方法和系统、以及用户设备和服务器 |
WO2015064383A1 (ja) * | 2013-10-30 | 2015-05-07 | ソニー株式会社 | 送信装置、送信方法、受信装置、及び、受信方法 |
US20150172731A1 (en) * | 2013-12-18 | 2015-06-18 | Time Warner Cable Enterprises Llc | Methods and apparatus for providing alternate content |
CN106464932A (zh) * | 2014-03-31 | 2017-02-22 | 英国电讯有限公司 | 多播流传输 |
US9787751B2 (en) * | 2014-08-06 | 2017-10-10 | At&T Intellectual Property I, L.P. | Method and apparatus for delivering media content utilizing segment and packaging information |
US10735823B2 (en) * | 2015-03-13 | 2020-08-04 | Telefonaktiebolaget Lm Ericsson (Publ) | System and method for optimized delivery of live ABR media |
US10063609B2 (en) * | 2015-08-19 | 2018-08-28 | Qualcomm Incorporated | Methods and apparatus for multimedia conferences using single source multi-unicast |
-
2016
- 2016-10-13 CN CN201610896179.2A patent/CN107948762B/zh active Active
-
2017
- 2017-10-11 EP EP17860949.1A patent/EP3518551A4/en active Pending
- 2017-10-11 WO PCT/CN2017/105693 patent/WO2018068727A1/zh unknown
- 2017-10-11 JP JP2019520440A patent/JP6966542B2/ja active Active
- 2017-10-11 KR KR1020197013434A patent/KR20190066046A/ko not_active IP Right Cessation
-
2019
- 2019-04-12 US US16/382,211 patent/US11019367B2/en active Active
Patent Citations (8)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20150106477A1 (en) * | 2000-06-29 | 2015-04-16 | Khanh Mai | Virtual multicasting |
CN1961590A (zh) * | 2004-11-05 | 2007-05-09 | 鲁库斯无线公司 | 通信网络中用于改进数据吞吐量的系统及方法 |
CN102449954A (zh) * | 2009-05-26 | 2012-05-09 | 阿尔卡特朗讯公司 | 用于将单播客户机请求转换为多播客户机请求的系统和方法 |
US20140282784A1 (en) * | 2013-03-15 | 2014-09-18 | Time Warner Cable Enterprises Llc | Apparatus and methods for multicast delivery of content in a content delivery network |
CN104426681A (zh) * | 2013-08-24 | 2015-03-18 | Nicira股份有限公司 | 端点的分布式多播 |
CN104954313A (zh) * | 2015-05-19 | 2015-09-30 | 鼎点视讯科技有限公司 | 一种分布式ipqam系统 |
CN105657534A (zh) * | 2016-01-07 | 2016-06-08 | 烽火通信科技股份有限公司 | 基于Android的网络电视播放切换系统及方法 |
CN106487690A (zh) * | 2016-09-23 | 2017-03-08 | 乐视控股(北京)有限公司 | 数据发送方法及装置 |
Non-Patent Citations (1)
Title |
---|
See also references of EP3518551A4 * |
Also Published As
Publication number | Publication date |
---|---|
JP6966542B2 (ja) | 2021-11-17 |
EP3518551A1 (en) | 2019-07-31 |
CN107948762A (zh) | 2018-04-20 |
EP3518551A4 (en) | 2019-11-13 |
KR20190066046A (ko) | 2019-06-12 |
US20190238897A1 (en) | 2019-08-01 |
JP2019537342A (ja) | 2019-12-19 |
CN107948762B (zh) | 2021-05-11 |
US11019367B2 (en) | 2021-05-25 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2018068727A1 (zh) | 直播视频的传输方法、装置和系统 | |
JP6648211B2 (ja) | マルチキャスト通信またはブロードキャスト通信において拡張したファイル配信を行う方法および装置 | |
US10321199B2 (en) | Streaming with optional broadcast delivery of data segments | |
US9350488B2 (en) | Content delivery system with allocation of source data and repair data among HTTP servers | |
US10205971B2 (en) | Media data live broadcast method, device, and system | |
US11277456B2 (en) | System and method for delivering an audio-visual con tent to a client device | |
US20100214970A1 (en) | Method and system for transmitting data packets from a source to multiple receivers via a network | |
KR102149445B1 (ko) | 멀티미디어 브로드캐스트 멀티캐스트 서비스 기반의 플렉서블 브로드캐스트 서비스를 위한 방법 및 장치 | |
WO2008052443A1 (fr) | Procédé et système de surveillance des performances d'un service multimédia | |
WO2009021460A1 (fr) | Procédé de rapport d'un résultat de mise en œuvre de politique, système de communication par réseau et équipement | |
KR101117874B1 (ko) | 실시간 제어 프로토콜(rtcp) 메시지 내로의 세션 설명메시지의 임베딩 | |
BRPI0706485A2 (pt) | processamento de dados de mìdia para serviço de seção com base em sip | |
Kim et al. | An efficient delay-constrained ARQ scheme for MMT packet-based real-time video streaming over IP networks | |
WO2016101213A1 (zh) | 一种文件修复的方法、相关装置及系统 | |
KR101745367B1 (ko) | 하이퍼텍스트 전송 프로토콜을 이용한 멀티미디어 컨텐츠 스트리밍 시스템 및 방법 | |
Srinivasan et al. | QoS Aware Cross Layer Design for Social Media Transmission using SCTP |
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: 17860949 Country of ref document: EP Kind code of ref document: A1 |
|
ENP | Entry into the national phase |
Ref document number: 2019520440 Country of ref document: JP Kind code of ref document: A |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
ENP | Entry into the national phase |
Ref document number: 2017860949 Country of ref document: EP Effective date: 20190425 |
|
ENP | Entry into the national phase |
Ref document number: 20197013434 Country of ref document: KR Kind code of ref document: A |