CN110677443A

CN110677443A - Data transmitting and receiving method, transmitting end, receiving end, system and storage medium

Info

Publication number: CN110677443A
Application number: CN201810710535.6A
Authority: CN
Inventors: 于荣国; 柏杨; 黄毅
Original assignee: ZTE Corp
Current assignee: ZTE Corp
Priority date: 2018-07-02
Filing date: 2018-07-02
Publication date: 2020-01-10

Abstract

The embodiment of the invention discloses a data sending method, which is applied to a data sending end and comprises the following steps: acquiring a download path list of a data file to be sent; generating a text description file aiming at the data file to be sent based on the download path list of the data file to be sent; and sending a data sending instruction of the download path carrying the text description file. The embodiment of the invention also discloses a data receiving method, a data sending end, a data receiving end, a system and a computer storage medium.

Description

Data transmitting and receiving method, transmitting end, receiving end, system and storage medium

Technical Field

The present invention relates to the field of communications, and in particular, to a data transmitting and receiving method, a data transmitting end, a data receiving end, a system, and a computer storage medium.

Background

With the rapid development of communication technology and semiconductor technology, liquid crystal technology with high resolution such as 4K, 8K and the like is continuously promoted, the number of Network video users is also rapidly increased, and a Content Delivery Network (CDN) technology is rapidly popularized and has successively started to be adopted and deployed on a large scale. However, different terminal types or network conditions have different requirements on video bitrate, resolution, coding format and service protocol, so that diversification of video files is urgently required, and higher requirements are provided for the injection technology of CDN content.

A traditional CDN system generally corresponds a content identifier to a unique physical media file, specifies a download path of the file through a service content management platform, and issues the file to a CDN node through an Application Programming Interface (API). In the current CD interface Extensible Markup Language (EML) work order content injection method commonly used by the CDN in the industry, the content delivery specification can only satisfy that the same content identifier corresponds to one physical content entity, and cannot satisfy the delivery of multiple entity files corresponding to the same content identifier.

Under the requirement of the current multi-code-rate content, one content identifier can correspond to a plurality of source media files with different code rates, the code rates are different, the types of source files are also diversified, such as posters, flowers, photos and the like, the source server where each source file is located and the characteristic attributes are different, the code rate requirements are diversified, and therefore the number of the source files corresponding to the content identifier is not fixed. The traditional single-path content injection method cannot meet the requirements, but the content injection method for directly expanding multiple paths in the current interface needs to modify the whole service flow, brings great changes to the injection mechanism of each current component, has great influences on database operation, message length, release state machine control and the like of each component, is equivalent to phase change, increases development and maintenance cost, and prolongs the development period.

Disclosure of Invention

In order to solve the existing technical problems, embodiments of the present invention provide a data sending and receiving method, a data sending end, a data receiving end, a system, and a computer storage medium, which are simple to implement, have high expandability of a content injection method, and are low in development and maintenance costs.

In order to achieve the above purpose, the technical solution of the embodiment of the present invention is realized as follows:

in a first aspect, an embodiment of the present invention provides a data sending method, applied to a data sending end, including:

acquiring a download path list of a data file to be sent;

generating a text description file aiming at the data file to be sent based on the download path list of the data file to be sent;

and sending a data sending instruction of the download path carrying the text description file.

In the above scheme, the method further comprises:

receiving a data receiving result correspondingly returned in response to the data sending instruction;

and updating the data sending state of the data file to be sent into a sent data file according to the data receiving result.

In a second aspect, an embodiment of the present invention provides a data receiving method, applied to a data receiving end, including:

receiving a data sending instruction of a download path carrying a text description file, wherein the text description file carries a download path list of a data file to be sent;

downloading the text description file according to the download path of the text description file;

and executing data receiving processing on the data file to be sent based on the download path list of the data file to be sent in the text description file according to the data sending instruction.

In the above scheme, the method further comprises:

and reporting a data receiving result generated after data receiving processing is carried out on the data file to be sent.

In a third aspect, an embodiment of the present invention provides a data sending end, where the data sending end includes a processor and a memory for storing a computer program that can be run on the processor; wherein,

the processor is configured to, when running the computer program, perform the steps of the data transmission method of the first aspect.

In a fourth aspect, an embodiment of the present invention provides a data receiving end, where the data receiving end includes a processor and a memory for storing a computer program capable of running on the processor; wherein,

the processor is configured to execute the steps of the data receiving method according to the second aspect when the computer program is executed.

In a fifth aspect, an embodiment of the present invention provides a data transmission system, including the data sending end in the third aspect and the data receiving end in the fourth aspect.

In the above scheme, the data sending end includes a service content management system, the data receiving end includes a service node, and the data file to be sent is a multi-rate media file; wherein,

the data sending end acquiring a download path list of a data file to be sent comprises the following steps: the service content management system acquires a download path list of the multi-code-rate media file according to the received multi-code-rate content release plan; the data sending end generates a text description file aiming at the data file to be sent based on the download path list of the data file to be sent, and the method comprises the following steps: the service content management system generates a text description file aiming at the multi-code rate media file based on the download path list of the multi-code rate media file, uploads the text description file to a content source server and acquires the download path of the text description file; the sending of the data sending instruction of the download path carrying the text description file by the data sending end comprises: the service content management system sends a data injection instruction of a download path carrying the text description file to the service node;

