WO2017181602A1 - 点播方法、装置、电子设备及系统 - Google Patents

点播方法、装置、电子设备及系统 Download PDF

Info

Publication number
WO2017181602A1
WO2017181602A1 PCT/CN2016/100437 CN2016100437W WO2017181602A1 WO 2017181602 A1 WO2017181602 A1 WO 2017181602A1 CN 2016100437 W CN2016100437 W CN 2016100437W WO 2017181602 A1 WO2017181602 A1 WO 2017181602A1
Authority
WO
WIPO (PCT)
Prior art keywords
demand
file
request
demand file
total
Prior art date
Application number
PCT/CN2016/100437
Other languages
English (en)
French (fr)
Inventor
李洪福
Original Assignee
乐视控股(北京)有限公司
乐视云计算有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 乐视控股(北京)有限公司, 乐视云计算有限公司 filed Critical 乐视控股(北京)有限公司
Publication of WO2017181602A1 publication Critical patent/WO2017181602A1/zh

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04NPICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/20Servers specifically adapted for the distribution of content, e.g. VOD servers; Operations thereof
    • H04N21/23Processing of content or additional data; Elementary server operations; Server middleware
    • H04N21/239Interfacing the upstream path of the transmission network, e.g. prioritizing client content requests
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04NPICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/20Servers specifically adapted for the distribution of content, e.g. VOD servers; Operations thereof
    • H04N21/23Processing of content or additional data; Elementary server operations; Server middleware
    • H04N21/239Interfacing the upstream path of the transmission network, e.g. prioritizing client content requests
    • H04N21/2393Interfacing the upstream path of the transmission network, e.g. prioritizing client content requests involving handling client requests
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04NPICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/20Servers specifically adapted for the distribution of content, e.g. VOD servers; Operations thereof
    • H04N21/25Management operations performed by the server for facilitating the content distribution or administrating data related to end-users or client devices, e.g. end-user or client device authentication, learning user preferences for recommending movies
    • H04N21/262Content or additional data distribution scheduling, e.g. sending additional data at off-peak times, updating software modules, calculating the carousel transmission frequency, delaying a video stream transmission, generating play-lists
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04NPICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/20Servers specifically adapted for the distribution of content, e.g. VOD servers; Operations thereof
    • H04N21/25Management operations performed by the server for facilitating the content distribution or administrating data related to end-users or client devices, e.g. end-user or client device authentication, learning user preferences for recommending movies
    • H04N21/262Content or additional data distribution scheduling, e.g. sending additional data at off-peak times, updating software modules, calculating the carousel transmission frequency, delaying a video stream transmission, generating play-lists
    • H04N21/26208Content or additional data distribution scheduling, e.g. sending additional data at off-peak times, updating software modules, calculating the carousel transmission frequency, delaying a video stream transmission, generating play-lists the scheduling operation being performed under constraints
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04NPICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/40Client devices specifically adapted for the reception of or interaction with content, e.g. set-top-box [STB]; Operations thereof
    • H04N21/45Management operations performed by the client for facilitating the reception of or the interaction with the content or administrating data related to the end-user or to the client device itself, e.g. learning user preferences for recommending movies, resolving scheduling conflicts
    • H04N21/458Scheduling content for creating a personalised stream, e.g. by combining a locally stored advertisement with an incoming stream; Updating operations, e.g. for OS modules ; time-related management operations
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04NPICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/40Client devices specifically adapted for the reception of or interaction with content, e.g. set-top-box [STB]; Operations thereof
    • H04N21/45Management operations performed by the client for facilitating the reception of or the interaction with the content or administrating data related to the end-user or to the client device itself, e.g. learning user preferences for recommending movies, resolving scheduling conflicts
    • H04N21/458Scheduling content for creating a personalised stream, e.g. by combining a locally stored advertisement with an incoming stream; Updating operations, e.g. for OS modules ; time-related management operations
    • H04N21/4583Automatically resolving scheduling conflicts, e.g. when a recording by reservation has been programmed for two programs in the same time slot
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04NPICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/40Client devices specifically adapted for the reception of or interaction with content, e.g. set-top-box [STB]; Operations thereof
    • H04N21/47End-user applications
    • H04N21/472End-user interface for requesting content, additional data or services; End-user interface for interacting with content, e.g. for content reservation or setting reminders, for requesting event notification, for manipulating displayed content
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04NPICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/40Client devices specifically adapted for the reception of or interaction with content, e.g. set-top-box [STB]; Operations thereof
    • H04N21/47End-user applications
    • H04N21/472End-user interface for requesting content, additional data or services; End-user interface for interacting with content, e.g. for content reservation or setting reminders, for requesting event notification, for manipulating displayed content
    • H04N21/47202End-user interface for requesting content, additional data or services; End-user interface for interacting with content, e.g. for content reservation or setting reminders, for requesting event notification, for manipulating displayed content for requesting content on demand, e.g. video on demand

