System and method for playlist generation

The system uses unique keys to manage stream segments in live streaming, ensuring efficient and rapid generation of playlist files for complete distribution playback, addressing the challenge of integrating segments across unstable internet connections.

JP2024161844AActive Publication Date: 2024-11-2017LIVE JAPAN INC
View PDF 4 Cites 0 Cited by

Patent Information

Application Number
JP2023076940
Authority / Receiving Office
JP · JP
Patent Type
Applications
Current Assignee / Owner
Filing Date
2023-05-08
Publication Date
2024-11-20
Estimated Expiration
2043-05-08

AI Technical Summary

Technical Problem

Existing live streaming systems struggle with integrating separate stream segments into a complete playback file when internet connectivity is unstable, leading to inefficient and time-consuming uploading of segments to different cloud spaces, resulting in the inability to generate a cohesive playback file.

Method used

A system and method that utilizes unique keys based on distributor and stream IDs to store stream portions in the same cloud space, ensuring consistency and integrity of stream segments, allowing simultaneous or parallel processing to dynamically generate playlist files, and update them upon internet disconnections.

Benefits of technology

Enables efficient and rapid generation of playlist files for complete distribution playback, ensuring all stream parts are stored in the same cloud space, facilitating seamless integration and dynamic updates, thus ensuring uninterrupted and synchronized playback.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 2024161844000001_ABST
    Figure 2024161844000001_ABST
Patent Text Reader

Abstract

To provide a system and a method for playlist generation.SOLUTION: A method includes the steps of: acquiring first information on a stream part and a unique key from a first streaming server; determining that a first set of the stream part stored on a space of a cloud server coincides with the first stream part information, and designating an address of the space by the unique key; generating a playlist file on the basis of the first stream part information; acquiring second stream part information and the unique key from a second streaming server; determining that a second set of the stream part stored on the space of the cloud server coincides with the second stream part information; and updating the playlist file on the basis of the second stream part information.SELECTED DRAWING: Figure 11
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

[0001] The present invention relates to the generation of playlists in the streaming field. [Background technology]

[0002] As exemplified by live streaming services, real-time communication over the Internet has become a part of everyday life. A variety of platforms and providers offer live streaming services, and competition is fierce. It is important for platforms to provide services that users want.

[0003] Taiwan Patent Application Publication No. 201445986 discloses a playlist server for accessing video data. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Taiwan Patent Application Publication No. 201445986 Summary of the Invention

[0005] A method according to one embodiment of the present invention is a method for playlist generation executed by one or more computers, comprising the steps of: obtaining first stream portion information and a unique key from a first streaming server; determining that a first set of stream portions stored on a space of a cloud server matches the first stream portion information, the space being addressable by the unique key; generating a playlist file based on the first stream portion information; obtaining second stream portion information and the unique key from a second streaming server; determining that a second set of stream portions stored on the space of the cloud server matches the second stream portion information; and updating the playlist file based on the second stream portion information.

[0006] A system according to one embodiment of the present invention is a system for playlist generation including one or more processors, the one or more computer processors executing machine-readable instructions to perform the following steps: obtaining first stream portion information and a unique key from a first streaming server; determining that a first set of stream portions stored on a space of a cloud server matches the first stream portion information, the space being addressable by the unique key; generating a playlist file based on the first stream portion information; obtaining second stream portion information and the unique key from a second streaming server; determining that a second set of stream portions stored on the space of the cloud server matches the second stream portion information; and updating the playlist file based on the second stream portion information.

[0007] A system according to an embodiment of the present invention includes a streaming server and a playlist generator, the streaming server being configured to: receive stream segments; generate a unique key based on a distributor ID and a stream ID of the stream segments; generate stream parts from the stream segments; timestamp the stream parts; send the stream parts and the unique key to a cloud space on a cloud server; and send the number of stream parts, the timestamp, and the unique key to the playlist generator. The playlist generator is configured to identify the cloud space on the cloud server with the unique key; determine the consistency of stream parts between the streaming server and the cloud space; and generate a playlist file based on the number of stream parts and the timestamp. [Brief description of the drawings]

[0008] [Figure 1]FIG. 1 is a schematic diagram showing a configuration of a live streaming system 1 according to some embodiments of the present invention. [Diagram 2] 6 is a block diagram illustrating the functionality and configuration of the user terminal 30 of FIG. 5 in accordance with some embodiments of the present invention. [Diagram 3] 2 is a block diagram illustrating the functionality and configuration of the server of FIG. 1 in accordance with some embodiments of the present invention. [Figure 4] 4 is a table showing an example data structure of the stream DB 310 of FIG. 3. [Diagram 5] 4 is a table illustrating an example data structure of the user DB 312 of FIG. 3. [Figure 6] 4 is a table showing an example data structure of the gift DB 314 of FIG. 3. [Figure 7] 1 is an exemplary flowchart illustrating a method according to the related art. [Figure 8] FIG. 2 is an exemplary sequence diagram illustrating a method according to some embodiments of the present invention. [Figure 9] FIG. 2 is an exemplary sequence diagram illustrating a method according to some embodiments of the present invention. [Figure 10] 4 is an exemplary data structure according to some embodiments of the present invention. [Figure 11] 1 is an exemplary flow chart illustrating a method according to some embodiments of the present invention. [Figure 12] 1 is an exemplary flow chart illustrating a method according to some embodiments of the present invention. [Figure 13] 1 is a block diagram showing an example of a hardware configuration of an information processing device according to some embodiments of the present invention. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0009] Hereinafter, the same or similar components, parts, steps, or signals shown in each drawing will be denoted by the same reference numerals in all drawings, and duplicated explanations will be omitted as appropriate. In addition, some parts that are not important in the explanation of each drawing will be omitted.

[0010] In a streaming system (or archive system) of related technology that the present inventors independently created for comparison with the present invention, when the Internet connection becomes unstable (or intermittent), the broadcast by the broadcaster (or streamer) is divided into separate segments. Alternatively, when the broadcaster jumps into a group call broadcast (or accepts an invitation to a group call broadcast) during his / her broadcast, the stream segment before the group call and the stream segment after the group call are cut into separate segments.

[0011] The different segments cannot be integrated into a complete stream in the correct order. A playback or playlist file for the complete stream cannot be generated from the split segments. The different segments are sent from the streamer to different streaming servers. The different segments are sent from each streaming server and stored in different spaces (or different files) in the cloud server. The upload of each segment to its corresponding cloud space starts only after it has been completely received at the corresponding streaming server, which is time-consuming and inefficient.

[0012] FIG. 7 is an exemplary flowchart illustrating a method according to the related art.

[0013] In step S700, a distributor D1 transmits a stream segment S11 to a streaming server 362. The stream segment S11 is part of a distribution file (or distribution session) S1.

[0014] In step S702, the distributor D1 experiences an internet disconnection, so the remainder of the distribution file S1 has not yet been sent.

