Data stream processing method and apparatus, system, and storage medium

HK40137293APending Publication Date: 2026-09-11HUAWEI CLOUD COMPUTING TECHNOLOGIES CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
HK42026126211
Authority / Receiving Office
HK · HK
Patent Type
Applications
Current Assignee / Owner
Filing Date
2026-07-16
Publication Date
2026-09-11

Smart Images

  • Figure 00000000_0000_ABST
    Figure 00000000_0000_ABST
Patent Text Reader

Abstract

The invention discloses a data stream processing method, device and system and a storage medium, and belongs to the field of communication. The method is applied to the content distribution system, the content distribution system comprises a first CDN center node, and a district where the first CDN center node is located further comprises at least one CDN center node. The method comprises the following steps: a first CDN center node receives a first data stream of a live broadcast service; the first CDN center node sends first information of the first data flow to at least one CDN center node, wherein the first information comprises identification information and position information of the first data flow; a second CDN center node in the at least one CDN center node sends a first pull stream request to the first CDN center node based on the first information; and the first CDN center node sends the first data stream to the second CDN center node. According to the invention, time delay and network resources can be reduced.
Need to check novelty before this filing date? Find Prior Art

Description

(19) State Intellectual Property Office (12) Invention Patent Application (10) Application Publication Number (43) Application Publication Date (21) Application Number 202410939054.8 (22) Application Date 2024.07.12 (71) Applicant Huawei Cloud Computing Technology Co., Ltd. Address 550025, Guizhou Province, Guiyang City, Gui'an New District, Qianzhong Avenue, Xinggong Road, Huawei Cloud Data Center (72) Inventor Zhu Jianping (74) Patent Agency Beijing Sangao Yongxin Intellectual Property Agency Co., Ltd. 11138 Patent Attorney Yan Jing (51) Int.Cl. H04N 21 / 2187 (2011.01) H04N 21 / 2343 (2011.01) H04N 21 / 262 (2011.01) (54) Invention Title: Method, Apparatus, System, and Storage Medium for Processing Data Streams (57) Abstract: This application discloses a method, apparatus, system, and storage medium for processing data streams, belonging to the field of communications. The method is applied to a content distribution system, which includes a first CDN central node, and the area where the first CDN central node is located also includes at least one CDN central node. The method includes: the first CDN central node receiving a first data stream of a live streaming service; the first CDN central node sending first information of the first data stream to at least one CDN central node, the first information including the identification information and location information of the first data stream; a second CDN central node among the at least one CDN central node sending a first pull request to the first CDN central node based on the first information; and the first CDN central node sending the first data stream to the second CDN central node. This application can reduce latency and network resources. Claims 6 pages, Description 29 pages, Drawings 12 pages, CN 121357336 A 2026.01.16 CN 1 21 35 73 36 A 1. A method for processing data streams, characterized in that the method is applied to a content distribution system, the content distribution system including a first content distribution network (CDN) central node, the region where the first CDN central node is located further including at least one CDN central node, the method including: the first CDN central node receiving a first data stream of a live streaming service; the first CDN central node sending first information of the first data stream to the at least one CDN central node respectively, the first information including identification information and location information of the first data stream; a second CDN central node among the at least one CDN central nodes sending a first pull request to the first CDN central node based on the first information; the first CDN central node sending the first data stream to the second CDN central node. 2. The method of claim 1, characterized in that the first pull request carries a transcoding template, the first...Sending the first data stream from a CDN central node to a second CDN central node includes: the first CDN central node transcoding the first data stream based on the transcoding template to obtain the transcoded first data stream; and the first CDN central node sending the transcoded first data stream to the second CDN central node. 3. The method as described in claim 1 or 2, wherein the second CDN central node sending a first pull request to the first CDN central node based on the first information includes: after receiving a second pull request from a terminal device, the second CDN central node sending the first pull request to the first CDN central node based on the first information. 4. The method as described in claim 1, characterized in that, before the first pull request carries a transcoding template, and before the second CDN central node sends the first pull request to the first CDN central node based on the first information, the method further includes: a third CDN central node among the at least one CDN central node sending a second pull request to the second CDN central node, the second pull request being used to request the second CDN central node to send the first pull request to the first CDN central node based on the first information; after the first CDN central node sends the first data stream to the second CDN central node, the method further includes: the second CDN central node transcoding the first data stream based on the transcoding template to obtain the transcoded first data stream; and the second CDN central node sending the transcoded first data stream to the third CDN central node. 5. The method as described in claim 1 or 2, wherein the second CDN center node includes a first scheduling strategy, and before the second CDN center node sends a first pull request to the first CDN center node based on the first information, it further includes: a third CDN center node among the at least one CDN center node sending a second pull request to the second CDN center node; the second CDN center node sending the first pull request to the first CDN center node based on the first information includes: when the second CDN center node selects the first CDN center node to transcode the data stream based on the first scheduling strategy, it sends the first pull request to the first CDN center node based on the first information and the second pull request. 6. The method as described in claim 4 or 5, wherein the third CDN center node includes a second scheduling strategy, and the third CDN center node sending the second pull request to the second CDN center node includes: when the third CDN center node selects the second CDN center node based on the second scheduling strategy, it sends the first pull request to the first CDN center node based on the first information and the second pull request.7. The method as described in claim 2, further comprising: the first CDN central node sending second information to the global management platform and the at least one CDN central node, the second information including the identification information and location information of the transcoded first data stream, the global management platform being used to send the second information to CDN central nodes other than the first CDN central node; wherein, the timestamp of each of the at least one CDN central nodes receiving the second information sent by the first CDN central node is earlier than the timestamp of receiving the second information sent by the global management platform. 8. The method according to any one of claims 1-7, wherein the region further includes a live streaming origin data platform, the first CDN central node includes a third scheduling strategy, the first pull request carries a transcoding template, and the method further includes: the first CDN central node sending the first data stream to the live streaming origin data platform; when the first CDN central node selects the live streaming origin data platform to transcode the data stream based on the third scheduling strategy, it sends a third pull request to the live streaming origin data platform, the third pull request carrying the transcoding template; the live streaming origin data platform transcodes the first data stream based on the transcoding template to obtain a transcoded first data stream; the live streaming origin data platform sends the transcoded first data stream to the first CDN central node; the first CDN central node sending the first data stream to the second CDN central node includes: the first CDN central node sending the transcoded first data stream to the second CDN central node. 9. The method according to any one of claims 1-8, wherein the range of the region is determined based on the latency and / or distance between the multiple CDN central nodes included in the region. 10. A method for processing a data stream, characterized in that the method is applied to a live streaming origin data platform included in a region, the live streaming origin data platform including a fourth scheduling strategy, the region also including a third-party transcoding service platform and a content delivery network (CDN) central node, the method comprising: the live streaming origin data platform receiving a first data stream sent by the CDN central node; the live streaming origin data platform receiving a third pull request, the third pull request carrying a transcoding template; when the live streaming origin data platform selects the third-party transcoding service platform to transcode the data stream based on the fourth scheduling strategy, the live streaming origin data platform sends a fourth pull request and the first data stream to the third-party transcoding service platform, the fourth pull request being used to instruct the third-party transcoding service platform to transcode the first data stream based on the transcoding template, to obtain the transcoded first data stream;The live streaming source data platform receives the transcoded first data stream sent by the third-party transcoding service platform. 11. The method of claim 10, further comprising: when the live streaming source data platform selects the live streaming source data platform to transcode the data stream based on the fourth scheduling strategy, transcoding the first data stream based on the transcoding template to obtain the transcoded first data stream. 12. The method of claim 10 or 11, further comprising: the live streaming source data platform sending third information to the global management platform, the third information including the identification information and location information of the transcoded first data stream. Claims 2 / 6, Page 3, CN 121357336, A 13. A method for processing data streams, characterized in that the method is applied to a global management platform, the global management platform being used to manage a live streaming source data platform and a content delivery network (CDN) central node included in a region, the CDN central node being used to send a first data stream to the live streaming source data platform, the method comprising: the global management platform receiving second information sent by the CDN central node when transcoding the first data stream to obtain a transcoded first data stream, the second information including identification information and first location information of the transcoded first data stream; the global management platform receiving third information sent by the live streaming source data platform when transcoding the first data stream to obtain a transcoded first data stream, the third information including identification information and second location information of the transcoded first data stream; the global management platform determining, based on the second information and the third information, that when the CDN central node and the live streaming source data platform repeatedly transcode the first data stream, stopping one of the CDN central node and the live streaming source data platform from continuing to transcode the first data stream. 14. The method as described in claim 13, wherein the global management platform stops one of the CDN central node and the live streaming origin data platform from continuing to transcode the first data stream, comprising: the global management platform sending a first stop command to the CDN central node, the first stop command being used to instruct the CDN central node to stop continuing to transcode the first data stream; or, the global management platform sending a second stop command to the live streaming origin data platform, the second stop command being used to instruct the live streaming origin data platform to stop continuing to transcode the first data stream. 15. A content distribution system, wherein the content distribution system includes a first content distribution network (CDN) central node, and the region where the first CDN central node is located further includes at least one CDN central node; the first CDN central node is used to receive a first data stream from a live streaming service;The first CDN central node is further configured to send first information of the first data stream to the at least one CDN central node respectively, the first information including the identification information and location information of the first data stream; the second CDN central node among the at least one CDN central nodes is configured to send a first pull request to the first CDN central node based on the first information; the first CDN central node is further configured to send the first data stream to the second CDN central node. 16. The content distribution system of claim 15, wherein the first pull request carries a transcoding template, and the first CDN central node is configured to: transcode the first data stream based on the transcoding template to obtain the transcoded first data stream; and send the transcoded first data stream to the second CDN central node. 17. The content distribution system of claim 15 or 16, wherein the second CDN central node is configured to send the first pull request to the first CDN central node based on the first information after receiving a second pull request from a terminal device. 18. The content distribution system as described in claim 15, wherein the first pull request carries a transcoding template; the third CDN center node among the at least one CDN center node is configured to send a second pull request to the second CDN center node, the second pull request being configured to request the second CDN center node to send the first pull request to the first CDN center node based on the first information; the second CDN center node is further configured to transcode the first data stream based on the transcoding template to obtain the first data stream after transcoding; the second CDN center node is further configured to send the transcoded first data stream to the third CDN center node. 19. The content distribution system of claim 15 or 16, wherein the second CDN center node includes a first scheduling strategy; a third CDN center node among the at least one CDN center node is configured to send a second pull request to the second CDN center node; and the second CDN center node is configured to send the first pull request to the first CDN center node based on the first information and the second pull request when selecting the first CDN center node to transcode the data stream based on the first scheduling strategy. 20. The content distribution system of claim 18 or 19, wherein the third CDN center node includes a second scheduling strategy; and the third CDN center node is configured to send the second pull request to the second CDN center node when selecting the second CDN center node based on the second scheduling strategy.21. The content distribution system as described in claim 16, characterized in that the content distribution system further includes a global management platform; the first CDN center node is further configured to send second information to the global management platform and the at least one CDN center node, the second information including the identification information and location information of the transcoded first data stream; the global management platform is configured to send the second information to CDN center nodes other than the first CDN center node; wherein, the timestamp of each CDN center node receiving the second information sent by the first CDN center node is earlier than the timestamp of receiving the second information sent by the global management platform. 22. The content distribution system according to any one of claims 15-21, characterized in that the region further includes a live streaming origin data platform, the first CDN center node includes a third scheduling strategy, and the first pull request carries a transcoding template; the first CDN center node is further configured to send the first data stream to the live streaming origin data platform; the first CDN center node is further configured to send a third pull request to the live streaming origin data platform when selecting the live streaming origin data platform to transcode the data stream based on the third scheduling strategy, the third pull request carrying the transcoding template; the live streaming origin data platform is configured to transcode the first data stream based on the transcoding template to obtain the transcoded first data stream; the live streaming origin data platform is further configured to send the transcoded first data stream to the first CDN center node; the first CDN center node is configured to send the transcoded first data stream to the second CDN center node. 23. The content distribution system according to any one of claims 15-22, characterized in that the range of the region is determined based on the latency and / or distance between the multiple CDN center nodes included in the region. 24. An apparatus for processing data streams, characterized in that the apparatus includes a fourth scheduling strategy, and the area where the apparatus is located (pages 4 / 6 of claim 5, CN 121357336 A) further includes a third-party transcoding service platform and a content delivery network (CDN) central node, the apparatus comprising: a receiving unit, configured to receive a first data stream sent by the CDN central node; the receiving unit is further configured to receive a third pull request, the third pull request carrying a transcoding template; and a sending unit, configured to send a fourth pull request and the first data stream to the third-party transcoding service platform when the fourth scheduling strategy selects the third-party transcoding service platform to transcode the data stream, the fourth pull request instructing the third-party transcoding service platform to transcode the first data stream based on the transcoding template to obtain the transcoded first data stream;The receiving unit is further configured to receive the transcoded first data stream sent by the third-party transcoding service platform. 25. The apparatus of claim 24, wherein the apparatus further comprises: a processing unit; the processing unit is configured to, when selecting the apparatus to transcode the data stream based on the fourth scheduling strategy, transcode the first data stream based on the transcoding template to obtain the transcoded first data stream. 26. The apparatus of claim 24 or 25, wherein the sending unit is further configured to send third information to the global management platform, the third information including the identification information and location information of the transcoded first data stream. 27. An apparatus for processing data streams, characterized in that the apparatus is used to manage a live streaming origin data platform and a content delivery network (CDN) central node included in a region, the CDN central node being used to send a first data stream to the live streaming origin data platform, the apparatus comprising: a receiving unit, used to receive second information sent by the CDN central node when transcoding the first data stream to obtain a transcoded first data stream, the second information including identification information and first location information of the transcoded first data stream; the receiving unit is further used to receive third information sent by the live streaming origin data platform when transcoding the first data stream to obtain a transcoded first data stream, the third information including identification information and second location information of the transcoded first data stream; and a processing unit, used to stop one of the CDN central node and the live streaming origin data platform from continuing to transcode the first data stream when it is determined, based on the second information and the third information, that the CDN central node and the live streaming origin data platform are repeatedly transcoding the first data stream. 28. The apparatus of claim 27, further comprising a sending unit, the sending unit being configured to: send a first stop command to the CDN central node, the first stop command being configured to instruct the CDN central node to stop transcoding the first data stream; or, send a second stop command to the live streaming source data platform, the second stop command being configured to instruct the live streaming source data platform to stop transcoding the first data stream. 29. A computing device cluster, comprising at least one computing device, each computing device comprising a processor and a memory; the processor of the at least one computing device being configured to execute instructions stored in the memory of the at least one computing device to cause the computing device cluster to perform the method of any one of claims 1-14. 30. A computer-readable storage medium, comprising computer program instructions, wherein when the computer program instructions are executed by the computing device cluster, the computing device cluster performs the method of any one of claims 1-14. ClaimsPage 5 / 6 6 CN 121357336 A 31. A computer program product containing instructions, characterized in that, when the instructions are executed by a cluster of computing devices, the cluster of computing devices causes the cluster of computing devices to perform the method as described in any one of claims 1-14. Claims Page 6 / 6 7 CN 121357336 A Method, apparatus, system and storage medium for processing data streams Technical Field

[0001] This application relates to the field of communications, and particularly to a method, apparatus, system and storage medium for processing data streams. Background Art

[0002] A live streaming system includes multiple content delivery network (CDN) central nodes and a live streaming source station data platform. A broadcaster user can access the first CDN central node among multiple CDN central nodes and push the data stream generated by the live stream to the first CDN central node. The first CDN central node sends the data stream to the live streaming source station data platform.

