Content interaction method and device, computer equipment and program product

Abstract

The embodiment of the invention discloses a content interaction method and device, computer equipment and a program product, after to-be-uploaded content is obtained, a multi-person production control is displayed, and the multi-person production control is used for opening the authority of uploading branch content for the to-be-uploaded content to other accounts. And if a trigger operation for the multi-person production space is obtained, setting a multi-version production interval for the to-be-uploaded content, namely which part of the to-be-uploaded content is used for displaying various branch contents. And after the multi-version production interval is set, uploading the multi-version content. Wherein the multi-version content is to-be-uploaded content with a multi-person production identifier, the multi-person production identifier is used for representing that the to-be-uploaded content supports displaying of multiple branch contents in a multi-version production interval, and the multiple branch contents are obtained through uploading based on multiple accounts. Therefore, various branch contents for the same multi-version content can be made and uploaded by a plurality of creators, so that the making difficulty and workload of each creator are reduced.

Description

Technical Field

[0001] This application relates to the field of Internet technology, and in particular to a content interaction method, apparatus, computer equipment, and program product. Background Technology

[0002] Multi-version content refers to content that can have multiple different versions of the storyline, i.e., multiple branching narratives. For example, a video documenting a journey from Beijing to Shanghai can generate multiple versions of the video content by choosing different modes of transportation; each version represents a branching narrative. Viewers can choose different branches while watching multi-version content, thus experiencing different content and enhancing the user experience.

[0003] In related technologies, multiple versions of content are generally created by the creator of the content, which is quite difficult and requires a lot of work. Summary of the Invention

[0004] To address the aforementioned technical issues, this application provides a content interaction method, apparatus, computer device, and program product to reduce the difficulty of creating multiple versions of content and decrease the workload of creators.

[0005] The embodiments of this application disclose the following technical solutions:

[0006] In a first aspect, embodiments of this application provide a content interaction method, the method comprising:

[0007] In response to receiving the content to be uploaded, a control panel created by multiple users is displayed;

[0008] In response to receiving a trigger operation for the multi-person creation control, a multi-version creation range is set for the content to be uploaded;

[0009] In response to obtaining confirmation for the multi-version production range, multi-version content is uploaded. The multi-version content is content with a multi-person production identifier added to the content to be uploaded. The multi-person production identifier is used to indicate that the multi-version content supports displaying multiple branch content in the multi-version production range. The multiple branch content is obtained by uploading multiple account identifiers.

[0010] Secondly, embodiments of this application provide a content interaction method, the method comprising:

[0011] In response to the selection operation for multiple versions of content, the target branch content is uploaded. The multiple version content is content with a multi-person production identifier. The multi-person production identifier is used to indicate that the multiple version content supports displaying multiple branch contents in the multiple version production interval.

[0012] If the target branch content is successfully uploaded, the target branch content will be identified as one of the multiple branch contents displayed in the multiple version production interval.

[0013] Thirdly, embodiments of this application provide a content interaction device, the device comprising: a display unit, a setting unit, and an uploading unit;

[0014] The display unit is used to display a multi-person creation control in response to obtaining the content to be uploaded;

[0015] The setting unit is used to set a multi-version production range for the content to be uploaded in response to receiving a trigger operation for the multi-person production control;

[0016] The upload unit is used to upload multi-version content in response to obtaining a confirmation operation for the multi-version production range. The multi-version content is content with a multi-person production identifier added to the content to be uploaded. The multi-person production identifier is used to indicate that the multi-version content supports displaying multiple branch content in the multi-version production range. The multiple branch content is obtained by uploading multiple account identifiers.

[0017] Optionally, the upload unit is specifically used for:

[0018] In response to obtaining confirmation for the multiple version production range, a user permission control is displayed;

[0019] After determining the set of account identifiers through the user permission control, the multi-version content is uploaded. The account identifiers included in the set of account identifiers have the permission to upload branch content for the content to be uploaded, and the multi-version content has a corresponding relationship with the set of account identifiers.

[0020] Optionally, the content interaction device further includes a message unit for:

[0021] After determining the account identifier set through the user permission control, a message sending control is displayed;

[0022] In response to receiving a trigger operation for the message sending control, a prompt for the multi-version content upload branch content is sent to the account identifiers included in the account identifier set.

[0023] Optionally, the upload unit is specifically used for:

[0024] In response to obtaining confirmation for the multi-version production range, a branch content quantity control is displayed;

[0025] After determining the maximum upload quantity of the various branch content through the content quantity control, the multiple versions of the content are uploaded, and the quantity of the various branch content is less than or equal to the maximum upload quantity.

[0026] Optionally, the upload unit is specifically used for:

[0027] Upload the multi-version content and its metadata, which includes a multi-person creation identifier for the multi-version content, whether the multi-person creation function is enabled for the multi-version content, the start position of the multi-version creation interval, and the end position of the multi-version creation interval.

[0028] Optionally, the upload unit is specifically used for:

[0029] The metadata of the multi-version content is encrypted to obtain the encrypted metadata of the multi-version content;

[0030] Upload the multi-version content and the encrypted metadata of the multi-version content.

[0031] Fourthly, embodiments of this application provide a content interaction device, the device comprising: an uploading unit and a determining unit;

[0032] The upload unit is used to upload target branch content in response to obtaining a selection operation for multi-version content. The multi-version content is content with a multi-person production identifier. The multi-person production identifier is used to indicate that the multi-version content supports displaying multiple branch contents in the multi-version production area.

[0033] The determining unit is configured to, if the target branch content is successfully uploaded, determine the target branch content as one of the multiple branch contents displayed in the multiple version production interval.

[0034] Optionally, the content interaction device further includes a branch selection unit, used for:

[0035] Display the aforementioned multiple versions of content;

[0036] When the multi-version content is displayed in the multi-version production area, preview content of various branches is displayed;

[0037] In response to a trigger operation targeting the first branch content to be displayed among the multiple branch contents, the first branch content to be displayed is displayed in the multi-version production interval.

[0038] Optionally, if the multi-version content is video content, and the multi-version content includes a second branch content to be displayed and a third branch content to be displayed, wherein the second branch content to be displayed and the third branch content to be displayed are different branch contents, then the branch selection unit is specifically used for:

[0039] When the multi-version content is displayed in the multi-version production interval, a combined data packet is obtained. The combined data packet is a data packet jointly encoded based on the first n video frames of the second branch content to be displayed and the first m video frames of the third branch content to be displayed, where m is a positive integer and n is a positive integer.

[0040] The combined data packet is decoded to obtain the first n video frames of the second branch content to be displayed and the first m video frames of the third branch content to be displayed;

[0041] The preview content includes the first n video frames of the second branch content to be displayed and the first m video frames of the third branch content to be displayed.

[0042] Optionally, the branch selection unit is specifically used for:

[0043] From the second branch content to be displayed and the third branch content to be displayed, determine the main branch content and the non-main branch content, wherein the main branch content and the non-main branch content are different branch contents;

[0044] Display video frames of the main branch content and video frames of the non-main branch content, and play the audio of the main branch content.

[0045] Optionally, the upload unit is specifically used for:

[0046] In response to a selection operation for multiple versions of content, multiple production ranges for the multiple versions of content are displayed;

[0047] In response to a triggered operation targeting a target multi-version production interval among the plurality of multi-version production intervals, the target branch content is uploaded to the target multi-version production interval.

[0048] Optionally, the content interaction device further includes a permission unit, used for:

[0049] Obtain the account identifier that uploaded the target branch content, and the set of account identifiers that correspond to the multiple versions of the content;

[0050] If the set of account identifiers includes the same account identifier as the account identifier that uploaded the target branch content, then the account identifier that uploaded the target branch content has the authority to upload branch content for the multi-version content.

[0051] Optionally, the content interaction device further includes a quantity unit for:

[0052] Get the maximum number of uploads for the multiple versions of content;

[0053] If the number of historical branch contents included in the multi-version content is less than the maximum upload quantity, then the target branch content is determined to have been successfully uploaded. The historical branch content refers to the branch content uploaded before the target branch content.

[0054] Optionally, the quantity unit is further used for:

[0055] If the number of historical branch contents included in the multi-version content is equal to the maximum upload quantity, then the popularity of each historical branch content is determined.

[0056] If the popularity of each of the historical branch contents meets the popularity condition, then the upload of the target branch content is determined to have failed.

[0057] If the target popularity does not meet the popularity condition among the popularity of each of the historical branch contents, then the historical branch content corresponding to the target popularity is deleted, and the target branch content is determined to have been successfully uploaded.

[0058] Optionally, after uploading the target branch content, the content interaction device further includes a popularity unit, used for:

[0059] Displays a button to increase popularity;

[0060] In response to receiving a trigger operation for the popularity increase button, a popularity increase strategy corresponding to the popularity increase button is set for the target branch content.

[0061] Fifthly, embodiments of this application provide a content interaction system, the system comprising: a first device and a second device;

[0062] The first device is configured to perform the method described in the first aspect;

[0063] The second device is used to perform the method described in the second aspect.

[0064] Sixthly, embodiments of this application provide a computer device, the computer device including a processor and a memory:

[0065] The memory is used to store computer programs and to transfer the computer programs to the processor;

[0066] The processor is configured to execute the methods described above according to instructions in the computer program.