[0015] In step S704, the streaming server 362 generates a playback file based on the stream segment S11. A transcoding process may be performed on the stream segment S11.

[0016] In step S706, the streaming server 362 transmits the playback file to the cloud space 382 on the cloud server.

[0017] In step S708, the broadcaster D1's Internet connection is restored and the broadcaster D1 sends stream segment S12, which is part of the broadcast file S1, to the streaming server 364. Often, the broadcast is likely to be sent to a different streaming server after the Internet outage, for example due to the allocation / distribution mechanism of a load balancer (not shown).

[0018] In step S710, the distributor D1 ends the distribution.

[0019] In step S712, the streaming server 364 generates a playback file based on the stream segment S12. A transcoding process may be performed on the stream segment S12.

[0020] In step S714, the streaming server 364 sends the playback file to a cloud space 384 on the cloud server. The cloud space 384 is different from the cloud space 382 because the streaming server 364 has no way to identify the space in which the playback file of stream segment S11 is stored on the cloud server.

[0021] The stream segments S11 and S12 belong to the same distribution file (or the same distribution session) S1. However, the playback files are separate and stored in different spaces on the cloud server. The above method cannot generate an integrated playback file of the complete distribution file S1 from the separate stream segments S11 and S12.

[0022] Step S704 begins only after step S702 occurs (or S700 ends). Step S706 begins only after step S704 ends. Step S712 begins only after step S710 occurs (or S708 ends). Step S714 begins only after step S712 ends.

[0023] The present invention provides a system and method for efficiently generating playlist files and / or playback files for playback of a complete broadcast.

[0024] FIG. 1 is a schematic diagram showing a configuration of a live streaming system 1 according to some embodiments of the present invention. The live streaming system 1 provides a live streaming service for streaming distributors (also called live broadcasters, anchors, and streamers) LV and viewers (also called audiences) AU (AU1, AU2, ...) to interact or communicate in real time. As shown in FIG. 1, the live streaming system 1 includes a server 10, a user terminal 20, and a user terminal 30 (30a, 30b, ...). In some embodiments, the streamers and viewers may be collectively referred to as users. The server 10 may include one or more information processing devices connected to a network NW. The user terminals 20 and 30 may be, for example, mobile terminal devices such as smartphones, tablets, notebook PCs, recorders, portable game consoles, and wearable terminals, or stationary devices such as desktop PCs. The server 10, the user terminals 20, and the user terminals 30 are connected to each other so as to be able to communicate with each other via various wired or wireless networks NW.

[0025] The live streaming system 1 includes a distributor LV, a viewer AU, and an administrator (or an app provider, not shown) who manages the server 10. The distributor LV is a person who distributes the content in real time by recording the content on his / her user terminal 20 and uploading it directly or indirectly to the server 10. Examples of the content may be the distributor's own song, talk, performance, game play, or any other content. The administrator provides a platform for live streaming the content on the server 10, and mediates or manages real-time interactions between the distributor LV and the viewer AU. The viewer AU accesses the platform with his / her user terminal 30, selects and watches desired content. During the live streaming of the selected content, the viewer AU performs operations such as sending comments, cheers, and gifts via the user terminal 30. The distributor LV who distributes the content may respond to those comments, cheers, or gifts. The response is transmitted to the viewer AU by video and / or audio, and two-way communication is established.

[0026] The term "live streaming" may refer to a data transmission mode that allows the content recorded at the user terminal 20 of the distributor LV to be played back and viewed at the user terminal 30 of the viewer AU in substantially real time, or may refer to a live broadcast realized by such a transmission mode. The live streaming may be realized by utilizing existing live streaming technologies such as HTTP live streaming, CMAF (Common Media Application Format), WebRTC (Web Real-Time Communications), RTMP (Real-Time Messaging Protocol), MPEG DASH, etc. Live streaming includes a transmission mode that allows the viewer AU to view the content with a certain delay at the same time as the content is recorded by the distributor LV. The length of the delay may be a delay that allows interaction between the distributor LV and the viewer AU. The live streaming is distinguished from so-called on-demand distribution, in which all recorded data of the content is stored once on the server and then provided to the user from the server upon the user's request.

[0027] The term "video data" as used herein refers to data including image data (also called video data) generated using the imaging function of the user terminal 20 or 30, and audio data generated using the audio input function of the user terminal 20 or 30. The video data is played on the user terminal 20, 30 so that the user can view the content. In some embodiments, it is assumed that the video data is subjected to a process such as compression, decompression, encoding, decoding, transcoding, etc., to change its format, size, or data specifications between the generation of the video data on the distributor's user terminal and the playback of the video data on the viewer's user terminal. However, since the content (e.g., video and audio) represented by the video data does not substantially change before and after such a process, the video data after such a process is expressed in this specification as being the same as the video data before such a process. In other words, when video data is generated at the distributor's user terminal and then played at the viewer's user terminal via the server 10, the video data generated at the distributor's user terminal, the video data passing through the server 10, and the video data received and played at the viewer's user terminal are all the same video data.

[0028] In the example shown in Fig. 1, the distributor LV provides live streaming data. The user terminal 20 of the distributor LV records video and audio of the distributor LV to generate the streaming data, and the generated data is transmitted to the server 10 via the network NW. At the same time, the user terminal 20 displays the recorded video VD of the distributor LV on the display of the user terminal 20, allowing the user to check the live streaming content currently being provided by the distributor LV.

[0029] The user terminals 30a, 30b of the viewers AU1, AU2 who have requested the platform to view the live streaming of the distributor LV receive video data related to the live streaming (hereinafter, may be referred to as "live streaming video data") via the network NW, play the received video data, display the videos VD1, VD2 on the display, and output audio from the speaker. The videos VD1, VD2 displayed on the user terminals 30a, 30b are substantially the same as the video VD captured by the user terminal 20 of the distributor LV, and the audio output from the user terminals 30a, 30b is substantially the same as the audio recorded by the user terminal 20 of the distributor LV.

[0030] The recording of video and audio on the user terminal 20 of the distributor LV and the playback of video data on the user terminals 30a and 30b of the viewers AU1 and AU2 are performed substantially simultaneously. When the viewer AU1 inputs a comment on the content provided by the distributor LV to the user terminal 30a, the server 10 displays the comment on the user terminal 20 of the distributor LV in real time, and also displays the comment on the user terminals 30a and 30b of the viewers AU1 and AU2. When the distributor LV reads the comment and develops a talk corresponding to the comment, the video and audio of the talk are displayed on the user terminals 30a and 30b of the viewers AU1 and AU2, respectively. This interactive operation is recognized as a conversation being established between the distributor LV and the viewer AU1. As a result, the live streaming system 1 realizes live streaming that enables two-way communication, not one-way communication.

