CN113727198A

CN113727198A - Slice video pause identification method, network equipment and storage medium

Info

Publication number: CN113727198A
Application number: CN202010450832.9A
Authority: CN
Inventors: 黄阿柳
Original assignee: ZTE Corp
Current assignee: ZTE Corp
Priority date: 2020-05-25
Filing date: 2020-05-25
Publication date: 2021-11-30

Abstract

The embodiment of the invention provides a method for identifying the stuck video in slices, network equipment and a storage medium, wherein when the network equipment evaluates a video service in slices, the network equipment can acquire the downloading condition of a single slice according to the downloading information of the slices, and because the network equipment also acquires a slice index file through acquired signaling data, the smoothness of downloading and playing of a plurality of slices in the video service in slices can be embodied by combining the slice index file with the downloading information of the slices, and meanwhile, the relationship between the downloading and playing process of one slice in the slice index file and the downloading and playing process of another slice in the slice index file can be determined by combining the slice index file with the downloading information of the slices, so that the stuck video between the slices can be identified. Therefore, the blocking in the slicing video service process can be accurately identified, so that the evaluation result is more in line with the real experience of the user, and a foundation is provided for the subsequent slicing video service improvement.

Description

Slice video pause identification method, network equipment and storage medium

Technical Field

The embodiment of the invention relates to the technical field of internet, in particular to a slice video stuck identification method, network equipment and a storage medium.

Background

In order to understand the user experience of the video service, the video service needs to be evaluated and analyzed, and the related video analysis method only considers the video service as a download service to analyze the video service according to Key Performance Indicators (KPIs) of the download service, such as rate and time delay. However, most of the current video services use a slicing protocol: the client downloads the slice index file of the video, and then pulls the slices in sequence according to the slice download addresses in the slice index file for playing. Playing a complete video in a slice video service may require downloading from hundreds of incompletely identical download addresses, so that a KPI system in the related art can only evaluate the quality of downloading a single slice, but a single slice download index cannot embody the smoothness of downloading and playing hundreds of slices by a client, resulting in a large difference between an evaluation result and the actual perception of a user.

Disclosure of Invention

The embodiment of the invention provides a slice video stuck identification method, network equipment and a storage medium, and mainly solves the technical problems that: the assessment scheme for the slice video service is provided, and the problem that assessment results cannot accurately reflect the actual playing fluency of the client side and the actual perception of a user due to the fact that the slice video service is only used as a download service for assessment analysis in the related art is solved.

In order to solve the above technical problem, an embodiment of the present invention provides a method for identifying a video clip of a slice, including:

acquiring signaling data on a core network link;

acquiring a slice index file and slice downloading information associated with the slice index file according to the signaling data;

and identifying the pause in the playing process of the slice video according to the slice index file and the slice downloading information.

The embodiment of the invention also provides network equipment, which comprises a processor, a memory and a communication bus;

the communication bus is used for realizing connection communication between the processor and the memory;

the processor is configured to execute one or more programs stored in the memory to implement the steps of the above-described slice video stuck identification method.

Embodiments of the present invention also provide a storage medium storing one or more programs, which are executable by one or more processors to implement the steps of the above-mentioned slice video katon identification method.

The invention has the beneficial effects that:

according to the method for identifying the stuck video in the slice video, the network device and the storage medium provided by the embodiment of the invention, the network device acquires the signaling data on the core network link, then acquires the slice index file and the slice downloading information associated with the slice index file according to the signaling data, and then the network device can identify the stuck video in the playing process of the slice video according to the slice index file and the slice downloading information. The section video pause identification scheme provided by the embodiment of the invention can acquire the downloading condition of a single section according to the section downloading information when evaluating the section video service, and because the network equipment also acquires the section index file through the acquired signaling data, and the section index file simultaneously corresponds to a plurality of or even all the sections in a video, the smoothness of downloading and playing a plurality of sections in the section video service can be embodied by utilizing the section index file and combining the section downloading information corresponding to the section index file, and simultaneously, because the playing of each section in the section index file is played one by one in sequence under the normal condition, the relationship between the downloading and playing process of one section in the section index file and the downloading and playing process of another section in the section index file can be determined by utilizing the combination of the section index file and the section downloading information, thereby identifying the slice-to-slice stuck. Therefore, the embodiment of the invention provides a new evaluation scheme for the slicing video service, which can accurately identify the pause in the slicing video service process, so that the evaluation result is more in line with the real experience of a user, and a foundation is provided for the subsequent slicing video service improvement.

Additional features and corresponding advantages of the invention will be set forth in part in the description which follows, and in part will be obvious from the description, or may be learned by practice of the invention.

Drawings

Fig. 1 is a flowchart of a slice video stuck identification method according to an embodiment of the present invention;

fig. 2 is a flowchart illustrating a network device obtaining a slice index file according to signaling data according to an embodiment of the present invention;

fig. 3 is a flowchart illustrating a network device obtaining slice download information according to signaling data according to an embodiment of the present invention;

fig. 4 is a flowchart illustrating a process of identifying a stuck video during playing of a sliced video according to a second embodiment of the present invention;

FIG. 5 is a flowchart illustrating a second embodiment of detecting a pause condition at a current slice;

FIG. 6 is a flowchart illustrating the identification of a pause as stuck according to a second embodiment of the present invention;

FIG. 7 is a flowchart of identifying and recording pauses provided in a third embodiment of the present invention;

fig. 8 is a flowchart of detecting a pause condition at a current slice according to a third embodiment of the present invention;

FIG. 9 is a flowchart illustrating the identification of a pause as a pause according to a third embodiment of the present invention;

fig. 10 is a flowchart illustrating the process of identifying a drag according to the third embodiment of the present invention;

fig. 11 is a schematic hardware structure diagram of a network device according to a fifth embodiment of the present invention.

Detailed Description

In order to make the objects, technical solutions and advantages of the present invention more apparent, embodiments of the present invention are described in detail below with reference to the accompanying drawings. It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.

The first embodiment is as follows:

with the rapid development of mobile networks, the traffic charges are continuously reduced, and the proportion of videos watched by users through the mobile networks is gradually increased. With the change of the service use habits of users, the concern of the mobile operators on the network quality gradually shifts to the data service quality from the initial voice call quality. The video service is different from the general data service of network browsing, and has higher requirements on the network stability as well as higher requirements on the bandwidth. If the network quality is not good, the video definition and the fluency are reduced, and the pause phenomenon is easy to occur. The excessive times of the blocking inevitably reduce the satisfaction degree of the user and increase the network complaint amount. Therefore, for a mobile operator, the real perception of the client-side user to the video service is known, and a corresponding improvement measure is given for the problem phenomenon, so that complaints can be reduced, and the user satisfaction and the user viscosity are improved.