the data receiving end receiving the data sending instruction of the download path carrying the text description file comprises the following steps: the service node receives a data injection instruction which is sent by the service content management system and carries a download path of the text description file; the data receiving end downloads the text description file according to the download path of the text description file, and the data receiving end downloads the text description file by the following steps: the service node downloads the text description file from a content source server according to the download path of the text description file, analyzes the text description file and obtains a download path list of the multi-rate media file; the data receiving end executes data receiving processing on the data file to be sent based on the download path list of the data file to be sent in the text description file according to the data sending instruction, and the data receiving end comprises the following steps: and the service node downloads the multi-code rate media file according to the download path list of the multi-code rate media file.

In the above scheme, the data sending end includes a service management system, the data receiving end includes a service node, and the data file to be sent includes a basic data file or a service data file; wherein,

the data sending end acquiring a download path list of a data file to be sent comprises the following steps: the service management system uploads the acquired basic data file or service data file to a content source server, and acquires a download path list of the corresponding basic data file or service data file; the data sending end generates a text description file aiming at the data file to be sent based on the download path list of the data file to be sent, and the method comprises the following steps: the service management system generates a text description file aiming at the corresponding basic data file or service data file based on the download path list; the sending of the data sending instruction of the download path carrying the text description file by the data sending end comprises: the service management system sends a data updating instruction carrying the download path of the text description file to the service node;

the data receiving end receiving the data sending instruction of the download path carrying the text description file comprises the following steps: the service node receives a data updating instruction which is sent by the service management system and carries a downloading path of the text description file; the data receiving end downloads the text description file according to the download path of the text description file, and the data receiving end downloads the text description file by the following steps: the service node downloads the text description file according to the download path of the text description file, analyzes the text description file, and acquires a download path list of the corresponding basic data file or service data file; the data receiving end executes data receiving processing on the data file to be sent based on the download path list of the data file to be sent in the text description file according to the data sending instruction, and the data receiving end comprises the following steps: and the service node downloads the corresponding basic data file or service data file from a content source server according to the corresponding download path list of the basic data file or service data file, and updates local data according to the corresponding basic data file or service data file.

In the above scheme, the data sending end includes a service node, the data receiving end includes a service management system, and the data file to be sent includes a ticket log file; wherein,

the data sending end acquiring a download path list of a data file to be sent comprises the following steps: the service node acquires a call ticket log file matched with the acquisition time period according to a received call ticket acquisition instruction carrying the acquisition time period, and acquires a download path list of the call ticket log file; the data sending end generates a text description file aiming at the data file to be sent based on the download path list of the data file to be sent, and the method comprises the following steps: the service node generates a text description file aiming at the call ticket log file based on the download path list of the call ticket log file; the sending of the data sending instruction of the download path carrying the text description file by the data sending end comprises: the service node sends a call ticket acquisition response instruction carrying the download path of the text description file to the service management system;

the data receiving end receiving the data sending instruction of the download path carrying the text description file comprises the following steps: the service management system receives a call ticket acquisition response instruction which is sent by the service node and carries the download path of the text description file; the data receiving end downloads the text description file according to the download path of the text description file, and the data receiving end downloads the text description file by the following steps: the service management system downloads the text description file according to the download path of the text description file, analyzes the text description file and acquires a download path list of a call ticket log file; the data receiving end executes data receiving processing on the data file to be sent based on the download path list of the data file to be sent in the text description file according to the data sending instruction, and the data receiving end comprises the following steps: and the service management system downloads the call ticket log file according to the download path list of the call ticket log file.

In the data sending and receiving method, the data sending end, the data receiving end, the system and the computer storage medium provided in the above embodiments, the data sending end generates a text description file according to a download path list of a data file to be sent, and sends a data sending instruction carrying a download path of the text description file to the data receiving end, and the data receiving end downloads the text description file according to the data sending instruction and performs data receiving processing on the data file to be sent based on the download path list of the data file to be sent in the text description file. Therefore, the data sending end aggregates the download path list of the data file to be sent by adopting the text description file and sends the text description file to the data receiving end, and the data receiving end can obtain the data file to be sent once according to the text description file, and can expand characteristic parameters in the text description file aiming at different entity subfiles, so that the expandability of the content injection method is improved, the data sending and receiving are realized, and the method is simple to realize and low in development and maintenance cost.

Drawings

Fig. 1 is a schematic flow chart of a data transmission method according to an embodiment of the present invention;

fig. 2 is a schematic structural diagram of a data transmitting end in an embodiment of the present invention;

fig. 3 is a schematic flow chart of a data receiving method according to another embodiment of the present invention;

fig. 4 is a schematic structural diagram of a data receiving end according to an embodiment of the present invention;

FIG. 5 is a block diagram of a data transmission system according to an embodiment of the present invention;

fig. 6 is a schematic diagram illustrating a detailed flow of a multi-rate content injection method in an alternative embodiment of the present invention;

FIG. 7 is a flowchart illustrating a data update method according to another alternative embodiment of the present invention;

fig. 8 is a schematic flow chart of a call ticket log collection method in another alternative embodiment of the present invention;

fig. 9 is a schematic structural diagram of a data receiving end and a data transmitting end in another embodiment of the present invention.

Detailed Description

The technical scheme of the invention is further elaborated by combining the drawings and the specific embodiments in the specification. Unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this invention belongs. The terminology used in the description of the invention herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the invention. As used herein, the term "and/or" includes any and all combinations of one or more of the associated listed items.

