CDN-based audio and video transmission, playback and delay detection method and equipment

By using CDN and tracking ID technology in the audio and video live broadcast system, the problem of large amount of log data in the audio and video live broadcast is solved, and fast and accurate fault analysis and positioning is achieved, improving the problem-solving efficiency.

CN113301397BActive Publication Date: 2024-11-15ALIBABA GROUP HOLDING LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202110191754.X
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2021-02-19
Publication Date
2024-11-15
Estimated Expiration
2041-02-19

AI Technical Summary

Technical Problem

The amount of log data generated by existing audio and video live broadcast content is large, which leads to low problem tracking efficiency and makes it difficult to quickly and accurately analyze the causes of playback abnormalities.

Method used

Using CDN-based audio and video transmission method, the audio and video data streams are distinguished by generating unique identifiers (tracking IDs) on the playback and data source, and the audio and video data streams are reduced to the amount of log data required for analysis, and accurately and quickly Positioning playback abnormality problem.

Benefits of technology

It improves the efficiency of analyzing playback abnormal problems, reduces the time for log data analysis, and achieves more accurate fault location and resolution.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN113301397B_ABST
    Figure CN113301397B_ABST
Patent Text Reader

Abstract

The embodiment of the present application provides a CDN-based audio and video transmission, playback and delay detection method and device. In the embodiment of the present application, for various audio and video application scenarios that adopt the push-pull streaming method, in the push-pull streaming process, the audio and video data stream is first distinguished and marked from the perspective of the playback end, so as to facilitate the search for the log data generated by the audio and video data stream on the transmission link for the specific playback end, which can reduce the log data required for analysis, thereby accurately and quickly analyzing the causes of abnormal problems on the playback end. Furthermore, the audio and video data stream is segmented from the perspective of the data source end, and the segmented stream segments are distinguished and marked, and the log data generated by tracking specific stream segments can be further targeted, which can further reduce the log data required for analysis, and can more accurately and quickly analyze playback anomalies and other problems, thereby improving the efficiency of problem solving.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present application relates to the technical field of audio and video processing, and in particular to a CDN-based audio and video transmission, playback and delay detection method and device. Background Art

[0002] With the development of real-time communication (RTC) technology, many audio and video applications that support low latency and online interaction have emerged, such as live video, video on demand, video conferencing, etc. These audio and video applications usually use streaming protocols, involving streaming ends and playback ends. The streaming end is responsible for collecting audio and video data, encapsulating the audio and video data using the transmission protocol and transmitting the encapsulated audio and video data to the network. Finally, the playback end pulls the audio and video data from the network and plays it after decapsulation.

[0003] Taking live video applications as an example, in order to improve the user's viewing experience, service providers will rely more on content delivery networks (CDNs) to speed up the distribution of audio and video content. As the streaming end, the live broadcast end can push the live content to the nearest CDN node, and the playback end sends a playback request to the nearest CDN node, and plays the live content after pulling it from the CDN network.

[0004] During the entire push-pull streaming process, playback failure, playback anomaly, or playback delay may occur due to various reasons. In order to quickly and accurately solve the problem, the cause of the problem can be tracked through the log data generated by the live content on the transmission link. However, the amount of log data generated by the existing live content is large, and problem tracking is time-consuming and inefficient. Summary of the invention

[0005] Multiple aspects of the present application provide a CDN-based audio and video transmission, playback and delay detection method and device, which are used to more accurately and quickly analyze playback anomalies and other problems, thereby improving the efficiency of problem solving.

[0006] An embodiment of the present application provides an audio and video transmission method, which is applicable to a network node, including: receiving a playback request sent by a playback end, the playback request including a target stream identifier, which is used to identify the audio and video data stream requested to be played by the playback end; generating a first tracking ID that can uniquely identify the playback end, and recording the corresponding relationship between the first tracking ID and the audio and video data stream; obtaining the audio and video data stream from the data source end, and returning the audio and video data stream to the playback end, so that the playback end can play the audio and video data stream.

[0007] The embodiment of the present application also provides a CDN-based live streaming transmission method, which is applicable to CDN nodes, including: receiving a playback request sent by a playback end, the playback request including a target stream identifier, which is used to identify the live stream that the playback end requests to play; generating a first tracking ID that can uniquely identify the playback end, and recording the corresponding relationship between the first tracking ID and the live stream; obtaining the live stream from the live stream end, and returning the live stream to the playback end, so that the playback end can play the live stream.

[0008] An embodiment of the present application also provides a CDN-based video conferencing method, which is applicable to CDN nodes, including: receiving a conference request sent by a conference terminal, the conference request including a conference identifier for identifying a conference video stream; generating a first tracking ID that can uniquely identify the conference terminal, and recording the correspondence between the first tracking ID and the conference video stream; obtaining a conference video stream from other conference terminals, and returning the conference video stream to the conference terminal so that the conference terminal can play the conference video stream.

[0009] The embodiment of the present application also provides an audio and video transmission method, which is applicable to a network node, including: receiving a first acquisition request, the first acquisition request is sent by a previous-hop network node on a target path of the network node, and the first acquisition request includes a second tracking ID; recording the correspondence between the second tracking ID and the audio and video data stream, the second tracking ID is used to track the node on the target path, and the target path is the path required to obtain the audio and video data stream; obtaining the audio and video data stream, and returning the audio and video data stream to the previous-hop network node that sent it, so that the previous-hop network node returns the audio and video data stream to the playback end that requests the audio and video data stream.

[0010] The embodiment of the present application also provides a CDN-based live streaming transmission method, which is applicable to CDN nodes, including: receiving a first acquisition request, the first acquisition request is sent by the previous-hop CDN node of the CDN node on the back-to-source path, and the first acquisition request includes a second tracking ID; recording the correspondence between the second tracking ID and the live stream, the second tracking ID is used to track the CDN node on the back-to-source path, and the back-to-source path is the path required to obtain the live stream; obtaining the live stream from the live end, and returning the live stream to the previous-hop CDN node, so that the previous-hop CDN node can return the live stream to the playback end that requests the live stream.

[0011] The embodiment of the present application also provides a CDN-based video conferencing method, which is applicable to CDN nodes, including: receiving a first acquisition request, the first acquisition request is sent by the previous-hop CDN node of the CDN node on the back-to-source path, and the first acquisition request includes a second tracking ID; recording the correspondence between the second tracking ID and the conference video stream, the second tracking ID is used to track the CDN node on the back-to-source path, and the back-to-source path is the path required to obtain the conference video stream; obtaining the conference video stream from other conference terminals, and returning the conference video stream to the previous-hop CDN node that sent it, so that the previous-hop CDN node can return the conference video stream to the conference terminal that initiated the conference request.

[0012] An embodiment of the present application also provides an audio and video transmission method, which is applicable to a network node, including: receiving an audio and video data stream sent by a data source; dividing the audio and video data stream into at least one stream segment according to a segmentation strategy; generating a third tracking ID for each of the at least one stream segments, wherein the third tracking ID can uniquely identify the stream segment to which it corresponds; and sending the at least one stream segment and its corresponding third tracking ID to a network node requesting the audio and video data stream.

[0013] An embodiment of the present application also provides an audio and video playback method, including: responding to an audio and video playback operation initiated by a user, sending a playback request to a network node, the playback request including a target stream identifier for identifying the audio and video data stream requested to be played by the user; receiving the audio and video data stream and a first tracking ID returned by the network node, the first tracking ID being generated by the network node and used to uniquely identify the playback end; playing the audio and video data stream, and recording the correspondence between the first tracking ID and the audio and video data stream.

[0014] An embodiment of the present application also provides a CDN-based live broadcast method, including: responding to a live broadcast operation initiated by a user, sending a playback request to a CDN node, the playback request including a target stream identifier for identifying the live stream requested to be played by the user; receiving the live stream returned by the CDN node and a first tracking ID, the first tracking ID being generated by the CDN node and used to uniquely identify the playback end; playing the live stream, and recording the correspondence between the first tracking ID and the live stream.

[0015] An embodiment of the present application also provides a CDN-based video conferencing method, including: responding to a user-initiated conference joining operation, sending a conference request to a CDN node, the conference request including a conference identifier for identifying the video conference requested by the user; receiving a conference video stream and a first tracking ID returned by the CDN node, the first tracking ID being generated by the CDN node and being used to uniquely identify a conference terminal that sends the conference request; playing the conference video stream, and recording the correspondence between the first tracking ID and the conference video stream.

[0016] An embodiment of the present application also provides a network delay detection method, which is applicable to a network node, including: receiving a playback request sent by a playback end, the playback request is used to request the playback of an audio and video data stream; sending a delay detection request to a next-hop network node that provides the audio and video data stream, the delay detection request includes a first time, and the first time is the local time when the network node sends the delay detection request; receiving a delay detection response returned by the next-hop network node, the delay detection response includes the first time; determining the delay between the network node and the next-hop network node based on the second time and the first time; the second time is the local time when the network node receives the delay detection response.

[0017] An embodiment of the present application also provides a network node, including: a memory and a processor; the memory is used to store a computer program; the processor is coupled to the memory and is used to execute the computer program, so as to: receive a playback request sent by a playback end, the playback request includes a target stream identifier, which is used to identify the audio and video data stream requested to be played by the playback end; generate a first tracking ID that can uniquely identify the playback end, and record the corresponding relationship between the first tracking ID and the audio and video data stream; obtain the audio and video data stream from the data source end, and return the audio and video data stream to the playback end so that the playback end can play the audio and video data stream.

[0018] An embodiment of the present application also provides a network node, including: a memory and a processor; the memory is used to store a computer program; the processor is coupled to the memory and is used to execute the computer program, so as to: receive a first acquisition request, the first acquisition request is sent by the previous-hop network node of the network node on the target path, and the first acquisition request includes a second tracking ID; record the correspondence between the second tracking ID and the audio and video data stream, the second tracking ID is used to track the node on the target path, and the target path is the path required to obtain the audio and video data stream; obtain the audio and video data stream, and return the audio and video data stream to the previous-hop network node that sent it, so that the previous-hop network node returns the audio and video data stream to the playback end that requests the audio and video data stream.

[0019] An embodiment of the present application also provides a network node, including: a memory and a processor; the memory is used to store a computer program; the processor is coupled to the memory and is used to execute the computer program, so as to: receive an audio and video data stream sent by a data source; according to a segmentation strategy, the audio and video data stream is segmented into at least one stream segment; a third tracking ID is generated for each of the at least one stream segment, and the third tracking ID can uniquely identify the stream segment to which it corresponds; and the at least one stream segment and its corresponding third tracking ID are sent to the network node requesting the audio and video data stream.

[0020] An embodiment of the present application also provides a network node, including: a memory and a processor; the memory is used to store a computer program; the processor is coupled to the memory and is used to execute the computer program, so as to: receive a playback request sent by a playback end, the playback request is used to request the playback of an audio and video data stream; send a delay detection request to a next-hop network node that provides the audio and video data stream, the delay detection request includes a first time, and the first time is the local time when the network node sends the delay detection request; receive a delay detection response returned by the next-hop network node, the delay detection response includes the first time; determine the delay between the network node and the next-hop network node based on the second time and the first time; the second time is the local time when the network node receives the delay detection response.

[0021] An embodiment of the present application also provides a playback terminal, including: a memory and a processor; the memory is used to store a computer program; the processor is coupled to the memory and is used to execute the computer program, so as to: respond to an audio and video playback operation initiated by a user, send a playback request to a network node, the playback request includes a target stream identifier, which is used to identify the audio and video data stream requested to be played by the user; receive the audio and video data stream returned by the network node and a first tracking ID, the first tracking ID is generated by the network node and is used to uniquely identify the playback terminal; play the audio and video data stream, and record the correspondence between the first tracking ID and the audio and video data stream.

[0022] An embodiment of the present application also provides a data transmission method, applicable to a network node, comprising: receiving a data request sent by a data receiving end, the data request comprising a data identifier for identifying target data requested by the data receiving end; generating a first tracking ID that can uniquely identify the data receiving end, and recording the corresponding relationship between the first tracking ID and the target data; obtaining the target data from a data source end, and returning the target data to the data receiving end.

[0023] An embodiment of the present application also provides a computer-readable storage medium storing a computer program. When the computer program is executed by a processor, the processor is enabled to implement the steps of any method provided in the embodiment of the present application.

[0024] An embodiment of the present application also provides a computer program product, including a computer program / instruction. When the computer program / instruction is executed by a processor, the processor is enabled to implement the steps of any method provided in the embodiment of the present application.

[0025] In the embodiments of the present application, for various audio and video application scenarios using push-pull streaming, in the push-pull streaming process, the audio and video data streams are first distinguished and marked from the perspective of the playback end, so as to facilitate the search for the log data generated by the audio and video data streams on the transmission link for a specific playback end, which can reduce the log data required for analysis, thereby accurately and quickly analyzing the causes of abnormal problems at the playback end. Further, the audio and video data streams are segmented from the perspective of the data source end, and the segmented stream segments are distinguished and marked, and the log data generated by tracking specific stream segments can be further targeted, which can further reduce the log data required for analysis, and can more accurately and quickly analyze playback abnormalities and other problems, thereby improving the efficiency of problem solving. BRIEF DESCRIPTION OF THE DRAWINGS

[0026] The drawings described herein are used to provide a further understanding of the present application and constitute a part of the present application. The illustrative embodiments of the present application and their descriptions are used to explain the present application and do not constitute an improper limitation on the present application. In the drawings:

[0027] Figure 1a A schematic diagram of the structure of an audio and video system provided for an exemplary embodiment of the present application;

[0028] Figure 1b A schematic diagram of the structure of another audio and video system provided for an exemplary embodiment of the present application;

[0029] Figure 1c A structural schematic diagram of another audio and video system provided for an exemplary embodiment of the present application;

[0030] Figure 2 A schematic diagram of the structure of a CDN-based live broadcast system provided for an exemplary embodiment of the present application;

[0031] Figure 3 A schematic diagram of the structure of a CDN-based video conferencing system provided for an exemplary embodiment of the present application;

[0032] Figure 4a A flowchart of an audio and video transmission method provided for an exemplary embodiment of the present application;

[0033] Figure 4b A flowchart of a CDN-based live streaming transmission method provided for an exemplary embodiment of the present application;

[0034] Figure 4c A flowchart of a CDN-based video conferencing method provided for an exemplary embodiment of the present application;

[0035] Figure 5a A flowchart of another audio and video transmission method provided for an exemplary embodiment of the present application;

[0036] Figure 5b A flowchart of another CDN-based live streaming transmission method provided for an exemplary embodiment of the present application;

[0037] Figure 5c A flowchart of another CDN-based video conferencing method provided for an exemplary embodiment of the present application;

[0038] Figure 6 A flowchart of another audio and video transmission method provided for an exemplary embodiment of the present application;

[0039] Figure 7a A flowchart of an audio and video playback method provided for an exemplary embodiment of the present application;

[0040] Figure 7b A flowchart of a CDN-based live broadcasting method provided for an exemplary embodiment of the present application;

[0041] Figure 7c A flowchart of a CDN-based video conferencing method provided for an exemplary embodiment of the present application;

[0042] Figure 8 A flowchart of a network delay detection method provided by an exemplary embodiment of the present application;

[0043] Figure 9a A schematic diagram of the structure of a network node provided for an exemplary embodiment of the present application;

[0044] Figure 9b A schematic diagram of the structure of a playback terminal provided for an exemplary embodiment of the present application. DETAILED DESCRIPTION

[0045] In order to make the purpose, technical solution and advantages of the present application clearer, the technical solution of the present application will be clearly and completely described below in combination with the specific embodiments of the present application and the corresponding drawings. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of the present application.

[0046] In view of the large amount of log data generated by existing live content, the problem tracking is time-consuming and inefficient. In the embodiment of the present application, for various audio and video application scenarios using push-pull streaming, in the push-pull streaming process, the audio and video data stream is first distinguished and marked from the perspective of the playback end, so as to facilitate the search for the log data generated by the audio and video data stream on the transmission link for the specific playback end. This can reduce the log data required for analysis, thereby accurately and quickly analyzing the causes of abnormal problems on the playback end. Furthermore, the audio and video data stream is segmented from the perspective of the data source, and the segmented stream segments are distinguished and marked. The log data generated by tracking specific stream segments can be further targeted. This can further reduce the log data required for analysis, and can more accurately and quickly analyze playback abnormalities and other problems, thereby improving the efficiency of problem solving.

[0047] The technical solutions provided by various embodiments of the present application are described in detail below in conjunction with the accompanying drawings.

[0048] Figure 1a A structural diagram of an audio and video system provided for an exemplary embodiment of the present application is shown in FIG. Figure 1a As shown, the audio and video system 100 includes: a playback end 101, a data source end 102, and a transmission network 103 between the playback end 101 and the data source end 102, and the transmission network 103 includes at least one network node. Figure 1b The network nodes L1, L2, L3 and L4 shown in FIG. 1 are connected to the playback terminal 101, and the network node L4 is connected to the data source terminal 102; the network node L2 and the network node L3 are located between the network node L1 and the network node L4. The number of network nodes in the transmission network 103 can be one or more. Figure 1b In the figure, four network nodes L1-L4 are taken as an example, but the present invention is not limited thereto.

