Method, apparatus, device and product for interface interaction

Abstract

An interface interaction method, apparatus, device and product are provided. The method proposed herein includes: presenting a content item, the content item being related to a live broadcast shared by a first user; receiving a first operation from a second user, the first operation including a trigger operation on the content item; and in response to the first operation, presenting a first interface, the first interface displaying first information, the first information being related to a first invitation, the first invitation being used to invite the second user to participate in a live interaction related to the live broadcast. In this way, the efficiency of users obtaining information can be improved.

Description

Technical Field

[0001] The examples in this article generally relate to the field of computer science, and in particular to methods, apparatuses, devices, and products for user interface interaction. Background Technology

[0002] With the development of computer technology, more and more applications are able to provide users with live streaming content. Various types of live streams can provide people with content covering information, education, lifestyle, and entertainment. Furthermore, these applications can also provide users with a variety of interactive activities during the live event. Summary of the Invention

[0003] In a first aspect, a method for interface interaction is provided. The method includes: presenting a content item related to a live stream shared by a first user; receiving a first operation from a second user, the first operation including a triggering operation on the content item; and responding to the first operation, presenting a first interface displaying first information related to a first invitation, the first invitation being used to invite the second user to participate in live stream-related interactions.

[0004] In a second aspect, a method for interface interaction is provided. The method includes: presenting a second interface displaying a live stream; receiving a second request for sharing the live stream; and on a third interface, presenting a content item, the content item including a first element, the first element including descriptive information of a first invitation, the first invitation being used to invite at least one user to participate in live stream interaction, the live stream interaction being related to the live stream.

[0005] In a third aspect, an apparatus for interface interaction is provided. The apparatus includes: a first presentation module configured to present content items related to a live stream shared by a first user; a first receiving module configured to receive a first operation from a second user, the first operation including a triggering operation on the content items; and a second presentation module configured to, in response to the first operation, present a first interface displaying first information related to a first invitation, the first invitation being used to invite the second user to participate in live stream-related interactions.

[0006] In a fourth aspect, an apparatus for interface interaction is provided. The apparatus includes: a third presentation module configured to present a second interface displaying a live stream; a second receiving module configured to receive a second request for sharing the live stream; and a fourth presentation module configured to present content items on the third interface, the content items including a first element, the first element including descriptive information of a first invitation, the first invitation being used to invite at least one user to participate in live stream interaction, the live stream interaction being related to the live stream.

[0007] In a fifth aspect, an electronic device is provided. The device includes at least one processor; and at least one memory coupled to the at least one processor and storing instructions for execution by the at least one processor. When executed by the at least one processor, the instructions cause the device to perform the methods of the first or second aspect.

[0008] In a sixth aspect, a computer program product is provided, which is tangibly stored in a computer storage medium and includes computer-executable instructions that, when executed by a device, cause the device to perform the method of the first or second aspect.

[0009] In this way, the sharing platform for live streams can be reused as an entry point for participating in live stream interactions and can provide feedback related to second users' participation in the live stream, thereby improving the efficiency of information acquisition. This reduces the page switching and communication rounds caused by separate sharing and invitation processing.

[0010] It should be understood that the content described in this section is not intended to limit the key or important features of the examples in this article, nor is it intended to restrict the scope of the solution. Other features will become readily apparent from the following description. Attached Figure Description

[0011] The above and other features, advantages, and aspects of the various examples herein will become more apparent when taken in conjunction with the accompanying drawings and the following detailed description. In the accompanying drawings, the same or similar reference numerals denote the same or similar elements, wherein: Figure 1 A schematic diagram of the example environment is shown; Figures 2A to 2F Example interfaces for some scenarios are shown; Figures 3A to 3E Example interfaces for some scenarios are shown; Figures 4A to 4C Example interfaces for some scenarios are shown; Figure 5 The flowcharts show example processes of interface interactions in some scenarios; Figure 6 The flowcharts show example processes of interface interactions in some scenarios; Figure 7 Schematic structural block diagrams of example devices for interface interaction in some scenarios are shown; Figure 8 Schematic block diagrams of example devices for interface interaction in some scenarios are shown; and Figure 9 A block diagram of an electronic device capable of implementing multiple illustrative scenarios is shown. Detailed Implementation

[0012] The examples in this document will now be described in more detail with reference to the accompanying drawings. While some examples are shown in the drawings, it should be understood that solutions can be implemented in various forms and should not be construed as limited to the examples presented herein. Rather, these examples are provided to provide a more thorough and complete understanding of the solutions. It should be understood that the drawings and examples in this document are for illustrative purposes only and are not intended to limit the scope of protection of the solutions.

[0013] It should be noted that the headings of any section / subsection provided herein are not restrictive. Various examples are described throughout this document, and examples of any type may be included under any section / subsection. Furthermore, examples described in any section / subsection may be combined in any way with any other examples described in the same section / subsection and / or different sections / subsections.

[0014] In the description of the examples in this document, the term "including" and similar terms should be understood as open inclusion, i.e., "including but not limited to". The term "based on" should be understood as "at least partially based on". The term "an example" or "the example" should be understood as "at least one example". The term "some examples" should be understood as "at least some examples". Other explicit and implicit definitions may also be included below. The terms "first", "second", etc., may refer to different or the same objects. Other explicit and implicit definitions may also be included below.

[0015] The examples in this document may involve user data, data acquisition, and / or use. All of these aspects comply with relevant laws, regulations, and rules. In the examples, all data collection, acquisition, processing, manipulation, forwarding, and use are conducted with the user's knowledge and confirmation. Accordingly, when implementing each example, the type, scope of use, and usage scenarios of any data or information that may be involved should be communicated to the user and their authorization obtained through appropriate means, in accordance with relevant laws and regulations. The specific methods of notification and / or authorization can vary depending on the actual situation and application scenario; the scope of the solution is not limited in this regard.

[0016] In this manual and the sample solutions, any processing of personal information will be conducted only on a legal basis (such as with the consent of the data subject or as necessary for the performance of a contract) and will only be carried out within the scope stipulated or agreed upon. A user's refusal to process personal information beyond what is necessary for basic functions will not affect the user's use of basic functions.

[0017] As used in this document, "live streaming" refers to a content delivery method in which media data is collected or provided by one or more electronic devices and transmitted in real time or near real time to one or more other devices via a communication network for users to watch or listen to simultaneously. Live streaming can include video live streaming, audio live streaming, multimedia live streaming, or live streaming based on the synthesis of multiple media streams.

[0018] As used in this article, "live interaction" refers to an activity in which at least two parties—the host, guests, or viewers—interact in real-time or near real-time via audio, video, text, or user commands during a live stream. Live interaction can include voice chat, video chat, live battles, messaging, virtual item interaction, or other forms of interaction associated with live streaming.

[0019] The term "first information" as used in this document refers to information presented on the first interface in response to a second user's triggering action on a content item, which is associated with the first invitation and used to guide the second user to participate in the live stream interaction. The first information may include text, images, icons, status prompts, interactive components, or a combination thereof, and its specific content or type can be determined based on the location of the triggering action, the first user's role and permissions, and the current state of the live stream interaction.

[0020] The term "first invitation" as used in this document refers to an invitation associated with a live stream shared by a first user, used to guide a second user to participate in the live stream interaction associated with that live stream. A first invitation can be a participation invitation issued by a user with direct invitation privileges, or a participation recommendation issued by a user without direct invitation privileges. A first invitation can be represented by text, images, icons, interactive components, or a combination thereof, and can guide a second user to directly join the live stream interaction, or send a participation request to a user associated with the live stream and possessing the corresponding privileges.

[0021] The term "participant" as used in this document refers to a user who participates in live streaming interaction. Participants may provide audio, video, text, operation commands, or other interactive information to the live streaming interaction. In a scenario where the host and viewers connect live, participants may include the host and the viewers who are connecting; in a scenario where hosts connect live, participants may include multiple hosts. Different participants may have the same or different roles and operating permissions.

