Content interaction method and apparatus, computer device, and program product

Abstract

Embodiments of the present application disclose a content interaction method and apparatus, a computer device, and a program product. When content to be uploaded is obtained, a multi-user creation control is displayed, wherein the multi-user creation control is used for granting other accounts permission to upload branch content for the content to be uploaded. If a trigger operation for the multi-user creation control is obtained, a multi-version creation section for the content to be uploaded, i.e., which part of said content is used for displaying multiple types of branch content, is set. Once the multi-version creation section is set, multi-version content is uploaded. The multi-version content is content to be uploaded that has a multi-user creation identifier, the multi-user creation identifier is used for representing that the content to be uploaded supports displaying the multiple types of branch content in the multi-version creation section, and the multiple types of branch content are uploaded by multiple accounts. Therefore, multiple types of branch content for the same multi-version content can be created and uploaded by multiple creators, thereby reducing the creation difficulty and workload of each creator.

Description

A content interaction method, apparatus, computer device, and program product

[0001] This application claims priority to Chinese Patent Application No. 202411204593.3, filed on August 29, 2024, entitled “A Content Interaction Method, Apparatus, Computer Equipment and Program Product”, the entire contents of which are incorporated herein by reference. Technical Field

[0002] This disclosure relates to the field of Internet technology, and more specifically to content interaction. Background Technology

[0003] Multi-version content refers to content that can have multiple different versions of the storyline, i.e., multiple branching narratives. For example, a video recording a journey from point A to point B using different modes of transportation can generate multiple different versions of the video content, each representing a branching narrative. Viewers can choose different branches while watching multi-version content, thus experiencing different content and enhancing the user experience.

[0004] In related technologies, multiple versions of content are generally created by the creators of those multiple versions, which is quite difficult and involves a large workload. Summary of the Invention

[0005] 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.

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

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

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

[0009] 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;

[0010] 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.

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

[0012] 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.

[0013] 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.

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

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

[0016] 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;

[0017] 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.

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

[0019] 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.

[0020] 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.

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

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

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

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

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

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

[0027] 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.

[0028] 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.

[0029] 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 based on the content to be uploaded. If a trigger operation is obtained for this multi-user creation control, 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 supports displaying multiple branch contents within the multi-version creation range, and these branch contents are obtained from uploads by multiple accounts.

[0030] 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

[0031] Figure 1 is a schematic diagram of a multi-version content provided in an embodiment of this application;

[0032] Figure 2 is a schematic diagram of an application scenario of a content interaction method provided in an embodiment of this application;

[0033] Figure 3 is a flowchart illustrating the content interaction method provided in an embodiment of this application;

[0034] Figure 4 is a schematic diagram of a control display for multiple users provided in an embodiment of this application;

[0035] Figure 5 is a schematic diagram of setting up multiple version production intervals according to an embodiment of this application;

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

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

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

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

[0040] Figure 10 is a flowchart illustrating the content interaction method provided in an embodiment of this application;

[0041] Figure 11 is a schematic diagram of uploading branch content according to an embodiment of this application;

[0042] Figure 12 is a signaling interaction diagram of uploading target branch content provided in an embodiment of this application;

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

[0044] Figure 14 is a signaling interaction diagram for viewing multiple versions of content provided in an embodiment of this application;

[0045] Figure 15 is a schematic diagram of a content interaction method provided in an embodiment of this application;

[0046] Figure 16 is a structural schematic diagram of a content interaction device provided in an embodiment of this application;

[0047] Figure 17 is a structural schematic diagram of a content interaction device provided in an embodiment of this application;

[0048] Figure 18 is a schematic diagram of the structure of a server provided in an embodiment of this application;

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

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

[0051] The content can be video content, article content, novel content, etc., and multiple versions of content include multiple branching content. See Figure 1, which is a schematic diagram of multiple versions of content provided in an embodiment of this application. In Figure 1, the multiple versions of content are video content, and the video content has multiple branching content for a period of time, namely storyline 1, storyline 2, and storyline 3. Viewers can choose any storyline to watch, thereby increasing viewer engagement.

[0052] In related technologies, multiple versions of content are generally created independently by the creator of each version. For example, the three storylines in Figure 1 all require the creation of the video content by the creator, which is quite difficult and involves a significant workload for that creator.