[0049] The audio and video system of this embodiment can be applied to various audio and video scenarios using push-pull streams, such as audio and video live broadcast scenarios, video conferencing scenarios, audio and video on-demand scenarios, etc. In this embodiment, in this embodiment, the data source end 102 is responsible for providing audio and video data streams to the transmission network 103. For example, the audio and video acquisition module can be used to collect audio and video data, and the collected audio and video data can be encoded and processed using a streaming protocol to obtain an audio and video data stream, and the audio and video data stream is pushed to the transmission network 103. Correspondingly, the playback end 101 is responsible for pulling the audio and video data stream from the transmission network 103, while pulling the stream and playing. From the perspective of push-pull streams, the data source end 102 can also be called a push stream end, and the playback end 101 can also be called a pull stream end. In this embodiment, the content of the audio and video data stream is not limited. For example, it can be remote education content, shopping content in a live broadcast scenario, or video conferencing content or online game content. In addition, the streaming protocol adopted by the data source end 102 can be the Real Time Streaming Protocol (RTSP), the Real Time Messaging Protocol (RTMP), the HTTP Live Streaming (HLS), etc., without limitation.

[0050] In this embodiment, the physical implementation form of the playback terminal 101 is not limited. For example, the playback terminal 101 can be, but not limited to, various terminal devices such as mobile phones, tablet computers, desktop computers, smart screens, and interactive televisions. Similarly, this embodiment does not limit the physical implementation form of the data source terminal 102. It can be any device that can provide audio and video data streams. For example, the data source terminal 102 can be, but not limited to, various smart phones, tablet computers, desktop computers, touch screens, DVs, cameras, and other terminal devices with acquisition functions, and can also be some relay devices, storage devices, etc. that can provide audio and video data streams. Similarly, this embodiment does not limit the implementation form of the network nodes in the transmission network 103. For example, the network nodes can be various network devices with data transmission functions such as gateway devices, switch devices, and servers in the network.

[0051] In this embodiment, there may be multiple data sources 102 that can push audio and video data streams to the transmission network 103 respectively. Of course, the same data source 102 can also push different audio and video data streams to the transmission network 103 at different times. The data source 102 pushing the audio and video data stream to the transmission network 103 specifically refers to pushing the audio and video data stream to a network node in the transmission network 103 that is communicatively connected to the data source 102, such as Figure 1b. It should be noted that the network node in the transmission network 103 that is communicatively connected to the data source end 102 may be one or more, preferably a network node that is close to the data source end 102 in distance, but is not limited thereto. Among them, the audio and video data stream can be transmitted between the network nodes in the transmission network 103 according to the playback request of the playback end 101 until it is transmitted to the playback end 101. Optionally, the network node that receives the audio and video data stream can cache a copy locally, or of course it can not cache, which depends on the transmission mechanism of the transmission network. Among them, in order to distinguish different audio and video data streams, each audio and video data stream has a unique stream identifier, such as the Uniform Resource Locator (URL) of the audio and video data stream, or a stream identifier generated based on a URL address, etc., such as a hyperlink. For the playback end 101, the stream identifier can be used to indicate the audio and video data stream that you want to play.

[0052] In this embodiment, the playback terminal 101 can respond to the audio and video playback operation initiated by the user to send a signal to the network node (such as the network node) in the transmission network 103 that is connected to the transmission network 103. Figure 1b The network node L1 in the playback request sends a playback request, the playback request includes a target stream identifier, the target stream identifier is used to identify the audio and video data stream requested to be played by the playback terminal 101, optionally, the target stream identifier can be a URL address corresponding to the audio and video data stream, wherein one URL address uniquely corresponds to one audio and video data stream; taking the network node L1 as an example, the network node L1 can receive the playback request sent by the playback terminal 101, obtain the audio and video data stream corresponding to the target stream identifier according to the target stream identifier in the playback request, and return the audio and video data stream to the playback terminal 101, so that the playback terminal 101 can play the audio and video data stream. Specifically, if the network node L1 has locally cached the audio and video data stream corresponding to the target stream identifier, the locally cached audio and video data stream can be directly returned to the playback terminal 101; if the network node L1 does not locally cache the audio and video data stream corresponding to the target stream identifier, the audio and video data stream corresponding to the target stream identifier can be obtained from other network nodes in the transmission network 103, and the obtained audio and video data stream is returned to the playback terminal 101.

[0053] During the entire push-pull stream process, that is, during the audio and video playback process of the playback end 101, the playback end 101 may fail to play, play abnormally, or play delayed due to various reasons. The reasons for the playback failure, abnormality, or delay may be due to the playback end 101 itself, or it may be due to a network node on the transmission link. In order to solve the problem quickly and accurately, the log data generated by the audio and video data stream on the transmission link can be queried to track the cause of the problem. In this embodiment, considering that in the audio and video application scenario using the push-pull stream method, the data source end 102 and the playback end 101 are usually one-to-many, that is, the audio and video data stream pushed by the same data source end 102 may be requested to be played by multiple playback ends 102. For example, in the audio and video live broadcast scenario, there are usually multiple users watching the live broadcast content of the same anchor at the same time, and the terminals of multiple users all need to pull the live broadcast content and play it. In this scenario, the live broadcast end can be implemented as the data source end 102, and the user's terminal can be implemented as the playback end 101. For another example, in a video conference, three or more people may participate in the conference at the same time. When one person speaks, the other participants need to pull the speaker's audio and video data stream for playback. In this scenario, the speaker's end can be implemented as the data source end 102, and the other participants' ends can be implemented as the playback end 101. In these scenarios, the audio and video data stream will generate a lot of log data. Obviously, if the problem analysis and location is based on the granularity of distinguishing the log data only by the stream identifier of the audio and video data stream, it is necessary to query a large amount of log data, which is time-consuming and inefficient.

[0054] In view of the above problems, in this embodiment, the audio and video data stream is distinguished and marked from the perspective of the playback end 101, so that the mark corresponds to the audio and video data stream and is reflected in the entire transmission link of the audio and video data stream, so that the mark will be recorded in the log data of the audio and video data stream. Of course, related action behaviors can also be recorded in the log data, so that the log data corresponding to different playback ends 101 of the same audio and video data stream can be distinguished through the mark, and then for a specific playback end 101, the log data corresponding to the playback end 101 can be used to analyze and locate the cause of the problem, which can reduce the log data required for analysis and help improve the efficiency of problem analysis and location.

[0055] Specifically, after the network node L1 receives the playback request sent by the playback terminal 101, in addition to providing the audio and video data stream to the playback terminal 101, a tracking ID can also be established for the playback terminal 101. The tracking ID can uniquely point to the playback terminal 101 that initiated the playback request. That is, the corresponding tracking IDs for different playback terminals 101 are different, such as Figure 1aAs shown, the tracking ID corresponding to the playback terminal A1 is tracking ID B1; the tracking ID corresponding to the playback terminal A2 is tracking ID B2; and the tracking ID corresponding to the playback terminal A3 is tracking ID B3. In order to distinguish it from other subsequent tracking IDs, the tracking ID that uniquely points to the playback terminal 101 is recorded as the first tracking ID. Different playback terminals 101 corresponding to the same audio and video data stream have different corresponding first tracking IDs. The first tracking ID can be the identification information of the playback terminal 101, such as the IP address, MAC address or name of the playback terminal 101; the first tracking ID can also be a unique string generated by the network node L1 for the playback terminal 101, and the string can be composed of at least one of letters, numbers or symbols, such as "Bh11*" or "h#m123".

[0056] After the network node L1 establishes the first tracking ID for the playback terminal 101 that sends the playback request, the corresponding relationship between the first tracking ID and the audio and video data stream corresponding to the target stream identifier carried in the playback request can be recorded. Specifically, the corresponding relationship between the first tracking ID and the target stream identifier (such as URL) can be recorded, so that the first tracking ID can be used to distinguish and mark the relevant information of the audio and video data stream for different playback terminals 101. For example, the network node L1 can record the corresponding relationship between the first tracking ID and the audio and video data stream in the log data generated by the audio and video data stream on the network node L1. In this way, when a playback abnormality occurs on the playback terminal 101, the log data corresponding to the first tracking ID can be obtained from the massive log data generated by the audio and video data stream based on the first tracking ID of the playback terminal 101, so that based on the local log data corresponding to the first tracking ID, the abnormality problem on the playback terminal can be accurately located, thereby quickly solving the playback abnormality problem.

[0057] In this embodiment, the network node L1 may or may not have the audio and video data stream requested by the playback terminal 101 locally. In these two cases, the transmission paths that the audio and video data streams travel from the transmission network 103 to the playback terminal 101 will be different. If the network node L1 has the audio and video data stream requested by the playback terminal 101 locally, the audio and video data stream can be directly returned to the playback terminal 101. At this time, the transmission path from the audio and video data stream to the playback terminal 101 only passes through the network node L1, and the network node L1 only needs to record the corresponding relationship between the first tracking ID and the audio and video data stream locally. On the contrary, if the network node L1 does not have the audio and video data stream requested by the playback terminal 101 locally, the network node L1 needs to plan the target path required for the playback terminal 101 to obtain the audio and video data stream, and the target path refers to a path from the network node L1 to a certain network node connected to the data source terminal 102; wherein, a certain network node connected to the data source terminal 102 has already stored the audio and video data stream pushed by the data source terminal 102 locally, or a certain network node connected to the data source terminal 102 can obtain the audio and video data stream from the data source terminal 102 according to the request of the previous node. Figure 1b As shown, the data source end 102 pushes the audio and video data stream to the network node L4, and the playback end 101 sends a playback request to the network node L1, and the playback request is used to request the audio and video data stream pushed by the data source end 102. At this time, the audio and video data stream requested by the playback end 101 exists locally in the network node L4, but the audio and video data stream requested by the playback end 101 does not exist locally in the network node L1. In this case, the network node L1 can plan a target path for obtaining the audio and video data. For example, the planned target path is: network node L1—>network node L2—>network node L3—>network node L4. It should be noted that since the transmission network 103 may include multiple network nodes, these network nodes may cache a copy locally when transmitting the audio and video data stream. Therefore, the situation of network nodes with audio and video data streams in the transmission network in different time periods will also be different. Therefore, the target path planned by network node L1 is not limited to network node L1->network node L2->network node L3->network node L4. Regardless of the target path, the audio and video data stream transmission principle is the same. Therefore, this embodiment takes the path of network node L1->network node L2->network node L3->network node L4 as an example for explanation.

[0058] After planning the target path for the playback terminal 101, in order to track the transmission process of the audio and video data stream from the transmission network 103 to the playback terminal 101, the network node L1 can generate a second tracking ID, which is used to track the nodes of the audio and video data stream on the target path from the dimension of the playback terminal. The second tracking ID corresponds to the first tracking ID, which can not only point to a playback terminal 101, but also track the network nodes that the audio and video data stream passes through from the transmission network 103 to the playback terminal 101. In view of this, in the process of the network node L1 obtaining the audio and video data stream according to the target path, each network node with a next hop on the target path needs to provide the second tracking ID to its next hop network node until it reaches the last network node on the target path that can provide the audio and video data stream, such as the network node L4. In this way, each network node on the target path can record the correspondence between the second tracking ID and the audio and video data stream, and specifically can record the correspondence between the second tracking ID and the target stream identifier (such as URL). Therefore, when a playback abnormality occurs at the playback end 101, the transmission link of the audio and video data stream can be tracked for the specific playback end based on the second tracking ID, which can further reduce the log data required for analyzing the audio and video data stream, more accurately locate the playback abnormality problem, and improve the efficiency of solving the abnormal problem.

[0059] Specifically, when the network node L1 does not have the audio and video data stream requested by the playback terminal 101 locally, the target path for obtaining the audio and video data stream is planned to be network node L1->network node L2->network node L3->network node L4. Network node L1 generates a second tracking ID, and locally records the correspondence between the second tracking ID and the audio and video data stream, and specifically records the correspondence between the second tracking ID and the target stream identifier (such as URL). In this embodiment, the implementation method for generating the second tracking ID is not limited. For example, the first tracking ID can be directly used as the second tracking ID; or, some keyword information can be added to the first tracking ID as the second tracking ID. Optionally, the keyword information can be used as a prefix or suffix of the first tracking ID. Among them, for different playback terminals 101, the keyword information can be the same or different. For example, the keyword information can be generated by at least one of letters, numbers, or symbols, and the identification information of each network node on the target path can also be used as the keyword information.

[0060] Next, the network node L1 sends a first acquisition request to its next hop network node on the target path, that is, the network node L2, and the first acquisition request includes the second tracking ID and the target stream identifier. The network node L2 receives the first acquisition request sent by the network node L1, parses the second tracking ID and the target stream identifier from the first acquisition request, and records the corresponding relationship between the second tracking ID and the audio and video data stream, and specifically records the corresponding relationship between the second tracking ID and the target stream identifier (such as URL). On the other hand, the network node L2 can determine whether there is an audio and video data stream corresponding to the target stream identifier locally. If the audio and video data stream exists locally in the network node L2, the audio and video data stream is acquired and returned to the network node L1, so that the network node L1 can return the audio and video data stream to the playback terminal 101; if the audio and video data stream does not exist locally in the network node L2, the network node L2 can send a second acquisition request to its next hop network node on the target path, that is, the network node L3, and the second acquisition request includes the second tracking ID and the target stream identifier to request the audio and video data stream from the network node L3.

[0061] The network node L3 receives the second acquisition request, parses the second tracking ID and the target stream identifier from the second acquisition request, and on the one hand records the correspondence between the second tracking ID and the audio and video data stream, specifically, the correspondence between the second tracking ID and the target stream identifier (such as URL), and on the other hand determines whether the audio and video data stream corresponding to the target stream identifier exists locally; if the audio and video data stream exists locally on the network node L3, the network node L3 can obtain the audio and video data stream and send the audio and video data stream to the network node L2, so that the network node L2 returns the audio and video data stream to the playback terminal 101 via the network node L1; if the audio and video data stream does not exist locally on the network node L3, the network node L3 can send a third acquisition request to the next-hop network node on its target path, that is, the network node L4, and the third acquisition request includes the second tracking ID and the target stream identifier to request the audio and video data stream from the network node L4.

[0062] The network node L4 receives the third acquisition request, parses the second tracking ID and the target stream identifier from the third acquisition request, and on the one hand records the correspondence between the second tracking ID and the audio and video data stream, specifically, can record the correspondence between the second tracking ID and the target stream identifier (such as URL), and on the other hand determines whether the audio and video data stream exists locally on the network node L4. Because the data source end 102 pushes the audio and video data stream to the network node L4, the audio and video data stream exists on the network node L4. The network node L4 can provide the audio and video data stream to the playback end 101 via the network node L3, the network node L2 and the network node L1.

[0063] In an optional embodiment, regardless of whether the network node L1 locally has the audio and video data stream requested by the playback terminal 101, the network node L1 may return the first tracking ID corresponding to the playback terminal 101 to the playback terminal 101 in addition to returning the audio and video data stream to the playback terminal 101, so that the playback terminal 101 can record the corresponding relationship between the first tracking ID and the audio and video data stream. Further optionally, in the case where the network node L1 obtains the audio and video data stream through the above-mentioned target path, the network node L1 may return the second tracking ID to the playback terminal 101 in addition to returning the audio and video data stream and the first tracking ID to the playback terminal 101, so that the playback terminal 101 can record the corresponding relationship between the first tracking ID, the second tracking ID and the audio and video data stream, and provide a data basis for subsequent problem analysis based on the tracking ID.

[0064] From the above, it can be seen that both the first tracking ID and the second tracking ID correspond to the audio and video data stream, and can be reflected in the entire transmission path from the network node providing the audio and video data stream to the playback end 101, or the first tracking ID is reflected in the entire transmission path from the network node L1 to the playback end 101, or the second tracking ID can be reflected in the entire transmission path of the audio and video data stream from the network node L4 to the playback end 101. Of course, the relevant action behavior will also be recorded in the log data. Then, when problems such as playback failure, abnormality or delay occur during the playback process, as long as a specified first tracking ID or second tracking ID is provided, the log data on the entire path related to the playback end corresponding to the ID can be quickly found in the log data. This can accurately lock the required local log data, from which the relevant actions of the audio and video data stream corresponding to the playback end on the entire transmission path can be found, which lays a data foundation for our further analysis, and is also conducive to improving the efficiency of log analysis, facilitating the rapid discovery of the cause of the problem, and then facilitating the rapid resolution of the problem.

[0065] In an embodiment of the present application, the information related to the audio and video data stream (such as log data on different nodes) is distinguished and marked from the dimension of the playback end through the first tracking ID, or the first tracking ID and the second tracking ID. In addition, in some other selected embodiments of the present application, different stream segments in the audio and video data stream can also be distinguished and marked from the dimension of the data source end 102 through the third tracking ID. The third tracking ID can uniquely identify a stream segment in the audio and video data stream. In other words, for the same audio and video data stream, the third tracking ID corresponding to different stream segments is different. Specifically, after the data source end 102 pushes the audio and video data stream to the network node L4, the network node L4 can receive the audio and video data stream sent by the data source end 102, and divide the audio and video data stream into at least one stream segment according to the segmentation strategy. Among them, the segmentation strategy is not limited. For example, the segmentation strategy can be a strategy related to the push time of the audio and video service provider, then the audio and video data stream can be divided into at least one stream segment according to the push time of the audio and video service provider, and different stream segments correspond to different push times. For example, for the audio and video data stream of the same URL, the audio and video content pushed between 11:00 am and 11:30 am on the audio and video service provider can be used as a stream segment, the audio and video content pushed between 12:00 am and 1:30 pm can be used as a stream segment, and the audio and video content pushed between 6:00 pm and 10:00 pm can be used as a stream segment. For another example, the segmentation strategy can be a strategy related to the content object of the audio and video data stream, and the audio and video data stream can be segmented into at least one stream segment according to the content object in the audio and video data stream, and different stream segments correspond to different content objects. Among them, according to different audio and video application scenarios, the content objects are also different. For example, in a live shopping scenario, the content object can be a commodity, and the audio and video content of the same commodity in the audio and video data stream can be segmented into a stream segment according to the changes in the live commodity; for another example, in a film and television drama scenario, the content object can be a character in the film and television drama, and the audio and video content of the specified film and television drama character in the audio and video data stream can be segmented into a stream segment according to the film and television drama character.