Referring to fig. 1, a data sending method provided in the embodiment of the present invention is applicable to a data sending end, and includes the following steps:

step S101: acquiring a download path list of a data file to be sent;

specifically, the data sending end obtains a download path list of a data file to be sent.

It should be noted that the data file to be sent includes multiple data files corresponding to the same content identifier, which may also be referred to as entity subfiles, and each data file corresponds to one download path. The data file to be sent can be a multi-rate media file, a basic data file, a service data file, a call ticket log file or the like. Taking the to-be-sent data file as an example of a multi-bitrate media file, assuming that, for a movie "a and B", a video file with bitrate of 720P and a corresponding download path thereof, and a video file with bitrate of 1080P and a corresponding download path thereof exist, the video file with bitrate of 720P and the video file with bitrate of 1080P may constitute the to-be-sent data file with rate of a and B as content identifiers, and the download path of the video file with bitrate of 720P and the download path of the video file with bitrate of 1080P may constitute the download path list.

Here, the data sending end acquires the download path list of the data file to be sent, where the data sending end directly receives a data sending instruction carrying the download path list of the data file to be sent, which is sent by a content provider, or the data sending end acquires the download path list of the data file to be sent according to a received data acquisition instruction, or the data sending end uploads the data file to be sent to a third-party server, so as to acquire the download path list of the data file to be sent. The data sending end can be different according to different data to be sent, for example, the data sending end is a multi-rate media file and is a service content management system; aiming at the data to be sent as a basic data file or a service data file, a data sending end is a service management system; and aiming at the condition that the data to be sent is a call ticket log file, the data sending end is a service node.

Step S102: generating a text description file aiming at the data file to be sent based on the download path list of the data file to be sent;

specifically, the data sending end generates a text description file for the data file to be sent according to the set data assembling format based on the download path list of the data file to be sent acquired in step S101.

Here, the generating of the text description file for the data file to be sent according to the set data assembling format may be understood as describing and representing a download path list of the data file to be sent according to the set data assembling format, so as to assemble a corresponding text description file. The data splicing format may be set according to actual needs, and in this embodiment, a JavaScript Object Notation (JSON, JavaScript Object notification) is used to describe and represent the download path list of the data file to be sent, and a JSON description file is correspondingly spliced as an example. It should be noted that characteristic parameters such as the size of the data file to be transmitted, the encryption algorithm and the encoding format used in the data file to be transmitted may also be inserted into the text description file.

Step S103: and sending a data sending instruction of the download path carrying the text description file.

Specifically, the data sending end sends a data sending instruction carrying the download path of the text description file to the data receiving end, so that the data receiving end performs data receiving processing according to the data sending instruction.

Here, the download path of the text description file may be determined by the data transmitting end according to a storage location of the text description file. In an alternative embodiment, step S103: before sending the data sending instruction of the download path carrying the text description file, the method further includes: and uploading the text description file to a third-party server, and acquiring a download path of the text description file. It can be understood that, when the data sending end uploads the text description file to the third-party server, the third-party server allocates a storage location to the text description file, and for the data sending end, the storage location is a download path corresponding to the text description file. Taking the data to be sent as a multi-rate media file as an example, the third-party server may be a content source server.

It should be noted that the data sending instruction may be sent to the data sending end by a content provider, or may be set by the data sending end according to an actual need and according to a preset format, for example, when the data sending end determines that the data sending state of the data file C is a data file to be sent, the data sending instruction for the data file C is generated according to the preset format. The data sending instruction may be a data injection instruction, a data update instruction, or the like, where the data injection instruction is used to instruct a data receiving end to download the data file to be sent according to the download path list of the data file to be sent; and the data updating instruction is used for indicating a data receiving end to download the data file to be sent according to the download path list of the data file to be sent and updating local data according to the downloaded data file to be sent.

In summary, in the data sending method provided in the above embodiment, the data sending end aggregates the download path list of the data file to be sent by using the text description file, and sends the data sending instruction carrying the text description file to the data receiving end, so that the issue of multiple data files corresponding to the same content identifier is realized, and the feature parameters can be extended in the text description file for different entity subfiles, thereby improving the scalability of the content injection method, and the implementation is simple, and the development and maintenance costs are low.

In an optional embodiment, the data sending method further includes:

Specifically, the data sending end receives a data receiving result correspondingly returned by the data receiving end in response to the data sending instruction, and updates the data sending state of the data file to be sent to the sent data file according to the data receiving result.

Here, the data receiving result may indicate whether reception of part or all of the data files to be transmitted is successful or failed, the reception success may be synchronization success, and the reception failure may be synchronization failure, and accordingly, updating the data transmission status of the data files to be transmitted according to the data receiving result includes: when all the data files in the data files to be sent are determined to be successfully received, updating the data sending state of the data files to be sent into sent data files; and when determining that all the data files in the data files to be transmitted are not successfully received, taking the data files which are not successfully processed as the data files to be transmitted, and returning to execute the step S101 to continue to execute data transmission operation on the data files which are not successfully processed.

Therefore, according to the received data receiving result of the data file to be sent, the data sending state of the data file to be sent is updated in time, and the data sending operation is executed again on the data file with failed processing, so that repeated processing of the data file to be sent caused by untimely updating of the data sending state can be effectively avoided.