[0022] The term "live streamer" as used in this article refers to a user who initiates, creates, hosts, or provides live stream content. A live streamer may include one or more broadcasters and may have permissions to manage the live stream or live stream interactions, such as initiating or ending live stream interactions, inviting other users to participate in live stream interactions, confirming participation requests, configuring participant permissions, or adjusting the presentation layout of the live stream content.

[0023] As used in this document, the term "guest" refers to a user who participates in live stream interaction after being invited, confirmed, or authorized by the live stream provider. Guest users may provide audio, video, text, or other interactive information during the live stream interaction and may be granted certain interactive permissions. The permissions granted to guest users may differ from those of the live stream provider; for example, a guest user's invitation to participate or a sharing request may only take effect after being confirmed by the live stream provider.

[0024] The term "viewer" as used in this article refers to a user who receives or watches live stream content. Viewers can interact with the live streamer or other users through text messages, virtual items, commands, or other means, and can also participate in live stream interactions by responding to invitations or making requests. When viewers participate in live stream interactions, they can act as participants in the live stream interaction, providing audio, video, or other media content.

[0025] As used in this document, "live content" refers to media data transmitted to one or more electronic devices during a live broadcast. Live content may include single media streams, multiple media streams, or layout data composed of multiple media streams.

[0026] As used in this article, the term "content item" refers to a carrier of information that can be presented and processed as a whole within the interface. Content items can be conversation messages, media cards, content stream items, or page objects accessible via links.

[0027] As used in this document, "media content" refers to data presented visually or aurally. Media content may include configuration images, live preview images, dynamic previews, or other media data associated with a live stream.

[0028] As used in this article, the term "element" refers to a visual object in an interface that can present information, receive actions, or indicate status. An element can be text, graphics, icons, or a combination thereof.

[0029] As used in this article, the term "interface" refers to the visual interactive medium presented by an electronic device through an output device. An interface can occupy the entire display area or be overlaid on another interface.

[0030] As used in this article, the term "action" refers to user input that an electronic device can receive and convert into an input event. Actions can be clicks, touches, swipes, long presses, or other forms of input.

[0031] As used in this article, the term "component" refers to a functional area within an interface that collaboratively presents a set of information and controls. A component can be a panel, a pop-up, a card, or an area within a page.

[0032] As used in this article, the term "control" refers to a UI element that can respond to input events and trigger processing actions. Controls can have an available state, a selected state, a disabled state, or other interactive states.

[0033] The term "interaction mode" as used in this article refers to the media access method used when users participate in live interactive sessions. Interaction mode can indicate whether audio or video is enabled, media sources are switched, or only one media type is provided.

[0034] The term "role information" as used in this article refers to data that characterizes a user's functional permissions during live streaming interactions. Role information can be represented by a role identifier, a set of permissions, or an operational capability field returned by the server.

[0035] As used in this document, the term "session interface" refers to an interface used to present messages between two or more communication participants. A session interface can correspond to a one-person session or a multi-person session.

[0036] As used in this article, the term "media content viewing interface" refers to the interface used to present media content published or shared by users. This interface can present multiple pieces of media content in the order of the content stream.

[0037] The term "interaction status" as used in this article refers to the state of a user's ability to participate in a content item at a specific moment. Interaction status can be determined based on a valid time period, available location, number of triggers, or permission status.

[0038] The term "disabled state" as used in this article refers to a state in which a content item no longer provides its original participating path. A disabled state can be expressed by stopping the rendering of the participating element or by switching the participating element to a disabled state.

[0039] As used in this document, the term "request" refers to structured control data transmitted between electronic devices or between an electronic device and a server. A request may carry a live stream identifier, content item identifier, role information, target information, and status parameters.

[0040] Live streaming sharing and live streaming interaction can have separate processing paths. After a user triggers a sharing action to share a live stream, they may need to re-enter the interaction portal and complete the participation configuration. The recipient may also need to open the shared content first and then locate the participation portal. If the shared content item lacks role permissions and live stream status information, the electronic device may display an operation that is currently unexecutable. This situation will generate an invalid request and increase the number of interaction rounds between the terminal and the server. Therefore, a participation invitation configuration can be included in the sharing request. The server can then generate a content item with the corresponding participation portal based on this. The electronic device then presents the corresponding content according to the triggering area, role permissions, and interaction status.

[0041] A user interface interaction scheme is proposed. According to the scheme, content items are presented, which are related to the live stream shared by a first user; a first operation is received from a second user, which includes a trigger operation on the content item; and in response to the first operation, a first interface is presented, which displays first information related to a first invitation, which is used to invite the second user to participate in live stream-related interactions.

[0042] In this way, the sharing platform for live streams can be reused as an entry point for participating in live stream interactions and can provide feedback related to second users' participation in the live stream, thereby improving the efficiency of information acquisition. This reduces the page switching and communication rounds caused by separate sharing and invitation processing.

[0043] Another interface interaction scheme is also proposed. According to this scheme, a second interface is presented, which displays the live stream; a second request is received, which is used to share the live stream; and on the third interface, content items are presented, which include a first element, which includes descriptive information of a first invitation, which is used to guide at least one user to participate in the live stream interaction, and the live stream interaction is related to the live stream.

[0044] In this way, the first user can simultaneously configure participation invitations when sharing a live stream, reducing the need for repeatedly selecting target objects and sending messages. Electronic device 110 can transmit sharing information and invitation information together. Server 130 can thus reduce the number of control requests and status writes.

[0045] The following describes various examples of this scheme in further detail with reference to the accompanying drawings.

[0046] Example Environment Figure 1 A schematic diagram of example environment 100 is shown. (e.g.) Figure 1 As shown, example environment 100 may include electronic device 110.

[0047] In this example environment 100, electronic device 110 can run an application 120 that supports user interface interaction. Application 120 can be any suitable type of application for user interface interaction, including but not limited to: live streaming applications, social applications, news feed viewing applications, or other suitable applications. User 140 can interact with application 120 via electronic device 110 and / or its attached devices.

[0048] exist Figure 1 In environment 100, if application 120 is active, electronic device 110 can use application 120 to present interface 150 for supporting interface interaction.

[0049] In some cases, electronic device 110 communicates with server 130 to provide services to application 120. Electronic device 110 can be any type of mobile terminal, fixed terminal, or portable terminal, including mobile phones, desktop computers, laptop computers, notebook computers, netbook computers, tablet computers, media computers, multimedia tablets, handheld computers, portable gaming terminals, virtual reality (VR) / augmented reality (AR) devices, personal communication system (PCS) devices, personal navigation devices, personal digital assistants (PDAs), audio / video players, digital cameras / camcorders, positioning devices, television receivers, radio receivers, e-book devices, gaming devices, or any combination of the foregoing, including accessories and peripherals of these devices or any combination thereof. In some cases, electronic device 110 can also support any type of user-facing interface (such as "wearable" circuitry).

[0050] Server 130 can be a single physical server, a server cluster or distributed system composed of multiple physical servers, or a cloud server providing cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, content delivery networks, and basic cloud computing services. Server 130 may include, for example, computing systems / servers such as mainframes, edge computing nodes, computing devices in a cloud environment, etc. Server 130 can provide backend services for applications 120 that support user interface interaction in electronic devices 110.

[0051] A communication connection can be established between server 130 and electronic device 110. This communication connection can be established via wired or wireless means. The communication connection can include, but is not limited to, Bluetooth, mobile network, Universal Serial Bus (USB), and Wireless Fidelity (WiFi) connections. In some cases, server 130 and electronic device 110 can exchange signaling information through their communication connection.

[0052] It should be understood that the structure and function of the various elements in environment 100 are described for illustrative purposes only and do not imply any limitation on the scope of the scheme.