[0031] 2 is a block diagram showing the functions and configuration of the user terminal 30 of FIG. 1 according to some embodiments of the present invention. The user terminal 20 has the same or similar functions and configuration as the user terminal 30. Each block of FIG. 2 and the following block diagrams may be realized by hardware elements such as a computer CPU or a mechanical device, or by software elements such as a computer program. The functional blocks may be realized by the cooperation of these elements. Therefore, it will be understood by those skilled in the art that these functional blocks may be realized in various forms by combining hardware and software.

[0032] The distributor LV and the viewer AU may download a live streaming application program (hereinafter, referred to as a live streaming application) from a download site via the network NW and install it on the user terminals 20 and 30. Alternatively, the live streaming application may be pre-installed on the user terminals 20 and 30. When the live streaming application is executed on the user terminals 20 and 30, the user terminals 20 and 30 communicate with the server 10 via the network NW and implement or execute various functions. Hereinafter, functions implemented by the user terminals 20 and 30 (processors such as CPUs) on which the live streaming application is executed will be described as functions of the user terminals 20 and 30. These functions are actually realized by the live streaming application on the user terminals 20 and 30. In some embodiments, these functions may be realized by a computer program written in a programming language such as HTML (HyperText Markup Language), transmitted from the server 10 to a web browser of the user terminals 20 and 30 via the network NW, and executed by the web browser.

[0033] The user terminal 30 includes a distribution unit 100 and a viewing unit 200. The distribution unit 100 generates video data in which the video and audio of the user (or the user side) are recorded, and provides the video data to the server 10. The viewing unit 200 receives the video data from the server 10 and plays the video data. The user starts the distribution unit 100 when performing live streaming, and starts the viewing unit 200 when the user watches a video. The user terminal on which the distribution unit 100 is started is the terminal of the distributor, i.e., the user terminal that generates the video data. The user terminal on which the viewing unit 200 is started is the terminal of the viewer, i.e., the user terminal on which the video data is reproduced and played.

[0034] The delivery unit 100 includes an imaging control unit 102, an audio control unit 104, a video transmission unit 106, and a distributor-side UI control unit 108. The imaging control unit 102 is connected to a camera (not shown in FIG. 2) and controls imaging performed by the camera. The imaging control unit 102 acquires image data from the camera. The audio control unit 104 is connected to a microphone (not shown in FIG. 2) and controls audio input from the microphone. The audio control unit 104 acquires the audio data from the microphone. The video transmission unit 106 transmits the image data acquired by the imaging control unit 102 and the video data including the audio data acquired by the audio control unit 104 to the server 10 via the network NW. The video data is transmitted in real time by the video transmission unit 106. That is, the generation of the video data by the imaging control unit 102 and the audio control unit 104 and the transmission of the generated video data by the video transmission unit 106 are performed substantially simultaneously. The distributor's UI control unit 108 controls the UI (user interface) of the distributor. The distributor's UI control unit 108 may be connected to a display (not shown in FIG. 2) and displays a video on the display by playing the video data transmitted by the video transmission unit 106. The distributor's UI control unit 108 may display an operation object or an instruction permission object on the display and accept an input from the distributor who taps on the object.

[0035] The viewing unit 200 includes a viewer-side UI control unit 202, an overlay information generating unit 204, and an input information transmitting unit 206. The viewing unit 200 receives video data related to live streaming in which the distributor, the viewer who is the user of the user terminal 30, and other viewers participate from the server 10 via the network NW. The viewer-side UI control unit 202 controls the UI of the viewer. The viewer-side UI control unit 202 is connected to a display and a speaker (not shown in FIG. 2), plays the received video data, displays the video on the display, and outputs the audio from the speaker. The state in which the video is output to the display and the audio is output from the speaker can be called a "video data is being played" state. The viewer-side UI control unit 202 is also connected to an input means (not shown in FIG. 2) such as a touch panel, a keyboard, a display, etc., and acquires a user's input via the input means. The overlay information generating unit 204 overlays a predetermined frame image on an image generated from video data from the server 10. The frame image includes various user interface objects (hereinafter simply referred to as "objects") for receiving input from the user, comments entered by the viewer, and / or information acquired from the server 10. The input information transmitting unit 206 transmits the user input acquired by the viewer-side UI control unit 202 to the server 10 via the network NW.

[0036] FIG. 3 shows a block diagram illustrating the function and configuration of the server 10 of FIG. 1 according to some embodiments of the present invention. The server 10 includes a distribution information providing unit 302, a relay unit 304, a gift processing unit 306, a payment processing unit 308, a stream DB 310, a user DB 312, a gift DB 314, a playlist generating device 330, a playback file generating device 332, a playlist DB 350, and a playback file DB 352. The server 10 communicates with a streaming server 372, a streaming server 374, and a cloud server 380. In some embodiments, the streaming servers 372, 374 may be implemented in the server 10.

[0037] When a notification or request to start live streaming is received from the user terminal 20 on the distributor side via the network NW, the distribution information providing unit 302 registers in the stream DB 310 a stream ID for identifying the live streaming and the distributor ID of the distributor performing the live streaming.

[0038] When the distribution information providing unit 302 receives a request for providing information about live streams from the viewing unit 200 of the user terminal 30 on the viewer side via the network NW, the distribution information providing unit 302 obtains or checks currently available live streams from the stream DB 310, and creates a list of available live streams. The distribution information providing unit 302 transmits the created list to the requesting user terminal 30 via the network NW. The viewer side UI control unit 202 of the requesting user terminal 30 generates a live stream selection screen based on the received list, and displays it on the display of the user terminal 30.

[0039] When the input information sending unit 206 of the user terminal 30 receives the selection result of the viewer on the live stream selection screen, the input information sending unit 206 generates a delivery request including the stream ID of the selected live stream and sends the request to the server 10 via the network NW. The delivery information providing unit 302 starts providing the live stream specified by the stream ID included in the received delivery request to the requesting user terminal 30. The delivery information providing unit 302 updates the stream DB 310 so that the viewer ID of (or the corresponding) the stream ID includes the user ID of the viewer of the requesting user terminal 30.

[0040] The relay unit 304 relays the video data from the user terminal 20 on the distributor side to the user terminal 30 on the viewer side in the live streaming started by the distribution information providing unit 302. The relay unit 304 receives a signal representing a user input by a viewer from the input information transmitting unit 206 during the live streaming or during playback of the video data. The signal representing the user input may be an object designation signal that designates an object displayed on the display of the user terminal 30. The object designation signal may include a viewer ID of the viewer, a distributor ID of the distributor of the live stream that the viewer is viewing, and an object ID that identifies the object. When the object is a gift, the object ID is a gift ID. Similarly, the relay unit 304 receives a signal representing a user input made by a distributor during playback (or live streaming) of the video data from the distribution unit 100 of the user terminal 20. The signal may be an object designation signal.