[0003] In related technologies, a first viewer user may request the first CDN central node to pull the data stream of the broadcaster user, and the first CDN central node sends the requested data stream to the first viewer user. It is also possible that a second viewer user requests the data stream of the broadcaster user from the second CDN center node among multiple CDN center nodes, and the second CDN center node then requests the data stream from the live streaming origin data platform. The live streaming origin data platform sends the requested data stream to the second CDN center node, and the second CDN center node forwards the requested data stream to the second viewer user.

[0004] In related technologies, it is possible to request the same data stream from both the first CDN center node and the live streaming origin data platform, resulting in a waste of network resources. Summary of the Invention

[0005] This application provides a method, apparatus, system, and storage medium for processing data streams to save network resources. The technical solution is as follows:

[0006] In a first aspect, this application provides a method for processing data streams, the method being applied to a content distribution system, the content distribution system including a first content distribution network CDN center node, and the area where the first CDN center node is located also including at least one CDN center node. In the method, the first CDN center node receives the first data stream of the live streaming service. The first CDN central node sends first information of the first data stream to at least one CDN central node, the first information including the identifier information and location information of the first data stream. The second CDN central node, one of the at least one CDN central nodes, sends a first pull request to the first CDN central node based on the first information. The first CDN central node sends the first data stream to the second CDN central node.

[0007] Since the first CDN central node and at least one CDN central node are located in the same region, the first CDN...After receiving the first data stream sent by the live user, the central node sends the first information of the first data stream to at least one CDN central node. Each of the at least one CDN central nodes receives the first information quickly. This ensures that when a viewer requests to pull the live user's data stream from a second CDN central node after the live user sends the first data stream, the second CDN central node receives the first information earlier than it receives the viewer's pull request. Therefore, based on the first information, it can be determined that the data stream requested by the viewer is located on the first CDN central node, and the viewer pulls the data stream from the first CDN central node. In other words, when a user in a region pulls the live user's data stream, the first information allows the data stream to be pulled from the CDN central node in the region, thereby reducing the latency of pulling the data stream and network resources.

[0008] In one possible implementation, the first pull request carries a transcoding template. The first CDN central node transcodes the first data stream based on the transcoding template to obtain the transcoded first data stream. The first CDN central node sends the transcoded first data stream to the second CDN central node (page 1 / 29, CN 121357336 A). This ensures that all pull requests within the region are forwarded to the first CDN central node, which then transcodes the first data stream, preventing other devices from transcoding it and thus avoiding redundant transcoding, saving computing and network resources.

[0009] In another possible implementation, after receiving a second pull request from a terminal device, the second CDN central node sends a first pull request to the first CDN central node based on first information. Since the second CDN central node receives the first information earlier than it receives the second pull request from the terminal device, it can accurately determine the data stream that the terminal device needs to pull from the first CDN central node based on the first information, ensuring that the data stream can be successfully pulled from the first CDN central node.

[0010] In another possible implementation, the first pull request carries a transcoding template. At least one third CDN central node sends a second pull request to a second CDN central node. The second pull request is used to request the second CDN central node to send the first pull request to the first CDN central node based on the first information. The second CDN central node transcodes the first data stream based on the transcoding template to obtain the transcoded first data stream. The second CDN central node sends the transcoded first data stream to the third CDN central node.

[0011] Since the third CDN central node can choose the second CDN central node to transcode, that is, to send the second pull request to the second CDN central node. The second CDN central node obtains the first data stream from the first CDN central node based on the first information.Transcoding the first data stream allows for flexible selection of who performs the transcoding. Furthermore, if the first CDN central node has transcoding capabilities, the transcoding task can be shared by the second CDN central node, improving transcoding efficiency; if the first CDN central node lacks transcoding capabilities, the third CDN central node selects the second CDN central node for transcoding, ensuring successful transcoding.

[0012] In another possible implementation, the second CDN central node includes a first scheduling strategy, whereby at least one third CDN central node sends a second pull request to the second CDN central node. When the second CDN central node selects the first CDN central node to transcode the data stream based on the first scheduling strategy, it sends a first pull request to the first CDN central node based on the first information and the second pull request. This first scheduling strategy controls who performs the transcoding, improving transcoding flexibility.

[0013] In another possible implementation, the third CDN central node includes a second scheduling strategy, whereby the third CDN central node sends a second pull request to the second CDN central node when selecting the second CDN central node based on the second scheduling strategy. This second scheduling strategy controls where to request streaming, improving the flexibility of streaming.

[0014] In another possible implementation, the first CDN central node sends second information to at least one CDN central node and the global management platform. The second information includes the identification information and location information of the transcoded first data stream. The global management platform is used to send the second information to CDN central nodes other than the first CDN central node. The timestamp of each CDN central node receiving the second information sent by the first CDN central node is earlier than the timestamp of receiving the second information sent by the global management platform. This allows each CDN central node to quickly obtain the second information. When a viewer requests to pull the transcoded first data stream, the CDN central node can quickly pull the transcoded first data stream from the first CDN central node based on the second information, improving the streaming rate and avoiding repeated transcoding of the first data stream.

[0015] In another possible implementation, the region also includes a live streaming origin data platform, the first CDN central node includes a third scheduling strategy, and the first streaming request carries a transcoding template. The first CDN central node sends the first data stream to the live streaming origin data platform. When the first CDN central node selects the live streaming origin data platform to transcode the data stream based on the third scheduling strategy, it sends a third pull request to the live streaming origin data platform, which carries a transcoding template. The live streaming origin data platform instruction manual (page 2 / 29, CN 121357336 A) transcodes the first data stream based on the transcoding template to obtain the transcoded first data stream. The live streaming origin data platform then sends the first data stream to the second CDN central node.A CDN central node sends a transcoded first data stream. The first CDN central node sends the transcoded first data stream to a second CDN central node. This uses a third scheduling strategy to control who performs the transcoding, improving transcoding flexibility. Alternatively, if the first CDN central node has transcoding capabilities, a live streaming origin data platform can be selected for transcoding, sharing the transcoding task of the first CDN central node and improving transcoding efficiency. Or, if the first CDN central node does not have transcoding capabilities, a live streaming origin data platform can be selected for transcoding, ensuring successful transcoding.

[0016] In another possible implementation, the range of the region is determined based on the latency and / or distance between multiple CDN central nodes included in the region. This ensures that at least one CDN central node can quickly receive the first information after the first CDN central node sends the first information.

[0017] In a second aspect, this application provides a method for processing data streams, applied to a live streaming origin data platform included in a region. The live streaming origin data platform includes a fourth scheduling strategy, and the region also includes a third-party transcoding service platform and a content delivery network (CDN) central node. In the method, the live streaming origin data platform receives a first data stream sent by the CDN central node. The live streaming origin data platform receives a third pull request, which carries a transcoding template. When the live streaming origin data platform selects a third-party transcoding service platform to transcode the data stream based on a fourth scheduling strategy, it sends a fourth pull request and the first data stream to the third-party transcoding service platform. The fourth pull request instructs the third-party transcoding service platform to transcode the first data stream based on the transcoding template to obtain the transcoded first data stream. The live streaming origin data platform receives the transcoded first data stream sent by the third-party transcoding service platform.

[0018] In this way, the transcoding tasks of the live streaming origin data platform are diverted through the third-party transcoding service platform. For example, when the idle resources of the live streaming origin data platform for transcoding are insufficient, the transcoding is performed in a timely manner through the third-party transcoding service platform. As another example, when the transcoding cost of the live streaming origin data platform is higher than the transcoding cost of the third-party transcoding service platform, the transcoding cost is reduced through the third-party transcoding service platform.

[0019] In one possible implementation, when the live streaming source data platform selects another live streaming source data platform to transcode the data stream based on the fourth scheduling strategy, it transcodes the first data stream based on the transcoding template to obtain the transcoded first data stream. This allows for flexible control over who performs the transcoding through the fourth scheduling strategy. For example, when the live streaming source data platform has sufficient idle resources for transcoding, it performs the transcoding promptly. Another example is when the transcoding cost of the live streaming source data platform is lower than that of a third-party transcoding service platform, the live streaming source data platform reduces the transcoding cost.

[0020] In another possible implementation, the live streaming source data platform sends third information to the global management platform.The third information includes the identification information and location information of the transcoded first data stream. This third information is used to notify the global management platform that the live streaming source data platform is transcoding the first data stream, so that the global management platform can determine which devices are repeatedly transcoding the first data stream using third-party information.

[0021] In a third aspect, a method for processing data streams is provided, the method being applied to a global management platform, which manages live streaming source data platforms and content delivery network (CDN) central nodes within a region, and the CDN central nodes are used to send the first data stream to the live streaming source data platform. In the method, the global management platform receives second information sent by the CDN central node when transcoding the first data stream to obtain the transcoded first data stream, the second information including the identification information and first location information of the transcoded first data stream. The global management platform also receives third information sent by the live streaming source data platform when transcoding the first data stream to obtain the transcoded first data stream, the third information including the identification information and second location information of the transcoded first data stream. When the global management platform determines, based on the second and third information, that the CDN central node and the live streaming origin data platform are repeatedly transcoding the first data stream, it stops one of the CDN central node and the live streaming origin data platform from continuing to transcode the first data stream. This allows one device to continue transcoding the first data stream, stopping repeated transcoding and saving computing and network resources.

[0022] In one possible implementation, the global management platform sends a first stop command to the CDN central node, instructing the CDN central node to stop transcoding the first data stream; or, the global management platform sends a second stop command to the live streaming origin data platform, instructing the live streaming origin data platform to stop transcoding the first data stream.

[0023] In another possible implementation, the global management platform obtains the CDN central node's scheduling policy and sends the scheduling policy to the CDN central node. This allows the CDN central node to flexibly select the device used for transcoding through the scheduling policy.

[0024] In a fourth aspect, this application provides a content distribution system for performing the method in the first aspect or any possible implementation thereof. Specifically, the content distribution system includes devices for performing the method in the first aspect or any possible implementation thereof.

[0025] In a fifth aspect, this application provides an apparatus for processing data streams for performing the method in the second aspect or any possible implementation thereof. Specifically, the apparatus includes units for performing the method in the second aspect or any possible implementation thereof.

[0026] Sixthly, this application provides an apparatus for processing data streams, used to perform the method in the third aspect or any possible implementation of the third aspect. Specifically, the apparatus includes units for performing the method in the third aspect or any possible implementation of the third aspect.

[0027] Seventhly, this application provides a computing device cluster, the computing device cluster including at least one computing device, each computing device including a processor and a memory; the processor of the at least one computing device is used to execute instructions stored in the memory of the at least one computing device to cause the computing device cluster to perform the method in the first aspect, the second aspect, the third aspect, any possible implementation of the first aspect, any possible implementation of the second aspect, or any possible implementation of the third aspect.

[0028] Eighthly, this application provides a computer program product including instructions, which, when executed by a computing device cluster, cause the computing device cluster to perform the method in the first aspect, the second aspect, the third aspect, any possible implementation of the first aspect, any possible implementation of the second aspect, or any possible implementation of the third aspect.

[0029] In a ninth aspect, this application provides a computer-readable storage medium including computer program instructions, wherein when the computer program instructions are executed by a computing device cluster, the computing device cluster executes the methods of the first aspect, the second aspect, the third aspect, any possible implementation of the first aspect, any possible implementation of the second aspect, or any possible implementation of the third aspect.

[0030] In a tenth aspect, this application provides a chip including a memory and a processor, wherein the memory is used to store computer instructions, and the processor is used to call and run the computer instructions from the memory to execute the methods of the first aspect, the second aspect, the third aspect, any possible implementation of the first aspect, any possible implementation of the second aspect, or any possible implementation of the third aspect.

[0031] FIG1 is a schematic diagram of the structure of a content distribution system provided in an embodiment of the present application;

[0032] FIG2 is a schematic diagram of the structure of another content distribution system provided in an embodiment of the present application;

[0033] FIG3 is a schematic diagram of the structure of another content distribution system provided in an embodiment of the present application; Specification 4 / 29 pages 11 CN 121357336 A

[0034] FIG4 is a schematic diagram of the structure of another content distribution system provided in an embodiment of the present application;

[0035] FIG5 is a flowchart of a method for processing data streams provided in an embodiment of the present application;

[0036] FIG6 is a schematic diagram of the structure of another content distribution system provided in an embodiment of the present application;

[0037] FIG7 is a flowchart of another method for processing data streams provided in an embodiment of the present application;

[0038] Figure 8 is a schematic diagram of another content distribution system provided in the embodiments of this application;

[0039] Figure 9 is a schematic diagram of another content distribution system provided in the embodiments of this application;

[0040] Figure 10 is a schematic diagram of a device for processing data streams provided in the embodiments of this application;

[0041] Figure 11 is a schematic diagram of another device for processing data streams provided in the embodiments of this application;

[0042] Figure 12 is a schematic diagram of a computing device provided in the embodiments of this application;

[0043] Figure 13 is a schematic diagram of a cluster structure for processing data streams provided in the embodiments of this application;

[0044] Figure 14 is a schematic diagram of another cluster structure for processing data streams provided in the embodiments of this application. Detailed Description

[0045] The relevant concepts appearing in the embodiments of this application are introduced below:

[0046] The first CDN central node, the second CDN central node, and the third CDN central node are different nodes in the same region.

[0047] The first pull request, the second pull request, the third pull request, the fourth pull request, and the fifth pull request are used to request the pull of data streams.

[0048] Wherein, the first pull request, the second pull request, the third pull request, and the fifth pull request may be the same, or the four pull requests may have the same content but different source and destination addresses.

[0049] Wherein, the fifth pull request is a pull request sent by the viewer to the third CDN central node. The second pull request is a pull request sent by the viewer to the second CDN central node, or it is a pull request sent by the third CDN central node to the second CDN central node after receiving the fifth pull request. The first pull request is a pull request sent by the second CDN central node to the first CDN central node after receiving the second pull request. The third pull request is a pull request sent by the first CDN central node, the second CDN central node, or the third CDN central node to the live streaming origin data platform when selecting the live streaming origin data platform to transcode the data stream. The fourth pull request is a pull request sent by the live streaming origin data platform to the third-party transcoding service platform when selecting the third-party transcoding service platform to transcode the data stream.

[0050] Referring to Figure 1, this application embodiment provides a content distribution system 100, which covers multiple regions for running live streaming services. The content distribution system 100 includes a global management platform 101, and multiple live streaming source data platforms 102 and multiple CDN center nodes 103 included in each region.

[0051] The global management platform 101 can communicate with each live streaming source data platform 102 included in each region, and can communicate with each CDN center node 103 included in each region.

[0052] Each CDN central node 103 in the same region can communicate with each other, and each CDN central node 103 in the same region can communicate with each live streaming source data platform 102 in that region.

[0053] In some embodiments, a region can be a region or an administrative region, etc. For example, a region can be a city, province, country or continent, etc. Optionally, the world includes multiple regions, and the global management platform 103 can manage the live streaming source data platforms 102 and CDN central nodes 103 in the multiple regions included globally.

[0054] In some embodiments, multiple live streaming source data platforms 102 in a region include at least one main live streaming source data platform, and one or more backup live streaming source data platforms corresponding to at least one main live streaming source data platform.

[0055] In some embodiments, the live streaming source data platforms 102 in the content distribution system 100 are deployed in a distributed manner. Optionally, the live streaming origin data platform 102 in the content distribution system 100 is deployed on the cloud. Optionally, the CDN central node 103 in the content distribution system 100 may also be deployed on the cloud. The cloud where the live streaming origin data platform 102 is located and the cloud where the CDN central node 103 is located may be different. For example, the cloud where the live streaming origin data platform 102 is located may be at a higher level than the cloud where the CDN central node 103 is located.

[0056] Optionally, the CDN central node 103 in the content distribution system 100 may be a CDN acceleration node, a CDN acceleration center node, or a CDN edge node. Optionally, the CDN central node 103 includes one or more physical devices and / or logical devices. For example, the CDN central node 103 includes one or more servers.