Therefore, it is very important to accurately evaluate the video service experience of the user and know the user perception. However, at present, for the slice video service lacks a suitable evaluation and analysis scheme, in order to solve the problem, the embodiment provides a slice video stuck identification method, which is applied to a network device, so as to help a network side to know the fluency of the user video service, please refer to a flowchart of the slice video stuck identification method shown in fig. 1:

s102: the network device collects signaling data on a core network link.

In this embodiment, the network device may collect signaling data on a link of the core network, for example, the network device may collect data of an interface connecting the core network and the radio access network, where the interface connecting the core network and the radio access network includes, but is not limited to, an S1-U interface. The S1 interface is a communication interface between the LTE eNodeB and the EPC (packet core network), which can divide the LTE system into a radio access network and a core network. The S1-U interface is an S1 user plane interface, which is connected between an eNodeB and an S-GW (Serving GateWay) and provides non-guaranteed transmission of user plane PDUs (Protocol Data units) between the eNodeB and the S-GW.

It should be understood that the S1-U interface is only a data acquisition object of the network device in the LTE communication scenario in the present embodiment, but those skilled in the art should understand that in 3G, 5G and other future communication scenarios, interfaces with the same function may have different names. Therefore, the network device is not limited in this embodiment to collect signaling data of the S1-U interface.

S104: and the network equipment acquires the slice index file and the slice downloading information associated with the slice index file according to the signaling data.

When the network device collects signaling data, it usually collects all signaling data passing through corresponding link interfaces in the whole network, and does not distinguish the specific content of the signaling data from the specific user to which the signaling data belongs before distinguishing. However, in this embodiment, the purpose of the network device in data acquisition is to acquire the slice index file and the slice download information, so in this embodiment, the network device processes the acquired data after acquiring the signaling data. The following describes a process of acquiring a slice index file by a network device according to signaling data with reference to fig. 2:

s202: the network device identifies a slice index file download request in an HTTP-GET request.

HTTP request signaling data transmitted between the core network and the wireless access network is divided into HTTP-GET (hypertext transfer protocol request to request data from a specified resource) request and HTTP-POST (hypertext transfer protocol request to submit data to be processed to a specified resource) request. Since the slice video service is to obtain the slice index file and the slice file from the server, the processing object required by the network device in this embodiment is an HTTP-GET request.

In an example of this embodiment, the network device identifies the slice index file download request from the HTTP-GET request, and optionally, the network device may determine whether an HTTP-GET request is a slice index file download request according to a URI (Uniform Resource Identifier) in an HTTP header parameter in the HTTP-GET request: there is a parameter indicating the file format in the URI, for example, the HTTP-GET request URI corresponding to the M3U8 file contains a character indicating the file format ". M3U 8? "so by parsing the URI within the HTTP header parameter of an HTTP-GET request, it can be determined whether the HTTP-GET request is a download request for requesting to obtain the slice index file.

S204: and the network equipment analyzes the payload data of the slice index file downloading request.

If the network device determines that a certain HTTP-GET request is a download request for requesting a slice index file through identification, the network device may further parse payload (payload data) of the HTTP-GET request, that is, parse payload content of the download request of the slice index file.

S206: and the network equipment restores the slice index file according to the analysis result.

Since the slice index file is transmitted in the signaling when the server transmits the slice index file to the client, the network device can directly restore the slice index file transmitted to the client by the server according to the analysis result by analyzing the payload of the download request of the slice index file. It can be understood that, when the server transmits the HTTP-GET request to the client, one HTTP-GET request message is divided into a plurality of data packets for transmission, and therefore, after the network device parses the data packets, the parsing results are merged, so as to restore the slice index file.

Some or all of the following information may be included in the slice index file in general: slice number indication information, slice download link (ext _ uri), slice duration (ext _ inf), slice file size (ext _ size), and the like. One slice index file generally corresponds to a plurality of slices, and therefore, download links, slice durations, and slice file sizes of the plurality of slices may be indicated in one slice index file. For example, in some examples of the present embodiment, since information of 10 slices is indicated in one slice index file, the first slice has a sequence number of "0", and the slice sequence number of each slice is an arithmetic sequence having a tolerance of 1, the slice index file is used to indicate information of 10 slices having slice sequence numbers of "0" to "9" to the client.

In some examples of this embodiment, after acquiring the slice index file, the network device may further acquire an index identifier (ext _ id) of the slice index file, where the index identifier is information for uniquely distinguishing one slice index file. In some cases, each slice index file has its own name, so the network device may identify the name of the slice index file as its index. In another example, the network device may use a timestamp that the network device acquired the slice index file as an index identifier of the slice index file.

The following describes a process of acquiring slice download information from signaling data by a network device with reference to fig. 3:

s302: the network device identifies a slice download request in the HTTP-GET request.

Similar to the process of identifying a slice index file download request from an HTTP-GET request, the network device may also determine whether an HTTP-GET request is a slice file download request according to the URI in the HTTP header parameter of the HTTP-GET request, for example, the URI includes "TS? "or". 264 TS? ",". 265 TS? "etc. represent characters of the format. Therefore, by identifying whether there is a "TS" within the URI of the HTTP-GET request header parameter? ",". 264 TS? ",". 265 TS? An isocharacter may determine whether the HTTP-GET request is a request for downloading a TS slice file.

S304: and the network equipment analyzes the head parameters of the slice downloading request to obtain slice downloading information.

After the network device identifies the slice downloading request in the HTTP-GET request, the slice downloading information may be obtained according to a header parameter of the slice downloading request.

It should be noted that, the relationship between the slice download information and the slices is one-to-one, and one slice download information can only represent the download situation of one slice, but cannot represent the download situation of other slices. Part or all of the following information may be included in one slice download information: the method includes the steps of requesting for downloading a slice corresponding to a slice request (that is, the time when the slice GET process starts), returning an HTTP response code, finishing downloading the last HTTP packet in the slice GET process, downloading an address of the slice, and adding the IP layer byte lengths (IP _ length) of all messages in the slice GET process. In some examples of this embodiment, a host name (host) providing the slice resource may also be included in the slice download information.

Request time of slice request download: here, denoted as "bmime", which indicates the time when the request for slicing to the server is started; time of HTTP response code return: here, denoted as "beginning of t", which indicates the time when the server returns the first packet of the slice to the client; time for completing downloading of the last HTTP packet in the slice GET process: here, denoted as "t end", indicates the time when the server returns the last packet of the slice to the client; the sum of the IP layer byte lengths of all messages in the slice GET flow: here, denoted as "ip _ length" indicates the actual flow rate during the slice download.