[0041] Furthermore, the signal representing the user input may be a comment input signal including a comment input by a viewer to the user terminal 30 and the viewer ID of the viewer. Upon receiving the comment input signal, the relay unit 304 transmits the comment and the viewer ID included in the signal to the user terminal 20 of the distributor and the user terminals 30 of other viewers. In these user terminals 20, 30, the viewer-side UI control unit 202 and the overlay information generation unit 204 display the received comment on a display associated with the viewer ID that has also been received.

[0042] The gift processing unit 306 increases the points of the distributor based on the points of the gift specified by the gift ID included in the object designation signal, and updates the user DB 312. Specifically, the gift processing unit 306 refers to the gift DB 314 to specify the points to be given to the gift ID included in the received object designation signal. Then, the gift processing unit 306 updates the user DB 312 and adds the specified points to the points of the distributor ID (or corresponding to the distributor ID) included in the object designation signal.

[0043] In response to receiving the object designation signal, the payment processing unit 308 processes the payment of the gift from the viewer. Specifically, the payment processing unit 308 refers to the gift DB 314 to determine the price points of the gift identified by the gift ID included in the object designation signal. Then, the payment processing unit 308 updates the user DB 312 and subtracts the determined price points from the points of the viewer identified by the viewer ID included in the object designation signal.

[0044] FIG. 4 is a table showing an exemplary data structure of the stream DB 310 of FIG. 3. The stream DB 310 holds information about a live stream currently being performed. The stream DB 310 stores a stream ID, a broadcaster ID, and a viewer ID in a mutually associated manner. The stream ID is an ID for identifying a live stream in a live streaming platform provided by the live streaming system 1. The broadcaster ID is a user ID for identifying a broadcaster providing the live stream. The viewer ID is a user ID for identifying a viewer of the live stream. In a live streaming platform provided by the live streaming system 1 according to some embodiments, when a user starts a live stream, the user becomes a broadcaster, and when the same user watches a live stream broadcasted by another user, the user also becomes a viewer. Therefore, the distinction between a broadcaster and a viewer is not fixed, and a user ID registered as a broadcaster ID at one time may be registered as a viewer ID at another time.

[0045] FIG. 5 is a table showing an exemplary data structure of the user DB 312 of FIG. 3. The user DB 312 holds information about users. The user DB 312 stores the user ID and the points in a mutually associated manner. The user ID identifies a user. The points correspond to points held by the corresponding user. The points are electronic value circulated within the live streaming platform. In some embodiments, when a broadcaster receives a gift from a viewer during a live stream, the broadcaster's points are increased by a value corresponding to the gift. The points are used, for example, to determine the amount of compensation (such as money) that the broadcaster receives from the administrator of the live streaming platform. In some embodiments, when the broadcaster receives a gift from a viewer, an amount corresponding to the gift may be given instead of the points.

[0046] FIG. 6 is a table showing an exemplary data structure of the gift DB 314 of FIG. 3. The gift DB 314 holds information about gifts available to the viewer during the live streaming. Gifts are electronic data. Gifts may be purchased with points or money, or may be provided free of charge. Gifts may be given to the broadcaster by the viewer. Giving a gift to the broadcaster is also called using a gift, sending a gift, throwing a gift, etc. Some gifts can be used immediately after purchase, while others can be used at any time after purchase by the viewer who purchased the gift. When a viewer gives a gift to a broadcaster, the broadcaster is given an amount of points corresponding to the gift. When a gift is used, an effect related to the gift may occur as a result of the use. For example, an effect (such as a visual effect or an auditory effect) corresponding to the gift is displayed on the live streaming screen.

[0047] The gift DB 314 stores a gift ID, an assignment point, and a price point in association with each other. The gift ID is for identifying a gift. The assignment point is the amount of points that is assigned to a broadcaster when the gift is given to the broadcaster. The price point is the amount of points paid for the use (purchase) of the gift. A viewer can give a desired gift to a broadcaster by paying the price points of the desired gift while watching a live stream. The payment of the price points can be made by an appropriate electronic payment means. For example, the viewer may pay the price points to the administrator. Alternatively, payment by bank transfer or credit card may be used. The administrator can arbitrarily set the relationship between the assignment points and the price points. For example, it may be set as assignment points = price points. Alternatively, it may be set as the price points obtained by multiplying the assignment points by a predetermined coefficient such as 1.2, or as the price points obtained by adding a predetermined fee point to the assignment points.

[0048] The streaming server (372 or 374) is configured to receive a distribution file (video or audio distribution file) from a user. The streaming server may receive a distribution file from a user terminal of a distributor. A distribution file is a complete distribution (or distribution session) and corresponds to one distributor ID and one stream ID. The streaming server may receive the distributor ID and the stream ID together with the distribution file (or a segment of the distribution file). For each distribution file, a unique key may be generated based on the distributor ID and the stream ID. The unique key corresponds to the distribution file. In some embodiments, the streaming server receives the unique key together with the distribution file. In some embodiments, the streaming server generates the unique key when receiving a distribution file. In some embodiments, a distribution file is defined by a distribution start action (or start signal) from the distributor and a distribution end action (or end signal) from the distributor.

[0049] During reception of the distribution file, the streaming server (372 or 374) serially (or in parallel) converts the received portions of the distribution file into stream portions. In some embodiments, the conversion process may involve transcoding. In some embodiments, it may have a Transport Stream (TS) format. In some embodiments, a stream portion may be a portion split off from the distribution file. The streaming server generates and appends a timestamp to each stream portion.

[0050] In some embodiments, the streaming server may generate a folder (or space, or file) in the streaming server and store the stream portion (or the converted stream portion) in the folder. The folder is generated based on the unique key. The folder corresponds to the unique key. For the same distribution file, the stream portion generated on one streaming server (372 or 374) is stored in the same folder on the streaming server.

[0051] While converting the distribution file into the stream portions, the streaming server (372 or 374) serially (or in parallel) transmits the stream portions (or converted stream portions) and their respective timestamps to a cloud space on the cloud server 380. The cloud space is specified by the unique key. The cloud space uniquely corresponds to the unique key. Stream portions corresponding to the same unique key are sent to the same cloud space. The streaming server may transfer the first portion (or converted portion) of the distribution file to a cloud space while generating (or converting) the second portion of the distribution file.

[0052] In some embodiments, the streaming server transfers or updates the folder (where the stream parts are stored) to the cloud space of the cloud server. The cloud space may thus be specified by the unique key corresponding to the folder. In some embodiments, the folder may be a temporary folder that is deleted after all stream parts have been sent to the cloud server.

[0053] The streaming server (372 or 374) is configured to send stream portion information of the stream portions stored on the streaming server to the playlist generator 330. The stream portion information may include a number of the stream portions, their respective timestamps, and a unique key.