[0057] In some embodiments, the range of a region may be determined based on factors such as latency and / or distance between multiple CDN central nodes 103 in the region. For example, the CDN central node 103 in a region may satisfy one or more of the following conditions: a first latency condition, a second latency condition, or a distance condition.

[0058] The first latency condition is that the transmission latency between any two CDN central nodes 102 in a region meets the latency threshold required by the live streaming service.

[0059] Optionally, the latency threshold required by the live streaming service may be the time length allowed by the live streaming service from when the broadcaster pushes the data stream to when the first viewer pulls the first frame of the data stream. After the broadcaster pushes the data stream, the viewer requests to pull the data stream at least after this latency threshold.

[0060] Optionally, the transmission latency between any two CDN central nodes 102 in a region is less than or equal to the latency threshold required by the live streaming service, so as to achieve the latency threshold required by the live streaming service.

[0061] The distance condition is that for any CDN center node 102 located in the same area, the distance between the CDN center node 102 and each other CDN center node 102 in the same area may be less than the distance between the CDN center node 102 and the global management platform 101.

[0062] For any CDN center node 102 located in the same area, and for other CDN center nodes 102 in the same area besides the CDN center node 102, the second latency condition that the CDN center node 102 may satisfy is: the transmission latency between the CDN center node 102 and the other CDN center nodes 102 is less than the sum of the transmission latency between the CDN center node 102 and the global management platform 101 and the transmission latency between the global management platform 101 and the other CDN center nodes 102. The latency threshold required for live streaming services is less than this sum of values.

[0063] For example, referring to Figure 2, multiple regions include a first region and a second region. The first region includes a first live streaming source data platform 1021, a second live streaming source data platform 1022, a first CDN central node 1031, a second CDN central node 1032, and a third CDN central node 1033. The first live streaming source data platform 1021 is the primary live streaming source data platform, and the second live streaming source data platform 1022 is the backup live streaming source data platform.

[0064] The global management platform 101 can communicate with the first live streaming source data platform 1021, the second live streaming source data platform 1022, the first CDN central node 1031, the second CDN central node 1032, and the third CDN central node 1033. The first live streaming source data platform 1021 can communicate with the first CDN central node 1031, the second CDN central node 1032, and the third CDN central node 1033. The second live streaming source data platform 1022 can communicate with the first CDN central node 1031, the second CDN central node 1032, and the third CDN central node 1033. The first CDN central node 1031, the second CDN central node 1032, and the third CDN central node 1033 can communicate with each other.

[0065] In the first area, the transmission latency between the first CDN central node 1031 and the second CDN central node 1032 meets the latency threshold required for live streaming services, the transmission latency between the second CDN central node 1032 and the third CDN central node 1033 meets the latency threshold required for live streaming services, and the transmission latency between the third CDN central node 1033 and the first CDN central node 1031 meets the latency threshold required for live streaming services.

[0066] The first CDN central node 1031 may meet the following second latency condition: the first CDN central node 1031 and the second CDN central node 1032 meet the latency threshold required for live streaming services.The transmission latency between CDN central nodes 1032 is less than the sum of the transmission latency between the first CDN central node 1031 and the global management platform 101 and the transmission latency between the global management platform 101 and the second CDN central node 1032; the transmission latency between the first CDN central node 1031 and the third CDN central node 1033 is less than the sum of the transmission latency between the first CDN central node 1031 and the global management platform 101 and the transmission latency between the global management platform 101 and the third CDN central node 1033. And / or, the distance between the first CDN central node 1031 and the second CDN central node 1032, and the distance between the first CDN central node 1031 and the third CDN central node 1033, are both less than the distance between the first CDN central node 1031 and the global management platform 1031.

[0067] The second CDN center node 1032 in the first region also satisfies the above-mentioned distance condition and / or second latency condition, and the third CDN center node 1033 also satisfies the above-mentioned distance condition and / or second latency condition.

[0068] The second region includes a third live streaming source data platform 1023, a fourth live streaming source data platform 1024, a fourth CDN center node 1034, a fifth CDN center node 1035, and a sixth CDN center node 1036. The third live streaming source data platform 1023 is the primary live streaming source data platform, and the fourth live streaming source data platform 1024 is the backup live streaming source data platform.

[0069] The global management platform 101 can communicate with the third live streaming source data platform 1023, the fourth live streaming source data platform 1024, the fourth CDN center node 1034, the fifth CDN center node 1035, and the sixth CDN center node 1036. The third live streaming origin data platform 1023 can communicate with the fourth CDN central node 1034, the fifth CDN central node 1035, and the sixth CDN central node 1036. The fourth live streaming origin data platform 1024 can communicate with the fourth CDN central node 1034, the fifth CDN central node 1035, and the sixth CDN central node 1036. The fourth CDN central node 1034, the fifth CDN central node 1035, and the sixth CDN central node 1036 can communicate with each other.

[0070] In the second region, the transmission latency between the fourth CDN central node 1034 and the fifth CDN central node 1035 meets the latency threshold required for live streaming services, the transmission latency between the fifth CDN central node 1035 and the sixth CDN central node 1036 meets the latency threshold required for live streaming services, and the transmission latency between the sixth CDN central node 1036 and the fourth CDN central node 1034 meets the latency threshold required for live streaming services.

[0071] In the second region, the fourth CDN central node 1034 satisfies the above-mentioned distance condition and / or the second delay condition.The fifth CDN center node 1035 satisfies the above-mentioned distance condition and / or the second latency condition, and the sixth CDN center node 1036 satisfies the above-mentioned distance condition and / or the second latency condition.

[0072] Referring to Figure 3, for any region, the region may also include a third-party transcoding service platform 104. The live streaming source data platform in the region can communicate with the third-party transcoding service platform 104. The third-party transcoding service platform 104 and the above-mentioned live streaming source data platform 102 belong to different companies, organizations, or groups.

[0073] For example, referring to Figure 3, the first live streaming source data platform 1031 in the first region can communicate with the third-party transcoding service platform 104. The first live streaming source data platform 1031 and the third-party transcoding service platform 104 are platforms from different companies.

[0074] Referring to Figure 4, for live streaming users located in the region, the live streaming users can communicate with the CDN center node 103 in the region and can push the first data stream generated by the live streaming to the CDN center node 103. For viewers located within the region, viewers can communicate with the CDN central node 103 within the region and request the CDN central node 103 to pull the second data stream.

[0075] The second data stream is obtained by transcoding the first data stream. The content of the first data stream and the second data stream are the same, but the parameters of the first data stream and the second data stream are different. The parameters of the first data stream may include one or more of the following, as shown on page 7 / 29 of the specification: bitrate, frame rate, resolution, or the width and height of the image in the first data stream. The parameters of the second data stream may include one or more of the following: bitrate, frame rate, resolution, or the width and height of the image in the second data stream.

[0076] Some or all of the CDN central nodes 103 within the region have transcoding functions.

[0077] Optionally, the CDN central node 103 may include a transcoding component, which has transcoding functions. For example, referring to Figure 4, both the first CDN central node 1031 and the second CDN central node 1032 in the first region include transcoding components, and both the first CDN central node 1031 and the second CDN central node 1032 have transcoding functions. Both the fourth CDN central node 1034 and the sixth CDN central node 1036 in the second region include transcoding components, and both the fourth CDN central node 1034 and the sixth CDN central node 1036 have transcoding functions.

[0078] Optionally, the transcoding component includes a transcoding virtual instance or a transcoding physical machine, etc. For example, a transcoding virtual instance may include a virtual machine and / or a container, etc., and a transcoding physical machine may be a transcoding card, etc.

[0079] Each live streaming source station data platform 102 within the region has a transcoding function. Optionally, the live streaming source station data platform 102 may include a transcoding component.

[0080] In some embodiments, both the CDN central node 103 and the live streaming origin data platform 102 within the region include at least one transcoding template, and each transcoding template is used to define different data streams. Optionally, the transcoding template includes parameters of the data stream defined by the transcoding template, that is, the transcoding template includes one or more of the following: the bitrate, frame rate, resolution or width and height of the data stream, etc.

[0081] Taking Figure 4 as an example, the process of live streaming users pushing live streaming data streams and viewers pulling data streams is described below: The first live streaming user in the first region pushes the first data stream to the first CDN central node 1031. The first CDN central node 1031 receives the first data stream, sends the first information of the first data stream to the global management platform 101, and sends the first data stream to multiple live streaming origin data platforms 102 within the first region. The first information of the first data stream includes the identification information and location information of the first data stream.

[0082] Optionally, when the first live streaming user pushes the first data stream, he / she also sends the push domain name of the live streaming application to the first CDN central node 1031.

[0083] Optionally, the location information is the location information of the first CDN central node 1031.

[0084] In the first region, there are multiple live streaming source data platforms 102 associated with the push domain name of the live streaming application. The live streaming application also has a pull domain name, and the multiple live streaming source data platforms 102 are also associated with the pull domain name of the live streaming application. Therefore, the first CDN central node 1031 can send the first data stream to the multiple live streaming source data platforms 102 associated with the push domain name.

[0085] The global management platform 101 receives the first information of the first data stream and sends the first information of the first data stream to CDN central nodes other than the first CDN central node 1031. For example, referring to FIG4, the global management platform 101 sends the first information of the first data stream to the second CDN central node 1032 and the third CDN central node 1033 in the first region, and sends the first information of the first data stream to the fourth CDN central node 1034, the fifth CDN central node 1035 and the sixth CDN central node 1036 in the second region. This ensures that the second CDN center node 1032 and the third CDN center node 1033 in the first region both receive the first information of the first data stream, and the fourth CDN center node 1034, the fifth CDN center node 1035, and the sixth CDN center node 1036 in the second region all receive the first information of the first data stream.

[0086] The global management platform 101 is used to manage multiple regions. The distance between each CDN center node 103 in each region and the global management platform 101 is relatively long, so the transmission delay between each CDN center node 103 in each region and the global management platform 101 is relatively large. The global management platform 101 needs to process a large amount of data, which causes the global management platform 101 to...The latency required to send the first information of the first data stream is also relatively long. Therefore, after the first CDN center node 1031 sends the first information of the first data stream, it takes a long transmission latency before each of the other CDN center nodes can receive the first information of the first data stream.

[0087] Referring to Figure 4, assuming that a first viewer user sends a pull request to the second CDN center node 1032 shortly after the first live stream user pushes the first data stream, the pull request includes the pull domain name of the live application, the identification information of the first transcoding template and the identification information of the first data stream. The first transcoding template is used to define the second data stream.

[0088] The second CDN center node 1032 receives the pull request, but at this time it has not yet received the first information of the first data stream sent by the global management platform 101. Therefore, the second CDN center node 1032 selects a live source data platform 101 from the multiple live source data platforms 101 associated with the pull domain name and sends the pull request to the selected live source data platform 101.

[0089] The live streaming origin data platform 101 receives the streaming request, obtains the first transcoding template based on the identification information of the first transcoding template, obtains the first data stream based on the identification information of the first data stream, and transcodes the first data stream into a second data stream based on the parameters of the second data stream included in the first transcoding template, and sends the second data stream to the second CDN center node 1032. The second CDN center node 1032 receives the second data stream and sends the second data stream to the first viewer user.

[0090] After the first viewer user requests the streaming request and after a period of time, a second viewer user sends the streaming request to the third CDN center node 1033. The streaming request includes the streaming domain name of the live streaming application, the identification information of the first transcoding template, and the identification information of the first data stream.

[0091] The third CDN central node 1033 receives the pull request, but at this time the third CDN central node 1033 has already received the first information of the first data stream sent by the global management platform 101. Therefore, the third CDN central node 1033 obtains the first information including the identification information of the first data stream, and sends the pull request to the first CDN central node 1031 based on the location information included in the first information.

[0092] The first CDN central node 1031 receives the pull request, obtains the first transcoding template based on the identification information of the first transcoding template, obtains the first data stream based on the identification information of the first data stream, and transcodes the first data stream into a second data stream based on the parameters of the second data stream included in the first transcoding template, and sends the second data stream to the third CDN central node 1033. The third CDN central node 1033 receives the second data stream and sends the second data stream to the second viewer user.

[0093] Similarly, referring to Figure 4, the second live streaming user in the second area can push a data stream to the fourth CDN center node 1034, the third viewer user can pull a data stream to the fifth CDN center node 1035, and the fourth viewer user can pull a data stream to the sixth CDN center node 1036.

[0094] Since the first CDN center node 1031 needs a long transmission delay after sending the first information of the first data stream, other CDN center nodes can only receive the first information after a long transmission delay. However, some viewer users request to pull the second data stream from the second CDN center node 1032 earlier. The second CDN center node 1032 has not yet received the first information, so it requests to pull the stream from the live streaming origin data platform 102. And some viewer users request to pull the second data stream from the third CDN center node 1033 later. The third CDN center node 1033 has already received the first information, so it requests to pull the stream from the first CDN center node 1031.

[0095] Therefore, when different viewers request to pull the same data stream, they may request the stream on different devices, resulting in a waste of computing and network resources. In addition, both the first CDN central node 1031 and the live streaming source data platform 101 will repeatedly transcode the first data stream into the second data stream, causing duplicate transcoding and further wasting computing and network resources. To solve the above problems, the problem can be solved through any of the following examples.

[0096] Referring to Figure 5, this application embodiment provides a method 500 for processing data streams. The method 500 can be applied to the content distribution system 100 shown in Figures 1, 2, 3 or 4. In the method 500, the first CDN central node receives a data stream, the second CDN central node sends a first pull request to the first CDN central node for pulling the data stream, and the first CDN central node sends the requested data stream to the second CDN central node. The method 500 includes the following process.

[0097] Step 501: The first CDN central node receives the first data stream of the live streaming service. The first CDN central node is located in the first region.

[0098] The first terminal device corresponding to the first live streaming user sends the first data stream of the live streaming service to the first CDN central node using a live streaming application. Optionally, the first live streaming user is a user in the first region, and the first CDN central node is a CDN central node close to the first live streaming user. Therefore, the first terminal device corresponding to the first live streaming user establishes a connection with the first CDN central node and sends the first data stream to the first CDN central node through this connection.

[0099] Optionally, referring to Figure 6, the first terminal device first accesses the first edge node close to the first live streaming user, and then...The first terminal device communicates with the first CDN central node through the first edge node, that is, the connection between the first terminal device and the first CDN central node passes through the first edge node.

[0100] Optionally, the first terminal device corresponding to the first live user may also send the push domain name of the live application to the first CDN central node.

[0101] Optionally, the first terminal device corresponding to the first live user may also send information such as the application identifier of the live application to the first CDN central node.

[0102] Step 502: The first CDN central node sends the first information of the first data stream to the CDN central nodes other than the first CDN central node in the first region. The first information of the first data stream includes the identifier information of the first data stream and the first location information.

[0103] In some embodiments, the first location information is the location information of the first CDN central node, and the first information of the first data stream is used to indicate that there is a first data stream on the first CDN central node.

[0104] For example, referring to FIG4, the CDN central nodes other than the first CDN central node in the first region include the second CDN central node and the third CDN central node.

[0105] The first CDN central node sends the first information of the first data stream to the second CDN central node and the third CDN central node.

[0106] The first CDN central node also sends the first information of the first data stream to the global management platform.

[0107] Step 503: The first CDN central node sends the first data stream to the live streaming origin data platform.

[0108] In step 503, the first CDN central node receives the push domain name of the live streaming application, determines multiple live streaming origin data platforms associated with the push domain name in the first region, and sends the first data stream to the multiple live streaming origin data platforms. The multiple live streaming origin data platforms include at least one main live streaming origin data platform and at least one backup live streaming origin data platform corresponding to the main live streaming origin data platform.

[0109] In some embodiments, for each of the multiple live streaming origin data platforms, after receiving the first data stream, the live streaming origin data platform can also send the second information of the first data stream to the global management platform. The second information of the first data stream includes the identification information and the second location information of the first data stream.