In order to implement the foregoing method, an embodiment of the present invention further provides a data sending end, as shown in fig. 2, including: the device comprises an acquisition module 10, a first processing module 11 and a sending module 12; wherein,

the acquiring module 10 is configured to acquire a download path list of a data file to be sent;

the first processing module 11 is configured to generate a text description file for the data file to be sent based on the download path list of the data file to be sent;

the sending module 12 is configured to send a data sending instruction of a download path carrying the text description file.

In summary, in the data sending end provided in the above embodiment, the download path list of the data file to be sent is aggregated by using the text description file, and a data sending instruction carrying the text description file is sent to the data receiving end, so that the issue of multiple data files corresponding to the same content identifier is realized, and the feature parameters can be extended in the text description file for different entity subfiles, thereby improving the extensibility of the content injection method, which is not only simple to implement, but also low in development and maintenance costs.

In an optional embodiment, the data sending end may further include: a first receiving module 13; wherein,

the first receiving module 13 is configured to receive a data receiving result correspondingly returned in response to the data sending instruction;

the first processing module 11 is further configured to update the data sending status of the data file to be sent to be a sent data file according to the data receiving result.

Therefore, the data sending state of the data file to be sent is updated in time according to the received data receiving result of the data file to be sent, and the data sending operation is executed again on the data file which fails to be received, so that the repeated processing of the data file to be sent caused by the untimely updating of the data sending state can be effectively avoided.

Referring to fig. 3, another data receiving method provided in the embodiment of the present invention is applicable to a data receiving end, and includes the following steps:

step S201: receiving a data sending instruction of a download path carrying a text description file, wherein the text description file carries a download path list of a data file to be sent;

specifically, the data receiving end receives a data sending instruction of a download path carrying a text description file sent by the data sending end, where the text description file carries a download path list of a data file to be sent.

Here, the data sending instruction may be a data injection instruction, a data update instruction, or the like, where the data injection instruction is used to instruct a data receiving end to download the data file to be sent according to the download path list of the data file to be sent; and the data updating instruction is used for indicating a data receiving end to download the data file to be sent according to the download path list of the data file to be sent and updating local data according to the downloaded data file to be sent. The data receiving end can be different according to different data to be sent, for example, the data receiving end is a service node for a multi-rate media file of the data to be sent; aiming at the data to be sent as a basic data file or a service data file, a data receiving end is a service node; and aiming at the condition that the data to be sent is a call ticket log file, a data receiving end is a service management system. The data file to be sent comprises a plurality of data files corresponding to the same content identifier, and each data file corresponds to one download path. The data file to be sent can be a multi-rate media file, a basic data file, a service data file, a call ticket log file or the like.

Step S202: downloading the text description file according to the download path of the text description file;

specifically, the data receiving end extracts the download path of the text description file carried in the data sending instruction according to the data sending instruction received in step S201, and downloads the text description file according to the download path of the text description file.

For example, if the text description file is stored in the third-party server, the data receiving end sends a download request carrying a download path of the text description file to the third-party server, and receives the text description file returned by the third-party server after the third-party server successfully responds to the download request, so that the text description file is downloaded according to the download path of the text description file.

Step S203: and executing data receiving processing on the data file to be sent based on the download path list of the data file to be sent in the text description file according to the data sending instruction.

Specifically, the data receiving end firstly parses the text description file acquired in step S202 according to the set data parsing format to obtain a download path list of the data file to be sent carried in the text description file, and then executes data receiving processing on the data file to be sent according to the data sending instruction acquired in step S201 and based on the download path list of the data file to be sent.

It can be understood that, when the data sending instruction is a data injection instruction, the executing data receiving processing on the data file to be sent according to the data sending instruction acquired in step S201 and based on the download path list of the data file to be sent includes: and the data receiving terminal downloads the data file to be sent according to the download path list of the data file to be sent, so that the data injection of the data receiving terminal is realized. When the data sending instruction is a data updating instruction, the executing data receiving processing on the data file to be sent according to the data sending instruction obtained in step S201 and based on the download path list of the data file to be sent includes: and the data receiving terminal downloads the data file to be sent according to the download path list of the data file to be sent, and updates local data according to the downloaded data file to be sent, so that the data updating of the data receiving terminal is realized.

It should be noted that the data parsing format used by the data receiving end for parsing the text description file matches with the data assembling format used by the data sending end for generating the text description file. When the data file to be sent is a multi-rate media file, the data receiving end converts the multi-rate media file into a content distribution network media file storage format after downloading the multi-rate media file, thereby providing media service for the terminal.

In summary, in the data receiving method provided in the above embodiment, after the data receiving end obtains the download path list of the data file to be sent by using text description file aggregation, the data receiving end performs data receiving processing on the data file to be sent according to the data sending instruction, that is, data receiving of multiple entity data files corresponding to the same content identifier is achieved at the same time, which is not only simple to implement, but also low in development and maintenance costs.

In an optional embodiment, the method may further include:

Specifically, after the data receiving end performs data receiving processing on the data file to be sent, the data receiving end reports a data receiving result to the data sending end, so as to inform the data sending end of the data receiving state of the data receiving end.

Here, the data receiving result may indicate whether receiving of part or all of the data files to be sent is successful or failed, for example, the receiving status of each data file in the data files to be sent is reported in sequence, or the receiving statuses of all the data files in the data files to be sent are reported simultaneously.