Definitions

  • the present application relates to the field of multimedia information processing technologies, and in particular, to an on-demand method, apparatus, electronic device, and system.
  • the client and the on-demand server will have more interactions.
  • the number of requests and responses for network transmissions is also increasing.
  • a bad network state such as when the client is in a non-stop state of movement and the network state is unstable, it is inevitable that some on-demand requests will not be responded. Therefore, the number of interactions is not only a waste of network resources, but also a communication failure due to network instability.
  • the present application provides an on-demand method, device, electronic device, and system, which are used to solve the problem that when the same client requests to play multiple on-demand files, the number of interactions is more wasteful of network resources, and the network instability may easily lead to communication failure.
  • the problem when the same client requests to play multiple on-demand files, the number of interactions is more wasteful of network resources, and the network instability may easily lead to communication failure.
  • an embodiment of the present application provides an on-demand method, where the method includes:
  • the client agent receives the on-demand request sent by the client and carries the on-demand file identifier and stores it;
  • an embodiment of the present application provides an on-demand method, where the method includes:
  • the server agent receives a total on-demand request sent by the client agent, where the total on-demand request is merged by at least two on-demand requests sent by the same client, and the on-demand request includes an on-demand file identifier of each on-demand request;
  • Each received on-demand file is sent to the client agent, so that the client agent sends each on-demand file to the client for playing.
  • an embodiment of the present invention provides an on-demand device, where the device includes:
  • the on-demand request storage module is configured to receive an on-demand request sent by the client and carry the on-demand file identifier, and store the request;
  • the on-demand request quantity determining module is configured to calculate the number of the on-demand requests sent by the client stored in the preset duration, and determine whether the quantity is greater than or equal to two;
  • the on-demand request merging module is configured to merge the on-demand requests of the client stored in the preset duration into one total on-demand request, if the judgment result of the on-demand request quantity determining module is yes, the total on-demand request includes The on-demand file identifier of each on-demand request;
  • a total on-demand request sending module configured to send the total on-demand request to a server proxy of the on-demand server, so that the service proxy obtains the total on-demand request from the on-demand server
  • Each on-demand file identifies the corresponding on-demand file
  • the on-demand file processing module is configured to receive an on-demand file corresponding to each of the on-demand file identifiers in the total on-demand request sent by the server agent, and send the file to the client for playing.
  • an embodiment of the present application provides an on-demand device, where the device includes:
  • a total on-demand request receiving module configured to receive a total on-demand request sent by the client agent, where the total on-demand request is merged by at least two on-demand requests sent by the same client, and the on-demand request includes on-demand request of each on-demand request File identification
  • a total on-demand request decomposition module configured to decompose the total on-demand request, obtain a decomposed on-demand request corresponding to each on-demand file identifier, and send the request to the on-demand server;
  • An on-demand file obtaining module configured to receive an on-demand file returned by the on-demand server for each decomposed on-demand request
  • the on-demand file processing module is configured to send the received on-demand files to the client agent, so that the client agent sends the on-demand files to the client for playing.
  • an embodiment of the present application provides an on-demand system, where the system includes:
  • the client is configured to send an on-demand file request with an on-demand file identifier to the client agent, and receive an on-demand file sent by the client agent for playing;
  • a client agent configured to receive an on-demand request for sending an on-demand file identifier sent by the client, and store the number of on-demand requests sent by the client stored in the preset duration, and determine whether the quantity is greater than or equal to two; And merging the on-demand requests of the client stored in the preset duration into a total on-demand request, where the total on-demand request includes an on-demand file identifier of each on-demand request; and sending the total on-demand request to the on-demand server a server agent; receiving an on-demand file corresponding to each of the on-demand file identifiers in the total on-demand request sent by the server agent, and sending the file to the client for playing;
  • a server agent configured to receive a total on-demand request sent by the client agent, where the total on-demand request is merged by at least two on-demand requests sent by the same client, and the on-demand request includes an on-demand file identifier of each on-demand request; Decomposing the total on-demand request to obtain a decomposed on-demand request corresponding to each on-demand file identifier, and sending the request to the on-demand server; receiving the on-demand file returned by the on-demand server for each decomposed on-demand request; and sending the received on-demand files to The client agent, so that the client agent sends each of the on-demand files to the client for playing;
  • the on-demand server is configured to receive the decomposed on-demand request sent by the server proxy and return the corresponding on-demand file.
  • the embodiment of the present application further provides a non-volatile computer storage medium storing computer executable instructions for performing the above-mentioned on-demand method of the present application.
  • the embodiment of the present application further provides an electronic device, including: at least one processor; and a memory; wherein the memory stores a program executable by the at least one processor, where the instruction is Said at least one processor is operative to enable said at least one processor to perform any of the above-described on-demand methods of the present application.
  • the embodiment of the present application further provides a computer program product, where the computer program product comprises a computing program stored on a non-transitory computer readable storage medium, the computer program comprising program instructions, when the program The instructions, when executed by a computer, cause the computer to perform any of the on-demand methods of the claims.
  • a total on-demand request is generated by combining the on-demand requests within the preset duration of the client, so that when the client requests to play a plurality of on-demand files, only one on-demand request is transmitted through the network.
  • the number of on-demand requests transmitted over the network can be reduced, thereby saving network resources.
  • the probability of transmitting an on-demand request and the transmission failure is low, and if one of the plurality of on-demand requests has a transmission failure, the probability is higher.
  • Embodiment 1 is an exemplary flowchart of an on-demand method in Embodiment 1 of the present application
  • FIG. 2 is an exemplary flowchart of an on-demand method in Embodiment 2 of the present application.
  • FIG. 3 is a schematic structural diagram of a video on-demand device according to Embodiment 3 of the present application.
  • FIG. 4 is a schematic structural diagram of a video on-demand device according to Embodiment 4 of the present application.
  • FIG. 5 is a schematic structural diagram of an on-demand system according to Embodiment 5 of the present application.
  • FIG. 6 is a schematic diagram showing the hardware structure of an apparatus for performing an on-demand method provided in Embodiment 7 of the present application. Figure.
  • FIG. 1 is a schematic flowchart diagram of an on-demand method provided by an embodiment of the present application, which is applicable to a client agent, and includes the following steps:
  • Step 101 The client agent receives the on-demand request sent by the client and carries the on-demand file identifier and stores it.
  • the on-demand server is used to provide an on-demand file
  • the on-demand file identifier is, for example, an on-demand file ID (IDentity, identification number), an on-demand file path, or an on-demand file name.
  • Step 102 Calculate the number of on-demand requests sent by the client stored in the preset duration, and determine whether the number is greater than or equal to two.
  • Step 103 If yes, merge the on-demand requests of the client stored in the preset duration into one total on-demand request, where the total on-demand request includes an on-demand file identifier of each on-demand request.
  • the client agent merges the stored three on-demand requests.
  • a total on-demand request is generated that carries an on-demand file identifier of the on-demand file 1, the on-demand file 2, and the on-demand file 3.
  • step 102 if the result of the determination in step 102 is no (that is, the number of the on-demand requests is less than 2), refer to the prior art processing, which is not described in this embodiment of the present application.
  • Step 104 Send the total on-demand request to the server proxy of the on-demand server, so that the service proxy obtains the on-demand file corresponding to each of the on-demand file identifiers in the total on-demand request from the on-demand server.
  • Step 105 Receive each of the on-demand messages in the total on-demand request sent by the server proxy The piece identifies the corresponding on-demand file and sends it to the client for playback.
  • a total on-demand request is generated by combining the on-demand requests within the preset duration of the client, so that when the client requests to play multiple on-demand files, only one on-demand request transmitted through the network (ie, total On-demand request).
  • the number of on-demand requests transmitted over the network can be reduced, thereby saving network resources.
  • the probability of transmitting an on-demand request and the transmission failure is low, and if one of the plurality of on-demand requests has a transmission failure, the probability is higher.
  • step 202 1), for step 202:
  • the number of the on-demand requests sent by the client stored in the preset duration is calculated in step 102 in the embodiment of the present application, which may specifically include the following steps:
  • Step A1 Start timing after receiving the first on-demand request, and set the number of on-demand requests to 1.
  • the first on-demand request refers to the first on-demand request sent by the client after the certain time period is not received if the on-demand request sent by the client is not received within a certain period of time. For example, if the certain time period is 5 minutes, if the on-demand request sent by the client is not received within 5 minutes, the first on-demand request received after 5 minutes is the first on-demand request in step A1.
  • the first on-demand request sent by the client after establishing a connection with the on-demand server is also counted as the first on-demand request in step A1.
  • Step A2 After receiving an on-demand request sent by the client within a preset duration after the start of the timer, the number of the on-demand requests is accumulated by one.
  • the preset duration in order to process the on-demand request as soon as possible, in order to prevent the user from being aware of the slow speed of obtaining the on-demand file, the preset duration may be 1 second in the embodiment of the present application.
  • the preset time length is not limited in this embodiment of the present application.
  • the first on-demand is received in the above steps A1 - A2
  • the request starts timing and determines the preset duration.
  • the time advance may be further divided into one time period, and each time period is a preset time length. For example, after the client establishes a connection with the on-demand server, it is the start of the first preset duration, thereby determining each time period as the preset duration.
  • the on-demand request of the client may be stored in a preset duration, and the number of on-demand requests is not calculated in an accumulated manner, and the on-demand request sent by the client in the preset duration is finally counted. quantity.
  • step 103 1), for step 103:
  • Step 103 in the example may specifically include the following steps:
  • Step B1 Insert a preset on-demand file identifier separator between the adjacent two on-demand file identifiers to generate total on-demand file identification information.
  • the preset on-demand file identifier splitter may be “,” or “/”, etc., of course, the server proxy can be identified as the preset on-demand file identifier splitter, which is applicable to the embodiment of the present application. This application does not limit this.
  • Step B2 Generate a total on-demand request carrying the total on-demand file identification information, so that the server agent performs the following operations: acquiring, according to the preset on-demand file identifier, from the total on-demand file request, each on-demand file identifier. , generating a decomposed on-demand request for each on-demand file identifier and sending it to the on-demand server.
  • the server agent can identify each on-demand file identifier, thereby generating a decomposed on-demand request for each on-demand file identifier and sending it to the on-demand server, so that the on-demand server can process according to the existing on-demand request. Without making changes to the on-demand server.
  • the embodiment of the present application may also combine the following on-demand requests to generate a total on-demand request according to the following method. Specifically, adding an on-demand request splitter between adjacent on-demand requests is equivalent to concatenating the on-demand requests. Generate a total on-demand request. In this way, the server agent can decompose the respective on-demand requests and send them to the on-demand server according to the on-demand request splitter, and can achieve the same effect.
  • step 105
  • the server agent may send the on-demand file returned by the on-demand server to each client agent for each of the decomposed on-demand requests.
  • the client agent is equivalent to how many on-demand requests are implemented, and how many responses there are.
  • each of the on-demand files returned by the on-demand server may be a merged on-demand file, so that only one merged on-demand file needs to be transmitted through the network (ie, Do a response once, without having to transfer it once for each on-demand file. specific:
  • the on-demand file corresponding to each of the on-demand file identifiers in the total on-demand request is a merged on-demand file
  • the merged on-demand file includes a header information and an on-demand file corresponding to each on-demand file identifier; wherein the header information includes: each The on-demand file identifier of the on-demand file, the location information of each of the on-demand files in the merged on-demand file; then, in step 105, the method may include the following steps:
  • Step C1 Receive the merged on-demand file, and parse the merged on-demand file according to the header information, and obtain an on-demand file corresponding to each on-demand file identifier.
  • the location information includes a start location and an end location of each on-demand file.
  • the on-demand file can be obtained according to the on-demand file identifier of the on-demand file and its corresponding location information.
  • Step C2 Send each of the on-demand files obtained after parsing to the client for playing.
  • the header information further includes: the number of the on-demand file identifiers, and the step C1 may specifically include the following steps:
  • Step D1 Confirm whether the number of on-demand file identifiers in the header information is the same as the total number of on-demand file identifiers.
  • Step D2 If the same, for each on-demand file, the on-demand file is obtained according to the on-demand file identifier and the location information of the on-demand file.
  • the error information may be fed back to the server proxy to retransmit the data.
  • the number of on-demand file identifiers in the header information may also facilitate the client to determine how many on-demand files need to be decomposed, so that the client agent allocates storage space.
  • a plurality of on-demand requests of the client may be combined to obtain a total on-demand request for transmission in the network, or the on-demand files of the plurality of on-demand requests may be combined into one merged on-demand file for transmission in the network.
  • multiple transmissions and interactions originally required in the prior art can be completed with only one interaction, which can save network resources.
  • due to 1 time The probability of interaction failure is low, and the stability of communication can also be improved.
  • the embodiment of the present application further provides an on-demand method, which is applicable to a server proxy.
  • FIG. 2 it is a schematic flowchart of the method, which may include the following steps:
  • Step 201 The server agent receives a total on-demand request sent by the client agent, where the total on-demand request is merged by at least two on-demand requests sent by the same client, and the on-demand request includes an on-demand file identifier of each on-demand request.
  • the total on-demand request is generated by the client agent, and the method for generating the same is described in the first embodiment, and details are not described herein again.
  • Step 202 Decompose the total on-demand request, obtain a decomposed on-demand request corresponding to each on-demand file identifier, and send the request to the on-demand server.
  • Step 203 Receive an on-demand file returned by the on-demand server for each decomposed on-demand request.
  • Step 204 Send the received on-demand files to the client agent, so that the client agent sends the on-demand files to the client for playing.
  • the server proxy receives a total on-demand request sent by the client proxy and synthesized by at least two on-demand requests.
  • the client requests to play multiple on-demand files there is only one on-demand request transmitted through the network (ie, the total on-demand request).
  • the number of on-demand requests transmitted over the network can be reduced, thereby reducing the number of interactions and saving network resources.
  • the probability of transmitting an on-demand request and the transmission failure is low, and if there is a possibility that one of the plurality of on-demand requests fails to be transmitted, in the embodiment of the present application, the plurality of on-demand requests are combined into one.
  • the on-demand request is transmitted in the network, and the network state is also prevented from being bad. As a result, some of the on-demand requests in the prior art cannot be transmitted and the communication fails, thereby improving the stability of the communication.
  • the received on-demand files are sent to the client agent in step 204, which may specifically include The following steps:
  • Step F1 Combine the received on-demand files to generate a merged on-demand file, where the merged on-demand file includes the header information and the on-demand file corresponding to each on-demand file identifier; wherein the header information includes: on-demand of each on-demand file File identification, each on-demand file at the merge point The location information in the file.
  • Step F2 Send the merged on-demand file to the client agent.
  • the merged on-demand file is sent to the client agent, so that the on-demand file that needs to be sent once for each on-demand file request is realized and sent together, thereby realizing multiple interactions required by the prior art, and only one time can be completed. , thereby further reducing the number of interactions and improving communication stability.
  • the header information further includes: an on-demand file identifier quantity, so that the client agent determines the on-demand according to the number of the on-demand file identifiers in the header information and the total number of the on-demand file identifiers in the header information. Whether the file is complete.
  • the total on-demand request includes the total on-demand file identification information.
  • the total on-demand file identification information includes each on-demand file identifier and a preset on-demand file identifier separator for setting between two adjacent on-demand file identifiers.
  • step 202 the total on-demand request is decomposed, and the de-asserted on-demand request corresponding to each of the on-demand file identifiers is obtained, which may include: obtaining, according to the preset on-demand file identifier, the on-demand broadcast from the total on-demand file request. File identification, and generate a decomposed on-demand request corresponding to each on-demand file identifier.
  • the on-demand request of the client may further include an on-demand file play priority in order to facilitate the personalized requirement, and the merged on-demand file may be combined to enable the on-demand file with higher priority than other on-demand broadcasts.
  • the file has a larger amount of data, so that the high-speed on-demand file is preferentially transmitted to the client.
  • the priority may be a user-specified priority.
  • the server proxy receives a total on-demand request, which is a request obtained by the client proxy to merge multiple on-demand requests of the client.
  • the embodiment of the present application further provides an on-demand device, as shown in FIG. Shown as a schematic structural view of the device, the device includes:
  • the on-demand request storage module 301 is configured to receive an on-demand request sent by the client and carry the on-demand file identifier, and store the request;
  • the on-demand request quantity determining module 302 is configured to calculate the number of the on-demand requests sent by the client stored in the preset duration, and determine whether the quantity is greater than or equal to two;
  • the on-demand request merging module 303 is configured to merge the on-demand requests of the client stored in the preset duration into one total on-demand request, if the judgment result of the on-demand request quantity determining module is yes, in the total on-demand request Including the on-demand file identifier of each on-demand request;
  • a total on-demand request sending module 304 configured to send the total on-demand request to a server proxy of the on-demand server, so that the service proxy obtains on-demand corresponding to each on-demand file identifier in the total on-demand request from the on-demand server file;
  • the on-demand file processing module 305 is configured to receive an on-demand file corresponding to each of the on-demand file identifiers in the total on-demand request sent by the server agent, and send the file to the client for playing.
  • the on-demand file corresponding to each of the on-demand file identifiers in the total on-demand request is a merged on-demand file
  • the merged on-demand file includes header information and an on-demand file corresponding to each on-demand file identifier
  • the header information includes: an on-demand file identifier of each on-demand file, and location information of each on-demand file in the merged on-demand file;
  • the on-demand file processing module specifically includes:
  • a merged on-demand file parsing unit configured to receive the merged on-demand file, and parse the merged on-demand file according to the header information, to obtain an on-demand file corresponding to each on-demand file identifier;
  • the on-demand file sending unit is configured to send each of the on-demand files obtained after parsing to the client for playing.
  • the header information further includes: an on-demand file identifier quantity
  • the merged on-demand file parsing unit is specifically used to:
  • the on-demand file is obtained according to the on-demand file identification and location information of the on-demand file.
  • the on-demand request merge module specifically includes:
  • a splitter insertion unit configured to insert a preset on-demand file identifier splitter between adjacent two on-demand file identifiers to generate total on-demand file identification information
  • a total on-demand request processing unit configured to generate a total point of carrying the total on-demand file identification information
  • the request is sent to enable the server agent to: obtain each of the on-demand file identifiers from the total on-demand file request according to the preset on-demand file identifier splitter, generate a decomposed on-demand request for each on-demand file identifier, and send the request Give the on-demand server.
  • the on-demand request quantity determining module specifically includes:
  • a timing unit configured to start timing after receiving the first on-demand request, and set the number of on-demand requests to be 1;
  • a calculating unit configured to accumulate the number of the on-demand requests by one after receiving an on-demand request sent by the client within a preset duration after starting the timing.
  • FIG. 4 is a schematic structural diagram of the device, where the device includes:
  • the total on-demand request receiving module 401 is configured to receive a total on-demand request sent by the client agent, where the total on-demand request is merged by at least two on-demand requests sent by the same client, and the on-demand request includes each of the on-demand requests.
  • the total on-demand request decomposition module 402 is configured to decompose the total on-demand request, obtain a decomposed on-demand request corresponding to each on-demand file identifier, and send the request to the on-demand server;
  • the on-demand file obtaining module 403 is configured to receive an on-demand file returned by the on-demand server for each decomposed on-demand request;
  • the on-demand file processing module 404 is configured to send the received on-demand files to the client agent, so that the client agent sends the on-demand files to the client for playing.
  • the on-demand file processing module specifically includes:
  • a merged on-demand file generating unit configured to combine the received on-demand files to generate a merged on-demand file, where the merged on-demand file includes a header information and an on-demand file corresponding to each on-demand file identifier; wherein the header information includes: An on-demand file identifier of an on-demand file, and location information of each on-demand file in the merged on-demand file;
  • a merge on-demand file generating unit sending unit configured to send the merged on-demand file to the client agent.
  • the header information further includes: an on-demand file identifier number.
  • the total on-demand request includes total on-demand file identification information, where the total on-demand file identification information includes each on-demand file identifier and a preset for setting between two adjacent on-demand file identifiers.
  • the total on-demand request decomposition module is configured to obtain, according to the preset on-demand file identifier, the respective on-demand file identifiers from the total on-demand file request, and generate a decomposed on-demand request corresponding to each of the on-demand file identifiers.
  • FIG. 5 is a schematic structural diagram of the system, where the system includes:
  • the client 501 is configured to send an on-demand file request with an on-demand file identifier to the client proxy, and receive an on-demand file sent by the client proxy for playing;
  • the client agent 502 is configured to receive an on-demand request for carrying the on-demand file identifier sent by the client, and store the number of the on-demand requests sent by the client stored in the preset duration, and determine whether the quantity is greater than or equal to two; And merging the on-demand requests of the client stored in the preset duration into a total on-demand request, where the total on-demand request includes an on-demand file identifier of each on-demand request; and sending the total on-demand request to the on-demand server a server agent; receiving an on-demand file corresponding to each of the on-demand file identifiers in the total on-demand request sent by the server agent, and sending the file to the client for playing;
  • the server proxy 503 is configured to receive a total on-demand request sent by the client proxy, where the total on-demand request is merged by at least two on-demand requests sent by the same client, and the on-demand request includes an on-demand file identifier of each on-demand request. Decomposing the total on-demand request to obtain a decomposed on-demand request corresponding to each on-demand file identifier, and sending the request to the on-demand server; receiving the on-demand file returned by the on-demand server for each decomposed on-demand request; sending each received on-demand file Giving the client agent to enable the client agent to send each on-demand file to the client for playing;
  • the on-demand server 504 is configured to receive the decomposed on-demand request sent by the server proxy, and return a corresponding on-demand file.
  • a sixth embodiment of the present application provides a non-volatile computer storage medium, where the computer storage medium stores computer-executable instructions, which can execute the on-demand method in the first embodiment and/or the second embodiment. .
  • non-volatile computer storage provided by the embodiment of the present application a medium, wherein computer executable instructions are stored, the computer executable instructions being set to:
  • the non-volatile computer storage medium provided by the embodiment of the present application, wherein the on-demand file corresponding to each on-demand file identifier in the total on-demand request is a merged on-demand file, and the merged on-demand file Included in the header information and the on-demand file corresponding to each on-demand file identifier; wherein the header information includes: an on-demand file identifier of each on-demand file, and location information of each on-demand file in the merged on-demand file;
  • Each of the on-demand files obtained after parsing is sent to the client for playback.
  • the non-volatile computer storage medium provided by the embodiment of the present application, wherein the header information further includes: an on-demand file identifier quantity;
  • Parsing the merged on-demand file according to the header information, and obtaining an on-demand file corresponding to each on-demand file identifier specifically:
  • the on-demand file is obtained according to the on-demand file identification and location information of the on-demand file.
  • the non-volatile computer storage medium provided by the embodiment of the present application, wherein the on-demand requests of the client stored in the preset duration are merged into one total on-demand request,
  • the total on-demand request includes the on-demand file identifier of each on-demand request, specifically include:
  • Generating a total on-demand request carrying the total on-demand file identification information so that the server proxy performs the following operations: acquiring, according to the preset on-demand file identifier splitter, the respective on-demand file identifiers from the total on-demand file request, and generating The decomposed on-demand request of each on-demand file identifier is sent to the on-demand server.
  • the non-volatile computer storage medium provided by the embodiment of the present application wherein calculating the number of the on-demand requests sent by the client stored in the preset duration includes:
  • the embodiment of the present application provides a non-volatile computer storage medium, where a total on-demand request sent by a client agent is received, and the total on-demand request is sent by at least two by the same client.
  • the on-demand request is merged, and the on-demand request includes an on-demand file identifier of each on-demand request;
  • Each received on-demand file is sent to the client agent, so that the client agent sends each on-demand file to the client for playing.
  • the embodiment of the present application provides a non-volatile computer storage medium, where the sending of the received on-demand files to the client agent includes:
  • the merged on-demand file includes the header information and the on-demand file corresponding to each on-demand file identifier; wherein the header information includes: an on-demand file identifier of each on-demand file, Location information of each on-demand file in the merged on-demand file;
  • the embodiment of the present application provides a non-volatile computer storage medium, wherein the header information further includes: an on-demand file identifier number.
  • the embodiment of the present application provides a non-volatile computer storage medium, where the total on-demand request includes total on-demand file identification information, and the total on-demand file identification information includes each on-demand file identifier. And a preset on-demand file identifier separator for setting between two adjacent on-demand file identifiers;
  • Decomposing the total on-demand request to obtain a decomposed on-demand request corresponding to each on-demand file identifier specifically including:
  • each on-demand file identifier from the total on-demand file request according to the preset on-demand file identifier splitter, and generating a decomposed on-demand request corresponding to each on-demand file identifier.
  • FIG. 6 is a schematic structural diagram of hardware of an electronic device for performing an on-demand method according to Embodiment 7 of the present application. As shown in FIG. 6, the device includes:
  • processors 610 and memory 620 one processor 610 is taken as an example in FIG.
  • the apparatus that performs the on-demand processing method may further include: an input device 630 and an output device 640.
  • the processor 610, the memory 620, the input device 630, and the output device 640 may be connected by a bus or other means, as exemplified by a bus connection in FIG.
  • the memory 620 is a non-volatile computer readable storage medium, and can be used to store non-volatile software programs, non-volatile computer-executable programs, and modules, such as program instructions corresponding to the on-demand method in the embodiment of the present application.
  • Module for example, the on-demand request storage module 301, the on-demand request quantity judging module 302, the on-demand request merge module 303, the total on-demand request sending module 304, and the on-demand file processing module 305 shown in FIG. 3); and/or, in FIG.
  • the total on-demand request receiving module 401, the total on-demand request decomposition module 402, the on-demand file acquisition module 403, and the on-demand file processing module 404) are shown.
  • the processor 610 executes various functional applications and data processing of the server by running non-volatile software programs, instructions and modules stored in the memory 620, that is, on-demand in the first embodiment and/or the second embodiment of the method. method.
  • the memory 620 may include a storage program area and a storage data area, wherein the storage program area may store an operating system, an application required for at least one function; the storage data area may store data created according to use of the on-demand device, and the like.
  • the memory 620 can include high speed random access
  • the memory may also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other non-volatile solid state storage device.
  • memory 620 can optionally include memory remotely located relative to processor 610, which can be connected to the on-demand device over a network. Examples of such networks include, but are not limited to, the Internet, intranets, local area networks, mobile communication networks, and combinations thereof.
  • Input device 630 can receive input numeric or character information and generate key signal inputs related to user settings and function control of the on-demand processing device.
  • the output device 640 can include a display device such as a display screen.
  • the one or more modules are stored in the memory 620, and when executed by the one or more processors 610, perform the on-demand method in the first embodiment and/or the second embodiment.
  • the electronic device of the embodiment of the present application exists in various forms, including but not limited to:
  • Mobile communication devices These devices are characterized by mobile communication functions and are mainly aimed at providing voice and data communication.
  • Such terminals include: smart phones (such as iPhone), multimedia phones, functional phones, and low-end phones.
  • Ultra-mobile personal computer equipment This type of equipment belongs to the category of personal computers, has computing and processing functions, and generally has mobile Internet access.
  • Such terminals include: PDAs, MIDs, and UMPC devices, such as the iPad.
  • Portable entertainment devices These devices can display and play multimedia content. Such devices include: audio, video players (such as iPod), handheld game consoles, e-books, and smart toys and portable car navigation devices.
  • the server consists of a processor, a hard disk, a memory, a system bus, etc.
  • the server is similar to a general-purpose computer architecture, but because of the need to provide highly reliable services, processing power and stability High reliability in terms of reliability, security, scalability, and manageability.
  • the embodiment of the present application provides an electronic device, where an on-demand request for carrying an on-demand file identifier sent by a client is received and stored;
  • the embodiment of the present application provides an electronic device, where the on-demand file corresponding to each on-demand file identifier in the total on-demand request is a merged on-demand file, and the merged on-demand file includes header information and each The on-demand file identifies the corresponding on-demand file; wherein the header information includes: an on-demand file identifier of each on-demand file, and location information of each on-demand file in the merged on-demand file;
  • Each of the on-demand files obtained after parsing is sent to the client for playback.
  • the embodiment of the present application provides an electronic device, where the header information further includes: an on-demand file identifier quantity;
  • Parsing the merged on-demand file according to the header information, and obtaining an on-demand file corresponding to each on-demand file identifier specifically:
  • the on-demand file is obtained according to the on-demand file identification and location information of the on-demand file.
  • the embodiment of the present application provides an electronic device, where each of the on-demand requests of the client stored in the preset duration is merged into a total on-demand request.
  • the on-demand request includes the on-demand file identifier of each on-demand request, and specifically includes:
  • Generating a total on-demand request carrying the total on-demand file identification information so that the server proxy performs the following operations: acquiring, according to the preset on-demand file identifier splitter, the respective on-demand file identifiers from the total on-demand file request, and generating The decomposed on-demand request of each on-demand file identifier is sent to the on-demand server.
  • the embodiment of the present application provides an electronic device, where the number of the on-demand requests sent by the client stored in the preset duration is calculated, which specifically includes:
  • the embodiment of the present application provides an electronic device, wherein the at least one processor is capable of:
  • Each received on-demand file is sent to the client agent, so that the client agent sends each on-demand file to the client for playing.
  • the embodiment of the present application provides an electronic device, where sending the received on-demand files to the client agent, specifically includes:
  • the merged on-demand file includes the header information and the on-demand file corresponding to each on-demand file identifier; wherein the header information includes: an on-demand file identifier of each on-demand file, Location information of each on-demand file in the merged on-demand file;
  • the embodiment of the present application provides an electronic device, where the header information further includes: an on-demand file identifier number.
  • the embodiment of the present application provides an electronic device, where the total on-demand request includes total on-demand file identification information, where the total on-demand file identification information includes each on-demand file identifier and is used to set a preset on-demand file identifier separator between two adjacent on-demand file identifiers;
  • Decomposing the total on-demand request to obtain a decomposed on-demand request corresponding to each on-demand file identifier specifically including:
  • each on-demand file identifier from the total on-demand file request according to the preset on-demand file identifier splitter, and generating a decomposed on-demand request corresponding to each on-demand file identifier.
  • the device embodiments described above are merely illustrative, wherein the units described as separate components may or may not be physically separate, and the components displayed as units may or may not be physical units, ie may be located A place, or it can be distributed to multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of the embodiment.