In this embodiment, the time sequence of the two processes of acquiring the slice index file and acquiring the slice download information from the signaling data by the network device is not strictly limited, and the network device may acquire the slice index file from the signaling data first, may acquire the slice download information first, and may even perform the two processes alternately/simultaneously.

After the network device obtains the slice index file and the slice download information, the network device can store the slice index file and the slice download information respectively. In some examples of this embodiment, the network device may store the slice index file in the dimension table, where information in the slice index file is stored at a granularity of a slice, and one slice download link is stored as a row, while the index identifier is used as a unique primary key of the dimension table. On the other hand, the network device stores the slice download information in the fact table, and the download information of one slice is stored as one line also with the slice as granularity.

It should be understood that there is no association correspondence between the slice index file and the slice download information directly obtained by the network device from the signaling data, because the network device usually collects data of all users in the whole network when data collection is performed, the association correspondence between the slice index file and the slice download information can be determined only by further analysis processing of the network device.

It is understood that a slice download link of a corresponding slice is included in the slice index file, and each slice download information also indicates a download address of the corresponding slice, so that the association correspondence between the slice index file and the slice download information can be realized through the slice URI. In this embodiment, after the network device implements association correspondence between information in the slice index file and the slice download performed through the slice URI, the information of the slice index file may be filled into the fact table according to the association correspondence with the slice as a granularity.

For example, assume that one slice URI is "a 111 a" and another slice URI is "bbbb" in a certain slice index file, while there is a slice download information indicating that the download address of the corresponding slice is "a 111 a" in the 11 th row of the fact table; if there is a slice download information at line 222 of the fact table indicating that the download address of the corresponding slice is "bbbb", the network device may fill the information corresponding to "a 111 a" in the slice index file to line 11 of the fact table and fill the information corresponding to "bbbb" in the slice index file to line 222 of the fact table.

S106: and the network equipment identifies the pause in the playing process of the slice video according to the slice index file and the slice downloading information.

It can be understood that, after the network device determines the association relationship between the slice index file and the slice download information, it means that the network device has already acquired the slice index file and the slice download information associated with the slice index file. The network device may then combine the slice index file with the slice download information to identify the pause in the playing of the sliced video. The network device can know the actual downloading condition of the video file corresponding to one slice index file according to the slice duration, the slice size, and the ip _ length, the beginning of t, the end of t, and the bmime in the slice downloading information in the slice index file, for example, the single-slice downloading speed of each slice first, the expected downloading speed of each slice in the entire index file, the theoretical accumulated playing duration at a certain playing position of the video, and the actual accumulated playing duration at the playing position of the network device. And then the network equipment identifies whether the video is jammed in the video playing process according to the calculated parameter value.

The embodiment provides a scheme for identifying a pause phenomenon in a playing process of a slice video by combining a slice index file and slice downloading information, through the evaluation mode, the slice video can be taken as a video to pay attention to the pause times of the video, not only the downloading speed and the downloading time delay of a single slice of the slice video, the slice video pause identification method is combined with the slice index file to evaluate the user experience from the whole slice video, and the pause problem which cannot be found when the single slice is taken as an evaluation object originally, such as the pause between the slices and the like, can be paid attention to. Meanwhile, the slice video stuck identification method is characterized in that data acquisition is carried out by equipment on the network side to complete evaluation and analysis, the user side does not need to be improved, negative influence on the user due to the stuck identification process is avoided, and the user experience can be further maintained.

Example two:

in this embodiment, a process of the network device identifying the pause in the playing process of the slice video according to the slice index file and the slice download information will be further described on the basis of the first embodiment, and first, please refer to a flowchart shown in fig. 4:

s402: and the network equipment detects whether a pause exists at the current slice according to the slice index file and the slice downloading information.

If the detection result is yes, the network device executes S404, otherwise, the identification of the current slice morton is ended.

In this embodiment, the network device may gradually identify the pause in the playing process of the slice video from front to back according to the downloading and playing sequence of each slice in the slice video, where the "current slice" is the current detection object of the network device, and it is needless to say that the current slice may also change continuously along with the progress of the network device identification process.

It should be understood that, in this embodiment, the process of performing hiton recognition by the network device may be performed in real time during the playing of the slice video, or may be performed after the playing of the slice video is completed.

In some examples of this embodiment, the network device may detect whether there is a pause at the current slice based solely on information of neighboring slices. In some examples of the present embodiment, the information of multiple slices may be combined to detect whether there is a pause at the current slice. For example, in the present embodiment, whether there is a pause at the current slice may be detected based on the business continuity process, please refer to fig. 5:

s502: and the network equipment determines the theoretical accumulated playing time of the current service continuous process according to the slice time of each slice in the slice index file.

In this embodiment, the service continuity process refers to a process in which the slice number and the playing time are both continuous when the slice is played. That is, in the playing process, the serial numbers of the slices are consistent all the time without jumping and without time pause. Therefore, in other words, the service continuity process in this embodiment refers to a playing process without progress dragging, pause, and pause.

The theoretical accumulated playing time length refers to the sum of the slice time lengths of all the slices already played in the service continuous process. For example, in an example, in a service continuity process, the client has currently played 14 slices continuously, and the sum of the slice durations of the 14 slices is the current theoretical cumulative playing duration. As can be seen from the foregoing description, the slice duration of each slice is recorded in the slice index file, and therefore, the network device can determine the theoretical cumulative playing duration according to the slice duration of each slice in the slice index file. The theoretical accumulated playing time length represents the time length required for completing one video playing under the conditions of no pause, no dragging and no pause.

S504: and the network equipment determines the actual accumulated playing time of the current service continuous process according to the downloading request time of each slice request in the slice downloading information.

The actual playing time length is the total time spent by the client from the start point of the service continuity process to the current time, and the request time of each slice requesting downloading can be determined according to the slice downloading information, so in this embodiment, the request time of the initial slice requesting downloading in the service continuity process is used to represent the start point of the service continuity process, that is, the initial slice is the first slice played in the service continuity process. And simultaneously, representing the current time by adopting the request time of the current slice requesting downloading. Therefore, the actual accumulated playing time is actually the time difference between the request time of the current slice for requesting downloading and the request time of the initial slice for requesting downloading.

The business continuation process ends with the occurrence of a stuck, paused or dragged event, and thus the initial slice naturally changes with the occurrence of a stuck, paused or dragged event.