Therefore, by reporting the data receiving result generated after the data receiving processing is performed on the data file to be sent in time, the repeated processing of the data file to be sent due to untimely reporting is avoided.

In order to implement the foregoing method, an embodiment of the present invention further provides a data receiving end, as shown in fig. 4, including: a second receiving module 20, a downloading module 21 and a second processing module 22; wherein,

a second receiving module 20, configured to receive a data sending instruction of a download path carrying a text description file, where the text description file carries a download path list of a data file to be sent;

the downloading module 21 is configured to download the text description file according to a downloading path of the text description file;

the second processing module 22 is configured to perform data receiving processing on the data file to be sent based on the download path list of the data file to be sent in the text description file according to the data sending instruction.

In summary, in the data receiving end provided in the above embodiment, after the download path list of the data file to be sent, which is obtained by aggregating the text description files, is obtained, data receiving processing is performed on the data file to be sent according to the data sending instruction, that is, data receiving of multiple entity data files corresponding to the same content identifier is achieved at the same time, which is not only simple to implement, but also low in development and maintenance costs.

In an optional embodiment, the data receiving end may further include: a reporting module 23, configured to report a data receiving result generated after data processing is performed on the data file to be sent.

The embodiment of the invention provides a data transmission system, which comprises a data sending end and a data receiving end, wherein the data sending end and the data receiving end are arranged in any embodiment of the invention; wherein,

the data sending terminal is used for acquiring a download path list of a data file to be sent; generating a text description file aiming at the data file to be sent based on the download path list of the data file to be sent; and sending a data sending instruction carrying the download path of the text description file to the data receiving end;

the data receiving end is used for receiving a data sending instruction of a download path carrying a text description file, wherein the text description file carries a download path list of a data file to be sent; downloading the text description file according to the download path of the text description file; and executing data receiving processing on the data file to be sent based on the download path list of the data file to be sent in the text description file according to the data sending instruction.

In the data transmission system provided in the above embodiment, the data sending end aggregates the download path list of the data file to be sent by using the text description file, and sends the text description file to the data receiving end, and the data receiving end can obtain the data file to be sent once according to the text description file, and can expand the characteristic parameters in the text description file for different entity subfiles, thereby improving the expandability of the content injection method, and realizing data sending and receiving, which is not only simple to implement, but also low in development and maintenance costs.

In an alternative embodiment of the method according to the invention,

the data receiving end is further configured to report a data receiving result generated after data receiving processing is performed on the data file to be sent to the data sending end;

the data sending end is further configured to receive a data receiving result, sent by the data receiving end, corresponding to the response to the data sending instruction; and updating the data sending state of the data file to be sent into a sent data file according to the data receiving result.

Therefore, the data receiving end reports the data receiving result generated after the data receiving processing is performed on the data file to be sent in time, and the data sending end updates the data sending state of the data file to be sent in time according to the data receiving result, so that the repeated processing of the data file to be sent caused by the untimely updating of the data sending state can be effectively avoided.

In an optional embodiment, the data sending end includes a service content management system, the data receiving end includes a service node, and the data file to be sent is a multi-rate media file; wherein,

the service content management system is specifically configured to: acquiring a download path list of the multi-code-rate media file according to the received multi-code-rate content release plan; generating a text description file aiming at the multi-code rate media file based on the download path list of the multi-code rate media file, uploading the text description file to a content source server, and acquiring a download path of the text description file; sending a data injection instruction of a download path carrying the text description file to the service node;

the service node is specifically configured to: receiving a data injection instruction carrying a download path of the text description file and sent by the service content management system; downloading the text description file from a content source server according to the download path of the text description file, analyzing the text description file, and acquiring a download path list of the multi-rate media file; and downloading the multi-code rate media file according to the download path list of the multi-code rate media file.

The following describes the embodiments of the present invention in further detail by using specific examples, where the data injection instruction is a content injection message, and the service node is a CDN service node. Referring to fig. 5, a data transmission system provided for the embodiment of the present invention includes: a service Content Management System (CMS), a Content Management system (CDNM), a Content delivery network service Management system (CDN Manager), and a CDN service NODE (labeled NODE); wherein,

CMS: receiving a content issuing plan of a content provider, and issuing a content injection, deletion or update instruction aiming at the multi-rate media file to the CDNM through a standard API (application program interface);

CDNM: receiving a content injection, deletion or update instruction for the multi-rate media file sent by the CMS, extracting service information required by the CDN, selecting a NODE corresponding to the service, and sending a content injection message containing the content injection instruction of the multi-rate media file to the NODE through an internal API (application program interface) of the CDN.

NODE: and receiving a content injection message issued by the CDNM, downloading the multi-rate media file, converting the multi-rate media file into a CDN media file storage format, and providing media service to the outside.

The specific principle is as follows: after receiving a content release plan for the multi-rate media file sent by a content provider, the CMS extracts storage information of the multi-rate media file, that is, a download path; generating a text description file corresponding to a download path list of the multi-rate media file according to the physical content identification, wherein the content list in the text description file is a complete download path (such as ftp, http, https and other paths) of each media file, and the data assembling format of the text description file is consistent with the analysis mode of NODE; the CMS uploads the generated text description file to a specified download server, and then transmits a content injection message carrying a download path of the text description file to the CDNM through a standard content injection API interface.