Landscapes

  • Engineering & Computer Science (AREA)
  • Multimedia (AREA)
  • Signal Processing (AREA)
  • Databases & Information Systems (AREA)
  • Human Computer Interaction (AREA)
  • Software Systems (AREA)
  • Information Transfer Between Computers (AREA)
  • Two-Way Televisions, Distribution Of Moving Picture Or The Like (AREA)

Abstract

本申请实施例提供点播方法、装置、电子设备及系统。本申请实施例中,通过将客户端预设时长内的点播请求合并生成一个总点播请求,使得在客户端请求播放多个点播文件时,通过网络传输的点播请求仅有一个。这样,能够减少通过网络传输点播请求的数量,从而节省网络资源。另外,现有技术中,传输一个点播请求、传输失败的概率较低,若多个点播请求中有一个传输失败的可能性则较高。本申请实施例中通过将多个点播请求合并成一个点播请求在网络中传输,也能够有效避免网络状态不好时容易导致现有技术中有些点播请求无法传输而导致通信失败的情况发生,从而能够提高通信的稳定性。

Description

点播方法、装置、电子设备及系统
本申请要求在2016年04月20日提交中国专利局、申请号为201610248835.8、申请名称为“点播方法、装置及系统”的中国专利申请的优先权,该申请的全部内容通过引用结合在本申请中。
技术领域
本申请涉及多媒体信息处理技术领域,尤其涉及点播方法、装置、电子设备及系统。
背景技术
随着网络的发展及多媒体资源的不断丰富,点播成为用户越来越喜欢的功能。
随着生活节奏的加快,一些用户为了节约时间,喜欢在同一客户端播放多个点播文件,以便于同时了解多个点播文件的信息。而现有技术中,则针对每个点播文件客户端均会发送一个携带点播文件标识的点播请求,点播服务器针对每个点播文件请求都必须有响应。这样,若同一客户端若要播放10个点播文件,则需要发送10个点播请求,通信网络需要将这10个点播请求一一发送给点播服务器。点播服务器需要针对每个点播请求一一作出响应,并将响应结果通过网络传输给客户端。这样,当客户端请求播放多个点播文件时,客户端和点播服务器的交互次数会较多。网络传输的请求数量和响应数量也越来越多。对于网络状态不好的情况,例如客户端处于不停的移动状态,网络状态不稳定的情况下,难免有些点播请求得不到响应。故此,交互次数较多不仅浪费网络资源,也会由于网络不稳定性,容易导致通信失败。
发明内容
本申请提供点播方法、装置、电子设备及系统,用以解决目前由于同一客户端请求播放多个点播文件时,交互次数较多浪费网络资源,也会由于网络不稳定性,容易导致通信失败等的问题。
本申请实施例提供的具体技术方案如下:
第一方面,本申请实施例提供一种点播方法,所述方法包括:
客户端代理接收客户端发送的携带点播文件标识的点播请求并存储;
计算预设时长内存储的所述客户端发送的点播请求的数量,并判断该数量是否大于或等于二;
若是,则将所述预设时长内存储的所述客户端的各点播请求合并成一个总点播请求,所述总点播请求中包括各点播请求的点播文件标识;
将所述总点播请求发送给点播服务器的服务器代理,以使所述服务代理从所述点播服务器中获取所述总点播请求中的各点播文件标识对应的点播文件;
接收所述服务器代理发送的所述总点播请求中的各点播文件标识对应的点播文件,并发送给所述客户端播放。
第二方面,本申请实施例提供一种点播方法,所述方法包括:
服务器代理接收客户端代理发送的总点播请求,所述总点播请求由同一客户端发送的至少两个点播请求合并而成,且所述点播请求中包括各点播请求的点播文件标识;
将所述总点播请求进行分解,获得各点播文件标识对应的分解后点播请求,并发送给点播服务器;
接收点播服务器针对每个分解后点播请求返回的点播文件;
将接收的各点播文件发送给所述客户端代理,以使所述客户端代理将各点播文件发送给所述客户端播放。
第三方面,本发明实施例提供一种点播装置,所述装置包括:
点播请求存储模块,用于接收客户端发送的携带点播文件标识的点播请求并存储;
点播请求数量判断模块,用于计算预设时长内存储的所述客户端发送的点播请求的数量,并判断该数量是否大于或等于二;
点播请求合并模块,用于若点播请求数量判断模块的判断结果为是,则将所述预设时长内存储的所述客户端的各点播请求合并成一个总点播请求,所述总点播请求中包括各点播请求的点播文件标识;
总点播请求发送模块,用于将所述总点播请求发送给点播服务器的服务器代理,以使所述服务代理从所述点播服务器中获取所述总点播请求中的 各点播文件标识对应的点播文件;
点播文件处理模块,用于接收所述服务器代理发送的所述总点播请求中的各点播文件标识对应的点播文件,并发送给所述客户端播放。
第四方面,本申请实施例提供一种点播装置,所述装置包括:
总点播请求接收模块,用于接收客户端代理发送的总点播请求,所述总点播请求由同一客户端发送的至少两个点播请求合并而成,且所述点播请求中包括各点播请求的点播文件标识;
总点播请求分解模块,用于将所述总点播请求进行分解,获得各点播文件标识对应的分解后点播请求,并发送给点播服务器;
点播文件获取模块,用于接收点播服务器针对每个分解后点播请求返回的点播文件;
点播文件处理模块,用于将接收的各点播文件发送给所述客户端代理,以使所述客户端代理将各点播文件发送给所述客户端播放。
第五方面,本申请实施例提供一种点播系统,所述系统包括:
客户端,用于发送携带点播文件标识的点播文件请求给客户端代理,并接收客户端代理发送的点播文件进行播放;
客户端代理,用于接收客户端发送的携带点播文件标识的点播请求并存储;计算预设时长内存储的所述客户端发送的点播请求的数量,并判断该数量是否大于或等于二;若是,则将所述预设时长内存储的所述客户端的各点播请求合并成一个总点播请求,所述总点播请求中包括各点播请求的点播文件标识;将所述总点播请求发送给点播服务器的服务器代理;接收所述服务器代理发送的所述总点播请求中的各点播文件标识对应的点播文件,并发送给所述客户端播放;
服务器代理,用于接收客户端代理发送的总点播请求,所述总点播请求由同一客户端发送的至少两个点播请求合并而成,且所述点播请求中包括各点播请求的点播文件标识;将所述总点播请求进行分解,获得各点播文件标识对应的分解后点播请求,并发送给点播服务器;接收点播服务器针对每个分解后点播请求返回的点播文件;将接收的各点播文件发送给所述客户端代理,以使所述客户端代理将各点播文件发送给所述客户端播放;
点播服务器,用于接收服务器代理发送的分解后点播请求,并返回相应的点播文件。
第六方面,本申请实施例还提供了一种非易失性计算机存储介质,存储有计算机可执行指令,所述计算机可执行指令用于执行本申请上述任一项点播方法。
第七方面,本申请实施例还提供了一种电子设备,包括:至少一个处理器;以及存储器;其中,所述存储器存储有可被所述至少一个处理器执行的程序,所述指令被所述至少一个处理器执行,以使所述至少一个处理器能够执行本申请上述任一项点播方法。
第八方面,本申请实施例还提供了一种计算机程序产品,所述计算机程序产品包括存储在非暂态计算机可读存储介质上的计算程序,所述计算机程序包括程序指令,当所述程序指令被计算机执行时,使所述计算机执行权利要求任一项点播方法。
本申请实施例中,通过将客户端预设时长内的点播请求合并生成一个总点播请求,使得在客户端请求播放多个点播文件时,通过网络传输的点播请求仅有一个。这样,能够减少通过网络传输点播请求的数量,从而节省网络资源。另外,现有技术中,传输一个点播请求、传输失败的概率较低,若多个点播请求中有一个传输失败的可能性则较高。本申请实施例中通过将多个点播请求合并成一个点播请求在网络中传输,也能够有效避免网络状态不好时容易导致现有技术中有些点播请求无法传输而导致通信失败的情况发生,从而能够提高通信的稳定性。
附图说明
一个或多个实施例通过与之对应的附图中的图片进行示例性说明,这些示例性说明并不构成对实施例的限定,附图中具有相同参考数字标号的元件表示为类似的元件,除非有特别申明,附图中的图不构成比例限制。
图1为本申请实施例一中点播方法的示例性流程图;
图2为本申请实施例二中点播方法的示例性流程图;
图3为本申请实施例三中点播装置的结构示意图;
图4为本申请实施例四中点播装置的结构示意图;
图5为本申请实施例五中点播系统的结构示意图;
图6是本申请实施例七提供的执行点播方法的设备的硬件结构示意 图。
具体实施方式
为使本申请实施例的目的、技术方案和优点更加清楚,下面将结合本申请实施例中的附图,对本申请实施例中的技术方案进行清楚、完整地描述,显然,所描述的实施例是本申请一部分实施例,而不是全部的实施例。基于本申请中的实施例,本领域普通技术人员在没有作出创造性劳动前提下所获得的所有其他实施例,都属于本申请保护的范围。
实施例一
如图1所示为本申请实施例提供的点播方法的流程示意图,适用于客户端代理,包括以下步骤:
步骤101:客户端代理接收客户端发送的携带点播文件标识的点播请求并存储。
其中,在一个实施例中,点播服务器用于提供点播文件,而其中的点播文件标识,例如是点播文件ID(IDentity,标识号码)、点播文件路径或点播文件名称等。
步骤102:计算预设时长内存储的所述客户端发送的点播请求的数量,并判断该数量是否大于或等于二。
步骤103:若是,则将所述预设时长内存储的所述客户端的各点播请求合并成一个总点播请求,所述总点播请求中包括各点播请求的点播文件标识。
例如,预设时长内存储的客户端的点播请求为3个,分别为请求点播文件1、点播文件2和点播文件3的点播请求,则客户端代理,将存储的这三个点播请求进行合并,生成一个携带点播文件1、点播文件2和点播文件3的点播文件标识的总点播请求。
其中,在一个实施例中,若步骤102的判断结果为否(即点播请求的数量小于2),可以参照现有技术处理,本申请实施例对此不做赘述。
步骤104:将所述总点播请求发送给点播服务器的服务器代理,以使所述服务代理从所述点播服务器中获取所述总点播请求中的各点播文件标识对应的点播文件。
步骤105:接收所述服务器代理发送的所述总点播请求中的各点播文 件标识对应的点播文件,并发送给所述客户端播放。
这样,本申请实施例中,通过将客户端预设时长内的点播请求合并生成一个总点播请求,使得在客户端请求播放多个点播文件时,通过网络传输的点播请求仅有一个(即总点播请求)。这样,能够减少通过网络传输点播请求的数量,从而节省网络资源。另外,现有技术中,传输一个点播请求、传输失败的概率较低,若多个点播请求中有一个传输失败的可能性则较高。本申请实施例中通过将多个点播请求合并成一个点播请求在网络中传输,也能够有效避免网络状态不好容易导致现有技术中有些点播请求无法传输而导致通信失败的情况发生,从而能够提高通信的稳定性。
为便于进一步理解,下面对本申请实施例提供的点播方法做进一步说明,包括:
1)、针对步骤202:
其中,在一个实施例中,为便于计算点播请求的数量,本申请实施例中步骤102中计算预设时长内存储的所述客户端发送的点播请求的数量,可具体包括以下步骤:
步骤A1:接收到第一个点播请求后开始计时,并设置点播请求的数量为1。
其中,在一个实施例中,第一个点播请求指若一定时间段内未接收到客户端发送的点播请求,该一定时间段之后接收到的该客户端发送的第一个点播请求。例如,一定时间段为5分钟,则若5分钟内没有收到客户端发送的点播请求,则在5分钟之后收到的第一个点播请求即为步骤A1中的第一个点播请求。
当然,客户端与点播服务器建立连接后发送的第一个点播请求,也算作步骤A1中的第一个点播请求。
步骤A2:在开始计时后的预设时长内每接收到一个所述客户端发送的点播请求后,将所述点播请求的数量累加1。
其中,在一个实施例中,为了尽快处理点播请求,以避免用户感知获取点播文件的速度慢,本申请实施例中,预设时长可以为1秒,当然具体实施时,用户可以根据实际需要设定预设时长,本申请实施例对此不做限定。
其中,在一个实施例中,上述步骤A1-步骤A2中是接收到第一个点播 请求开始计时,并确定预设时长。具体实施时,本申请实施例中,还可以将时间提前划分为一个个时间段,每个时间段为一个预设时长。例如,客户端与点播服务器建立连接后为第一个预设时长的开始,从而确定出各个时间段作为预设时长。
其中,在一个实施例中,也可以以预设时长为单位存储客户端的点播请求,不采用累加的方式计算点播请求的数量,而在最后统计一下预设时长内所述客户端发送的点播请求的数量。
2)、针对步骤103:
其中,在一个实施例中,为便于服务器代理能够识别总点播请求是请求哪些点播文件,且为了服务器代理从点播服务器中获取客户端请求的各点播文件时,不对点播服务器进行修改,本申请实施例中步骤103可具体包括以下步骤:
步骤B1:在相邻两点播文件标识之间插入一个预设点播文件标识分割符,生成总点播文件标识信息。
其中,在一个实施例中,预设点播文件标识分割符可以为“,”或者“/”等,当然,能够使得服务器代理能够识别为预设点播文件标识分割符均适用于本申请实施例,本申请对此不做限定。
步骤B2:生成携带所述总点播文件标识信息的总点播请求,以使所述服务器代理执行以下操作:根据所述预设点播文件标识分割符从所述总点播文件请求中获取各点播文件标识,生成针对各点播文件标识的分解后点播请求并发送给点播服务器。
这样,通过预设点播文件标识分割符,使得服务器代理能够识别各个点播文件标识,从而生成针对每个点播文件标识的分解后点播请求发送给点播服务器,使得点播服务器可以按照现有的点播请求处理,而无需对点播服务器进行更改。
其中,在一个实施例中,本申请实施例中还可以根据以下方法合并各点播请求生成总点播请求,具体的:在相邻点播请求之间添加点播请求分割符,相当于将点播请求串联起来生成总点播请求。这样,服务器代理可以根据点播请求分割符分解出各个点播请求发送给点播服务器,也能达到同样的效果。
3)、针对步骤105:
其中,在一个实施例中,本申请实施例中,服务器代理可以将点播服务器针对每个分解后点播请求返回的点播文件逐一发送给客户端代理。这样,客户端代理相当于实现有多少个点播请求,就有多少个响应。本申请实施例中,为便于进一步减少交互次数,提高传输的稳定性,点播服务器返回的各个点播文件可以为合并后的合并点播文件,这样,通过网络只需要传输一个合并点播文件即可(即做一次响应即可),而无需针对每个点播文件传输一次。具体的:
所述总点播请求中的各点播文件标识对应的点播文件为合并点播文件,所述合并点播文件中包括头信息和各点播文件标识对应的点播文件;其中,所述头信息中包括:每个点播文件的点播文件标识、每个点播文件在所述合并点播文件中的位置信息;则步骤105,具体可包括以下步骤:
步骤C1:接收所述合并点播文件,并根据所述头信息解析所述合并点播文件,获得每个点播文件标识对应的点播文件。
其中,在一个实施例中,位置信息包括每个点播文件的起始位置和结束位置。这样,针对每个点播文件,根据该点播文件的点播文件标识及其对应位置信息,便可以得到该点播文件。
步骤C2:将解析后获得的各点播文件发送给所述客户端播放。
其中,在一个实施例中,为便于确认合并点播文件信息是否全面,所述头信息中还包括:点播文件标识数量,则步骤C1可具体包括以下步骤:
步骤D1:确认头信息中的点播文件标识数量与点播文件标识的总数是否相同。
步骤D2:若相同,针对每个点播文件,根据该点播文件的点播文件标识及位置信息得到该点播文件。
其中,在一个实施例中,若不相同,则说明反馈的合并点播文件有误,可以反馈错误信息给服务器代理,以便重传数据。
其中,在一个实施例中,头信息中的点播文件标识数量还可以便于客户端确定需要分解出多少点播文件,以便于客户端代理分配存储空间。
综上,本申请实施例中,可以将客户端的多个点播请求合并后得到一个总点播请求在网络中传输,也可以将多个点播请求的点播文件合并成一个合并点播文件在网络中传输。这样,原本在现有技术中需要的多次传输和交互,只需要1次交互便可完成,能够节省网络资源。此外,由于1次 交互失败的概率低,还能够提高通信的稳定性。
实施例二
基于相同的发明构思,本申请实施例还提供一种点播方法,适用于服务器代理。如图2所示,为该方法的流程示意图,可包括以下步骤:
步骤201:服务器代理接收客户端代理发送的总点播请求,所述总点播请求由同一客户端发送的至少两个点播请求合并而成,且所述点播请求中包括各点播请求的点播文件标识。
其中,总点播请求由客户端代理生成,其生成方法已在实施例一中说明,在此不再赘述。
步骤202:将所述总点播请求进行分解,获得各点播文件标识对应的分解后点播请求,并发送给点播服务器。
步骤203:接收点播服务器针对每个分解后点播请求返回的点播文件。
步骤204:将接收的各点播文件发送给所述客户端代理,以使所述客户端代理将各点播文件发送给所述客户端播放。
这样,本申请实施例中,服务器代理接收的是客户端代理发送的由至少两个点播请求合成的一个总点播请求。使得在客户端请求播放多个点播文件时,通过网络传输的点播请求仅有一个(即总点播请求)。这样,能够减少通过网络传输点播请求的数量,从而减少交互次数,节省网络资源。另外,现有技术中,传输一个点播请求、传输失败的概率较低,若多个点播请求中有一个传输失败的可能性则较高,本申请实施例中通过将多个点播请求合并成一个点播请求在网络中传输,也能够有效避免网络状态不好导致现有技术中有些点播请求无法传输而导致通信失败的情况发生,从而能够提高通信的稳定性。
为便于进一步理解,下面对本申请实施例提供的点播方法做进一步说明,包括:
本申请实施例中,为便于进一步减少网络传输响应的次数,即以便于进一步减少交互次数,本申请实施例中,步骤204中将接收的各点播文件发送给所述客户端代理,可具体包括以下步骤:
步骤F1:将接收的各点播文件进行合并生成合并点播文件,所述合并点播文件中包括头信息和各点播文件标识对应的点播文件;其中,所述头信息中包括:每个点播文件的点播文件标识、每个点播文件在所述合并点 播文件中的位置信息。
步骤F2:将所述合并点播文件发送给所述客户端代理。
这样,将合并点播文件发送给客户端代理,从而实现原本需要针对每个点播文件请求发送一次的点播文件,实现一起发送,从而实现原本现有技术需要的多次交互,只需要一次即可完成,从而进一步减少交互次数,提高通信稳定性。
其中,在一个实施例中,所述头信息中还包括:点播文件标识数量,以便于客户端代理根据头信息中的点播文件标识数量,以及头信息中的各点播文件标识的总数,确定点播文件是否完整。
其中,在一个实施例中,为了使点播服务器还能够按照现有的处理方式处理点播请求,而无需改造点播服务器,本申请实施例中,所述总点播请求中包括总点播文件标识信息,所述总点播文件标识信息中包括各点播文件标识和用于设置在相邻两点播文件标识之间的预设点播文件标识分割符。
步骤202中将所述总点播请求进行分解,获得各点播文件标识对应的分解后点播请求,可具体包括:根据所述预设点播文件标识分割符,从所述总点播文件请求中获取各点播文件标识,并生成各点播文件标识对应的分解后点播请求。
其中,在一个实施例中,为了便于可以满足个性化需求,客户端的点播请求中还可以包括点播文件播放优先级,而合并生成合并点播文件时,可以使优先级高的点播文件相较其他点播文件的数据量多一些,从而实现优先级高的点播文件优先传输给客户端。其中,优先级可以是用户指定的优先级。
综上,本申请实施例中,服务器代理接收的是总点播请求,该总点播请求为客户端代理将客户端的多个点播请求合并后得到的一个请求。服务器代理向客户端发送的合并点播文件,为多个点播请求的点播文件合并后得到的一个文件。这样,只需要一次交互既可以实现现有技术中多次交互的作用,减少了交互数量,节约网络资源。此外,由于1次交互失败的概率低,还能够提高通信的稳定性。
实施例三
基于相同的发明构思,本申请实施例还提供一种点播装置,如图3所 示,为该装置的结构示意图,所述装置包括:
点播请求存储模块301,用于接收客户端发送的携带点播文件标识的点播请求并存储;
点播请求数量判断模块302,用于计算预设时长内存储的所述客户端发送的点播请求的数量,并判断该数量是否大于或等于二;
点播请求合并模块303,用于若点播请求数量判断模块的判断结果为是,则将所述预设时长内存储的所述客户端的各点播请求合并成一个总点播请求,所述总点播请求中包括各点播请求的点播文件标识;
总点播请求发送模块304,用于将所述总点播请求发送给点播服务器的服务器代理,以使所述服务代理从所述点播服务器中获取所述总点播请求中的各点播文件标识对应的点播文件;
点播文件处理模块305,用于接收所述服务器代理发送的所述总点播请求中的各点播文件标识对应的点播文件,并发送给所述客户端播放。
其中,在一个实施例中,所述总点播请求中的各点播文件标识对应的点播文件为合并点播文件,所述合并点播文件中包括头信息和各点播文件标识对应的点播文件;其中,所述头信息中包括:每个点播文件的点播文件标识、每个点播文件在所述合并点播文件中的位置信息;
点播文件处理模块,具体包括:
合并点播文件解析单元,用于接收所述合并点播文件,并根据所述头信息解析所述合并点播文件,获得每个点播文件标识对应的点播文件;
点播文件发送单元,用于将解析后获得的各点播文件发送给所述客户端播放。
其中,在一个实施例中,所述头信息中还包括:点播文件标识数量;
合并点播文件解析单元,具体用于:
确认头信息中的点播文件标识数量与点播文件标识的总数是否相同;
若相同,针对每个点播文件,根据该点播文件的点播文件标识及位置信息得到该点播文件。
其中,在一个实施例中,点播请求合并模块,具体包括:
分割符插入单元,用于在相邻两点播文件标识之间插入一个预设点播文件标识分割符,生成总点播文件标识信息;
总点播请求处理单元,用于生成携带所述总点播文件标识信息的总点 播请求,以使所述服务器代理执行以下操作:根据所述预设点播文件标识分割符从所述总点播文件请求中获取各点播文件标识,生成针对各点播文件标识的分解后点播请求并发送给点播服务器。
其中,在一个实施例中,点播请求数量判断模块,具体包括:
计时单元,用于接收到第一个点播请求后开始计时,并设置点播请求的数量为1;
计算单元,用于在开始计时后的预设时长内每接收到一个所述客户端发送的点播请求后,将所述点播请求的数量累加1。
实施例四
基于相同的发明构思,本申请实施例还提供一种点播装置,如图4所示,为该装置的结构示意图,所述装置包括:
总点播请求接收模块401,用于接收客户端代理发送的总点播请求,所述总点播请求由同一客户端发送的至少两个点播请求合并而成,且所述点播请求中包括各点播请求的点播文件标识;
总点播请求分解模块402,用于将所述总点播请求进行分解,获得各点播文件标识对应的分解后点播请求,并发送给点播服务器;
点播文件获取模块403,用于接收点播服务器针对每个分解后点播请求返回的点播文件;
点播文件处理模块404,用于将接收的各点播文件发送给所述客户端代理,以使所述客户端代理将各点播文件发送给所述客户端播放。
其中,在一个实施例中,点播文件处理模块,具体包括:
合并点播文件生成单元,用于将接收的各点播文件进行合并生成合并点播文件,所述合并点播文件中包括头信息和各点播文件标识对应的点播文件;其中,所述头信息中包括:每个点播文件的点播文件标识、每个点播文件在所述合并点播文件中的位置信息;
合并点播文件生成单元发送单元,用于将所述合并点播文件发送给所述客户端代理。
其中,在一个实施例中,所述头信息中还包括:点播文件标识数量。
其中,在一个实施例中,所述总点播请求中包括总点播文件标识信息,所述总点播文件标识信息中包括各点播文件标识和用于设置在相邻两点播文件标识之间的预设点播文件标识分割符;
总点播请求分解模块,具体用于根据所述预设点播文件标识分割符,从所述总点播文件请求中获取各点播文件标识,并生成各点播文件标识对应的分解后点播请求。
实施例五
基于相同的发明构思,本申请实施例还提供一种点播系统,如图5所示,为该系统的结构示意图,所述系统包括:
客户端501,用于发送携带点播文件标识的点播文件请求给客户端代理,并接收客户端代理发送的点播文件进行播放;
客户端代理502,于接收客户端发送的携带点播文件标识的点播请求并存储;计算预设时长内存储的所述客户端发送的点播请求的数量,并判断该数量是否大于或等于二;若是,则将所述预设时长内存储的所述客户端的各点播请求合并成一个总点播请求,所述总点播请求中包括各点播请求的点播文件标识;将所述总点播请求发送给点播服务器的服务器代理;接收所述服务器代理发送的所述总点播请求中的各点播文件标识对应的点播文件,并发送给所述客户端播放;
服务器代理503,用于接收客户端代理发送的总点播请求,所述总点播请求由同一客户端发送的至少两个点播请求合并而成,且所述点播请求中包括各点播请求的点播文件标识;将所述总点播请求进行分解,获得各点播文件标识对应的分解后点播请求,并发送给点播服务器;接收点播服务器针对每个分解后点播请求返回的点播文件;将接收的各点播文件发送给所述客户端代理,以使所述客户端代理将各点播文件发送给所述客户端播放;
点播服务器504,用于接收服务器代理发送的分解后点播请求,并返回相应的点播文件。
关于上述实施例中的装置,其中各个模块执行操作的具体方式已经在有关该方法的实施例中进行了详细描述,此处将不做详细阐述说明。
实施例六
本申请实施例六提供了一种非易失性计算机存储介质,所述计算机存储介质存储有计算机可执行指令,该计算机可执行指令可执行上述实施例一和/或实施例二中的点播方法。
在一种可能的实施方式中,本申请实施例提供的非易失性计算机存储 介质,其中,存储有计算机可执行指令,所述计算机可执行指令设置为:
接收客户端发送的携带点播文件标识的点播请求并存储;
计算预设时长内存储的所述客户端发送的点播请求的数量,并判断该数量是否大于或等于二;
若是,则将所述预设时长内存储的所述客户端的各点播请求合并成一个总点播请求,所述总点播请求中包括各点播请求的点播文件标识;
将所述总点播请求发送给点播服务器的服务器代理,以使所述服务代理从所述点播服务器中获取所述总点播请求中的各点播文件标识对应的点播文件;
接收所述服务器代理发送的所述总点播请求中的各点播文件标识对应的点播文件,并发送给所述客户端播放。
在一种可能的实施方式中,本申请实施例提供的非易失性计算机存储介质,其中,所述总点播请求中的各点播文件标识对应的点播文件为合并点播文件,所述合并点播文件中包括头信息和各点播文件标识对应的点播文件;其中,所述头信息中包括:每个点播文件的点播文件标识、每个点播文件在所述合并点播文件中的位置信息;
接收所述服务器代理发送的所述总点播请求中的各点播文件标识对应的点播文件,并发送给所述客户端播放,具体包括:
接收所述合并点播文件,并根据所述头信息解析所述合并点播文件,获得每个点播文件标识对应的点播文件;
将解析后获得的各点播文件发送给所述客户端播放。
在一种可能的实施方式中,本申请实施例提供的非易失性计算机存储介质,其中,所述头信息中还包括:点播文件标识数量;
根据所述头信息解析所述合并点播文件,获得每个点播文件标识对应的点播文件,具体包括:
确认头信息中的点播文件标识数量与点播文件标识的总数是否相同;
若相同,针对每个点播文件,根据该点播文件的点播文件标识及位置信息得到该点播文件。
在一种可能的实施方式中,本申请实施例提供的非易失性计算机存储介质,其中,将所述预设时长内存储的所述客户端的各点播请求合并成一个总点播请求,所述总点播请求中包括各点播请求的点播文件标识,具体 包括:
在相邻两点播文件标识之间插入一个预设点播文件标识分割符,生成总点播文件标识信息;
生成携带所述总点播文件标识信息的总点播请求,以使所述服务器代理执行以下操作:根据所述预设点播文件标识分割符从所述总点播文件请求中获取各点播文件标识,生成针对各点播文件标识的分解后点播请求并发送给点播服务器。
在一种可能的实施方式中,本申请实施例提供的非易失性计算机存储介质,其中,计算预设时长内存储的所述客户端发送的点播请求的数量,具体包括:
接收到第一个点播请求后开始计时,并设置点播请求的数量为1;并,
在开始计时后的预设时长内每接收到一个所述客户端发送的点播请求后,将所述点播请求的数量累加1。
此外,在一种可能的实施方式中,本申请实施例提供非易失性计算机存储介质,其中,接收客户端代理发送的总点播请求,所述总点播请求由同一客户端发送的至少两个点播请求合并而成,且所述点播请求中包括各点播请求的点播文件标识;
将所述总点播请求进行分解,获得各点播文件标识对应的分解后点播请求,并发送给点播服务器;
接收点播服务器针对每个分解后点播请求返回的点播文件;
将接收的各点播文件发送给所述客户端代理,以使所述客户端代理将各点播文件发送给所述客户端播放。
在一种可能的实施方式中,本申请实施例提供非易失性计算机存储介质,其中,将接收的各点播文件发送给所述客户端代理,具体包括:
将接收的各点播文件进行合并生成合并点播文件,所述合并点播文件中包括头信息和各点播文件标识对应的点播文件;其中,所述头信息中包括:每个点播文件的点播文件标识、每个点播文件在所述合并点播文件中的位置信息;
将所述合并点播文件发送给所述客户端代理。
在一种可能的实施方式中,本申请实施例提供非易失性计算机存储介质,其中,所述头信息中还包括:点播文件标识数量。
在一种可能的实施方式中,本申请实施例提供非易失性计算机存储介质,其中,所述总点播请求中包括总点播文件标识信息,所述总点播文件标识信息中包括各点播文件标识和用于设置在相邻两点播文件标识之间的预设点播文件标识分割符;
将所述总点播请求进行分解,获得各点播文件标识对应的分解后点播请求,具体包括:
根据所述预设点播文件标识分割符,从所述总点播文件请求中获取各点播文件标识,并生成各点播文件标识对应的分解后点播请求。
实施例七
图6是本申请实施例七提供的执行点播方法的电子设备的硬件结构示意图,如图6所示,该设备包括:
一个或多个处理器610以及存储器620,图6中以一个处理器610为例。
执行点播处理方法的设备还可以包括:输入装置630和输出装置640。
处理器610、存储器620、输入装置630和输出装置640可以通过总线或者其他方式连接,图6中以通过总线连接为例。
存储器620作为一种非易失性计算机可读存储介质,可用于存储非易失性软件程序、非易失性计算机可执行程序以及模块,如本申请实施例中的点播方法对应的程序指令/模块(例如,附图3所示的点播请求存储模块301、点播请求数量判断模块302、点播请求合并模块303、总点播请求发送模块304和点播文件处理模块305;和/或,附图4中所示的总点播请求接收模块401、总点播请求分解模块402、点播文件获取模块403、点播文件处理模块404)。处理器610通过运行存储在存储器620中的非易失性软件程序、指令以及模块,从而执行服务器的各种功能应用以及数据处理,即实现上述方法实施例一和/或实施例二中的点播方法。
存储器620可以包括存储程序区和存储数据区,其中,存储程序区可存储操作系统、至少一个功能所需要的应用程序;存储数据区可存储根据点播装置的使用所创建的数据等。此外,存储器620可以包括高速随机存 取存储器,还可以包括非易失性存储器,例如至少一个磁盘存储器件、闪存器件、或其他非易失性固态存储器件。在一些实施例中,存储器620可选包括相对于处理器610远程设置的存储器,这些远程存储器可以通过网络连接至点播装置。上述网络的实例包括但不限于互联网、企业内部网、局域网、移动通信网及其组合。
输入装置630可接收输入的数字或字符信息,以及产生与点播处理装置的用户设置以及功能控制有关的键信号输入。输出装置640可包括显示屏等显示设备。
所述一个或者多个模块存储在所述存储器620中,当被所述一个或者多个处理器610执行时,执行上述方法实施例一和/或实施例二中的点播方法。
上述产品可执行本申请实施例所提供的方法,具备执行方法相应的功能模块和有益效果。未在本实施例中详尽描述的技术细节,可参见本申请实施例所提供的方法。
本申请实施例的电子设备以多种形式存在,包括但不限于:
(1)移动通信设备:这类设备的特点是具备移动通信功能,并且以提供话音、数据通信为主要目标。这类终端包括:智能手机(例如iPhone)、多媒体手机、功能性手机,以及低端手机等。
(2)超移动个人计算机设备:这类设备属于个人计算机的范畴,有计算和处理功能,一般也具备移动上网特性。这类终端包括:PDA、MID和UMPC设备等,例如iPad。
(3)便携式娱乐设备:这类设备可以显示和播放多媒体内容。该类设备包括:音频、视频播放器(例如iPod),掌上游戏机,电子书,以及智能玩具和便携式车载导航设备。
(4)服务器:提供计算服务的设备,服务器的构成包括处理器、硬盘、内存、系统总线等,服务器和通用的计算机架构类似,但是由于需要提供高可靠的服务,因此在处理能力、稳定性、可靠性、安全性、可扩展性、可管理性等方面要求较高。
(5)其他具有数据交互功能的电子装置。
在一种可能的实施方式中,本申请实施例提供电子设备,其中,接收客户端发送的携带点播文件标识的点播请求并存储;
计算预设时长内存储的所述客户端发送的点播请求的数量,并判断该数量是否大于或等于二;
若是,则将所述预设时长内存储的所述客户端的各点播请求合并成一个总点播请求,所述总点播请求中包括各点播请求的点播文件标识;
将所述总点播请求发送给点播服务器的服务器代理,以使所述服务代理从所述点播服务器中获取所述总点播请求中的各点播文件标识对应的点播文件;
接收所述服务器代理发送的所述总点播请求中的各点播文件标识对应的点播文件,并发送给所述客户端播放。
在一种可能的实施方式中,本申请实施例提供电子设备,其中,所述总点播请求中的各点播文件标识对应的点播文件为合并点播文件,所述合并点播文件中包括头信息和各点播文件标识对应的点播文件;其中,所述头信息中包括:每个点播文件的点播文件标识、每个点播文件在所述合并点播文件中的位置信息;
接收所述服务器代理发送的所述总点播请求中的各点播文件标识对应的点播文件,并发送给所述客户端播放,具体包括:
接收所述合并点播文件,并根据所述头信息解析所述合并点播文件,获得每个点播文件标识对应的点播文件;
将解析后获得的各点播文件发送给所述客户端播放。
在一种可能的实施方式中,本申请实施例提供电子设备,其中,所述头信息中还包括:点播文件标识数量;
根据所述头信息解析所述合并点播文件,获得每个点播文件标识对应的点播文件,具体包括:
确认头信息中的点播文件标识数量与点播文件标识的总数是否相同;
若相同,针对每个点播文件,根据该点播文件的点播文件标识及位置信息得到该点播文件。
在一种可能的实施方式中,本申请实施例提供电子设备,其中,将所述预设时长内存储的所述客户端的各点播请求合并成一个总点播请求,所 述总点播请求中包括各点播请求的点播文件标识,具体包括:
在相邻两点播文件标识之间插入一个预设点播文件标识分割符,生成总点播文件标识信息;
生成携带所述总点播文件标识信息的总点播请求,以使所述服务器代理执行以下操作:根据所述预设点播文件标识分割符从所述总点播文件请求中获取各点播文件标识,生成针对各点播文件标识的分解后点播请求并发送给点播服务器。
在一种可能的实施方式中,本申请实施例提供电子设备,其中,计算预设时长内存储的所述客户端发送的点播请求的数量,具体包括:
接收到第一个点播请求后开始计时,并设置点播请求的数量为1;并,
在开始计时后的预设时长内每接收到一个所述客户端发送的点播请求后,将所述点播请求的数量累加1。
在一种可能的实施方式中,本申请实施例提供电子设备,其中,所述至少一个处理器能够:
接收客户端代理发送的总点播请求,所述总点播请求由同一客户端发送的至少两个点播请求合并而成,且所述点播请求中包括各点播请求的点播文件标识;
将所述总点播请求进行分解,获得各点播文件标识对应的分解后点播请求,并发送给点播服务器;
接收点播服务器针对每个分解后点播请求返回的点播文件;
将接收的各点播文件发送给所述客户端代理,以使所述客户端代理将各点播文件发送给所述客户端播放。
在一种可能的实施方式中,本申请实施例提供电子设备,其中,将接收的各点播文件发送给所述客户端代理,具体包括:
将接收的各点播文件进行合并生成合并点播文件,所述合并点播文件中包括头信息和各点播文件标识对应的点播文件;其中,所述头信息中包括:每个点播文件的点播文件标识、每个点播文件在所述合并点播文件中的位置信息;
将所述合并点播文件发送给所述客户端代理。
在一种可能的实施方式中,本申请实施例提供电子设备,其中,所述头信息中还包括:点播文件标识数量。
在一种可能的实施方式中,本申请实施例提供电子设备,其中,所述总点播请求中包括总点播文件标识信息,所述总点播文件标识信息中包括各点播文件标识和用于设置在相邻两点播文件标识之间的预设点播文件标识分割符;
将所述总点播请求进行分解,获得各点播文件标识对应的分解后点播请求,具体包括:
根据所述预设点播文件标识分割符,从所述总点播文件请求中获取各点播文件标识,并生成各点播文件标识对应的分解后点播请求。
以上所描述的装置实施例仅仅是示意性的,其中所述作为分离部件说明的单元可以是或者也可以不是物理上分开的,作为单元显示的部件可以是或者也可以不是物理单元,即可以位于一个地方,或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部模块来实现本实施例方案的目的。
通过以上的实施方式的描述,本领域的技术人员可以清楚地了解到各实施方式可借助软件加通用硬件平台的方式来实现,当然也可以通过硬件。基于这样的理解,上述技术方案本质上或者说对相关技术做出贡献的部分可以以软件产品的形式体现出来,该计算机软件产品可以存储在计算机可读存储介质中,如ROM/RAM、磁碟、光盘等,包括若干指令用以使得一台计算机设备(可以是个人计算机,服务器,或者网络设备等)执行各个实施例或者实施例的某些部分所述的方法。
最后应说明的是:以上实施例仅用以说明本申请的技术方案,而非对其限制;尽管参照前述实施例对本申请进行了详细的说明,本领域的普通技术人员应当理解:其依然可以对前述各实施例所记载的技术方案进行修改,或者对其中部分技术特征进行等同替换;而这些修改或者替换,并不使相应技术方案的本质脱离本申请各实施例技术方案的精神和范围。