[0110] In some embodiments, the second location information is the location information of the live streaming source data platform, and the second information of the first data stream is used to indicate that there is a first data stream on the live streaming source data platform.

[0111] For example, referring to FIG4, the multiple live streaming source data platforms associated with the push domain name in the first region include a first live streaming source data platform and a second live streaming source data platform. The first CDN central node sends the first data stream to the first live streaming source data platform and the second live streaming source data platform. The first live streaming source data platform is the primary live streaming source data platform, and the second live streaming source data platform is the backup live streaming source data platform. (Specification 10 / 29)Page 17 CN 121357336 A

[0112] The first live streaming source data platform receives the first data stream and sends the second information 1 of the first data stream to the global management platform. The second information 1 of the first data stream includes the identification information of the first data stream and the second location information 1. The second location information 1 is the location information of the first live streaming source data platform. The second information 1 of the first data stream is used to indicate that there is a first data stream on the first live streaming source data platform.

[0113] The second live streaming source data platform receives the first data stream and sends the second information 2 of the first data stream to the global management platform. The second information 2 of the first data stream includes the identification information of the first data stream and the second location information 2. The second location information 2 is the location information of the second live streaming source data platform. The second information 2 of the first data stream is used to indicate that there is a first data stream on the second live streaming source data platform.

[0114] The execution order of step 502 and step 503 is not sequential; that is, step 502 can be executed first and then step 503, or step 503 can be executed first and then step 502, or steps 502 and 503 can be executed simultaneously.

[0115] In some embodiments, the global management platform receives the first information of the first data stream and sends the first information of the first data stream to CDN center nodes other than the first CDN center node.

[0116] In some embodiments, the global management platform receives the second information of the first data stream and sends the second information of the first data stream to CDN center nodes other than the first CDN center node.

[0117] The CDN center nodes other than the first CDN center node include the CDN center nodes other than the first CDN center node in the multiple regions managed by the global management platform.

[0118] For example, referring to Figure 4, the multiple regions managed by the global management platform include a first region and a second region. The CDN center nodes other than the first CDN center node include the second and third CDN center nodes in the first region, and the fourth, fifth, and sixth CDN center nodes in the second region.

[0119] That is, the global management platform receives the first information of the first data stream sent by the first CDN center node, and sends the first information of the first data stream to the second and third CDN center nodes in the first region, and the fourth, fifth, and sixth CDN center nodes in the second region. And / or,

[0120] the global management platform receives the second information 1 of the first data stream sent by the first live streaming source data platform, and sends the second information 1 of the first data stream to the second and third CDN center nodes in the first region, and the fourth, fifth, and sixth CDN center nodes in the second region. And, the global management platform receives...The second information 2 of the first data stream sent by the second live streaming source data platform is sent to the second CDN center node and the third CDN center node in the first region, as well as the fourth CDN center node, the fifth CDN center node and the sixth CDN center node in the second region.

[0121] Step 504: The second CDN center node receives the first information of the first data stream. The CDN center nodes in the first region other than the first CDN center node include the second CDN center node.

[0122] In some embodiments, the second CDN center node may also receive the first information of the first data stream sent by the global management platform.

[0123] Since the distance between the first CDN center node and the second CDN center node is usually smaller than the distance between the first CDN center node and the global management platform, and smaller than the distance between the second CDN center node and the global management platform, the transmission delay between the first CDN center node and the second CDN center node is less than the sum of the transmission delay between the first CDN center node and the global management platform and the transmission delay between the second CDN center node and the global management platform. Therefore, the timestamp for receiving the first information of the first data stream sent by the first CDN central node to the second CDN central node is much earlier than the timestamp for receiving the first information of the first data stream sent by the global management platform. Specification 11 / 29 pages 18 CN 121357336 A

[0124] In some embodiments, the second CDN central node may also receive the second information of the first data stream sent by the global management platform.

[0125] For example, referring to FIG4, the second CDN central node and the third CDN central node in the first region both receive the first information of the first data stream from the first CDN central node.

[0126] The second CDN central node and the third CDN central node in the first region, as well as the fourth CDN central node, the fifth CDN central node and the sixth CDN central node in the second region, also receive the first information of the first data stream, the second information 1 of the first data stream and the second information 2 of the first data stream sent by the global management platform.

[0127] In some embodiments, the CDN central node with transcoding function in the first region may also periodically or irregularly send node information to the global management platform. This node information includes one or more of the following: the amount of idle resources used for transcoding in the CDN central node, or the transcoding cost of the CDN central node, etc.

[0128] For example, referring to Figure 4, assuming that the CDN central node with transcoding function in the first region includes a first CDN central node and a second CDN central node, the first CDN central node may periodically or irregularly send the first...The node information of the CDN central node, the node information of the first CDN central node includes the amount of idle resources used for transcoding in the first CDN central node and / or the transcoding cost of the first CDN central node, etc. The second CDN central node may periodically or irregularly send the node information of the second CDN central node to the global management platform, the node information of the second CDN central node includes the amount of idle resources used for transcoding in the second CDN central node and / or the transcoding cost of the second CDN central node, etc.

[0129] In some embodiments, the live streaming origin data platform in the first region may also periodically or irregularly send platform information to the global management platform, the platform information including one or more of the following: the amount of idle resources used for transcoding in the live streaming origin data platform, or the transcoding cost of the live streaming origin data platform, etc.

[0130] For example, referring to Figure 4, the first live streaming source data platform in the first region can also periodically or irregularly send platform information of the first live streaming source data platform to the global management platform. The platform information of the first live streaming source data platform includes one or more of the following: the number of idle resources used for transcoding in the first live streaming source data platform, or the transcoding cost of the first live streaming source data platform, etc. The second live streaming source data platform in the first region can also periodically or irregularly send platform information of the second live streaming source data platform to the global management platform. The platform information of the second live streaming source data platform includes one or more of the following: the number of idle resources used for transcoding in the second live streaming source data platform, or the transcoding cost of the second live streaming source data platform, etc.

[0131] In some embodiments, the global management platform can receive node information of CDN center nodes with transcoding function in the first region and receive platform information of live streaming source data platforms in the first region. Based on the received node information and platform information, the global management platform can configure a scheduling strategy for each CDN center node in the first region and configure a scheduling strategy for each live streaming source data platform in the first region. The scheduling policy of each CDN center node in the first region is sent to each CDN center node, and the scheduling policy of each live streaming origin data platform in the first region is sent to each live streaming origin data platform.

[0132] The scheduling policy of the CDN center nodes in the first region is used to indicate whether to select a CDN center node or a live streaming origin data platform to transcode the data stream.

[0133] For example, referring to Figure 4, the global management platform can receive the node information of the first CDN center node, the node information of the second CDN center node, the platform information of the first live streaming origin data platform, and the platform information of the second live streaming origin data platform. Based on the received node information and platform information, the scheduling policy is configured for the first CDN center node, the second CDN center node, and the third CDN center node in the first region, and the scheduling policy is configured for the first live streaming origin data platform in the first region.And configure scheduling strategies for the second live streaming origin data platform. Manual 12 / 29 pages 19 CN 121357336 A

[0134] For ease of explanation, the scheduling strategy configured for the second CDN center node in the first region is referred to as the first scheduling strategy, the scheduling strategy configured for the third CDN center node is referred to as the second scheduling strategy, the scheduling strategy configured for the first CDN center node is referred to as the third scheduling strategy, the scheduling strategy configured for the first live streaming origin data platform is referred to as the fourth scheduling strategy, and the scheduling strategy configured for the second live streaming origin data platform is referred to as the fifth scheduling strategy.

[0135] The global management platform sends the third scheduling strategy to the first CDN center node, the second scheduling strategy to the second CDN center node, the third scheduling strategy to the third CDN center node, the fourth scheduling strategy to the first live streaming origin data platform, and the fifth scheduling strategy to the second live streaming origin data platform.

[0136] Optionally, the scheduling strategy of the CDN central node is used to indicate that when the idle resources for transcoding in a CDN central node with transcoding function in the first region are insufficient, the live streaming origin data platform or other CDN central nodes with transcoding function should be selected for transcoding; and when the idle resources for transcoding in the CDN central nodes with transcoding function in the first region are sufficient, the CDN node should be selected for transcoding.

[0137] Optionally, the scheduling strategy of the CDN central node may include one or more of the following: the number of idle resources of the CDN central nodes with transcoding function in the first region, a first weight for selecting the CDN central node to transcode the data stream, or a second weight for selecting the live streaming origin data platform to transcode the data stream, etc.

[0138] Optionally, the more idle resources for transcoding in the CDN central nodes with transcoding function in the first region, the larger the first weight for selecting the CDN central node to transcode the data stream configured by the global management platform, and the smaller the second weight for selecting the live streaming origin data platform to transcode the data stream. And / or, the lower the transcoding cost of the CDN center node with transcoding function in the first region, the greater the first weight of the global management platform in configuring the CDN center node to transcode the data stream, and the smaller the second weight in configuring the live streaming origin data platform to transcode the data stream.

[0139] Optionally, the less idle resources available for transcoding in the CDN center node with transcoding function in the first region, the smaller the first weight of the global management platform in configuring the CDN center node to transcode the data stream, and the greater the second weight in configuring the live streaming origin data platform to transcode the data stream.

[0140] Optionally, the first weight and the second weight can be two ratios. For example, assuming the first weight is 90% and the second weight is 10%, that is, for 90% of the received pull requests, the CDN center node is selected for transcoding, and for the remaining 10%...The streaming request selects the live streaming source data platform for transcoding.

[0141] The scheduling strategy of the live streaming source data platform in the first area is used to indicate whether to select the live streaming source data platform or a third-party transcoding service platform to transcode the data stream.

[0142] Optionally, the scheduling strategy of the live streaming source data platform is used to indicate that when there are sufficient idle resources for transcoding in the live streaming source data platform, the live streaming source data platform is selected for transcoding; and when there are insufficient idle resources for transcoding in the live streaming source data platform, a third-party transcoding service platform is selected for transcoding. And / or, the scheduling strategy of the live streaming source data platform is used to indicate that when the transcoding cost in the live streaming source data platform is lower than the transcoding cost of the third-party transcoding service platform, the live streaming source data platform is selected for transcoding; and when the transcoding cost in the live streaming source data platform is higher than the transcoding cost of the third-party transcoding service platform, a third-party transcoding service platform is selected for transcoding.

[0143] Optionally, the scheduling strategy of the live streaming source data platform may include a third weight for selecting the live streaming source data platform to transcode the data stream and a fourth weight for selecting a third-party transcoding service platform to transcode the data stream.

[0144] Optionally, when the number of idle resources for transcoding in the live streaming source data platform is greater, the global management platform configures a larger third weight for selecting the live streaming source data platform to transcode the data stream, and a smaller fourth weight for selecting a third-party transcoding service platform to transcode the data stream. And / or, when the transcoding cost of the live streaming source data platform is lower, the global management platform configures a larger third weight for selecting the live streaming source data platform to transcode the data stream, and a smaller fourth weight for selecting a third-party transcoding service platform to transcode the data stream.

[0145] Optionally, when the number of idle resources for transcoding in the live streaming origin data platform is less, the third weight of the global management platform in configuring the selection of the live streaming origin data platform for transcoding the data stream is smaller, and the fourth weight of configuring the selection of a third-party transcoding service platform for transcoding the data stream is larger. And / or, when the transcoding cost of the live streaming origin data platform is higher, the third weight of the global management platform in configuring the selection of the live streaming origin data platform for transcoding the data stream is smaller, and the fourth weight of configuring the selection of a third-party transcoding service platform for transcoding the data stream is larger.

[0146] Optionally, the global management platform may periodically or periodically configure a scheduling strategy for each CDN center node and / or configure a scheduling strategy for each live streaming origin data platform.

[0147] Step 505: The second CDN center node receives a second pull request. The second pull request includes the first transcoding template and the identification information of the first data stream. The first transcoding template is used to define the second data stream.

[0148] Optionally, the second pull request may not include the first transcoding template, but may include the identifier of the first transcoding template.Information. That is, the second pull request includes the identification information of the first transcoding template and the first data stream, or the second pull request includes the identification information of the first transcoding template and the identification information of the first data stream.

[0149] In some embodiments, the second pull request is sent by the second terminal device corresponding to the first viewer user. After the first live user pushes the first data stream and a period of time has passed, a first viewer user needs to pull the data stream generated by the live stream of the first live user. The duration of this period of time may be greater than or equal to the latency threshold required by the live streaming service. The second terminal device corresponding to the first viewer user sends the second pull request to the second CDN center node.

[0150] Optionally, the first viewer user is a user in the first region, and the second CDN center node is a CDN center node close to the first viewer user. Therefore, the second terminal device corresponding to the first viewer user establishes a connection with the second CDN center node and sends the first pull request to the second CDN center node through this connection.

[0151] Optionally, referring to FIG6, the second terminal device accesses the second edge node close to the first viewer user and then establishes a connection with the second CDN center node. This connection passes through the second edge node.

[0152] The parameters of the first data stream and the parameters of the second data stream that the second terminal device can play are different. The second terminal device can directly play the second data stream, but cannot directly play the first data stream. Therefore, the second pull request sent by the second terminal device includes a first transcoding template or the identification information of the first transcoding template for defining the second data stream, in order to request that the first data stream be transcoded into the second data stream defined by the first transcoding template.

[0153] Optionally, the second pull request also includes the pull domain name of the live streaming application, etc.

[0154] Optionally, the first transcoding template includes one or more of the following: the resolution, frame rate, bit rate of the second data stream, or the image width and height in the second data stream, etc.

[0155] Optionally, the second pull request also includes the pull domain name of the live streaming application, etc.

[0156] In some embodiments, the second pull request is sent by the third CDN central node. The third CDN central node includes a second scheduling strategy sent from the global management platform. The third CDN central node does not have a transcoding function, while the second CDN central node has a transcoding function. After the first live stream user pushes the first data stream and a period of time has passed, a second viewer user needs to pull the data stream generated by the first live stream user. The third terminal device corresponding to the second viewer user sends a fifth pull request to the third CDN central node. The fifth pull request includes the identification information of the first data stream and the first transcoding template, or the fifth pull request includes the identification information of the first data stream and the identification information of the first transcoding template. The third CDN central node receives the fifth pull request and, when selecting the second CDN central node based on the second scheduling strategy, sends a second pull request to the second CDN central node.

[0157] Optionally, the second pull request and the fifth pull request are the same, or the source and destination addresses of the second pull request are different from those of the fifth pull request (page 14 / 29, CN 121357336 A). Similar content will not be listed hereafter.

[0158] Optionally, the fifth pull request also includes the pull domain name of the live streaming application, and the second pull request also includes the pull domain name of the live streaming application.

[0159] In some embodiments, the first CDN central node may also have transcoding functionality. The operation of the third CDN central node selecting a device for transcoding the data stream based on the second scheduling strategy can be as follows:

[0160] The third CDN central node selects a CDN central node or a live streaming origin data platform to transcode the data stream based on the second scheduling strategy. When selecting a CDN central node to transcode the data stream, if the idle resources for transcoding in the first CDN central node are insufficient or the first CDN central node does not have transcoding functionality, a second CDN central node with transcoding functionality is selected, and a second pull request is sent to the second CDN central node.

[0161] Optionally, the second scheduling strategy includes the number of idle resources for transcoding in the CDN central nodes with transcoding capabilities. For example, referring to Figure 4, the CDN central nodes with transcoding capabilities include a first CDN central node and a second CDN central node. The third CDN central node obtains the number of idle resources for transcoding in the first CDN central node from the second scheduling strategy. When it is determined that the idle resources for transcoding in the first CDN central node are insufficient based on the amount of idle resource data, it obtains the number of idle resources for transcoding in the second CDN central node from the second scheduling strategy. When it is determined that the idle resources for transcoding in the second CDN central node are sufficient based on the amount of idle resource data, it selects the second CDN central node to transcode the data stream.