[0066] In this embodiment, in order to facilitate the tracking of stream segments in the audio and video data stream, the network node L4 can generate a third tracking ID for each stream segment based on the stream segment as a dimension. The third tracking ID can uniquely identify the corresponding stream segment, and the third tracking ID can be reflected in the entire transmission path of the stream segment from the data source end 102 to the playback end 101. That is to say, on the transmission path from the data source end 102 to the playback end 101, each network node needs to record the correspondence between the third tracking ID and the corresponding stream segment in the audio and video data stream. In this way, using the third tracking ID, the log data of each stream segment in the audio and video data stream during the entire life cycle can be obtained. Further combined with the first tracking ID and the second tracking ID, the log data corresponding to the playback end can be further reduced. In this way, the log data required for analysis can be greatly reduced, abnormal problems can be located more accurately, and the efficiency of problem solving is improved.

[0067] Optionally, the third tracking ID can be generated based on the identification information of the data source end 102. For example, the third tracking ID can add keyword information to the identification information of the data source end 102, for example, add a prefix or suffix to the IP address or MAC address of the data source end 102, wherein the keyword information can be composed of at least one of letters, numbers or symbols, etc., and the prefix or suffix information is different for different stream fragments; of course, the third tracking ID can also be a string generated by a network node, and the string can be composed of at least one of letters, numbers or symbols, etc., for example, it can be "Cg99*" or "456!@ML", etc., and the corresponding strings are different for different stream fragments.

[0068] The following takes the example where the data source end 102 pushes the audio and video data stream to the network node L4 and the playback end 101 sends a playback request to the network node L1 to describe in detail the transmission process of the audio and video data stream.

[0069] like Figure 1bAs shown, after the data source end 102 collects audio and video data and encodes and generates an audio and video data stream, it sends the audio and video data stream to the network node L4 that is connected to it for communication. The network node L4 uses a segmentation strategy to segment the audio and video data stream to obtain at least one stream segment, generates a third tracking ID for at least one stream segment, and records the correspondence between the third tracking ID and the corresponding stream segment in the audio and video data stream; and upon receiving a request, the at least one stream segment and its corresponding third tracking ID can be sent to the network node that initiates the request. Further optionally, the network node L4 can also send the third tracking ID corresponding to each stream segment to the data source end 102, so that the data source end 102 can record the third tracking ID corresponding to each stream segment. Specifically, the correspondence between the third tracking ID and the stream segment is specifically: recording the correspondence between the target stream identifier (such as URL) corresponding to the audio and video data stream and each third tracking ID.

[0070] During this period, the playback terminal 101 can send a playback request to the network node L1, and the playback request includes the target stream identifier corresponding to the audio and video data stream. At this time, the network node L1 does not have the audio and video data stream corresponding to the target stream identifier locally, so in combination with the network topology of the transmission network 103, a target path for obtaining the audio and video data stream is planned, and the target path is network node L1->network node L2->network node L3->network node L4. On the other hand, the network node L1 generates a first tracking ID for the playback terminal 101, and the first tracking ID can uniquely identify a playback terminal 101 requesting the audio and video data stream; further, a second tracking ID is generated based on the first tracking ID, and the second tracking ID can uniquely identify the playback terminal 101, and can also be used to track each network node on the target path. Afterwards, the network node L1 sends a first acquisition request to its next-hop network node L2 on the target path, and the first acquisition request includes a second tracking ID and a target stream identifier. Network node L2 receives the first acquisition request, and on the one hand, locally records the correspondence between the second tracking ID and the target flow identifier, as well as the related actions; on the other hand, because the audio and video data stream does not exist locally, it sends a second acquisition request to its next-hop network node L3 on the target path, and the second acquisition request includes the second tracking ID and the target flow identifier. Network node L3 receives the second acquisition request, and on the one hand, locally records the correspondence between the second tracking ID and the target flow identifier, as well as the related actions; on the other hand, because the audio and video data stream does not exist locally, it sends a third acquisition request to its next-hop network node L4 on the target path, and the third acquisition request includes the second tracking ID and the target flow identifier.

[0071] The network node L4 receives the third acquisition request, and on the one hand, locally records the correspondence between the second tracking ID and the target stream identifier, as well as the related action behavior; on the other hand, provides at least one stream segment of the audio and video data stream and its corresponding third tracking ID to the network node L3. The network node L3 receives the at least one stream segment returned by the network node L4 and its corresponding third tracking ID, locally records the correspondence between the third tracking ID and at least one stream segment in the audio and video data stream, and sends the at least one stream segment and its corresponding third tracking ID to the network node L2. The network node L2 receives the at least one stream segment returned by the network node L3 and its corresponding third tracking ID, locally records the correspondence between the third tracking ID and at least one stream segment in the audio and video data stream, and sends the at least one stream segment and its corresponding third tracking ID to the network node L1. The network node L1 receives the at least one stream segment returned by the network node L2 and its corresponding third tracking ID, locally records the correspondence between the third tracking ID and at least one stream segment in the audio and video data stream, and sends the at least one stream segment to the playback terminal 101.

[0072] Furthermore, the network node L1 can also send the first tracking ID, the second tracking ID and the third tracking ID corresponding to at least one stream segment to the playback terminal 101, so that the playback terminal can record the correspondence between the first tracking ID, the second tracking ID and the third tracking ID corresponding to at least one stream segment and the target stream identifier (such as URL). It is explained here that after the above transmission process, the network nodes L1-L4 and the playback terminal 101 all record the correspondence between the second tracking ID and the third tracking ID and the target stream identifier (such as URL), which can be specifically recorded in the log data of the audio and video data stream on each network node. Of course, the log data also includes the time when each network node receives the audio and video data stream, the sending time, and some other processing actions on the audio and video data stream, thereby providing a data basis for obtaining log data for a specific playback terminal and a specific stream segment.

[0073] In some optional embodiments of the present application, Figure 1bAs shown, the system also includes a log database 104 for storing log data corresponding to each audio and video data stream. Specifically, each network node can output the log data generated by the audio and video data stream on the network node to the log database 104. The log data generated by the audio and video data stream on each network node includes: the correspondence between the first tracking ID, the second tracking ID, and the third tracking ID and the audio and video data stream, which can be specifically the correspondence between the first tracking ID, the second tracking ID, and the third tracking ID and the stream identifier (such as URL) of the audio and video data stream. In addition, the log data also records information such as the transmission delay, receiving and sending time of the audio and video data on each network node, and various actions of the network node on the audio and video data stream.

[0074] In some optional embodiments of the present application, Figure 1b As shown, each network node can also report the correspondence between the first tracking ID, the second tracking ID and the third tracking ID and the audio and video data stream to the server device 105, so that the server device 105 can obtain the first tracking ID, the second tracking ID and the third tracking ID corresponding to the audio and video data stream according to the correspondence, and can initiate a log query request for a specific playback end and / or a specific stream segment to the log database 104 according to at least one of the tracking IDs, and then perform problem analysis and location based on the queried log data.

[0075] In some other optional embodiments of the present application, Figure 1b As shown, the network node can also output the correspondence between the first tracking ID, the second tracking ID and the third tracking ID and the audio and video data stream to the maintenance personnel of the log database, specifically, the correspondence is output to the terminal device used by the maintenance personnel, so that the maintenance personnel can obtain the first tracking ID, the second tracking ID and the third tracking ID corresponding to the audio and video data stream according to the correspondence, and can initiate a log query request for a specific playback end and / or a specific stream segment to the log database 104 according to at least one of the tracking IDs, and then accurately and quickly analyze and locate the problem according to the queried log data, and promptly solve the abnormal problems occurring during the audio and video playback process.

[0076] It is hereby explained that in an embodiment of the present application, the audio and video service provider can feedback playback problems to the server device 105 or maintenance personnel, thereby triggering the server device 105 or maintenance personnel to initiate a log query request for a specific playback terminal and / or a specific stream segment to the log database 104 according to at least one tracking ID in the above-mentioned correspondence, and then accurately and quickly analyze and locate the problem based on the queried log data. In addition, the playback terminal 101 can also feedback playback problems to the server device 105. Specifically, the playback terminal 101 can send a problem feedback request to the server device 105 in response to a problem feedback operation triggered by a user, and the problem feedback request includes at least one tracking ID among the first tracking ID, the second tracking ID, and the third tracking ID. A problem feedback control may be set on the playback interface of the playback end 101. Once the audio and video data stream played by the playback end 101 is abnormal, the user may trigger the problem feedback control. The playback end 101 responds to the problem feedback operation triggered by the user, for example, the user may manually click to trigger or voice recognition to trigger, etc., obtain at least one of the first tracking ID, the second tracking ID and the third tracking ID corresponding to the audio and video data stream, carry at least one of the first tracking ID, the second tracking ID and the third tracking ID in the problem feedback request, and send the problem feedback request to the server device 105; the server device 105 may receive the problem feedback request, and according to at least one of the first tracking ID, the second tracking ID and the third tracking ID in the problem feedback request, obtain the log data of the audio and video data stream corresponding to at least one of the first tracking ID, the second tracking ID and the third tracking ID in the log database, analyze the log data, obtain the problem cause information, and return the problem cause information to the playback end 101; the playback end 101 receives the problem cause information and provides it to the user, for example, it may be displayed in the playback interface in the form of text, or the problem cause information may be broadcast in the form of voice.

[0077] In this embodiment, the audio and video data stream can be distinguished and marked from the perspective of the playback end, or from the perspective of the playback end and the data source end at the same time. First, the audio and video data stream is distinguished and marked from the perspective of the playback end, so that it is convenient to find the log data generated by the audio and video data stream on the transmission link for a specific playback end, which can reduce the log data required for analysis, so as to accurately and quickly analyze the cause of abnormal problems at the playback end. Further, the audio and video data stream is segmented from the perspective of the data source end, and the segmented stream segments are distinguished and marked, and the log data generated by tracking specific stream segments can be further targeted, which can further reduce the log data required for analysis, and can more accurately and quickly analyze playback abnormalities and other problems, thereby improving the efficiency of problem solving.

[0078] In an embodiment of the present application, in addition to being able to distinguish and mark the audio and video data streams from the playback end and the data source end, the link delay of the audio and video data stream during the transmission process can also be detected during the transmission of the audio and video data stream. In an embodiment of the present application, the delay between adjacent network nodes on the transmission path of the audio and video data stream can be detected first, and then the delay between adjacent network nodes is accumulated to finally obtain the delay on the entire transmission path, which is referred to as the link delay. Furthermore, in order to improve the accuracy of the link delay, when detecting the delay of the audio and video data stream between adjacent network nodes, the calculation is based on the local time of the same network node, which does not rely on the time synchronization between network nodes, is easy to implement, and has a high delay accuracy.

[0079] Below Figure 1b As an example of the system architecture shown in the figure, a link delay detection process is as follows Figure 1c As shown. After planning the target path for obtaining the audio and video data stream, the network node L1 can send a first delay detection request to the next hop network node on its target path, that is, the network node L2. The first delay detection request includes a first time, which is the local time when the network node L1 sends the first delay detection request; after receiving the first delay detection request, the network node L2 promptly returns a first delay detection response to the network node L1, and the first delay detection response includes the first time; the network node L1 receives the first delay detection response, and uses the local time when the first delay detection response is received as the second time, and determines the delay between the network node L1 and the network node L2 according to the second time and the first time, and specifically, half of the time difference between the second time and the first time can be used as the delay between the network node L1 and the network node L2.

[0080] Similarly, network node L2 can send a second delay detection request to its next hop node on the target path, namely network node L3, the second delay detection request including a third time, which is the local time when network node L2 sends the second delay detection request; after receiving the second delay detection request, network node L3 promptly returns a second delay detection response to network node L2, the second delay detection response including the third time; network node L2 receives the second delay detection response, and uses the local time when the second delay detection response is received as the fourth time, and determines the delay between network node L2 and its next hop network node L3 based on the third time and the fourth time, and specifically, half of the time difference between the fourth time and the third time can be used as the delay between network node L2 and network node L3.

[0081] Based on the above similar method, the network node L3 can also detect the delay between itself and the network node L4; and the network node L4 can also detect the delay between the expiration and the data source end 102. Figure 1c In FIG. 1 , the solid line represents the process of detecting the delay between adjacent network nodes. Afterwards, the delay between the network node L4 and the data source end 102, the delay between the network node L3 and the network node L4, the delay between the network node L2 and the network node L3, and the delay between the network node L1 and the network node L2 can be accumulated to obtain the link delay of the audio and video data stream on the entire transmission path. The process is as follows: Figure 1c Shown by the dashed line.

[0082] In this embodiment, when a network node detects the delay between it and the next-hop network node on the audio and video data stream transmission path, it uses the local time difference of the network node, does not rely on the local time of the next-hop network node, does not need to synchronize time with adjacent network nodes, is not affected by the accuracy of time synchronization, and can accurately count the delay between adjacent network nodes, thereby improving the accuracy of the detected delay of the entire link.

[0083] In this embodiment, the execution time of detecting the delay between adjacent network nodes is not limited. For example, in the process that network node L1 requests audio and video data stream from network node L4 via network node L2 and network node L3, each network node on the entire link can detect the delay between it and the next hop network node by sending a delay detection request to its next hop network node. For example, after receiving the play request sent by the playback terminal 101, network node L1 can send a first delay detection request to its next hop network node L2 under the triggering of the play request to detect the delay between it and network node L2; for network node L2, after receiving the first delay detection request, it can detect the delay between it and the next hop network node L3 under the triggering of the first delay detection request, and so on, until network node L4 detects the delay between it and the data source terminal 102. It should be noted that, considering that the network state and the state of each network node are dynamically changing, under the cooperation of network nodes on the transmission path, the link delay can be detected multiple times, for example, the link delay can be detected periodically.

[0084] In an optional embodiment of the present application, the data source end 102 transmits the audio and video data stream to the network node L4. The delay from the network node L4 to the data source end 102 can be considered to be 0, and the delay from the network node L1 to the data source end 102 can be considered to be the sum of the delays from the network node L1 to the network node L2, the network node L2 to the network node L3, and the network node L3 to the network node L4. In view of this, after the network node L1, the network node L2, and the network node 3 respectively detect the delay between them and the next hop network node, the link delay of obtaining the audio and video data stream from the network L1 to the data source end 102 is described in detail.

[0085] As the last hop on the target path, network node L4, after receiving the third acquisition request sent by network node L3, can perform the above-described related operations to provide audio and video data streams to network node L3. For the transmission process of audio and video data streams between network nodes, please refer to the above-mentioned embodiment, and the detection process of link delay is focused on here. On the other hand, network node L4 can determine that its delay to data source end 102 is 0, and send its delay to data source end 102 to network node L3. After network node L3 receives the delay from network node L4 to data source end 102, it determines the delay from network node L3 to data source end 102 according to the delay from network node L3 to next hop network node L4 and the delay from network node L4 to data source end 102. Specifically, the sum of the delay from network node L3 to next hop network node L4 and the delay from network node L4 to data source end 102 can be used as the delay from network node L3 to data source end 102, and network node L3 sends its delay to data source end 102 to network node L2. Network node L2 receives the delay from network node L3 to data source end 102, and determines the delay from network node L2 to data source end 102 based on the delay from network node L2 to the next-hop network node L3 and the delay from network node L3 to data source end 102. Specifically, the sum of the delay from network node L2 to the next-hop network node L3 and the delay from network node L3 to data source end 102 can be used as the delay from network node L2 to data source end 102, and then the delay to data source end 102 is sent to network node L1. Network node L1 receives the delay from network node L2 to data source end 102, and determines the delay from network node L1 to data source end 102 according to the delay from network node L1 to the next-hop network node L2 and the delay from network node L2 to data source end 102. Specifically, the sum of the delay from network node L1 to the next-hop network node L2 and the delay from network node L2 to data source end 102 can be used as the delay from network node L1 to data source end 102, that is, the link delay of the audio and video data stream on the entire target path.

[0086] In this embodiment, the operation of the network node L1 after obtaining the link delay of the audio and video data stream on the target path is not limited. In an optional embodiment, after the network node L1 obtains the link delay, it can output the link delay of the audio and video data stream to the playback terminal 101, and the playback terminal 101 receives the link delay of the audio and video data stream sent by the network node L1, and displays the link delay on the playback interface. In another optional embodiment, the network node L1 can output the link delay of the audio and video data stream to the server device 105 or the audio and video service provider, so that the server device 105 or the audio and video service provider can perform subsequent operations on the audio and video data stream based on the link delay. For example, if the link delay is too large, the audio and video data stream is tracked and located to improve the problem of excessive link delay. In another optional embodiment, the network node L1 recommends network value-added services or network improvement suggestions to the audio and video service provider based on the link delay, so that the audio and video service provider can improve the quality of network services. Among them, network value-added services refer to services that can help audio and video service providers improve the quality of network services, such as bandwidth purchasing services or VIP services. Bandwidth purchasing services or VIP services can provide audio and video service providers with higher quality network services to ensure network transmission quality, improve users' audio and video viewing experience, and increase user stickiness for audio and video service providers.