Claims (39)

  1. 一种点播方法,应用于电子设备,其特征在于,所述方法包括:
    客户端代理接收客户端发送的携带点播文件标识的点播请求并存储;
    计算预设时长内存储的所述客户端发送的点播请求的数量,并判断该数量是否大于或等于二;
    若是,则将所述预设时长内存储的所述客户端的各点播请求合并成一个总点播请求,所述总点播请求中包括各点播请求的点播文件标识;
    将所述总点播请求发送给点播服务器的服务器代理,以使所述服务代理从所述点播服务器中获取所述总点播请求中的各点播文件标识对应的点播文件;
    接收所述服务器代理发送的所述总点播请求中的各点播文件标识对应的点播文件,并发送给所述客户端播放。
  2. 根据权利要求1所述的方法,其特征在于,所述总点播请求中的各点播文件标识对应的点播文件为合并点播文件,所述合并点播文件中包括头信息和各点播文件标识对应的点播文件;其中,所述头信息中包括:每个点播文件的点播文件标识、每个点播文件在所述合并点播文件中的位置信息;
    接收所述服务器代理发送的所述总点播请求中的各点播文件标识对应的点播文件,并发送给所述客户端播放,具体包括:
    接收所述合并点播文件,并根据所述头信息解析所述合并点播文件,获得每个点播文件标识对应的点播文件;
    将解析后获得的各点播文件发送给所述客户端播放。
  3. 根据权利要求2所述的方法,其特征在于,所述头信息中还包括:点播文件标识数量;
    根据所述头信息解析所述合并点播文件,获得每个点播文件标识对应的点播文件,具体包括:
    确认头信息中的点播文件标识数量与点播文件标识的总数是否相同;
    若相同,针对每个点播文件,根据该点播文件的点播文件标识及位置信息得到该点播文件。
  4. 根据权利要求1所述的方法,其特征在于,将所述预设时长内存储的所述客户端的各点播请求合并成一个总点播请求,所述总点播请求中包 括各点播请求的点播文件标识,具体包括:
    在相邻两点播文件标识之间插入一个预设点播文件标识分割符,生成总点播文件标识信息;
    生成携带所述总点播文件标识信息的总点播请求,以使所述服务器代理执行以下操作:根据所述预设点播文件标识分割符从所述总点播文件请求中获取各点播文件标识,生成针对各点播文件标识的分解后点播请求并发送给点播服务器。
  5. 根据权利要求1-4中任一所述的方法,其特征在于,计算预设时长内存储的所述客户端发送的点播请求的数量,具体包括:
    接收到第一个点播请求后开始计时,并设置点播请求的数量为1;并,
    在开始计时后的预设时长内每接收到一个所述客户端发送的点播请求后,将所述点播请求的数量累加1。
  6. 一种点播方法,其特征在于,所述方法包括:
    服务器代理接收客户端代理发送的总点播请求,所述总点播请求由同一客户端发送的至少两个点播请求合并而成,且所述点播请求中包括各点播请求的点播文件标识;
    将所述总点播请求进行分解,获得各点播文件标识对应的分解后点播请求,并发送给点播服务器;
    接收点播服务器针对每个分解后点播请求返回的点播文件;
    将接收的各点播文件发送给所述客户端代理,以使所述客户端代理将各点播文件发送给所述客户端播放。
  7. 根据权利要求6所述的方法,其特征在于,将接收的各点播文件发送给所述客户端代理,具体包括:
    将接收的各点播文件进行合并生成合并点播文件,所述合并点播文件中包括头信息和各点播文件标识对应的点播文件;其中,所述头信息中包括:每个点播文件的点播文件标识、每个点播文件在所述合并点播文件中的位置信息;
    将所述合并点播文件发送给所述客户端代理。
  8. 根据权利要求7所述的方法,其特征在于,所述头信息中还包括:点播文件标识数量。
  9. 根据权利要求6-8中任一所述的方法,其特征在于,所述总点播请 求中包括总点播文件标识信息,所述总点播文件标识信息中包括各点播文件标识和用于设置在相邻两点播文件标识之间的预设点播文件标识分割符;
    将所述总点播请求进行分解,获得各点播文件标识对应的分解后点播请求,具体包括:
    根据所述预设点播文件标识分割符,从所述总点播文件请求中获取各点播文件标识,并生成各点播文件标识对应的分解后点播请求。
  10. 一种非易失性计算机存储介质,其特征在于,存储有计算机可执行指令,所述计算机可执行指令设置为:
    接收客户端发送的携带点播文件标识的点播请求并存储;
    计算预设时长内存储的所述客户端发送的点播请求的数量,并判断该数量是否大于或等于二;
    若是,则将所述预设时长内存储的所述客户端的各点播请求合并成一个总点播请求,所述总点播请求中包括各点播请求的点播文件标识;
    将所述总点播请求发送给点播服务器的服务器代理,以使所述服务代理从所述点播服务器中获取所述总点播请求中的各点播文件标识对应的点播文件;
    接收所述服务器代理发送的所述总点播请求中的各点播文件标识对应的点播文件,并发送给所述客户端播放。
  11. 根据权利要求10所述的非易失性计算机存储介质,其特征在于,所述总点播请求中的各点播文件标识对应的点播文件为合并点播文件,所述合并点播文件中包括头信息和各点播文件标识对应的点播文件;其中,所述头信息中包括:每个点播文件的点播文件标识、每个点播文件在所述合并点播文件中的位置信息;
    接收所述服务器代理发送的所述总点播请求中的各点播文件标识对应的点播文件,并发送给所述客户端播放,具体包括:
    接收所述合并点播文件,并根据所述头信息解析所述合并点播文件,获得每个点播文件标识对应的点播文件;
    将解析后获得的各点播文件发送给所述客户端播放。
  12. 根据权利要求11所述的非易失性计算机存储介质,其特征在于,所述头信息中还包括:点播文件标识数量;
    根据所述头信息解析所述合并点播文件,获得每个点播文件标识对应的点播文件,具体包括:
    确认头信息中的点播文件标识数量与点播文件标识的总数是否相同;
    若相同,针对每个点播文件,根据该点播文件的点播文件标识及位置信息得到该点播文件。
  13. 根据权利要求10所述的非易失性计算机存储介质,其特征在于,将所述预设时长内存储的所述客户端的各点播请求合并成一个总点播请求,所述总点播请求中包括各点播请求的点播文件标识,具体包括:
    在相邻两点播文件标识之间插入一个预设点播文件标识分割符,生成总点播文件标识信息;
    生成携带所述总点播文件标识信息的总点播请求,以使所述服务器代理执行以下操作:根据所述预设点播文件标识分割符从所述总点播文件请求中获取各点播文件标识,生成针对各点播文件标识的分解后点播请求并发送给点播服务器。
  14. 根据权利要求10-13中任一所述的非易失性计算机存储介质,其特征在于,计算预设时长内存储的所述客户端发送的点播请求的数量,具体包括:
    接收到第一个点播请求后开始计时,并设置点播请求的数量为1;并,
    在开始计时后的预设时长内每接收到一个所述客户端发送的点播请求后,将所述点播请求的数量累加1。
  15. 一种电子设备,其特征在于,包括:
    至少一个处理器;以及,
    与所述至少一个处理器通信连接的存储器;其中,
    所述存储器存储有可被所述至少一个处理器执行的指令,所述指令被所述至少一个处理器执行,以使所述至少一个处理器能够:
    接收客户端发送的携带点播文件标识的点播请求并存储;
    计算预设时长内存储的所述客户端发送的点播请求的数量,并判断该数量是否大于或等于二;
    若是,则将所述预设时长内存储的所述客户端的各点播请求合并成一个总点播请求,所述总点播请求中包括各点播请求的点播文件标识;
    将所述总点播请求发送给点播服务器的服务器代理,以使所述服务代 理从所述点播服务器中获取所述总点播请求中的各点播文件标识对应的点播文件;
    接收所述服务器代理发送的所述总点播请求中的各点播文件标识对应的点播文件,并发送给所述客户端播放。
  16. 根据权利要求15所述的电子设备,其特征在于,所述总点播请求中的各点播文件标识对应的点播文件为合并点播文件,所述合并点播文件中包括头信息和各点播文件标识对应的点播文件;其中,所述头信息中包括:每个点播文件的点播文件标识、每个点播文件在所述合并点播文件中的位置信息;
    接收所述服务器代理发送的所述总点播请求中的各点播文件标识对应的点播文件,并发送给所述客户端播放,具体包括:
    接收所述合并点播文件,并根据所述头信息解析所述合并点播文件,获得每个点播文件标识对应的点播文件;
    将解析后获得的各点播文件发送给所述客户端播放。
  17. 根据权利要求16所述的电子设备,其特征在于,所述头信息中还包括:点播文件标识数量;
    根据所述头信息解析所述合并点播文件,获得每个点播文件标识对应的点播文件,具体包括:
    确认头信息中的点播文件标识数量与点播文件标识的总数是否相同;
    若相同,针对每个点播文件,根据该点播文件的点播文件标识及位置信息得到该点播文件。
  18. 根据权利要求15所述的电子设备,其特征在于,将所述预设时长内存储的所述客户端的各点播请求合并成一个总点播请求,所述总点播请求中包括各点播请求的点播文件标识,具体包括:
    在相邻两点播文件标识之间插入一个预设点播文件标识分割符,生成总点播文件标识信息;
    生成携带所述总点播文件标识信息的总点播请求,以使所述服务器代理执行以下操作:根据所述预设点播文件标识分割符从所述总点播文件请求中获取各点播文件标识,生成针对各点播文件标识的分解后点播请求并发送给点播服务器。
  19. 根据权利要求15-18中任一所述的电子设备,其特征在于,计算 预设时长内存储的所述客户端发送的点播请求的数量,具体包括:
    接收到第一个点播请求后开始计时,并设置点播请求的数量为1;并,
    在开始计时后的预设时长内每接收到一个所述客户端发送的点播请求后,将所述点播请求的数量累加1。
  20. 一种非易失性计算机存储介质,其特征在于,存储有计算机可执行指令,所述计算机可执行指令设置为:
    接收客户端代理发送的总点播请求,所述总点播请求由同一客户端发送的至少两个点播请求合并而成,且所述点播请求中包括各点播请求的点播文件标识;
    将所述总点播请求进行分解,获得各点播文件标识对应的分解后点播请求,并发送给点播服务器;
    接收点播服务器针对每个分解后点播请求返回的点播文件;
    将接收的各点播文件发送给所述客户端代理,以使所述客户端代理将各点播文件发送给所述客户端播放。
  21. 根据权利要求20所述的非易失性计算机存储介质,其特征在于,将接收的各点播文件发送给所述客户端代理,具体包括:
    将接收的各点播文件进行合并生成合并点播文件,所述合并点播文件中包括头信息和各点播文件标识对应的点播文件;其中,所述头信息中包括:每个点播文件的点播文件标识、每个点播文件在所述合并点播文件中的位置信息;
    将所述合并点播文件发送给所述客户端代理。
  22. 根据权利要求21所述的非易失性计算机存储介质,其特征在于,所述头信息中还包括:点播文件标识数量。
  23. 根据权利要求20-22中任一所述的非易失性计算机存储介质,其特征在于,所述总点播请求中包括总点播文件标识信息,所述总点播文件标识信息中包括各点播文件标识和用于设置在相邻两点播文件标识之间的预设点播文件标识分割符;
    将所述总点播请求进行分解,获得各点播文件标识对应的分解后点播请求,具体包括:
    根据所述预设点播文件标识分割符,从所述总点播文件请求中获取各点播文件标识,并生成各点播文件标识对应的分解后点播请求。
  24. 一种电子设备,其特征在于,包括:
    至少一个处理器;以及,
    与所述至少一个处理器通信连接的存储器;其中,
    所述存储器存储有可被所述至少一个处理器执行的指令,所述指令被所述至少一个处理器执行,以使所述至少一个处理器能够:
    接收客户端代理发送的总点播请求,所述总点播请求由同一客户端发送的至少两个点播请求合并而成,且所述点播请求中包括各点播请求的点播文件标识;
    将所述总点播请求进行分解,获得各点播文件标识对应的分解后点播请求,并发送给点播服务器;
    接收点播服务器针对每个分解后点播请求返回的点播文件;
    将接收的各点播文件发送给所述客户端代理,以使所述客户端代理将各点播文件发送给所述客户端播放。
  25. 根据权利要求24所述的电子设备,其特征在于,将接收的各点播文件发送给所述客户端代理,具体包括:
    将接收的各点播文件进行合并生成合并点播文件,所述合并点播文件中包括头信息和各点播文件标识对应的点播文件;其中,所述头信息中包括:每个点播文件的点播文件标识、每个点播文件在所述合并点播文件中的位置信息;
    将所述合并点播文件发送给所述客户端代理。
  26. 根据权利要求25所述的电子设备,其特征在于,所述头信息中还包括:点播文件标识数量。
  27. 根据权利要求24-26中任一所述的电子设备,其特征在于,所述总点播请求中包括总点播文件标识信息,所述总点播文件标识信息中包括各点播文件标识和用于设置在相邻两点播文件标识之间的预设点播文件标识分割符;
    将所述总点播请求进行分解,获得各点播文件标识对应的分解后点播请求,具体包括:
    根据所述预设点播文件标识分割符,从所述总点播文件请求中获取各点播文件标识,并生成各点播文件标识对应的分解后点播请求。
  28. 一种计算机程序产品,其特征在于,所述计算机程序产品包括存 储在非暂态计算机可读存储介质上的计算程序,所述计算机程序包括程序指令,当所述程序指令被计算机执行时,使所述计算机执行权利要求1-5所述的方法。
  29. 一种点播装置,其特征在于,所述装置包括:
    点播请求存储模块,用于接收客户端发送的携带点播文件标识的点播请求并存储;
    点播请求数量判断模块,用于计算预设时长内存储的所述客户端发送的点播请求的数量,并判断该数量是否大于或等于二;
    点播请求合并模块,用于若点播请求数量判断模块的判断结果为是,则将所述预设时长内存储的所述客户端的各点播请求合并成一个总点播请求,所述总点播请求中包括各点播请求的点播文件标识;
    总点播请求发送模块,用于将所述总点播请求发送给点播服务器的服务器代理,以使所述服务代理从所述点播服务器中获取所述总点播请求中的各点播文件标识对应的点播文件;
    点播文件处理模块,用于接收所述服务器代理发送的所述总点播请求中的各点播文件标识对应的点播文件,并发送给所述客户端播放。
  30. 根据权利要求29所述的装置,其特征在于,所述总点播请求中的各点播文件标识对应的点播文件为合并点播文件,所述合并点播文件中包括头信息和各点播文件标识对应的点播文件;其中,所述头信息中包括:每个点播文件的点播文件标识、每个点播文件在所述合并点播文件中的位置信息;
    点播文件处理模块,具体包括:
    合并点播文件解析单元,用于接收所述合并点播文件,并根据所述头信息解析所述合并点播文件,获得每个点播文件标识对应的点播文件;
    点播文件发送单元,用于将解析后获得的各点播文件发送给所述客户端播放。
  31. 根据权利要求30所述的装置,其特征在于,所述头信息中还包括:点播文件标识数量;
    合并点播文件解析单元,具体用于:
    确认头信息中的点播文件标识数量与点播文件标识的总数是否相同;
    若相同,针对每个点播文件,根据该点播文件的点播文件标识及位置 信息得到该点播文件。
  32. 根据权利要求29所述的装置,其特征在于,点播请求合并模块,具体包括:
    分割符插入单元,用于在相邻两点播文件标识之间插入一个预设点播文件标识分割符,生成总点播文件标识信息;
    总点播请求处理单元,用于生成携带所述总点播文件标识信息的总点播请求,以使所述服务器代理执行以下操作:根据所述预设点播文件标识分割符从所述总点播文件请求中获取各点播文件标识,生成针对各点播文件标识的分解后点播请求并发送给点播服务器。
  33. 根据权利要求29-32中任一所述的装置,其特征在于,点播请求数量判断模块,具体包括:
    计时单元,用于接收到第一个点播请求后开始计时,并设置点播请求的数量为1;
    计算单元,用于在开始计时后的预设时长内每接收到一个所述客户端发送的点播请求后,将所述点播请求的数量累加1。
  34. 一种点播装置,其特征在于,所述装置包括:
    总点播请求接收模块,用于接收客户端代理发送的总点播请求,所述总点播请求由同一客户端发送的至少两个点播请求合并而成,且所述点播请求中包括各点播请求的点播文件标识;
    总点播请求分解模块,用于将所述总点播请求进行分解,获得各点播文件标识对应的分解后点播请求,并发送给点播服务器;
    点播文件获取模块,用于接收点播服务器针对每个分解后点播请求返回的点播文件;
    点播文件处理模块,用于将接收的各点播文件发送给所述客户端代理,以使所述客户端代理将各点播文件发送给所述客户端播放。
  35. 根据权利要求34所述的装置,其特征在于,点播文件处理模块,具体包括:
    合并点播文件生成单元,用于将接收的各点播文件进行合并生成合并点播文件,所述合并点播文件中包括头信息和各点播文件标识对应的点播文件;其中,所述头信息中包括:每个点播文件的点播文件标识、每个点播文件在所述合并点播文件中的位置信息;
    合并点播文件生成单元发送单元,用于将所述合并点播文件发送给所述客户端代理。
  36. 根据权利要求35所述的装置,其特征在于,所述头信息中还包括:点播文件标识数量。
  37. 根据权利要求34-36中任一所述的装置,其特征在于,所述总点播请求中包括总点播文件标识信息,所述总点播文件标识信息中包括各点播文件标识和用于设置在相邻两点播文件标识之间的预设点播文件标识分割符;
    总点播请求分解模块,具体用于根据所述预设点播文件标识分割符,从所述总点播文件请求中获取各点播文件标识,并生成各点播文件标识对应的分解后点播请求。
  38. 一种计算机程序产品,其特征在于,所述计算机程序产品包括存储在非暂态计算机可读存储介质上的计算程序,所述计算机程序包括程序指令,当所述程序指令被计算机执行时,使所述计算机执行权利要求6-9所述的方法。
  39. 一种点播系统,其特征在于,所述系统包括:
    客户端,用于发送携带点播文件标识的点播文件请求给客户端代理,并接收客户端代理发送的点播文件进行播放;
    客户端代理,用于接收客户端发送的携带点播文件标识的点播请求并存储;计算预设时长内存储的所述客户端发送的点播请求的数量,并判断该数量是否大于或等于二;若是,则将所述预设时长内存储的所述客户端的各点播请求合并成一个总点播请求,所述总点播请求中包括各点播请求的点播文件标识;将所述总点播请求发送给点播服务器的服务器代理;接收所述服务器代理发送的所述总点播请求中的各点播文件标识对应的点播文件,并发送给所述客户端播放;
    服务器代理,用于接收客户端代理发送的总点播请求,所述总点播请求由同一客户端发送的至少两个点播请求合并而成,且所述点播请求中包括各点播请求的点播文件标识;将所述总点播请求进行分解,获得各点播文件标识对应的分解后点播请求,并发送给点播服务器;接收点播服务器针对每个分解后点播请求返回的点播文件;将接收的各点播文件发送给所述客户端代理,以使所述客户端代理将各点播文件发送给所述客户端播放;
    点播服务器,用于接收服务器代理发送的分解后点播请求,并返回相应的点播文件。