[0053] 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.

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

[0055] 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.

[0056] 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.

[0057] 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.

[0058] Referring to Figure 2, this figure is a schematic diagram of an application scenario for a content interaction method provided in an embodiment of this application. As shown in Figure 2, 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 any combination of Bluetooth, local area network (LAN), metropolitan area network (MAN), wide area network (WAN), mobile, private network, or virtual private network. In some embodiments, customized or dedicated data communication technologies can be used to replace or supplement the above-mentioned data communication technologies. In this embodiment, the multiple versions of content are video content.

[0059] The following is an explanation of the multiple versions of content uploaded by the blogger. The blogger refers to the user who uploaded the content to be uploaded.

[0060] The terminal device 210 is equipped with a client for providing content interaction services, which allows bloggers to upload video content. After selecting the content to be uploaded through the client, the blogger clicks the upload control 211 (marked as "completed" in Figure 2) to upload the content they created (content D shown in Figure 2). After obtaining the content to be uploaded, the terminal device 210 displays the multi-user creation control 212 (marked as "multi-version content setting" in Figure 2). When the blogger clicks the multi-user creation control 212, it means that the blogger has granted other creators permission to create content based on the content to be uploaded, meaning that 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 interval for the content to be uploaded, that is, which part of the video content to be uploaded can have other branch content. As shown in Figure 2, the content to be uploaded is a 3-minute video, and the blogger sets the time period from the 1st minute to the 2nd minute as the multi-version creation interval, within which multiple branch contents can be created. Once the blogger has finalized the multi-version production range settings, such as by clicking the confirmation control 213 (the control marked as "confirmation" in Figure 2), the multi-version content will be uploaded. This multi-version content is content to be uploaded that has a multi-person production identifier. This multi-person production identifier indicates that the content to be uploaded supports displaying multiple branches of content in the multi-version production range. The multiple branches of content are uploaded based on multiple accounts.

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

[0062] The terminal device 220 is equipped with a client for providing interactive content services, which allows viewers to view and upload branch content. Viewers can choose which multi-version content to upload branch content for, as shown in Figure 2. After selecting multi-version content 2, they click the upload control 221 (the control marked "upload" in Figure 2) to upload the target branch content for that multi-version content. If the target branch content is successfully uploaded, it is identified as one of the multiple branch contents displayed within the multi-version production area. As shown in Figure 2, the multi-version content includes three branch contents: branch content 1, branch content 2, and the target branch content.

[0063] 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.

[0064] 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 the terminal device 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.

[0065] 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.

[0066] Referring to Figure 3, this figure is a flowchart illustrating 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. As shown in Figure 3, the content interaction method includes S301-S303.

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

[0068] The content to be uploaded is the content waiting to be uploaded, which can be text content, video content, etc. Video content can be related to games, TV series, etc. The multi-user creation control is a control used to grant viewers permission to upload branch content.

[0069] Referring to Figure 4, this figure is a schematic diagram of a multi-user creation control provided in an embodiment of this application. The blogger can first select the content they want to upload, and then click the "Complete Selection" control 401 (i.e., the control marked as "Complete" in Figure 4). The selected content then becomes the content to be created into multiple versions and uploaded. In response to obtaining the content to be uploaded, the multi-user creation control 402 (i.e., the control marked as "Multi-Version Content Setting" in Figure 4) is displayed.

[0070] 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.

[0071] 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.

[0072] 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.

[0073] 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.

[0074] 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.

[0075] 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.

[0076] Referring to Figure 5, this figure is a schematic diagram of setting a multi-version production interval according to an embodiment of this application. In Figure 5, taking video content as an example of multi-version content, after the blogger performs a trigger operation on the multi-person production control (such as clicking the multi-person production 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., the control marked as confirmation in Figure 5) and the cancellation control 502 (i.e., the control marked as cancellation in Figure 5), the start time (i.e., 1 minute as the start position) and end time (i.e., 2 minutes as the end position) of the multi-version production interval can be set.

[0077] 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 by the blogger during that interval can be considered a branch, or, depending on the blogger's choice, not considered a branch during playback. This application does not impose specific limitations on this. Similarly, 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 the blogger can upload branch content for each multiple-version production interval.

[0078] 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.

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