[0067] In a seventh aspect, embodiments of this application provide a computer-readable storage medium for storing a computer program for performing the methods described above.

[0068] Eighthly, embodiments of this application provide a computer program product or computer program including computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the computer device to perform the methods described above.

[0069] As can be seen from the above technical solution, after obtaining the content to be uploaded, a multi-user creation control is displayed. This control grants other accounts permission to upload branch content for the content to be uploaded. If a trigger operation is obtained for this multi-user creation space, a multi-version creation range is set for the content to be uploaded, specifying which part of the content will be used to display multiple branch contents. After the multi-version creation range is set, the multi-version content is uploaded. The multi-version content is the content to be uploaded with a multi-user creation identifier, which indicates that the content to be uploaded supports displaying multiple branch contents within the multi-version creation range, and these branch contents are obtained from uploads by multiple accounts.

[0070] Therefore, by having multiple people create the control, other accounts can be granted permission to upload branch content for the content to be uploaded. In other words, multiple creators can create and upload multiple branch contents for the same multi-version content, thereby reducing the production difficulty and workload for each creator. Attached Figure Description

[0071] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0072] Figure 1 A schematic diagram illustrating a multi-version content provided in an embodiment of this application;

[0073] Figure 2 This is a schematic diagram illustrating an application scenario of a content interaction method provided in an embodiment of this application.

[0074] Figure 3 A flowchart illustrating the content interaction method provided in the embodiments of this application;

[0075] Figure 4 A schematic diagram illustrating a control created by multiple users, provided as an embodiment of this application;

[0076] Figure 5 This is a schematic diagram illustrating the setting of a multi-version production area as provided in an embodiment of this application;

[0077] Figure 6 A schematic diagram of a user permission control provided in an embodiment of this application;

[0078] Figure 7 A schematic diagram of a user permission control provided in an embodiment of this application;

[0079] Figure 8 A schematic diagram of a user permission control provided in an embodiment of this application;

[0080] Figure 9 A schematic diagram illustrating a control for displaying the number of branch contents and a user permission control provided in an embodiment of this application;

[0081] Figure 10 A flowchart illustrating the content interaction method provided in the embodiments of this application;

[0082] Figure 11 This is a schematic diagram illustrating an embodiment of uploading branch content provided in this application.

[0083] Figure 12 This application provides a signaling interaction diagram for uploading target branch content.

[0084] Figure 13 A flowchart illustrating a content interaction method provided in an embodiment of this application;

[0085] Figure 14 This application provides a signaling interaction diagram for viewing multiple versions of content in an embodiment.

[0086] Figure 15 A schematic diagram illustrating a content interaction method provided in an embodiment of this application;

[0087] Figure 16 This is a schematic diagram of the structure of a content interaction device provided in an embodiment of this application;

[0088] Figure 17 This is a schematic diagram of the structure of a content interaction device provided in an embodiment of this application;

[0089] Figure 18 This application provides a schematic diagram of the structure of a server according to an embodiment of the present application.

[0090] Figure 19 This is a schematic diagram of the structure of a terminal device provided in an embodiment of this application. Detailed Implementation

[0091] The embodiments of this application will now be described with reference to the accompanying drawings.

[0092] Content can be video content, article content, novel content, etc., and multiple versions of content include multiple branches. See also Figure 1 This figure is a schematic diagram of a multi-version content provided in an embodiment of this application. Figure 1 The content in this video format consists of multiple versions, each with a branching storyline (Story 1, Story 2, and Story 3) within a certain period. Viewers can choose to watch any of these storylines, thus enhancing their engagement.

[0093] In related technologies, multiple versions of content are typically created solely by the creator of each version. For example, Figure 1 All three storylines in the video need to be produced by the creator of the video content, which is quite difficult and requires a lot of work for the creator.

[0094] Based on this, this application provides a content interaction method. The creator of the content to be uploaded can perform a trigger operation on the control created by multiple people, thereby granting other accounts the permission to upload branch content for the content to be uploaded. This allows multiple creators to create and upload multiple branch contents for the multiple versions of the content, thereby reducing the production difficulty and workload of each creator.

[0095] The content interaction method provided in this application can be applied to computer devices with content interaction capabilities, such as terminal devices and servers.

[0096] Specifically, terminal devices can be desktop computers, laptops, smartphones, tablets, IoT devices, and portable wearable devices. IoT devices can be smart speakers, smart TVs, smart air conditioners, smart in-vehicle devices, etc. Smart in-vehicle devices can be in-vehicle navigation terminals and in-vehicle computers, etc. Portable wearable devices can be smartwatches, smart bracelets, head-mounted devices, etc., but are not limited to these.

[0097] The server can be a standalone physical server, a server cluster or distributed system composed of multiple physical servers, or a cloud server or server cluster that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, content delivery networks (CDNs), and big data and artificial intelligence platforms. Terminal devices and servers can be connected directly or indirectly via wired or wireless communication; this application does not impose any restrictions on this.

[0098] To facilitate understanding of the content interaction method provided in the embodiments of this application, the following example uses a server as the execution subject of the content interaction method to illustrate the application scenarios of the content interaction method.

[0099] See Figure 2 This figure is a schematic diagram illustrating an application scenario of a content interaction method provided in an embodiment of this application. For example... Figure 2 As shown, this application scenario includes terminal device 210 and terminal device 220. Terminal device 210 and terminal device 220 can communicate directly through a communication network, or indirectly through a server via a communication network. The communication network uses standard communication technologies and / or protocols, typically the Internet, but can also be any network, including but not limited to Bluetooth, local area network (LAN), metropolitan area network (MAN), wide area network (WAN), mobile, private network, or any combination of virtual private networks. In some embodiments, customized or dedicated data communication technologies can be used to replace or supplement the aforementioned data communication technologies. In this embodiment, the multiple versions of content are video content.

[0100] The following is an explanation of the multiple versions of content uploaded by the blogger. Among them, the blogger uploads content to be uploaded by the user.