In addition, it should be noted that in this embodiment, the execution timing of S504 and S502 by the network device may be reversed, that is, the network device determines the actual accumulated playing time first and then determines the theoretical accumulated playing time, or in some examples of this embodiment, the network device determines the actual accumulated playing time and the theoretical accumulated playing time synchronously.

S506: and if the actual accumulated playing time length is greater than the theoretical accumulated playing time length, the network equipment determines that the current slice is stopped.

After the actual accumulated playing time and the theoretical accumulated playing time are determined, the network device may determine whether a pause occurs currently according to the sizes of the actual accumulated playing time and the theoretical accumulated playing time, and it is doubtless that if a pause occurs at the current slice, the actual accumulated playing time is greater than the theoretical playing time, and therefore, if the actual accumulated playing time is greater than the theoretical accumulated playing time, the network device may determine that a pause exists at the current slice.

S404: and the network equipment identifies whether the pause is pause or not according to the slice index file and the slice downloading information.

If the determination result is yes, the network device executes S406, otherwise, the process is ended.

In this embodiment, a scheme for a network device to identify whether a pause is stuck or not is provided, please refer to a flowchart shown in fig. 6:

s602: and the network equipment determines the expected downloading speed of each slice according to the size of each slice in the slice index file and the slice duration of each slice.

In this embodiment, the expected downloading speed may be represented by a ratio of a sum of file sizes of all slices corresponding to the slice index file to a sum of slice durations, which is a downloading speed that needs to be ensured if a user wants to watch a slice video in a flow without pause or drag. As can be seen from the description of the first embodiment, the file size of each slice and the time length of each slice can be determined according to the slice index file, and therefore, the network device can calculate the total file size of each slice corresponding to the slice index file, that is:

wherein S represents the total file size of each slice corresponding to the slice index file, ext _ size_iThe file size of the ith slice is shown, and M shows that the total number of slices corresponding to the slice index file is M.

Meanwhile, the network device may also determine the total duration of each slice corresponding to the slice index file:

wherein T represents the total duration of each slice corresponding to the slice index file, ext _ inf_iIndicating the duration of the ith slice.

Therefore, the desired download speed is the ratio of S to T.

S604: and the network equipment determines the actual single-slice downloading speed of each slice in the current service continuous process according to the slice downloading information.

The single-slice download speed refers to the actual download speed of a single slice, and this embodiment provides a way to determine the download speed of each slice in the service continuity process:

for each slice in the service continuous process, the network device determines the sum of the IP layer byte lengths of all messages in the slice downloading flow, i.e. IP _ length, according to the slice downloading information corresponding to the slice, and determines the flow time spent by the slice downloading flow. As can be seen from the description of the foregoing embodiment, the slice download information includes beginning t (the time when the server returns the first data packet of the slice to the client) and end t (the time when the server returns the last data packet of the slice to the client), so that, according to the end t and the beginning t in one slice download information, the network device can determine the flow time taken to download the corresponding slice, that is, the flow time t:

t is t end-t initial;

the network device may then determine the ratio of ip _ length of the slice to the flow time t as the single-slice download speed for the slice.

It should be appreciated that the execution timing of S604 and S602 by the network device in this embodiment may be reversed, that is, the network device determines the single-slice download speed first and then determines the desired download speed, or in some examples of this embodiment, the network device determines the single-slice download speed and the desired download speed synchronously.

S606: and if the single-slice downloading speed of at least one slice in the service continuous process is lower than the expected downloading speed, judging that the pause existing at the current slice of the network equipment is pause.

In this embodiment, when the network device recognizes a pause, it may be settled that the current slice is paused only by requiring that the single-slice downloading speed of at least one slice in the service continuity process is lower than the expected downloading speed, but it may be understood that, in some other examples of this embodiment, the network device may also require that the pause occurring in the current slice is determined to be stuck when the single-slice downloading speed of the slices in the service continuity process at the first preset ratio or the first preset number (the preset number is greater than 1) is lower than the expected downloading speed.

S406: the network device records that the playing of the current slice is blocked.

After the network device identifies the currently sliced morton, it may record the morton, in one example of this embodiment, the network device may record the morton in a fact table.

In the stuck-in recognition scheme provided in this embodiment, the network device first detects whether there is a pause in one slice, and further recognizes whether the pause is stuck in the case that it is determined that there is a pause. In addition, in the process of detecting the pause, the network equipment can detect only according to the adjacent slices, so that the detection complexity is reduced. Or, the network device can also detect by combining each slice in the service continuous process, so that the accuracy and the comprehensiveness of the stuck detection are improved.

Example three:

it should be understood that, in the process of performing stuck detection based on the business continuation process, the determination of the initial slice, which is the starting point of the business continuation process, affects the result of stuck identification, but the business continuation process and the initial slice are affected not only by stuck but also by pause and drag, so that it is very important to identify pause and drag. In this embodiment, a process of identifying pause and drag will be described, please refer to a flowchart of pause identification shown in fig. 7:

s702: and the network equipment detects whether a pause exists at the current slice according to the slice index file and the slice downloading information.

If the detection result is yes, the network device executes S704, otherwise, the identification of the current slice pause is ended.

In some examples of this embodiment, the network device may use the flow illustrated in fig. 5 to detect whether there is a pause at the current slice, that is, the network device may combine information of multiple slices to detect whether there is a pause at the current slice. However, in some other examples, the network device may detect whether there is a pause at the current slice based only on the information of the neighboring slices, see the flowchart shown in fig. 8:

s802: and the network equipment determines the request time of the current slice and the request time of the next slice according to the request time of each slice requesting downloading in the slice downloading information.

The next slice is a slice subsequent to the current slice, for example, if the slice number of the current slice is "14", the slice with the slice number "15" is the next slice of the current slice. For a slice with a slice number of "14" (hereinafter referred to as "14") and a slice with a slice number of "15" (hereinafter referred to as "15"), the network device can determine that the request time of two slices requesting downloading is the bmime 14 and the bmime 15, respectively, according to the slice duration of each slice in the slice index file.

S804: and the network equipment determines the slicing time length of the current slice according to the slicing time length of each slice in the slice index file.

The slice duration of each slice is recorded in the slice index file, so that the network device can determine the slice duration of the current slice according to the slice duration of each slice in the slice index file. It can be understood that, in the ideal case of no drag, pause and pause, the time required for playing the current slice is actually the slice duration of the current slice, so for the slice with the slice number "14", the time required in the ideal state should be equal to the slice duration.

S806: the network device determines a time difference between the request time of the next slice and the request time of the current slice.