[0080] The confirmation operation is used to determine the production range of multiple versions. This can be a single click, double click, interactive action, etc., and this application does not specify any particular limitation. After the blogger determines the production range of multiple versions, a multi-person production identifier can be added to the content to be uploaded, resulting in multiple versions of the content, which can then be uploaded.

[0081] 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 period, and that these multiple branches of content are uploaded through multiple account identifiers. 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 multiple branches of content based on their own accounts. The account identifier is an identifier used to identify the account.

[0082] 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.

[0083] 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.

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

[0085] 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:

[0086] 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 starting position of the multi-version production interval, such as the start time, and end_time is the ending position of the multi-version production interval, such as the end time.

[0087] After defining the metadata, use the ffmpeg command: ffmpeg-iinput.mp4-metadata:s:v:0xml="<multi_content_video> <tag>support_multi_content_video < / tag> <params> start_time=123 < / params> <params> end_time=456 < / params> < / multi_content_video> The "-codec copy ouput.mp4" command adds metadata to the video.

[0088] Here, ffmpeg is used to invoke the FFmpeg command-line tool. `-iinput.mp4` specifies the input file as the i-th `input.mp4`. `-metadata:s:v:0` specifies the video stream (metadata) to be modified. `s:v:0` indicates 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> start_time=123 < / params> <params> end_time=456< / params> < / multi_content_video> "Used to add custom metadata. This metadata is an XML string containing a `multi_content_video` tag and multiple `params` tags. `-codec copy` instructs FFmpeg not to re-encode the video and audio streams during processing, but to copy them directly. This preserves the original quality and speeds up processing. `output.mp4` specifies the output file as output.mp4.

[0089] Furthermore, if multiple production ranges are set for the content to be uploaded, the metadata defined in XML format is as follows:

[0090] Therefore, by adding metadata to the content to be uploaded, the metadata can include not only the multi-person production identifier and the start and end positions of the multi-version production interval, but also whether the multi-person production function is enabled for the multi-version content. This distinguishes between multi-version content created by the blogger alone and multi-version content for which the blogger has given the audience permission to upload branch content, making it convenient and quick.

[0091] As one possible implementation, the metadata of multiple versions of content can be encrypted to obtain encrypted metadata for the multiple versions of content. This involves uploading both the multiple versions of content and their encrypted metadata. In other words, compared to directly uploading metadata, uploading encrypted metadata can prevent data tampering, thus preventing any impact on viewing the multiple versions of content and improving platform security.

[0092] 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 based on the content to be uploaded. If a trigger operation is obtained for this multi-user creation control, 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 supports displaying multiple branch contents within the multi-version creation range, and these branch contents are obtained from uploads by multiple accounts.

[0093] 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.

[0094] As one possible implementation, bloggers can also set which viewers can participate in uploading branch content during the process of uploading multiple versions of content, see A1-A2 for details.

[0095] A1: In response to obtaining confirmation for the multi-version production range, display the user permission control.

[0096] The user permission control is used to select users who have permission to upload branch content.

[0097] Referring to Figure 6, 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, the user permission control 601 is displayed. In Figure 6, the controls labeled as friends on social platform A, friends on social platform B, and all friends are all user permission controls 601. Users with permissions to upload branch content can be selected through different user permission controls 601, which is convenient and quick.

[0098] Referring to 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, the user permission control 701 is displayed. In Figure 7, 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 first set of account identifiers with upload permissions is obtained, thus making the selection more targeted.

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

[0100] The blogger can select users with permission to upload branch content through the user permission control. The account identifiers of users with permission to upload branch content for this multi-version content constitute the first set of account identifiers.

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

[0102] 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 (i.e., users indicated by the account identifiers included in the first set of account identifiers), but also ensures the content quality of multiple versions of content by setting specific users, thus preventing excessive and useless branch content from affecting the content quality of multiple versions of content.

[0103] One possible implementation is not only through the A1-A2 approach, where users are assigned permissions to upload branch content before uploading multiple versions of the content, but also through the B1-B2 approach, where user permission controls are displayed after uploading multiple versions of the content. This allows the blogger to further configure which viewers can participate in uploading branch content after uploading multiple versions.

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

[0105] Among them, the target multi-version content is one of the multiple multi-version content.

[0106] Referring to 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 the multiple versions of content they have uploaded as the target version of content, as shown in Figure 8, version 2 is selected as the target version of content, and user permission control 701 is displayed.