After receiving the content injection message of the CMS, the CDNM extracts content delivery information required by the CDN, selects a NODE corresponding to a service and generates a CDN content delivery task; then, the CDNM sends the content injection message carrying the download path of the text description file to the NODE through a private API interface inside the CDN.

And after receiving the content injection message of the CDNM, the NODE downloads and analyzes the text description file according to the download path of the text description file, keeps the download path list of the multi-rate media file in a local memory, and then downloads the multi-rate media file one by one. And converting the coding mode and the code rate information of the multi-code rate media file into a CDN media file storage format. After all the multi-rate media files are released, reporting the release result to the CDNM and providing media service to various terminals.

As shown in fig. 6, still taking the case that the data sending end includes a service content management system CMS, the data receiving end includes a service NODE, and the data file to be sent is a multi-rate media file, the multi-rate content injection method provided in an optional specific embodiment of the present invention includes the following steps:

step S301: receiving a content publishing plan and generating a JSON description file according to the content publishing plan;

specifically, after receiving a content publishing plan for the multi-rate media file sent by a content provider, the CMS extracts storage information of the multi-rate media file, that is, a download path, and generates a text description file corresponding to a download path list of the multi-rate media file according to a physical content identifier. In the embodiment, the text description file is taken as a JSON description file as an example, and the data assembling method is simple and convenient to analyze. As shown below, for the JSON description file with the content identifier "cataid 00000001060542" provided in this embodiment, it can be seen that video files with different bit rates correspond to different download addresses, that is, the JSON description file describes a download address list of video files with different bit rates.

Step S302: uploading a JSON description file;

specifically, the CMS uploads the generated JSON description file to a specified content source server (CLIB), and acquires a download path of the JSON description file.

Step S303: sending a content injection message carrying a download path of the JSON description file;

specifically, the CMS issues the download path of the JSON description file to the CDNM through a content injection message through a standard content injection API interface.

Step S304: issuing a content injection message carrying a download path of the text description file;

specifically, after receiving the content delivery message of the CMS, the CDNM extracts service information required by the CDN, selects a NODE corresponding to the service, and generates a content delivery task. And then, the CDNM issues the download path of the JSON description file to the NODE through a content injection message through an internal API (application program interface).

Step S305: downloading a JSON description file;

specifically, the NODE downloads the JSON description file from the CLIB according to a download path of the JSON description file after receiving the content injection message of the CDNM.

Step S306: downloading the multi-code rate media file according to the JSON description file;

specifically, the NODE parses the JSON description file, extracts a download path list of the multi-rate media file, and stores the download path list in the local memory. And then, downloading the multi-code-rate media files one by one, and slicing or transcoding according to the coding format and the code rate information of the multi-code-rate media files to generate a CDN media file storage format.

Step S307: reporting a release result;

specifically, the NODE reports the release result to the CDNM after all the multi-rate media files are released.

Step S308: reporting a release result;

specifically, the CDNM reports the release result to the CMS.

In summary, in the multi-rate media file synchronization process, the multi-rate content injection method provided by this embodiment adopts the text description file to aggregate the download path list of the multi-rate media file, the assembling and parsing method is simple, the standard API interface between the service content management system and the CDNM does not need to be changed, the method is easy to implement, the influence of new requirements on the interfaces of the components is reduced, and the service requirements can be met only by making compatibility between the head end and the bottom layer of the content distribution system, thereby reducing the product development period. The service and CDN middleware network element does not need to pay attention to the delivery state of each media file, so that complex state machine judgment is omitted, the service logic complexity is reduced, and the product maintenance cost is reduced. In addition, the characteristic parameters can be expanded in the text description file aiming at different media files, and the expandability is improved.

In another optional embodiment, the data sending end includes a service management system, the data receiving end includes a service node, and the data file to be sent includes a basic data file or a service data file; wherein,

the service management system is specifically configured to: uploading the obtained basic data file or service data file to a content source server, and obtaining a corresponding download path list of the basic data file or service data file; generating a text description file aiming at the corresponding basic data file or service data file based on the download path list; sending a data updating instruction carrying the downloading path of the text description file to the service node;

the service node is specifically configured to: receiving a data updating instruction which is sent by the service management system and carries the downloading path of the text description file; downloading the text description file according to the download path of the text description file, analyzing the text description file, and acquiring a download path list of the corresponding basic data file or service data file; and downloading the corresponding basic data file or service data file from a content source server according to the corresponding download path list of the basic data file or service data file, and updating local data according to the corresponding basic data file or service data file.

The following describes the embodiment of the present invention in further detail by using specific examples, and as shown in fig. 7, a data updating method provided in an optional specific embodiment of the present invention is particularly suitable for data updating in a large-scale networking mode of a CDN service node, and includes the following steps:

step S401: generating a data file to be sent by data needing to be synchronized to NODE;

specifically, the CDNM periodically exports various types of basic data or service data that need to be synchronized to each NODE to generate a data file to be sent, and encrypts the data file to be sent by an encryption algorithm.

Step S402: uploading a data file to be sent;

specifically, the CDNM uploads the data file to be sent to the CLIB, and acquires download path information of the data file to be sent.

Step S403: generating a JSON description file according to the download path information of the data file to be sent;

specifically, the CDNM assembles information such as basic description information and a storage path of the data file to be transmitted, generates a corresponding JSON description file, and acquires a download path of the JSON description file.

Step S404: sending a data updating instruction carrying a download path of the JSON description file;