The description continues with two slices, slice "14" and slice "15", as examples: the time difference between the btime15 and the btime14 is the time it actually takes for the slice "14" to complete from the start of the requested download.

It is understood that in the above process, S806 needs to be performed before S802, but the timing of S804 is not fixed, and in some examples, the network device may perform the process of S804 before performing S802, or perform the process of S804 after performing the process of S806.

S808: and if the time difference is larger than the slicing duration of the current slice, the network equipment determines that the pause occurs at the current slice.

If the time difference between the bdime 15 and the bdime 14 is greater than the slice duration of slice "14", then it is evident that there is a pause in the playback of slice "14" or between slice "14" and slice "15", which in this embodiment is counted as occurring before slice "15" on slice 14, i.e., counted as occurring on the current slice.

S704: and the network equipment identifies the pause as pause according to the slice index file and the slice downloading information.

After the network device recognizes that there is a pause on the current slice, it needs to determine whether the pause is a pause. Optionally, please refer to the flow shown in fig. 9:

s902: the network equipment determines the expected downloading speed of each slice according to the size of each slice in the slice index file and the slice duration of each slice;

s904: the network equipment determines the actual single-slice downloading speed of each slice in the current service continuous process according to the slice downloading information;

the timing and specific process for determining the desired download speed and the single-slice download speed by the network device may refer to the description in embodiment two, and are not described herein again.

S906: and if the single-slice downloading speed of all slices in the service continuous process is greater than the expected downloading speed, determining that the current slice is paused.

It is understood that, in some other examples of this embodiment, the network device may also require that the pause occurring when the single-slice download speed of the slices that are not less than the second preset ratio or the second preset number (the preset number is greater than 1) in the service continuity process is less than the expected download speed is determined as the pause.

S706: the network device records the pause at the current slice.

The following describes a process of detecting dragging during playing of a slice video by a network device with reference to a flowchart shown in fig. 10:

s1002: the network equipment detects the dragging condition of the current slice according to the slice index file;

s1004: and when determining that the dragging occurs at the current slice, the network equipment records the dragging.

Optionally, when the network device detects a dragging condition at the current slice, the network device may determine the slice sequence number of the current slice and the slice sequence number of the next slice according to the slice index file, that is, determine the slice sequence number of the current slice and the slice sequence number of the next slice of the current slice. Generally, the slice number of the consecutive slices is an arithmetic progression with a tolerance of 1, so if the network device determines that the difference between the slice number of the next slice and the current slice is greater than 1, it may determine that there is a drag at the current slice. Of course, in this embodiment, the case that the slice serial number of each slice in the slice video is an arithmetic difference series whose tolerance is greater than 1 is not excluded, and in these cases, if the network device determines that the difference between the slice serial numbers of the next slice and the current slice is greater than the corresponding tolerance, it may also be determined that there is dragging at the current slice.

In this embodiment, when the network device recognizes pause, stuck, or dragging, the pause, stuck, and dragging are recorded, and optionally, the network device may directly record in the fact table. In an example, the network device may add a column to each of the fact table for the three cases of katon, pause, and drag, for example, the column added for katon is column x, and in the column x, the network device may record whether there is a katon on the slice corresponding to each row. For example, the network device indicates the presence of a stuck at "0" and indicates the absence of a stuck at "1". Similar is true for pause and drag recording. In another example of the embodiment, the network device may also add a column to the fact table for recording three cases of stuck, paused and dragged, for example, the network device represents stuck with "1", pauses with "2", and drags with "3". For the normal case, recording can be done with "0" or null.

In the method for identifying the stuck video in the slice video provided by this embodiment, the network device can not only identify the stuck video in the playing process of the slice video, but also distinguish pause and dragging. For the recognition of pause and dragging, on one hand, the method can help determine the initial slicing and service continuous process in the process of pause recognition, increase the accuracy of pause recognition, and simultaneously, can more comprehensively understand the operation of a user in the process of playing the slicing video and help the slicing video resource provider to understand the preference of the user to the video resource.

Example four:

the present embodiment will continue to explain the slice video stuck identification method in the foregoing embodiment with reference to specific examples:

at present, video services mostly use a slicing protocol, such as a common HLS (HTTP Live Streaming) protocol, an MPEG-DASH (Dynamic Adaptive Streaming over HTTP, which may also be abbreviated as DASH) protocol, and a playing process of a sliced video is as follows approximately: the client downloads the slice index file of the video (for example, the slice index file of the HLS protocol is a file in the M3U8 format), and then sequentially pulls a TS (Transport Stream) slice, a M4S (Myst IV) slice, or an MP4(Moving Picture Experts Group 4) slice according to the slice download address in the slice index file for playing.

The following describes a specific analysis flow of the slice video stuck by taking a slice video stuck identification scene using the HLS protocol as an example.

(1) The network equipment collects signaling data of an s1-u interface on a core network link.

(2) And the network equipment analyzes the HTTP-GET request to acquire a slice index file and slice downloading information.

When the slice video is played by adopting the HLS protocol, the slice index file is an M3U8 index file. M3U8 is a file format, and in HLS protocol, an M3U8 index file can be understood as a play reference for playing a playlist slice video, and the file contains download links of all slice files in addition to some basic parameter information of slices (such as slice serial number, slice file size, slice duration, etc.). The following shows part of the content in an M3U8 index file:

#EXTM3U

#EXT-X-VERSION:3

#EXT-X-TARGETDURATION:11

#EXT-X-MEDIA-SEQUENCE:0

#EXT-MGTV-VIDEO-WIDTH:1280

#EXT-MGTV-VIDEO-HEIGHT:720

#EXT-MGTV-File-SIZE:993204

#EXTINF:5.080000,

2C0CA6524020671105BE4B27F631066E_0_5080_1564_v02_mp4.tspm＝8oQlzbMQgdBTiO1NJFz～d8Xg～Grcdv～6Iy9kmnppyCYbGactIHELL34EbK1zWv530BaO_TDQQNeYLRLOKsOmmxy6XsXBxvgpad6ZUp_nbDhhpGdoaUpaME3BJhESI2GKHLnpqQyC6sv36a3_eejzdvZldC_o8Tgh8～wVwA7ks3q65OoN3ITeR9F6TiSH0ISW_B1nF0O7Ex9MJQamPXCanhUniiNwtDE9PNujMpfcoFguGFUITiXLmN7oEmmMaxhBU3Gf1ACM～ODA0RyB

wherein "EXT-X-VERSION" indicates an indexed VERSION;

"EXT-X-TARGETDURATION" indicates the maximum media segment time length;