[0087] It should be noted that the above-mentioned link delay detection method can be applied to audio and video scenarios using push-pull streaming methods, combined with the push-pull streaming process of audio and video data streams, but is not limited to this. The above-mentioned link delay detection method can be applied to various network transmission scenarios.

[0088] In addition, in the above system embodiment, the implementation method and network structure of the transmission network are not limited, for example, it can be any network structure with network transmission function. In an optional embodiment, considering the large amount of data in the audio and video data stream, in order to reduce network congestion, improve the response time of the playback end, and meet the requirements for playback delay, the transmission network 103 can adopt a CDN network, and the above network nodes L1-L4 are specifically CDN nodes, which can reduce network congestion by virtue of the advantages of the CDN network, and also facilitate the playback end to obtain the audio and video data stream nearby, improve the timeliness of the response, reduce the playback delay, and meet the requirements of online live broadcast, video conferencing, and some short-delay RTC live broadcast scenarios.

[0089] The above audio and video system can be applied to live broadcast scenarios, video conferencing scenarios, short-delay RTC live broadcast scenarios, etc. The following takes the application of the audio and video system in live broadcast scenarios and video conferencing scenarios as examples for detailed description. Figure 2 and Figure 3 Shown are a live broadcast system and a video conferencing system.

[0090] Figure 2 The following is a schematic diagram of the architecture of a CDN-based live broadcast system provided by an exemplary embodiment of the present application. Figure 2 As shown, the system includes a playback terminal 201, an anchor terminal 202, and a CDN network 203, and the CDN network 203 includes at least one CDN node.

[0091] In this embodiment, the CDN network 203 is an intelligent virtual network built on the basis of the existing network. It relies on edge servers (i.e., CDN nodes) deployed in various places, which can enable users to obtain the required content nearby and improve the response speed of user access. In addition, in the CDN network 203, CDN nodes mostly adopt a multi-level cache structure, which can be a second level or a third level. Figure 2 The second-level cache structure is used as an example for illustration, but it is not limited to this. In the case where the CDN node adopts a second-level cache structure, the first-level CDN node is an edge node, and the second-level CDN node is a central node. The user request first reaches the edge node. If the edge node does not cache the content required by the user, it will request the corresponding content from its upper-level CDN node, that is, the central node, until the origin server (Origin Server), and return it to the user, thereby improving the user access success rate. Figure 2 In the figure, CDN network 203 includes CDN nodes L1a, L2a, L1b and L2b, but the present invention is not limited thereto. CDN nodes L1a and L1b represent first-level CDN nodes, and CDN nodes L2a and L2b represent second-level CDN nodes.

[0092] In this embodiment, for the live stream of the same URL, on the one hand, from the perspective of the playback end 201, a tracking ID for different playback ends 201 is generated for the live stream under the URL, which is recorded as url_traceid, which can correspond to the first tracking ID in the above embodiment; on the other hand, from the perspective of the anchor end 202, it may be necessary to segment the live stream under the URL to obtain different stream segments, and generate different tracking IDs for different stream segments, which are recorded as stream_id. It can correspond to the third tracking ID in the above embodiment, which reduces the log data required for analysis, and can analyze playback anomalies and other problems more accurately and quickly, thereby improving the efficiency of problem solving. The following is a detailed description of the live stream transmission process combining the playback end 201 and the anchor end 202.

[0093] The anchor terminal 202 pushes the live video to the CDN network 203. The CDN node L1b in the CDN network 203 receives the live video and divides the live stream into at least one stream segment according to the push time. A third tracking ID is generated for each of the at least one stream segment, and the third tracking ID is stream_id.

[0094] If a user wants to watch the live video pushed by the anchor terminal 202, he can initiate the viewing through the playback terminal 201. The playback terminal 201 responds to the live playback operation initiated by the user and sends a playback request to the CDN network 203. The playback request includes: the URL of the live stream; the CDN node L1a in the CDN network 203 receives the playback request, generates a first tracking ID for the playback terminal 201, namely url_traceid, and records the correspondence between url_traceid and the URL of the live stream. The CDN node L1a determines that the live stream does not exist locally, so the CDN node L1a plans a return path for obtaining the live stream. The return path is CDN node L1a->CDN node L2a->CDN node L2b->CDN node L1b. Next, CDN node L1a generates a second tracking ID, namely relay_traceid, based on url_traceid. relay_traceid can uniquely identify the playback end and can also be used to track each CDN node on the back-to-source path, that is, each CDN node on the back-to-source path must record the correspondence between relay_traceid and the URL of the live stream in the log data of the live stream; CDN node L1a sends a first acquisition request to CDN node L2a, and the first acquisition request includes relay_traceid. CDN node L2a receives the first acquisition request, records the correspondence between relay_traceid and the URL of the live stream, and determines that the live stream does not exist locally. CDN node L2a sends a second acquisition request to CDN node L2b, and the second acquisition request includes relay_traceid. CDN node L2b receives the second acquisition request, records the corresponding relationship between relay_traceid and the URL of the live stream, and determines that the live stream does not exist locally. CDN node L2b sends a third acquisition request to CDN node L1b, and the third acquisition request includes relay_traceid; CDN node L1b receives the third acquisition request, records the corresponding relationship between relay_traceid and the URL of the live stream, and determines that the live stream exists locally, and provides at least one stream segment in the live stream and its corresponding stream_id to CDN node L2b. CDN node L2b receives the at least one stream segment and its corresponding stream_id, records the corresponding relationship between the at least one stream segment and its corresponding stream_id, and sends the at least one stream segment and its corresponding stream_id to CDN node L2a. CDN node L2a receives the at least one stream segment and its corresponding stream_id, records the corresponding relationship between the at least one stream segment and its corresponding stream_id, and sends the at least one stream segment and its corresponding stream_id to CDN node L1a.The CDN node L1a receives the at least one stream segment and its corresponding stream_id, records the corresponding relationship between the at least one stream segment and its corresponding stream_id, and sends the at least one stream segment to the playback terminal 201. So far, the corresponding relationship between the URL, stream_id and relay_traceid of the live stream is recorded on the CDN nodes L1a, L2a, L1b and L2b, that is, the stream_id and relay_traceid are reflected in the entire transmission path of the live stream corresponding to the specific playback terminal, which is convenient for tracking the live stream according to the two ids.

[0095] In this embodiment, CDN node L1a provides url_traceid, relay_traceid and stream_id to playback terminal 201, and playback terminal 201 records the correspondence between url_traceid and the live stream, the correspondence between relay_traceid and the live stream, and the correspondence between stream_id and the live stream. In addition, each CDN node can output the log data generated by the live stream on the CDN node to the log database 204, and the log data generated on each CDN node includes: the correspondence between url_traceid, relay_traceid and stream_id and the URL of the live stream. In addition, the log data also records the transmission delay, receiving and sending time of the live stream on each CDN node, and various actions of the CDN node on the live stream. CDN node L1a can also output the correspondence between url_traceid, relay_traceid and stream_id and the live stream to the maintenance personnel of the log database, so that the maintenance personnel can accurately locate and track the live stream with problems when abnormal problems are found, and solve the abnormal problems in time.

[0096] In this embodiment, stream_id can be used to obtain all log information in the entire life cycle of the live stream segment, and then combined with url_traceid and relay_traceid, the log data of the live stream corresponding to the playback end can be further reduced. In this way, the log data required for analyzing the live stream can be greatly reduced, abnormal problems can be located more accurately, and the efficiency of solving problems is improved.

[0097] In this embodiment, after planning the return path for obtaining the live stream, CDN node L1a can send a first delay detection request to CDN node L2a, and the first delay detection request includes a first time T1, which is the local time when CDN node L1a sends the first delay detection request; CDN node L2a receives the first delay detection request and returns a first delay detection response to CDN node L1a, and the first delay detection response includes the first time T1; CDN node L1a receives the first delay detection response, determines the local time when the first delay detection response is received, recorded as the second time T2, and calculates (T1+T2) / 2 to obtain the delay T12 between CDN node L1a and CDN node L2a. Based on the same method, CDN node L2a can calculate the delay T22 between it and CDN node L2b, and CDN node L2b can calculate the delay T21 between it and CDN node L1b.

[0098] In this embodiment, when a CDN node counts the delay between itself and the next-hop CDN node on its transmission path, what is counted is the local time difference of the CDN node. For the statistics of link delay, the local time of other CDN nodes is not used, and there is no need to synchronize the system time between multiple CDN nodes. Therefore, the link delay between two CDN nodes can be accurately counted, thereby improving the accuracy of link delay statistics.

[0099] In this embodiment, CDN node L1a can gradually determine the delay from CDN node L1a to anchor terminal 202 based on the delay between CDN nodes on the back-to-source path. When CDN node L1a sends a live stream acquisition request to CDN node L1b via CDN node L2a and CDN node L2b, CDN node L1b can also return the delay 0 from CDN node L1b to anchor terminal 202 to CDN node L2b while returning the live stream. CDN node L2b adds the delay 0 from CDN node L1b to anchor terminal 202 and the delay T21 from CDN node L2b to CDN node L1b to obtain the delay from CDN node L2b to anchor terminal 202, which is T21. CDN node L1a sends a live stream acquisition request to CDN node L1b via CDN node L2a and CDN node L2b. CDN node L1b sends a live stream acquisition request to CDN node L1b via CDN node L2a and CDN node L2b. CDN node L1b sends a live stream acquisition request to CDN node L1b via CDN node L2a and CDN node L2b. CDN node L1b sends a live stream acquisition request to CDN node L1b via CDN node L2a and CDN node L2b. Node L2b sends the delay T21 from CDN node L2b to live broadcast end 202 to CDN node L2a; CDN node L2a receives the delay T21, adds T21 to the delay T22 from CDN node L2a to CDN node L2b, and obtains the delay from CDN node L2a to live broadcast end 202, which is T21+T22. CDN node L2a sends the delay T21+T22 from CDN node L2a to live broadcast end 202 to CDN node L1a; CDN node L1a receives T21+T22, adds T21+T22 to the delay T12 from CDN node L1a to CDN node L2a, and obtains the link delay of the return path, which is T21+T22+T12.

[0100] In this embodiment, after CDN node L1a obtains the link delay, it delays the link to playback terminal 201, playback terminal 201 receives the link delay of the live stream sent by CDN node L1a, and displays the link delay on the playback interface. Further, if the link delay is greater than the set delay threshold, transitional content related to the live content to be played in the live stream is displayed to wait for the live content to be played, wherein the transitional content may be content cached in advance to playback terminal 201, for example, it may be an advertisement, or a preview of the live broadcast, etc., which is not limited to this.

[0101] Figure 3 A CDN-based video conferencing system is provided for an exemplary embodiment of the present application, such as Figure 3 As shown, the system includes: a plurality of conference terminals 301 and a CDN network 302, wherein the CDN network 302 includes at least one CDN node. For the content of the CDN network, please refer to the above embodiment, which will not be described here.

[0102] In this embodiment, after each conference terminal 301 joins the video conference, there will be a current speaker and non-speakers in the conference. The conference terminal 301 of the current speaker can collect the conference video stream in the environment where the current speaker is located and push it to the CDN network 302. The conference terminal 301 of the current non-speaker can pull the conference video stream pushed by the current speaker from the CDN network 302 to obtain information such as the content of the current speaker's speech, thereby realizing a remote video conference with multiple participants. Figure 3 In the figure, the conference terminal 301 is illustrated as three conference terminals, but it is not limited to this. The three conference terminals are conference terminal 301a, conference terminal 301b and conference terminal 301c. Conference terminal 301a corresponds to CDN node L1a, conference terminal 301b corresponds to CDN node L1b, and conference terminal 301c corresponds to CDN node L1c. The following takes the example of conference terminal 301b pushing conference video stream to CDN node L1b and conference terminal 301a pulling conference video stream from CDN node L1a to explain the entire video conference process. The process of conference terminal 301c pulling conference video stream from CDN node L1c is similar to the process of conference terminal 301a pulling conference video stream from CDN node L1a, which will not be repeated here.

[0103] In this embodiment, the conference terminal 301b pushes the conference video stream to the CDN network 203, and the CDN node L1b in the CDN network 203 receives the conference video stream and divides the conference video stream into at least one stream segment according to the push time; a third tracking ID is generated for at least one stream segment, and the third tracking ID is stream_id.

[0104] Conference terminal 301a hopes to obtain the conference video stream of conference terminal 301b. Conference terminal 301a responds to the conference joining operation initiated by the user and sends a conference request to CDN network 302. The conference request includes: the URL of the conference video stream; CDN node L1a in CDN network 302 receives the conference request, generates a first tracking ID for conference terminal 301a, namely url_traceid, and records the corresponding relationship between url_traceid and the conference video stream URL. CDN node L1a determines that the conference video stream does not exist locally, so CDN node L1a plans a target path for obtaining the conference video stream. The target path is CDN node L1a->CDN node L1a. Point L2a->CDN node L2b->CDN node L1b, then CDN node L1a generates a second tracking ID, namely relay_traceid, according to the first tracking ID, CDN node L1a sends a first acquisition request to CDN node L2a, and the first acquisition request includes relay_traceid; CDN node L2a receives the first acquisition request, records the corresponding relationship between relay_traceid and the conference video stream URL, and determines that the conference video stream does not exist locally, CDN node L2a sends a second acquisition request to CDN node L2b, and the second acquisition request includes relay_traceid; CDN node L2b receives the first acquisition request, records the corresponding relationship between relay_traceid and the conference video stream URL, and determines that the conference video stream does not exist locally, CDN node L2a sends a second acquisition request to CDN node L2b, and the second acquisition request includes relay_traceid; The CDN node L2b receives the second acquisition request, records the corresponding relationship between relay_traceid and the conference video stream URL, and determines that the conference video stream does not exist locally. The CDN node L2b sends a third acquisition request to the CDN node L1b, and the third acquisition request includes relay_traceid; the CDN node L1b receives the third acquisition request, records the corresponding relationship between relay_traceid and the conference video stream URL, and determines that the conference video stream exists locally, and provides at least one stream segment in the conference video stream and its corresponding stream_id to the CDN node L2b; the CDN node L2b receives the at least one stream segment and its corresponding stream_id, records Record the correspondence between at least one stream segment and its corresponding stream_id, and send at least one stream segment and its corresponding stream_id to CDN node L2a; CDN node L2a receives the at least one stream segment and its corresponding stream_id, records the correspondence between at least one stream segment and its corresponding stream_id, and sends at least one stream segment and its corresponding stream_id to CDN node L1a; CDN node L1a receives the at least one stream segment and its corresponding stream_id, records the correspondence between at least one stream segment and its corresponding stream_id, and sends at least one stream segment to conference terminal 301a.

[0105] In this embodiment, CDN node L1a provides url_traceid, relay_traceid and stream_id to conference terminal 301a, and conference terminal 301a records the correspondence between url_traceid and the conference video stream, the correspondence between relay_traceid and the conference video stream, and the correspondence between stream_id and the conference video stream.

[0106] In this embodiment, stream_id can be used to obtain all log information in the entire life cycle of the conference video stream segment, and then combined with url_traceid and relay_traceid, the log data of the conference video stream corresponding to the playback end can be further reduced. In this way, the log data required for analyzing the conference video stream can be greatly reduced, abnormal problems can be located more accurately, and the efficiency of problem solving is improved.

[0107] In this embodiment, after planning the target path for obtaining the conference video stream, CDN node L1a can send a first delay detection request to CDN node L2a, and the first delay detection request includes a first time T1, which is the local time when CDN node L1a sends the first delay detection request; CDN node L2a receives the first delay detection request and returns a first delay detection response to CDN node L1a, and the first delay detection response includes the first time T1; CDN node L1a receives the first delay detection response, determines the local time when the first delay detection response is received, recorded as the second time T2, and calculates (T1+T2) / 2 to obtain the delay T12 between CDN node L1a and CDN node L2a. Based on the same method, CDN node L2a can calculate the delay T22 between it and CDN node L2b, and CDN node L2b can calculate the delay T21 between it and CDN node L1b.

[0108] In this embodiment, when a CDN node counts the delay between itself and the next-hop CDN node on its transmission path, what is counted is the local time difference of the CDN node. For the statistics of link delay, the local time of other CDN nodes is not used, and there is no need to synchronize the system time between multiple CDN nodes. Therefore, the link delay between two CDN nodes can be accurately counted, thereby improving the accuracy of link delay statistics.

[0109] In this embodiment, CDN node L1a can gradually determine the delay from CDN node L1a to conference terminal 301b based on the delay between CDN nodes on the target path. When CDN node L1a sends a conference video stream acquisition request to CDN node L1b via CDN node L2a and CDN node L2b, CDN node L1b can also return the delay 0 from CDN node L1b to conference terminal 301b to CDN node L2b while returning the conference video stream; CDN node L2b adds the delay 0 from CDN node L1b to conference terminal 301b and the delay T21 from CDN node L2b to CDN node L1b to obtain the delay from CDN node L2b to conference terminal 301b, which is T21. CDN node L2b sends the delay T21 from CDN node L2b to conference terminal 301b to CDN node L2a; CDN node L2a receives the delay T21, adds T21 to the delay T22 from CDN node L2a to CDN node L2b, and obtains the delay from CDN node L2a to conference terminal 301b, which is T21+T22. CDN node L2a sends the delay T21+T22 from CDN node L2a to conference terminal 301b to CDN node L1a; CDN node L1a receives T21+T22, adds T21+T22 to the delay T12 from CDN node L1a to CDN node L2a, and obtains the link delay of the target path, which is T21+T22+T12.