[0053] The following description of the example will continue with reference to the accompanying drawings.

[0054] Example Interaction Figure 2A The sharing-side live streaming interface 200A is shown according to some scenarios. Figure 2B and Figure 2C This shows the different states of the sharing configuration when entering from the live broadcast interface 200A. Figures 2D to 2F This shows a third interface that can hold content items after a share request is generated.

[0055] In some cases, electronic device 110 displays a second interface that shows the live stream. The live stream is linked to live interaction, which supports multiple participants. For example, such as... Figure 2A As shown, the electronic device 110 can display a second interface (e.g., interface 200A). Interface 200A displays the live stream, meaning it can display live stream content. This live stream content can include one or more of the following: audio content, video content, text content, image content, and graphic content. The live stream displayed in interface 200A can be associated with live stream interactions, such as multi-party interactive sessions or collaborative live streams.

[0056] In some cases, the second interface comprises multiple areas, each configured to display information from multiple participants. For example, such as... Figure 2A As shown, the electronic device 110 presents a live content area 202 and a second element on the interface 200A. The second element may include, for example, a sharing entry 204. The live content area 202 may include multiple regions. For example, the live content area 202 may adopt a multi-grid layout, presenting multiple pieces of second information from multiple participants in different regions. These multiple pieces of second information may include live content corresponding to multiple participants (e.g., media streams associated with multiple participants), identification information, etc.

[0057] The first user can correspond to different identities, which are associated with the live stream displayed on interface 200A. For example, the first user can be the live streamer, a guest, etc. In response to the first user triggering the sharing entry 204, electronic device 110 can create a sharing panel invocation event and overlay it on interface 200A as follows: Figure 2B Component 206 is shown.

[0058] Alternatively, the electronic device 110 can display an operation list in response to a long press operation on the live content area 202. After receiving an operation on the share entry in the operation list, the electronic device 110 can display component 206.

[0059] In this way, the first user can directly access the sharing configuration from the live broadcast interface, reducing the need for page jumps to locate the sharing function. Electronic device 110 only loads the sharing panel resources after receiving the sharing trigger event, thereby reducing the number of nodes and memory usage during the initial rendering of interface 200A.

[0060] In some cases, electronic device 110 receives a second request. This second request is for sharing the live stream. For example, such as... Figure 2B As shown. Figure 2B An interface 200B is shown with component 206 in an object selection state. Electronic device 110 presents at least one object identifier in component 206. The at least one object identifier may include object identifiers 208-1 and 208-2. The at least one object identifier includes a first object identifier, for example, the first object identifier may be object identifier 208-1. The at least one object identifier may correspond to different objects, such as users, groups, etc.

[0061] In some scenarios, electronic device 110 may also present sharing channel selection controls 210-1 and 210-2 and publishing control 211 in component 206. Sharing channel selection controls 210-1 and 210-2 are used to select the application carrying the content item. Publishing control 211 is used to trigger the formation of media content accessible to multiple second users. Electronic device 110 can receive a fourth operation. The fourth operation may include a trigger operation on a first object identifier (e.g., object identifier 208-1), which is used to select the object to be shared. In response to the trigger on object identifier 208-1, electronic device 110 may present, as shown below... Figure 2C The sharing component 207 shown is used to share a live stream to at least one user. For example, the sharing component 207 can be used to send content items to at least one user. The sharing component 207 includes a fourth control 214.

[0062] By selecting objects before loading invitation configurations, electronic device 110 does not need to calculate the permission status of each object when no object is selected. This reduces aimless permission queries and control rendering, and lowers the load on server 130 for handling invalid queries.

[0063] Figure 2C An interface 200C presenting the sharing component 207 is shown. The electronic device 110 displays the selected object identifier 208-1, input control 212, fourth control 214, and send control 216. The electronic device 110 can receive a second request via the sharing component 207. This second request, also referred to as a sharing request, can originate from the first user. For example, when user 140 clicks the send control 216, the electronic device 110 can use the event of clicking the send control 216 as a second request to share the live stream.

[0064] In some cases, the electronic device 110 can present input controls, and input content can be obtained through these controls. The third interface also displays the input content. For example, such as... Figure 2C As shown, the input control 212 can be used to obtain input content. The input content can be additional text associated with this sharing, also known as a postscript. When the input content is obtained, the electronic device 110 can simultaneously display the currently input content on the interface 200C. After the electronic device 110 receives the input content and shares the live stream, the terminal device associated with the shared object can provide input content for the shared object.

[0065] In some cases, electronic device 110 may present a fourth control. This fourth control is used to configure whether to invite at least one user to participate in the live interaction. Furthermore, electronic device 110 may receive a second request in response to a triggering action of the fourth control. For example, such as... Figure 2C As shown, the fourth control 214 is used to configure whether to invite the selected user to participate in the live broadcast interaction. The fourth control 214 can be in an unselected state by default. When the electronic device 110 receives a trigger operation on the fourth control, it can switch the fourth control to the selected state. In response to the fourth control 214 being switched to the selected state, the electronic device 110 generates a second request after receiving a trigger operation on the sending control 216 to invite the selected user to participate in the live broadcast interaction (e.g., participate in a live chat).

[0066] In some cases, electronic device 110 can save the selection state of the fourth control 214 according to the first user's current role. When the first user opens the sharing component 207 again with the same role, electronic device 110 reads the state corresponding to that role. When the first user opens the sharing component 207 with a different role, electronic device 110 can use the default state.

[0067] If the fourth control 214 is not selected, the server 130 can generate a regular shareable content item that does not include a participation entry. If the fourth control 214 is selected, the server 130 can further determine the target object's communication status and participation permissions.

[0068] If the communication status of the target object does not meet the sending conditions, the server 130 returns a sending failure status to the electronic device 110. The electronic device 110 continues to display the sharing component 207 and displays a failure message.

[0069] If the target user can receive the shared content but does not have the permission to participate, server 130 sends a regular live stream content item to the receiving side. Upon triggering this content item, the receiving side enters the viewing path. The sending side can still display feedback indicating that an invitation configuration has been generated, allowing the first user to recognize their previous selection.

[0070] If the target object is able to receive the shared content and has the permission to participate, the server 130 sends the invitation content item status to both the sending and receiving sides. The electronic device 110 then presents the content item with the participation entry based on this status.

[0071] In the implementation where the first user is a guest user, electronic device 110 can first send a third request to a third user associated with the live stream. Server 130 only sends the content items to the third interface after the third request's confirmation status indicates that sharing is allowed. This third user can, for example, be a live stream user, i.e., the live streamer.

[0072] Alternatively, guest users can first share content items with recommended information. After a second user triggers this content item, they can then send a participation request to the live streamer or administrator. This path will... Figures 4A to 4C Further details are provided below.

[0073] By combining the sharing parameters, invitation configuration, and validity parameters into a second request, the first user does not need to perform sharing and invitation operations separately. Electronic device 110 reduces the number of panel switching and input operations. Server 130 can complete target validation and content item generation in a single request processing, thereby reducing the number of control messages and database read / write operations.

[0074] Figure 2D An example of a content item presented in a first style in the session interface 200D is shown. Content item 218 includes first media content and a first element (e.g., element 220). The first element (e.g., element 220) includes descriptive information for a first invitation used to guide at least one user to participate in a live interaction associated with the live stream. For example, the first element (e.g., element 220) may include the text description "Join Live Stream". "Join Live Stream" could indicate that a user viewing the content item can join the live stream interaction (e.g., join a live stream).

[0075] In some scenarios, the session interface 200D can display a first session, whose participants may include a first user and multiple users. The electronic device 110 can present a first message and a second message separately in the session interface 200D. The first message includes content items, and the second message includes input content obtained through the input control 212. As an example, when the electronic device 110 obtains input content through the input control, the electronic device 110 can use different messages to carry the content item 218 and the input content.