"EXT-X-MEDIA-SEQUENCE" indicates the slice number of the first slice in the slice index file;

"EXT-MGTV-VIDEO-WIDTH" indicates the WIDTH of the sliced VIDEO pictures;

"EXT-MGTV-VIDEO-HEIGHT" indicates the HEIGHT of the slice VIDEO picture;

"EXT-MGTV-File-SIZE" indicates the SIZE of the slice;

"EXTINF" indicates the slice length;

"2C 0CA6524020671105BE4B27F631066E _0_5080_1564_ v02_ mp4.tspm ═ 8 oQlzbMQgdBDTiO 1 NJFz-d 8 Xg-Grcdv-6 Iy9 kmnpyCybGactIHELL 34EbK1zWv530BaO _ TDQNeYLLOKOmmxy 6XsXBxvgpad6ZUp _ nbdhDOaUpME 3 BJhEISI 2 GKHLnqyC 6sv36a3_ eejzvZldC _ O8T 8-wVwA 7 gh ks3q65OoN3ITeR9F6TiSH0ISW _ B1nF0O7Ex9 QamCanhNhUniwPfPfPfPfPfM 7-mGFMfM 1-mACXLGA is a slice.

In order to obtain information such as slice duration and file size of each slice, an M3U8 index file needs to be restored by using a payload message in a corresponding GET flow, and required information needs to be extracted. In some examples of this embodiment, the information that needs to be extracted is as follows:

ext _ id: an index ID;

ext _ uri: a slice download link;

ext _ inf: slicing time length;

ext _ file _ size: a slice file size;

ext _ no: and the slicing serial number is 0 by sequentially sequencing the slicing files from top to bottom.

After the information in the M3U8 index file is extracted, the information extracted from the M3U8 index file is stored with the slice as granularity, that is, each slice link corresponds to one row, and a generated dimension table takes ext _ id as a unique main key.

The following describes the process of acquiring slice download information:

in the HLS protocol, a common video slice file is a TS slice. Although other formats, such as MP4 format, may be used in practice. In the present embodiment, the format of the slice is not limited.

For slice download information, key information of a GET process thereof needs to be acquired, for example:

and (b) time: GET process start time;

and (t) initial: time of HTTP response code return;

and t at the end: time of the last HTTP download sub-package of the GET process;

uri: a uniform resource identifier;

host: a host name;

ip _ length: the sum of the IP layer byte lengths of all messages in the GET flow.

After the network device obtains the slice index file and the slice download information, the slice index file may be stored in the hadoop cluster in the form of a dimension table, and the slice download information may be stored in the form of a fact table (also called a manifest table).

(3) And the network equipment associates the slice index file in the dimension table with the slice downloading information in the fact table.

(4) The network device performs the calculation of the following basic parameters:

ext _ avg _ rate: the network device accumulates the slice duration and the slice file size of all slices in the M3U8 index file to obtain the total file size and the total duration of the video, so that an average rate, i.e., the desired download speed, can be obtained by using the total file size/total duration.

ext _ rate: and the single-slice downloading speed is calculated according to the ip _ length, the beginning t and the end t in the slice downloading information.

ext _ time: the theoretical accumulated playing time length and the total length of each slice in the service continuity process, that is, the total length of each slice from the initial slice to the slice before the current slice (including the previous slice). The default of the initial slice is the first slice of the slice index file, but if the slice is stuck, paused or dragged, the first slice after stuck/paused/dragged is changed, that is, after the stuck, paused or dragged occurs, the business continuity process is determined again.

ext _ time _ rel: actual playing time, difference between current slice and initial slice btime.

(5) The network device identifies the stuck, suspended and dragged based on the calculated basic parameters.

For recognition of pauses: and if the time difference between the request time of the next slice and the request time of the current slice is greater than ext _ inf of the current slice, and the ext _ rate of each slice in the service continuous process is greater than ext _ avg _ rate, recording that the pause occurs once at the current slice.

For the identification of dragging: and if the difference value of the serial numbers of the slices between the next slice and the current slice is greater than 1, recording that the current slice is dragged once.

For identification of katton: if ext _ time _ rel > ext _ time and the ext _ rate of at least one slice in each slice in the service continuity process is less than the ext _ avg _ rate, recording that the current slice is stuck once.

Compared with the related technology, the slice video stuck identification method provided by the embodiment does not depend on complex factors such as client cache, video resolution, code rate and the like, combines technologies such as protocol analysis, data cleaning and the like, solves the difficulty of video analysis, and improves the accuracy of video stuck identification.

Example five:

the present embodiment provides a storage medium, in which one or more computer programs that can be read, compiled and executed by one or more processors are stored, and in the present embodiment, the storage medium may store a slice video stuck identification program, and the slice video stuck identification program can be used by one or more processors to execute a process for implementing any one of the slice video stuck identification methods described in the foregoing embodiments.

The present embodiment further provides a network device, as shown in fig. 11: the network device 11 includes a processor 111, a memory 112, and a communication bus 113 for connecting the processor 111 and the memory 112, wherein the memory 112 may be the aforementioned storage medium storing the slice video cassette identification program. The processor 111 may read the slice video stuck identification program, compile and execute the flow implementing the slice video stuck identification method described in the foregoing embodiment:

the processor 111 of the network device 11 acquires signaling data on a link of the core network, and then acquires a slice index file and slice download information associated with the slice index file according to the signaling data. Then, the processor 111 identifies the pause in the playing process of the slice video according to the slice index file and the slice download information.

When the processor 111 acquires the slice index file and the slice download information associated with the slice index file according to the signaling data, it may acquire the slice index file according to the signaling data and acquire the slice download information according to the signaling data. Then, the processor 111 determines the association relationship between the acquired slice index file and the slice download information according to the URI in the slice index file and the download address corresponding to the slice download information.

The processor 111 acquires the slice index file according to the signaling data, acquires the slice download information according to the signaling data, stores the acquired slice index file in the dimension table, stores the acquired slice download information in the fact table, and after the processor 111 determines the association correspondence between the acquired slice index file and the slice download information according to the URI in the slice index file and the download address corresponding to the slice download information, the processor 111 may also fill the information of the slice index file in the dimension table into the fact table according to the association correspondence with the granularity of the slice.

In some examples of the embodiment, the signaling data includes an HTTP-GET request, and when the processor 111 obtains the slice index file according to the signaling data, it may first identify a download request of the slice index file in the HTTP-GET request, then parse payload data of the download request of the slice index file, and then restore the slice index file according to a result of the parsing.