specifically, the CDNM sends the JSON description file to each NODE through an internal API interface in a manner similar to a content publishing process, where the data updating instruction of the download path carrying the JSON description file is sent to each NODE.

Step S405: downloading a data file to be sent according to the JSON description file;

specifically, after receiving a data update instruction sent by the CDNM, the NODE downloads a JSON description file, parses the JSON description file, and extracts a download path list of a data file to be sent; and downloading the data file to be sent from the CLIB server according to the download path list of the data file to be sent, and analyzing, thereby updating NODE local data according to the downloaded data file to be sent.

Step S406: reporting a data updating result;

specifically, after updating the local data, the NODE reports the data update result to the CDNM.

Step S407: updating the data sending state;

specifically, after receiving the data update result reported by the NODE, the CDNM updates the data transmission state, and for the NODE with failed data transmission, the CDNM may choose to retry to transmit the data file to be transmitted.

In an optional embodiment, the data sending end includes a service node, the data receiving end includes a service management system, and the data file to be sent includes a ticket log file; wherein,

the service node is specifically configured to: acquiring a call ticket log file matched with an acquisition time period according to a received call ticket acquisition instruction carrying the acquisition time period, and acquiring a download path list of the call ticket log file; generating a text description file aiming at the call ticket log file based on the download path list of the call ticket log file; and sending a call ticket collection response instruction carrying the download path of the text description file to the service management system;

the service management system is specifically configured to: receiving a call ticket acquisition response instruction which is sent by the service node and carries the download path of the text description file; downloading the text description file according to the download path of the text description file, analyzing the text description file, and acquiring a download path list of a call ticket log file; and downloading the call ticket log file according to the download path list of the call ticket log file.

As shown in fig. 8, the method for acquiring a call ticket log provided by an optional specific embodiment of the present invention is particularly suitable for acquiring a call ticket log under a large-scale networking mode of a CDN service node, and includes the following steps:

step S501: issuing a call ticket acquisition request;

specifically, the CDNM regularly generates a call ticket collection task to each NODE, and the call ticket collection task may be specific to a certain time period. The CDNM regularly processes the call ticket collection task and sends call ticket collection requests to all NODEs.

Step S502: acquiring a call ticket log file and a download path thereof according to the call ticket acquisition request, and generating a JSON description file;

specifically, after receiving the ticket collection request, the NODE screens all local ticket log files meeting the conditions and download paths thereof according to the time period information in the request, assembles the files into a file list, and generates a corresponding JSON description file.

Step S503: sending a ticket collection response message carrying a download path of the JSON description file;

specifically, the NODE reports the download path of the JSON description file to the CDNM in a manner of collecting a response message in a ticket through an internal API.

Step S504: downloading a call ticket log file;

specifically, after receiving the call ticket acquisition response message of each NODE, the CDNM downloads the JSON description file, analyzes the JSON description file, and extracts a download path list of the call ticket log file. And the CDNM downloads the call ticket log files one by one from each NODE server according to the download path list of the call ticket log files. For the call ticket log file which fails to download, the CDNM can automatically retry downloading.

An embodiment of the present invention provides a data sending end, and as shown in fig. 9, the data sending end includes: at least one processor 310 and a memory 311 for storing computer programs capable of running on the processor 310; the processor 310 illustrated in fig. 9 is not used to refer to the number of the processors 310 as one, but is only used to refer to the position relationship of the processor 310 relative to other devices, and in practical applications, the number of the processors 310 may be one or more; similarly, the memory 311 shown in fig. 9 is also used in the same sense, i.e. it is only used to refer to the position relationship of the memory 311 with respect to other devices, and in practical applications, the number of the memory 311 may be one or more.

Wherein, when the processor 310 is configured to run the computer program, the following steps are executed:

acquiring a download path list of a data file to be sent;

In an alternative embodiment, the processor 310 is further configured to execute the following steps when the computer program is executed:

The data transmitting end further comprises: at least one network interface 312. The various components in the data sender are coupled together by a bus system 313. It will be appreciated that the bus system 313 is used to enable communications among the components connected. The bus system 313 includes a power bus, a control bus, and a status signal bus in addition to the data bus. For clarity of illustration, however, the various buses are labeled as bus system 313 in FIG. 9.

The memory 311 may be a volatile memory or a nonvolatile memory, or may include both volatile and nonvolatile memories. Among them, the nonvolatile Memory may be a Read Only Memory (ROM), a Programmable Read Only Memory (PROM), an Erasable Programmable Read-Only Memory (EPROM), an Electrically Erasable Programmable Read-Only Memory (EEPROM), a magnetic random access Memory (FRAM), a Flash Memory (Flash Memory), a magnetic surface Memory, an optical disk, or a Compact Disc Read-Only Memory (CD-ROM); the magnetic surface storage may be disk storage or tape storage. Volatile memory can be Random Access Memory (RAM), which acts as external cache memory. By way of illustration and not limitation, many forms of RAM are available, such as Static Random Access Memory (SRAM), Synchronous Static Random Access Memory (SSRAM), Dynamic Random Access Memory (DRAM), Synchronous Dynamic Random Access Memory (SDRAM), Double Data Rate Synchronous Dynamic Random Access Memory (DDRSDRAM), Enhanced Synchronous Dynamic Random Access Memory (ESDRAM), Enhanced Synchronous Dynamic Random Access Memory (Enhanced DRAM), Synchronous Dynamic Random Access Memory (SLDRAM), Direct Memory (DRmb Access), and Random Access Memory (DRAM). The memory 311 described in connection with the embodiments of the invention is intended to comprise, without being limited to, these and any other suitable types of memory.