[0162] Optionally, the second scheduling strategy includes a first weight for selecting a CDN central node to transcode the data stream and a second weight for selecting a live streaming origin data platform to transcode the data stream. The third CDN central node selects a CDN central node to transcode the data stream based on the first weight and the second weight, or selects a live streaming origin data platform to transcode the data stream.

[0163] Sufficient idle resources for transcoding means that the number of idle resources for transcoding in the first CDN central node exceeds a threshold, or that the idle resources for transcoding in the first CDN central node are sufficient to meet the resource requirements for transcoding at least one data stream.

[0164] Insufficient idle resources for transcoding means that the number of idle resources for transcoding in the first CDN central node does not exceed a threshold, or that the idle resources for transcoding in the first CDN central node are insufficient to meet the resource requirements for transcoding at least one data stream.

[0165] In some embodiments, when selecting a live streaming source data platform to transcode the data stream, the third CDN central node performs a hash operation on the identification information of the second data stream to obtain a first hash value. The identification information of the second data stream includes the identification information of the first transcoding template and the identification information of the first data stream. The first hash value is moduloed with a specified value to obtain the sequence number of the live streaming source data platform. At least one main live streaming source data platform is determined among multiple live streaming source data platforms associated with the streaming domain name. Based on the sequence number, a live streaming source data platform is selected from the at least one main live streaming source data platform as the first live streaming source data platform. A third streaming request is sent to the first live streaming source data platform. The third streaming request includes the identification information of the first data stream and the first transcoding template, or the third streaming request includes the identification information of the first data stream and the identification information of the first transcoding template.

[0166] The specified value can be a preset value (such as 10, 20, 50, 80 or 100, etc.), or it can be the number of at least one main live streaming source data platform.

[0167] Step 506: The second CDN central node sends a first pull request to the first CDN central node based on the first information of the first data stream. The first pull request includes the identification information of the first data stream.

[0168] The second CDN central node may receive the first information of the first data stream sent by the first CDN central node before receiving the second pull request. This ensures that when the second CDN central node receives the second pull request, it obtains the first information of the first data stream based on the identification information of the first data stream included in the pull request. The first information of the first data stream includes first location information, which is used to indicate the location of the first CDN central node. The second CDN central node sends the first pull request to the first CDN central node based on the first location information.

[0169] In some embodiments, the second CDN central node may receive a first scheduling policy sent by the global management platform and select a CDN central node or a live streaming source data platform to transcode the data stream based on the first scheduling policy. When selecting a CDN central node to transcode a data stream, if the first CDN central node has transcoding capabilities, it may be selected; if the second CDN central node has transcoding capabilities, it may be selected.

[0170] When selecting a CDN central node to transcode a data stream, if the first CDN central node has sufficient idle resources for transcoding, the second CDN central node sends a first pull request to the first CDN central node based on the first information of the first data stream. The first pull request includes the identification information of the first data stream and the first transcoding template, or...The stream request includes the identification information of the first data stream and the identification information of the first transcoding template. At this time, the first pull stream request is used to request the first CDN central node to transcode the first data stream into the second data stream defined by the first transcoding template.

[0171] If the idle resources for transcoding in the first CDN central node are insufficient and the idle resources for transcoding in the second CDN central node are sufficient, the second CDN central node selects itself to transcode the data stream, and sends the first pull stream request to the third CDN central node based on the first information of the first data stream. The first pull stream request includes the identification information of the first data stream. At this time, the first pull stream request is used to request the first CDN central node to obtain the first data stream.

[0172] When selecting a live streaming source data platform to transcode the data stream, the second CDN central node sends a third pull stream request to the first live streaming source data platform in the first region. The third pull stream request includes the identification information of the first data stream and the first transcoding template, or the third pull stream request includes the identification information of the first data stream and the identification information of the first transcoding template.

[0173] Optionally, the first scheduling strategy includes the number of idle resources for transcoding in the CDN central nodes with transcoding capabilities. For example, referring to Figure 4, the CDN central nodes with transcoding capabilities include a first CDN central node and a second CDN central node. The second CDN central node obtains the number of idle resources for transcoding in the first CDN central node from the first scheduling strategy. When it is determined that the idle resources for transcoding in the first CDN central node are sufficient based on the amount of idle resource data, the second CDN central node selects the first CDN central node to transcode the data stream. When it is determined that the idle resources for transcoding in the first CDN central node are insufficient based on the amount of idle resource data, but the second CDN central node itself has sufficient idle resources for transcoding, the second CDN central node selects itself to transcode the data stream.

[0174] Optionally, the first scheduling strategy includes a first weight for selecting a CDN central node to transcode the data stream and a second weight for selecting a live streaming origin data platform to transcode the data stream. The second CDN central node selects a CDN central node to transcode the data stream based on the first weight and the second weight, or selects a live streaming origin data platform to transcode the data stream.

[0175] In some embodiments, when selecting a live streaming source data platform to transcode the data stream, the second CDN central node performs a hash operation on the identification information of the second data stream to obtain a first hash value. The identification information of the second data stream includes the identification information of the first transcoding template and the identification information of the first data stream. The first hash value is moduloed with a specified value to obtain the sequence number of the live streaming source data platform. At least one primary live streaming source data platform is determined among multiple live streaming source data platforms associated with the streaming domain name. Based on the sequence number, a live streaming source data platform is selected from the at least one primary live streaming source data platform as the first live streaming source data platform, and a streaming request is sent to the first live streaming source data platform.

[0176] Step 507: The first CDN central node receives the first pull request and sends the first data stream to the second CDN central node.

[0177] In some embodiments, the first pull request is used to request the first CDN central node to obtain the first data stream, and the first pull request includes the identification information of the first data stream. In this case, the first CDN central node sends the first data stream to the second CDN central node based on the identification information of the first data stream.

[0178] In some embodiments, the first pull request is used to request the first CDN central node to transcode the first data stream into a second data stream defined by the first transcoding template, and the first data stream sent by the first CDN central node to the second CDN central node is the transcoded first data stream, and the transcoded first data stream is the second data stream.

[0179] In implementation, if the first pull request includes the identification information of the first data stream and the identification information of the first transcoding template, the first CDN central node transcodes the first data stream into a second data stream defined by the first transcoding template based on the identification information of the first transcoding template and the identification information of the first data stream, and sends the second data stream to the second CDN central node.

[0180] Optionally, the first CDN central node includes multiple transcoding templates, which include the first transcoding template, and the first transcoding template includes at least one parameter of the second data stream. In step 507, the first CDN central node obtains the first transcoding template based on the identification information of the first transcoding template. Based on the identification information of the first data stream, it obtains the first data stream from the received data stream. Based on at least one parameter of the second data stream included in the first transcoding template, it transcodes the first data stream into a second data stream defined by the first transcoding template.

[0181] If the first pull request includes the identification information of the first data stream and the first transcoding template, the first CDN central node obtains the first data stream from the received data stream based on the identification information of the first data stream. The first data stream is transcoded into a second data stream defined by the first transcoding template, and the second data stream is sent to the second CDN central node.

[0182] In some embodiments, when the first pull request is used to request the first CDN central node to transcode the first data stream into a second data stream defined by the first transcoding template, the first CDN central node may receive a third scheduling policy sent by the global management platform. Based on the third scheduling policy, the first CDN central node or the live streaming source data platform is selected to transcode the data stream. When the first CDN central node is selected to transcode the data stream, the first data stream is transcoded into a second data stream defined by the first transcoding template. When the live streaming source data platform is selected to transcode the data stream, a third pull request is sent to a live streaming source data platform in the first region. The third pull request includes the identification information of the first data stream and the first transcoding template.Alternatively, the third pull request includes the identification information of the first data stream and the identification information of the first transcoding template.

[0183] Optionally, the third scheduling strategy includes a first weight for selecting a CDN central node to transcode the data stream and a second weight for selecting a live streaming source data platform to transcode the data stream. The first CDN central node selects a first CDN central node to transcode the data stream based on the first weight and the second weight, or selects a live streaming source data platform to transcode the data stream.

[0184] In some embodiments, when selecting a live streaming source data platform to transcode the data stream, the first CDN central node performs a hash operation on the identification information of the second data stream to obtain a first hash value. The identification information of the second data stream includes the identification information of the first transcoding template and the identification information of the first data stream. The first hash value is moduloed with a specified value to obtain the sequence number of the live streaming source data platform. At least one main live streaming source data platform is determined among multiple live streaming source data platforms associated with the pull domain name. Based on the sequence number, a live streaming source data platform is selected from at least one main live streaming source data platform, and a first pull request is sent to the selected live streaming source data platform.

[0185] In this design, each CDN central node (such as the first CDN central node, the second CDN central node, or the third CDN central node) in the first region follows the same rule for selecting the live streaming origin data platform. This ensures that multiple CDN central nodes that need to transcode the first data stream into the second data stream will select the same live streaming origin data platform. This allows a single live streaming origin data platform to transcode the first data stream into the second data stream and return it to multiple CDN central nodes, thus ensuring that only one live streaming origin data platform transcodes the first data stream into the second data stream. This avoids multiple live streaming origin data platforms repeatedly transcoding the first data stream into the second data stream, saving computing and network resources.

[0186] In some embodiments, when the first CDN central node transcodes the first data stream into a second data stream, the CDN central node can also send the first information of the second data stream to other CDN central nodes in the first region besides the first CDN central node. The first information of the second data stream includes the identification information and the first location information of the second data stream. The first information of the second data stream is used to indicate that there is a second data stream on the first CDN central node.

[0187] In some embodiments, the first CDN central node can also send the first information of the second data stream to the global management platform. The global management platform sends the first information of the second data stream to CDN central nodes other than the first CDN central node.

[0188] The CDN central nodes in the first region besides the first CDN central node (as shown in Figure 4, the second CDN central node)The second CDN center node receives the first information of the second data stream sent by the first CDN center node, and / or receives the first information of the second data stream sent by the global management platform. The timestamp for receiving the first information of the second data stream sent by the first CDN center node is earlier than the timestamp for receiving the first information of the second data stream sent by the global management platform.

[0189] Step 508: The second CDN center node receives the first data stream and sends the second data stream.

[0190] In some embodiments, when the second CDN center node selects itself to transcode the data stream, if the second pull request includes the identifier information of the first data stream and the identifier information of the first transcoding template, the second CDN center node includes multiple transcoding templates. The second CDN center node obtains the first transcoding template based on the identifier information of the first transcoding template, and transcodes the first data stream into the second data stream defined by the first transcoding template based on at least one parameter of the second data stream included in the first transcoding template. If the second pull request includes the identification information of the first data stream and the first transcoding template, the second CDN central node transcodes the first data stream into the second data stream defined by the first transcoding template based on at least one parameter of the second data stream included in the first transcoding template.

[0191] Optionally, the second CDN central node may also send second information of the second data stream to CDN central nodes other than the second CDN central node in the first region. The second information of the second data stream includes the identification information and second location information of the second data stream. The second information of the second data stream is used to indicate that there is a second data stream on the second CDN central node.

[0192] Optionally, the second CDN central node may also send the second information of the second data stream to the global management platform. The global management platform sends the second information of the second data stream to CDN central nodes other than the second CDN central node.

[0193] In some embodiments, when the second CDN central node selects the first CDN central node to transcode the data stream, the first data stream received by the second CDN central node is the transcoded first data stream, which is the second data stream.

[0194] For the aforementioned second data stream, if the second pull request received by the second CDN central node is a request from the second terminal device, the second CDN central node sends the second data stream to the second terminal device corresponding to the first viewer user.

[0195] In some embodiments, for other viewer users communicating with the second CDN central node, if the terminal device corresponding to the other viewer user sends a pull request to the second CDN central node for pulling the second data stream, since the second CDN central node is continuously transcoding the received first data stream into the second data stream, or is continuously receiving the second data stream sent by the first CDN central node, the second CDN central node can directly send the second data stream to the second terminal device corresponding to the other viewer user.The terminal device sends a second data stream.

[0196] If the second pull request received by the second CDN central node is a request from the third CDN central node, the second CDN central node sends the second data stream to the third CDN central node, and the third CDN central node sends the second data stream to the third terminal device corresponding to the second viewer user.

[0197] Wherein, when the first CDN central node transcodes the first data stream into the second data stream, for other CDN central nodes in the first area, the other CDN central nodes have received the first information of the second data stream. The first information of the second data stream includes the identification information of the second data stream and the first location information. Specification 18 / 29 pages 25 CN 121357336 A

[0198] Therefore, the other CDN central nodes receive the pull request sent by the terminal device corresponding to the viewer user. The pull request includes the identification information of the second data stream (the identification information of the first data stream and the identification information of the first transcoding template). Based on the identification information of the second data stream, the first information of the second data stream is obtained, and the pull request is sent to the first CDN central node based on the first location information included in the first information of the second data stream. The first CDN central node receives the pull request and, based on the identification information of the second data stream, sends the second data stream to other CDN central nodes. Other CDN central nodes receive the second data stream and send it to the terminal device corresponding to the viewer user. This avoids repeatedly transcoding the first data stream into the second data stream, saving computing and network resources.

[0199] Similarly, when the second CDN central node transcodes the first data stream into the second data stream, for other CDN central nodes in the first region, the other CDN central nodes have already received the second information of the second data stream. The second information of the second data stream includes the identification information and the second location information of the second data stream.

[0200] Therefore, when other CDN central nodes receive the pull request sent by the terminal device corresponding to the viewer user, the pull request includes the identification information of the second data stream (the identification information of the first data stream and the identification information of the first transcoding template). Based on the identification information of the second data stream, they obtain the second information of the second data stream and, based on the second location information included in the second information of the second data stream, send the pull request to the second CDN central node. The second CDN central node receives the streaming request and, based on the identifier information of the second data stream, sends the second data stream to other CDN central nodes. Other CDN central nodes receive the second data stream and send it to the terminal devices corresponding to the viewers / users. This avoids repeatedly transcoding the first data stream into the second data stream, saving computing and network resources.

[0201] In this embodiment, after receiving the first data stream, the first CDN central node sends it to the terminal devices of the first region other than the first...Each CDN central node other than the first CDN central node sends the first information of the first data stream. The first information of the first data stream includes the identification information and the first location information of the first data stream, used to indicate that the first data stream is present on the first CDN central node. Since the CDN central nodes in the first region meet the aforementioned first latency condition, second latency condition, and / or distance condition, each CDN central node in the first region other than the first CDN central node receives the pull request from the audience user before receiving the first information of the first data stream. For example, the transmission latency between the first CDN central node and each CDN central node in the first region other than the first CDN central node is less than the latency threshold required for the live streaming service. However, after the broadcaster sends the first data stream, the time from when the first audience user requests to pull the first data stream is usually greater than this latency threshold. Therefore, each CDN central node in the first region other than the first CDN central node receives the pull request before receiving the first information of the first data stream. Thus, each CDN central node sends a pull request to the first CDN central node based on the first information. This ensures that when users in the first region need to pull a data stream, the pull can be completed on the CDN central node within the first region, reducing the latency and network resources of pulling the data stream. Furthermore, when the first CDN central node has a transcoding function, the first information can be used to control the transcoding of the first data stream into the second data stream on the first CDN central node as much as possible, avoiding repeated transcoding of the first data stream into the second data stream, thus saving computing and network resources.

[0202] Referring to Figure 7, this application embodiment provides a method 700 for processing data streams. The method 700 can be applied to the content distribution system 100 shown in Figures 1, 2, 3, or 4. In the method 700, the first live streaming source data platform in the first region receives the first data stream, the CDN central node in the first region receives a first pull request for pulling the second data stream, and selects the live streaming source data platform to transcode the data stream. Therefore, it sends a third pull request to the live streaming source data platform, which requests the first live streaming source data platform to transcode the first data stream into the second data stream. The method 700 includes the following process.