[0110] In this embodiment, after CDN node L1a obtains the link delay, it transmits the link delay to conference terminal 301a. Conference terminal 301a receives the link delay of the conference video stream sent by CDN node L1a and displays the link delay on the playback interface.

[0111] Figure 4a A flowchart of an audio and video transmission method provided for an exemplary embodiment of the present application is applicable to a network node, such as Figure 4a As shown, the method includes:

[0112] 401a. Receive a play request sent by a playback end, where the play request includes a target stream identifier, which is used to identify the audio and video data stream that the playback end requests to play;

[0113] 402a, generating a first tracking ID that can uniquely identify the playback end, and recording the corresponding relationship between the first tracking ID and the audio and video data stream;

[0114] 403a. Acquire the audio and video data stream from the data source end, and return the audio and video data stream to the playback end so that the playback end can play the audio and video data stream.

[0115] In an optional embodiment, the network node may also send the first tracking ID to the playback end, so that the playback end can record the corresponding relationship between the first tracking ID and the audio and video data stream.

[0116] In an optional embodiment, obtaining an audio and video data stream from a data source includes: if the audio and video data stream does not exist locally, planning a target path for obtaining the audio and video data stream, and generating a second tracking ID, the second tracking ID is used to track the nodes on the target path; sending an acquisition request to a next-hop network node of the network node on the target path, the acquisition request includes the second tracking ID, so that the next-hop network node records the correspondence between the second tracking ID and the audio and video data stream and returns the audio and video data stream; receiving the audio and video data stream returned by the next-hop network node; wherein the second tracking ID corresponds to the first tracking ID.

[0117] In an optional embodiment, generating the second tracking ID includes: using the first tracking ID directly as the second tracking ID; or adding keyword information to the first tracking ID as the second tracking ID.

[0118] In an optional embodiment, when the audio and video data stream includes at least one stream fragment, the method also includes: receiving a third tracking ID corresponding to each of the at least one stream fragments returned by the next-hop network node, where the third tracking ID can uniquely identify the stream fragment to which it corresponds; and recording the correspondence between the third tracking ID and at least one stream fragment in the audio and video data stream.

[0119] In an optional embodiment, the method provided in this embodiment also includes at least one of the following operations: sending the second tracking ID and the third tracking ID to the playback end, so that the playback end records the correspondence between the second tracking ID and the third tracking ID and the audio and video data stream; reporting the correspondence between the first tracking ID, the second tracking ID and the third tracking ID and the audio and video data stream to the server device; outputting the log data of the audio and video data stream on the network node to a log database, the log data including the correspondence between the first tracking ID, the second tracking ID and the third tracking ID and the audio and video data stream; outputting the correspondence between the first tracking ID, the second tracking ID and the third tracking ID and the audio and video data stream to the maintenance personnel of the log database.

[0120] In an optional embodiment, the method provided in this embodiment also includes: sending a delay detection request to a next-hop network node, the delay detection request includes a first time, and the first time is the local time when the network node sends the delay detection request; receiving a delay detection response returned by the next-hop network node, the delay detection response includes the first time; determining the delay between the network node and the next-hop network node based on the second time and the first time; the second time is the local time when the network node receives the delay detection response.

[0121] In an optional embodiment, the method provided in this embodiment also includes: receiving the delay from the next-hop network node to the data source; determining the link delay of the audio and video data stream based on the delay between the network node and the next-hop network node and the delay from the next-hop network node to the data source.

[0122] In an optional embodiment, the method provided in this embodiment also includes: outputting the link delay of the audio and video data stream to the playback end, the server device or the audio and video service provider; and / or recommending network value-added services or network improvement suggestions to the audio and video service provider based on the link delay, so that the audio and video service provider can improve the quality of network services.

[0123] In this embodiment, the audio and video transmission method is applicable to a variety of application scenarios, such as live broadcast scenarios, video conferencing scenarios, etc., wherein, in the above scenarios, the network node can be implemented as a CDN node in a CDN network. Based on this, this embodiment also provides a CDN-based live streaming transmission method, which is applicable to CDN nodes, such as Figure 4b As shown, the method includes:

[0124] 401b. Receive a playback request sent by a playback end, where the playback request includes a target stream identifier, which is used to identify the live stream that the playback end requests to play;

[0125] 402b, generating a first tracking ID that can uniquely identify the playback end, and recording the corresponding relationship between the first tracking ID and the live broadcast stream;

[0126] 403b. Obtain the live stream from the live broadcast end, and return the live stream to the playback end so that the playback end can play the live stream.

[0127] This embodiment also provides a CDN-based video conferencing method, which is applicable to CDN nodes, such as Figure 4c As shown, the method includes:

[0128] 401c. Receive a conference request sent by a conference terminal, where the conference request includes a conference identifier for identifying a conference video stream;

[0129] 402c, generating a first tracking ID that can uniquely identify the conference terminal, and recording the corresponding relationship between the first tracking ID and the conference video stream;

[0130] 403c. Acquire conference video streams from other conference terminals, and return the conference video streams to the conference terminal so that the conference terminal can play the conference video streams.

[0131] about Figure 4a-4c The detailed description and detailed implementation of each step in the illustrated embodiment can be found in the aforementioned system embodiment and will not be repeated here.

[0132] Figure 5a Another audio and video transmission method provided by the exemplary embodiment of the present application is applicable to a network node, such as Figure 5a As shown, the method includes:

[0133] 501a. Receive a first acquisition request, where the first acquisition request is sent by a previous-hop network node on a target path of the network node, and the first acquisition request includes a second tracking ID.

[0134] 502a, recording the correspondence between the second tracking ID and the audio and video data stream, where the second tracking ID is used to track nodes on a target path, where the target path is a path required to obtain the audio and video data stream;

[0135] 503a. Acquire the audio and video data stream, and return the audio and video data stream to the previous-hop network node, so that the previous-hop network node returns the audio and video data stream to the player requesting the audio and video data stream.

[0136] In an optional embodiment, obtaining the audio and video data stream includes: if the audio and video data stream does not exist locally, sending a second acquisition request to the next-hop network node on the target path of the network node, the second acquisition request including a second tracking ID, so that the next-hop network node can record the correspondence between the second tracking ID and the audio and video data stream and return the audio and video data stream; and receiving the audio and video data stream returned by the next-hop network node.

[0137] In an optional embodiment, when the audio and video data stream includes at least one stream segment, the method also includes: receiving a third tracking ID corresponding to each of the at least one stream segments returned by the next-hop network node, where the third tracking ID can uniquely identify the stream segment to which it corresponds; recording the correspondence between the third tracking ID and at least one stream segment in the audio and video data stream; and sending the third tracking ID corresponding to each of the at least one stream segment to the previous-hop network node, so that the previous-hop network node can record the correspondence between the third tracking ID and at least one stream segment.

[0138] In an optional embodiment, the method provided in this embodiment also includes: receiving a first delay detection request sent by a previous-hop network node, the first delay detection request includes a first time, and the first time is the local time when the previous-hop network node sends the first delay detection request; returning a first delay detection response to the previous-hop network node, the first delay detection response includes the first time, so that the previous-hop network node determines the delay between itself and the network node based on the first time and the second time; the second time is the local time when the previous-hop network node receives the first delay detection response.

[0139] In an optional embodiment, the method provided in this embodiment also includes: sending a second delay detection request to a next-hop network node, the second delay detection request includes a third time, and the third time is the local time when the network node sends the second delay detection request; receiving a second delay detection response returned by the next-hop network node, the second delay detection response includes the third time; determining the delay between the network node and the next-hop network node based on the third time and the fourth time; the fourth time is the local time when the network node receives the second delay detection response.

[0140] In an optional embodiment, the method provided in this embodiment also includes: receiving the delay from the next-hop network node to the data source end returned by the next-hop network node; determining the delay from the network node to the data source end based on the delay between the network node and the next-hop network node and the delay from the next-hop network node to the data source end; and sending the delay from the network node to the data source end to the previous-hop network node so that the previous-hop network node can determine the delay from the network node to the data source end.

[0141] Figure 5b A flowchart of another CDN-based live streaming transmission method provided for an exemplary embodiment of the present application is shown in FIG. Figure 5b As shown, the method includes:

[0142] 501b. Receive a first acquisition request, where the first acquisition request is sent by a previous-hop CDN node on the back-to-source path of the CDN node, and the first acquisition request includes a second tracking ID.

[0143] 502b. Record the correspondence between the second tracking ID and the live stream. The second tracking ID is used to track the CDN node on the back-to-source path. The back-to-source path is the path required to obtain the live stream.

[0144] 503b. Obtain the live stream from the live broadcast end, and return the live stream to the previous CDN node, so that the previous CDN node returns the live stream to the playback end that requests the live stream.

[0145] Figure 5c A flowchart of another CDN-based video conferencing method provided for an exemplary embodiment of the present application is shown in FIG. Figure 5c As shown, the method includes:

[0146] 501c. Receive a first acquisition request, where the first acquisition request is sent by a previous-hop CDN node on the back-to-source path of the CDN node, and the first acquisition request includes a second tracking ID;

[0147] 502c, recording the correspondence between the second tracking ID and the conference video stream, where the second tracking ID is used to track the CDN node on the back-to-source path, where the back-to-source path is the path required to obtain the conference video stream;

[0148] 503c. Acquire conference video streams from other conference terminals, and return the conference video streams to the previous-hop CDN node, so that the previous-hop CDN node returns the conference video streams to the conference terminal that initiated the conference request.

[0149] about Figure 5a-5c The detailed description and detailed implementation of each step in the illustrated embodiment can be found in the aforementioned system embodiment and will not be repeated here.

[0150] Figure 6 A flowchart of another audio and video transmission method provided for an exemplary embodiment of the present application is applicable to a network node close to a data source, such as Figure 6 As shown, the method includes:

[0151] 601. Receive an audio and video data stream sent by a data source;

[0152] 602. According to the segmentation strategy, the audio and video data stream is segmented into at least one stream segment;

[0153] 603. Generate a third tracking ID for at least one stream segment respectively, where the third tracking ID can uniquely identify the stream segment corresponding to the third tracking ID.

[0154] 604. Send at least one stream segment and its corresponding third tracking ID to the network node requesting the audio and video data stream.

[0155] In an optional embodiment, the audio and video data stream is divided into at least one stream segment according to the segmentation strategy, including: according to the streaming time of the audio and video service provider, the audio and video data stream is divided into at least one stream segment, and different stream segments correspond to different streaming times; and / or according to the content object in the audio and video data stream, the audio and video data stream is divided into at least one stream segment, and different stream segments correspond to different content objects.

[0156] Figure 7a A flowchart of an audio and video playback method provided for an exemplary embodiment of the present application is applicable to a playback end, such as Figure 7a As shown, the method includes:

[0157] 701a. In response to the audio and video playback operation initiated by the user, a playback request is sent to the network node, where the playback request includes a target stream identifier, which is used to identify the audio and video data stream requested to be played by the user;

[0158] 702a, receiving the audio and video data stream and the first tracking ID returned by the network node, where the first tracking ID is generated by the network node and is used to uniquely identify the playback terminal;

[0159] 703a. Play the audio and video data stream, and record the corresponding relationship between the first tracking ID and the audio and video data stream.

[0160] In an optional embodiment, the method provided in this embodiment also includes: receiving a second tracking ID returned by the network node, and recording the correspondence between the second tracking ID and the audio and video data stream, the second tracking ID is used to track the nodes on the target path, and the target path is the path planned by the network node for obtaining the audio and video data stream; and / or in the case where the audio and video data stream includes at least one stream segment, receiving a third tracking ID corresponding to each of the at least one stream segment returned by the network node, and recording the correspondence between the third tracking ID and the at least one stream segment.

[0161] In an optional embodiment, the method provided in this embodiment also includes: in response to a problem feedback operation triggered by a user, sending a problem feedback request to a server device, the problem feedback request including at least one tracking ID among a first tracking ID, a second tracking ID and a third tracking ID; receiving problem cause information returned by the server device, and outputting the problem cause information, the problem cause information being obtained by the server device based on log data analysis of an audio and video data stream corresponding to at least one tracking ID obtained from a log database.

[0162] In an optional embodiment, the method provided in this embodiment further includes: receiving a link delay of an audio and video data stream sent by a network node, and displaying the link delay on a playback interface.

[0163] In an optional embodiment, the method provided in this embodiment also includes: if the link delay is greater than a set delay threshold, displaying transitional content related to the audio and video content to be played in the audio and video data stream to wait for the audio and video content to be played.

[0164] Figure 7b A flow chart of a CDN-based live broadcasting method provided for an exemplary embodiment of the present application is shown in FIG. Figure 7b As shown, the method includes:

[0165] 701b. In response to the live broadcast operation initiated by the user, a playback request is sent to the CDN node, where the playback request includes a target stream identifier, which is used to identify the live broadcast stream requested to be played by the user;

[0166] 702b, receiving the live stream and the first tracking ID returned by the CDN node, where the first tracking ID is generated by the CDN node and is used to uniquely identify the playback terminal;

[0167] 703b. Play the live stream and record the corresponding relationship between the first tracking ID and the live stream.

[0168] Figure 7c A flow chart of a CDN-based video conferencing method provided for an exemplary embodiment of the present application is shown in FIG. Figure 7c As shown, the method includes:

[0169] 701c. In response to the conference joining operation initiated by the user, a conference request is sent to the CDN node, where the conference request includes a conference identifier, which is used to identify the video conference requested by the user to attend;

[0170] 702c, receiving the conference video stream and the first tracking ID returned by the CDN node, where the first tracking ID is generated by the CDN node and is used to uniquely identify the conference terminal that sends the conference request;

[0171] 703c. Play the conference video stream, and record the corresponding relationship between the first tracking ID and the conference video stream.

[0172] about Figure 7a-7c The detailed description and detailed implementation of each step in the illustrated embodiment can be found in the aforementioned system embodiment and will not be repeated here.

[0173] Figure 8 The exemplary embodiment of the present application provides a flow chart of a network delay detection method, which is applicable to a network node, such as Figure 8 As shown, the method includes:

[0174] 801. Receive a play request sent by a player, where the play request is used to request to play an audio or video data stream;

[0175] 802. Send a delay detection request to a next-hop network node that provides an audio and video data stream, where the delay detection request includes a first time, which is a local time when the network node sends the delay detection request;

[0176] 803. Receive a delayed detection response returned by a next-hop network node, where the delayed detection response includes a first time;

[0177] 804. Determine a delay between the network node and a next-hop network node according to a second time and the first time; the second time is a local time when the network node receives a delay detection response.

[0178] In an optional embodiment, the method provided in this embodiment also includes: receiving the delay from the next-hop network node to the data source; determining the link delay of the audio and video data stream based on the delay between the network node and the next-hop network node and the delay from the next-hop network node to the data source.

[0179] In an optional embodiment, the method provided in this embodiment also includes: outputting the link delay of the audio and video data stream to the playback end, the server device or the audio and video service provider; and / or recommending network value-added services or network improvement suggestions to the audio and video service provider based on the link delay, so that the audio and video service provider can improve the quality of network services.

[0180] In an optional embodiment, the network node is a CDN node, and the audio and video data stream is a live stream or a conference video stream in a video conference.

[0181] In the embodiments of the present application, for various audio and video application scenarios using push-pull streaming, in the push-pull streaming process, the audio and video data streams are first distinguished and marked from the perspective of the playback end, so as to facilitate the search for the log data generated by the audio and video data streams on the transmission link for a specific playback end, which can reduce the log data required for analysis, thereby accurately and quickly analyzing the causes of abnormal problems at the playback end. Further, the audio and video data streams are segmented from the perspective of the data source end, and the segmented stream segments are distinguished and marked, and the log data generated by tracking specific stream segments can be further targeted, which can further reduce the log data required for analysis, and can more accurately and quickly analyze playback abnormalities and other problems, thereby improving the efficiency of problem solving.

[0182] In the above embodiment of the present application, various tracking IDs are generated during the transmission of audio and video data streams, which can cause relevant changes in the log data generated during the transmission of audio and video data streams, thereby facilitating the locking of local log data based on these tracking IDs and reducing the log data required for analysis. However, it should be noted that the scheme is not limited to the data form of audio and video, and can be extended to various data transmission processes. In view of this, the embodiment of the present application also provides a data transmission system, including: a data receiving end and a data source end, and a transmission network between a request end and a data source end; the transmission network includes at least one network node.

[0183] In this embodiment, the data source is used to generate data to be transmitted and is responsible for pushing the data to the transmission network so that the data is transmitted to the data receiving end via the transmission network. The data receiving end is responsible for pulling the required data from the transmission network and further processing the pulled data. It should be noted that, depending on the application scenario, the data source, the data generated by the data source, and the data receiving end and the further processing of the data receiving end after pulling the required data will be different. The following examples are provided:

[0184] For example, in a live broadcast scenario, the data source end is the live broadcast end, and the data it generates can be a live stream. The data receiving end is the playback end, which will play the live stream after pulling it, and can further save, edit, and process the live stream.

[0185] For example, in an audio and video conference scenario, the data source is the conference terminal of any party, and the data generated by it can be a conference video stream. The data receiving end is other conference terminals, which will play the conference video stream after pulling it, and can further save, recognize text, edit, and process the conference video stream.