[0076] The first and second messages can have different message identifiers. Server 130 can update the interaction state of content items individually without changing the input content. This reduces the duplication of message sending and rendering across the entire session.

[0077] Content item 218 may include first media content. The first media content may include a first image. The first image may be preset content configured for the live stream, such as a live stream cover image, the streamer's avatar, or other images configured by the streamer.

[0078] Alternatively, the primary media content may also include a second image. The second image includes a preview of the live stream and can be arranged in a grid layout depending on the number of participants. Server 130 can distribute low-bitrate preview streams or periodic preview frames.

[0079] If a live preview is unavailable, the electronic device 110 can fall back to displaying the configuration image. The electronic device 110 can also cache the configuration image and replace it after the preview stream is established. This progressive loading method can shorten the initial display time of content items.

[0080] In some cases, content items can be sent to a session involving a first user and one or more other users. That is, content items can be sent to a one-on-one chat session or a group chat session that includes the first user. Content items can also be accessed by corresponding objects that do not have a pre-established session relationship. Server 130 can collapse the content item according to message reception rules and notify the target terminal via status notification. If the object to be shared with is already in the live stream, electronic device 110 can directly present a participation confirmation component on the current live stream interface. Electronic device 110 does not need to reload the live media stream, thus reducing the number of media channel reconstructions.

[0081] Figure 2E An example of a content item presented in a second style in the session interface 200E is shown. In some cases, in response to a condition being met regarding the interactive state of a content item, electronic device 110 switches a first element (e.g., element 220) from an available state to an invalid state. The interactive state can be determined by server 130 based on the content item's state record. If the presentation duration of the content item reaches a certain threshold, server 130 updates the state record to invalid. Server 130 then sends a state update to the electronic device accessing the content item.

[0082] The interaction status can also be determined based on the number of times a content item is triggered. If the number of triggers reaches a certain threshold, server 130 will reject new participation tokens and return an invalidation status.

[0083] Interaction status can also be determined based on available interaction positions (such as microphone slots in a live chat). If occupied and reserved positions reach capacity limits, server 130 can invalidate content items. This process applies to configurations that do not allow entry into the waiting queue.

[0084] In some scenarios, when the interaction state of a content item meets certain conditions, the electronic device 110 can also stop displaying the first element (e.g., element 220) in the content item. Alternatively, the electronic device 110 can retain the first element (e.g., element 220) and indicate that the first element (e.g., element 220) is disabled using a third style. For example, the first element (e.g., element 220) can be changed from "Join Voice Chat" to "Voice Chat Participants Full". Another example is changing the first element (e.g., element 220) from a first color to a second color.

[0085] Server 130 can perform joint verification of the content item identifier and the operation request identifier. Duplicate operation requests can return the same status without repeatedly increasing the trigger count. This idempotent processing can prevent content items from becoming invalid prematurely due to network retransmissions.

[0086] For content items that allow access from multiple users, server 130 can atomically update the remaining trigger count. Only requests that successfully participate in live interaction reduce the remaining count. This reduces quota over-allocation and state inconsistencies caused by concurrent operations.

[0087] After a content item becomes available but before participation is confirmed, the interaction slot may be occupied by other requests. Server 130 can recheck capacity during the confirmation phase. If capacity is exhausted but queuing is allowed, server 130 adds the second user to the waiting queue.

[0088] By synchronously displaying the invalidation status in the content items, users can know the current capabilities before initiating participation. Electronic device 110 can thus reduce the loading of invalid components and redundant operations. Server 130 can also reduce permission queries and participation request processing for invalid content items.

[0089] Figure 2F A media content viewing interface 200F, serving as a third interface, is shown. In some cases, when the publishing control 211 is triggered, the electronic device 110 can publish second media content including content items. Further, the electronic device 110 can present second media content 221 published by the first user in interface 200F. The second media content 221 includes content items and a first element (e.g., element 222).

[0090] The media content viewing interface 200F can display a content stream. The content stream also includes third media content. In response to receiving a fifth operation on the interface 200F, the electronic device 110 stops displaying content items and displays the third media content on the interface 200F. The fifth operation can be a swipe operation along a predetermined direction. After receiving the fifth operation, the electronic device 110 can stop displaying content items and display the third media content on the interface 200F.

[0091] In some cases, the second media content can be media content with a separate viewing interface. The first element (e.g., element 222) can be overlaid on the second media content and carry parameters for returning to the live stream and requesting participation in live stream interaction.

[0092] Alternatively, content items can be transmitted via an external communication channel. The target electronic device launches application 120 according to the link parameters and requests the content item status from server 130. Server 130 returns an available participation entry only if the status is valid.

[0093] By reusing the same content item in both the session interface and the media content viewing interface, server 130 can employ unified status recording and permission verification. Different terminals only need to select the rendering template based on the interface they are hosting, thereby reducing the overhead of multi-channel status maintenance.

[0094] Figure 3A A receiving-side session interface 300A is shown. In some cases, the electronic device 110 presents content item 302 in interface 300A. Content item 302 is associated with a live stream shared by a first user. That is, content item 302 can be constructed after the first user shares the live stream. This live stream is associated with live stream interaction. Live stream interaction supports multiple participants, and the electronic device 110 can provide users with live stream content from multiple participants. Here, live stream interaction can include, for example, multi-person interactive sessions, collaborative live streams, etc.

[0095] Content item 302 includes a second region 304, a first element (e.g., element 306), and a first region 308. The first element (e.g., element 306) may be presented in the first region 308. The first element (e.g., element 306) includes descriptive information for a first invitation. This descriptive information may, for example, include text content such as "A first user invites you to join a live chat." Electronic device 110 can receive a first operation associated with content item 302 from a second user. The first operation includes a triggering operation on content item 302. For example, the first operation may trigger either the first region 308 or the second region 304 of content item 302. Electronic device 110 encodes the trigger location as a region identifier in an input event.

[0096] Electronic device 110 sends a status request carrying a content item identifier and a region identifier to server 130. Server 130 returns the live broadcast status, the role information of the first user, and the participation permissions of the second user. Electronic device 110 determines the type of interactive component to be presented based on the triggering location of the first operation (e.g., triggering the first region 308 or triggering the second region 304). The interactive component here may include subsequent... Figure 3B The second component and presented in Figure 3C The first component in.

[0097] In some scenarios, in response to the first operation, the electronic device 110 presents a first interface. The first interface may display first information related to the first invitation. The first invitation is used to invite a second user to participate in the live stream interaction. For example, the first information may include text content such as "Inviting you to participate in the live stream interaction," indicating an invitation to the second user to participate in the live stream interaction. The second user here may, for example, be a viewer, i.e., the audience. In some scenarios, the first information may include interactive components, i.e., including… Figure 3B The second component in Figure 3C The first component or Figure 3E The waiting queue component allows different hot zones to reuse the same content item but trigger different processing branches. This reduces the space occupied by setting multiple individual cards in the session interface. Electronic device 110 can also directly load target components based on area identifiers, thereby reducing the rendering of intermediate pages and server status requests.

[0098] Figure 3B A first interface 300B is shown after the first operation triggers the second area 304. The electronic device 110 first enters the live streaming viewing state, and then presents a second component (e.g., component 310) on the interface 300B. The second component (e.g., component 310) includes a first identifier (e.g., identifier 312), a second control (e.g., control 314), and a first control (e.g., control 316). The first identifier (e.g., identifier 312) corresponds to the first user, and may include, for example, the first user's avatar, virtual object, etc. The first control (e.g., control 316) is used to accept a first invitation to join the live streaming interaction. The second control (e.g., control 314) is used to reject the first invitation. In response to the second user triggering the second control (e.g., control 314), the electronic device 110 closes the second component (e.g., component 310) and maintains the live streaming viewing state.