[0203] Step 701: The first live streaming source data platform receives the first data stream sent by the first CDN central node. Both the first live streaming source data platform and the first CDN central node are located in the first region. Specification 19 / 29 pages 26 CN 121357336 A

[0204] The push domain name of the first data stream is associated with multiple live streaming source data platforms in the first region, including the first live streaming source data platform.

[0205] The first CDN central node receives the first data stream and push domain name sent by the first terminal device corresponding to the first live streaming user.Stream domain name. Identify multiple live streaming source data platforms in the first region associated with the push streaming domain name, and send the first data stream to the multiple live streaming source data platforms.

[0206] Step 702: The first live streaming source data platform receives a third pull stream request. The third pull stream request includes the identification information of the first data stream and the first transcoding template.

[0207] In some embodiments, the third pull stream request includes the identification information of the first data stream and the identification information of the first transcoding template.

[0208] Optionally, the third pull stream request may be sent by a third CDN central node. For a detailed implementation process of the third CDN central node sending the third pull stream request, please refer to the relevant content in step 505 of the embodiment shown in Figure 5, which will not be described in detail here.

[0209] Optionally, the third pull stream request may be sent by a second CDN central node. For a detailed implementation process of the second CDN central node sending the third pull stream request, please refer to the relevant content in step 506 of the embodiment shown in Figure 5, which will not be described in detail here.

[0210] Optionally, the third pull request may be sent by the first CDN central node. For a detailed explanation of how the first CDN central node sends the third pull request, please refer to step 507 of the embodiment shown in Figure 5, which will not be described in detail here.

[0211] Step 703: The first live streaming origin data platform selects either the first live streaming origin data platform or a third-party transcoding service platform to transcode the data stream based on the fourth scheduling strategy.

[0212] In some embodiments, the fourth scheduling strategy is used to instruct that when there are sufficient idle resources for transcoding in the first live streaming origin data platform, the first live streaming origin data platform is selected for transcoding; and when there are insufficient idle resources for transcoding in the first live streaming origin data platform, a third-party transcoding service platform is selected for transcoding. Therefore, the first live streaming origin data platform obtains idle resources for transcoding in the first live streaming origin data platform based on the fourth scheduling strategy. When there are sufficient idle resources for transcoding in the first live streaming origin data platform, the first live streaming origin data platform is selected; when there are insufficient idle resources for transcoding in the first live streaming origin data platform, a third-party transcoding service platform is selected.

[0213] Optionally, when the number of idle resources used for transcoding exceeds a quantity threshold, or when the idle resources used for transcoding are sufficient to meet the resources required for transcoding at least one data stream, it is determined that the idle resources used for transcoding in the first live streaming source platform are sufficient.

[0214] Optionally, when the number of idle resources used for transcoding does not exceed a quantity threshold, or when the idle resources used for transcoding are insufficient to meet the resources required for transcoding at least one data stream, it is determined that the idle resources used for transcoding in the first live streaming source platform are insufficient.

[0215] In some embodiments, the fourth scheduling strategy is used to indicate the transcoding cost in the first live streaming source platform.When the transcoding cost of the first live streaming source platform is lower than that of the third-party transcoding service platform, the first live streaming source platform is selected for transcoding; and when the transcoding cost of the first live streaming source platform is higher than that of the third-party transcoding service platform, the third-party transcoding service platform is selected for transcoding. Therefore, the first live streaming source platform obtains the transcoding cost of the first live streaming source platform and the transcoding cost of the third-party transcoding service platform based on the fourth scheduling strategy. When the transcoding cost of the first live streaming source platform is lower than that of the third-party transcoding service platform, the first live streaming source platform is selected; when the transcoding cost of the first live streaming source platform is higher than that of the third-party transcoding service platform, the third-party transcoding service platform is selected. Specification 20 / 29 pages 27 CN 121357336 A

[0216] In some embodiments, the fourth scheduling strategy includes a third weight for selecting the first live streaming source platform to transcode the data stream and a fourth weight for selecting the third-party transcoding service platform to transcode the data stream. The first live streaming source platform selects a third-party transcoding service platform to transcode the data stream based on the third and fourth weights.

[0217] Step 704: When selecting a third-party transcoding service platform to transcode the data stream, the first live streaming source platform sends a fourth pull request and the first data stream to the third-party transcoding service platform.

[0218] In step 704, the first live streaming source platform obtains the first data stream from the received data stream based on the identification information of the first data stream, and sends a fourth pull request and the first data stream to the third-party transcoding service platform. The fourth pull request includes the first transcoding template, or the fourth pull request includes the identification information of the first transcoding template.

[0219] Step 705: The third-party transcoding service platform receives the first data stream and the fourth pull request, and transcodes the first data stream into the second data stream defined by the first transcoding template based on the first transcoding template.

[0220] In step 705, the fourth streaming request includes a first transcoding template, and the third-party transcoding service platform transcodes the first data stream into a second data stream defined by the first transcoding template. Alternatively, the fourth streaming request includes the identification information of the first transcoding template, the third-party transcoding service platform includes multiple transcoding templates, the third-party transcoding service platform obtains the first transcoding template based on the identification information of the first transcoding template, and transcodes the first data stream into a second data stream defined by the first transcoding template based on at least one parameter of the second data stream included in the first transcoding template.

[0221] Step 706: The third-party transcoding service platform sends the second data stream to the first live streaming source data platform.

[0222] Step 707: The first live streaming source data platform receives the second data stream, sends the second data stream, and ends.

[0223] Optionally, the third streaming request may be sent by the third CDN central node, and the first live streaming source data platform sends...The third CDN central node sends the second data stream.

[0224] Optionally, the third pull request may be sent by the second CDN central node, and the first live streaming origin data platform sends the second data stream to the second CDN central node.

[0225] Optionally, the third pull request may be sent by the first CDN central node, and the first live streaming origin data platform sends the second data stream to the first CDN central node.

[0226] Step 708: When the first live streaming origin data platform selects the first live streaming origin data platform to transcode the data stream, it transcodes the first data stream into the second data stream defined by the first transcoding template.

[0227] When the third pull request includes the identification information of the first data stream and the first transcoding template, the first live streaming origin data platform obtains the first data stream from the received data stream based on the identification information of the first data stream. It transcodes the first data stream into the second data stream defined by the first transcoding template.

[0228] When the third pull request includes the identification information of the first data stream and the identification information of the first transcoding template, the first live streaming origin data platform obtains the first data stream from the received data stream based on the identification information of the first data stream. Based on the identification information of the first transcoding template, it obtains the first transcoding template. Based on at least one parameter of the second data stream included in the first transcoding template, it transcodes the first data stream into the second data stream defined by the first transcoding template.

[0229] Step 709: The first live streaming origin data platform sends the second data stream, and the process ends.

[0230] Optionally, the third pull request may be sent by the third CDN central node, and the first live streaming origin data platform sends the second data stream to the third CDN central node.

[0231] Optionally, the third pull request may be sent by the second CDN central node, and the first live streaming origin data platform sends the second data stream to the second CDN central node.

[0232] Optionally, the third pull request may be sent by the first CDN central node, and the first live streaming origin data platform sends the second data stream to the first CDN central node (pages 21 / 29 of the specification, CN 121357336 A).

[0233] In some embodiments, the first live streaming origin data platform may also send third information of the second data stream to the global management platform. The third information of the second data stream includes the identification information and third location information of the second data stream. The third location information is used to indicate the location of the first live streaming origin data platform, and the third information of the second data stream is used to indicate that there is a second data stream on the first live streaming origin data platform. The global management platform sends the third information of the second data stream to CDN central nodes in multiple regions.

[0234] In some embodiments, assuming that the third pull request may be sent by the second CDN central node, if there is an abnormality in the connection between the first live streaming origin data platform and the second CDN central node, the second CDN central node sends the second live streaming origin data stream to the second CDN central node.The first live streaming source platform sends a third pull request. The second live streaming source platform is a backup live streaming source platform for the first live streaming source platform. Based on the third pull request, the second live streaming source platform transcodes the first data stream into a second data stream and sends the second data stream to the second CDN center node. Similarly, if the third pull request is sent by either the first or third CDN center node, and there is a connection error, the live streaming source platform is switched in the manner described above.

[0235] In some embodiments, the second live streaming source platform can also send fourth information of the second data stream to the global management platform. The fourth information of the second data stream includes the identification information and the fourth location information of the second data stream. The fourth location information is used to indicate the location of the second live streaming source platform and to indicate that there is a second data stream on the second live streaming source platform. The global management platform sends the fourth information of the second data stream to the CDN center nodes in multiple regions.

[0236] In some embodiments, the global management platform may receive first information of the second data stream sent by the first CDN central node, the first information of the second data stream including the identification information and first location information of the second data stream; and receive third information of the second data stream sent by the first live streaming origin data platform, the third information of the second data stream including the identification information and third location information of the second data stream.

[0237] Based on the first information and the third information of the second data stream, the global management platform determines that when both the first CDN central node and the first live streaming origin data platform transcode the first data stream into the second data stream, it stops one of the first CDN central node and the first live streaming origin data platform from continuing to transcode the first data stream into the second data stream. Similarly, in the same manner as described above, the global management platform may also stop one of the second CDN central node and the first live streaming origin data platform from continuing to transcode the first data stream into the second data stream.

[0238] Optionally, the global management platform sends a first stop command to the first CDN central node. The first stop command includes the identification information of the second data stream. Based on the first stop command, the first CDN central node stops transcoding the first data stream into the second data stream.

[0239] When the first CDN central node stops transcoding the first data stream into the second data stream, for other CDN central nodes that pulled the second data stream from the first CDN central node, the other CDN central nodes obtain the third information of the second data stream, including the identification information of the second data stream. Based on the third location information included in the third information of the second data stream, they obtain the second data stream from the first live streaming source data platform.

[0240] Optionally, the global management platform sends a second stop command to the first live streaming source data platform. The second stop command is used to instruct the first live streaming source data platform to stop transcoding the first data stream into the second data stream.

[0241] When the first live streaming source data platform stops transcoding the first data stream into the second data stream, for other CDN center nodes that pull the second data stream from the first live streaming source data platform, the other CDN center nodes obtain the first information of the second data stream, including the identification information of the second data stream, and obtain the second data stream from the first CDN center node based on the first location information included in the first information of the second data stream. Specification 22 / 29 pages 29 CN 121357336 A

[0242] When there is an abnormality in the connection between the first live streaming source data platform and the CDN center node (such as the first CDN center node, the second CDN center node or the third CDN center node mentioned above), the second live streaming source data platform is the backup live streaming source data platform of the first live streaming source data platform. The second live streaming source data platform transcodes the first stream data stream into the second data stream and sends the second transcoded stream to the CDN center node. However, at this time, the first live streaming source station data platform continues to transcode the first data stream into the second data stream. That is, the first live streaming source station data platform and the second live streaming source station data platform repeatedly transcode the first data stream into the second data stream.

[0243] In this case, the global management platform will receive the fourth information of the second data stream sent by the second live streaming source station data platform. Based on the third information of the second data stream and the fourth information of the second data stream, it determines that both the first live streaming source station data platform and the second live streaming source station data platform are transcoding the first data stream into the second data stream, and stops the first live streaming source station data platform from continuing to transcode the first data stream into the second data stream.

[0244] Optionally, the global management platform sends a second stop command to the first live streaming source station data platform. The second stop command is used to instruct the first live streaming source station data platform to stop continuing to transcode the first data stream into the second data stream.

[0245] In some embodiments, referring to FIG8, the global management platform includes one or more of the following: a scheduling service module, a stream management service module, an alarm service module, a live streaming management service module, and a call detail record (CDR) billing service module.

[0246] The scheduling service module is used to schedule transcoding tasks and issue scheduling strategies during live streaming push and pull.

[0247] The stream management service module is used to receive and forward information from the data stream. For example, it receives and forwards the first and / or second information of the first data stream, and receives and forwards the first, second, third, and / or fourth information of the second data stream.

[0248] The alarm service module is used to detect various abnormal alarms in the live streaming business scenario. Currently, it is mainly used for abnormal detection under repeated transcoding and notifies manual or automatic abnormal handling under repeated transcoding, such as stopping repeated transcoding on multiple devices.

[0249] The live streaming management service module is used for live streaming configuration management (configuring transcoding templates) and control management. Currently, it is mainly used forThe duplicate transcoding is used to issue a stop command for abnormally repeated transcoding tasks. The duplicate transcoding tasks are reduced by issuing a transcoding stop command for a specified stream.

[0250] The call detail record (CDR) billing service module is used to collect and report live streaming billing CDRs, form live streaming billing and provide it to the operation system for billing processing. Currently, it mainly refers to the generation of transcoding billing CDRs and the filtering of duplicate transcoding billing CDRs, so as to process the billing CDRs generated by duplicate transcoding from the customer side and reduce the cost caused by duplicate transcoding at the customer side.

[0251] In the embodiment of this application, the first live streaming source station data platform receives a third streaming request. When its own idle resources for transcoding are insufficient, it can request a third-party transcoding service platform to transcode the first stream data into a second data stream to ensure successful transcoding of the data stream. When its own transcoding cost is higher than the transcoding cost of the third-party transcoding service platform, it can request the third-party transcoding service platform to transcode the first stream data into a second data stream to reduce the cost of transcoding the data stream.

[0252] Referring to FIG9, this application embodiment provides a content distribution system 900. The content distribution system 900 may include a first content distribution network CDN center node 901 as shown in FIG1, FIG2, FIG3 or FIG4. The area where the first CDN center node 901 is located also includes at least one CDN center node;

[0253] The first CDN center node 901 is used to receive the first data stream of the live broadcast service;

[0254] The first CDN center node 901 is also used to send the first information of the first data stream to at least one CDN center node respectively. The first information includes the identification information and location information of the first data stream;

[0255] The second CDN center node 902 among the at least one CDN center node is used to send a first pull request to the first CDN center node 901 based on the first information;

[0256] The first CDN center node 901 is also used to send the first data stream to the second CDN center node 902.

[0257] Optionally, the detailed implementation process of the first CDN central node 901 receiving the first data stream of the live broadcast service is described in detail in step 501 of method 500 shown in Figure 5, and will not be described in detail here.

[0258] Optionally, the detailed implementation process of the first CDN central node 901 sending the first information of the first data stream to at least one CDN central node is described in detail in step 502 of method 500 shown in Figure 5, and will not be described in detail here.

[0259] Optionally, the detailed implementation process of the second CDN central node 902 sending the first pull request is described in detail in step 506 of method 500 shown in Figure 5, and will not be described in detail here.

[0260] Optionally, the detailed implementation process of the first CDN central node 901 sending the first data stream is described in detail in method 500 shown in Figure 5.The details of step 507 in method 500 are not described in detail here.

[0261] Optionally, the first pull request carries a transcoding template, and the first CDN center node 901 is used to:

[0262] transcode the first data stream based on the transcoding template to obtain the transcoded first data stream;

[0263] send the transcoded first data stream to the second CDN center node 902.

[0264] Optionally, the detailed implementation process of the first CDN center node 901 transcoding the first data stream based on the transcoding template to obtain the transcoded first data stream is described in detail in step 507 of method 500 shown in Figure 5, and will not be described in detail here.

[0265] Optionally, the detailed implementation process of the first CDN center node 901 sending the transcoded first data stream is described in detail in step 507 of method 500 shown in Figure 5, and will not be described in detail here.

[0266] Optionally, the second CDN central node 902 is configured to send a first pull request to the first CDN central node 901 based on the first information after receiving the second pull request from the terminal device.