[0186] For example, in a resource management scenario, the data source is the resource provider, and the data it generates can be static resources, such as pictures, HTML files, CSS files, JS files, library functions, software installation packages, open source codes, etc. The data receiving end is the resource demand end, and it will use the static resources after pulling them. For example, it can render the required web pages based on static resources such as pictures, HTML files, CSS files, JS files, etc., run library functions, or do secondary development based on open source codes.

[0187] In this embodiment, considering that the same data may be pulled from the transmission network by multiple data receiving ends, in order to facilitate distinction, in this embodiment, the data receiving end, the network node in the transmission network and the data source end cooperate with each other to implement a new data transmission method, which is described in detail below.

[0188] The data receiving end sends a data request to a network node in the transmission network, and the network node in the transmission network receives the data request sent by the receiving end, wherein the data request includes a data identifier for identifying the target data requested by the data receiving end. The target data can be any data that can be generated by the data source end, such as a picture, an HTML file, a CSS file, a JS file, a library function, a software installation package, an open source code, etc., or a live stream, a conference video stream, etc.

[0189] After receiving the data request, the network node generates a first tracking ID that can uniquely identify the data receiving end, and records the correspondence between the first tracking ID and the target data; the correspondence can reflect that the data receiving end corresponding to the first tracking ID has requested the target data.

[0190] Next, the network node obtains the target data from the data source and returns the target data to the data receiving end. Furthermore, the first tracking ID may be returned to the data receiving end so that the data receiving end can record the corresponding relationship between the first tracking ID and the target data.

[0191] In an optional embodiment, when acquiring target data, the above network node may first determine whether the target data exists locally; if the target data exists locally, the target data is directly acquired locally; if the target data does not exist locally, the target path required for acquiring the target data is planned, and a second tracking ID corresponding to the first tracking ID is generated, and the second tracking ID is used to track the network nodes on the target path; thereafter, an acquisition request is sent to the next-hop network node on the target path where it is located, and the acquisition request includes the second tracking ID, so that the next-hop network node can record the corresponding relationship between the second tracking ID and the target data and return the target data; and the target data returned by the next-hop network node is received. For other network nodes on the target path, if the target data does not exist locally, acquisition requests will continue to be sent to the next-hop network node on the target path until the target data is acquired.

[0192] In an optional embodiment, the target data can be divided into multiple data fragments at the data source end, and a third tracking ID that can uniquely identify the data fragment is generated for each data fragment. In view of this, when the data source end pushes the target data to the network node connected to it in the transmission network, it actually pushes each data fragment and its corresponding third tracking ID to the network node connected to it. In view of this, the above-mentioned process of receiving the target data returned by the next-hop network node is: receiving at least one data fragment returned by the next-hop network node and each corresponding third tracking ID, the third tracking ID can uniquely identify the data fragment to which it corresponds; and recording the correspondence between the third tracking ID and at least one data fragment in the target data. Among them, each node on the target path will record the correspondence between the third tracking ID and at least one data fragment in the target data.

[0193] Further optionally, the network node that receives the data request may also perform at least one of the following operations:

[0194] Sending the second tracking ID and the third tracking ID to the data receiving end, so that the data receiving end records the corresponding relationship between the second tracking ID and the third tracking ID and the target data;

[0195] Reporting the correspondence between the first tracking ID, the second tracking ID, the third tracking ID and the target data to the server device;

[0196] Outputting log data of the target data on the network node to a log database, wherein the log data includes a correspondence between the first tracking ID, the second tracking ID, and the third tracking ID and the target data;

[0197] The corresponding relationship between the first tracking ID, the second tracking ID, the third tracking ID and the target data is output to a maintainer of the log database.

[0198] In this embodiment, by generating various tracking IDs during the data transmission process, relevant changes in the log data generated during the data transmission process can be caused, thereby facilitating locking of local log data based on these tracking IDs, reducing the log data required for analysis, and facilitating more accurate and rapid analysis of transmission anomalies and other problems, thereby improving the efficiency of problem solving.

[0199] It should be noted that the execution subject of each step of the method provided in the above embodiment can be the same device, or the method can be executed by different devices. For example, the execution subject of steps 401a to 403a can be device A; for another example, the execution subject of steps 401a and 402a can be device A, and the execution subject of step 403a can be device B; and so on.

[0200] In addition, in some of the processes described in the above embodiments and the accompanying drawings, multiple operations that appear in a specific order are included, but it should be clearly understood that these operations may not be executed in the order in which they appear in this article or executed in parallel, and the sequence numbers of the operations, such as 401a, 402a, etc., are only used to distinguish between different operations, and the sequence numbers themselves do not represent any execution order. In addition, these processes may include more or fewer operations, and these operations may be executed in sequence or in parallel. It should be noted that the descriptions of "first", "second", etc. in this article are used to distinguish different messages, devices, modules, etc., do not represent the order of precedence, and do not limit the "first" and "second" to be different types.

[0201] Figure 9a A schematic diagram of the structure of a network node provided by an exemplary embodiment of the present application. Figure 9a As shown, the network node includes: a memory 94 and a processor 95 .

[0202] The memory 94 is used to store computer programs and can be configured to store various other data to support operations on the network node. Examples of such data include instructions for any application program or method operating on the network node.

[0203] The memory 94 may be implemented by any type of volatile or nonvolatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic disk or optical disk.

[0204] The processor 95 is coupled to the memory 94 and is used to execute the computer program in the memory 94, so as to: receive a playback request sent by the playback end, the playback request includes a target stream identifier, which is used to identify the audio and video data stream requested to be played by the playback end; generate a first tracking ID that can uniquely identify the playback end, and record the corresponding relationship between the first tracking ID and the audio and video data stream; obtain the audio and video data stream from the data source end, and return the audio and video data stream to the playback end so that the playback end can play the audio and video data stream.

[0205] In an optional embodiment, the processor 95 is further configured to send the first tracking ID to the playback end, so that the playback end can record the corresponding relationship between the first tracking ID and the audio and video data stream.

[0206] In an optional embodiment, when the processor 95 obtains the audio and video data stream from the data source, it is specifically used to: if the audio and video data stream does not exist locally, plan a target path for obtaining the audio and video data stream, and generate a second tracking ID, the second tracking ID is used to track the nodes on the target path; send an acquisition request to the next-hop network node of the network node on the target path, the acquisition request includes the second tracking ID, so that the next-hop network node can record the correspondence between the second tracking ID and the audio and video data stream and return the audio and video data stream; receive the audio and video data stream returned by the next-hop network node; wherein the second tracking ID corresponds to the first tracking ID.

[0207] In an optional embodiment, when generating the second tracking ID, the processor 95 is specifically configured to: use the first tracking ID directly as the second tracking ID; or add keyword information to the first tracking ID as the second tracking ID.

[0208] In an optional embodiment, when the audio and video data stream includes at least one stream segment, the processor 95 is further used to: receive a third tracking ID corresponding to each of the at least one stream segments returned by the next-hop network node, where the third tracking ID can uniquely identify the stream segment to which it corresponds; and record the correspondence between the third tracking ID and at least one stream segment in the audio and video data stream.

[0209] In an optional embodiment, the processor 95 is further used to perform at least one of the following operations: sending the second tracking ID and the third tracking ID to the playback end so that the playback end records the correspondence between the second tracking ID and the third tracking ID and the audio and video data stream; reporting the correspondence between the first tracking ID, the second tracking ID and the third tracking ID and the audio and video data stream to the server device; outputting the log data of the audio and video data stream on the network node to a log database, the log data including the correspondence between the first tracking ID, the second tracking ID and the third tracking ID and the audio and video data stream; outputting the correspondence between the first tracking ID, the second tracking ID and the third tracking ID and the audio and video data stream to the maintenance personnel of the log database.

[0210] In an optional embodiment, the processor 95 is also used to: send a delay detection request to a next-hop network node, the delay detection request includes a first time, and the first time is the local time when the network node sends the delay detection request; receive a delay detection response returned by the next-hop network node, the delay detection response includes the first time; determine the delay between the network node and the next-hop network node based on the second time and the first time; the second time is the local time when the network node receives the delay detection response.

[0211] In an optional embodiment, the processor 95 is also used to: receive the delay from the next-hop network node to the data source; and determine the link delay of the audio and video data stream based on the delay between the network node and the next-hop network node and the delay from the next-hop network node to the data source.

[0212] In an optional embodiment, the processor 95 is also used to: output the link delay of the audio and video data stream to the playback end, server device or audio and video service provider; and / or recommend network value-added services or network improvement suggestions to the audio and video service provider based on the link delay, so that the audio and video service provider can improve the quality of network services.

[0213] Further, if Figure 9a As shown, the network node also includes: a communication component 96a, a display 97a, a power component 98a, an audio component 99a and other components. Figure 9a Only some components are shown schematically, which does not mean that the network node only includes Figure 9a It should be noted that Figure 9a The components in the dotted box are optional components, not mandatory components, and the specific components depend on the product form of the network node.

[0214] In an optional embodiment, the network node of this embodiment can be applied to different networks, for example, it can be applied to a CDN network, and can be implemented as a CDN node. Further, when the network node of this embodiment is implemented as a CDN node, it can be applied to various push-pull streaming scenarios, such as live broadcast scenarios or video conferencing scenarios.

[0215] Furthermore, when the network node of the present embodiment is implemented as a CDN node and applied to a live broadcast scenario, its processor executes a computer program stored in a memory, and specifically can implement the following operations: receiving a playback request sent by a playback end, the playback request including a target stream identifier, which is used to identify the live broadcast stream that the playback end requests to play; generating a first tracking ID that can uniquely identify the playback end, and recording the corresponding relationship between the first tracking ID and the live broadcast stream; obtaining the live broadcast stream from the live broadcast end, and returning the live broadcast stream to the playback end so that the playback end can play the live broadcast stream.

[0216] Furthermore, when the network node of this embodiment is implemented as a CDN node and applied to a video conferencing scenario, its processor executes a computer program stored in the memory, and specifically can implement the following operations: receiving a conference request sent by a conference terminal, the conference request including a conference identifier for identifying a conference video stream; generating a first tracking ID that can uniquely identify the conference terminal, and recording the correspondence between the first tracking ID and the conference video stream; obtaining the conference video stream from other conference terminals, and returning the conference video stream to the conference terminal so that the conference terminal can play the conference video stream.

[0217] Furthermore, the network node of this embodiment can also be used in any data transmission scenario, and its processor executes the computer program stored in the memory, and specifically can implement the following operations: receiving a data request sent by a data receiving end, the data request including a data identifier for identifying the target data requested by the data receiving end; generating a first tracking ID that can uniquely identify the data receiving end, and recording the corresponding relationship between the first tracking ID and the target data; obtaining the target data from the data source end, and returning the target data to the data receiving end.

[0218] Accordingly, the embodiment of the present application further provides a computer-readable storage medium storing a computer program, which can achieve the above-mentioned Figure 4a The illustrated method embodiment includes steps that can be executed by a network node.

[0219] Accordingly, the embodiment of the present application also provides a computer program product, including a computer program / instruction, wherein the computer program / instruction can achieve the above-mentioned Figure 4aThe illustrated method embodiment includes steps that can be executed by a network node.

[0220] The embodiment of the present application also provides a network node, the implementation structure of the network node is Figure 9a The implementation structure of the network nodes shown is the same or similar, and can be referred to Figure 9a The network node provided in this embodiment is implemented as follows: Figure 9a The difference between the network nodes in the illustrated embodiments mainly lies in: the functions implemented by the processor executing the computer program stored in the memory are different. For the network node provided in this embodiment, its processor executes the computer program stored in the memory, which can be used to: receive a first acquisition request, the first acquisition request is sent by the previous hop network node on the target path of the network node, and the first acquisition request includes a second tracking ID; record the correspondence between the second tracking ID and the audio and video data stream, the second tracking ID is used to track the node on the target path, and the target path is the path required to obtain the audio and video data stream; obtain the audio and video data stream, and return the audio and video data stream to the previous hop network node that sent it, so that the previous hop network node returns the audio and video data stream to the playback end that requests the audio and video data stream.

[0221] In an optional embodiment, when the processor acquires the audio and video data stream, it is specifically used to: if the audio and video data stream does not exist locally, send a second acquisition request to the next-hop network node on the target path of the network node, the second acquisition request including a second tracking ID, so that the next-hop network node can record the correspondence between the second tracking ID and the audio and video data stream and return the audio and video data stream; and receive the audio and video data stream returned by the next-hop network node.

[0222] In an optional embodiment, when the audio and video data stream includes at least one stream segment, the processor is further used to: receive a third tracking ID corresponding to each of the at least one stream segments returned by a next-hop network node, where the third tracking ID can uniquely identify the stream segment to which it corresponds; record the correspondence between the third tracking ID and at least one stream segment in the audio and video data stream; and send the third tracking ID corresponding to each of the at least one stream segment to a previous-hop network node, so that the previous-hop network node can record the correspondence between the third tracking ID and at least one stream segment.

[0223] In an optional embodiment, the processor is also used to: receive a first delay detection request sent by a previous-hop network node, the first delay detection request includes a first time, and the first time is the local time when the previous-hop network node sends the first delay detection request; return a first delay detection response to the previous-hop network node, the first delay detection response includes the first time, so that the previous-hop network node determines the delay between itself and the network node based on the first time and the second time; the second time is the local time when the previous-hop network node receives the first delay detection response.

[0224] In an optional embodiment, the processor is also used to: send a second delay detection request to a next-hop network node, the second delay detection request includes a third time, and the third time is the local time when the network node sends the second delay detection request; receive a second delay detection response returned by the next-hop network node, the second delay detection response includes the third time; determine the delay between the network node and the next-hop network node based on the third time and the fourth time; the fourth time is the local time when the network node receives the second delay detection response.

[0225] In an optional embodiment, the processor is also used to: receive the delay from the next-hop network node to the data source end returned by the next-hop network node; determine the delay from the network node to the data source end based on the delay between the network node and the next-hop network node and the delay from the next-hop network node to the data source end; and send the delay from the network node to the data source end to the previous-hop network node so that the previous-hop network node can determine the delay from the network node to the data source end.

[0226] In an optional embodiment, the network node of this embodiment can be applied to different networks, for example, it can be applied to a CDN network, and can be implemented as a CDN node. Further, when the network node of this embodiment is implemented as a CDN node, it can be applied to various push-pull streaming scenarios, such as live broadcast scenarios or video conferencing scenarios.

[0227] Furthermore, when the network node of the present embodiment is implemented as a CDN node and applied to a live broadcast scenario, its processor executes a computer program stored in a memory, and specifically can implement the following operations: receiving a first acquisition request, the first acquisition request is sent by the previous-hop CDN node of the CDN node on the back-to-source path, and the first acquisition request includes a second tracking ID; recording the correspondence between the second tracking ID and the live broadcast stream, the second tracking ID is used to track the CDN node on the back-to-source path, and the back-to-source path is the path required to obtain the live broadcast stream; obtaining the live broadcast stream from the live broadcast end, and returning the live broadcast stream to the previous-hop CDN node that sent it, so that the previous-hop CDN node returns the live broadcast stream to the playback end that requests the live broadcast stream.

[0228] Furthermore, when the network node of the present embodiment is implemented as a CDN node and applied to a video conferencing scenario, its processor executes a computer program stored in a memory, and specifically implements the following operations: receiving a first acquisition request, the first acquisition request is sent by the previous-hop CDN node of the CDN node on the return-to-source path, and the first acquisition request includes a second tracking ID; recording the correspondence between the second tracking ID and the conference video stream, the second tracking ID is used to track the CDN node on the return-to-source path, and the return-to-source path is the path required to obtain the conference video stream; obtaining the conference video stream from other conference terminals, and returning the conference video stream to the previous-hop CDN node that sent it, so that the previous-hop CDN node can return the conference video stream to the conference terminal that initiated the conference request.

[0229] Accordingly, the embodiment of the present application further provides a computer-readable storage medium storing a computer program, which can achieve the above-mentioned Figure 5a The illustrated method embodiment includes steps that can be executed by a network node.

[0230] Accordingly, the embodiment of the present application also provides a computer program product, including a computer program / instruction, wherein the computer program / instruction can achieve the above-mentioned Figure 5a The illustrated method embodiment includes steps that can be executed by a network node.

[0231] The embodiment of the present application also provides a network node, the implementation structure of the network node is Figure 9a The implementation structure of the network nodes shown is the same or similar, and can be referred to Figure 9a The network node provided in this embodiment is implemented as follows: Figure 9a The difference between the network nodes in the illustrated embodiments mainly lies in: the functions implemented by the processor executing the computer program stored in the memory are different. For the network node provided in this embodiment, its processor executes the computer program stored in the memory, which can be used to: receive the audio and video data stream sent by the data source; divide the audio and video data stream into at least one stream segment according to the segmentation strategy; generate a third tracking ID for at least one stream segment, and the third tracking ID can uniquely identify the stream segment to which it corresponds; and send at least one stream segment and its corresponding third tracking ID to the network node requesting the audio and video data stream.

[0232] In an optional embodiment, when the processor divides the audio and video data stream into at least one stream segment according to the segmentation strategy, it is specifically used to: divide the audio and video data stream into at least one stream segment according to the streaming time of the audio and video service provider, and different stream segments correspond to different streaming times; and / or divide the audio and video data stream into at least one stream segment according to the content object in the audio and video data stream, and different stream segments correspond to different content objects.

[0233] Accordingly, the embodiment of the present application further provides a computer-readable storage medium storing a computer program, which can achieve the above-mentioned Figure 6 The illustrated method embodiment includes steps that can be executed by a network node.