[0107] B2: After determining the second account identifier set through the user permission control, establish the correspondence between the target multi-version content and the second account identifier set.

[0108] See A1-A2 for details, which will not be repeated here. The account identifiers of users with the authority to upload branch content for multiple versions of the target content constitute the second set of account identifiers.

[0109] As one possible implementation, if a multi-version content has multiple multi-version production intervals, and different multi-version production intervals correspond to different branch content, then different upload permissions can be set based on different multi-version production intervals, that is, the user's permissions for uploading branch content can be refined, thereby meeting the diverse needs of bloggers.

[0110] Therefore, the user permission control can be displayed after multiple versions of content have been uploaded, so that users with the permission to upload branch content can be set through the user permission control, thereby meeting the diverse needs of bloggers through multiple settings.

[0111] As one possible implementation, this application embodiment provides an upload prompt function after setting up users with permissions to upload branch content, as detailed in C1-C2.

[0112] C1: After determining the first set of account identifiers through the user permission control, display the message sending control.

[0113] The message sending control is used to send a prompt to the account identifiers included in the first set of account identifiers regarding the upload of branch content for multiple versions of content.

[0114] C2: In response to the trigger operation for the message sending control, send a prompt for the multi-version content upload branch content to the account identifiers included in the first account identifier set.

[0115] As one possible implementation, after determining the first set of account identifiers through the user permission control, it is possible not only to send a prompt to users with upload permissions regarding the upload of branch content for multi-version content, but also to send a prompt to users with upload permissions regarding which multi-version production interval to upload branch content for.

[0116] Therefore, by setting up a message sending control, prompts can be sent to users with upload permissions based on the blogger's wishes, improving the blogger's experience and helping to quickly complete the production of multiple versions of content with various branches, thus improving production efficiency.

[0117] As one possible implementation, not only can a notification be sent to users with upload permissions via a message sending control after the first set of account identifiers is determined through the user permission control, but a notification can also be sent directly to users with upload permissions, which is convenient and fast.

[0118] One possible implementation is to send a notification to users with upload permissions. This could be an internal message on a multi-version content display platform, which users can view upon logging into the platform. Alternatively, it could be an external message across platforms, such as SMS or social media platforms that are not part of the multi-version content display platform.

[0119] As one possible implementation, bloggers can also set the maximum number of branch content uploads for multiple versions of content, see D1-D2 for details.

[0120] D1: In response to receiving confirmation for a multi-version production range, display a control showing the number of branches.

[0121] The branch content quantity control is used to set the maximum number of branch content items included in multiple versions of content. In other words, it specifies the maximum number of branch content items that can be displayed within a single multi-version production interval, or the maximum number of branch content items a user can upload within the same multi-version production interval for the same multi-version content. For example, the maximum upload quantity can be determined by entering a number or by using a dropdown list; this application does not impose specific limitations on this.

[0122] As one possible implementation, in response to obtaining confirmation for a multi-version production range, a branch content quantity control and a user permission control are displayed.

[0123] Referring to Figure 9, this figure is a schematic diagram illustrating a display of a branch content quantity control and a user permission control according to an embodiment of this application. In Figure 9, a branch content quantity control 902 and a user permission control 901 are displayed on the same page. The blogger can conveniently and quickly set the users with upload permissions and the maximum upload quantity on the same page.

[0124] As one possible implementation, the multi-version content display platform can also set a maximum number of branch content that can be uploaded for the multi-version content (i.e., the maximum number of uploads stipulated by the platform). Thus, the maximum number of branch content that users can upload for their multi-version content, as set by the blogger through the branch content quantity control (i.e., the maximum number of uploads set by the blogger), is less than the maximum number of uploads for a single branch content of the multi-version content display platform. In other words, the maximum number of uploads set by the blogger is less than the maximum number of uploads stipulated by the platform, thereby reducing the storage pressure on the multi-version content display platform.

[0125] D2: After determining the maximum upload quantity of various branch content through the branch content quantity control, upload multiple versions of content.

[0126] It is understandable that the number of different branches of this multi-version content is less than or equal to the maximum number of uploads set by the blogger.

[0127] Since people generally focus their attention on 3-5 items, bloggers can use the branch content quantity control to set the number of branch content to 5, etc.