[0099] In some cases, the type of the first information is associated with the role information of the first user. Role information represents the first user's permissions in the live interaction. When the first user has direct invitation permissions (e.g., the first user is a live streamer), the electronic device 110 can present a second component (e.g., component 310) including a first control for accepting the first invitation. The situation where the first user does not have direct invitation permissions (e.g., the first user is a guest or audience member) will be described below. In some cases, when the first control (e.g., control 316) is triggered, the electronic device 110 can present... Figure 3C The first component shown (e.g., component 318) By overlaying a second component (such as component 310) onto the live streaming interface, users can process invitations while watching the live content. Electronic device 110 does not need to load a separate invitation page first, thus reducing the number of page renderings and avoiding the need for duplicate establishment of live media channels.

[0100] Figure 3C A first interface 300C is shown after the first operation triggers the first area 308. The electronic device 110 presents a first component (e.g., component 318) on the interface 300C. First information includes the first component (e.g., component 318). The first component (e.g., component 318) includes a mode preview area 320, a fifth control 320-1, and a join control 322. A second user can configure an interaction mode via the fifth control 320-1. The interaction mode represents how the second user participates in the live interaction. The interaction mode can indicate whether to enable audio only, enable both audio and video, or switch media input sources. The electronic device 110 can preview the current media access status in the mode preview area 320.

[0101] By configuring the interactive mode before actual integration, electronic device 110 can establish only the acquisition and encoding links corresponding to the selected media type. Unselected video links do not need to be initialized, thereby reducing processor usage, power consumption, and uplink bandwidth usage.

[0102] In some cases, electronic device 110 may, in response to receiving a second operation on the first component, present a first prompt on the first interface. The first prompt indicates that the second user is a participant in the live interactive session. As an example, such as... Figure 3C As shown, electronic device 110 can receive the second operation via join control 322. In response to the second user triggering join control 322, electronic device 110 sends a participation confirmation request to server 130. The participation confirmation request carries the interaction mode and the previously obtained participation token. Server 130 verifies the participation token and the current capacity. If an available interaction location exists, server 130 updates the second user's status to "joined" and distributes new layout data to multiple participating terminals. Further, after the second user joins the live interaction, electronic device 110 can present a first prompt. The first prompt can be any appropriate prompt indicating that the second user has joined the live interaction, such as a text prompt saying "You have joined the live stream".

[0103] In some scenarios, when the first control (e.g., control 316) is triggered, the electronic device 110 can directly present the interface 300C and present the first component (e.g., component 318) in the interface 300C so that the user can directly join the live interaction. Figure 3DThe first interface 300D after the second user joins the live interaction is shown. After the server 130 returns a successful joining status, the electronic device 110 presents content 324 and a participation status message 326 based on the updated layout data. Content 324 indicates that the second user has become a participant in the live interaction. Content 324 can be media content provided by the electronic device 110, or it can be a placeholder graphic used during the establishment of the media channel. The participation status message 326 can have the same participant identifier as content 324. The electronic device 110 can replace the placeholder graphic with the actual media content after receiving the first media data packet. This two-stage presentation method can first provide feedback on the joining status, and then wait for the media channel to complete negotiation. This shortens the user's perceived response time and avoids the interface remaining in a no-feedback state before the first media frame arrives.

[0104] Figure 3E The first interface 300E is shown when there are currently no available interactive locations. After determining that the capacity is full and queuing is allowed during the participation confirmation phase, server 130 adds the second user to the waiting queue.

[0105] In some scenarios, electronic device 110 presents a waiting queue component 328 on interface 300E. The waiting queue component 328 can represent the waiting status of the second user and the number of users ahead in the queue, and provides a cancellation control. Server 130 can maintain the waiting queue according to the request time or other configured order. After an interaction position is released, server 130 sends a joinable status to the head electronic device. Electronic device 110 can then re-present the first component (e.g., component 318) or directly execute the confirmed interaction mode. After the second user triggers the cancellation control, electronic device 110 sends a cancellation flag to server 130. Server 130 removes the corresponding record from the waiting queue and returns a cancellation complete status to electronic device 110. The waiting queue status can prevent the second user from repeatedly submitting participation requests. This reduces the number of terminal operations and lowers the processing load on server 130 for repeated capacity queries and repeated enqueue requests.

[0106] Figure 4A The diagram shows the session interface 400A when the first user is the first role (including guest user or audience user). The first element (e.g., element 404) in the content item (e.g., content item 402) is presented as the entry point for requesting participation. Each time a second user enters the live stream through this content item, the electronic device 110 presents a third component.

[0107] Server 130 can determine that the first user does not have direct invitation privileges based on the first user's role information. Server 130 writes the request type into the content item status. When the first user is determined to be the first role, electronic device 110 presents a third component including a request participation entry, instead of a direct acceptance entry.

[0108] In response to a second user triggering the first element (e.g., element 404), electronic device 110 enters live streaming viewing mode and displays... Figure 4B The third component shown is (e.g., component 406). Role-driven entry types allow the electronic device 110 to express the actual executable capabilities of the third component (e.g., component 406) before user interaction, such as presenting a text description of "Request to Connect" in the first element (e.g., element 404). This reduces accidental activations of invitations without proper permissions. The server 130 also does not need to handle acceptance requests that do not match the role's permissions.

[0109] Figure 4B A third component (e.g., component 406) is shown. The third component (e.g., component 406) includes an identifier 408, a control 410, and a control 412. Control 412 is used to send a first request. Electronic device 110 can receive a third operation through the third component, which may include triggering a third control (e.g., control 412). Electronic device 110 then sends the first request to a third user associated with the live stream. The first request is used to request a second user to participate in the live stream interaction. The first request can be forwarded by server 130 to the electronic device corresponding to the live stream user or the managing user. After the third user processes the first request, server 130 returns a confirmation status to the electronic device corresponding to the second user. When the second user triggers control 410, electronic device 110 closes the third component (e.g., component 406) and remains in viewing mode. This operation does not generate a participation request.

[0110] By converting guest user recommendations into participation requests requiring confirmation, the interface retains the viewing path resulting from sharing, while avoiding bypassing the access control of live interaction. Server 130 can reuse existing participation request queues, thereby reducing the number of new state machines and data tables.

[0111] Figure 4C The first interface 400C is shown after the first request has been sent. The electronic device 110 presents a request waiting component 414 and a request cancellation control 416.

[0112] The request waiting component 414 indicates that a first request has been sent and is awaiting processing. Electronic device 110 can receive confirmation status via a control channel and update the request waiting component 414 accordingly. When a second user triggers the cancel request control 416, electronic device 110 sends a withdrawal request to server 130. Server 130 withdraws the first request before it has been processed and synchronizes the status with associated terminals. In cases where multiple electronic devices use the same account, server 130 can synchronize the latest status with each device based on the content item identifier and request identifier. Later status updates carry a newer version number, which electronic device 110 uses to overwrite older caches.

[0113] By presenting a cancelable waiting state, the second user does not need to repeatedly trigger the request entry. Electronic device 110 can push on-site update components based on the status, reducing the number of polling times. The request queue of server 130 can also avoid duplicate records occupying storage space.

[0114] In some implementations, server 130 maintains live stream status records, content item status records, and participation request records. Live stream status records include the live stream identifier, interaction capacity, and role permissions. Content item status records include the content item identifier, valid time period, remaining trigger count, and current style status.

[0115] The participation request record can include a request identifier, a content item identifier, a requester identifier, a target role, and a processing status. Server 130 uses the content item identifier to establish a correspondence between the three types of records. Electronic device 110 only needs to carry the content item identifier to obtain the currently executable action.

[0116] The generation of content items can be accomplished by electronic device 110 or server 130. Electronic device 110 can extract preview frames from the received live media stream. Server 130 can also generate low-bitrate previews from the synthesized multi-stream media and write the preview address into the content item.