[0267] Optionally, the detailed implementation process of the second CDN central node 902 sending the first pull request to the first CDN central node 901 based on the first information after receiving the second pull request from the terminal device is described in detail in step 506 of method 500 shown in FIG5, and will not be described in detail here.

[0268] Optionally, the first pull request carries a transcoding template;

[0269] At least one third CDN center node 903 in the CDN center nodes is used to send a second pull request to the second CDN center node 902. The second pull request is used to request the second CDN center node to send a first pull request to the first CDN center node 901 based on the first information;

[0270] The second CDN center node 902 is also used to transcode the first data stream based on the transcoding template to obtain the transcoded first data stream;

[0271] The second CDN center node 902 is also used to send the transcoded first data stream to the third CDN center node 903.

[0272] Optionally, the detailed implementation process of the third CDN center node 903 sending the second pull request to the second CDN center node 902 is shown in step 505 of method 500 in Figure 5, and will not be described in detail here.

[0273] Optionally, the second CDN central node 902 transcodes the first data stream based on the transcoding template to obtain the transcoded first data stream. For details of this process, please refer to step 508 of method 500 shown in Figure 5, which will not be described in detail here.

[0274] Optionally, the detailed process of the second CDN central node 902 sending the transcoded first data stream to the third CDN central node 903 is described in step 508 of method 500 shown in Figure 5, which will not be described in detail here.

[0275] Optionally, the second CDN center node 902 includes a first scheduling strategy;

[0276] At least one third CDN center node 903 in the CDN center nodes is used to send a second pull request to the second CDN center node 902;

[0277] The second CDN center node 902 is used to send a first pull request to the first CDN center node based on the first information and the second pull request when selecting the first CDN center node to transcode the data stream according to the first scheduling strategy.

[0278] Optionally, the detailed implementation process of the third CDN center node 903 sending the second pull request to the second CDN center node 902 is described in detail in step 505 of method 500 shown in Figure 5, and will not be described in detail here.

[0279] Optionally, when the second CDN center node 902 selects the first CDN center node to transcode the data stream based on the first scheduling strategy, the detailed implementation process of sending the first pull request to the first CDN center node based on the first information and the second pull request is described in detail in step 506 of method 500 shown in Figure 5, and will not be described in detail here.

[0280] Optionally, the third CDN center node 903 includes the second scheduling strategy;

[0281] The third CDN center node 903 is used to send the second pull request to the second CDN center node 902 when selecting the second CDN center node 902 based on the second scheduling strategy.

[0282] Optionally, when the third CDN center node 903 selects the second CDN center node 902 based on the second scheduling strategy, the detailed implementation process of sending the second pull request to the second CDN center node 902 is described in detail in step 505 of method 500 shown in Figure 5, and will not be described in detail here.

[0283] Optionally, the content distribution system 900 further includes a global management platform 904;

[0284] The first CDN center node 901 is further configured to send second information to the global management platform 904 and at least one CDN center node, the second information including the identification information and location information of the transcoded first data stream;

[0285] The global management platform 904 is configured to send the second information to CDN center nodes other than the first CDN center node 901;

[0286] Wherein, the timestamp of each CDN center node receiving the second information sent by the first CDN center node 901 is earlier than the timestamp of receiving the second information sent by the global management platform 904.

[0287] Optionally, the detailed implementation process of the first CDN center node 901 sending the second information is described in detail in step 507 of method 500 shown in Figure 5, and will not be described in detail here.

[0288] Optionally, the global management platform 904 sends the second information to CDN center nodes other than the first CDN center node 901.For a detailed explanation of the information implementation process, please refer to step 507 of method 500 shown in Figure 5, which will not be elaborated further here.

[0289] Optionally, the region also includes a live streaming origin data platform 905, and the first CDN center node 901 includes a third scheduling strategy, and the first pull request carries a transcoding template;

[0290] The first CDN center node 901 is also used to send a first data stream to the live streaming origin data platform 905;

[0291] The first CDN center node 901 is also used to send a third pull request to the live streaming origin data platform when selecting the live streaming origin data platform to transcode the data stream based on the third scheduling strategy, and the third pull request carries a transcoding template;

[0292] The live streaming origin data platform 905 is used to transcode the first data stream based on the transcoding template to obtain the transcoded first data stream;

[0293] The live streaming origin data platform 905 is also used to send the transcoded first data stream to the first CDN center node 901;

[0294] The first CDN center node 901 is used to send the transcoded first data stream to the second CDN center node 902.

[0295] Optionally, the detailed implementation process of the first CDN central node 901 sending the first data stream to the live streaming origin data platform 905 is described in detail in step 503 of method 500 shown in Figure 5, and will not be described in detail here.

[0296] Optionally, when the first CDN central node 901 selects the live streaming origin data platform to transcode the data stream based on the third scheduling strategy, the detailed implementation process of sending the third pull request to the live streaming origin data platform is described in detail in step 507 of method 500 shown in Figure 5, and will not be described in detail here.

[0297] Optionally, the detailed implementation process of the live streaming origin data platform 905 transcoding the first data stream based on the transcoding template to obtain the transcoded first data stream is described in detail in step 708 of method 700 shown in Figure 7, and will not be described in detail here. (See page 25 / 29, CN 121357336 A for details.)

[0298] Optionally, the detailed implementation process of the live streaming origin data platform 905 sending the transcoded first data stream to the first CDN central node 901 is described in detail in step 709 of method 700 shown in Figure 7, and will not be described in detail here.

[0299] Optionally, the detailed implementation process of the first CDN central node 901 sending the transcoded first data stream to the second CDN central node 902 is described in detail in step 507 of method 500 shown in Figure 5, and will not be described in detail here.

[0300] Optionally, the range of the region is determined based on the latency and / or distance between the multiple CDN central nodes included in the region.

[0301] In this embodiment of the application, since the first CDN central node and at least one CDN central node are located in the same region...In the region, after receiving the first data stream, the first CDN central node sends the first information of the first data stream to at least one CDN central node, and each of the at least one CDN central nodes quickly receives the first information. In this way, when the second CDN central node in the at least one CDN central node requests to pull the data stream, the second CDN central node receives the first information earlier than the received pull request, so based on the first information, it can be determined that the data stream to be pulled is located on the first CDN central node, and the data stream is pulled from the first CDN central node. In this way, when a user in the region pulls the data stream of a live user, the data stream can be pulled on the CDN central node in the region through the first information, thereby reducing the latency of pulling the data stream and network resources.

[0302] Referring to FIG10, this application embodiment provides a device 1000 for processing data streams, which is deployed on the live source data platform in the content delivery network 100 shown in FIG1, FIG2, FIG3 or FIG4. The device 1000 includes a fourth scheduling strategy. The area where the device 1000 is located also includes a third-party transcoding service platform and a content delivery network (CDN) central node. The device 1000 includes:

[0303] a receiving unit 1001, used to receive a first data stream sent by the CDN central node;

[0304] the receiving unit 1001 is also used to receive a third pull request, the third pull request carrying a transcoding template;

[0305] a sending unit 1002, used to send a fourth pull request and a first data stream to the third-party transcoding service platform when selecting the third-party transcoding service platform to transcode the data stream based on the fourth scheduling strategy. The fourth pull request is used to instruct the third-party transcoding service platform to transcode the first data stream based on the transcoding template to obtain the transcoded first data stream;

[0306] the receiving unit 1001 is also used to receive the transcoded first data stream sent by the third-party transcoding service platform.

[0307] Optionally, the detailed implementation process of the receiving unit 1001 receiving the first data stream sent by the CDN central node is described in detail in step 701 of method 700 shown in Figure 7, and will not be described in detail here.

[0308] Optionally, the detailed implementation process of the receiving unit 1001 receiving the third pull request is described in detail in step 702 of method 700 shown in Figure 7, and will not be described in detail here.

[0309] Optionally, the detailed implementation process of the sending unit 1002 sending the fourth pull request and the first data stream to the third-party transcoding service platform is described in detail in step 704 of method 700 shown in Figure 7, and will not be described in detail here.

[0310] Optionally, the detailed implementation process of the receiving unit 1001 receiving the transcoded first data stream sent by the third-party transcoding service platform is described in detail in step 707 of method 700 shown in Figure 7, and will not be described in detail here.

[0311] Optionally, the device 1000 further includes: a processing unit 1003;

[0312] The processing unit 1003 is used to transcode the first data stream based on the transcoding template when selecting the device 1000 to transcode the data stream based on the fourth scheduling strategy, to obtain the transcoded first data stream.

[0313] Optionally, the detailed implementation process of the processing unit 1003 transcoding the first data stream based on the transcoding template to obtain the transcoded first data stream is described in detail in step 708 of method 700 shown in Figure 7, and will not be described in detail here.

[0314] Optionally, the sending unit 1002 is also used to send third information to the global management platform. The third information includes the identification information and location information of the first data stream after page 26 / 29 of the transcoding specification 33 CN 121357336 A.

[0315] Optionally, the detailed implementation process of the sending unit 1002 sending the third information to the global management platform is described in detail in step 709 of method 700 shown in Figure 7, and will not be described in detail here.

[0316] In this embodiment of the application, when the sending unit 1002 selects a third-party transcoding service platform to transcode the data stream based on the fourth scheduling strategy, it sends a fourth pull request and a first data stream to the third-party transcoding service platform. The fourth pull request is used to instruct the third-party transcoding service platform to transcode the first data stream based on the transcoding template to obtain the transcoded first data stream. In this way, the transcoding tasks of the device 1000 can be distributed through the third-party transcoding service platform.

[0317] Referring to FIG11, this embodiment of the application provides a device 1100 for processing data streams. The device is deployed on a global management platform in the content delivery network 100 shown in FIG1, FIG2, FIG3 or FIG4. The device 1100 is used to manage the live streaming source data platform and the content delivery network (CDN) central node included in the region. The CDN central node is used to send a first data stream to the live streaming source data platform. The device 1100 includes:

[0318] a receiving unit 1101, used to receive second information sent by the CDN central node when transcoding the first data stream to obtain a transcoded first data stream. The second information includes the identification information and first location information of the transcoded first data stream;

[0319] the receiving unit 1101 is also used to receive third information sent by the live streaming source data platform when transcoding the first data stream to obtain a transcoded first data stream. The third information includes the identification information and second location information of the transcoded first data stream;

[0320] a processing unit 1102, used to stop one of the CDN central node and the live streaming source data platform from continuing to transcode the first data stream when it is determined, based on the second information and the third information, that the CDN central node and the live streaming source data platform are repeatedly transcoding the first data stream.

[0321] Optionally, the device 1100 further includes: a transmitting unit 1103, configured to:

[0322] A first stop command is sent to the CDN central node, which instructs the CDN central node to stop transcoding the first data stream; or,

[0323] a second stop command is sent to the live streaming origin data platform, which instructs the live streaming origin data platform to stop transcoding the first data stream.

[0324] In this embodiment, when the processing unit determines, based on the second and third information, that the CDN central node and the live streaming origin data platform are repeatedly transcoding the first data stream, it stops one of the CDN central node and the live streaming origin data platform from continuing to transcode the first data stream. This allows one device to continue transcoding the first data stream, stopping repeated transcoding, thus saving computing and network resources.

[0325] Referring to Figure 12, this embodiment provides a computing device 1200. For example, the computing device 1200 may be a CDN central node, a live streaming origin data platform, or a global management platform in the content delivery network 100 shown in Figures 1-4.

[0326] As shown in FIG12, the computing device 1200 includes: a bus 1202, a processor 1204, a memory 1206, and a communication interface 1208. The processor 1204, the memory 1206, and the communication interface 1208 communicate with each other via the bus 1202. The computing device 1200 may be a server or a terminal device. It should be understood that this application does not limit the number of processors and memories in the computing device 1200.

[0327] The bus 1202 may be a peripheral component interconnect (PCI) bus or an extended industry standard architecture (EISA) bus, etc. The bus may be divided into address bus, data bus, control bus, etc. For ease of representation, only one line is used in FIG12, but it does not mean that there is only one bus or one type of bus. The bus 1202 may include a path for transmitting information between various components of the computing device 1200 (e.g., processor 1204, memory 1206, communication interface 1208). Specification page 27 / 29 34 CN 121357336 A

[0328] The processor 1204 may include any one or more of the following processors: central processing unit (CPU), graphics processing unit (GPU), microprocessor (MP), or digital signal processor (DSP).

[0329] The memory 1206 may include volatile memory.The memory 1206 may include non-volatile memory, such as read-only memory (ROM), flash memory, hard disk drive (HDD), or solid-state drive (SSD).

[0330] The memory 1206 stores executable program code, which the processor 1204 executes to implement the functions of the first CDN central node 901, the second CDN central node 902, or the third CDN central node 903 in the content distribution system 900 shown in FIG. 9, thereby implementing the method provided in any of the above embodiments. That is, the memory 1206 stores instructions for executing the method provided in any of the above embodiments. Alternatively,

[0331] Referring to FIG. 13, the memory 1206 stores executable program code, and the processor 1204 executes the executable program code to implement the functions of the receiving unit 1001, the transmitting unit 1002, and the processing unit 1003 in the device 1000 shown in FIG. 10, thereby implementing the method provided in any of the above embodiments. That is, the memory 1206 stores instructions for executing the method provided in any of the above embodiments. Alternatively,

[0332] Referring to FIG. 13, the memory 1206 stores executable program code, and the processor 1204 executes the executable program code to implement the functions of the receiving unit 1101, the processing unit 1102, and the transmitting unit 1103 in the device 1100 shown in FIG. 11, thereby implementing the method provided in any of the above embodiments. That is, the memory 1206 stores instructions for executing the method provided in any of the above embodiments. Alternatively,

[0333] the communication interface 1208 uses a transceiver module, such as, but not limited to, a network interface card or transceiver, to realize communication between the computing device 1200 and other devices or communication networks.

[0334] This application embodiment also provides a cluster for processing data streams. The cluster for processing data streams includes at least one computing device. The computing device may be a server, such as a central server, an edge server, or a local server in a local data center. In some embodiments, the computing device may also be a desktop computer, a laptop computer, or a smartphone or other terminal device.

[0335] As shown in FIG14, the cluster for processing data streams includes at least one computing device 1200. The memory 1206 in one or more computing devices 1200 in the cluster for processing data streams may store the same instructions for performing the methods provided in any of the above embodiments.

[0336] In some possible implementations, the memory 1206 of one or more computing devices 1200 in the data stream processing cluster may also store partial instructions for executing the above-described data stream processing method. In other words, a combination of one or more computing devices 1200 can jointly execute instructions for executing the method provided in any of the above embodiments.

[0337] In some possible implementations, one or more computing devices in the data stream processing cluster can be connected via a network. The network may be a wide area network or a local area network, etc. FIG14 shows one possible implementation. As shown in FIG14, two computing devices 1200A and 1200B are connected via a network. Specifically, they are connected to the network through the communication interface in each computing device.

[0338] In some possible implementations, the memory 1206 in computing device 1200A stores instructions for executing the function of processing unit 1003 in the embodiment shown in FIG10. At the same time, the memory 1206 in computing device 1200B stores instructions for executing the functions of receiving unit 1001 and sending unit 1002 in the embodiment shown in FIG10.

[0339] In some possible implementations, the memory 1206 in computing device 1200A stores instructions for performing the functions of processing unit 1102 in the embodiment shown on pages 28 / 29 of FIG11 (CN 121357336 A). Simultaneously, the memory 1206 in computing device 1200B stores instructions for performing the functions of receiving unit 1101 and sending unit 1103 in the embodiment shown in FIG11.

[0340] It should be understood that the functions of computing device 1200A shown in FIG14 can also be performed by multiple computing devices 1200. Similarly, the functions of computing device 1200B can also be performed by multiple computing devices 1200.