In another example of the embodiment, when the processor 111 obtains the slice download information according to the signaling data, it may identify the slice download request in the HTTP-GET request, and then parse the header parameter of the slice download request to obtain the slice download information.

In some examples of the embodiment, when the processor 111 identifies a pause in the playing process of the slice video according to the slice index file and the slice download information, it may detect a pause condition at the current slice according to the slice index file and the slice download information, where the current slice is a current detection object; and when the stop exists at the current slice, identifying the stop as pause according to the slice index file and the slice downloading information, and then recording the play of the current slice as pause.

When the processor 111 detects the pause condition of the current slice according to the slice index file and the slice downloading information, the processor 111 may determine the theoretical accumulated playing time of the current service continuous process according to the slice time of each slice in the slice index file, and determine the actual accumulated playing time of the service continuous process according to the request time of each slice in the slice downloading information for requesting downloading; the business continuous process is a process that the sequence number of the slices and the playing time are continuous when the slices are played; the theoretical accumulated playing time is the sum of the slice time of each slice played in the service continuous process, the actual accumulated playing time is the time difference between the request time of the current slice and the request time of the initial slice, and the initial slice is the first slice played in the service continuous process. If the actual accumulated playing time is longer than the theoretical accumulated playing time, the processor 111 determines that a pause occurs at the current slice.

Optionally, when the pause is identified as pause according to the slice index file and the slice downloading information, the processor 111 determines an expected downloading speed of each slice according to the size of each slice in the slice index file and the slice duration of each slice, and determines an actual single-slice downloading speed of each slice in the current service continuous process according to the slice downloading information, wherein the service continuous process is a process in which the serial number of the slice and the playing time are continuous when the slice is played; the desired download speed is a ratio of the sum of file sizes of all slices corresponding to the slice index file to the sum of slice durations. If the single-slice download speed of at least one slice in the business continuity process is lower than the expected download speed, the processor 111 determines that the pause existing at the current slice is stuck.

In some examples of this embodiment, when the processor 111 determines the actual single-slice downloading speed of each slice in the service continuity process according to the slice downloading information, for each slice in the service continuity process, the sum of the IP layer byte lengths of all messages in the slice downloading flow is determined according to the slice downloading information corresponding to the slice, the flow time spent in the slice downloading flow is determined, and then the ratio of the sum of the IP layer byte lengths of all messages to the flow time is determined as the single-slice downloading speed of the slice.

Alternatively, the processor 111 may determine a time when the first data packet in the slice downloading flow returns as an initial packet return time, and determine a time when the last data packet in the slice downloading flow returns as an end packet return time. The processor 111 then determines the time difference between the last packet return time and the first packet return time as the flow time taken for the slice download flow.

After detecting the pause condition at the current slice according to the slice index file and the slice download information, the processor 111 may further identify that the pause is a pause according to the slice index file and the slice download information when determining that the pause exists at the current slice, and record the pause at the current slice.

When the pause is identified as the pause according to the slice index file and the slice downloading information, the processor 111 may determine an expected downloading speed of each slice according to the size of each slice in the slice index file and the slice duration of each slice, and determine an actual single-slice downloading speed of each slice in the current service continuous process according to the slice downloading information, where the service continuous process is a process in which the serial number of the slice and the playing time are continuous when the slice is played. If the single-slice download speed of all slices in the service continuity process is greater than the expected download speed, the processor 111 determines that a pause occurs at the current slice.

When the processor 111 detects the pause condition of the current slice according to the slice index file and the slice download information, the request time of the current slice and the request time of the next slice may be determined according to the request time of each slice requesting download in the slice download information, and the slice time of the current slice is determined according to the slice time of each slice in the slice index file, where the next slice is a slice subsequent to the current slice. The processor 111 then determines the time difference between the request time of the next slice and the request time of the current slice, and determines that a pause occurs at the current slice if the time difference is greater than the slice duration of the current slice.

In some examples, the processor 111 may further detect a dragging situation at the current slice from the slice index file, and record the dragging when it is determined that the dragging occurs at the current slice.

For example, the processor 111 determines the slice number of the current slice and the slice number of the next slice from the slice index file, where the next slice is a slice subsequent to the current slice. And if the difference value of the serial numbers of the slices between the next slice and the current slice is greater than 1, judging that dragging exists at the current slice.

The network device provided by this embodiment, when evaluating a slice video service, not only can acquire the download status of a single slice according to the slice download information, but also because the network device obtains a slice index file through the collected signaling data, and the slice index file corresponds to a plurality of or even all slices in a video at the same time, the smoothness of download and play of a plurality of slices in the slice video service can be embodied by using the slice index file in combination with the download information of each slice corresponding to the slice index file, and simultaneously, because the play of each slice in the slice index file is sequentially played one by one under normal conditions, the relationship between the download and play process of one slice in the slice index file and the download and play process of another slice in the slice index file can be determined by using the combination of the slice index file and the slice download information, thereby identifying the slice-to-slice stuck. Therefore, the network device in the embodiment can accurately identify the pause in the slicing video service process, so that the evaluation result is more in line with the real experience of the user, and a basis is provided for the subsequent slicing video service improvement.

It will be apparent to those skilled in the art that all or some of the steps of the methods, systems, functional modules/units in the devices disclosed above may be implemented as software (which may be implemented in program code executable by a computing device), firmware, hardware, and suitable combinations thereof. In a hardware implementation, the division between functional modules/units mentioned in the above description does not necessarily correspond to the division of physical components; for example, one physical component may have multiple functions, or one function or step may be performed by several physical components in cooperation. Some or all of the physical components may be implemented as software executed by a processor, such as a central processing unit, digital signal processor, or microprocessor, or as hardware, or as an integrated circuit, such as an application specific integrated circuit. Such software may be distributed over computer-readable media, which may include computer storage media (or non-transitory media) and communication media (or transitory media), executed by a computing device, and in some cases may perform the steps shown or described in a different order than here. The term computer storage media includes volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules or other data, as is well known to those of ordinary skill in the art. Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, Digital Versatile Disks (DVD) or other optical disk storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can be accessed by a computer. In addition, communication media typically embodies computer readable instructions, data structures, program modules or other data in a modulated data signal such as a carrier wave or other transport mechanism and includes any information delivery media as known to those skilled in the art. Thus, the present invention is not limited to any specific combination of hardware and software.

The foregoing is a more detailed description of embodiments of the present invention, and the present invention is not to be considered limited to such descriptions. For those skilled in the art to which the invention pertains, several simple deductions or substitutions can be made without departing from the spirit of the invention, and all shall be considered as belonging to the protection scope of the invention.