[0117] When generating a preview on the device side, the electronic device 110 can reuse decoded frames, avoiding the server 130 from repeatedly performing image extraction. When generating a preview on the server side, multiple receiving terminals can reuse the same preview resource, thereby reducing the overall amount of data transmitted.

[0118] Invitation status can be sent by server 130 via a persistent connection message. Alternatively, electronic device 110 can request the latest status when a content item enters the visible area. The former method is suitable for timely updates, while the latter method can reduce the energy consumption caused by maintaining background connections.

[0119] Electronic device 110 can cache the sharing settings corresponding to a role locally. Server 130 can also save these settings across devices. Regardless of which side the settings are stored on, the cache key can include the user identifier and the current role identifier to avoid incorrect reuse between different roles.

[0120] The above processing can be performed by electronic device 110 alone, or partial state calculations can be performed by server 130 alone. Alternatively, electronic device 110 and server 130 can perform the processing collaboratively. The execution location can be determined based on network status, media data availability, and state consistency requirements.

[0121] Example process Figure 5A flowchart of a first interface interaction process 500 according to certain scenarios is shown. Process 500 can be implemented at electronic device 110. See below for reference. Figure 5 To describe process 500.

[0122] like Figure 5 As shown, in box 510, electronic device 110 presents content items that are associated with the live stream shared by the first user, and the live stream is associated with live interaction.

[0123] In box 520, electronic device 110 receives a first operation from a second user, the first operation including a trigger operation on a content item.

[0124] In frame 530, electronic device 110 responds to the first operation and presents a first interface. The first interface displays first information, which is related to the first invitation. The first invitation is used to invite a second user to participate in the live interaction.

[0125] In this way, a second user can directly access the viewing or participation path from the shared content item, reducing the need to search and switch between multiple entry points. The electronic device 110 can reuse the status requests of the content item and load only the target component, thereby reducing page rendering overhead and the number of end-to-cloud communication rounds.

[0126] In some cases, electronic device 110 may present first media content and first element in the content item. The first media content is associated with the live broadcast, and the first element includes descriptive information of the first invitation.

[0127] In this way, viewing information and participation entry points can be identified within the same content item. Electronic device 110 is able to reduce the number of rendering nodes and status requests for separate invitation messages.

[0128] In some cases, the first media content may include a first image, which is preset content configured for the live stream. Alternatively, the first media content may include a second image containing a live stream preview.

[0129] In this way, electronic device 110 can select the presentation path based on the availability of preview resources. Cached images can reduce the first-screen wait time, and low-bitrate previews can avoid transmitting the entire live stream.

[0130] In some cases, the electronic device 110 may present interactive components on a first interface, the type of which is related to the triggering location of the first operation, and the first information includes the interactive components.

[0131] In this way, different hot zones can directly access different processing branches, reducing intermediate operations. Electronic device 110 can select components based on zone identifiers, thereby reducing unnecessary page loading and status queries.

[0132] In some cases, electronic device 110, in response to the trigger location being in the first area, presents a first component on the first interface; and electronic device 110, in response to receiving a second operation on the first component, presents a first prompt on the first interface, the first prompt indicating that the second user is a participant in the live interaction.

[0133] In some cases, the electronic device 110, in its first component, presents a fifth control, which is used to configure an interaction mode that represents how a second user participates in the live interaction.

[0134] In this way, a second user can determine the media access method before joining. Electronic device 110 only initializes the selected media link, thereby reducing processor usage and uplink bandwidth usage.

[0135] In some cases, in response to the trigger location being in the second area, the electronic device 110 presents a second component on the first interface. The interactive component includes a second component, which includes a first control and a second control. The first control is used to accept the first invitation, and the second control is used to reject the first invitation.

[0136] In this way, a second user can process invitations while watching the live stream. Electronic device 110 does not need to rebuild the live media channel, thus reducing media connection latency and page rendering overhead.

[0137] In some cases, the electronic device 110 may display a first identifier corresponding to the first user in the second component.

[0138] In this way, the second user can identify the correspondence between the invitation source and the current operation. Electronic device 110 can reuse the role identifier in the content item, reducing additional identity data requests and component refreshes.

[0139] In some cases, the first user corresponds to the first role in the live interaction, and the electronic device 110 presents a third component on the first interface. The type of the third component is related to the first role, and the first information includes the third component.

[0140] In this way, the interface only displays actions that match the current permissions, reducing accidental operations. Server 130 can also reduce the rejection of mismatched requests and duplicate permission queries.

[0141] In some scenarios, the first role designates the first user as a guest user in the live interaction, and the third component includes a third control. The electronic device 110 receives a third operation via the third component, the third operation including triggering the third control; and sends a first request to the third user, the first request being used to request participation in the live interaction, the third user being associated with the live stream.

[0142] In this way, guest users' sharing can be transformed into permission-bound participation requests. Server 130 can reuse the participation request queue, thereby reducing the need for additional control flow and state storage.

[0143] Figure 6 A flowchart of an interaction process 600 according to certain scenarios is shown. Process 600 can be implemented at electronic device 110. See below for reference. Figure 6 To describe process 600.

[0144] like Figure 6 As shown in box 610, electronic device 110 presents a second interface, which displays the live broadcast.

[0145] In box 620, electronic device 110 receives a second request for sharing the live stream.

[0146] In box 630, electronic device 110 presents content items on the third interface. The content items include a first element, which includes descriptive information of a first invitation. The first invitation is used to invite at least one user to participate in live interaction, and the live interaction is associated with the live stream.

[0147] In this way, the first user can simultaneously configure participation invitations when sharing a live stream, reducing the need for repeatedly selecting target objects and sending messages. Electronic device 110 can transmit sharing information and invitation information together. Server 130 can thus reduce the number of control requests and status writes.

[0148] In some cases, the electronic device 110 can present input controls and obtain input content through these controls. The third interface also displays the input content.

[0149] In this way, the input content can be completed in the same panel as the sharing request. The electronic device 110 does not need to switch to a separate editing interface, thereby reducing page loading and input state transitions.

[0150] In some cases, the third interface displays the first session. The electronic device 110 can present a first message and a second message. The first message includes content items, and the second message includes input content.

[0151] In this way, media card status and additional content can be updated individually. Server 130 can reduce overall message group retransmissions, and electronic device 110 can also reduce redrawing of irrelevant areas.

[0152] In some cases, electronic device 110 may present a fourth control for configuring whether to invite at least one user to participate in the live interaction. Based on the triggering operation of the fourth control, electronic device 110 receives a second request.

[0153] In this way, sharing and inviting can be completed in the same sending action. The merged request reduces the number of rounds of interaction between the end and cloud and the number of state writes to the server (130).

[0154] In some scenarios, electronic device 110 presents at least one object identifier, the at least one object identifier including a first object identifier; receives a fourth operation, the fourth operation including a trigger operation on the first object identifier; and presents a sharing component, the sharing component including the fourth control, the sharing component being used to share the live stream with the at least one user associated with the first object identifier.

[0155] In some scenarios, the second request originates from the first user, and the content item supports access by multiple second users. The third interface can be a session interface involving the first user and multiple second users. Alternatively, the third interface can be a viewing interface for second media content published by the first user, which includes content items.

[0156] In this way, the same invitation status can be adapted to multiple interfaces. Server 130 can reuse a unified status record, thereby reducing the overhead of multi-channel status maintenance.

[0157] In some cases, the media content viewing interface displays a content stream, which also includes third-party media content. In response to the fifth operation, electronic device 110 stops displaying content items and displays the third-party media content.

[0158] In this way, users can continuously browse the content stream. Electronic device 110 can stop decoding and rendering of non-visual previews, thereby reducing processor usage and memory spikes.