[0101] The terminal device 210 has a client installed to provide content interaction services, and this client can provide bloggers with the service of uploading video content. After selecting the content to be uploaded through the client, the blogger clicks the upload control 211 (i.e., Figure 1 The control marked as completed uploads the content it created. After obtaining the content to be uploaded, the terminal device 210 displays the control created by multiple users 212 (i.e., the control created by multiple users). Figure 1The control marked "Multi-Version Content Settings" indicates that when the blogger clicks on the multi-creation control 212, it means the blogger is granting other creators permission to create content based on the content to be uploaded. This means other creators can create at least one branch of content based on the content to be uploaded. The blogger needs to set the multi-version creation area for the content to be uploaded, that is, which part of the video content to be uploaded can have other branch content, such as... Figure 2 As shown, the content to be uploaded is a 3-minute video. The blogger has set the first 1-2 minutes as a multi-version production area, which can correspond to multiple branches of content. Once the blogger has confirmed the multi-version production area settings, they can click the confirmation control 213 (i.e....). Figure 1 After the space is marked as confirmed, upload multiple versions of content. This multiple version content is content to be uploaded with a multi-person creation identifier. This multi-person creation identifier indicates that the content to be uploaded supports displaying multiple branches of content in the multiple version creation area. The multiple branches of content are based on uploads from multiple accounts.

[0102] Then, the instructions on how viewers can upload branch content for the multiple versions of the content are explained. Viewers refer to users who create branch content for the content to be uploaded, or users who view the content to be uploaded.

[0103] The terminal device 220 is equipped with a client for providing interactive content services, which allows viewers to watch and upload branch content. Viewers can choose which multi-version content to upload branch content for, such as... Figure 2 As shown, after selecting multiple versions of content 2, click upload control 221 (i.e. Figure 1 The space marked as "Upload Space" will be used to upload the target branch content for this multi-version content. If the target branch content is uploaded successfully, it will be identified as one of the various branch contents displayed within the multi-version content creation period, such as... Figure 1 The multi-version content includes three branches: branch content 1, branch content 2, and target branch content.

[0104] Therefore, by having multiple people create the control, other accounts can be granted permission to upload branch content for the content to be uploaded. In other words, multiple creators can create and upload multiple branch contents for the same multi-version content, thereby reducing the production difficulty and workload for each creator.

[0105] The content interaction method provided in this application embodiment can be executed by a terminal device. However, in other embodiments of this application, the server may also have similar functions to execute the content interaction method provided in this application embodiment, or the terminal device and the server may jointly execute the content interaction method provided in this application embodiment. This embodiment does not limit this.

[0106] The following describes in detail a content interaction method provided by this application through method embodiments. This application embodiment provides the permission for bloggers to upload multiple versions of content and grant viewers the permission to upload branch content, as well as the method for viewers to upload branch content. The permission for bloggers to upload multiple versions of content and grant viewers the permission to upload branch content will be explained first.

[0107] See Figure 3 This figure is a schematic flowchart of the content interaction method provided in an embodiment of this application. For ease of description, the following embodiments will still use a terminal device as the executing subject of the content interaction method. Figure 3 As shown, the content interaction method includes S301-S303.

[0108] S301: In response to retrieving content to be uploaded, display the multi-user creation control.

[0109] Content to be uploaded refers to content that is waiting to be uploaded. This can be text content, video content, etc. Video content can be related to games, TV series, etc.

[0110] See Figure 4 This figure is a schematic diagram illustrating a control display for multiple users, provided in an embodiment of this application. The blogger can first select the content they want to upload, and then click to select control 401 (i.e., Figure 4 After selecting the control marked as complete, the selected content becomes the content to be uploaded, waiting to be created into multi-version content. In response to retrieving the content to be uploaded, a multi-version creation control 402 (i.e., ...) is displayed. Figure 4 (The control marked with a middle label is for multi-version content settings).

[0111] In related technologies, multiple versions of content are created and uploaded by the blogger. To reduce the blogger's production difficulty and workload, and to increase audience participation, this application embodiment grants viewers permission to participate in creating branch content of multiple versions of the blogger's content through a multi-user creation control.

[0112] In response to the conditions or states on which the operation is performed depends, one or more operations may be performed in real time or with a set delay when the conditions or states on which they depend are met. Unless otherwise specified, there is no restriction on the order in which the multiple operations are performed.

[0113] It is understood that all data collected in this application (such as multi-version content, branch content, etc.) is collected with the consent and authorization of the data subject (such as user, organization or enterprise), and the collection, use and processing of related data must comply with the relevant laws, regulations and standards of the relevant countries and regions.

[0114] S302: In response to receiving a trigger operation for a control created by multiple people, set a multi-version creation range for the content to be uploaded.

[0115] If the blogger executes a trigger operation for a control created by multiple people, it means that the blogger has granted viewers permission to participate in creating multiple versions of the blogger's content. In this case, in response to the trigger operation for the control created by multiple people, the multi-version creation range for the content to be uploaded is set.

[0116] The triggering operation can be a click, double-click, selection, etc., and this application does not specifically limit it. The multi-version production interval is the display interval for multiple branches of content. For example, if the first and second minutes of a video are used to display different branches of content, then the first and second minutes constitute the multi-version production interval for that video content. Similarly, if chapters 5 to 10 of a text are used to display different branches of content, then chapters 5 to 10 constitute the multi-version production interval for that text content.

[0117] See Figure 5 This figure is a schematic diagram illustrating the setting of a multi-version production area according to an embodiment of this application. Figure 5 In the example of video content with multiple versions, after the blogger performs a trigger operation on the multi-person creation control (such as clicking the multi-person creation control 402), the blogger can adjust the time of the content to be uploaded by dragging left and right, etc., combined with the confirmation control 501 (i.e. Figure 5 The control marked as "Confirm" and the Cancel control 502 (i.e. Figure 5 The control marked as cancel allows you to set the start time (starting at 1 minute) and end time (ending at 2 minutes) for the production interval of multiple versions.

[0118] It should be noted that the content to be uploaded can be complete or incomplete; this application does not impose specific limitations on this. For example, a blogger can create a complete video and select a specific period within that video as the multiple-version production interval. The content created within that interval can be considered a branch, or, depending on the blogger's choice, not as a branch; this application does not impose specific limitations on this. Alternatively, a blogger can create only the first half of the video and use the second half as the multiple-version production interval. Both viewers and bloggers can upload branch content for the multiple-version production area.

[0119] As one possible implementation, one or more production intervals can be set for the same content to be uploaded; this application does not make any specific limitations on this.

[0120] S303: In response to obtaining confirmation for the multi-version production range, upload multi-version content.

[0121] Once the blogger has determined the production range for multiple versions, they can add a multi-person production marker to the content to be uploaded, thus obtaining multiple versions of the content, and then uploading multiple versions of the content.

[0122] Among them, multi-version content refers to content to be uploaded with a multi-person creation identifier. The multi-person creation identifier indicates that multi-version content supports the display of multiple branches of content within the multi-version creation interval, and that these multiple branches of content are uploaded by multiple accounts. For example, a blogger uploads one branch of content based on their own account, viewers upload another branch of content based on their own accounts, or multiple viewers each upload branch of content based on their own accounts. The account identifier is an identifier used to identify the account.

[0123] In other words, the multiple versions of content will include various branches of content from multiple accounts, and these branches will be displayed in the multiple version production area set by the blogger. Subsequently, based on the audience's choices, the branch content selected by the audience will be displayed in the multiple version production area.

[0124] One possible implementation is to upload not only multiple versions of content but also metadata for those versions. This metadata includes a multi-person creation identifier, whether multi-person creation is enabled for each version, the start and end positions of the multi-person creation interval, and so on. Understandably, while content can be presented as multiple versions, the blogger can choose not to enable the feature for viewers to upload branched content, instead using the multi-person creation feature to indicate whether the blogger is creating the multiple versions themselves.

[0125] The following example illustrates how video content metadata is generated using Extensible Markup Language (XML).

[0126] After the blogger set up multiple production ranges for the content to be uploaded, the metadata was obtained using audio and video codec tools and development kits (Fast Forward Moving Picture Experts Group, FFmpeg), and then added to the content to be uploaded to obtain multiple versions of the content. Specifically, the metadata defined in XML format is as follows:

[0127] <multi_content_video>

[0128] <tag> support_multi_content_video< / tag>

[0129] <fragment>

[0130] <params> start_time = 123< / params>

[0131] <params> end_time = 456< / params>

[0132] < / fragment>

[0133] < / multi_content_video>

[0134] in,<multi_content_video> The label was created by multiple people. <tag>The `support_multi_content_video` field in the tag indicates that the multi-user creation feature is enabled for multiple versions of content; the absence of this field indicates that the multi-user creation feature is not enabled for multiple versions of content. <fragment>The tag is used to represent a multi-version production range, so that each multi-version production range is... <fragment>Use labels to differentiate. <params>The tags wrap start_time and end_time, respectively. start_time is the start position of the multi-version production interval, such as the start time, and end_time is the end position of the multi-version production interval, such as the end time.

[0135] After defining the metadata, use the ffmpeg command: ffmpeg -i input.mp4 -metadata:s:v:0 xml="<multi_content_video> <tag> support_multi_content_video< / tag> <params> st art_time=123< / params> <params> end_time = 456< / params> < / multi_content_video>" -codec copy output.mp4 to add metadata to the video.

[0136] Here, ffmpeg is used to call the FFmpeg command line tool. -i input.mp4 is used to specify the input file as the i-th input.mp4. -metadata:s:v:0 is used to specify the stream of the video (metadata) to be modified. s:v:0 means selecting the first video stream. s represents the stream, v represents the video, and 0 represents the index. xml="<multi_content_video> <tag> support_multi_content_video< / tag> <params> st art_time=123< / params> <params> end_time = 456< / params> < / multi_content_video>" is used to add custom metadata. The metadata here is an XML-formatted string containing a multi_content_video tag and multiple params tags. -codec copy is used to instruct FFmpeg not to re-encode video and audio streams during processing, but to copy them directly. This will preserve the original quality and speed up processing. output.mp4 is used to specify the output file as output.mp4.

[0137] In addition, if multiple multi-version production intervals are set for the content to be uploaded, the metadata defined in xml format is as follows:

[0138] <multi_content_video>

[0139] <tag> support_multi_content_video< / tag>

[0140] <fragment>

[0141] <params> start_time = 123< / params>

[0142] <params> end_time = 456< / params>

[0143] < / fragment>

[0144] <fragment>

[0145] <params> start_time = 321< / params>

[0146] <params> end_time = 654< / params>

[0147] < / fragment>

[0148] <fragment>

[0149] <params> start_time = 312< / params>

[0150] <params> end_time = 645< / params>

[0151] < / fragment>

[0152] < / multi_content_video>

[0153] Thus, by adding metadata to the content to be uploaded, the metadata can not only include multi-person production identification, start position and end position of multi-version production interval, but also include whether the multi-version content enables multi-person production function, so as to distinguish the multi-version content produced by the blogger himself alone, which is convenient and fast.

[0154] As a possible implementation, the metadata of the multi-version content is also encrypted to obtain encrypted metadata of the multi-version content, and the multi-version content and the encrypted metadata of the multi-version content are uploaded. That is, the encrypted metadata is uploaded, that is, the encrypted metadata, so as to prevent data tampering and affect the viewing of the multi-version content, thereby improving the security of the platform.

[0155] As can be seen from the above technical solution, after obtaining the content to be uploaded, a multi-person production control is displayed, which is used to open the permission of other accounts to upload branch content for the content to be uploaded. If a trigger operation for the multi-person production space is obtained, a multi-version production interval for the content to be uploaded is set, that is, which part of the content to be uploaded is used to display multiple branch contents. After the multi-version production interval is set, the multi-version content is uploaded. The multi-version content is the content to be uploaded with a multi-person production identification, which is used to represent that the content to be uploaded supports displaying multiple branch contents in the multi-version production interval, and the multiple branch contents are obtained based on multiple accounts.

[0156] Thus, through the multi-person production control, the permission of other accounts to upload branch content for the content to be uploaded can be opened, that is, multiple branch contents for the same multi-version content can be produced and uploaded by multiple creators, thereby reducing the production difficulty and workload of each creator.

[0157] As a possible implementation, the blogger can also set which audience can participate in the uploading of the branch content, see A1-A2.

[0158] A1: In response to obtaining a confirmation operation for the multi-version production interval, a user permission control is displayed.

[0159] The user permission control is used to select users with the permission of uploading branch content.

[0160] Referring to Figure 6 , the figure is a schematic diagram of a user permission control provided by an embodiment of the present application. When the multi-version production interval is successfully set by the blogger, the user permission control 601 is displayed. In Figure 6 In the document, the controls labeled as friends of social platform A, friends of social platform B, and all friends are all user permission controls 601. Users with the permission to upload branch content can be selected through different user permission controls 601, which is convenient and quick.

[0161] See Figure 7 This figure is a schematic diagram of a user permission control provided in an embodiment of this application. After the blogger successfully sets up multiple version creation intervals, user permission control 701 is displayed. Figure 7 In this context, each user waiting to be selected is a user permission control 701. When the blogger selects a user with the permission to upload branch content from multiple users, in response to the trigger operation on the user permission control, a set of account identifiers with upload permission is obtained, thus making it more targeted.

[0162] A2: After determining the set of account identifiers through the user permission control, upload multiple versions of content.

[0163] Bloggers can use the user permission control to select users with permission to upload branch content. The account identifiers of users with permission to upload branch content for this multi-version content constitute a set of account identifiers.

[0164] It should be noted that the uploaded multiple versions of content at this time correspond to the set of account identifiers. For example, the multiple versions of content carry the set of account identifiers, so that it is possible to determine which users can upload branch content for the multiple versions of content based on the set of account identifiers corresponding to the multiple versions of content.

[0165] Therefore, users with the permission to upload branch content can be selected through the user permission control. This not only allows for targeted interaction with specific users but also ensures the quality of content across multiple versions, preventing excessive and useless branch content from affecting the overall quality of the content.

[0166] One possible implementation is not only through the A1-A2 method, where users are granted permissions to upload branch content before uploading multiple versions of the content, but also through the B1-B2 method, where user permission controls are displayed after uploading multiple versions of the content.

[0167] B1: In response to a selection action for target multi-version content, display the user permission control.

[0168] The target multi-version content is one of the multiple multi-version content items.

[0169] See Figure 8 This figure is a schematic diagram of a user permission control provided in an embodiment of this application. When a blogger selects one of multiple versions of content they have uploaded as the target version, such as... Figure 8 The multi-version content 2 is selected as the target multi-version content, and the user permission control 701 is displayed.

[0170] B2: After determining the account identifier set through the user permission control, a corresponding relationship between the target multi-version content and the account identifier set is established.

[0171] For details, please refer to A1-A2, which will not be repeated here.

[0172] As a possible implementation, if a multi-version content has multiple multi-version production intervals, different multi-version production intervals correspond to different branch contents, so that different upload permissions can be set based on different multi-version production intervals, that is, the user's upload branch content permission is refined, thereby meeting the needs of bloggers' diversity.

[0173] Therefore, after uploading the multi-version content, the user permission control can be displayed to set users with upload branch content permissions through the user permission control, so that the diversity needs of bloggers can be met through multiple setting methods.

[0174] As a possible implementation, after setting users with upload branch content permissions, the application embodiment further provides an upload prompt function, please refer to C1-C2.

[0175] C1: After determining the account identifier set through the user permission control, a message sending control is displayed.

[0176] C2: In response to obtaining a triggering operation on the message sending control, a prompt for uploading branch content of the multi-version content is sent to the account identifier included in the account identifier set.

[0177] As a possible implementation, after determining the account identifier set through the user permission control, not only can the user with upload permission be sent a prompt for uploading branch content of the multi-version content, but also the user with upload permission can be sent a prompt for uploading branch content of which multi-version production interval in the multi-version content.

[0178] Therefore, by setting the message sending control, the user with upload permission can be prompted based on the blogger's willingness, improving the blogger's experience and helping the multi-version content to quickly complete the production of multiple branch contents.

[0179] As a possible implementation, not only can the user with upload permission be prompted through the message sending control after determining the account identifier set through the user permission control, but also the user with upload permission can be directly prompted, which is convenient and fast.

[0180] As a possible implementation, the prompt to the user with upload permission can be a platform internal message of the multi-version content display platform, which can be viewed by the user logging into the platform, or a platform external message across platforms. For example, the prompt is sent to the user through a short message, a social platform, or a non-multi-version content display platform.

[0181] As a possible implementation, the blogger can also set the maximum number of branch content for the multi-version content. See D1-D2.

[0182] D1: In response to obtaining the confirmation operation for the multi-version production interval, display the branch content number control.

[0183] The branch content number control is used to set the maximum number of branch content, that is, the maximum number of branch content displayed in the multi-version production interval, or in other words, the maximum number of branch content that the user can upload for the same multi-version production interval of the same multi-version content. For example, the maximum upload number is determined by inputting a number, by a drop-down box, etc. The present application does not make specific limitations.

[0184] As a possible implementation, in response to obtaining the confirmation operation for the multi-version production interval, the branch content number control and the user permission control are displayed.

[0185] Referring to Figure 9 , the figure is a schematic diagram of the present application for displaying the branch content number control and the user permission control. In Figure 9 , the branch content number control 902 and the user permission control 901 are displayed on the same page. The blogger can set the user with upload permission and the maximum upload number in the same page, which is convenient and fast.

[0186] As a possible implementation, the multi-version content display platform can also set a maximum number of branch content for a multi-version content, so that the maximum number of branch content that the user can upload for the multi-version content set by the blogger through the branch content number control is less than the maximum number of branch content for a multi-version content set by the multi-version content display platform, so as to reduce the storage pressure of the multi-version content display platform.

[0187] D2: After determining the maximum number of branch content through the content number control, upload the multi-version content.

[0188] It can be understood that the number of branch content of the multi-version content is less than or equal to the maximum upload number.

[0189] Since the attention of a person is generally more focused on 3-5 contents, the blogger can set the number of branch contents to be 5 or the like by using the branch content number control.

[0190] In this way, by using the branch content number control, the blogger can also set the maximum upload number of branch contents for the multi-version content, so as to reduce the storage pressure of the multi-version content display platform, prevent too many branch contents from affecting the subsequent selection of the audience, and improve the user experience.

[0191] After the process of uploading the multi-version content by the blogger and opening the permission of uploading the branch content by the audience, the way of uploading the branch content by the audience is described below.

[0192] Referring to Figure 10 , this figure is a flowchart of a content interaction method provided by an embodiment of the present application. In order to facilitate description, the following embodiments are still described by taking the terminal device as an execution subject of the content interaction method. As Figure 10 shown, the content interaction method includes S1001-S1002.

[0193] S1001: In response to obtaining a selection operation for a multi-version content, uploading a target branch content.

[0194] When the audience selects the multi-version content, in response to obtaining a trigger operation for the multi-version content, the audience selects and uploads the branch content for the multi-version content, i.e., the target branch content.

[0195] Referring to Figure 11 , this figure is a schematic diagram of uploading a branch content provided by an embodiment of the present application. In Figure 11 , after the audience selects a multi-version content for which the audience wants to upload a branch content from a plurality of multi-version contents, the selection of the multi-version content is realized based on the confirmation control 1101 (such as the control marked as confirmation). Figure 11 Then, the branch content that the audience wants to upload, i.e., the target branch content 1102 (such as content D in Figure 11 ), is selected, and the uploading of the target branch content 1102 is realized based on the confirmation control 1103 (such as the control marked as confirmation). Figure 11

[0196] As a possible implementation manner, after logging in the multi-version content display platform, the audience can receive a prompt sent by the display platform for the permission of uploading a branch content for a certain multi-version content. The audience can also receive a prompt sent by the display platform for the permission of uploading a branch content for a certain multi-version content in other social platforms.

[0197] ​S1002: If the target branch content is successfully uploaded, the target branch content will be determined as one of the multiple branch contents displayed in the multi-version production interval.

[0198] If the target branch content is uploaded successfully, then the target branch content becomes a branch of the multi-version content within the multi-version production interval. See also... Figure 11 The multi-version production area includes three types of branch content: target branch content, branch content 1, and branch content 2.

[0199] Therefore, when a blogger grants viewers permission to upload branch content for multiple versions of content, viewers can create and upload target branch content. After successful upload, the target branch content can be used as one of the multiple branches included in the multiple versions of content. This enables bloggers and viewers to co-create multiple versions of content. In other words, multiple branches of the same multiple versions of content can be created and uploaded by multiple creators, thereby reducing the production difficulty and workload for each creator.

[0200] As one possible implementation, if a multi-version content includes multiple multi-version production intervals, viewers can choose one of the multi-version production intervals to upload the target branch content, see E1-E2 for details.

[0201] E1: In response to a selection operation for multi-version content, display multiple multi-version production ranges for multi-version content.

[0202] If a multi-version content includes multiple multi-version production sections, then after the viewer selects the multi-version content, the multiple multi-version production sections included in the multi-version content will be displayed, and branch content can be uploaded to each multi-version production section.

[0203] E2: In response to a triggered operation targeting a target multi-version production range among multiple multi-version production ranges, upload the target branch content to the target multi-version production range.

[0204] Viewers can select one of several multi-version production zones. Taking the target multi-version production zone as an example, viewers can upload target branch content to the target multi-version production zone, which will then display the target branch content.

[0205] Therefore, if a multi-version content includes multiple multi-version production sections, multiple multi-version production sections can be displayed for the multi-version content, so that viewers can select one of the multi-version production sections to upload the target branch content, which is convenient and quick.

[0206] As one possible implementation, if the blogger sets upload permissions for multiple versions of content, then only viewers with upload permissions can upload content from the target branch. See F1-F2 for details.

[0207] F1: Retrieves the account identifier of the uploaded target branch content, as well as a set of account identifiers that correspond to multiple versions of the content.

[0208] If a blogger sets upload permissions for multiple versions of content, then each version of the content corresponds to a set of account identifiers with upload permissions. When a viewer wants to upload content to a target branch of that content, they need to obtain the account identifier for the target branch and the set of account identifiers that correspond to that content for subsequent comparison.

[0209] F2: If the set of account identifiers includes account identifiers that are the same as the account identifiers of the target branch content being uploaded, then the account identifiers of the target branch content being uploaded have the permission to upload branch content for multiple versions of content.

[0210] The audience's account identifier is compared with the set of account identifiers. If the audience's account identifier matches one of the account identifiers in the set of account identifiers, that is, if the set of account identifiers includes the same account identifier as the account identifier of the target branch content, then the account identifier of the target branch content has the permission to upload branch content for multiple versions of content.

[0211] Therefore, after setting upload permissions for multiple versions of content, the blogger can determine whether each viewer has upload permissions based on their account identifier. In other words, only viewers with upload permissions can upload the branch content they create. This allows the blogger to not only interact with specific users in a targeted manner but also to ensure the quality of the multiple versions of content, preventing too much useless branch content from affecting the overall quality of the content.

[0212] As one possible implementation, viewers could be users who have been verified to have the permission to upload branch content for multiple versions of the content while watching it. Thus, when the multiple versions of the content are displayed, viewers can be prompted that they have upload permission, and then they can upload the target branch content for that version of the content.

[0213] As one possible implementation, if the blogger sets a maximum number of uploads for multiple versions of content, then viewers can only upload content for the target branch if the number of branch contents is less than the maximum number of uploads, see G1-G2 for details.

[0214] G1: Get the maximum number of uploads for multi-version content.

[0215] The maximum number of uploadable multi-version content refers to the maximum number of branch content that can be uploaded for multi-version content.

[0216] G2: If the number of historical branch contents included in the multi-version content is less than the maximum upload limit, then the target branch content is successfully uploaded.

[0217] The historical branch content included in the multi-version content refers to the branch content uploaded before the target branch content for that multi-version content. If the number of historical branch contents included in the multi-version content is less than the maximum upload limit, it means that more branch content can be uploaded for that multi-version branch content, and the target branch content is uploaded successfully.

[0218] Therefore, if a blogger sets a maximum upload limit for multiple versions of content, it's necessary to consider both the number of historical branch content and the maximum upload limit to determine whether the target branch content can be uploaded successfully. This reduces the storage pressure on the platform displaying multiple versions of content while preventing excessive branch content from influencing viewers' subsequent choices, thus improving the user experience.

[0219] As one possible implementation method, the following explanation uses the interaction process between the terminal device and the server.

[0220] See Figure 12 This figure is a signaling interaction diagram for uploading target branch content provided in an embodiment of this application.

[0221] S1201: The terminal device obtains the content of the target branch.

[0222] S1202: The terminal device sends an upload request to the server interface layer.

[0223] A server consists of a server interface layer and a server logic layer.

[0224] The upload request includes an identifier for the multiple versions of the content corresponding to the target branch, as well as an account identifier used to upload the content of the target branch.

[0225] S1203: The server interface layer sends a permission query request to the server logic layer.

[0226] The permission query request includes the identifier of the multiple versions of the content corresponding to the target branch, as well as the account identifier used to upload the content to the target branch.

[0227] S1204: The server logic layer returns the permission query result to the server interface layer.

[0228] The permission query result indicates whether upload permission is granted. The server logic layer retrieves a set of account identifiers with upload permission based on the identifiers of the multiple versions of the target branch content. If the set of account identifiers includes the account identifier for uploading the target branch content, then the account has upload permission; otherwise, it does not.

[0229] S1205: If the permission query result determines that the user has upload permission, the server interface layer sends a version number request to the server logic layer.

[0230] This version quantity request is used to query the maximum number of uploads for this multi-version content.

[0231] S1206: The server logic returns the upper limit query result to the server interface layer.

[0232] The upper limit query result is used to identify whether the historical branch content included in this multi-version content has reached the maximum upload limit.

[0233] S1207: The server interface layer sends the upload result to the terminal device.

[0234] The upload result is used to indicate whether the viewer is able to upload content for the target branch.

[0235] As one possible approach, since not all branch content uploaded by viewers attracts other viewers, in order to ensure the quality of multiple versions of content, it is possible to determine whether to retain branch content based on popularity, as detailed in H1-H3.

[0236] H1: If the number of historical branch contents included in the multi-version content is equal to the maximum upload quantity, then determine the popularity of each historical branch content.

[0237] If the number of historical branch contents included in the multi-version content is equal to the maximum upload limit, it means that the number of branch contents that have been uploaded for the multi-version content has already met the maximum upload limit, and at this time, it is not possible to upload branch contents such as the target branch content.

[0238] Popularity is used to represent the popularity of various pieces of content, such as the number of views and shares. For example, it can also be based on the ratio of upload time to views to allow for more viewing time for newly uploaded content.

[0239] H2: If the popularity of each historical branch's content meets the popularity criteria, then the upload of the target branch's content is determined to have failed.

[0240] If the popularity of each historical branch meets the popularity criteria, it means that the uploaded historical branch content is quite popular, so no more content for the target branch will be uploaded at this time.

[0241] The embodiments of this application do not specifically limit the heat conditions, and those skilled in the art can set them according to actual needs.

[0242] H3: If the target popularity does not meet the popularity criteria among the popularity of each historical branch, then delete the historical branch content corresponding to the target popularity and confirm that the target branch content was successfully uploaded.

[0243] If the target popularity threshold is not met in the popularity rankings of various historical branches, it means that the historical branch content corresponding to the target popularity is not very popular. In this case, the historical branch content can be deleted, and the target branch content can be uploaded, thus confirming that the target branch content has been successfully uploaded. The less popular branch content can then be replaced with the new branch content.

[0244] In addition, bloggers can set audience interaction values ​​and audience transfer characteristics as sorting criteria, but this application does not impose specific limitations on this.

[0245] Therefore, if the number of historical branch contents included in multiple versions of content is equal to the maximum number of uploads, it is possible to determine whether to retain historical branch contents based on popularity, thereby ensuring that the historical branch contents of multiple versions of content are all highly popular branch contents, thus improving the content quality of multiple versions of content and enhancing the user experience.

[0246] One possible implementation is to add a "popularity boost" button to help viewers increase the popularity of their uploaded content in the target branch. See I1-I2 for details.

[0247] I1: Displays the button to increase popularity.

[0248] After the content of the target branch is successfully uploaded, one or more "Increase Popularity" buttons can be displayed. These buttons are used to increase the popularity of the uploaded branch content.

[0249] Each "increase popularity" button corresponds to a strategy for increasing popularity. For example, watching and sharing can increase the intimacy value with the uploader, or the uploader can transfer feature values ​​(such as displaying the platform's virtual currency) to the sharer. This application does not make specific limitations on this.

[0250] I2: In response to the trigger action of the popularity increase button, set the popularity increase strategy corresponding to the popularity increase button for the target branch content.

[0251] If the viewer (i.e. the uploader) who uploaded the target branch content triggers the popularity increase button, it means that they want to increase the popularity of the target branch content. Then, a popularity increase strategy corresponding to the popularity increase button is set for the target branch content so that the target branch content is not deleted because of low popularity.

[0252] Therefore, by setting up a "popularity increase" button, viewers can be helped to increase the popularity of their uploaded content in the target branch, thereby increasing viewer engagement and interaction.

[0253] After explaining how viewers upload branch content, the instructions on how viewers watch multiple versions of content will be provided, see S1301-S1303 for details.

[0254] See Figure 13 The figure is a flowchart illustrating a content interaction method provided in an embodiment of this application.

[0255] S1301: Display multiple versions of content.

[0256] When a viewer selects a multiple version of content to view, that multiple version of content is displayed.

[0257] S1302: If multiple versions of content are displayed in the multiple version production area, then multiple branches of content for the multiple versions will be displayed.

[0258] If multiple versions of content are displayed in the multiple version production area, such as at the beginning of the multiple version production area, and the multiple version production area is used to display multiple branches of content, then multiple branches of content for the multiple versions will be displayed.

[0259] For example, if the multi-version content is text-based, then when a viewer views the text content corresponding to the multi-version production period, multiple branching content will be displayed. Similarly, if the multi-version content is video-based, then when a viewer watches the video content corresponding to the multi-version production period, multiple branching content will be displayed.

[0260] Understandably, if there is a lot of content in a branch, then the content identifiers of the branch content, such as titles and plot points, can be displayed. This application does not make any specific restrictions on this.

[0261] S1303: In response to a selection operation for the first branch content to be displayed among multiple branch contents, display the first branch content to be displayed.

[0262] Users can only view one branch of content from multiple branches. In response to the selection of the first branch to be displayed among the multiple branches, the first branch to be displayed is displayed.

[0263] Therefore, when the multi-version content is displayed to the beginning of the multi-version production interval, the audience can see multiple branches of content corresponding to that multi-version production interval. The audience can then select one branch from these branches as the first branch to be displayed, thus enabling the display of that first branch.

[0264] As one possible implementation method, the following explanation uses the interaction process between the terminal device and the server.

[0265] See Figure 14 This figure is a signaling interaction diagram for viewing multiple versions of content provided in an embodiment of this application.

[0266] S1401: Terminal devices display multiple versions of content.

[0267] S1402: The terminal device sends a request to the server to retrieve branch content.

[0268] The request to retrieve branch content includes identifiers for multiple versions of the content.

[0269] S1403: The server sends a combined data packet to the terminal device.

[0270] This combined data package includes preview content for each of the various branches.

[0271] S1404: The terminal device sends an identifier of the first branch content to be displayed to the server.

[0272] S1405: The server sends the first branch content to be displayed to the terminal device.

[0273] S1406: The terminal device displays the content of the first branch to be displayed in the multi-version production area.

[0274] As one possible implementation, to facilitate viewers' selection of the branch content they wish to view, preview content could be provided for multiple branch content options. When multiple versions of content are displayed in the multiple version production area, in addition to showing the various branch content options for each version, preview content corresponding to each branch content could also be displayed. In response to a trigger operation for the first branch content to be displayed among the multiple branch content options, that first branch content would be displayed in the multiple version production area.

[0275] The preview content is used to describe the branch content. Taking video content as an example, it could be the first few frames of the branch content, plot summary text, etc., and this application does not make specific limitations on it.

[0276] This allows for the display of multiple branches of content in a preview format, making it easier for viewers to quickly select the branch they want to watch and improving the user experience.

[0277] The following section uses multiple versions of video content as an example to explain how to display the preview content corresponding to the various branches of content for multiple versions. See J1-J3 for details.

[0278] The multiple versions of content include the second branch content to be displayed and the third branch content to be displayed. The second branch content to be displayed and the third branch content to be displayed are different branch contents. The first branch content to be displayed can be the second branch content to be displayed, or it can be the third branch content to be displayed, or it can be neither. This application does not make specific limitations in this regard.

[0279] J1: When displaying multi-version content within the multi-version production range, retrieve the combined data package.

[0280] The combined data packet is a data packet jointly encoded from the first n video frames of the second branch to be displayed and the first m video frames of the third branch to be displayed, where m is a positive integer and n is a positive integer.

[0281] In other words, the first few video frames of multiple versions of content are encoded into the same data packet to obtain a combined data packet. When the multi-version content is displayed at the beginning of the multi-version production interval, this combined data packet is obtained to display the preview content.

[0282] J2: Decode the combined data packets to obtain the first n video frames of the second branch to be displayed and the first m video frames of the third branch to be displayed.

[0283] The embodiments of this application do not specifically limit the encoding and decoding methods, and those skilled in the art can set them according to actual needs.

[0284] J3: Displays the first n video frames of the second branch to be displayed and the first m video frames of the third branch to be displayed.

[0285] The preview content includes the first n video frames of the second branch to be displayed and the first m video frames of the third branch to be displayed.

[0286] Therefore, when multiple versions of content are video content, the first few video frames of various branches can be encoded into the same combined data packet. This allows for the acquisition of the first few video frames corresponding to each branch based on a single encoding and decoding, enabling rapid display to the audience and achieving the effect of opening multiple branches of content instantly, thus improving the user experience.

[0287] As one possible implementation, when displaying the first n video frames of the second branch content and the first m video frames of the third branch content, one of the second or third branch content can be designated as the primary content and the other as a secondary content. This allows displaying video frames of both the primary and secondary branch content while playing the audio of the primary branch content. In other words, multiple branch content video frames are displayed simultaneously, but only the audio of the primary content is played, thus avoiding disruption to the viewer's viewing experience.

[0288] This application does not specifically limit the method of determining the main content, such as taking the most popular branch content as the main content, or taking the branch content created by the blogger as the main content, etc. This application does not make specific limitations in this regard.

[0289] Therefore, by designating one branch of content as the primary content and the others as secondary content, when displaying previews of multiple branches, only the first few video frames of all branches are shown, while only the audio of the primary content is played. This avoids negatively impacting the viewer's experience.

[0290] Therefore, this application introduces the permissions for bloggers to upload multiple versions of content and grant viewers the right to upload branch content, the methods for viewers to upload branch content, and the methods for viewers to view multiple versions of content. Below, we will further combine... Figure 15 Please provide an explanation.

[0291] See Figure 15 This figure is a schematic diagram of a content interaction method provided in an embodiment of this application. Figure 15 This includes the blogger uploading multiple versions of content, setting permissions for viewers to upload branch content, successful upload of multiple versions of content, viewers uploading branch content, and viewers watching multiple versions of content.

[0292] For details on bloggers uploading multiple versions of content, please refer to S301-S303. For setting permissions for viewers uploading branch content, please refer to A1-A2. For viewers uploading branch content, please refer to S1001-S1002. For viewers viewing multiple versions of content, please refer to S1301-S1303.

[0293] In relation to the content interaction method described above, this application also provides a corresponding content interaction device so that the above content interaction method can be applied and implemented in practice.

[0294] See Figure 16 This figure is a schematic diagram of the structure of a content interaction device provided in an embodiment of this application. Figure 16 As shown, the content interaction device 1600 includes: a display unit 1601, a setting unit 1602, and an upload unit 1603;

[0295] The display unit 1601 is used to display a multi-person creation control in response to obtaining the content to be uploaded;

[0296] The setting unit 1602 is used to set a multi-version production range for the content to be uploaded in response to obtaining a trigger operation for the multi-person production control;

[0297] The uploading unit 1603 is used to upload multi-version content in response to obtaining a confirmation operation for the multi-version production range. The multi-version content is content with a multi-person production identifier added to the content to be uploaded. The multi-person production identifier is used to indicate that the multi-version content supports displaying multiple branch content in the multi-version production range. The multiple branch content is obtained by uploading multiple account identifiers.

[0298] As one possible implementation, the uploading unit 1603 is specifically used for:

[0299] In response to obtaining confirmation for the multiple version production range, a user permission control is displayed;

[0300] After determining the set of account identifiers through the user permission control, the multi-version content is uploaded. The account identifiers included in the set of account identifiers have the permission to upload branch content for the content to be uploaded, and the multi-version content has a corresponding relationship with the set of account identifiers.

[0301] As one possible implementation, the content interaction device 1600 further includes a message unit for:

[0302] After determining the account identifier set through the user permission control, a message sending control is displayed;

[0303] In response to receiving a trigger operation for the message sending control, a prompt for the multi-version content upload branch content is sent to the account identifiers included in the account identifier set.

[0304] As one possible implementation, the uploading unit 1603 is specifically used for:

[0305] In response to obtaining confirmation for the multi-version production range, a branch content quantity control is displayed;

[0306] After determining the maximum upload quantity of the various branch content through the content quantity control, the multiple versions of the content are uploaded, and the quantity of the various branch content is less than or equal to the maximum upload quantity.

[0307] As one possible implementation, the uploading unit 1603 is specifically used for:

[0308] Upload the multi-version content and its metadata, which includes a multi-person creation identifier for the multi-version content, whether the multi-person creation function is enabled for the multi-version content, the start position of the multi-version creation interval, and the end position of the multi-version creation interval.

[0309] As one possible implementation, the uploading unit 1603 is specifically used for:

[0310] The metadata of the multi-version content is encrypted to obtain the encrypted metadata of the multi-version content;

[0311] Upload the multi-version content and the encrypted metadata of the multi-version content.

[0312] See Figure 17 This figure is a schematic diagram of the structure of a content interaction device provided in an embodiment of this application. Figure 17 As shown, the content interaction device 1700 includes: an uploading unit 1701 and a determining unit 1702;

[0313] The upload unit 1701 is used to upload target branch content in response to obtaining a selection operation for multi-version content. The multi-version content is content with a multi-person production identifier. The multi-person production identifier is used to indicate that the multi-version content supports displaying multiple branch contents in the multi-version production interval.

[0314] The determining unit 1702 is used to determine the target branch content as one of the multiple branch contents displayed in the multiple version production interval if the target branch content is successfully uploaded.

[0315] As one possible implementation, the content interaction device 1700 further includes a branch selection unit for:

[0316] Display the aforementioned multiple versions of content;

[0317] When the multi-version content is displayed in the multi-version production area, preview content of various branches is displayed;

[0318] In response to a trigger operation targeting the first branch content to be displayed among the multiple branch contents, the first branch content to be displayed is displayed in the multi-version production interval.

[0319] As one possible implementation, if the multi-version content is video content, and the multi-version content includes a second branch content to be displayed and a third branch content to be displayed, wherein the second branch content to be displayed and the third branch content to be displayed are different branch contents, then the branch selection unit is specifically used for:

[0320] When the multi-version content is displayed in the multi-version production interval, a combined data packet is obtained. The combined data packet is a data packet jointly encoded based on the first n video frames of the second branch content to be displayed and the first m video frames of the third branch content to be displayed, where m is a positive integer and n is a positive integer.

[0321] The combined data packet is decoded to obtain the first n video frames of the second branch content to be displayed and the first m video frames of the third branch content to be displayed;

[0322] The preview content includes the first n video frames of the second branch content to be displayed and the first m video frames of the third branch content to be displayed.

[0323] As one possible implementation, the branch selection unit is specifically used for:

[0324] From the second branch content to be displayed and the third branch content to be displayed, determine the main branch content and the non-main branch content, wherein the main branch content and the non-main branch content are different branch contents;

[0325] Display video frames of the main branch content and video frames of the non-main branch content, and play the audio of the main branch content.

[0326] As one possible implementation, the uploading unit 1701 is specifically used for:

[0327] In response to a selection operation for multiple versions of content, multiple production ranges for the multiple versions of content are displayed;

[0328] In response to a triggered operation targeting a target multi-version production interval among the plurality of multi-version production intervals, the target branch content is uploaded to the target multi-version production interval.

[0329] As one possible implementation, the content interaction device 1700 further includes a permission unit for:

[0330] Obtain the account identifier that uploaded the target branch content, and the set of account identifiers that correspond to the multiple versions of the content;

[0331] If the set of account identifiers includes the same account identifier as the account identifier that uploaded the target branch content, then the account identifier that uploaded the target branch content has the authority to upload branch content for the multi-version content.

[0332] As one possible implementation, the content interaction device 1700 further includes a quantity unit for:

[0333] Get the maximum number of uploads for the multiple versions of content;

[0334] If the number of historical branch contents included in the multi-version content is less than the maximum upload quantity, then the target branch content is determined to have been successfully uploaded. The historical branch content refers to the branch content uploaded before the target branch content.

[0335] As one possible implementation, the quantity unit is also used for:

[0336] If the number of historical branch contents included in the multi-version content is equal to the maximum upload quantity, then the popularity of each historical branch content is determined.

[0337] If the popularity of each of the historical branch contents meets the popularity condition, then the upload of the target branch content is determined to have failed.

[0338] If the target popularity does not meet the popularity condition among the popularity of each of the historical branch contents, then the historical branch content corresponding to the target popularity is deleted, and the target branch content is determined to have been successfully uploaded.

[0339] As one possible implementation, after uploading the target branch content, the content interaction device 1700 further includes a popularity unit, used for:

[0340] Displays a button to increase popularity;

[0341] In response to receiving a trigger operation for the popularity increase button, a popularity increase strategy corresponding to the popularity increase button is set for the target branch content.

[0342] In conjunction with the content interaction method described above, this application also provides a corresponding content interaction system to enable the above content interaction method to be applied and implemented in practice. The content interaction system includes a first device and a second device;

[0343] The first device is used to perform the methods related to embodiments S301-S303;

[0344] The second device is used to perform the methods associated with embodiments S1001-S1002.

[0345] This application also provides a computer device, which can be a server or a terminal device. The computer device provided in this application will be described below from a hardware implementation perspective. Figure 18 The diagram shown is a schematic of the server's structure. Figure 19 The diagram shown is a structural schematic of the terminal device.

[0346] See Figure 18 This figure is a schematic diagram of a server structure provided in an embodiment of this application. The server 1800 can vary considerably due to different configurations or performance, and may include one or more processors 1822, such as a central processing unit (CPU), memory 1832, and one or more storage media 1830 (e.g., one or more mass storage devices) for application programs 1842 or data 1844. The memory 1832 and storage media 1830 can be temporary or persistent storage. The program stored in the storage media 1830 may include one or more modules (not shown in the figure), each module may include a series of instruction operations on the server. Furthermore, the processor 1822 may be configured to communicate with the storage media 1830 and execute the series of instruction operations in the storage media 1830 on the server 1800.

[0347] Server 1800 may also include one or more power supplies 1826, one or more wired or wireless network interfaces 1850, one or more input / output interfaces 1858, and / or one or more operating systems 1841, such as Windows Server. TM Mac OS X TM Unix TM Linux TM FreeBSD TM etc.

[0348] The steps performed by the server in the above embodiments can be based on this Figure 18 The server structure shown.

[0349] The processor 1822 is used to perform the following steps:

[0350] In response to receiving the content to be uploaded, a control panel created by multiple users is displayed;

[0351] In response to receiving a trigger operation for the multi-person creation control, a multi-version creation range is set for the content to be uploaded;

[0352] In response to obtaining confirmation for the multi-version production range, multi-version content is uploaded. The multi-version content is content with a multi-person production identifier added to the content to be uploaded. The multi-person production identifier is used to indicate that the multi-version content supports displaying multiple branch content in the multi-version production range. The multiple branch content is obtained by uploading multiple account identifiers.

[0353] Alternatively, processor 1822 is used to perform the following steps:

[0354] In response to the selection operation for multiple versions of content, the target branch content is uploaded. The multiple version content is content with a multi-person production identifier. The multi-person production identifier is used to indicate that the multiple version content supports displaying multiple branch contents in the multiple version production interval.

[0355] If the target branch content is successfully uploaded, the target branch content will be identified as one of the multiple branch contents displayed in the multiple version production interval.

[0356] Optionally, the processor 1422 may also execute method steps of any specific implementation of the content interaction method in the embodiments of this application.

[0357] See Figure 19 This figure is a schematic diagram of the structure of a terminal device provided in an embodiment of this application. The description will be based on a smartphone as an example. Figure 19 The diagram shown is a partial structural block diagram of the smartphone, which includes: a radio frequency (RF) circuit 1910, a memory 1920, an input unit 1930, a display unit 1940, a sensor 1950, an audio circuit 1960, a Wi-Fi module 1970, a processor 1980, and a power supply 1990, among other components. Those skilled in the art will understand that... Figure 19 The smartphone structure shown does not constitute a limitation on smartphones and may include more or fewer components than shown, or combine certain components, or have different component arrangements.

[0358] The following is combined with Figure 19 A detailed introduction to the various components of a smartphone:

[0359] The RF circuit 1910 can be used to receive and transmit signals during information transmission or calls. In particular, it receives downlink information from the base station and processes it with the processor 1980; in addition, it transmits uplink data to the base station.

[0360] The memory 1920 can be used to store software programs and modules, and the processor 1980 runs the software programs and modules stored in the memory 1920 to realize various functions and data processing of the smartphone.

[0361] Input unit 1930 can be used to receive input numeric or character information and generate key signal inputs related to user settings and function control of the smartphone. Specifically, input unit 1930 may include touch panel 1931 and other input devices 1932. Touch panel 1931, also known as a touch screen, can collect touch operations on or near the user and drive corresponding connected devices according to a pre-set program. In addition to touch panel 1931, input unit 1930 may also include other input devices 1932. Specifically, other input devices 1932 may include, but are not limited to, one or more of the following: physical keyboard, function keys (such as volume control buttons, power buttons, etc.), trackball, mouse, joystick, etc.

[0362] The display unit 1940 can be used to display information input by the user or information provided to the user, as well as various menus of the smartphone. The display unit 1940 may include a display panel 1941, which may optionally be configured as a liquid crystal display (LCD), an organic light-emitting diode (OLED), or the like.

[0363] Smartphones may also include at least one sensor 1950, such as a light sensor, a motion sensor, and other sensors. Other sensors that smartphones may also be equipped with, such as gyroscopes, barometers, hygrometers, thermometers, and infrared sensors, will not be detailed here.

[0364] Audio circuitry 1960, speaker 1961, and microphone 1962 provide an audio interface between the user and the smartphone. Audio circuitry 1960 converts received audio data into electrical signals and transmits them to speaker 1961, where speaker 1961 converts them into sound signals for output. On the other hand, microphone 1962 converts collected sound signals into electrical signals, which are received by audio circuitry 1960, converted into audio data, and then processed by processor 1980 before being transmitted via RF circuitry 1910 to, for example, another smartphone, or the audio data can be output to memory 1920 for further processing.

[0365] The processor 1980 is the control center of the smartphone, connecting various parts of the smartphone via various interfaces and lines. It performs various functions and processes data by running or executing software programs and / or modules stored in the memory 1920, and by calling data stored in the memory 1920. Optionally, the processor 1980 may include one or more processing units.

[0366] The smartphone also includes a power supply 1990 (such as a battery) that supplies power to various components. Preferably, the power supply can be logically connected to the processor 1980 through a power management system, thereby enabling functions such as charging, discharging, and power consumption management through the power management system.

[0367] Although not shown, smartphones may also include a camera, Bluetooth module, etc., which will not be described in detail here.

[0368] In this embodiment of the application, the memory 1920 included in the smartphone can store computer programs and transmit the computer programs to the processor.

[0369] The processor 1980 included in the smartphone can execute the content interaction method provided in the above embodiments according to the instructions in the computer program.

[0370] This application also provides a computer-readable storage medium for storing a computer program that executes the content interaction method provided in the above embodiments.

[0371] This application also provides a computer program product or computer program that includes computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the computer device to perform the content interaction methods provided in the various optional implementations of the above aspects.

[0372] Those skilled in the art will understand that all or part of the steps of the above method embodiments can be implemented by hardware related to program instructions. The aforementioned program can be stored in a computer-readable storage medium. When the program is executed, it performs the steps of the above method embodiments. The aforementioned storage medium can be at least one of the following media: read-only memory (ROM), RAM, magnetic disk or optical disk, and other media that can store computer programs.

[0373] The terms "first," "second," "third," "fourth," etc. (if present) in the specification, claims, and accompanying drawings of this application are used to distinguish similar objects and are not necessarily used to describe a particular order or sequence. It should be understood that such use of data can be interchanged where appropriate so that the embodiments of this application described herein can be implemented, for example, in orders other than those illustrated or described herein. Furthermore, the terms "comprising" and "corresponding to," and any variations thereof, are intended to cover a non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.

[0374] In this application embodiment, the terms "module" or "unit" refer to a computer program or part of a computer program that has a predetermined function and works with other related parts to achieve a predetermined goal, and can be implemented wholly or partially using software, hardware (such as processing circuitry or memory), or a combination thereof. Similarly, a processor (or multiple processors or memory) can be used to implement one or more modules or units. Furthermore, each module or unit can be part of an overall module or unit that includes the functionality of that module or unit.

[0375] It should be noted that the various embodiments in this specification are described in a progressive manner, and the same or similar parts between the various embodiments can be referred to mutually. Each embodiment focuses on describing the differences from other embodiments. In particular, for the device and system embodiments, since they are basically similar to the method embodiments, the description is relatively simple, and the relevant parts can be referred to the description of the method embodiments. The device and system embodiments described above are merely illustrative. The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of the modules can be selected to achieve the purpose of the solution in this embodiment according to actual needs. Those skilled in the art can understand and implement this without creative effort.

[0376] The above description is merely one specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the technical scope disclosed in this application should be included within the scope of protection of this application. Based on the implementation methods provided in the above aspects, this application can also be further combined to provide more implementation methods. Therefore, the scope of protection of this application should be determined by the scope of the claims.< / params> < / fragment> < / fragment> < / tag>

Claims

1. A content interaction method, characterized by, The method comprises: in response to obtaining to-be-uploaded content, displaying a multi-person production control; in response to obtaining a triggering operation on the multi-person production control, setting a multi-version production interval for the to-be-uploaded content; in response to obtaining a confirmation operation on the multi-version production interval, uploading multi-version content, the multi-version content being content to which a multi-person production identifier is added, the multi-person production identifier being used to represent that the multi-version content supports displaying multiple branch contents in the multi-version production interval, the multiple branch contents being uploaded by multiple account identifiers.

2. The method of claim 1, wherein, The method further comprises: in response to obtaining a confirmation operation on the multi-version production interval, displaying a user permission control; after determining a set of account identifiers through the user permission control, uploading the multi-version content, the account identifiers in the set of account identifiers having the permission to upload branch content for the to-be-uploaded content, the multi-version content having a corresponding relationship with the set of account identifiers.

3. The method of claim 2, wherein, The method further comprises: after determining a set of account identifiers through the user permission control, displaying a message sending control; in response to obtaining a triggering operation on the message sending control, sending a prompt to upload branch content for the multi-version content to the account identifiers in the set of account identifiers.

4. The method of claim 1, wherein, The method further comprises: in response to obtaining a confirmation operation on the multi-version production interval, displaying a branch content quantity control; after determining a maximum upload quantity of the multiple branch contents through the content quantity control, uploading the multi-version content, the number of the multiple branch contents being less than or equal to the maximum upload quantity.

5. The method of claim 1, wherein, The method further comprises: uploading the multi-version content and metadata of the multi-version content, the metadata comprising a multi-person production identifier of the multi-version content, whether the multi-person production function of the multi-version content is enabled, a start position of the multi-version production interval, and an end position of the multi-version production interval.

6. The method of claim 5, wherein, The method further comprises: encrypting the metadata of the multi-version content to obtain encrypted metadata of the multi-version content; uploading the multi-version content and the encrypted metadata of the multi-version content.

7. A content interaction method characterized by, The method comprises: in response to obtaining a selection operation on multi-version content, uploading target branch content, the multi-version content being content with a multi-person production identifier, the multi-person production identifier being used to represent that the multi-version content supports displaying multiple branch contents in a multi-version production interval; if the target branch content is successfully uploaded, determining the target branch content as one of the multiple branch contents displayed by the multi-version content in the multi-version production interval.

8. The method of claim 7, wherein, The method further comprises: displaying the multi-version content; when the multi-version content is displayed to the multi-version production interval, displaying preview content of the multiple branch contents. In response to a triggering operation for a first to-be-displayed branch content in the plurality of branch contents, the first to-be-displayed branch content is displayed in the multi-version production interval.

9. The method of claim 8, wherein, If the multi-version content is video content, the multi-version content includes a second to-be-displayed branch content and a third to-be-displayed branch content, and the second to-be-displayed branch content and the third to-be-displayed branch content are different branch contents, the displaying of the preview content of each branch content when the multi-version content is displayed in the multi-version production interval includes: When the multi-version content is displayed in the multi-version production interval, a combined data packet is obtained, the combined data packet is a data packet obtained by jointly encoding the first n video frames of the second to-be-displayed branch content and the first m video frames of the third to-be-displayed branch content, m is a positive integer, and n is a positive integer; The combined data packet is decoded to obtain the first n video frames of the second to-be-displayed branch content and the first m video frames of the third to-be-displayed branch content; The first n video frames of the second to-be-displayed branch content and the first m video frames of the third to-be-displayed branch content are displayed, and the preview content includes the first n video frames of the second to-be-displayed branch content and the first m video frames of the third to-be-displayed branch content.

10. The method of claim 9, wherein, The displaying of the first n video frames of the second to-be-displayed branch content and the first m video frames of the third to-be-displayed branch content includes: The main push branch content and the non-main push branch content are determined from the second to-be-displayed branch content and the third to-be-displayed branch content, the main push branch content and the non-main push branch content are different branch contents; The video frames of the main push branch content and the video frames of the non-main push branch content are displayed, and the audio of the main push branch content is played.

11. The method of claim 7, wherein, The uploading of the target branch content in response to the obtaining of the selection operation for the multi-version content includes: In response to the obtaining of the selection operation for the multi-version content, a plurality of multi-version production intervals for the multi-version content are displayed; In response to a triggering operation for a target multi-version production interval in the plurality of multi-version production intervals, the target branch content is uploaded for the target multi-version production interval.

12. The method of claim 7, wherein, The method further includes: An account identifier of the account that uploads the target branch content and a set of account identifiers that have a corresponding relationship with the multi-version content are obtained; If the set of account identifiers includes an account identifier that is the same as the account identifier of the account that uploads the target branch content, the account identifier of the account that uploads the target branch content has the permission to upload branch content for the multi-version content.

13. The method of claim 7, wherein, The method further includes: If the number of historical branch contents included in the multi-version content is less than the maximum upload number, it is determined that the target branch content is uploaded successfully, and the historical branch content is a branch content uploaded before the target branch content.

14. The method of claim 13, wherein, The method further includes: If the number of historical branch contents included in the multi-version content is equal to the maximum upload number, the heat of each historical branch content is determined; If the heat of each historical branch content meets the heat condition, it is determined that the target branch content fails to be uploaded. If the target heat degree does not satisfy the heat degree condition among the heat degrees of the historical branch content, the historical branch content corresponding to the target heat degree is deleted, and it is determined that the target branch content is uploaded successfully.

15. The method of claim 13, wherein, After uploading the target branch content, the method further includes: displaying a heat degree increasing button; In response to obtaining a triggering operation on the heat degree increasing button, a heat degree increasing strategy corresponding to the heat degree increasing button is set for the target branch content.

16. A content interaction device, characterized by The device includes a display unit, a setting unit, and an uploading unit. The display unit is configured to display a multi-person production control in response to obtaining to-be-uploaded content. The setting unit is configured to set a multi-version production interval for the to-be-uploaded content in response to obtaining a triggering operation on the multi-person production control. The uploading unit is configured to upload multi-version content in response to obtaining a confirmation operation on the multi-version production interval, the multi-version content being content with a multi-person production identifier added to the to-be-uploaded content, the multi-person production identifier being used to represent that the multi-version content supports displaying multiple branch contents in the multi-version production interval, the multiple branch contents being obtained by uploading multiple account identifiers.

17. A content interaction device, characterized by The device includes an uploading unit and a determining unit. The uploading unit is configured to upload target branch content in response to obtaining a selection operation on multi-version content, the multi-version content being content with a multi-person production identifier, the multi-person production identifier being used to represent that the multi-version content supports displaying multiple branch contents in a multi-version production interval. The determining unit is configured to determine the target branch content as one of the multiple branch contents displayed by the multi-version content in the multi-version production interval if the target branch content is uploaded successfully.

18. A content interaction system characterized by, The system includes a first device and a second device. The first device is configured to perform the method of any one of claims 1-6. The second device is configured to perform the method of any one of claims 7-15.

19. A computer device, comprising: The computer device includes a processor and a memory: The memory is configured to store a computer program and transmit the computer program to the processor. The processor is configured to perform the method of any one of claims 1-6 or the method of any one of claims 7-15 according to the computer program.

20. A computer program product comprising a computer program, characterised in that, When it runs on a computer device, it makes the computer device perform the method of any one of claims 1-6 or the method of any one of claims 7-15.

Images