Claims

1. A slice video stuck identification method comprises the following steps:

acquiring signaling data on a core network link;

2. The slice video katon identification method of claim 1, wherein said obtaining a slice index file and slice download information associated with the slice index file from the signaling data comprises:

acquiring a slice index file according to the signaling data, and acquiring slice downloading information according to the signaling data;

and determining the association corresponding relation between the acquired slice index file and the slice downloading information according to the uniform resource identifier URI in the slice index file and the downloading address corresponding to the slice downloading information.

3. The slice video katon identification method of claim 2, wherein after obtaining the slice index file according to the signaling data and obtaining the slice download information according to the signaling data, further comprising:

storing the acquired slice index file in a dimension table, and storing the acquired slice downloading information in a fact table;

after determining the association corresponding relationship between the acquired slice index file and the slice download information according to the uniform resource identifier URI in the slice index file and the download address corresponding to the slice download information, the method further comprises the following steps:

and filling the information of the slice index file in the dimension table into the fact table according to the association corresponding relation by taking the slice as granularity.

4. The slice video katon recognition method of claim 2, wherein the signaling data comprises an HTTP-GET request, and obtaining the slice index file from the signaling data comprises:

identifying a slice index file download request in the HTTP-GET request;

analyzing the effective load data of the downloading request of the slice index file;

and restoring the slice index file according to the analysis result.

5. The slice video katon recognition method of claim 2, wherein the signaling data comprises an HTTP-GET request, and obtaining slice download information from the signaling data comprises:

identifying a slice download request in the HTTP-GET request;

and analyzing the head parameters of the slice downloading request to obtain slice downloading information.

6. The method for identifying the video morton of the slice according to any one of claims 1 to 5, wherein the identifying the video morton during playing of the slice according to the slice index file and the slice download information comprises:

detecting the pause condition of the current slice according to the slice index file and the slice downloading information, wherein the current slice is a current detection object;

when the current slice is determined to have pause, identifying the pause as pause according to the slice index file and the slice downloading information;

and recording the playing of the current slice to be chutten.

7. The slice video katon identification method of claim 6, wherein the detecting a pause condition at a current slice according to the slice index file and the slice download information comprises:

determining the theoretical accumulated playing time of the current service continuous process according to the slice time of each slice in the slice index file, and determining the actual accumulated playing time of the service continuous process according to the request moment of each slice requesting downloading in the slice downloading information; the business continuous process is a process that the serial number of the slices and the playing time are continuous when the slices are played; the theoretical accumulated playing time is the sum of the slice time of each slice played in the service continuous process, the actual accumulated playing time is the time difference between the request time of the current slice and the request time of the initial slice, and the initial slice is the first slice played in the service continuous process;

and if the actual accumulated playing time length is longer than the theoretical accumulated playing time length, determining that the current slice is stopped.

8. The slice video katon identification method of claim 6, wherein said identifying the pause as katon based on the slice index file and the slice download information comprises:

determining an expected downloading speed of each slice according to the size of each slice in the slice index file and the slice duration of each slice, and determining an actual single-slice downloading speed of each slice in the current service continuous process according to the slice downloading information, wherein the service continuous process is a process in which the serial number of the slices and the playing time are continuous when the slices are played; the expected downloading speed is the ratio of the sum of the file sizes of all the slices corresponding to the slice index file to the sum of the slice duration;

and if the single-slice downloading speed of at least one slice in the service continuous process is lower than the expected downloading speed, judging that the pause existing at the current slice is pause.

9. The slice video katon recognition method of claim 8, wherein said determining an actual single-slice download speed for each slice in the service continuity process based on the slice download information comprises:

for each slice in the service continuous process, determining the sum of the IP layer byte lengths of all messages in the slice downloading process according to the slice downloading information corresponding to the slice, and determining the process time spent by the slice downloading process;

and determining the ratio of the sum of the IP layer byte lengths of all the messages to the flow time as the single slice downloading speed of the slice.

10. The slice video katon recognition method of claim 9, wherein said determining the flow time taken for the slice download flow comprises:

determining the time when the first data packet in the slice downloading flow returns as the initial packet returning time, and determining the time when the last data packet in the slice downloading flow returns as the final packet returning time;

and determining the time difference between the return time of the last packet and the return time of the first packet as the process time spent by the slice downloading process.

11. The slice video morton identification method according to claim 6, wherein after detecting the pause condition at the current slice according to the slice index file and the slice download information, the method further comprises:

when it is determined that a pause exists at the current slice, identifying the pause as a pause according to the slice index file and the slice downloading information;

a pause at the current slice is recorded.

12. The slice video morton identification method according to claim 11, wherein the identifying the pause as a pause according to the slice index file and the slice download information comprises:

determining an expected downloading speed of each slice according to the size of each slice in the slice index file and the slice duration of each slice, and determining an actual single-slice downloading speed of each slice in the current service continuous process according to the slice downloading information, wherein the service continuous process is a process in which the serial number of the slices and the playing time are continuous when the slices are played;

and if the single-slice downloading speed of all slices in the service continuous process is greater than the expected downloading speed, determining that the current slice is paused.

13. The slice video morton identification method according to claim 11, wherein the detecting a pause condition at a current slice according to the slice index file and the slice download information comprises:

determining the request time of the current slice and the request time of the next slice according to the request time of each slice requesting downloading in the slice downloading information, and determining the slice duration of the current slice according to the slice duration of each slice in the slice index file, wherein the next slice is the next slice of the current slice;

determining a time difference between the request time of the next slice and the request time of the current slice;

and if the time difference is larger than the slice duration of the current slice, determining that a pause occurs at the current slice.

14. The slice video stuck identification method of claim 6, wherein the slice video stuck identification method further comprises:

detecting the dragging condition of the current slice according to the slice index file;

upon determining that a drag occurs at the current slice, recording the drag.

15. The slice video katon identification method of claim 14, wherein said detecting a drag condition at a current slice from the slice index file comprises:

determining the slice serial number of the current slice and the slice serial number of a next slice according to the slice index file, wherein the next slice is a slice next to the current slice;

and if the difference value of the serial numbers of the slices between the next slice and the current slice is greater than 1, judging that dragging exists at the current slice.

16. A network device comprising a processor, a memory, and a communication bus;

the processor is configured to execute one or more programs stored in the memory to implement the steps of the slice video stuck identification method according to any one of claims 1 to 15.

17. A storage medium storing one or more programs, the one or more programs being executable by one or more processors to implement the steps of the slice video stuck recognition method according to any one of claims 1 to 15.