[0128] Therefore, by using the branch content quantity control, bloggers can also set the maximum number of branch contents included in the uploaded multi-version content. This reduces the storage pressure on the multi-version content display platform, prevents excessive branch content from affecting the audience's subsequent choices, and improves the user experience.

[0129] After explaining how bloggers can upload multiple versions of content and how viewers can upload branch content, the following section explains how viewers can upload branch content.

[0130] Referring to Figure 10, this figure is a flowchart illustrating 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. As shown in Figure 10, the content interaction method includes S1001-S1002.

[0131] S1001: In response to the selection operation for multiple versions of content, upload the target branch content.

[0132] The selection operation is an operation used for selection, which can be a single click, double click, interactive operation, etc. This application does not make specific limitations on it.

[0133] When a viewer selects the multiple versions of content they wish to co-create, in response to the trigger action for obtaining the multiple versions of content, the viewer selects and uploads the branch content for that multiple versions of content, i.e., the target branch content.

[0134] Referring to Figure 11, this figure is a schematic diagram of uploading branch content according to an embodiment of this application. In Figure 11, after the viewer selects a multi-version content from multiple multi-version content options, the selection of the multi-version content is realized based on the confirmation control 1101 (marked as the confirmation control in Figure 11). Then, the viewer selects the branch content they want to upload, i.e., the target branch content 1102 (content D in Figure 11), and uploads the target branch content 1102 based on the upload control 1103 (marked as the upload control in Figure 11). In addition, after selecting the target branch content 1102, a second confirmation of the target branch content can be realized based on the confirmation control (marked as the confirmation control in Figure 11) to improve the accuracy of subsequent uploads.

[0135] As one possible implementation, viewers could receive a notification from the platform granting them permission to upload a branch of a specific version of the content after logging into the platform. They could also receive this notification on other social media platforms. Based on this notification, viewers could then select the version of the content for which they have permission to upload the branch, thus responding to the selection action and uploading the target branch.

[0136] 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.

[0137] If the target branch content is successfully uploaded, the target branch content becomes a branch content displayed in the multi-version production area. Continuing to refer to Figure 11, the multi-version production area includes 3 types of branch content, namely the target branch content, branch content 1, and branch content 2.

[0138] 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.

[0139] 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.

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

[0141] 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.

[0142] 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.

[0143] Viewers can select one of several multi-version production areas. Taking the selected multi-version production area as the target multi-version production area, viewers can upload target branch content to the target multi-version production area so that the target branch content can be displayed in the target multi-version production area.

[0144] 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.

[0145] 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-F3 for details.

[0146] F1: Get the account identifier of the uploaded target branch content, and the first set of account identifiers that correspond to the multiple versions of the content.

[0147] If a blogger sets upload permissions for multiple versions of content, each version of the content corresponds to a set of first-level 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 first-level account identifiers that correspond to that content for subsequent comparison.

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

[0149] The audience's account identifier is compared with the first set of account identifiers. If the audience's account identifier matches one of the account identifiers in the first set of account identifiers, that is, if the first set of account identifiers includes account identifiers that are the same 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.

[0150] F3: In response to the selection operation for multiple versions of content, and the account identifier of the target branch content has the permission to upload branch content for multiple versions of content, upload the target branch content.

[0151] In other words, whether or not the content of the target branch can be uploaded depends on whether the account ID of the target branch has upload permissions.

[0152] 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.

[0153] 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. In this way, when displaying the production sections of multiple versions of the content, viewers could be prompted that they have the upload permission, and then they could upload the target branch content for that version of the content.

[0154] 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.

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

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

[0157] 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.

[0158] 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.

[0159] 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 further branch content can be uploaded for that specific multi-version content—that is, whether the target branch content can be successfully uploaded. 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.

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

[0161] Referring to Figure 12, this figure is a signaling interaction diagram of uploading target branch content provided in an embodiment of this application.

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

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

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

[0165] 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.

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

[0167] 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.

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

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

[0170] 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.

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

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

[0173] 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.

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

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

[0176] 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.

[0177] 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.

[0178] 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.

[0179] 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.

[0180] 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.

[0181] 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.

[0182] 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.

[0183] 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.