[0234] Accordingly, the embodiment of the present application also provides a computer program product, including a computer program / instruction, wherein the computer program / instruction can achieve the above-mentioned Figure 6 The illustrated method embodiment includes steps that can be executed by a network node.

[0235] The embodiment of the present application also provides a network node, the implementation structure of the network node is similar to Figure 9a The implementation structure of the network nodes shown is the same or similar, and can be referred to Figure 9a The network node provided in this embodiment is implemented as follows: Figure 9a The difference between the network nodes in the illustrated embodiments mainly lies in: the functions implemented by the processor executing the computer program stored in the memory are different. For the network node provided in this embodiment, its processor executes the computer program stored in the memory, which can be used to: receive a play request sent by the playback end, the play request is used to request to play the audio and video data stream; send a delay detection request to the next hop network node that provides the audio and video data stream, the delay detection request includes a first time, the first time is the local time when the network node sends the delay detection request; receive a delay detection response returned by the next hop network node, the delay detection response includes the first time; determine the delay between the network node and the next hop network node according to the second time and the first time; the second time is the local time when the network node receives the delay detection response.

[0236] In an optional embodiment, the processor is also used to: receive the delay from the next-hop network node to the data source; and determine the link delay of the audio and video data stream based on the delay between the network node and the next-hop network node and the delay from the next-hop network node to the data source.

[0237] In an optional embodiment, the processor is also used to: output the link delay of the audio and video data stream to the playback end, server device or audio and video service provider; and / or recommend network value-added services or network improvement suggestions to the audio and video service provider based on the link delay, so that the audio and video service provider can improve the quality of network services.

[0238] In an optional embodiment, the network node is a CDN node, and the audio and video data stream is a live stream or a conference video stream in a video conference.

[0239] Figure 9b A schematic diagram of the structure of a playback terminal provided by an exemplary embodiment of the present application. Figure 9b As shown, the playback terminal includes: a memory 94 and a processor 95.

[0240] The memory 94 is used to store computer programs and can be configured to store various other data to support operations on the playback terminal. Examples of these data include instructions for any application program or method used to operate on the playback terminal.

[0241] The memory 94 may be implemented by any type of volatile or nonvolatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic disk or optical disk.

[0242] The processor 95 is coupled to the memory 94 and is used to execute the computer program in the memory 94, so as to: respond to the audio and video playback operation initiated by the user, send a playback request to the network node, the playback request includes a target stream identifier, which is used to identify the audio and video data stream requested to be played by the user; receive the audio and video data stream and the first tracking ID returned by the network node, the first tracking ID is generated by the network node and is used to uniquely identify the playback end; play the audio and video data stream, and record the corresponding relationship between the first tracking ID and the audio and video data stream.

[0243] In an optional embodiment, the processor is further used to: receive a second tracking ID returned by the network node, and record the correspondence between the second tracking ID and the audio and video data stream, the second tracking ID is used to track nodes on a target path, and the target path is a path planned by the network node for obtaining the audio and video data stream; and / or when the audio and video data stream includes at least one stream segment, receive a third tracking ID corresponding to each of the at least one stream segment returned by the network node, and record the correspondence between the third tracking ID and at least one stream segment.

[0244] In an optional embodiment, the processor is also used to: in response to a problem feedback operation triggered by a user, send a problem feedback request to a server device, wherein the problem feedback request includes at least one tracking ID among a first tracking ID, a second tracking ID, and a third tracking ID; receive problem cause information returned by the server device, and output the problem cause information, wherein the problem cause information is obtained by the server device based on log data analysis of an audio and video data stream corresponding to at least one tracking ID obtained from a log database.

[0245] In an optional embodiment, the processor is further used to: receive the link delay of the audio and video data stream sent by the network node, and display the link delay on the playback interface.

[0246] In an optional embodiment, the processor is further used to: if the link delay is greater than a set delay threshold, display transitional content related to the audio and video content to be played in the audio and video data stream to wait for the audio and video content to be played.

[0247] Further, if Figure 9b As shown, the playback terminal also includes: a communication component 96b, a display 97b, a power component 98b, an audio component 99b and other components. Figure 9b Only some components are shown schematically, which does not mean that the playback terminal only includes Figure 9b It should be noted that Figure 9b The components in the dotted box are optional components, not mandatory components, and the specific components depend on the product form of the playback terminal.

[0248] In an optional embodiment, the playback terminal of this embodiment can be applied to various push-pull stream scenarios, such as a live broadcast scenario or a video conferencing scenario.

[0249] Furthermore, when the playback terminal of this embodiment is applied to a live broadcast scenario, its processor executes a computer program stored in the memory, and specifically can implement the following operations: respond to a live broadcast operation initiated by a user, send a playback request to the CDN node, the playback request includes a target stream identifier, which is used to identify the live stream requested to be played by the user; receive the live stream and the first tracking ID returned by the CDN node, the first tracking ID is generated by the CDN node, and is used to uniquely identify the playback terminal; play the live stream, and record the correspondence between the first tracking ID and the live stream.

[0250] Furthermore, when the playback terminal of this embodiment is applied to a video conferencing scenario, its processor executes a computer program stored in the memory, and specifically can implement the following operations: respond to a user-initiated conference participation operation, send a conference request to the CDN node, and the conference request includes a conference identifier for identifying the video conference the user requests to attend; receive the conference video stream and the first tracking ID returned by the CDN node, and the first tracking ID is generated by the CDN node and is used to uniquely identify the conference terminal that sends the conference request; play the conference video stream, and record the correspondence between the first tracking ID and the conference video stream.

[0251] Accordingly, the embodiment of the present application further provides a computer-readable storage medium storing a computer program, which can achieve the above-mentioned Figure 7a The steps in the method embodiment shown may be executed by the playback terminal.

[0252] Accordingly, the embodiment of the present application also provides a computer program product, including a computer program / instruction, wherein the computer program / instruction can achieve the above-mentioned Figure 7a The illustrated method embodiment includes steps that can be executed by a network node.

[0253] Above Figure 9a and Figure 9b The communication component in is configured to facilitate wired or wireless communication between the device where the communication component is located and other devices. The device where the communication component is located can access a wireless network based on a communication standard, such as WiFi, 2G, 3G, 4G / LTE, 5G and other mobile communication networks, or a combination thereof. In an exemplary embodiment, the communication component receives a broadcast signal or broadcast-related information from an external broadcast management system via a broadcast channel. In an exemplary embodiment, the communication component also includes a near field communication (NFC) module to facilitate short-range communication. For example, the NFC module can be implemented based on radio frequency identification (RFID) technology, infrared data association (IrDA) technology, ultra-wideband (UWB) technology, Bluetooth (BT) technology and other technologies.

[0254] Above Figure 9a and Figure 9b The display in the embodiment includes a screen, which may include a liquid crystal display (LCD) and a touch panel (TP). If the screen includes a touch panel, the screen may be implemented as a touch screen to receive input signals from a user. The touch panel includes one or more touch sensors to sense touch, slide, and gestures on the touch panel. The touch sensor may not only sense the boundary of a touch or slide action, but also detect the duration and pressure associated with the touch or slide operation.

[0255] Above Figure 9a and Figure 9b The power supply component in the device provides power to various components of the device where the power supply component is located. The power supply component may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power to the device where the power supply component is located.

[0256] Above Figure 9a and Figure 9b The audio component in can be configured to output and / or input audio signals. For example, the audio component includes a microphone (MIC), and when the device where the audio component is located is in an operating mode, such as a call mode, a recording mode, and a speech recognition mode, the microphone is configured to receive an external audio signal. The received audio signal can be further stored in a memory or sent via a communication component. In some embodiments, the audio component also includes a speaker for outputting an audio signal.

[0257] Those skilled in the art will appreciate that the embodiments of the present application may be provided as methods, systems, or computer program products. Therefore, the present application may adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment in combination with software and hardware. Moreover, the present application may adopt the form of a computer program product implemented in one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) that include computer-usable program code.

[0258] The present application is described with reference to the flowchart and / or block diagram of the method, device (system) and computer program product according to the embodiment of the present application. It should be understood that each process and / or box in the flowchart and / or block diagram, and the combination of the process and / or box in the flowchart and / or block diagram can be realized by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device produce a device for realizing the function specified in one process or multiple processes in the flowchart and / or one box or multiple boxes in the block diagram.

[0259] These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing device to work in a specific manner, so that the instructions stored in the computer-readable memory produce a manufactured product including an instruction device that implements the functions specified in one or more processes in the flowchart and / or one or more boxes in the block diagram.

[0260] These computer program instructions may also be loaded onto a computer or other programmable data processing device so that a series of operational steps are executed on the computer or other programmable device to produce a computer-implemented process, whereby the instructions executed on the computer or other programmable device provide steps for implementing the functions specified in one or more processes in the flowchart and / or one or more boxes in the block diagram.

[0261] In a typical configuration, a computing device includes one or more processors (CPU), input / output interfaces, network interfaces, and memory.

[0262] The memory may include non-permanent storage in a computer-readable medium, random access memory (RAM) and / or non-volatile memory in the form of read-only memory (ROM) or flash RAM. The memory is an example of a computer-readable medium.