The memory 311 in the embodiment of the present invention is used to store various types of data to support the operation of the data transmitting end. Examples of such data include: any computer program for operating on the data transmitter, such as operating systems and application programs; contact data; telephone book data; a message; a picture; video, etc. The operating system includes various system programs, such as a framework layer, a core library layer, a driver layer, and the like, and is used for implementing various basic services and processing hardware-based tasks. The application programs may include various application programs such as a Media Player (Media Player), a Browser (Browser), etc. for implementing various application services. Here, the program that implements the method of the embodiment of the present invention may be included in an application program.

The embodiment further provides a computer storage medium, for example, including a memory 311 storing a computer program, where the computer program is executable by the processor 310 in the data transmitting end to perform the steps of the foregoing method. The computer storage medium can be FRAM, ROM, PROM, EPROM, EEPROM, Flash Memory, magnetic surface Memory, optical disk, or CD-ROM; or may be a variety of devices including one or any combination of the above memories, such as a mobile phone, computer, tablet device, personal digital assistant, etc.

A computer storage medium having a computer program stored therein, the computer program when executed by a processor performing the steps of:

acquiring a download path list of a data file to be sent;

In an alternative embodiment, the computer program, when executed by the processor, further performs the steps of:

The embodiment of the present invention provides a data receiving end, please refer to fig. 9 again, where the data receiving end includes: at least one processor 310 and a memory 311 for storing computer programs capable of running on the processor 310; the processor 310 illustrated in fig. 9 is not used to refer to the number of the processors 310 as one, but is only used to refer to the position relationship of the processor 310 relative to other devices, and in practical applications, the number of the processors 310 may be one or more; similarly, the memory 311 shown in fig. 9 is also used in the same sense, i.e. it is only used to refer to the position relationship of the memory 311 with respect to other devices, and in practical applications, the number of the memory 311 may be one or more.

The data receiving end further comprises: at least one network interface 312. The various components in the data receiving end are coupled together by a bus system 313. It will be appreciated that the bus system 313 is used to enable communications among the components connected. The bus system 313 includes a power bus, a control bus, and a status signal bus in addition to the data bus. For clarity of illustration, however, the various buses are labeled as bus system 313 in FIG. 9.

The memory 311 in the embodiment of the present invention is used to store various types of data to support the operation of the data receiving end. Examples of such data include: any computer program for operating on the data receiving end, such as operating systems and application programs; contact data; telephone book data; a message; a picture; video, etc. The operating system includes various system programs, such as a framework layer, a core library layer, a driver layer, and the like, and is used for implementing various basic services and processing hardware-based tasks. The application programs may include various application programs such as a Media Player (Media Player), a Browser (Browser), etc. for implementing various application services. Here, the program that implements the method of the embodiment of the present invention may be included in an application program.

The present embodiment further provides a computer storage medium, for example, including a memory 311 storing a computer program, which can be executed by the processor 310 in the data receiving end to perform the steps of the foregoing method. The computer storage medium can be FRAM, ROM, PROM, EPROM, EEPROM, Flash Memory, magnetic surface Memory, optical disk, or CD-ROM; or may be a variety of devices including one or any combination of the above memories, such as a mobile phone, computer, tablet device, personal digital assistant, etc.

A computer storage medium having a computer program stored therein, the computer program, when executed by a processor, performing the steps of:

The above description is only for the specific embodiments of the present invention, but the scope of the present invention is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present invention, and all the changes or substitutions should be covered within the scope of the present invention. The scope of the invention is to be determined by the scope of the appended claims.

Claims

1. A data sending method is applied to a data sending end, and is characterized by comprising the following steps:

acquiring a download path list of a data file to be sent;

2. The method of claim 1, further comprising:

3. A data receiving method, applied to a data receiving end, the method comprising:

4. The method of claim 3, further comprising:

5. A data sender, characterized in that the data sender comprises a processor and a memory for storing a computer program capable of running on the processor; wherein,

the processor is configured to execute the steps of the data transmission method according to any one of claims 1 to 2 when the computer program is executed.

6. A data receiving end, characterized in that the data receiving end comprises a processor and a memory for storing a computer program capable of running on the processor; wherein,

the processor is adapted to perform the steps of the data receiving method of any one of claims 3 to 4 when running the computer program.

7. A data transmission system, characterized in that the data transmission system comprises a data transmitting end according to claim 5 and a data receiving end according to claim 6.

8. The data transmission system according to claim 7, wherein the data sending end comprises a service content management system, the data receiving end comprises a service node, and the data file to be sent is a multi-rate media file; wherein,

9. The data transmission system according to claim 7, wherein the data sending end comprises a service management system, the data receiving end comprises a service node, and the data file to be sent comprises a basic data file or a service data file; wherein,

10. The data transmission system of claim 7, wherein the data sending end comprises a service node, the data receiving end comprises a service management system, and the data file to be sent comprises a call ticket log file; wherein,

11. A computer storage medium, characterized in that a computer program is stored in the computer storage medium, which computer program, when being executed by a processor, realizes the steps of the data transmission method of any one of claims 1 to 2 or the data reception method of any one of claims 3 to 4.