[0054] The playlist generating device 330 is configured to generate a playlist file for the distribution file. The playlist generating device 330 compares or synchronizes the stream parts stored in the streaming server with the stream parts transferred or updated (and stored) in the cloud space. The playlist generating device 330 determines or checks whether the stream parts on the streaming server and the stream parts updated in the cloud space are consistent. The playlist generating device 330 generates the playlist file based on the stream part information received from the streaming server. The generated playlist file is stored in the playlist DB 350 and uploaded to the cloud space.

[0055] The playback file generator 332 is updated to generate a playback file for a distribution file. The playback file generator 332 may receive stream parts from a streaming server, and generate a complete playback file using the corresponding playlist file and the stream parts. The playback file generator 332 may perform transcoding on the stream parts to generate a playback file having a format required by a party (e.g., a user or client of a streaming platform). The generated playback file may be stored in the playback file DB 352 and uploaded to the cloud server 380.

[0056] In some embodiments, the cloud server 380 may be a Google GCS server. In some embodiments, the cloud server 380 may be an Amazon S3 server.

[0057] 8 and 9 are exemplary sequence diagrams illustrating methods according to some embodiments of the present invention.

[0058] In step S800, the distributor D1 sends a stream segment S11 to the streaming server 372. The stream segment S11 is part of a distribution file (or distribution session) S1. The user ID of the distributor D1 and the stream ID of the distribution file S1 are also sent to the streaming server 372.

[0059] In step S802, the streaming server 372 generates a unique key based on the user ID and the stream ID, and creates a temporary folder (or space, or file) on the streaming server 372 based on the unique key.

[0060] Then the flow enters a loop L1 where a TS file (or a stream part) is generated and uploaded to the cloud server.

[0061] In step S804, the streaming server 372 generates a TS file S111 and adds a timestamp to it. The TS file S111 is generated from the stream segment S11. Transcoding and video splitting processes may be included. The TS file S111 is stored in the temporary folder.

[0062] In step S806, the streaming server 372 uploads the TS file S111 to the cloud space 382 on the cloud server 380. The upload process may include uploading / updating / copying the entire temporary folder to the cloud space 382. The temporary folder is specified by the unique key, and therefore the cloud space 382 is specified by the unique key.

[0063] Steps S804 and S806 are repeated. TS files S112, S113, ..., S11M are generated from the stream segment S11, time stamps are sequentially added, and the files are uploaded to the cloud space 382. The stream segment S11 is converted into M TS files. The number M may be referred to as the TS number of the stream segment S11 on the streaming server 372.

[0064] In step S808, the distributor D1 experiences an internet disconnection, so the remainder of the distribution file S1 has not yet been sent.

[0065] In step S810, the streaming server 372 transmits the TS number, time stamp information, and the unique key to the playlist generator 330. In some embodiments, the TS number and the time stamp information may be referred to as stream portion information.

[0066] After that, the flow enters a loop L2, and the consistency of the number of TS files is confirmed between the streaming server 372 and the cloud space 382. At the time of the Internet disconnection, it is possible that not all TS files have been transmitted from the streaming server 372 to the cloud space 382.

[0067] In step S812, the playlist generating device 330 accesses the cloud space 382 using the unique key, and requests to obtain the TS number and time stamp information of the TS file stored in the cloud space 382.

[0068] In step S814, the playlist generator 330 checks the consistency between the number of TSs (i.e., M) on the streaming server 372 (for example, during the period specified by the time stamp information) and the number of TSs on the cloud space 382. If it is determined that there is consistency, the flow proceeds to step S818, otherwise the flow proceeds to step S816.

[0069] In step S816, the playlist generator 330 waits for the remaining TS files (on the streaming server 372) to be uploaded to the cloud space 382. In some embodiments, the waiting time may be set to be equal to or greater than the upload period of the TS files uploaded from the streaming server 372 to the cloud space 382.

[0070] For example, when the playlist generator 330 determines that the TS file (or stream portion) stored in the cloud space 382 is missing a portion (compared to the TS file of the streaming server 372) based on the TS number and timestamp information (at step S814), the playlist generator 330 waits until the streaming server 372 transmits the remaining portion to the cloud space 372. In some embodiments, the waiting step may be referred to as waiting for transmission of the remaining stream portion.