[0341] This application embodiment also provides another data stream processing cluster. The connection relationship between the computing devices in this data stream processing cluster can be similarly referred to the connection method of the data stream processing cluster shown in FIG14. The difference is that the memory 1206 of one or more computing devices 1200 in the data stream processing cluster may store the same instructions for executing the methods provided in any of the above embodiments.

[0342] In some possible implementations, the memory 1206 of one or more computing devices 1200 in the data stream processing cluster may also store partial instructions for executing the methods provided in any of the above embodiments. In other words, a combination of one or more computing devices 1200 can jointly execute the instructions for executing the methods provided in any of the above embodiments.

[0343] This application embodiment also provides a computer program product containing instructions. The computer program product can...This refers to a software or program product containing instructions that can run on a computing device or be stored in any available medium. When the computer program product is run on at least one computing device, it causes the at least one computing device to perform the methods provided in any of the above embodiments.

[0344] This application embodiment also provides a computer-readable storage medium. The computer-readable storage medium can be any available medium that a computing device can store or a data storage device such as a data center containing one or more available media. The available medium can be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., solid-state drive), etc. The computer-readable storage medium includes instructions that instruct a computing device to perform the methods provided in any of the above embodiments.

[0345] Those skilled in the art will understand that all or part of the steps of the above embodiments can be implemented by hardware, or by a program instructing related hardware. The program can be stored in a computer-readable storage medium, such as a read-only memory, a disk, or an optical disk, etc.

[0346] The above description is only an optional embodiment of this application and is not intended to limit this application. Any modifications, equivalent substitutions, improvements, etc. made within the principles of this application should be included within the protection scope of this application. Instruction manual page 29 / 29, page 36, CN 121357336 A, Figure 1; Instruction manual figure 1 / 12, page 37, CN 121357336 A, Figure 2; Instruction manual figure 2 / 12, page 38, CN 121357336 A, Figure 3; Instruction manual figure 3 / 12, page 39, CN 121357336 A, Figure 4; Instruction manual figure 4 / 12, page 40, CN 121357336 A, Figure 5; Instruction manual figure 5 / 12, page 41, CN 121357336 A, Figure 6; Instruction manual figure 6 / 12, page 42, CN 121357336 A, Figure 7; Instruction manual figure 7 / 12, page 43, CN 121357336 A, Figure 8; Instruction manual figure 8 / 12, page 44, CN 121357336 A, Figure 9; Figure 10; Instruction manual figure 9 / 12, page 45, CN 121357336 A, Figure 11. Figure 12 Appendix to the Instruction Manual, Page 10 / 12, 46 CN 121357336 A Figure 13 Appendix to the Instruction Manual, Page 11 / 12, 47 CN 121357336 A Figure 14 Appendix to the Instruction Manual, Page 12 / 12, 48 CN 121357336 A Abstract The presentapplication relates to the field of communications, and discloses a data stream processing method and apparatus, a system, and a storage medium. The method is applied to a content delivery system. The content delivery system comprises a first CDN central node, and a region where the first CDN central node is located further comprises at least one CDN central node. The method comprises: the first CDN central node receives a first data stream of a live- streaming service; the first CDN central node separately sends first information of the first data stream to the at least one CDN central node, wherein the first information comprises identification information of the first data stream and location information; a second CDN central node among the at least one CDN central node sends a first pull-stream request to the first CDN central node on the basis of the first information; the first CDN central node sends the first data stream to the second CDN central node. The present applicationcan reduce latency and save network resources.

Claims

1. A method of processing a data stream, characterized by, The method is applied to a content distribution system, the content distribution system comprising a first content distribution network (CDN) center node, a region where the first CDN center node is located further comprising at least one CDN center node, the method comprising: The first CDN center node receives a first data stream of a live broadcast service; The first CDN center node sends first information of the first data stream to the at least one CDN center node respectively, the first information comprising identification information and location information of the first data stream; A second CDN center node in the at least one CDN center node sends a first pull stream request to the first CDN center node based on the first information; The first CDN center node sends the first data stream to the second CDN center node.

2. The method of claim 1, wherein, The first pull stream request carries a transcoding template, and the first CDN center node sending the first data stream to the second CDN center node comprises: The first CDN center node transcodes the first data stream based on the transcoding template to obtain transcoded first data stream; The first CDN center node sends the transcoded first data stream to the second CDN center node.

3. The method of claim 1 or 2, wherein, The second CDN center node sends a first pull stream request to the first CDN center node based on the first information comprises: The second CDN center node sends the first pull stream request to the first CDN center node based on the first information after receiving a second pull stream request from a terminal device.

4. The method of claim 1, wherein, The first pull stream request carries a transcoding template, and the second CDN center node sending a first pull stream request to the first CDN center node based on the first information further comprises: A third CDN center node in the at least one CDN center node sends a second pull stream request to the second CDN center node, the second pull stream request being used to request the second CDN center node to send the first pull stream request to the first CDN center node based on the first information; The first CDN center node sending the first data stream to the second CDN center node further comprises: The second CDN center node transcodes the first data stream based on the transcoding template to obtain transcoded first data stream; The second CDN center node sends the transcoded first data stream to the third CDN center node.

5. The method of claim 1 or 2, wherein, The second CDN center node comprises a first scheduling strategy, and the second CDN center node sending a first pull stream request to the first CDN center node based on the first information further comprises: A third CDN center node in the at least one CDN center node sends a second pull stream request to the second CDN center node; The second CDN center node sending a first pull stream request to the first CDN center node based on the first information comprises: The second CDN center node sends the first pull stream request to the first CDN center node based on the first information and the second pull stream request based on the first scheduling strategy of selecting the first CDN center node to transcode the data stream.

6. The method of claim 4 or 5, wherein, The third CDN center node comprises a second scheduling strategy, and the third CDN center node sends a second pull stream request to the second CDN center node, comprising: The third CDN center node sends the second pull stream request to the second CDN center node based on the second scheduling strategy of selecting the second CDN center node.

7. The method of claim 2, wherein, The method further comprises: The first CDN center node sends second information to a global management platform and the at least one CDN center node, the second information comprising identification information and location information of the transcoded first data stream, and the global management platform is configured to send the second information to CDN center nodes other than the first CDN center node. Wherein, the receiving time stamp of the second information sent by the first CDN center node is earlier than the receiving time stamp of the second information sent by the global management platform.

8. The method according to any one of claims 1 to 7, wherein, The slice further comprises a live source station data platform, the first CDN center node comprises a third scheduling strategy, and the first pull stream request carries a transcoding template, and the method further comprises: The first CDN center node sends the first data stream to the live source station data platform; The first CDN center node sends a third pull stream request to the live source station data platform based on the third scheduling strategy of selecting the live source station data platform to transcode the data stream, and the third pull stream request carries the transcoding template; The live source station data platform transcodes the first data stream based on the transcoding template to obtain the transcoded first data stream; The live source station data platform sends the transcoded first data stream to the first CDN center node; The first CDN center node sends the first data stream to the second CDN center node, comprising: The first CDN center node sends the transcoded first data stream to the second CDN center node.

9. The method according to any one of claims 1 to 8, wherein, The range of the slice is determined based on the time delay and / or distance between the plurality of CDN center nodes comprised by the slice.

10. A method of processing a data stream, characterized by, The method is applied to a live source station data platform comprised by a slice, the live source station data platform comprises a fourth scheduling strategy, the slice further comprises a third-party transcoding service platform and a content distribution network (CDN) center node, and the method comprises: The live source station data platform receives a first data stream sent by the CDN center node; The live source station data platform receives a third pull stream request, and the third pull stream request carries a transcoding template; The live source station data platform transcodes the first data stream based on the transcoding template to obtain a transcoded first data stream; The live source station data platform sends the transcoded first data stream to the CDN center node; and The CDN center node receives the transcoded first data stream sent by the live source station data platform. The live source station data platform sends a fourth pull stream request and the first data stream to the third-party transcoding service platform when selecting the third-party transcoding service platform to transcode the data stream based on the fourth scheduling strategy, and the fourth pull stream request is used to instruct the third-party transcoding service platform to transcode the first data stream based on the transcoding template to obtain the transcoded first data stream. The live source station data platform receives the transcoded first data stream sent by the third-party transcoding service platform.

11. The method of claim 10, wherein, The method further comprises: The live source station data platform transcodes the first data stream based on the transcoding template to obtain the transcoded first data stream when selecting the live source station data platform to transcode the data stream based on the fourth scheduling strategy.

12. The method of claim 10 or 11, wherein, The method further comprises: The live source station data platform sends third information to the global management platform, and the third information includes identification information and location information of the transcoded first data stream.

13. A method of processing a data stream, characterized by, The method is applied to a global management platform, the global management platform is used to manage live source station data platforms and content distribution network (CDN) center nodes included in a region, and the CDN center nodes are used to send first data streams to the live source station data platforms. The method comprises: The global management platform receives second information sent by the CDN center node when the CDN center node transcodes the first data stream to obtain the transcoded first data stream, and the second information includes identification information and first location information of the transcoded first data stream. The global management platform receives third information sent by the live source station data platform when the live source station data platform transcodes the first data stream to obtain the transcoded first data stream, and the third information includes identification information and second location information of the transcoded first data stream. The global management platform stops one of the CDN center node and the live source station data platform from continuing to transcode the first data stream based on the second information and the third information when the CDN center node and the live source station data platform repeatedly transcode the first data stream.

14. The method of claim 13, wherein, The global management platform stops one of the CDN center node and the live source station data platform from continuing to transcode the first data stream, comprising: The global management platform sends a first stop command to the CDN center node, and the first stop command is used to instruct the CDN center node to stop continuing to transcode the first data stream; or The global management platform sends a second stop command to the live source station data platform, and the second stop command is used to instruct the live source station data platform to stop continuing to transcode the first data stream.

15. A content distribution system characterized by comprising: The content distribution system comprises a first content distribution network (CDN) center node, and a region where the first CDN center node is located further comprises at least one CDN center node; The first CDN center node is used to receive a first data stream of live streaming service; The first CDN center node is used to receive a first data stream of live streaming service; The first CDN center node is further configured to send first information of the first data stream to the at least one CDN center node respectively, the first information comprising identification information and location information of the first data stream; A second CDN center node in the at least one CDN center node is configured to send a first pull stream request to the first CDN center node based on the first information; The first CDN center node is further configured to send the first data stream to the second CDN center node.

16. The content distribution system of claim 15, wherein, The first pull stream request carries a transcoding template, and the first CDN center node is configured to: transcode the first data stream based on the transcoding template to obtain transcoded first data stream; and send the transcoded first data stream to the second CDN center node.

17. The content distribution system of claim 15 or 16, wherein, The second CDN center node is configured to send the first pull stream request to the first CDN center node based on the first information after receiving a second pull stream request from a terminal device.

18. The content distribution system of claim 15, wherein, The first pull stream request carries a transcoding template; A third CDN center node in the at least one CDN center node is configured to send a second pull stream request to the second CDN center node, the second pull stream request being used to request the second CDN center node to send the first pull stream request to the first CDN center node based on the first information; The second CDN center node is further configured to transcode the first data stream based on the transcoding template to obtain transcoded first data stream; The second CDN center node is further configured to send the transcoded first data stream to the third CDN center node.

19. The content distribution system of claim 15 or 16, wherein, The second CDN center node comprises a first scheduling strategy; The third CDN center node in the at least one CDN center node is configured to send a second pull stream request to the second CDN center node; The second CDN center node is configured to send the first pull stream request to the first CDN center node based on the first information and the second pull stream request when the first CDN center node is selected by the second CDN center node to transcode a data stream based on the first scheduling strategy.

20. The content distribution system of claim 18 or 19, wherein, The third CDN center node comprises a second scheduling strategy; The third CDN center node is configured to send the second pull stream request to the second CDN center node when the second CDN center node is selected based on the second scheduling strategy.

21. The content distribution system of claim 16, wherein, The content distribution system further comprises a global management platform; The first CDN center node is further configured to send second information to the global management platform and the at least one CDN center node, the second information comprising identification information and location information of the transcoded first data stream; The global management platform is configured to send the second information to CDN center nodes other than the first CDN center node; The receiving time stamp of the second information sent by the first CDN center node is earlier than the receiving time stamp of the second information sent by the global management platform.

22. The content distribution system of any of claims 15-21, wherein, The slice area further comprises a live source station data platform, the first CDN center node comprises a third scheduling strategy, and the first pull stream request carries a transcoding template; The first CDN center node is further configured to send the first data stream to the live source station data platform; The first CDN center node is further configured to send a third pull stream request to the live source station data platform based on the third scheduling strategy when the live source station data platform is selected to transcode the data stream, and the third pull stream request carries the transcoding template; The live source station data platform is configured to transcode the first data stream based on the transcoding template to obtain transcoded first data stream; The live source station data platform is further configured to send the transcoded first data stream to the first CDN center node; The first CDN center node is configured to send the transcoded first data stream to the second CDN center node.

23. The content distribution system of any of claims 15-22, wherein, The range of the slice area is determined based on the time delay and / or distance between the plurality of CDN center nodes comprised in the slice area.

24. An apparatus for processing a data stream, the apparatus comprising: The device comprises a fourth scheduling strategy, and a third-party transcoding service platform and a content distribution network (CDN) center node are further comprised in the slice area in which the device is located, and the device comprises: The receiving unit is configured to receive a first data stream sent by the CDN center node; The receiving unit is further configured to receive a third pull stream request, and the third pull stream request carries a transcoding template; The sending unit is configured to send a fourth pull stream request and the first data stream to the third-party transcoding service platform based on the fourth scheduling strategy when the third-party transcoding service platform is selected to transcode the data stream, and the fourth pull stream request is used to instruct the third-party transcoding service platform to transcode the first data stream based on the transcoding template to obtain transcoded first data stream; The receiving unit is further configured to receive the transcoded first data stream sent by the third-party transcoding service platform.

25. The apparatus of claim 24, wherein, The device further comprises a processing unit; The processing unit is configured to transcode the first data stream based on the transcoding template to obtain transcoded first data stream based on the fourth scheduling strategy when the device is selected to transcode the data stream.

26. The apparatus of claim 24 or 25, wherein, The sending unit is further configured to send third information to a global management platform, and the third information comprises identification information and location information of the transcoded first data stream.

27. An apparatus for processing a data stream, the apparatus comprising: The device is used to manage a live source station data platform and a content distribution network (CDN) center node comprised in a slice area, the CDN center node is configured to send a first data stream to the live source station data platform, and the device comprises: The receiving unit is configured to receive second information sent by the CDN center node when the CDN center node transcodes the first data stream to obtain transcoded first data stream, and the second information comprises identification information and first location information of the transcoded first data stream. The receiving unit is further configured to receive third information sent by the live source station data platform when the live source station data platform transcodes the first data stream to obtain transcoded first data stream, the third information comprising identification information and second location information of the transcoded first data stream; The processing unit is configured to determine, based on the second information and the third information, that when the CDN center node and the live source station data platform repeatedly transcode the first data stream, one of the CDN center node and the live source station data platform stops transcoding the first data stream.

28. The apparatus of claim 27, wherein, The apparatus further comprises a sending unit configured to: send a first stop command to the CDN center node, the first stop command being used to instruct the CDN center node to stop transcoding the first data stream; or send a second stop command to the live source station data platform, the second stop command being used to instruct the live source station data platform to stop transcoding the first data stream.

29. A cluster of computing devices, characterized in that, at least one computing device, each computing device comprising a processor and a memory; the processor of the at least one computing device is configured to execute instructions stored in the memory of the at least one computing device to cause the cluster of computing devices to perform the method of any one of claims 1-14.

30. A computer-readable storage medium, characterized in that, computer program instructions that, when executed by a cluster of computing devices, cause the cluster of computing devices to perform the method of any one of claims 1-14.

31. A computer program product comprising instructions, wherein: the instructions, when executed by a cluster of computing devices, cause the cluster of computing devices to perform the method of any one of claims 1-14.