[0159] In some cases, electronic device 110 presents the content item in a first style. When the interaction state of the content item meets the conditions, electronic device 110 presents the content item in a second style representing a failure state.

[0160] In this way, users can identify whether a content item is available before performing an operation. Electronic device 110 can intercept invalid operations, and server 130 can reduce the handling of invalid requests.

[0161] In some cases, electronic device 110 may stop displaying the first element. Alternatively, electronic device 110 may display the first element in a third style that indicates a disabled state.

[0162] In this way, the interface can hide entry points or retain status feedback as needed based on layout requirements. Electronic device 110 can reduce event handling for interactive nodes and avoid sending invalid requests to server 130.

[0163] In some cases, the conditions corresponding to the interactive state can be configured through a second request.

[0164] In some cases, the condition corresponding to the interactive state may include the presentation duration of the content item reaching a first time. Alternatively, this condition may include the number of times the content item is triggered reaching a first number.

[0165] In this way, content items can automatically stop providing expired or excessive participation entries. Server 130 can intercept requests in advance based on timing fields and atomic counts, thereby reducing concurrent load and state conflicts.

[0166] In some cases, the second request originates from the first user. When the first user is a guest user, the electronic device 110 sends a third request to a third user associated with the live stream. After the confirmation status of the third request indicates permission, the electronic device 110 displays the content item on the third interface.

[0167] In this way, the invitation configuration of guest users can be controlled by permissions before presentation. Server 130 can complete role verification during the content generation stage, reducing subsequent unauthorized requests and rollback processing.

[0168] In some cases, the second interface includes multiple areas, which are configured to display information from multiple participants respectively.

[0169] Example devices and equipment A first interface interaction device 700 for implementing process 500 is also provided. Figure 7 A block diagram of device 700 is shown. Device 700 may be implemented as or included in electronic device 110.

[0170] like Figure 7 As shown, the device 700 includes a first presentation module 710, a first receiving module 720, and a second presentation module 730. The first presentation module 710 is configured to present content items associated with a live stream shared by a first user. The first receiving module 720 is configured to receive a first operation from a second user, the first operation including a trigger operation on the content item. The second presentation module 730 is configured to, in response to the first operation, present a first interface displaying first information related to a first invitation, which is used to invite the second user to participate in live stream interaction.

[0171] In some cases, the first presentation module 710 may also be configured to present first media content associated with the live broadcast in the content item and present a first element including descriptive information of a first invitation.

[0172] In some cases, the first media content may include a first image, which is preset content configured for the live stream. Alternatively, the first media content may include a second image containing a live stream preview.

[0173] In some cases, the second presentation module 730 may also be configured to present an interactive component on the first interface, the type of which is related to the triggering location of the first operation, and the first information includes the interactive component.

[0174] In some cases, the second presentation module 730 may also be configured to present the first component on the first interface in response to the trigger location being in the first area; and the second presentation module 730 may also be configured to present a first prompt on the first interface in response to receiving a second operation on the first component, the first prompt indicating that the second user is a participant in the live interaction.

[0175] In some cases, the second presentation module 730 can also be configured to present a fifth control in the first component. The fifth control is used to configure an interaction mode that indicates how the second user participates in the live interaction.

[0176] In some cases, the second presentation module 730 may also be configured to present a second component on the first interface in response to a trigger location being in the second area. The second component includes a first control and a second control, the first control being used to accept the first invitation and the second control being used to reject the first invitation.

[0177] In some cases, the second presentation module 730 may also be configured to present a first identifier corresponding to the first user in the second component.

[0178] In some cases, the first user corresponds to the first role in the live interaction, and the second presentation module 730 can also be configured to present a third component on the first interface, the type of which is related to the first role, and the first information includes the third component.

[0179] In some scenarios, the first role indicates that the first user is a guest user, and the third component includes a third control. The first receiving module 720 can also be configured to receive a third operation via the third component, the third operation including a triggering operation on the third control. The device 700 can also send a first request to a third user associated with the live stream to request participation in live stream interaction.

[0180] An interactive device 800 for implementing process 600 is also provided. Figure 8 A block diagram of device 800 is shown. Device 800 may be implemented as or included in electronic device 110.

[0181] like Figure 8 As shown, the device 800 includes a third presentation module 810, a second receiving module 820, and a fourth presentation module 830. The third presentation module 810 is configured to present a second interface displaying a live stream. The second receiving module 820 is configured to receive a second request for sharing the live stream. The fourth presentation module 830 is configured to present content items on the third interface. Each content item includes a first element, which includes descriptive information for a first invitation. This first invitation is used to invite at least one user to participate in a live stream interaction, which is associated with the live stream.

[0182] In some cases, the second receiving module 820 can also be configured to present an input control; and to obtain input content through the input control, and display the input content on a third interface.

[0183] In some cases, the third interface can display the first session. The fourth presentation module 830 can also be configured to present a first message including content items and a second message including input content.

[0184] In some cases, the second receiving module 820 may also be configured to present a fourth control, which is used to configure whether to invite at least one user to participate in the live interaction; and to receive the second request based on the triggering operation of the fourth control.

[0185] In some cases, the second receiving module 820 may also be configured to present at least one object identifier, the at least one object identifier including a first object identifier; receive a fourth operation, the fourth operation including a trigger operation on the first object identifier; and present a sharing component, the sharing component including the fourth control, the sharing component being used to share the live stream with the at least one user associated with the first object identifier.

[0186] In some cases, the second request originates from the first user, and content items can support access by multiple users.

[0187] In some cases, the third interface can be a session interface, where the participants include the first user and the plurality of second users. Alternatively, the third interface can be a viewing interface for second media content published by the first user, where the second media content includes content items.

[0188] In some scenarios, the media content viewing interface can display a content stream that includes third-party media content. The fourth presentation module 830 can also be configured to stop presenting content items and present the third-party media content in response to the fifth operation.

[0189] In some cases, the fourth presentation module 830 may also be configured to present the content item in a first style and, when the interaction state meets the conditions, present the content item in a second style representing the failure state.

[0190] In some cases, the fourth rendering module 830 can also be configured to stop rendering the first element. Alternatively, the fourth rendering module 830 can be configured to render the first element in a third style that indicates a disabled state.

[0191] In some cases, the conditions corresponding to the interactive state can be configured through a second request.

[0192] In some cases, the condition corresponding to the interactive state may include the presentation duration of the content item reaching a first time. Alternatively, this condition may include the number of times the content item is triggered reaching a first number.

[0193] In some cases, the second request may originate from the first user. If the first user is a guest user, device 800 may send a third request to the third user. The fourth presentation module 830 may also be configured to present content items on the third interface in response to a confirmation status of the third request.

[0194] In some cases, the second interface includes multiple areas, which are configured to display information from multiple participants.

[0195] The modules in devices 700 and 800 can be implemented using software, hardware, firmware, or any combination thereof. One or more modules can be implemented using machine-executable instructions on a storage medium.

[0196] Some or all of the modules in devices 700 and 800 may also be implemented using hardware logic components. Hardware logic components may include field-programmable gate arrays (FPGAs) or application-specific integrated circuits (ASICs). Hardware logic components may also include application-specific standard parts (ASSPs) or systems on a chip (SOCs). Alternatively, hardware logic components may include complex programmable logic devices (CPLDs).

[0197] Figure 9 A block diagram of an electronic device 900 in which one or more examples may be implemented is shown. It should be understood that... Figure 9The electronic device 900 shown is merely exemplary and should not be construed as limiting the functionality and scope of the examples described herein. Electronic device 900 can be used to implement electronic device 110.

[0198] like Figure 9 As shown, electronic device 900 is in the form of a general-purpose electronic device. Components of electronic device 900 may include one or more processors 910, memory 920, storage device 930, one or more communication units 940, one or more input devices 950, and one or more output devices 960. Processor 910 may be a physical or virtual processor and is capable of performing various processes according to programs stored in memory 920.