[0263] Computer readable media include permanent and non-permanent, removable and non-removable media that can be implemented by any method or technology to store information. Information can be computer readable instructions, data structures, program modules or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disk read-only memory (CD-ROM), digital versatile disk (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device. As defined herein, computer readable media does not include temporary computer readable media (transitory media), such as modulated data signals and carrier waves.

[0264] It should also be noted that the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, commodity or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, commodity or device. In the absence of more restrictions, the elements defined by the sentence "comprises a ..." do not exclude the existence of other identical elements in the process, method, commodity or device including the elements.

[0265] The above is only an embodiment of the present application and is not intended to limit the present application. For those skilled in the art, the present application may have various changes and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application should be included in the scope of the claims of the present application.

Claims

1. An audio and video transmission method, applicable to a network node, characterized in that: include: Receive a playback request sent by a playback end, wherein the playback request includes a target stream identifier for identifying an audio or video data stream requested to be played by the playback end; Generate a first tracking ID that can uniquely identify the playback end, and record the corresponding relationship between the first tracking ID and the audio and video data stream in the log data of the audio and video data stream, so that when a playback abnormality occurs on the playback end, the log data corresponding to the first tracking ID is obtained from the log data of the recorded audio and video data stream based on the first tracking ID to analyze the cause of the abnormality on the playback end; Acquire the audio and video data stream from the data source end, and return the audio and video data stream to the playback end so that the playback end can play the audio and video data stream; Wherein, obtaining the audio and video data stream from the data source includes: If the audio and video data stream does not exist locally, plan a target path for acquiring the audio and video data, and generate a second tracking ID, where the second tracking ID is used to track nodes on the target path; Sending an acquisition request to a next-hop network node of the network node on the target path, wherein the acquisition request includes the second tracking ID, so that the next-hop network node records the corresponding relationship between the second tracking ID and the audio and video data stream and returns the audio and video data stream; Receive the audio and video data stream returned by the next-hop network node; wherein the second tracking ID corresponds to the first tracking ID.

2. The method according to claim 1, characterized in that: Also includes: The first tracking ID is sent to the playback end so that the playback end records the corresponding relationship between the first tracking ID and the audio and video data stream.

3. The method according to claim 1, characterized in that Generate a secondary tracking ID, including: Use the first tracking ID directly as the second tracking ID; or Keyword information is added to the first tracking ID to serve as the second tracking ID.

4. The method according to claim 3, characterized in that In the case where the audio and video data stream includes at least one stream segment, the method further includes: receiving a third tracking ID corresponding to each of the at least one flow segment returned by the next-hop network node, where the third tracking ID can uniquely identify the flow segment corresponding thereto; The correspondence between the third tracking ID and at least one stream segment in the audio and video data stream is recorded.

5. The method according to claim 4, characterized in that Also includes at least one of the following operations: Sending the second tracking ID and the third tracking ID to the playback end, so that the playback end records the corresponding relationship between the second tracking ID and the third tracking ID and the audio and video data stream; Reporting the correspondence between the first tracking ID, the second tracking ID, the third tracking ID and the audio and video data stream to the server device; Outputting log data of the audio and video data stream on the network node to a log database, the log data including a correspondence between the first tracking ID, the second tracking ID, and the third tracking ID and the audio and video data stream; The corresponding relationship between the first tracking ID, the second tracking ID, the third tracking ID and the audio and video data stream is output to a maintainer of a log database.

6. The method according to claim 1, characterized in that Also includes: Sending a delayed detection request to the next-hop network node, the delayed detection request including a first time, the first time being a local time when the network node sends the delayed detection request; receiving a delayed detection response returned by the next-hop network node, wherein the delayed detection response includes the first time; Determine a delay between the network node and the next-hop network node according to a second time and the first time; The second time is the local time when the network node receives the delayed detection response.

7. The method according to claim 6, characterized in that Also includes: Receive the delay from the next hop network node to the data source end returned by the next hop network node; The link delay of the audio and video data stream is determined according to the delay between the network node and the next-hop network node and the delay from the next-hop network node to the data source.

8. The method according to claim 7, characterized in that Also includes: Outputting the link delay of the audio and video data stream to the playback end, server device or audio and video service provider; and / or Based on the link delay, network value-added services or network improvement suggestions are recommended to the audio and video service provider so that the audio and video service provider can improve the quality of network services.

9. A live streaming transmission method based on a content distribution network CDN, applicable to a CDN node, characterized in that: include: Receiving a playback request sent by a playback end, wherein the playback request includes a target stream identifier, which is used to identify the live stream that the playback end requests to play; Generate a first tracking ID that can uniquely identify the playback end, and record the corresponding relationship between the first tracking ID and the live stream in the log data of the live stream, so that when a playback abnormality occurs on the playback end, log data corresponding to the first tracking ID is obtained from the log data of the recorded live stream based on the first tracking ID to analyze the cause of the abnormality on the playback end; Acquire the live stream from the live broadcast end, and return the live stream to the playback end so that the playback end can play the live stream; Wherein, obtaining the live stream from the live broadcast end includes: If the live stream does not exist locally, plan to obtain a target path for the live stream and generate a second tracking ID, where the second tracking ID is used to track nodes on the target path; Sending an acquisition request to a next-hop CDN node of the CDN node on the target path, wherein the acquisition request includes the second tracking ID, so that the next-hop CDN node records the corresponding relationship between the second tracking ID and the live stream and returns the live stream; Receive the live stream returned by the next-hop CDN node; wherein the second tracking ID corresponds to the first tracking ID.

10. A video conferencing method based on a content distribution network (CDN), applicable to a CDN node, characterized in that: include: Receiving a conference request sent by a conference terminal, wherein the conference request includes a conference identifier for identifying a conference video stream; Generate a first tracking ID that can uniquely identify the conference terminal, and record the corresponding relationship between the first tracking ID and the conference video stream in the log data of the conference video stream, so that when a playback abnormality occurs on the playback end, the log data corresponding to the first tracking ID is obtained from the log data of the recorded conference video stream based on the first tracking ID to analyze the cause of the abnormality on the playback end; Acquire the conference video stream from other conference terminals, and return the conference video stream to the conference terminal so that the conference terminal can play the conference video stream; Wherein, obtaining the conference video stream from other conference terminals includes: If the conference video stream does not exist locally, plan a target path for acquiring the conference video stream and generate a second tracking ID, where the second tracking ID is used to track nodes on the target path; Sending an acquisition request to a next-hop CDN node of the CDN node on the target path, wherein the acquisition request includes the second tracking ID, so that the next-hop CDN node records the corresponding relationship between the second tracking ID and the conference video stream and returns the conference video stream; Receive the conference video stream returned by the next-hop CDN node; wherein the second tracking ID corresponds to the first tracking ID.

11. An audio and video transmission method, applicable to a network node, characterized in that: include: receiving a first acquisition request, where the first acquisition request is sent by a previous-hop network node of the network node on a target path, and the first acquisition request includes a second tracking ID; Recording the corresponding relationship between the second tracking ID and the audio and video data stream in the log data of the audio and video data stream, wherein the second tracking ID is used to track the nodes on the target path, wherein the target path is the path required to obtain the audio and video data stream, so that when a playback abnormality occurs on the playback end, the log data corresponding to the second tracking ID is obtained from the log data of the recorded audio and video data stream based on the second tracking ID to analyze the cause of the abnormality on the playback end; Acquire the audio and video data stream, and return the audio and video data stream to the previous-hop network node that sends it, so that the previous-hop network node returns the audio and video data stream to the playback terminal that requests the audio and video data stream; Wherein, obtaining the audio and video data stream includes: If the audio and video data stream does not exist locally, send a second acquisition request to the next-hop network node of the network node on the target path, wherein the second acquisition request includes the second tracking ID, so that the next-hop network node can record the correspondence between the second tracking ID and the audio and video data and return the audio and video data; and receive the audio and video data stream returned by the next-hop network node.

12. The method according to claim 11, characterized in that In the case where the audio and video data stream includes at least one stream segment, the method further includes: receiving a third tracking ID corresponding to each of the at least one flow segment returned by the next-hop network node, where the third tracking ID can uniquely identify the flow segment corresponding thereto; Recording a correspondence between the third tracking ID and at least one stream segment in the audio and video data stream; and The third tracking ID corresponding to each of the at least one flow segment is sent to the previous-hop network node, so that the previous-hop network node records the corresponding relationship between the third tracking ID and the at least one flow segment.

13. The method according to any one of claims 11-12, characterized in that: Also includes: Receiving a first delayed detection request sent by the previous-hop network node, where the first delayed detection request includes a first time, and the first time is a local time when the previous-hop network node sends the first delayed detection request; Returning a first delay detection response to the previous-hop network node, where the first delay detection response includes the first time, so that the previous-hop network node can determine the delay between itself and the network node according to the first time and the second time; The second time is the local time when the previous-hop network node receives the first delay detection response.

14. The method according to claim 11 or 12, characterized in that: Also includes: Sending a second delayed detection request to the next-hop network node, where the second delayed detection request includes a third time, and the third time is a local time when the network node sends the second delayed detection request; Receiving a second delayed detection response returned by the next-hop network node, wherein the second delayed detection response includes a third time; The delay between the network node and the next-hop network node is determined according to the third time and the fourth time; the fourth time is the local time when the network node receives the second delay detection response.

15. The method according to claim 14, characterized in that Also includes: Receive the delay from the next hop network node to the data source end returned by the next hop network node; Determine the delay from the network node to the data source end according to the delay between the network node and the next-hop network node and the delay from the next-hop network node to the data source end; The delay from the network node to the data source is sent to the previous-hop network node, so that the previous-hop network node can determine the delay from the previous-hop network node to the data source.

16. A live streaming transmission method based on a content distribution network CDN, applicable to a CDN node, characterized in that: include: receiving a first acquisition request, where the first acquisition request is sent by a previous-hop CDN node of the CDN node on a back-to-source path, and the first acquisition request includes a second tracking ID; In the log data of the live stream, the corresponding relationship between the second tracking ID and the live stream is recorded, wherein the second tracking ID is used to track the CDN node on the back-to-source path, and the back-to-source path is a path required to obtain the live stream, so that when a playback abnormality occurs on the playback end, the log data corresponding to the second tracking ID is obtained from the log data of the recorded live stream based on the second tracking ID to analyze the cause of the abnormality on the playback end; Acquire the live stream from the live broadcast end, and return the live stream to the previous-hop CDN node that sends the live stream, so that the previous-hop CDN node returns the live stream to the playback end that requests the live stream; Wherein, obtaining the live stream from the live broadcast end includes: If the live stream does not exist locally, send a second acquisition request to the next-hop network node of the CDN node on the return-to-source path, wherein the second acquisition request includes the second tracking ID, so that the next-hop network node can record the correspondence between the second tracking ID and the live stream and return the live stream; and receive the live stream returned by the next-hop network node.

17. A video conferencing method based on a content distribution network (CDN), applicable to a CDN node, characterized in that: include: receiving a first acquisition request, where the first acquisition request is sent by a previous-hop CDN node of the CDN node on a back-to-source path, and the first acquisition request includes a second tracking ID; In the log data of the conference video stream, the corresponding relationship between the second tracking ID and the conference video stream is recorded, the second tracking ID is used to track the CDN node on the back-to-source path, and the back-to-source path is the path required to obtain the conference video stream, so that in the case of abnormal playback on the playback end, the log data corresponding to the second tracking ID is obtained from the log data of the recorded conference video stream based on the second tracking ID to analyze the cause of the abnormal playback end. Acquire the conference video stream from other conference terminals, and return the conference video stream to the previous-hop CDN node that sends the previous-hop CDN node, so that the previous-hop CDN node returns the conference video stream to the conference terminal that initiates the conference request; Wherein, obtaining the conference video stream from other conference terminals includes: If the conference video stream does not exist locally, a second acquisition request is sent to the next-hop network node on the return path of the CDN node, and the second acquisition request includes the second tracking ID, so that the next-hop network node can record the correspondence between the second tracking ID and the conference video stream and return the conference video stream; and receive the conference video stream returned by the next-hop network node.

18. An audio and video transmission method, applicable to a network node, characterized in that: include: Receive audio and video data streams sent by the data source; According to the segmentation strategy, the audio and video data stream is segmented into at least one stream segment; Generate a third tracking ID for each of the at least one stream segment, wherein the third tracking ID can uniquely identify the stream segment corresponding to the third tracking ID, and record the correspondence between the third tracking ID and the corresponding stream segment in the audio and video data stream in the log data of the audio and video data stream, so that when a playback abnormality occurs on the playback end, the log data corresponding to the third tracking ID is obtained from the log data of the recorded audio and video data stream based on the third tracking ID to analyze the cause of the abnormality on the playback end; as well as Sending the at least one stream segment and its corresponding third tracking ID to a network node requesting the audio and video data stream; The receiving of the audio and video data stream sent by the data source includes: If the audio and video data stream does not exist locally, plan a target path for acquiring the audio and video data, and generate a second tracking ID, where the second tracking ID is used to track nodes on the target path; Sending an acquisition request to a next-hop network node of the network node on the target path, wherein the acquisition request includes the second tracking ID, so that the next-hop network node records the corresponding relationship between the second tracking ID and the audio and video data stream and returns the audio and video data stream; Receive the audio and video data stream returned by the next-hop network node; wherein the second tracking ID corresponds to the first tracking ID that can uniquely identify the playback end.

19. The method according to claim 18, characterized in that According to the segmentation strategy, the audio and video data stream is segmented into at least one stream segment, including: According to the streaming time of the audio and video service provider, the audio and video data stream is divided into at least one stream segment, and different stream segments correspond to different streaming times; and / or According to the content object in the audio and video data stream, the audio and video data stream is divided into at least one stream segment, and different stream segments correspond to different content objects.

20. An audio and video playback method, characterized in that: include: In response to the audio and video playback operation initiated by the user, a playback request is sent to the network node, wherein the playback request includes a target stream identifier for identifying the audio and video data stream requested to be played by the user; Receive the audio and video data stream and the first tracking ID returned by the network node according to the method of claim 1, wherein the first tracking ID is generated by the network node and is used to uniquely identify the playback end, and the network node records the corresponding relationship between the first tracking ID and the audio and video data stream in the log data of the audio and video data stream, so that when a playback abnormality occurs at the playback end, the log data corresponding to the first tracking ID is obtained from the log data of the recorded audio and video data stream based on the first tracking ID to analyze the cause of the abnormality at the playback end; The audio and video data stream is played, and the corresponding relationship between the first tracking ID and the audio and video data stream is recorded.

21. The method according to claim 20, characterized in that Also includes: receiving a second tracking ID returned by the network node, and recording a correspondence between the second tracking ID and the audio and video data stream, wherein the second tracking ID is used to track nodes on a target path, and the target path is a path planned by the network node for obtaining the audio and video data stream; and / or In the case that the audio and video data stream includes at least one stream segment, a third tracking ID corresponding to each of the at least one stream segment returned by the network node is received, and a corresponding relationship between the third tracking ID and the at least one stream segment is recorded.

22. The method according to claim 21, characterized in that Also includes: In response to a problem feedback operation triggered by the user, sending a problem feedback request to the server device, wherein the problem feedback request includes at least one tracking ID among the first tracking ID, the second tracking ID and the third tracking ID; Receive the problem cause information returned by the server device, and output the problem cause information, wherein the problem cause information is obtained by the server device based on the log data of the audio and video data stream corresponding to the at least one tracking ID obtained from the log database.

23. The method according to any one of claims 20 to 22, characterized in that: Also includes: Receive the link delay of the audio and video data stream sent by the network node, and display the link delay on the playback interface.

24. The method according to claim 23, characterized in that Also includes: If the link delay is greater than the set delay threshold, transitional content related to the audio and video content to be played in the audio and video data stream is displayed to wait for the audio and video content to be played.

25. A live broadcasting method based on a content distribution network CDN, characterized in that: include: In response to a live broadcast operation initiated by a user, a playback request is sent to a CDN node, where the playback request includes a target stream identifier, which is used to identify the live stream requested to be played by the user; Receive the live stream and the first tracking ID returned by the CDN node according to the method of claim 9, wherein the first tracking ID is generated by the CDN node and is used to uniquely identify the playback end, wherein the CDN node records the corresponding relationship between the first tracking ID and the live stream in the log data of the live stream, so that when a playback abnormality occurs at the playback end, the log data corresponding to the first tracking ID is obtained from the log data of the recorded live stream based on the first tracking ID to analyze the cause of the abnormality at the playback end; Play the live stream, and record the corresponding relationship between the first tracking ID and the live stream.

26. A video conferencing method based on a content distribution network (CDN), characterized in that: include: In response to the user's initiation of a conference joining operation, a conference request is sent to the CDN node, where the conference request includes a conference identifier for identifying the video conference that the user requests to attend; Receive the conference video stream and the first tracking ID returned by the CDN node according to the method of claim 10, wherein the first tracking ID is generated by the CDN node and is used to uniquely identify the conference terminal that sends the conference request, wherein the CDN node records the corresponding relationship between the first tracking ID and the conference video stream in the log data of the conference video stream, so that when an abnormal playback problem occurs at the playback end, the log data corresponding to the first tracking ID is obtained from the log data of the recorded conference video stream based on the first tracking ID to analyze the cause of the abnormal problem at the playback end; The conference video stream is played, and the corresponding relationship between the first tracking ID and the conference video stream is recorded.

27. A network delay detection method, applicable to a network node, characterized in that: include: Receive a playback request sent by a playback end, wherein the playback request is used to request playback of an audio or video data stream; Sending a delay detection request to a next-hop network node that provides the audio and video data stream, wherein the delay detection request includes a first time, and the first time is a local time when the network node sends the delay detection request; receiving a delayed detection response returned by the next-hop network node, wherein the delayed detection response includes the first time; Determine the delay between the network node and the next-hop network node according to a second time and the first time; the second time is the local time when the network node receives the delay detection response; Wherein, the network node executes the method described in any one of claims 1 to 5 to return the audio and video data stream to the playback end.

28. The method according to claim 27, characterized in that Also includes: Receive the delay from the next hop network node to the data source end returned by the next hop network node; The link delay of the audio and video data stream is determined according to the delay between the network node and the next-hop network node and the delay from the next-hop network node to the data source.

29. The method according to claim 28, characterized in that Also includes: Outputting the link delay of the audio and video data stream to the playback end, server device or audio and video service provider; and / or Based on the link delay, network value-added services or network improvement suggestions are recommended to the audio and video service provider so that the audio and video service provider can improve the quality of network services.

30. The method according to any one of claims 27 to 29, characterized in that: The network node is a CDN node, and the audio and video data stream is a live stream or a conference video stream in a video conference.

31. A network node, characterized in that: include: Memory and processor; The memory is used to store a computer program; the processor is coupled to the memory and is used to execute the computer program to: Receive a playback request sent by a playback end, wherein the playback request includes a target stream identifier for identifying an audio or video data stream requested to be played by the playback end; Generate a first tracking ID that can uniquely identify the playback end, and record the corresponding relationship between the first tracking ID and the audio and video data stream in the log data of the audio and video data stream, so that when a playback abnormality occurs on the playback end, the log data corresponding to the first tracking ID is obtained from the log data of the recorded audio and video data stream based on the first tracking ID to analyze the cause of the abnormality on the playback end; Acquire the audio and video data stream from the data source end, and return the audio and video data stream to the playback end so that the playback end can play the audio and video data stream; Wherein, obtaining the audio and video data stream from the data source includes: If the audio and video data stream does not exist locally, plan a target path for acquiring the audio and video data, and generate a second tracking ID, where the second tracking ID is used to track nodes on the target path; Sending an acquisition request to a next-hop network node of the network node on the target path, wherein the acquisition request includes the second tracking ID, so that the next-hop network node records the corresponding relationship between the second tracking ID and the audio and video data stream and returns the audio and video data stream; Receive the audio and video data stream returned by the next-hop network node; wherein the second tracking ID corresponds to the first tracking ID.

32. A network node, characterized in that: include: Memory and processor; The memory is used to store a computer program; the processor is coupled to the memory and is used to execute the computer program to: receiving a first acquisition request, where the first acquisition request is sent by a previous-hop network node of the network node on a target path, and the first acquisition request includes a second tracking ID; Recording the corresponding relationship between the second tracking ID and the audio and video data stream in the log data of the audio and video data stream, wherein the second tracking ID is used to track the nodes on the target path, wherein the target path is the path required to obtain the audio and video data stream, so that when a playback abnormality occurs on the playback end, the log data corresponding to the second tracking ID is obtained from the log data of the recorded audio and video data stream based on the second tracking ID to analyze the cause of the abnormality on the playback end; Acquire the audio and video data stream, and return the audio and video data stream to the previous-hop network node that sends it, so that the previous-hop network node returns the audio and video data stream to the playback terminal that requests the audio and video data stream; Wherein, obtaining the audio and video data stream includes: If the audio and video data stream does not exist locally, send a second acquisition request to the next-hop network node of the network node on the target path, wherein the second acquisition request includes the second tracking ID, so that the next-hop network node can record the correspondence between the second tracking ID and the audio and video data and return the audio and video data; and receive the audio and video data stream returned by the next-hop network node.

33. A network node, characterized in that: include: Memory and processor; The memory is used to store a computer program; the processor is coupled to the memory and is used to execute the computer program to: Receive audio and video data streams sent by the data source; According to the segmentation strategy, the audio and video data stream is segmented into at least one stream segment; Generate a third tracking ID for each of the at least one stream segment, wherein the third tracking ID can uniquely identify the stream segment to which it corresponds; and record the correspondence between the third tracking ID and the corresponding stream segment in the audio and video data stream in the log data of the audio and video data stream, so that when a playback abnormality occurs on the playback end, the log data corresponding to the third tracking ID is obtained from the log data of the recorded audio and video data stream based on the third tracking ID to analyze the cause of the abnormality on the playback end, and Sending the at least one stream segment and its corresponding third tracking ID to a network node requesting the audio and video data stream; The receiving of the audio and video data stream sent by the data source includes: If the audio and video data stream does not exist locally, plan a target path for acquiring the audio and video data, and generate a second tracking ID, where the second tracking ID is used to track nodes on the target path; Sending an acquisition request to a next-hop network node of the network node on the target path, wherein the acquisition request includes the second tracking ID, so that the next-hop network node records the corresponding relationship between the second tracking ID and the audio and video data stream and returns the audio and video data stream; Receive the audio and video data stream returned by the next-hop network node; wherein the second tracking ID corresponds to the first tracking ID that can uniquely identify the playback end.

34. A network node, characterized in that: include: Memory and processor; The memory is used to store a computer program; the processor is coupled to the memory and is used to execute the computer program to: Receive a playback request sent by a playback end, wherein the playback request is used to request playback of an audio or video data stream; Sending a delay detection request to a next-hop network node that provides the audio and video data stream, wherein the delay detection request includes a first time, and the first time is a local time when the network node sends the delay detection request; receiving a delayed detection response returned by the next-hop network node, wherein the delayed detection response includes the first time; Determine the delay between the network node and the next-hop network node according to a second time and the first time; the second time is the local time when the network node receives the delay detection response; Wherein, the network node executes the method described in any one of claims 1 to 5 to return the audio and video data stream to the playback end.

35. A playback terminal, characterized in that: include: Memory and processor; The memory is used to store a computer program; the processor is coupled to the memory and is used to execute the computer program to: In response to the audio and video playback operation initiated by the user, a playback request is sent to the network node, wherein the playback request includes a target stream identifier for identifying the audio and video data stream requested to be played by the user; Receive the audio and video data stream and the first tracking ID returned by the network node according to the method of claim 1, wherein the first tracking ID is generated by the network node and is used to uniquely identify the playback end, and the network node records the corresponding relationship between the first tracking ID and the audio and video data stream in the log data of the audio and video data stream, so that when a playback abnormality occurs at the playback end, the log data corresponding to the first tracking ID is obtained from the log data of the recorded audio and video data stream based on the first tracking ID to analyze the cause of the abnormality at the playback end; The audio and video data stream is played, and the corresponding relationship between the first tracking ID and the audio and video data stream is recorded.

36. A data transmission method, applicable to a network node, characterized in that: include: Receiving a data request sent by a data receiving end, wherein the data request includes a data identifier for identifying target data requested by the data receiving end; Generate a first tracking ID that can uniquely identify the data receiving end, and record the corresponding relationship between the first tracking ID and the target data in the log data of the target data, so that when a playback abnormality occurs at the data receiving end, the log data corresponding to the first tracking ID is obtained from the log data of the recorded target data based on the first tracking ID to analyze the cause of the abnormality at the data receiving end; Acquire the target data from the data source end, and return the target data to the data receiving end; Wherein, obtaining the target data from the data source includes: If the target data does not exist locally, plan a target path for acquiring the target data, and generate a second tracking ID, where the second tracking ID is used to track nodes on the target path; Sending an acquisition request to a next-hop network node of the network node on the target path, wherein the acquisition request includes the second tracking ID, so that the next-hop network node records the corresponding relationship between the second tracking ID and the target data and returns the target data; The target data returned by the next-hop network node is received; wherein the second tracking ID corresponds to the first tracking ID.

37. The method according to claim 36, characterized in that In the case where the target data includes at least one data segment, the method further includes: Receive a third tracking ID corresponding to each of the at least one data fragment returned by the next-hop network node, where the third tracking ID can uniquely identify the data fragment corresponding thereto; The corresponding relationship between the third tracking ID and at least one data segment in the target data is recorded.

38. A computer-readable storage medium storing a computer program, characterized in that: When the computer program is executed by a processor, the processor is enabled to implement the steps of the method according to any one of claims 1 to 30 and 36 to 37.

39. A computer program product comprising a computer program / instructions, characterized in that When the computer program / instructions are executed by a processor, the processor is enabled to implement the steps in the method of any one of claims 1-30 and 36-37.