[0184] The target popularity level is one of the popularity levels corresponding to multiple historical branches. If the target popularity level does not meet the popularity criteria among the various historical branches, it means that the historical branch content corresponding to the target popularity level is not 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 lower-popularity branch content can then be replaced with new branch content.

[0185] 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.

[0186] 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.

[0187] 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.

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

[0189] After the content in 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 content. If there are multiple "Increase Popularity" buttons, different buttons can correspond to different popularity-increasing strategies.

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

[0191] 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.

[0192] 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.

[0193] 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.

[0194] 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.

[0195] Referring to Figure 13, this figure is a flowchart illustrating a content interaction method provided in an embodiment of this application.

[0196] S1301: Display multiple versions of content.

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

[0198] 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.

[0199] 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.

[0200] 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.

[0201] 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.

[0202] 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.

[0203] 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.

[0204] 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.

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

[0206] Referring to Figure 14, this figure is a signaling interaction diagram for viewing multiple versions of content provided in an embodiment of this application.

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

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

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

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

[0211] The server determines the combined data packet based on the identifiers of the multiple versions of content. This combined data packet includes preview content corresponding to each of the various branches of content.

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

[0213] The terminal device displays preview content corresponding to multiple branches. When the user selects a branch of interest from the multiple previews, i.e. the first branch to be displayed, the terminal device sends an identifier of the first branch to be displayed to the server.

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

[0215] The server determines the first branch content to be displayed based on the identifier of the first branch content to be displayed, and sends it to the terminal device.

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

[0217] 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.

[0218] 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.

[0219] 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.

[0220] 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.

[0221] 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.

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

[0223] 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.

[0224] 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.

[0225] 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.

[0226] 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.

[0227] 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.

[0228] 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.

[0229] 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.

[0230] 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.

[0231] 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.

[0232] 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.

[0233] 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. This will be further explained below with reference to Figure 15.

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

[0235] 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.

[0236] 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.

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

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

[0239] 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;

[0240] 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.

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

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

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

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

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

[0246] 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 first account identifier set.

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

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

[0249] After determining the maximum upload quantity of the various branch contents using the branch content quantity control, the multiple versions of the content are uploaded, wherein the quantity of the various branch contents is less than or equal to the maximum upload quantity.

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

[0251] 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.

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

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

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

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

[0256] 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.

[0257] 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.

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

[0259] Display the aforementioned multiple versions of content;

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

[0261] 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.

[0262] 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:

[0263] 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.

[0264] 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;

[0265] 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.

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

[0267] 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;

[0268] 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.

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

[0270] In response to obtaining a selection operation for the multi-version content, multiple production ranges for the multi-version content are displayed;

[0271] 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.

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

[0273] Obtain the account identifier that uploaded the target branch content, and a first set of account identifiers that correspond to the multi-version content;

[0274] If the first set of account identifiers includes account identifiers that are the same as the account identifiers that uploaded the target branch content, then the account identifiers that uploaded the target branch content have the authority to upload branch content for the multi-version content;

[0275] The uploading unit 1701 is specifically used for:

[0276] In response to obtaining a selection operation for the multiple versions of content, and the account identifier that uploaded the target branch content has the permission to upload branch content for the multiple versions of content, the target branch content is uploaded.

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

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

[0279] 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.

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

[0281] 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.

[0282] 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.

[0283] 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.

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

[0285] Displays a button to increase popularity;

[0286] 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.

[0287] 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;

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

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

[0290] 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 the perspective of hardware implementation. Figure 18 shows a schematic diagram of the server structure, and Figure 19 shows a schematic diagram of the terminal device structure.

[0291] Referring to Figure 18, which 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. It 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 including 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.

[0292] 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™, Mac OS X™, Unix™, Linux™, FreeBSD™, etc.

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

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

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

[0296] 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;

[0297] 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.

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

[0299] 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.

[0300] 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.

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

[0302] Referring to Figure 19, this figure is a schematic diagram of the structure of a terminal device provided in an embodiment of this application. Taking a smartphone as an example, Figure 19 shows a block diagram of part of the structure 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, etc. Those skilled in the art will understand that the smartphone structure shown in Figure 19 does not constitute a limitation on the smartphone, and may include more or fewer components than shown, or combine certain components, or have different component arrangements.

[0303] The following section, with reference to Figure 19, provides a detailed introduction to the various components of a smartphone:

[0304] 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.

[0305] 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.

[0306] 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.

[0307] 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.

[0308] 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.

[0309] 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.

[0310] 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.

[0311] 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.

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

[0313] 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.

[0314] 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.

[0315] 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.

[0316] 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.

[0317] 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.

[0318] 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.

[0319] 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.

[0320] 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.

[0321] 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, the method being executed by a computer device, the method comprising: In response to receiving the content to be uploaded, a control panel created by multiple users is displayed; 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; 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.

2. The method according to claim 1, wherein uploading multi-version content in response to obtaining a confirmation operation for the multi-version production range includes: In response to obtaining confirmation for the multiple version production range, a user permission control is displayed; After determining the first set of account identifiers through the user permission control, the multi-version content is uploaded. The account identifiers included in the first set of account identifiers have the permission to upload branch content for the multi-version content, and the multi-version content has a corresponding relationship with the first set of account identifiers.

3. The method according to claim 2, further comprising: After determining the first account identifier set through the user permission control, a message sending control is displayed; 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 first account identifier set.

4. The method according to any one of claims 1-3, wherein uploading multi-version content in response to obtaining a confirmation operation for the multi-version production range includes: In response to obtaining confirmation for the multi-version production range, a branch content quantity control is displayed; After determining the maximum upload quantity of the various branch contents using the branch content quantity control, the multiple versions of the content are uploaded, wherein the quantity of the various branch contents is less than or equal to the maximum upload quantity.

5. The method according to any one of claims 1-4, wherein uploading multiple versions of content includes: 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.

6. The method according to claim 5, wherein uploading the multi-version content and the metadata of the multi-version content includes: The metadata of the multi-version content is encrypted to obtain the encrypted metadata of the multi-version content; Upload the multi-version content and the encrypted metadata of the multi-version content.

7. A content interaction method, the method being performed by a computer device, the method comprising: 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. 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.

8. The method according to claim 7, further comprising: Display the aforementioned multiple versions of content; When the multi-version content is displayed in the multi-version production area, preview content of various branches is displayed; 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.

9. The method according to claim 8, wherein if the multi-version content is video content, the multi-version content includes a second branch content to be displayed and a third branch content to be displayed, and the second branch content to be displayed and the third branch content to be displayed are different branch contents, then when the multi-version content is displayed to the multi-version production area, displaying preview content of various branch contents 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 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. 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; 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.

10. The method according to claim 9, wherein displaying 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 comprises: 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; 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.

11. The method according to any one of claims 7-10, wherein uploading the target branch content in response to obtaining a selection operation for multiple versions of content includes: In response to obtaining a selection operation for the multi-version content, multiple production ranges for the multi-version content are displayed; 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.

12. The method according to any one of claims 7-11, further comprising: Obtain the account identifier that uploaded the target branch content, and a first set of account identifiers that correspond to the multi-version content; If the first set of account identifiers includes account identifiers that are the same as the account identifiers that uploaded the target branch content, then the account identifiers that uploaded the target branch content have the authority to upload branch content for the multi-version content; The response to obtaining a selection operation for multiple versions of content, uploading the target branch content, includes: In response to obtaining a selection operation for the multiple versions of content, and the account identifier that uploaded the target branch content has the permission to upload branch content for the multiple versions of content, the target branch content is uploaded.

13. The method according to any one of claims 7-12, further comprising: 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.

14. The method according to claim 13, further comprising: 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. 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. 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.

15. The method according to claim 13 or 14, further comprising, after uploading the target branch content: Displays a button to increase popularity; 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.

16. A content interaction device, the device comprising: Display unit, settings unit, and upload unit; The display unit is used to display a multi-person creation control in response to obtaining the content to be uploaded; 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; 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.

17. A content interaction device, the device comprising: Upload unit and confirm unit; 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. 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.

18. A content interaction system, the system comprising: First equipment and second equipment; The first device is configured to perform the method according to any one of claims 1-6; The second device is used to perform the method described in any one of claims 7-15.

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

20. A computer program product comprising a computer program, which, when run on a computer device, causes the computer device to perform the method of any one of claims 1-6, or to perform the method of any one of claims 7-15.

21. A computer-readable storage medium for storing a computer program for performing the method of any one of claims 1-6, or performing the method of any one of claims 7-15.

Images