[0199] In a multiprocessor system, multiple processors can execute computer-executable instructions in parallel to improve the parallel processing capability of the electronic device 900. The electronic device 900 typically includes multiple computer storage media. Such media can be any media accessible to the electronic device 900, including volatile media, non-volatile media, removable media, and non-removable media.

[0200] The memory 920 can be either volatile or non-volatile. Volatile memory may include registers, caches, and random access memory (RAM). Non-volatile memory may include read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), and flash memory.

[0201] Storage device 930 may be a removable or non-removable medium. Storage device 930 may include a flash drive, a hard disk, or other medium capable of storing information and accessible within electronic device 900. Memory 920 may include computer program product 925. Computer program product 925 has one or more program modules configured to perform various example methods or actions.

[0202] The communication unit 940 enables communication with other electronic devices via a communication medium. The component functions of the electronic device 900 can be implemented in a single computing device or multiple computing devices. Multiple computing devices can communicate via a communication connection.

[0203] Input device 950 may include a mouse, keyboard, touchscreen, camera, or audio capture device. Output device 960 may include a monitor, speaker, or printer. Electronic device 900 may also communicate with external storage device or display device via communication unit 940.

[0204] A computer-readable storage medium is provided. The medium stores computer-executable instructions that are executed by a processor 910 to implement the methods described above. A computer program product 925 is also provided. The computer program product 925 includes computer-executable instructions that are executed by an electronic device 900 to implement the methods described above.

[0205] The flowcharts or block diagrams of the methods, apparatus, devices, and computer program products referred to herein describe various aspects. Each block in the flowchart or block diagram, and combinations of blocks, can be implemented by computer-readable program instructions.

[0206] Computer-readable program instructions can be provided to the processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device. When executed by the processor, these instructions create means for implementing the functions and actions shown in the flowchart or block diagram.

[0207] Computer-readable program instructions can also be stored in a computer-readable storage medium. The instructions cause a computer, programmable data processing device, or other equipment to function in a particular manner. A computer-readable medium storing instructions can constitute an article of manufacture comprising instructions that implement the corresponding functions and actions.

[0208] Computer-readable program instructions can also be loaded onto a computer, other programmable data processing apparatus, or other devices. This causes a series of operations to be performed on the corresponding device to produce a computer-implemented process.

[0209] The flowcharts and block diagrams in the accompanying figures illustrate the possible architecture, functionality, and operation of the system, method, and computer program product. Each block may represent a module, program segment, or part of an instruction. This part may contain one or more executable instructions for implementing the specified logical function.

[0210] In some alternative implementations, the functions marked in the boxes may occur in a different order than shown in the accompanying figures. Two consecutive boxes may be executed substantially in parallel or in reverse order. The boxes and combinations thereof may also be implemented by dedicated hardware or a combination of dedicated hardware and computer instructions.

[0211] Various examples have been described above. The above descriptions are exemplary, not exhaustive, and are not limited to the described implementations. Many modifications and changes can be made by those skilled in the art without departing from the scope and spirit of the described implementations.

Claims

1. A method for interface interaction, comprising: Present content items, which are related to the live stream shared by the first user; A first operation is received from a second user, the first operation including a triggering operation on the content item; as well as In response to the first operation, a first interface is presented, which displays first information related to a first invitation. The first invitation is used to invite the second user to participate in the live broadcast-related interaction.

2. The method according to claim 1, further comprising: The content item presents first media content and a first element, the first media content being related to the live stream, and the first element including descriptive information of the first invitation.

3. The method according to claim 1, further comprising: On the first interface, interactive components are presented. The type of the interactive components is related to the triggering position of the first operation. The first information includes the interactive components.

4. The method according to claim 3, wherein presenting interactive components on the first interface includes: In response to the trigger location being located in the first area, the first component is presented on the first interface; and The method further includes: In response to receiving a second operation on the first component, a first prompt is displayed on the first interface, indicating that the second user is a participant in the live interaction.

5. The method according to claim 3, further comprising: In response to the trigger location being in the second area, a second component is presented on the first interface. The second component includes a first control and a second control. The first control is used to accept the first invitation, and the second control is used to reject the first invitation.

6. The method according to claim 5, further comprising: In the second component, a first identifier is presented, which corresponds to the first user.

7. The method according to claim 1, wherein the first user corresponds to a first role in the live interaction, the method further comprising: On the first interface, a third component is presented. The type of the third component is related to the first role, and the first information includes the third component.

8. The method of claim 7, wherein the first role indicates that the first user is a guest user in the live interaction, the third component includes a third control, and the method further includes: The third component receives a third operation, which includes a trigger operation on the third control. as well as A first request is sent to a third user, the first request being used to request participation in the live stream interaction, the third user being related to the live stream.

9. A method for interface interaction, comprising: A second interface is displayed, which shows the live stream. Receive a second request, the second request being used to share the live stream; as well as On the third interface, content items are presented, including a first element. The first element includes a description of a first invitation, which is used to invite at least one user to participate in a live interaction. The live interaction is related to the live stream.

10. The method of claim 9, wherein receiving the second request comprises: A fourth control is presented, which is used to configure whether to invite the at least one user to participate in the live interaction; as well as Based on the triggering operation of the fourth control, the second request is received.

11. The method of claim 10, wherein presenting the fourth control comprises: Present at least one object identifier, wherein the at least one object identifier includes a first object identifier; Receive a fourth operation, the fourth operation including a trigger operation on the first object identifier; as well as A sharing component is presented, the sharing component including the fourth control, the sharing component being used to share the live stream with the at least one user, the at least one user being associated with the first object identifier.

12. The method of claim 9, wherein the second request originates from the first user, and the content item supports access by multiple second users.

13. The method of claim 12, wherein the third interface comprises: A conversation interface, wherein the participants in the conversation interface include the first user and the plurality of second users; or The interface for viewing second media content, which is published by the first user, includes the content items.

14. The method of claim 9, further comprising: The content items are presented in the first style; as well as In response to the content item's interaction state meeting a condition, the content item is presented in a second style, which indicates that the content item is in an invalid state.

15. The method of claim 14, wherein presenting the content item in a second style comprises: Stop displaying the first element in the content item; or The first element is presented in a third style, which represents the disabled state of the first element.

16. The method of claim 9, wherein the second request originates from the first user, and the presentation of content items on the third interface includes: In response to the fact that the first user is a guest user in the live interaction, a third request is sent to the third user; as well as In response to the confirmation status of the third request, the content item is presented on the third interface.

17. A device for interface interaction, comprising: The first presentation module is configured to present content items, which are associated with the live stream shared by the first user, and the live stream is associated with live interaction; A first receiving module is configured to receive a first operation from a second user, the first operation including a triggering operation on the content item; as well as The second presentation module is configured to respond to the first operation by presenting a first interface, the first interface displaying first information related to a first invitation, the first invitation being used to guide the second user to participate in the live interaction.

18. A device for interface interaction, comprising: The third presentation module is configured to present the second interface, which displays the live stream. The second receiving module is configured to receive a second request, the second request being used to share the live stream; as well as The fourth presentation module is configured to present content items on the third interface. The content items include a first element, which includes description information of a first invitation. The first invitation is used to invite at least one user to participate in a live interaction, and the live interaction is associated with the live stream.

19. An electronic device comprising: At least one processor; as well as At least one memory coupled to the at least one processor and storing instructions for execution by the at least one processor, the instructions causing the electronic device to perform the method according to any one of claims 1 to 8 or 9 to 16 when executed by the at least one processor.

20. A computer program product tangibly stored in a computer storage medium and comprising computer-executable instructions that, when executed by a device, cause the device to perform the method according to any one of claims 1 to 8 or 9 to 16.

Images