[0071] Part of loop L2 (steps S812, S814 and / or S816) may overlap (or be performed simultaneously) with part of loop L1 (such as generating and uploading the final TS file(s). In some embodiments, step S810 may overlap with the last steps of loop L1.

[0072] In step S818, the playlist generator 330 determines that all TS files on the streaming server 372 have been uploaded to the cloud space 382.

[0073] In step S820, the playlist generating device 330 generates a playlist file based on the number of TSs and the time stamp information.

[0074] In step S822, the playlist generator 330 uploads the playlist file to the cloud space 382.

[0075] In step S824, the playlist generator 330 notifies a participant of a playback URL. The playback URL is configured to access or address the cloud space 382 where the playlist file and the TS files are stored. In some embodiments, the playback URL corresponds to the unique key. The playback URL may be obtained, for example, in step S812. The participant may be a back-end server or a user terminal of a user who wants to watch the playback of the stream. The playback (or replay) of the stream may be performed with the playlist file and the TS files.

[0076] Figure 9 is a continuation of Figure 8.

[0077] In step S900, the Internet connection of the distributor D1 is restored, and the distributor D1 transmits the stream segment S12, which is a part of the distribution file S1, to the streaming server 374. The user ID of the distributor D1 and the stream ID of the distribution file S1 are also transmitted to the streaming server 374.

[0078] In step S902, the streaming server 374 generates a unique key based on the user ID and the stream ID, and generates a temporary folder (or space, or file) on the streaming server 374 based on the unique key. Since the user ID and the stream ID also correspond to the distribution file S1, the unique key is the same as the unique key generated in step S802.

[0079] In step S904, the streaming server 374 identifies the cloud space 382 by the unique key. The streaming server 374 may perform a lookup process on the cloud server 380 using the unique key to address the cloud space 382. In some embodiments, a fetch-or-create operation may be performed by the streaming server 374.

[0080] The flow then enters a loop L3 where a TS file is generated and uploaded to the cloud space 382.

[0081] In step S906, the streaming server 374 generates and timestamps a TS file S121. The TS file S121 is generated from the stream segment S12. Transcoding and video splitting may be included. The TS file S121 is stored in the temporary folder.

[0082] In step S908, the streaming server 374 uploads the TS file S121 to the cloud space 382 on the cloud server 380. The upload process may include uploading / updating / copying the entire temporary folder to the cloud space 382.

[0083] Steps S906 and S908 are repeated. TS files S122, S123, ..., S12N are generated from the stream segment S12, time stamps are sequentially added, and the files are uploaded to the cloud space 382. The stream segment S12 is converted into N TS files. The number N may be referred to as the TS number of the stream segment S12 on the streaming server 374.

[0084] In step S910, the distributor D1 ends the distribution. The distributor D1 may transmit a distribution end signal together with the stream ID of the distribution file S1.

[0085] In step S912, the streaming server 374 transmits the number of TSs, time stamp information, and the unique key to the playlist generating device 330.

[0086] Then, the flow enters a loop L4, where the consistency of the number of TSs between the streaming server 374 and the cloud space 382 is confirmed.

[0087] In step S914, the playlist generating device 330 accesses the cloud space 382 using the unique key, and requests to obtain the TS number and time stamp information of the TS file stored in the cloud space 382.

[0088] In step S916, the playlist generator 330 checks the consistency between the number of TSs (i.e., N) on the streaming server 374 (for example, for a period specified by time stamp information) and the number of TSs on the cloud space 382. If it is determined that there is consistency, the flow proceeds to step S920, otherwise the flow proceeds to step S918.

[0089] In step S918, the playlist generator 330 waits for the remaining TS files (on the streaming server 374) to be uploaded to the cloud space 382. In some embodiments, the waiting time may be set to be equal to or greater than the upload period of the TS files uploaded from the streaming server 374 to the cloud space 382.

[0090] Part of loop L4 (steps S914, S916 and / or S918) may overlap (or be performed simultaneously) with part of loop L3 (such as generating and uploading the final TS file(s). In some embodiments, step S912 may overlap with the last steps of loop L3.

[0091] In step S920, the playlist generator 330 determines that all TS files on the streaming server 374 have been uploaded to the cloud space 382.

[0092] In step S922, the playlist generation device 330 updates the playlist file based on the number of TSs and the time stamp information. The playlist generation device 330 may specify the playlist file by the unique key.

[0093] In step S924, the playlist generator 330 uploads (or updates) the playlist file to the cloud space 382.

[0094] In step S926, the playlist generator 330 informs an interested party of the playback URL. Since the unique key is the same, the playback URL is the same as the playback URL in step S824. The interested party may be a backend server or a user terminal of a user who wants to watch the playback of the stream. The playback of the stream may be performed with the playlist file and the TS file.

[0095] FIG. 10 is an exemplary data structure according to some embodiments of the present invention.

[0096] As shown in Figure 10, due to an Internet disconnection (e.g., at the distributor), stream segments A1, A2, and A3 are sent to different streaming servers ST1, ST2, and ST3. The stream segments A1, A2, and A3 belong to the same distribution session (or distribution file), so they correspond to the same streamer ID / distributor ID (ABC) and the same stream ID (XYZ). Each streaming server creates a unique key ( / streamerABC / streamXYZ) based on the distributor ID and the stream ID, creates a folder based on the unique key, converts each stream segment into a TS file, timestamps the TS files, and calculates the number of TS files.

[0097] The folder (with the TS file and the unique key) is sent to the cloud space. Because the unique keys of the three stream segments are the same, the TS file is sent to the same cloud space on the cloud server. The cloud space also corresponds to the unique key.

[0098] When a stream segment ends (due to an Internet disconnection or end of distribution, etc.), the corresponding streaming server notifies the m3u8 generation device to check the consistency of TS file information (TS number and timestamp) between the streaming server and the cloud space.

[0099] After the consistency check of the TS file information is completed, the m3u8 generator generates or updates the playlist file. When new TS file information is added to the m3u8 playlist file, the tag "EXT-X-ENDLIST" is always updated at the bottom.

[0100] The present invention can generate a playlist file for playing a complete distribution file from individual stream segments of the distribution file. The present invention can dynamically update the playlist file whenever the distributor encounters an Internet disconnection. The present invention uses timestamps to ensure that the stream parts on the cloud space are played in the correct order. The present invention uses a playlist generator to perform processes such as checking stream part information and waiting for the remaining stream parts to be sent, and ensures the integrity of the stream parts on the cloud space. The present invention uses a unique key corresponding to the distributor ID and the stream ID to ensure that all stream parts of the same distribution file can be stored in the same cloud space. Processes such as receiving stream segments from a distributor, generating stream parts, and uploading the stream parts to the cloud server may be performed simultaneously or in parallel by the streaming server. The playlist file can be generated more dynamically and quickly.

[0101] 11 is an exemplary flow chart illustrating a method according to some embodiments of the present invention. Stream segment S11 and stream segment S12 belong to one complete distribution file S1 and are sent separately from the distributor due to an Internet disconnection.

[0102] In step S1100, the streaming server 372 receives a stream segment S11 from the distributor. The stream segment S11 may have a TS or FLV format, or another format. The streaming server 372 generates a unique key based on the distributor ID and the stream ID.

[0103] In step S1102, the streaming server 372 generates a stream portion from the stream segment S11, timestamps the stream portion, and transmits the stream portion and the unique key to the playback file generation device 332.

[0104] In step S1104, the playlist generator 330 checks the consistency of stream part information (such as the number of stream parts and timestamps) between the stream parts on the streaming server 372 and the stream parts on the playback file generator 332. The unique key may be used to identify each stream part to be compared. The playlist generator 330 ensures that all stream parts are sent from the streaming server 372 to the playback file generator 332.

[0105] In step S1106, the playlist generator 330 generates a playlist file based on the stream portion information, and sends the playlist file to the playback file generator 332. The playlist file may have an m3u8 format.

[0106] In step S1108, the playback file generator 332 generates a playback file based on the playlist file and the stream portion received from the streaming server 372. The generation of the playback file may involve a transcoding process. The playback file may have an MP4 or MKV format, or another format. In some embodiments, the format of the playback file may be set by a configuration signal from a user or an operator of the streaming system. In some embodiments, the playback file may have a format similar to that of the data stored in the cloud space, as shown in FIG. 10.

[0107] In step S1110, the streaming server 374 receives the stream segment S12 from the distributor. The streaming server 374 generates a unique key based on the distributor ID and the stream ID. Since the stream segments S12 and S11 correspond to the same distribution file S1, the stream segments S12 and S11 have the same distributor ID and the same stream ID. Therefore, the unique key generated in step S1110 is the same as the unique key generated in step S1100.

[0108] In step S1112, the streaming server 374 generates a stream portion from the stream segment S12, timestamps the stream portion, and transmits the stream portion and the unique key to the playback file generator 332.

[0109] In step S1114, the playlist generator 330 checks the consistency of stream part information (such as the number of stream parts and timestamps) between the stream parts on the streaming server 374 and the stream parts on the playback file generator 332. The unique key and the timestamp may be used to identify each stream part to be compared. The playlist generator 330 ensures that all stream parts are sent from the streaming server 374 to the playback file generator 332.

[0110] In step S1116 , the playlist generator 330 updates the playlist file based on the stream portion information (and the unique key) and sends the updated playlist file to the playback file generator 332 .

[0111] In step S1118, the playback file generator 332 updates the playback file based on the updated playlist file and the stream portion received from the streaming server 374. The unique key may be used to identify the playback file to be updated. The update of the playback file may involve a transcoding process. The updated playback file corresponds to the complete distribution file S1 and may be used to play the distribution file S1.

[0112] In step S1120, the playback file generation device 332 uploads the playback file to the cloud server 380 and notifies interested parties of the URL for accessing the playback file.

[0113] In this embodiment, receiving stream segments, generating stream parts from the segments, and sending the stream parts to the playback file generator may be performed simultaneously or in parallel. A consistency check of the stream part information ensures the integrity of the playback file. The present invention can quickly generate a playback file for playback of the complete distribution file from individual stream segments of the distribution file.

[0114] 12 is an exemplary flow chart illustrating a method according to some embodiments of the present invention. Stream segment S11 and stream segment S12 belong to one complete distribution file S1 and are sent separately from the distributor due to an Internet disconnection.

[0115] In step S1200, the streaming server 372 receives the stream segment S11 from the distributor. The streaming server 372 generates a unique key based on the distributor ID and the stream ID.

[0116] In step S1202, the streaming server 372 generates a stream part from the stream segment S11, timestamps the stream part, and sends the stream part information and the unique key to the playlist generator 330.

[0117] In step S1204, the playlist generator 330 generates a playlist file based on the stream portion information, the playlist file corresponding to the unique key.

[0118] In step S1206, the streaming server 374 receives the stream segment S12 and a distribution end signal from the distributor (or together with the stream end signal). The streaming server 374 generates a unique key based on the distributor ID and the stream ID. The unique key is the same as the unique key generated in step S1200.

[0119] In step S1208, the streaming server 374 generates a stream part from the stream segment S12, timestamps the stream part, and transmits the stream part information and the unique key to the playlist generating device 330. The stream part information includes the distribution end signal.

[0120] In step S1210, the playlist generating device 330 updates the playlist file based on the stream portion information and the unique key. Triggered by the distribution end signal, the playlist generating device 330 transmits the playlist file to the playback file generating device 332.

[0121] In step S1212, the playback file generator 332 generates a playback file with the playlist file and the stream parts on the streaming servers 372 and 374. The playlist file may include information of the streaming servers 372 and 374. The playback file generator 332 uses the unique key to access the correct stream parts stored on the streaming servers 372 and 374, respectively, and generates the playback file. Transcoding may be performed.

[0122] In step S1214, the playback file generation device 332 uploads the playback file to the cloud server 380 and notifies interested parties of the URL for accessing the playback file.

[0123] In this embodiment, the generation of the playback file occurs only after the streaming has properly finished, and the interested parties are guaranteed to be able to see the complete playback of the distribution file when they receive notification.

[0124] The hardware configuration of the information processing device will be described with reference to Fig. 13. Fig. 13 is a block diagram showing an example of the hardware configuration of an information processing device based on some embodiments of the present invention. The information processing device 900 shown in the figure can realize, for example, the server 10 and / or the user terminals 20 and 30 in some embodiments.

[0125] The information processing device 900 includes a CPU 901, a ROM (read only memory) 903, and a RAM (random access memory) 905. The information processing device 900 may also include a host bus 907, a bridge 909, an external bus 911, an interface 913, an input device 915, an output device 917, a storage device 919, a drive 921, a connection port 925, and a communication device 929. The information processing device 900 further includes an imaging device such as a camera (not shown). The information processing device 900 may also include a DSP (digital signal processor) or an ASIC (application specific integrated circuit) in addition to or instead of the CPU 901.

[0126] The CPU 901 functions as an arithmetic processing device and a control device, and controls all or part of the operation of the information processing device 900 according to various programs stored in the ROM 903, the RAM 905, the storage device 919, or the removable recording medium 923. For example, the CPU 901 controls the overall operation of each functional unit included in the server 10 and the user terminals 20 and 30 in some embodiments. The ROM 903 stores programs and arithmetic parameters used by the CPU 901. The RAM 905 functions as a main storage device that stores programs used when the CPU 901 is executed, parameters that change appropriately during execution, and the like. The CPU 901, the ROM 903, and the RAM 905 are interconnected by a host bus 907, which may be an internal bus such as a CPU bus. Furthermore, the host bus 907 is connected to an external bus 911 such as a PCI (Peripheral Component Interconnect / Interface) bus via a bridge 909.

[0127] The input device 915 may be a device operated by a user, such as a mouse, a keyboard, a touch panel, a button, a switch, or a lever, or a device that converts a physical quantity into an electric signal, such as a sound sensor represented by a microphone, an acceleration sensor, a tilt sensor, an infrared sensor, a depth sensor, a temperature sensor, or a humidity sensor. The input device 915 may be, for example, a remote control device that uses radio waves such as infrared rays, or an external connection device 927 such as a mobile phone that supports the operation of the information processing device 900. The input device 915 includes an input control circuit that generates an input signal based on information input by the user or a detected physical quantity and outputs the input signal to the CPU 901. The user operates the input device 915 to input various data to the information processing device 900 and instruct the information processing device 900 to operate.

[0128] The output device 917 is a device that can visually or audibly notify the user of acquired information. The output device 917 may be, for example, a display such as an LCD, a PDP, or an OLED, an audio output device such as a speaker or a headphone, or a printer. The output device 917 outputs the processing result by the information processing device 900 as a video such as text or an image, or an audio such as a voice.

[0129] The storage device 919 is a data storage device and is configured as an example of a storage unit of the information processing device 900. The storage device 919 is, for example, a magnetic storage device such as a hard disk drive (HDD), a semiconductor storage device, an optical storage device, or a magneto-optical storage device. The storage device 919 stores the programs executed by the CPU 901, various data, various data acquired from the outside, and the like.

[0130] The drive 921 is a reader / writer of a removable recording medium 923 such as a magnetic disk, an optical disk, a magneto-optical disk, or a semiconductor memory, and is built into or externally attached to the information processing device 900. The drive 921 reads out information recorded on the attached removable recording medium 923, and outputs it to the RAM 905. Furthermore, the drive 921 writes information to the attached removable recording medium 923.

[0131] The connection port 925 is a port for directly connecting a device to the information processing device 900. The connection port 925 may be, for example, a USB (Universal Serial Bus) port, an IEEE 1394 port, or a SCSI (Small Computer System Interface) port. Furthermore, the connection port 925 may be an RS-232C port, an optical audio terminal, an HDMI (High Definition Multimedia Interface) port, or the like. By connecting the external connection device 927 to the connection port 925, various data can be exchanged between the information processing device 900 and the external connection device 927.

[0132] The communication device 929 is, for example, a communication interface formed by a communication device for connecting to the network NW. The communication device 929 may be, for example, a communication card for a wired or wireless local area network (LAN), Bluetooth (trademark), or wireless USB (WUSB). Furthermore, the communication device 929 may be a router for optical communication, a router for ADSL (asymmetric digital subscriber line), or a modem for various communications. The communication device 929 transmits and receives signals, etc., on the Internet or between other communication devices using a predetermined protocol such as TCP / IP. The communication network NW connected to the communication device 929 is a network connected by wire or wirelessly, for example, the Internet, a home LAN, infrared communication, radio wave communication, satellite communication, etc. The communication device 929 realizes a function as a communication device.

[0133] The imaging device (not shown) is a device that captures an image of real space using an imaging element such as a CCD (charge-coupled device) or a CMOS (complementary metal-oxide semiconductor) and various members such as a lens for controlling the formation of a subject image on the imaging element, and generates a captured image. The imaging device may capture still images or moving images.

[0134] The configuration and operation of the live streaming system 1 according to this embodiment have been described above. This embodiment is merely an example, and it will be understood by those skilled in the art that various modifications are possible with respect to the combination of each component and each process, and that such modifications are also within the scope of the present invention.

[0135] The processes and procedures described in the present invention can be realized by software, hardware, or any combination thereof, in addition to those explicitly described. For example, the processes and procedures described herein can be realized by implementing logic corresponding to the processes and procedures in a medium such as an integrated circuit, a volatile memory, a non-volatile memory, a non-transitory computer-readable medium, a magnetic disk, etc. Furthermore, the processes and procedures described herein can be realized as a computer program corresponding to the processes and procedures, and can be executed by various computers.

[0136] Furthermore, the system or method described in the above embodiments may be integrated into a program stored in a non-transitory computer-readable medium such as a solid-state storage device, an optical disk storage device, a magnetic disk storage device, etc. Alternatively, the program may be downloaded from a server via the Internet and executed by a processor.

[0137] Although the technical contents and features of the present invention have been described above, those skilled in the art can still make many variations and modifications without departing from the teachings and disclosure of the present invention. Therefore, the scope of the present invention is not limited to the embodiments already disclosed, but is within the scope of the claims, including other variations and modifications that do not depart from the present invention. [Explanation of symbols]

[0138] 1. Communication Systems 10 Server 20 User terminal 30, 30a, 30b User terminal LV Streamer AU1, AU2 viewers VD, VD1, VD2 Video NW Network 30 User terminal 100 Delivery Units 102 Imaging control unit 104 Audio control unit 106 Video Transmission Unit 108 Provider UI Control Unit 200 viewing units 202 Viewer side UI control unit 204 Superposition Information Generation Unit 206 Input information transmission unit 302 Distribution Information Unit 304 Relay unit 306 Gift Processing Unit 308 Payment Processing Unit 310 Stream DB 312 User DB 314 Gift DB 330 Playlist Generator 332 Reproduction File Generator 350 Playlist DB 352 Playback File DB 362, 364, 372, 374 Streaming Server 380 Cloud Server 382, 384 Cloud Space S700, S702, S704, S706, S708, S710, S712, S714 process S800, S802, S804, S806, S808, S810, S812, S814, S816, S818, S820, S822, S824 Process S900, S902, S904, S906, S908, S910, S912, S914, S916, S918, S920, S922, S924, S926 process S1100, S1102, S1104, S1106, S1108, S1110, S1112, S1114, S1116, S1118, S1120 process S1200, S1202, S1204, S1206, S1208, S1210, S1212, S1214 process 900 Information processing device 901 CPU 903 ROM 905 RAM 907 Host Bus 909 Bridge 911 External Bus 913 Interface 915 Input Device 917 Output Device 919 Storage Device 921 Drive 923 Removable Recording Media 925 Connection Port 927 External connection device 929 Communication Equipment

Claims

1. 1. A playlist generation method executed by a playlist generation device, comprising: obtaining first stream portion information and a unique key from a first streaming server; determining that a first set of stream portions stored on a space of a cloud server matches the first stream portion information, the space being addressable by the unique key; generating a playlist file based on the first stream portion information; obtaining second stream portion information and the unique key from a second streaming server; determining that a second set of stream portions stored on the space of the cloud server matches the second stream portion information; updating the playlist file based on the second stream portion information; 13. A playlist generating method comprising:

2. moreover, Identifying the space on the cloud server with the unique key; uploading the playlist file to the space; 2. The method of claim 1, further comprising:

3. The playlist generating method according to claim 2, further comprising the step of transmitting an address at which the playlist file in the space can be accessed.

4. 2. The playlist generating method according to claim 1, characterized in that the first streaming server transmits a first portion of the first set of stream portions to the space of the cloud server while generating a second portion of the first set of stream portions, wherein the first portion and the second portion are generated by the first streaming server based on a distribution file received from a user terminal and correspond to the unique key.

5. 5. The playlist generating method of claim 4, wherein the first streaming server generates a first timestamp for the first portion and a second timestamp for the second portion, and the stream portion information includes a number of the first set of stream portions, the first timestamp, and the second timestamp.

6. 2. The playlist generating method of claim 1, wherein the first set of stream portions corresponds to a first segment of a distribution file of a distributor at a first time and the second set of stream portions corresponds to a second segment of the distribution file of the distributor at a second time, wherein the distribution file and the distributor are specified by the unique key.

7. Determining that a first set of stream portions stored on the space of the cloud server matches the first stream portion information further comprises: determining that a first set of stream portions stored on the space of the cloud server is missing a portion based on the first stream portion information; and waiting for the first streaming server to transmit the portion to the space of the cloud server; 2. The playlist generating method of claim 1, wherein generating the playlist file based on the first stream portion information is performed after a step of determining that the first set of stream portions stored on the space of the cloud server matches the first stream portion information.

8. 1. A system for playlist generation, comprising: one or more processors, the one or more processors executing machine-readable instructions to: obtaining first stream portion information and a unique key from a first streaming server; determining that a first set of stream portions stored on a space of a cloud server matches the first stream portion information, the space being addressable by the unique key; generating a playlist file based on the first stream portion information; obtaining second stream portion information and the unique key from a second streaming server; determining that a second set of stream portions stored on the space of the cloud server matches the second stream portion information; updating the playlist file based on the second stream portion information.

9. A system for playlist generation, comprising: a streaming server and a playlist generation device, The streaming server, Receive a stream segment, generating a unique key based on a distributor ID and a stream ID of the stream segment; generating stream portions from the stream segments; adding a timestamp to the stream portion; Transmitting the stream portion and the unique key to a cloud space on a cloud server; sending the number of stream portions, the timestamps and the unique key to the playlist generator; It is configured as follows: The playlist generation device, Identifying the cloud space on the cloud server with the unique key; Determining the consistency of the stream portions between the streaming server and the cloud space; generating a playlist file based on the number of stream portions and the timestamps; A system for generating a playlist, comprising:

Citation Information

Patent Citations

  • Content processing system, terminal device, and program

    JP2019110480A

  • System and method for using a website containing video playlists as input to a download manager

    US9082174B2

  • Methods and apparatuses for a distributed live-on-demand (LOD) origin

    US9942578B1

  • Internet multimedia playback system and method thereof

    TW201445986A