PCT/CN2016/100437 2016-04-20 2016-09-27 点播方法、装置、电子设备及系统 WO2017181602A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201610248835.8A CN105933728A (zh) 2016-04-20 2016-04-20 点播方法、装置及系统
CN201610248835.8 2016-04-20

Publications (1)

Publication Number Publication Date
WO2017181602A1 true WO2017181602A1 (zh) 2017-10-26

Family

ID=56839332

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2016/100437 WO2017181602A1 (zh) 2016-04-20 2016-09-27 点播方法、装置、电子设备及系统

Country Status (2)

Country Link
CN (1) CN105933728A (zh)
WO (1) WO2017181602A1 (zh)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105933728A (zh) * 2016-04-20 2016-09-07 乐视控股(北京)有限公司 点播方法、装置及系统
CN113126920A (zh) * 2021-04-02 2021-07-16 深圳市杉岩数据技术有限公司 对象存储批量读取及写入方法、客户端、存储网关及介质

Citations (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101202896A (zh) * 2007-10-17 2008-06-18 杭州华三通信技术有限公司 视频点播方法、视频数据发送方法、服务器及节目源设备
CN102025784A (zh) * 2010-12-21 2011-04-20 中兴通讯股份有限公司 一种流媒体文件的下载方法、装置及系统
CN102291324A (zh) * 2011-06-28 2011-12-21 北京神州泰岳软件股份有限公司 高并发业务请求处理方法
CN102387206A (zh) * 2011-10-20 2012-03-21 镇江睿泰信息科技有限公司 一种Web服务并发请求合成方法及系统
CN102547408A (zh) * 2012-01-17 2012-07-04 深圳市同洲视讯传媒有限公司 播放点播节目的方法、系统和会话管理器
CN103458318A (zh) * 2013-07-26 2013-12-18 深圳市融创天下科技股份有限公司 媒体数据传输方法及系统
CN103747285A (zh) * 2013-12-27 2014-04-23 乐视网信息技术(北京)股份有限公司 一种节目播放方法和服务端、客户端
CN104283800A (zh) * 2013-07-05 2015-01-14 株式会社日立制作所 网关装置、通信系统以及流量控制方法
US20150142917A1 (en) * 2013-11-19 2015-05-21 Samsung Electronics Co., Ltd. Server, user terminal apparatus, and method for providing streaming data service
CN105847386A (zh) * 2016-04-20 2016-08-10 乐视控股(北京)有限公司 直播流的处理方法、装置及系统
CN105933728A (zh) * 2016-04-20 2016-09-07 乐视控股(北京)有限公司 点播方法、装置及系统

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9553912B2 (en) * 2011-01-19 2017-01-24 Electronics And Telecommunications Research Institute Method and apparatus for transmitting media content via a single port or multiple ports
CN102904918B (zh) * 2011-07-28 2017-06-09 腾讯科技(北京)有限公司 网络媒介信息的展示处理方法和系统

Patent Citations (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101202896A (zh) * 2007-10-17 2008-06-18 杭州华三通信技术有限公司 视频点播方法、视频数据发送方法、服务器及节目源设备
CN102025784A (zh) * 2010-12-21 2011-04-20 中兴通讯股份有限公司 一种流媒体文件的下载方法、装置及系统
CN102291324A (zh) * 2011-06-28 2011-12-21 北京神州泰岳软件股份有限公司 高并发业务请求处理方法
CN102387206A (zh) * 2011-10-20 2012-03-21 镇江睿泰信息科技有限公司 一种Web服务并发请求合成方法及系统
CN102547408A (zh) * 2012-01-17 2012-07-04 深圳市同洲视讯传媒有限公司 播放点播节目的方法、系统和会话管理器
CN104283800A (zh) * 2013-07-05 2015-01-14 株式会社日立制作所 网关装置、通信系统以及流量控制方法
CN103458318A (zh) * 2013-07-26 2013-12-18 深圳市融创天下科技股份有限公司 媒体数据传输方法及系统
US20150142917A1 (en) * 2013-11-19 2015-05-21 Samsung Electronics Co., Ltd. Server, user terminal apparatus, and method for providing streaming data service
CN103747285A (zh) * 2013-12-27 2014-04-23 乐视网信息技术(北京)股份有限公司 一种节目播放方法和服务端、客户端
CN105847386A (zh) * 2016-04-20 2016-08-10 乐视控股(北京)有限公司 直播流的处理方法、装置及系统
CN105933728A (zh) * 2016-04-20 2016-09-07 乐视控股(北京)有限公司 点播方法、装置及系统

Also Published As

Publication number Publication date
CN105933728A (zh) 2016-09-07

Similar Documents

Publication Publication Date Title
WO2017181601A1 (zh) 直播流的处理方法、装置、电子设备及系统
US9467650B2 (en) Method and apparatus for transmitting media stream in video conference
US10569169B2 (en) Data processing method and apparatus for network system
US20220249959A1 (en) Method and system for managing multiplayer game sessions
WO2017185616A1 (zh) 文件存储方法及电子设备
CN108452525B (zh) 一种游戏中聊天信息的监控方法及系统
CN101622587B (zh) 用于唤醒计算设备的集中式服务
WO2014183427A1 (en) Method and apparatus for displaying webcast rooms
US20170171585A1 (en) Method and Electronic Device for Recording Live Streaming Media
US20170171571A1 (en) Push Video Documentation Methods and Appliances
JP6655093B2 (ja) 部分的セグメント用の表示
WO2017107831A1 (zh) 一种基于应用软件实现播报的方法、装置及电子设备
WO2019205555A1 (zh) 消息推送方法及装置
CN109451076B (zh) 一种网络请求的合并处理方法、装置及电子设备
US20240009578A1 (en) Data matching method and apparatus, device and computer-readable storage medium
WO2018000692A1 (zh) 数据同步方法、系统及用于数据同步的用户终端和服务端
WO2012031511A1 (zh) 管理消息的方法和装置
WO2017181602A1 (zh) 点播方法、装置、电子设备及系统
JP2018514108A (ja) 部分的セグメント用の表示
WO2023005199A1 (zh) 数据处理方法及装置
CN109413455B (zh) 一种用于语音连麦互动的用户信息显示方法及装置
US20170155739A1 (en) Advertisement data processing method and router
US20170171339A1 (en) Advertisement data transmission method, electrnoic device and system
WO2012139351A1 (zh) 第三方iptv业务的推送方法及系统
WO2016197955A1 (zh) 多媒体流组播方法和装置

Legal Events

Date Code Title Description
NENP Non-entry into the national phase

Ref country code: DE

121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 16899187

Country of ref document: EP

Kind code of ref document: A1

122 Ep: pct application non-entry in european phase

Ref document number: 16899187

Country of ref document: EP

Kind code of ref document: A1