Live streaming room sharing method, device, system, equipment and program product

Abstract

This disclosure provides a method, apparatus, system, device, and program product for sharing live streams, relating to the field of internet live streaming technology. The live stream sharing method includes: receiving an activity sharing request; generating the activity sharing request when a limited-time activity sharing entry point in the target live stream is triggered, the activity sharing request including a live stream identifier, a sharing user identifier, and a sharing entry identifier, the live stream identifier identifying the target live stream, the sharing user identifier identifying the user initiating the activity sharing request, and the sharing entry identifier identifying the limited-time activity sharing entry point; querying the valid activity period of the limited-time activity based on the sharing entry identifier; and when it is detected that the limited-time activity has ended, feeding back sharing information according to a predetermined degradation method, the predetermined degradation method being used to downgrade the activity sharing of the target live stream to a general sharing of the target live stream, the sharing information being associated with the live stream identifier and the sharing user identifier.

Description

Technical Field

[0001] This specification relates to the field of Internet live streaming technology, and in particular to a live streaming sharing method, device, system, computer equipment, computer-readable storage medium, and computer program product. Background Technology

[0002] With the rapid development of the internet and live streaming technology, various limited-time events have become an important means for platforms to increase user activity. For live streaming platforms, limited-time events are usually promoted through associated live streaming rooms. During the event, users can complete corresponding sharing tasks in the live streaming room through their live streaming client to earn rewards. However, limited-time events usually have a set validity period. When the event ends, some live streaming clients may still be in the live streaming room, and the cached event parameters may be updated later. This means that the live streaming client can still initiate event sharing requests, but the server has updated the event parameters in time. Therefore, the server will directly reject the event sharing requests initiated by the live streaming client after the event ends, causing the live streaming client to receive error messages and be unable to complete the sharing operation, thus affecting the user experience.

[0003] In view of the above, some embodiments of this specification provide a method, apparatus, system, computer device, computer-readable storage medium, and computer program product for sharing live streaming rooms, which aim to improve the live streaming room sharing experience after the end of a limited-time event. Summary of the Invention

[0004] This specification provides one or more embodiments of a live streaming room sharing method, the method comprising: receiving an activity sharing request; generating the activity sharing request when a limited-time activity sharing entry for a target live streaming room is triggered, the activity sharing request including a live streaming room identifier, a sharing user identifier, and a sharing entry identifier, wherein the live streaming room identifier is used to identify the target live streaming room, the sharing user identifier is used to identify the user initiating the activity sharing request, and the sharing entry identifier is used to identify the limited-time activity sharing entry; querying the valid activity period of the limited-time activity based on the sharing entry identifier; and when it is detected that the limited-time activity has ended, feeding back sharing information according to a predetermined degradation method, wherein the predetermined degradation method is used to downgrade the activity sharing of the target live streaming room to a general sharing of the target live streaming room, and the sharing information is associated with the live streaming room identifier and the sharing user identifier.

[0005] According to one or more embodiments of this specification, the activity sharing request includes a first sharing request of image type; the sharing information includes an empty sharing code generated based on a first error code; receiving the activity sharing request includes: receiving the first sharing request transmitted by the client through a first link; the first sharing request carries a source mark during transmission through the first link, the source mark being used to indicate that the sharing information is returned through the first link; the first link is an activity image sharing path associated with the target live streaming room; when it is detected that the timed activity has ended, the sharing information is fed back according to a predetermined degradation method, including: when it is detected that the timed activity has ended, a first error code is fed back through the first link, the first error code being used to indicate the return of an empty sharing code, the empty sharing code being used to trigger the client to automatically switch to a second link to resend the first sharing request to obtain a general sharing image of the target live streaming room, the general sharing image being associated with the live streaming room identifier and the sharing user identifier; the second link is a general image sharing path associated with the target live streaming room.

[0006] According to one or more embodiments of this specification, the method for sharing an activity includes a second sharing request of a link type; the sharing information includes a live room sharing link; receiving the activity sharing request includes: receiving the second sharing request transmitted by the client through a third link; the third link is an activity and / or general link sharing path associated with the target live room; when it is detected that the time-limited activity has ended, the sharing information is fed back according to a predetermined degradation method, including: when it is detected that the time-limited activity has ended, generating a general sharing link for the target live room based on the live room identifier and the sharing user identifier, and returning the general sharing link through the third link.

[0007] According to one or more embodiments of this specification, the activity sharing request includes a third sharing request of the password type; the sharing information includes a live room sharing password; receiving the activity sharing request includes: receiving the third sharing request transmitted by the client through a fourth link; the fourth link is an activity and / or general password sharing path associated with the target live room; when it is detected that the time-limited activity has ended, the sharing information is fed back according to a predetermined degradation method, including: when it is detected that the time-limited activity has ended, generating a general sharing password for the target live room based on the live room sharing text, the live room identifier, and the sharing user identifier, and returning the general sharing password through the fourth link.

[0008] According to one or more embodiments of this specification, the method further includes: when it is detected that the limited-time activity is still valid, querying whether the target live room belongs to the activity live room corresponding to the limited-time activity based on the live room identifier; the limited-time activity is participated in by at least one activity live room; if the target live room does not belong to the activity live room, then a second error code is fed back, the second error code being used to indicate that the sharing has been rejected.

[0009] According to one or more embodiments of this specification, the method further includes: when it is detected that the timed activity is still valid, if a system abnormality occurs, a third error code is fed back, the third error code being used to indicate that an abnormality has occurred and to guide a retry; the system abnormality includes at least one of request timeout and system error.

[0010] According to one or more embodiments of this specification, the method further includes: during the effective activity period of a time-limited activity, acquiring response information associated with an activity sharing request, the response information including at least a response time and a response result; determining the error ratio of the number of requests that return a third error code within a sliding time window to the total number of requests; if the error ratio corresponding to a predetermined number of consecutive sliding time windows exceeds a ratio threshold, then for the received activity sharing request, returning sharing information according to a predetermined degradation method.

[0011] This specification provides one or more embodiments of a live streaming room sharing method, the method comprising: when a limited-time activity sharing entry for a target live streaming room is triggered, generating an activity sharing request based on a live streaming room identifier, a sharing user identifier, and a sharing entry identifier; the live streaming room identifier is used to identify the target live streaming room, the sharing user identifier is used to identify the user initiating the activity sharing request, and the sharing entry identifier is used to identify the limited-time activity sharing entry; sending the activity sharing request; the activity sharing request is used to trigger a query for the valid activity period of the limited-time activity based on the sharing entry identifier; receiving feedback sharing information, the sharing information being associated with the live streaming room identifier and the sharing user identifier; the sharing information being obtained according to a predetermined downgrade method when it is detected that the limited-time activity has ended; the predetermined downgrade method is used to downgrade the activity sharing of the target live streaming room to a general sharing of the target live streaming room.

[0012] According to one or more embodiments of this specification, the activity sharing request includes a first sharing request of image type; the sharing information includes an empty sharing code generated based on a first error code; sending the activity sharing request includes: sending the first sharing request through a first link; the first sharing request is carried with a source mark during transmission through the first link, the source mark being used to indicate that the sharing information is returned through the first link; the first link is an activity image sharing path associated with a target live streaming room; receiving feedback sharing information includes: receiving an empty sharing code generated based on the feedback first error code through the first link, and automatically switching to a second link to resend the first sharing request based on the empty sharing code; the first error code is fed back when it is detected that the timed activity has ended; the second link is a general image sharing path associated with the target live streaming room; receiving a general sharing image of the target live streaming room fed back through the second link, the general sharing image being associated with a live streaming room identifier and a sharing user identifier.

[0013] According to one or more embodiments of this specification, the activity sharing request includes a second sharing request of the link type; the sharing information includes a live room sharing link; sending the activity sharing request includes: sending the second sharing request through a third link; the third link is an activity and / or general link sharing path associated with the target live room; receiving feedback sharing information includes: receiving the general sharing link of the target live room through the third link; the general sharing link is generated based on the live room identifier and the sharing user identifier when it is detected that the time-limited activity has ended.

[0014] According to one or more embodiments of this specification, the activity sharing request includes a third sharing request of the password type; the sharing information includes a live room sharing password; sending the activity sharing request includes: sending the third sharing request through a fourth link; the fourth link is an activity and / or general password sharing path associated with the target live room; receiving feedback sharing information includes: receiving the target live room's general sharing password through the fourth link, the general sharing password being generated based on the live room sharing text, the live room identifier, and the sharing user identifier when it is detected that the time-limited activity has ended.

[0015] This specification also provides a live streaming room sharing device in one or more embodiments. The device includes: a request receiving module, used to receive an activity sharing request; the activity sharing request is generated when the limited-time activity sharing entry of the target live streaming room is triggered, the activity sharing request includes a live streaming room identifier, a sharing user identifier, and a sharing entry identifier, the live streaming room identifier is used to identify the target live streaming room, the sharing user identifier is used to identify the user who initiated the activity sharing request, and the sharing entry identifier is used to identify the limited-time activity sharing entry; an activity query module, used to query the valid activity period of the limited-time activity based on the sharing entry identifier; and an information feedback module, used to provide sharing information according to a predetermined degradation method when it is detected that the limited-time activity has ended, the predetermined degradation method is used to downgrade the activity sharing of the target live streaming room to the general sharing of the target live streaming room, and the sharing information is associated with the live streaming room identifier and the sharing user identifier.

[0016] This specification also provides a live streaming room sharing device in one or more embodiments. The device includes: a request generation module, used to generate an activity sharing request based on a live streaming room identifier, a sharing user identifier, and a sharing entry identifier when a limited-time activity sharing entry for a target live streaming room is triggered; the live streaming room identifier is used to identify the target live streaming room, the sharing user identifier is used to identify the user initiating the activity sharing request, and the sharing entry identifier is used to identify the limited-time activity sharing entry; a request sending module, used to send the activity sharing request; the activity sharing request is used to trigger a query for the valid activity period of the limited-time activity based on the sharing entry identifier; and an information receiving module, used to receive feedback sharing information, the sharing information being associated with the live streaming room identifier and the sharing user identifier; the sharing information is obtained according to a predetermined downgrade method when it is detected that the limited-time activity has ended; the predetermined downgrade method is used to downgrade the activity sharing of the target live streaming room to a general sharing of the target live streaming room.

[0017] This specification also provides a live streaming room sharing system in one or more embodiments. The system includes: a client and a server; the client is used to generate an activity sharing request based on the live streaming room identifier, the sharing user identifier, and the sharing entry identifier when the limited-time activity sharing entry of the target live streaming room is triggered, and to send the activity sharing request to the server and receive sharing information from the server; the live streaming room identifier is used to identify the target live streaming room, the sharing user identifier is used to identify the user who initiated the activity sharing request, and the sharing entry identifier is used to identify the limited-time activity sharing entry; the server is used to receive the activity sharing request, query the valid activity period of the limited-time activity based on the sharing entry identifier, and when it is detected that the limited-time activity has ended, to provide sharing information to the client according to a predetermined degradation method; the predetermined degradation method is used to downgrade the activity sharing of the target live streaming room to the general sharing of the target live streaming room, and the sharing information is associated with the live streaming room identifier and the sharing user identifier.

[0018] One or more embodiments of this specification also provide a computer device, which includes a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, it can implement the live streaming sharing method described in some embodiments of this specification.

[0019] One or more embodiments of this specification also provide a computer-readable storage medium storing computer instructions, which, when executed by a processor, can implement the live streaming sharing method described in some embodiments of this specification.

[0020] One or more embodiments of this specification also provide a computer program product, including a computer program that, when at least a portion of the computer program is executed by a processor, can implement the live streaming sharing method described in some embodiments of this specification.

[0021] The effective effects that the embodiments of this specification may bring include, but are not limited to: querying the valid activity period of the limited-time activity based on the sharing entry identifier in the activity sharing request, and feeding back sharing information according to the predetermined downgrade method after the limited-time activity has ended. Since the predetermined downgrade method is used to downgrade the activity sharing of the target live room to the general sharing of the target live room, the sharing information can still be fed back even after the limited-time activity has ended, so that the user can complete the sharing operation without realizing it, avoiding the direct rejection of the activity sharing request and causing the user to keep receiving error messages, thus improving the live room sharing experience after the limited-time activity ends.

[0022] Since the first image sharing request carries a source marker during transmission through the first link, the source marker can indicate that the sharing information is returned through the first link. The first link is the active image sharing path associated with the target live stream room. Therefore, it can be ensured that the sharing information can be returned through the active image sharing path, avoiding the breakdown of the degradation link, that is, avoiding the failure of the transmission of the sharing information used to transmit the degradation signal. The returned sharing information includes an empty sharing code generated based on the first error code. The empty sharing code can trigger the client to automatically switch to the second link to resend the first sharing request. The second link is the general image sharing path associated with the target live stream room. Since the client's link switching is automatically triggered based on the feedback empty sharing code, it can achieve image sharing degradation without the user's awareness, and can transmit the first sharing request through the general image sharing path to obtain the general shared image of the target live stream room.

[0023] For the second sharing request of the link type, when it is detected that the time-limited event has ended, a general sharing link of the target live room can be generated based on the live room identifier and the sharing user identifier in the second sharing request, so that the link sharing can be downgraded without the user's awareness.

[0024] For third-party sharing requests using passwords, once the time-limited event has ended, a universal sharing password for the target live stream can be generated based on the live stream sharing text, the live stream identifier, and the sharing user identifier. This allows for password sharing downgrades that are imperceptible to the user, and the displayed sharing password can be replaced by the live stream sharing text instead of the event sharing text.

[0025] During the validity period of the limited-time event, if a second error code is returned when the target live stream is not found to be the live stream corresponding to the limited-time event, the client can be triggered to display a message indicating that the sharing has been rejected. This distinguishes the event from the downgraded handling method after the event ends and accurately conveys feedback information for different abnormal situations.

[0026] During the effective period of the actual event, by reporting a third error code when a system abnormality occurs, the client can be triggered to display a prompt message guiding retry. This can be distinguished from abnormal situations such as non-event live rooms and the end of limited-time events, accurately conveying the message that the event sharing failed to the user. This can avoid direct downgrading that may cause users to mistakenly believe that they have successfully participated in the event, resulting in a loss of event experience.

[0027] By acquiring the response time and results associated with sharing requests during the effective period of a limited-time event, and calculating the error ratio of requests with the third error code within a sliding time window to the total number of requests, when the error ratio corresponding to a predetermined number of consecutive sliding time windows exceeds a threshold, it indicates that the system anomaly may be an unrecoverable fault. In this case, instead of guiding the user to retry, the sharing information is switched to a predetermined degradation method, degrading the sharing of the target live stream to a general sharing of the target live stream, thus avoiding repeated retries that negatively impact the user's sharing experience. The error ratio determined by the sliding time window is dynamically changing; therefore, when the error ratio is below the threshold, user retry guidance can be restored, achieving dynamic feedback based on fault conditions.

[0028] It should be noted that different embodiments may produce different beneficial effects. In different embodiments, the beneficial effects may be any one or a combination of the above, or any other possible beneficial effects. Attached Figure Description

[0029] This specification will be further described by way of exemplary embodiments, which will be described in detail with reference to the accompanying drawings. The same numbers in the drawings denote the same structures or steps.

[0030] Figure 1 This is a schematic diagram illustrating an application scenario of live streaming sharing according to some embodiments of this specification.

[0031] Figure 2 This is an exemplary flowchart illustrating a live streaming sharing method according to some embodiments of this specification.

[0032] Figure 3 This is a schematic diagram of a first link for sharing images in a live streaming room, as shown in some embodiments of this specification.

[0033] Figure 4 This is a schematic diagram of a third link for sharing a live streaming room link, as shown in some embodiments of this specification.

[0034] Figure 5 This is a schematic diagram of a fourth link for sharing live room passwords, as shown in some embodiments of this specification.

[0035] Figure 6 This is a schematic diagram of a second link for sharing images in a live streaming room, as shown in some embodiments of this specification.

[0036] Figure 7 This is an exemplary flowchart illustrating a non-activity live stream sharing during an activity, according to some embodiments of this specification.

[0037] Figure 8 This is an exemplary flowchart illustrating an adaptive degradation based on error rate feedback during an activity, according to some embodiments of this specification.

[0038] Figure 9 This is an exemplary flowchart illustrating another live streaming sharing method according to some embodiments of this specification.

[0039] Figure 10 This is an exemplary block diagram of a live streaming sharing device according to some embodiments of this specification.

[0040] Figure 11 This is an exemplary block diagram of another live streaming sharing device according to some embodiments of this specification.

[0041] Figure 12 This is an exemplary block diagram of a live streaming sharing system according to some embodiments of this specification. Detailed Implementation

[0042] To more clearly illustrate the technical solutions of the embodiments in this specification, the embodiments will be described in detail below with reference to the accompanying drawings. Obviously, the content described below are some examples or embodiments of this specification. For those skilled in the art, without creative effort, the technical solutions or means disclosed in this specification can be applied to other scenarios based on this technical content.

[0043] It should be understood that the terms "system," "device," "unit," and / or "module" used in this specification are a method of distinguishing different components, elements, parts, sections, or assemblies at different levels. However, if other terms can achieve the same purpose, they may be replaced by other expressions.

[0044] Unless otherwise specified, the technical terms used to describe components, elements, etc. in this specification are not singular but may include plural. Generally speaking, terms such as "comprising" or "including" only indicate that explicitly identified steps, elements, or components are included, and these steps, elements, and components do not constitute an exclusive list, as the described method or apparatus may also include other steps or components.

[0045] This specification uses flowcharts to illustrate the operational steps performed by the apparatus or system of related embodiments. However, unless otherwise specified, the order in which these steps are described should not be construed as a limitation on the order of execution. Those skilled in the art can adjust the order of these steps based on the knowledge and information conveyed by the embodiments in this specification. Such adjustments include, but are not limited to, reversing the order of steps, merging multiple steps, and splitting a step.

[0046] With the rapid development of the internet and live streaming technology, various limited-time events have become an important means for platforms to increase user activity. For live streaming platforms, limited-time events are usually promoted through associated live streaming rooms. During the event, users can complete corresponding sharing tasks in the live streaming room through their live streaming client to earn rewards. However, limited-time events usually have a set validity period. When the event ends, some live streaming clients may still be in the live streaming room, and the cached event parameters may be updated later. This means that the live streaming client can still initiate event sharing requests, but the server has updated the event parameters in time. Therefore, the server will directly reject the event sharing requests initiated by the live streaming client after the event ends, causing the live streaming client to receive error messages and be unable to complete the sharing operation, thus affecting the user experience.

[0047] Therefore, some embodiments of this specification propose a method, apparatus, system, computer device, computer-readable storage medium, and computer program product for sharing live streams, aiming to improve the live stream sharing experience after a limited-time event ends.

[0048] Figure 1 This is a schematic diagram illustrating an application scenario of live streaming sharing, based on some embodiments of this specification. For example... Figure 1As shown, application scenario 100 may include: server 110, client 120, and network 130. Server 110 and client 120 can transmit data through network 130. Client 120 may be a live streaming client, which may include a sharing SDK (Software Development Kit). The sharing SDK refers to the sharing component integrated into the live streaming client, used to call the interface provided by the target sharing channel to send shared content. Server 110 may include a sharing server, which can handle various sharing requests, such as generating sharing codes, sharing links, and sharing passwords for live streaming rooms, and also generating sharing codes, sharing links, and sharing passwords for limited-time events. In some embodiments, server 110 may further include a live streaming server. The live streaming server can receive a request from a live streaming client to share an activity image related to a limited-time event in the live streaming room, and transmit the activity image sharing request to the sharing server after adding a source tag. The source tag is used to notify the sharing server that the activity image sharing request originates from the activity link, thereby instructing the sharing server to provide feedback on the processing result of the activity image sharing request through the activity link (feedback on activity sharing information during the event, and feedback on activity error information after the event ends). In some embodiments, the live streaming server can also add information about the live streaming room (e.g., the name, identifier, avatar, etc. of the live streaming room) based on the activity sharing information (e.g., activity sharing code, activity image, etc.) provided by the sharing server to assemble a complete sharing material, and return the complete sharing material to the live streaming client. The live streaming client can render and display the activity sharing image containing the activity sharing code based on the complete sharing material. In some embodiments, the live streaming server can also return an empty sharing code to the live streaming client based on the activity error information provided by the sharing server. The empty sharing code can trigger the live streaming client to automatically switch to the general link (the regular sharing link of the live streaming room) and resend the sharing request to obtain the general sharing image of the live streaming room. In some embodiments, the sharing server and the live streaming server can be independent of each other. In some embodiments, the sharing server and the live streaming server can be integrated into one.

[0049] In some embodiments, server 110 may be a high-performance computer device used to process various sharing requests (event sharing requests or live stream sharing requests). In some embodiments, server 110 includes a sharing server that can provide feedback on sharing information according to a predetermined degradation method when the time-limited event ends. The predetermined degradation method is used to downgrade the event sharing in the live stream to a general sharing in the live stream. In some embodiments, server 110 may include a background processing server that can receive event sharing requests and, when it detects that the time-limited event has ended, provide feedback on sharing information according to a predetermined degradation method. In some embodiments, server 110 may include a local server or a cloud server. Depending on different service requirements, local servers corresponding to one or more regions may be deployed. In some embodiments, server 110 also includes a live stream server that can transmit data based on a streaming media transmission protocol. The streaming media transmission protocol may include: HLS (HTTP Live Streaming), RTMP (Real-Time Messaging Protocol), DASH (Dynamic Adaptive Streaming over HTTP), etc. In some embodiments, server 110 may include a streaming media server, a transcoding server, a storage server, an authentication server, etc. The streaming media server can transmit data based on a streaming media transmission protocol. The transcoding server can be used to transcode live video data, the storage server can be used to cache and store live data, and the authentication server can be used to verify user access permissions. In some embodiments, server 110 may be a single computer device or a computing cluster composed of multiple computer devices, thereby providing more powerful computing power and more efficient response to user service requests. It is understood that in the specific embodiments of this specification, the collection, use, or processing of data (such as live room identifiers, sharing user identifiers, sharing entry identifiers, etc.) involves the following: When one or more embodiments of this specification are applied to specific products or technology implementations, permission or consent from the data subject is required. Furthermore, the collection, use, or processing of related data must strictly comply with the relevant laws, regulations, and standards of the data source country, implementation country, and other relevant countries and regions. De-identification technology is used to ensure that the final data used is securely processed de-identified data, protecting the rights and interests of the data subject and data security.

[0050] In some embodiments, client 120 can be a live stream viewer client, used to display the live stream room and play corresponding live stream video data to viewers. It can also provide interactive functions and interfaces (e.g., displaying a sharing control), and can generate an activity sharing request based on the live stream room identifier, the sharing user identifier, and the sharing entry identifier when the limited-time activity sharing entry of the live stream room is triggered. In some embodiments, client 120 can be, but is not limited to, terminal devices such as desktop computers, smartphones, laptops, VR (Virtual Reality) devices, tablets, smart TVs, and in-vehicle terminals. In some embodiments, client 120 can be an APP, mini-program, website, etc., running on the terminal and corresponding to the live stream platform, to use the viewer-related functions or services provided by the live stream platform. Client 120 can include a display screen and a processor. The display screen can be used to present a graphical user interface. For example, client 120 can present the live stream video content of the live stream room through the graphical user interface. In some embodiments, the display screen can be separated from the human-machine interface device. Users can operate on the graphical user interface through the human-machine interface device. The processor of client 120 can receive operation instructions generated by operating on the graphical user interface through the human-machine interface device. The display screen can be used to present the graphical user interface, for example, to present the response results generated based on the operation instructions input by the graphical user interface. In other embodiments, the display screen may be a touch screen, which can receive user operation commands input based on the graphical user interface. For example, the operation commands generated by the user acting on the graphical user interface may include an activity sharing request generated by the timed activity sharing entry point that triggers the live event room in the graphical user interface. The processor of the client 120 may be configured to transmit the activity sharing request to the server 110 for processing after receiving the activity sharing request generated by the timed activity sharing entry point that triggers the live event room. In some embodiments, the activity sharing request may be an activity image sharing request. If the activity is valid, the client 120 receives the activity image sharing material returned by the server 110 and renders and displays it. If the activity is not valid, the client 120 receives the live event room sharing image returned by the server 110 and displays it.

[0051] In some embodiments, network 130 can be any form of wired or wireless network, or any combination thereof. As examples, network 130 can be one or more combinations of wired networks, fiber optic networks, telecommunications networks, internal networks, the Internet, local area networks (LANs), wide area networks (WANs), wireless local area networks (WLANs), metropolitan area networks (MANs), public switched telephone networks (PSTNs), Bluetooth networks, etc. Network 130 can have multiple access points, through which server 110 and client 120 can access network 130.

[0052] It should be noted that, Figure 1 The application scenario of live streaming sharing shown is merely an example. The application scenarios described in the embodiments of this specification are for the purpose of more clearly illustrating the technical solutions of the embodiments of this specification, and do not constitute a limitation on the technical solutions provided in the embodiments of this specification. For example, Figure 1 The number of server-side 110 and client-side 120 in this specification is merely illustrative and is not intended to limit the scope of patent protection of this application. Depending on the actual situation, any number of server-side 110 and client-side 120 may be used. As will be apparent to those skilled in the art, with the development of live streaming technology and the emergence of new business scenarios, the technical solutions provided in the embodiments of this specification are also applicable to similar technical problems.

[0053] To improve the live stream sharing experience after the limited-time event ends, this manual provides a method for sharing the live stream. Figure 2 This is an exemplary flowchart illustrating a live streaming room sharing method according to some embodiments of this specification. Figure 2 The process 200 shown can be executed by a processing device, for example, by... Figure 1 The server 110 shown executes the process. In some embodiments, process 200 can be implemented by a live streaming sharing device 1000 deployed on a processing device. The live streaming sharing device 1000 may include a request receiving module 1010, an activity query module 1020, and an information feedback module 1030. Figure 2 As shown, in some embodiments, process 200 may include the following steps.

[0054] Step 210: Receive an activity sharing request. The activity sharing request is generated when the time-limited activity sharing entry of the target live room is triggered. The activity sharing request includes the live room identifier, the sharing user identifier, and the sharing entry identifier. In some embodiments, step 210 can be implemented by the request receiving module 1010.

[0055] In some embodiments, a limited-time event can be a specific event initiated by a live streaming platform with a valid event period. The limited-time event is participated in by at least one live streaming room, which can be called the event live streaming room. Users can share the limited-time event information by initiating a sharing operation in the event live streaming room. If the sharing is successful and / or the shared user enters the event live streaming room through the sharing user's sharing behavior, the sharing user can be given corresponding rewards.

[0056] In some embodiments, the attribute information of an active live streaming room may include activity parameters, such as whether the live streaming room is an active live streaming room. For example, the field may be "Whether it is an active live streaming room," and the value of this field may include "Yes" (which can also be represented by "1," "T," "true," etc.) or "No" (which can also be represented by "0," "F," "false," etc.). In some embodiments, during an active period, when a live streaming client first enters a live streaming room, the live streaming client requests various attribute information and streaming data of the live streaming room from the live streaming server and caches them. If the live streaming client remains in the live streaming room, in order to reduce the pressure on the live streaming server and network overhead, the basic attribute information of the live streaming room (including the live streaming room name, live streaming room identifier, broadcaster identifier, whether it is an active live streaming room, streaming address, etc.) remains unchanged in the cache, while the cached live streaming data, real-time interaction data, etc., can be updated in real time. In some embodiments, when the live streaming client re-enters the live streaming room or restarts the live streaming platform (including restarting the website, APP, mini-program, etc.), the live streaming client re-requests various attribute information and streaming data of the live streaming room from the live streaming server, and the previously cached information is updated. In some embodiments, the cache has a cache TTL (Time To Live), which refers to the effective duration for which cached data is allowed to exist in the storage medium. If there is no re-entry into the live room or restart of the live platform, the cached information will be updated after the cache TTL expires.

[0057] In some embodiments, when a live streaming client receives an instruction that a time-limited event sharing entry has been triggered within an active live streaming room, the live streaming client can query the cached attribute information of the live streaming room, generate an event sharing instruction based on the live streaming room identifier, sharing entry identifier, and sharing user identifier that triggered the sharing instruction in the attribute information, and query whether the live streaming room is an active live streaming room. For active live streaming rooms, two sharing paths can be configured: an active sharing path and a general sharing path (the two sharing paths may be different or the same). The live streaming client can determine which path to send the event sharing request through based on the query result of whether it is an active live streaming room. If it is an active live streaming room, the event sharing request is sent through the active sharing path; if it is not an active live streaming room, the event sharing request is sent through the general sharing path. In some embodiments, if the live streaming client remains within the active live streaming room, after the time-limited event ends, due to the lag in updating the cached information (not re-entering the live streaming room, not restarting the live streaming platform, or the cache TTL not expiring), the value of the cached "whether it is an active live streaming room" field may not be updated in time. When the live streaming client receives an instruction that a time-limited event sharing entry has been triggered after the event ends, the live streaming client can still send the event sharing request through the active sharing path based on the query result of whether it is an active live streaming room. In some embodiments, there may be multiple limited-time events in the same time period or the effective activity periods of multiple limited-time events may overlap. Different limited-time events may correspond to different limited-time event sharing entry points, and different limited-time event sharing entry points correspond to different sharing entry point identifiers.

[0058] In some embodiments, where there may be multiple limited-time events within the same time period or the effective activity periods of multiple limited-time events may overlap, the attribute information of the live streaming room may include information about the limited-time events that the live streaming room participates in. For example, the field is "Participate in Limited-Time Events". The value of this field may include an event identifier, which is used to identify the corresponding limited-time event. The event identifier may include the event name, such as "Accumulate Blessings for Chinese New Year". The event identifier may also include an event ID (Identification, event code, used to distinguish different limited-time events), such as "Event 112233". In some embodiments, if the "Participate in Limited-Time Events" field is empty or "0", it indicates that the live streaming room does not belong to the event live streaming room. In some embodiments, when a live streaming client receives an instruction that a limited-time event sharing entry has been triggered within an event live streaming room, the live streaming client can query the cached attribute information of the live streaming room, generate an event sharing request based on the live streaming room identifier, sharing entry identifier, and sharing user identifier that triggered the sharing instruction in the attribute information, and determine whether to send the event sharing request through the event sharing link (where the value of the "Participate in Limited-Time Event" field is the event identifier) ​​or through the general sharing link (where the value of the "Participate in Limited-Time Event" field is empty or 0) based on the value in the cached "Participate in Limited-Time Event" field. In some embodiments, the event sharing request may also include an event identifier so that the server can quickly determine the event corresponding to the event identifier. In some embodiments, the attribute information of the live streaming room may simultaneously include both "whether it is an event live streaming room" and "participate in a limited-time event" event parameters.

[0059] In some embodiments, a live room identifier is used to identify a target live room. In some embodiments, the live room identifier may be a string or numeric code that uniquely identifies the live room, generated and assigned by the live streaming server when the live room is created. In some embodiments, the live room identifier may include a live room ID, such as a numeric ID (e.g., 12345678) or a string ID (e.g., room_abc123).

[0060] In some embodiments, the sharing user identifier is used to identify the user who initiated the activity sharing request. In some embodiments, the sharing user identifier may refer to information that uniquely identifies the user who initiated the sharing. The sharing user identifier can be attributed to the sharing behavior in the sharing chain, recording "who initiated this sharing," so that when other users subsequently enter the activity live room through that user's sharing, the rewards can be correctly distributed to the user who initiated the sharing. In some embodiments, the sharing user identifier may include the account or UID (User Identification) of the user who initiated the sharing.

[0061] In some embodiments, the sharing entry identifier is used to identify the sharing entry point for a limited-time event. In some embodiments, the sharing entry identifier can uniquely identify the specific trigger point within the client for initiating the sharing of the event. For example, the trigger point for initiating the sharing of the event could be triggering the "Share" option after triggering an extended menu control (e.g., the "..." control in the upper right corner of the live stream page), and then triggering the limited-time event sharing entry point in the pop-up sharing channel list. Alternatively, the trigger point could be triggering the "Share" option after triggering an extended function control (e.g., the "+" control in the message editing bar) in the message editing area, and then triggering the limited-time event sharing entry point in the pop-up sharing channel list. Different trigger points correspond to different sharing entry identifiers, which can be used to distinguish different sharing entry points. For limited-time events, a specific entry point associated with the limited-time event can be added to the sharing channel list of the event's live stream. In some embodiments, the sharing entry identifier may include a sharing entry ID or a share_ID. In some embodiments, different types of limited-time event sharing entry points for the same limited-time event can correspond to different sharing entry point identifiers. For example, a limited-time event sharing entry point for an image type corresponds to the sharing entry point ID "share_id_11111", a limited-time event sharing entry point for a link type corresponds to the sharing entry point ID "share_id_22222", and a limited-time event sharing entry point for a password type corresponds to the sharing entry point ID "share_id_33333". In some embodiments, the sharing channel list can display only one limited-time event sharing entry point corresponding to the limited-time event. When the limited-time event sharing entry point is triggered, a pop-up window further displays the sharing type option (image sharing / link sharing / password sharing). When the sharing type option is triggered, the corresponding sharing entry point identifier can be determined based on two triggers. For example, the ID of the limited-time event sharing entry point is "share_id_123"; after the image type sharing option is triggered, the sharing entry point ID is updated to "share_id_123_1", after the link type sharing option is triggered, the sharing entry point ID is updated to "share_id_123_2", and after the password type sharing option is triggered, the sharing entry point ID is updated to "share_id_123_3". In some embodiments, when the limited-time event ends and the live streaming client updates the cache of the event's live streaming room, the limited-time event sharing entry becomes invalid and is removed from the sharing channel list.

[0062] In some embodiments, the activity sharing request can be sent directly from the live streaming client to the sharing server for processing via the sharing SDK. In other embodiments, the activity sharing request can be sent from the live streaming client to the live streaming server, which then forwards it to the sharing server for processing.

[0063] In some embodiments, the target live stream room may refer to the live stream room where the user triggers the sharing operation. In some embodiments, the target live stream room may refer to the live stream room participating in a limited-time event. In some embodiments, the basic attribute information of the target live stream room cached on the live streaming client may differ from the basic attribute information of the target live stream room stored on the live streaming server due to parameter lag.

[0064] In some embodiments, the activity sharing request may include a first sharing request of the image type. In some embodiments, step 210 may further include: receiving a first sharing request transmitted by the client through a first link; the first sharing request carries a source marker during transmission through the first link, the source marker being used to indicate that the sharing information is returned through the first link; the first link is an activity image sharing path associated with the target live streaming room.

[0065] In some embodiments, when the live streaming client receives a trigger instruction for the image sharing entry of a limited-time event or the image sharing option of the limited-time event sharing entry, the live streaming client can generate a first sharing request based on the live streaming room identifier, the sharing user identifier, and the sharing entry identifier.

[0066] In some embodiments, the first link may refer to an image-type activity sharing link. In some embodiments, the activity sharing image (i.e., the activity image of the target live stream) needs to display relevant elements of the live stream (e.g., the live stream cover, the host's nickname, the room number, etc.), the activity sharing code (obtained based on the sharing link, the live stream identifier, and the sharing user identifier encoding), and activity elements (e.g., activity images, activity text, etc.). The activity elements can be randomly selected by the server from multiple different sets of activity elements, making the presentation style of the activity sharing image more diverse. The image elements in the activity sharing image are more complex than those in a general sharing image, and the processing logic is different. Therefore, the design of the image-type activity sharing link is usually different from that of the general sharing link. In some embodiments, image-type activity sharing needs to go through the live stream server. When the live stream server receives the first sharing request of the image type sent by the live stream client, it adds a source tag and forwards it to the sharing server. The source tag can notify the sharing server that the first sharing request comes from the activity sharing link. In some embodiments, the source tag can be added to the extended parameters of the request. In some embodiments, if during the valid period of a limited-time event, the sharing server determines that the limited-time event is still valid and the live stream belongs to the event live stream based on the sharing entry identifier, then it will obtain the event sharing code based on the live stream identifier and the sharing user identifier. The sharing server will return the event sharing code to the live stream server. The live stream server will assemble complete sharing materials based on the live stream-related elements corresponding to the live stream identifier. The live stream server will return the sharing materials and the event sharing code to the live stream client together. The live stream client will render the event sharing image based on the received sharing materials and the event sharing code. In some embodiments, if the limited-time event has ended, but the live stream client's cached information is lagging, causing the live stream client to still initiate the first sharing request (image-type event sharing request) through the first link (event sharing link), the sharing server can return sharing information according to a predetermined degradation method (degrading the live stream event sharing to general sharing), in conjunction with reference to [reference needed]. Figure 3 , Figure 3 This is a schematic diagram of a first link for sharing images in a live streaming room, according to some embodiments of this specification. Exemplarily, in the first link 300, the live streaming client initiates a first sharing request to the live streaming server. The live streaming server adds a source marker (used to notify the sharing server that the first sharing request comes from the activity sharing link, so that the sharing server can quickly execute different processing logic for activity image sharing than for general image sharing), and then transmits the first sharing request to the sharing server. If the sharing server detects that the limited-time activity has ended, it returns a first error code (semantically corresponding to "activity has ended") to the live streaming server. Upon receiving the first error code, the live streaming server returns an empty sharing code to the live streaming client. The live streaming client automatically switches to the general sharing link (second link) based on the empty sharing code and retransmits the first sharing request. It should be noted that... Figure 3 The path after automatic retransmission corresponds to the general sharing link (second link). Figure 3 The process of switching links is briefly illustrated below. For the specific path of the general shared link (second link), please refer to the following text. Figure 6 The relevant information will not be repeated here.

[0067] In some embodiments, the activity sharing request may include a second sharing request of the link type. In some embodiments, step 210 may further include: receiving a second sharing request transmitted by the client via a third link; the third link is an activity and / or general link sharing path associated with the target live room.

[0068] In some embodiments, when the live streaming client receives a trigger instruction for sharing a link to a limited-time event or for sharing a link to a limited-time event, the live streaming client can generate a second sharing request based on the live streaming room identifier, the sharing user identifier, and the sharing entry identifier.

[0069] In some embodiments, the activity sharing link and the general sharing link in the live room can both be plain text content, the difference being that the text content is different. The server can return the activity sharing link corresponding to the limited-time activity or the general sharing link corresponding to the live room without too much complex processing. Therefore, for link-type sharing requests, the activity link sharing link and the general link sharing link can use the same link (i.e., the third link) and can be returned without calling the live room server to provide live room-related elements. The server (sharing server) decides whether to execute the predetermined degradation method based on the detection result of whether the limited-time activity has ended, and then decides whether to return the activity sharing link or the general sharing link.

[0070] Figure 4 This is a schematic diagram of a third-party link for sharing a live streaming room link, according to some embodiments of this specification. In some embodiments, such as Figure 4As shown, in the third link 400, the live streaming client initiates a second sharing request of the link type through the SDK. The sharing SDK requests an activity sharing link from the sharing server. If the activity is still within its validity period, the sharing server generates an activity sharing link based on the live room identifier and the sharing user identifier and returns it to the sharing SDK. The sharing SDK then returns the activity sharing link to the live streaming client, which can display the activity sharing link in the selected sharing channel (e.g., a social app). (Users who click the activity sharing link can be redirected to the activity page or the activity live room, and based on the sharing user identifier in the activity sharing link, the successful sharing behavior can be attributed to the user who initiated the sharing, and a corresponding reward can be issued to them.) If the sharing server detects that the limited-time activity has ended, it can generate a general sharing link based on the live room identifier and the sharing user identifier and return it to the sharing SDK. The sharing SDK then returns the general sharing link to the live streaming client, which can display the general sharing link in the selected sharing channel. (Users who click the general sharing link can be redirected to a regular live room to watch the live content.)

[0071] In some embodiments, the activity sharing request may include a third sharing request of the password type. In some embodiments, step 210 may further include: receiving a third sharing request transmitted by the client via a fourth link; the fourth link is an activity and / or general password sharing path associated with the target live room.

[0072] In some embodiments, when the live streaming client receives a trigger instruction for the password sharing entry of a time-limited event or the password sharing option of the time-limited event sharing entry, the live streaming client can generate a third sharing request based on the live streaming room identifier, the sharing user identifier, and the sharing entry identifier.

[0073] In some embodiments, the activity sharing password and the general sharing password for the live broadcast room can both be plain text content, the difference being that the text content is different. The server can return the activity sharing password corresponding to the limited-time activity or the general sharing password corresponding to the live broadcast room. Similarly, no complicated processing is required. Therefore, for password-type sharing requests, the activity password sharing link and the general password sharing link can use the same link (i.e., the fourth link). The server (sharing server) determines whether to execute the predetermined degradation method based on the detection result of whether the limited-time activity has ended, and then decides whether to return the activity sharing password or the general sharing password.

[0074] Figure 5 This is a schematic diagram of a fourth link for sharing live streaming passwords, according to some embodiments of this specification. In some embodiments, such as... Figure 5As shown, in the fourth link 500, the live streaming client initiates a third sharing request of the password type through the SDK. The sharing SDK requests the activity sharing password from the sharing server. If it is still within the validity period of the limited-time activity, the sharing server generates the activity sharing password based on the activity sharing text, the live room identifier, and the sharing user identifier and returns it to the sharing SDK. The sharing SDK returns the activity sharing password to the live streaming client. The live streaming client can paste the activity sharing password into the selected sharing channel (such as a social app). (The shared user can copy the activity sharing password and open the live streaming platform to jump to the activity page or the activity live room. Based on the sharing user identifier in the activity sharing password, the successful sharing behavior can be attributed to the sharing initiator user, and a corresponding reward can be issued to them.) If the sharing server detects that the limited-time activity has ended, it can generate a general sharing password based on the live room sharing text, the live room identifier, and the sharing user identifier and return it to the sharing SDK. The sharing SDK returns the general sharing password to the live streaming client. The live streaming client can display the general sharing password in the selected sharing channel. (The shared user can copy the general sharing password and open the live streaming platform to jump to the regular live room to watch the live streaming content.)

[0075] Step 220: Query the valid activity period of the limited-time activity based on the sharing entry identifier. In some embodiments, step 220 can be implemented by the activity query module 1020.

[0076] In some embodiments, if only one limited-time event exists within the same time period, the sharing server can determine that the event sharing request was triggered by the limited-time event sharing entry based on the sharing entry identifier, and can directly query the valid event period of the limited-time event. In some embodiments, the sharing server can store the correspondence between limited-time events and sharing entry identifiers (the relationship between limited-time events and sharing entry identifiers can be one-to-many), and store the valid event period of the limited-time event. Based on the sharing entry identifier, the sharing server can query the corresponding limited-time event, and then query the valid event period of that limited-time event.

[0077] In some embodiments, if multiple different limited-time events exist within the same time period, or if the valid activity periods of multiple limited-time events overlap, the sharing server can store the correspondence between each limited-time event and the sharing entry identifier (each limited-time event can have a one-to-many relationship with its corresponding sharing entry identifier), and store the valid activity period of each limited-time event. In some embodiments, the sharing server can determine the corresponding limited-time event based on the sharing entry identifier, and then query the valid activity period of that limited-time event.

[0078] Step 230: When it is detected that the limited-time event has ended, the sharing information is fed back according to a predetermined degradation method. The predetermined degradation method is used to downgrade the event sharing of the target live broadcast room to a general sharing of the target live broadcast room. The sharing information is associated with the live broadcast room identifier and the sharing user identifier. In some embodiments, step 230 can be implemented by the information feedback module 1030.

[0079] In some embodiments, the shared information may include an empty sharing code generated based on a first error code. In some embodiments, step 230 may further include: when it is detected that the timed event has ended, a first error code is fed back through a first link. The first error code is used to indicate the return of an empty sharing code. The empty sharing code is used to trigger the client to automatically switch to a second link to resend the first sharing request to obtain a generic sharing image of the target live room. The generic sharing image is associated with the live room identifier and the sharing user identifier. The second link is a generic image sharing path associated with the target live room.

[0080] In some embodiments, the semantics of the first error code can be represented as "the event has ended". The sharing server, based on the source tag, transmits the first error code (e.g., 110007) to the live streaming server through the first link to notify the live streaming server that the event has ended. Then, the live streaming server returns an empty sharing code (the sharing code field is empty or 0) to the live streaming client. In some embodiments, the live streaming server does not directly forward the first error code, but returns an empty sharing code. This allows the live streaming client to only execute the logic of triggering link switching and degradation based on the empty sharing code, without needing to understand the semantics of the first error code. This facilitates the live streaming server's later expansion to return an empty sharing code based on other abnormal situations (e.g., the user does not meet the event eligibility requirements, the event is urgently taken offline, etc.), without requiring additional functional upgrades to the live streaming client.

[0081] In some embodiments, the sharing code can be obtained based on the live stream identifier and the sharing user identifier. In some embodiments, for normal activity sharing during the valid activity period of a limited-time event, the sharing server can obtain the activity sharing code based on the live stream identifier and the sharing user identifier, and then return the activity sharing code to the live stream server through the first link. The live stream server combines the relevant elements of the activity live stream to assemble a complete material, and finally, when the live stream server returns it to the live stream client, the sharing code field can correspond to the image of the activity sharing code. In some embodiments, the sharing code can be in the form of a graphic code such as a QR code or a barcode.

[0082] In some embodiments, using an empty sharing code instead of an error message as the degradation signal to trigger the live streaming client to switch links makes the entire degradation switching process transparent to the user, allowing the live streaming client to automatically switch links without the user's awareness. In some embodiments, when the live streaming client receives an empty sharing code, it can automatically switch to the second link (the common sharing link in the live streaming room) and resend the first sharing request, in conjunction with reference to [reference needed]. Figure 6 , Figure 6 This is a schematic diagram of a second link for sharing images in a live streaming room, as shown in some embodiments of this specification. Figure 6 As shown, in the second link 600, the live streaming client can send a first sharing request through the sharing SDK. The sharing SDK requests a general sharing image of the target live streaming room from the sharing server. Since the second link is a general sharing link for the live streaming room, the sharing server does not need to make any judgments about the limited-time event. It can directly obtain the general sharing code based on the live streaming room identifier and the sharing user identifier encoding in the first sharing request. Since the general sharing image also requires relevant elements of the live streaming room, the sharing server needs to retrieve the relevant elements of the live streaming room from the live streaming server and synthesize them with the general sharing code to obtain the general sharing image. The sharing server returns the synthesized general sharing image to the sharing SDK. The sharing SDK returns the general sharing image to the live streaming client, and the live streaming client renders and displays the general sharing image.

[0083] In some embodiments, for event-shared images or general-shared images, the live streaming client responds to an image storage instruction and stores the image locally for pasting or sending within the selected sharing channel. In some embodiments, for event-shared images, the recipient can scan the event sharing code in the event-shared image to be redirected to the corresponding event page or event live stream room. In some embodiments, for general-shared images, the recipient can scan the general sharing code in the general-shared image to be redirected to the corresponding regular live stream room to watch the live stream.

[0084] In some embodiments, the sharing information may include a live stream sharing link. In some embodiments, step 230 may further include: when it is detected that the time-limited event has ended, generating a universal sharing link for the target live stream based on the live stream identifier and the sharing user identifier, and returning the universal sharing link through a third link.

[0085] In some embodiments, a link can refer to a string conforming to the URL (Uniform Resource Locator) specification, allowing users to directly access specific online resources (such as live stream pages, event pages, etc.) by clicking or copying the link. Shared links are a common form of live stream sharing; they can be dynamically generated by the sharing server and presented as clickable card messages on third-party social platforms. In some embodiments, event shared links can be used to access event live stream pages or event pages, while general shared links can be used to access regular live stream pages.

[0086] In some embodiments, for a second sharing request of the link type, the sharing server can perform internal downgrading based on the detection result that the time-limited activity has ended, that is, the sharing server generates a general sharing link and returns it after the time-limited activity has ended.

[0087] In some embodiments, the sharing information may include a live stream sharing password. In some embodiments, step 230 may further include: when it is detected that the time-limited event has ended, generating a universal sharing password for the target live stream based on the live stream sharing text, the live stream identifier, and the sharing user identifier, and returning the universal sharing password through the fourth link.

[0088] In some embodiments, a password refers to a plain text string with a specific format identifier. The sharing user can share it by copying and pasting. The receiving user can copy the password and open the corresponding client. The client automatically recognizes the password content by reading the clipboard, parses out the activity information or live stream information contained within, and then redirects to the activity page or live stream page. In some embodiments, the password may use a pair of special symbols (such as #, ¥, $, etc.) as start and end markers so that the client can quickly recognize it. In some embodiments, the password may also include specific text to introduce the function or content corresponding to the password. In some embodiments, the activity sharing password for the target live stream may include activity sharing text (e.g., "Open the live stream and join the lucky draw activity!"). In some embodiments, the general sharing password for the target live stream may include live stream sharing text (e.g., "XXX is live streaming, watch the exciting live stream content with me!").

[0089] In some embodiments, for a third-party sharing request of the password type, if the sharing server detects that the limited-time event is still in effect and the target live stream is the event's live stream, the sharing server can generate an event sharing password based on the event sharing text, the live stream identifier, and the sharing user identifier. The user being shared with can copy the event sharing password and open the live stream platform to be redirected to the event's live stream or event page. In some embodiments, for a third-party sharing request of the password type, if the sharing server detects that the limited-time event has ended, the sharing server can perform internal downgrading based on the detection result that the limited-time event has ended. That is, the sharing server can generate a general sharing password and return it based on the live stream sharing text, the live stream identifier, and the sharing user identifier after the limited-time event has ended.

[0090] In some embodiments, some live streaming rooms may not be eligible to initiate activity sharing (non-activity live streaming rooms). Such sharing requests are different from the abnormal situation of the end of the activity, and the sharing server can provide different information based on different abnormal situations. Figure 7 This is an exemplary flowchart illustrating a non-activity live stream sharing during an activity, according to some embodiments of this specification. Figure 7 The process 700 shown can be executed by a processing device, for example, by... Figure 1 The server 110 shown is executed. In some embodiments, such as Figure 7 As shown, process 700 may include the following steps.

[0091] Step 710: When it is detected that the limited-time event is still valid, query whether the target live room belongs to the event live room corresponding to the limited-time event based on the live room identifier; the limited-time event is participated in by at least one event live room.

[0092] In some embodiments, due to abnormal situations such as cached data lag (e.g., switching from an event live stream to a regular live stream but the event parameters are not updated, and the client still initiates an event sharing request), malicious attacks (e.g., intercepting event sharing requests and replacing the live stream identifier), and violations (e.g., maliciously using functional code to inflate event rewards), the live stream corresponding to the event sharing request may not be an event live stream. The sharing server can query whether the live stream belongs to the event live stream based on the live stream identifier in the event sharing request. In some embodiments, the sharing server can store the correspondence between limited-time events and the live streams participating in the limited-time events. For example, it can store the event identifier corresponding to at least one live stream identifier. The sharing server can query whether the live stream is in the list of live stream identifiers that correspond to the limited-time event based on the live stream identifier to determine whether the live stream is an event live stream.

[0093] Step 720: If the target live stream room is not part of the event live stream room, a second error code will be returned. The second error code is used to indicate that the sharing has been rejected and to terminate the sharing process.

[0094] In some embodiments, the semantics of the second error code can be represented as "illegal request / share rejected". When the sharing server detects that the target live room does not belong to the active live room, it returns the second error code (e.g., 110000) to trigger the live client to display a message indicating that the share has been rejected. In some embodiments, for a first share request of image type, the sharing server can feed back the second error code to the live server through the first link (active share link), and the live server will then pass the second error code to the live client. In some embodiments, for a second share request of link type or a third share request of password type, the sharing server can feed back the second error code directly to the live client through the sharing SDK.

[0095] In some embodiments, system anomalies may occur during the validity period of a limited-time event. These anomalies differ from those occurring when the event ends or when there are no events in the live stream. If the sharing server directly downgrades the process, users may mistakenly believe they have successfully shared the event when they have not actually participated. If the sharing server directly rejects the sharing, it will negatively impact the user's experience. The sharing server can provide different feedback depending on the specific anomaly. In some embodiments, the live stream sharing method may further include: when the limited-time event is still valid, if a system anomaly occurs, a third error code is fed back. This third error code indicates the anomaly and guides a retry. System anomalies include at least one of request timeout and system error.

[0096] In some embodiments, the semantics of the third error code can be represented as "system exception". When the sharing server encounters an exception such as a response timeout or system error at a certain link in the activity sharing link, since the failure of the intermediate link during the valid activity is usually short-lived, in order to avoid the user losing the activity participation experience due to the user's imperceptible sharing degradation when the system exception occurs during the valid activity period (in the case of imperceptible degradation, the user thinks that he / she has successfully shared the activity, but actually shared the live room, so the successful sharing behavior cannot add the corresponding reward to the sharing user), for the system exception, the sharing server can return a third error code with specific semantics (for example, -504 specifically indicates system timeout, -500 generally indicates system exception) to trigger the live client to display the prompt "Sharing exception, please try again". In some embodiments, for the first sharing request of image type, the sharing server can return the third error code to the live server through the first link (activity sharing link), and the live server will pass the third error code to the live client. In some embodiments, for a first sharing request of image type, the sharing server can send a third error code to the live streaming server via a first link. The live streaming server can then send a system error message to the live streaming client based on the third error code. The live streaming client can then display controls guiding the user to retry based on the system error message. In some embodiments, for a second sharing request of link type or a third sharing request of password type, the sharing server can send the third error code directly to the live streaming client via the sharing SDK.

[0097] In some embodiments, the sharing server returns multiple semantically clear error codes based on different processing results of the activity sharing request. The live streaming server and / or live streaming client can execute differentiated response logic based on different error codes. In some embodiments, setting different error codes can effectively distinguish between abnormal situations with different semantics, thereby enabling more targeted handling measures. For other possible abnormal situations, new error codes can also be added for differentiation.

[0098] In some embodiments, if a normal activity sharing request during the validity period of a limited-time activity encounters an anomaly, the user can be guided to retry in order to avoid failure to participate in the activity. However, if the normal activity sharing request continues to encounter anomalies, in order to avoid the user constantly retrying but failing to share, thus affecting the user's sharing experience, an adaptive degradation can be implemented based on the persistence of the anomaly. Figure 8 This is an exemplary flowchart illustrating an adaptive degradation based on error rate feedback during an activity, according to some embodiments of this specification. Figure 8 The process 800 shown can be executed by a processing device, for example, by... Figure 1 The server 110 shown is executed. In some embodiments, such as Figure 8 As shown, process 800 may include the following steps.

[0099] Step 810: During the valid activity period of the limited-time activity, obtain the response information associated with the activity sharing request. The response information includes at least the response time and the response result.

[0100] In some embodiments, during the effective period of a time-limited activity, to ensure a good user experience, the response information of the activity sharing request can be monitored. In some embodiments, the response time can refer to the time taken by the sharing server from receiving the activity sharing request to providing feedback on the sharing information. If the response time exceeds a preset response duration threshold, it can be determined as a response timeout. In some embodiments, the response result can refer to the sharing information provided by the sharing server (e.g., error codes with different semantics for different abnormal situations).

[0101] Step 820: Determine the percentage of requests that returned a third error code within the sliding time window relative to the total number of requests.

[0102] In some embodiments, since the sharing server can return semantically distinct and clearly defined error codes for different processing results of activity sharing requests, the sharing server can separately count the number of requests corresponding to the third error code in system abnormal situations.

[0103] In some embodiments, a sliding time window can divide the timeline into multiple consecutive, fixed-length time periods (windows). Each window slides forward continuously as real time passes, and can be used to statistically analyze data from a recent period. Because the sliding time window is dynamic, the total number of requests and the number of requests for the third error code also change dynamically, and the error ratio also changes dynamically over time. In some embodiments, the sliding time window can be set to 1 minute.

[0104] Step 830: If the error ratios corresponding to a predetermined number of consecutive sliding time windows all exceed the ratio threshold, then for the received activity sharing request, the sharing information is fed back according to the predetermined degradation method.

[0105] In some embodiments, if the sliding time window moves by seconds, with one time window corresponding to each second, and the error ratio for a predetermined number of consecutive sliding time windows exceeds a threshold, it indicates that the system error has persisted for a predetermined number of seconds, reflecting that the system anomaly may be an unrecoverable failure. If the user is still guided to repeatedly retry based on the third error code, the user will still be unable to share successfully after multiple retries, which may affect the sharing experience. Therefore, when the system anomaly is severe, the activity sharing can be downgraded to a general sharing in the live stream according to a predetermined degradation method, prioritizing the user's ability to successfully complete the sharing operation. In some embodiments, since the sliding time window is dynamically sliding, the error ratio also changes dynamically as the sliding time window slides. When the error ratio falls below the threshold in subsequent statistical processes, it indicates that the system anomaly may have been alleviated or recovered. At this time, it is not necessary to provide sharing information according to the predetermined degradation method; the user can still be guided to retry to ensure the user's activity participation experience. Dynamic adaptive adjustment between guided retry and automatic degradation can be implemented based on the system anomaly situation.

[0106] In some embodiments, the sliding step size (interval duration) of two adjacent sliding time windows can be determined comprehensively based on factors such as actual computing performance and network performance, for example, it can be set to 1 second, 10 seconds, 30 seconds, 1 minute, etc.

[0107] In some embodiments, this specification also provides a method for sharing a live streaming room. Figure 9 This is an exemplary flowchart illustrating another live streaming sharing method according to some embodiments of this specification. Figure 9 The process 900 shown can be executed by a terminal device, for example, by... Figure 1 The client 120 shown executes the process. In some embodiments, process 900 can be implemented by a live streaming sharing device 1100 deployed on a terminal device. The live streaming sharing device 1100 may include a request generation module 1110, a request sending module 1120, and an information receiving module 1130. In some embodiments, such as Figure 9 As shown, process 900 may include the following steps.

[0108] Step 910: When the limited-time activity sharing entry of the target live stream is triggered, an activity sharing request is generated based on the live stream identifier, the sharing user identifier, and the sharing entry identifier. The live stream identifier identifies the target live stream, the sharing user identifier identifies the user initiating the activity sharing request, and the sharing entry identifier identifies the limited-time activity sharing entry. In some embodiments, step 910 can be implemented by the request generation module 1110.

[0109] In some embodiments, the live streaming client can display a limited-time event sharing entry in the sharing channel list of the target live streaming room. Users can generate an event sharing instruction by triggering the limited-time event sharing entry. After receiving the event sharing instruction, the live streaming client can generate an event sharing request based on the live streaming room identifier, the sharing user identifier, and the sharing entry identifier. For a detailed explanation of the limited-time event sharing entry, the live streaming room identifier, the sharing user identifier, and the sharing entry identifier, please refer to the relevant description in step 210 above, which will not be repeated here.

[0110] Step 920: Send an activity sharing request; the activity sharing request is used to trigger a query of the valid activity period of the time-limited activity based on the sharing entry identifier. In some embodiments, step 920 can be implemented by the request sending module 1120.

[0111] In some embodiments, the activity sharing request can be sent directly from the live streaming client to the sharing server via the sharing SDK. In other embodiments, the activity sharing request can be sent from the live streaming client to the live streaming server, which then forwards it to the sharing server. For an explanation of the activity sharing request and its transmission process, please refer to the relevant descriptions of steps 210 and 220 above, which will not be repeated here.

[0112] In some embodiments, the activity sharing request includes a first sharing request of image type. In some embodiments, step 920 may further include: sending the first sharing request via a first link; the first sharing request carries a source marker during transmission via the first link, the source marker indicating that the sharing information is returned via the first link; the first link is an activity image sharing path associated with the target live streaming room. Refer to the foregoing for information on the first link. Figure 3 The relevant explanations will not be repeated here.

[0113] In some embodiments, the activity sharing request includes a second sharing request of the link type. In some embodiments, step 920 may further include: sending the second sharing request via a third link; the third link is an activity and / or general link sharing path associated with the target live stream room. Refer to the foregoing for information on the third link. Figure 4 The relevant explanations will not be repeated here.

[0114] In some embodiments, the activity sharing request includes a third sharing request of the password type. In some embodiments, step 920 may further include: sending the third sharing request via a fourth link; the fourth link is an activity and / or general password sharing path associated with the target live streaming room. Refer to the foregoing for information on the fourth link. Figure 5 The relevant explanations will not be repeated here.

[0115] Step 930: Receive feedback sharing information, which is associated with the live stream identifier and the sharing user identifier; the sharing information is obtained according to a predetermined downgrade method when it is detected that the limited-time event has ended; the predetermined downgrade method is used to downgrade the activity sharing of the target live stream to the general sharing of the target live stream. In some embodiments, step 930 can be implemented by the information receiving module 1130.

[0116] In some embodiments, the shared information includes an empty sharing code generated based on a first error code. In some embodiments, step 930 may further include: receiving the empty sharing code generated based on the first error code via a first link; automatically switching to a second link to resend the first sharing request based on the empty sharing code; the first error code being fed back when it is detected that the timed activity has ended; the second link being a generic image sharing path associated with the target live stream room; receiving a generic sharing image of the target live stream room fed back via the second link, the generic sharing image being associated with the live stream room identifier and the sharing user identifier. For details on the second link, please refer to the foregoing. Figure 6 For related explanations, please refer to the explanations regarding image sharing in step 230 above. They will not be repeated here.

[0117] In some embodiments, the shared information includes a live stream sharing link. In some embodiments, step 930 may further include: receiving a generic sharing link for the target live stream via a third link; the generic sharing link is generated based on the live stream identifier and the sharing user identifier when it is detected that the timed event has ended. For details regarding the generic sharing link, please refer to the relevant explanation of link sharing in step 230 above, which will not be repeated here.

[0118] In some embodiments, the shared information includes a live stream sharing password. In some embodiments, step 930 may further include: receiving a universal sharing password for the target live stream via a fourth link. The universal sharing password is generated based on the live stream sharing text, the live stream identifier, and the sharing user identifier when it is detected that the timed event has ended. For details regarding the universal sharing password, please refer to the relevant explanation regarding password sharing in step 230 above; it will not be repeated here.

[0119] This manual also provides a live streaming sharing device. Figure 10 This is an exemplary block diagram of a live streaming room sharing device according to some embodiments of this specification. In some embodiments, the live streaming room sharing device 1000 may be deployed on a server 110. Figure 10 As shown, in some embodiments, the live streaming sharing device 1000 may include a request receiving module 1010, an activity query module 1020, and an information feedback module 1030.

[0120] In some embodiments, the request receiving module 1010 can be used to receive an activity sharing request. The activity sharing request is generated when the time-limited activity sharing entry of the target live room is triggered. The activity sharing request includes a live room identifier, a sharing user identifier, and a sharing entry identifier. The live room identifier is used to identify the target live room, the sharing user identifier is used to identify the user who initiated the activity sharing request, and the sharing entry identifier is used to identify the time-limited activity sharing entry.

[0121] In some embodiments, the activity sharing request includes a first sharing request of the image type. In some embodiments, the request receiving module 1010 can also be used to receive the first sharing request transmitted by the client through the first link; the first sharing request carries a source mark during transmission through the first link, the source mark being used to indicate that the sharing information is returned through the first link; the first link is an activity image sharing path associated with the target live streaming room.

[0122] In some embodiments, the activity sharing request includes a second sharing request of the link type. In some embodiments, the request receiving module 1010 can also be used to receive the second sharing request transmitted by the client through a third link; the third link is an activity and / or general link sharing path associated with the target live room.

[0123] In some embodiments, the activity sharing request includes a third sharing request of the password type. In some embodiments, the request receiving module 1010 can also be used to receive a third sharing request transmitted by the client through a fourth link; the fourth link is an activity and / or general password sharing path associated with the target live room.

[0124] In some embodiments, the activity query module 1020 can be used to query the valid activity period of a time-limited activity based on the sharing entry identifier.

[0125] In some embodiments, the information feedback module 1030 can be used to provide feedback on sharing information according to a predetermined degradation method when it is detected that the time-limited activity has ended. The predetermined degradation method is used to downgrade the activity sharing of the target live room to the general sharing of the target live room. The sharing information is associated with the live room identifier and the sharing user identifier.

[0126] In some embodiments, the shared information includes an empty sharing code generated based on a first error code. In some embodiments, the information feedback module 1030 can also be used to, when detecting that a timed event has ended, feed back a first error code through a first link. The first error code is used to indicate the return of an empty sharing code. The empty sharing code is used to trigger the client to automatically switch to a second link to resend the first sharing request in order to obtain a generic sharing image for the target live stream. The generic sharing image is associated with the live stream identifier and the sharing user identifier. The second link is a generic image sharing path associated with the target live stream.

[0127] In some embodiments, the shared information includes a live stream sharing link. In some embodiments, the information feedback module 1030 can also be used to generate a universal sharing link for the target live stream based on the live stream identifier and the sharing user identifier when it is detected that the time-limited event has ended, and the universal sharing link is returned through a third link.

[0128] In some embodiments, the shared information includes a live stream sharing password. In some embodiments, the information feedback module 1030 can also be used to generate a universal sharing password for the target live stream based on the live stream sharing text, the live stream identifier, and the sharing user identifier when it is detected that the time-limited activity has ended. The universal sharing password is returned through the fourth link.

[0129] This manual also provides another live streaming sharing device. Figure 11 This is an exemplary block diagram of another live streaming room sharing device according to some embodiments of this specification. In some embodiments, the live streaming room sharing device 1100 may be deployed on the client 120. Figure 11 As shown, in some embodiments, the live streaming sharing device 1100 may include a request generation module 1110, a request sending module 1120, and an information receiving module 1130.

[0130] In some embodiments, the request generation module 1110 can be used to generate an activity sharing request based on the live room identifier, the sharing user identifier, and the sharing entry identifier when the limited-time activity sharing entry of the target live room is triggered; the live room identifier is used to identify the target live room, the sharing user identifier is used to identify the user who initiates the activity sharing request, and the sharing entry identifier is used to identify the limited-time activity sharing entry.

[0131] In some embodiments, the request sending module 1120 can be used to send an activity sharing request; the activity sharing request is used to trigger a query of the valid activity period of a time-limited activity based on the sharing entry identifier.

[0132] In some embodiments, the activity sharing request includes a first sharing request of the image type. In some embodiments, the request sending module 1120 can also be used to send the first sharing request through a first link; the first sharing request carries a source mark during transmission through the first link, the source mark being used to indicate that the sharing information is returned through the first link; the first link is an activity image sharing path associated with the target live streaming room.

[0133] In some embodiments, the activity sharing request includes a second sharing request of the link type. In some embodiments, the request sending module 1120 can also be used to send the second sharing request via a third link; the third link is an activity and / or general link sharing path associated with the target live room.

[0134] In some embodiments, the activity sharing request includes a third sharing request of the password type. In some embodiments, the request sending module 1120 can also be used to send the third sharing request via a fourth link; the fourth link is an activity and / or general password sharing path associated with the target live room.

[0135] In some embodiments, the information receiving module 1130 can be used to receive feedback sharing information, which is associated with the live room identifier and the sharing user identifier; the sharing information is obtained according to a predetermined degradation method when it is detected that the time-limited activity has ended; the predetermined degradation method is used to downgrade the activity sharing of the target live room to the general sharing of the target live room.

[0136] In some embodiments, the shared information includes an empty sharing code generated based on a first error code. In some embodiments, the information receiving module 1130 can also be configured to receive the empty sharing code generated based on the first error code via a first link, and automatically switch to a second link to resend the first sharing request based on the empty sharing code; the first error code is fed back when it is detected that the timed event has ended; the second link is a general image sharing path associated with the target live room; and receive a general sharing image of the target live room fed back via the second link, the general sharing image being associated with the live room identifier and the sharing user identifier.

[0137] In some embodiments, the shared information includes a live stream sharing link. In some embodiments, the information receiving module 1130 can also be used to receive a general sharing link of the target live stream via a third link; the general sharing link is generated based on the live stream identifier and the sharing user identifier when it is detected that the timed event has ended.

[0138] In some embodiments, the shared information includes a live room sharing password. In some embodiments, the information receiving module 1130 can also be used to receive a universal sharing password for the target live room via a fourth link. The universal sharing password is generated based on the live room sharing text, the live room identifier, and the sharing user identifier when it is detected that the timed event has ended.

[0139] This manual also provides a live streaming sharing system. Figure 12 This is an exemplary block diagram of a live streaming sharing system according to some embodiments of this specification. Figure 12As shown, the live streaming sharing system 1200 may include a server 1210 and a client 1220. In some embodiments, the server 1210 may be the server 110 in application scenario 100, and the client 1220 may be the client 120 in application scenario 100. In some embodiments, the server 1210 may include a sharing server. In some embodiments, the server 1210 may also include a live streaming server. In some embodiments, the sharing server and the live streaming server are functionally independent. In some embodiments, the sharing server and the live streaming server may be implemented with independent functions by different processing devices. In some embodiments, the sharing server and the live streaming server may be implemented by the same processing device, that is, one processing device can be used as a sharing server or as a live streaming server.

[0140] In some embodiments, the client 1220 can be used to generate an activity sharing request based on the live room identifier, the sharing user identifier, and the sharing entry identifier when the limited-time activity sharing entry of the target live room is triggered, and send the activity sharing request to the server 1210 and receive the sharing information fed back by the server 1210; the live room identifier is used to identify the target live room, the sharing user identifier is used to identify the user who initiates the activity sharing request, and the sharing entry identifier is used to identify the limited-time activity sharing entry.

[0141] Server 1210 can be used to receive activity sharing requests, query the valid activity period of the limited-time activity based on the sharing entry identifier, and when it is detected that the limited-time activity has ended, it will feed back the sharing information to client 1220 according to the predetermined degradation method. The predetermined degradation method is used to downgrade the activity sharing of the target live room to the general sharing of the target live room, and the sharing information is associated with the live room identifier and the sharing user identifier.

[0142] For more information on each module, please refer to [link / reference]. Figures 2 to 9 The relevant explanations will not be repeated here. It should be understood that... Figures 10 to 12The systems and modules shown can be implemented in various ways. For example, in some embodiments, the systems and modules can be implemented by hardware, software, or a combination of both. The hardware portion can be implemented using dedicated logic; the software portion can be stored in memory and executed by an appropriate instruction execution system, such as a microprocessor or dedicated-design hardware. Those skilled in the art will understand that the methods and systems described above can be implemented using computer-executable instructions and / or included in the control code of a processor, such as on a media such as a disk, CD, or DVD-ROM, or in the memory of a programmable device. The systems and modules of this specification can be implemented not only by hardware circuits such as very large-scale integrated circuits or gate arrays, semiconductors such as logic chips and transistors, or programmable hardware devices such as field-programmable gate arrays and programmable logic devices, but also by software, for example, executed by various types of processors, or by a combination of the aforementioned hardware circuits and software (e.g., firmware).

[0143] It should be noted that the above description of the system and its modules is for convenience only and should not be construed as limiting this specification to the embodiments described. It is understood that those skilled in the art, after understanding the principles of this system, may arbitrarily combine the various modules without departing from these principles to form subsystems connected to other modules. Alternatively, some modules may be split to obtain more modules or multiple units under a single module. Such modifications are all within the scope of this specification.

[0144] Some embodiments of this specification also provide a computer device, which includes a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, it can implement this specification. Figures 2 to 9 The method for sharing the live stream is shown.

[0145] Some embodiments of this specification also provide a computer-readable storage medium storing computer instructions that, when executed by a processor, can implement this specification. Figures 2 to 9 The method for sharing the live stream is shown.

[0146] Some embodiments of this specification also provide a computer program product, including a computer program that, when at least a portion of the computer program is executed by a processor, can implement this specification. Figures 2 to 9The live streaming sharing method is illustrated. In some embodiments, the computer program product may only involve a computer program, which may be carried on a storage medium or a processing device. In other embodiments, the computer program product may also be a storage medium or a processing device containing the aforementioned computer program. The processing device may include one or more processors, and the storage medium.

[0147] In some embodiments, the processor may be a combination of one or more of the following processors: central processing unit (CPU), application-specific integrated circuit (ASIC), application-specific instruction set processor (ASIP), graphics processing unit (GPU), physical processing unit (PPU), digital signal processor (DSP), field-programmable gate array (FPGA), programmable logic device (PLD), programmable logic controller (PLC), reduced instruction set computer (RISC), and microprocessor.

[0148] In some embodiments, the storage medium may include one or more combinations of the following: mass storage, removable storage, volatile read-write memory, and read-only memory (ROM). Exemplary mass storage may include disks, optical disks, solid-state drives, etc. Exemplary removable storage may include flash drives, floppy disks, optical disks, memory cards, compressed hard disks, magnetic tapes, etc. Exemplary volatile read-write memory may include random access memory (RAM). Exemplary RAM may include dynamic random access memory (DRAM), dual data rate synchronous dynamic random access memory (DDRSDRAM), static random access memory (SRAM), silicon controlled retrieval memory (T-RAM), and zero-capacitance memory (Z-RAM), etc. Exemplary read-only memory may include masked read-only memory (MROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), compressed hard disk read-only memory (CD-ROM), and digital multifunction hard disk read-only memory, etc.

[0149] The basic concepts have been described above. It is obvious that the detailed disclosure above is merely illustrative and does not constitute a limitation of this specification. Although not explicitly stated herein, various modifications, improvements, and corrections may be made to this specification by those skilled in the art. Such modifications, improvements, and corrections are taught in this specification and therefore remain within the spirit and scope of the exemplary embodiments described herein.

Claims

1. A method for sharing live stream content, characterized in that, The method includes: Receive an activity sharing request; the activity sharing request is generated when the limited-time activity sharing entry of the target live room is triggered, the activity sharing request includes a live room identifier, a sharing user identifier, and a sharing entry identifier, the live room identifier is used to identify the target live room, the sharing user identifier is used to identify the user who initiated the activity sharing request, and the sharing entry identifier is used to identify the limited-time activity sharing entry; Based on the shared entry identifier, query the valid activity period of the limited-time event; When it is detected that the limited-time event has ended, the sharing information is fed back according to the predetermined downgrade method. The predetermined downgrade method is used to downgrade the event sharing of the target live room to the general sharing of the target live room. The sharing information is associated with the live room identifier and the sharing user identifier.

2. The method according to claim 1, characterized in that, The activity sharing request includes a first sharing request of image type; The shared information includes an empty sharing code generated based on the first error code; The receiving of activity sharing requests includes: The system receives the first sharing request transmitted by the client through the first link; the first sharing request carries a source marker during transmission through the first link, the source marker indicating that the sharing information is returned through the first link; the first link is an activity image sharing path associated with the target live streaming room; When it is detected that the time-limited activity has ended, the sharing information is fed back according to the predetermined downgrade method, including: When it is detected that the time-limited event has ended, the first error code is fed back through the first link. The first error code is used to indicate the return of the empty sharing code. The empty sharing code is used to trigger the client to automatically switch to the second link to resend the first sharing request in order to obtain the general sharing image of the target live room. The general sharing image is associated with the live room identifier and the sharing user identifier. The second link is a general image sharing path associated with the target live room.

3. The method according to claim 1, characterized in that, The activity sharing request includes a second sharing request of the link type; the sharing information includes a live stream sharing link; The receiving of activity sharing requests includes: Receive the second sharing request transmitted by the client through a third link; the third link is an activity and / or general link sharing path associated with the target live room; When it is detected that the time-limited activity has ended, the sharing information is fed back according to the predetermined downgrade method, including: When it is detected that the time-limited event has ended, a universal sharing link for the target live stream is generated based on the live stream identifier and the sharing user identifier, and the universal sharing link is returned through the third link.

4. The method according to claim 1, characterized in that, The activity sharing request includes a third-party sharing request of the password type; the sharing information includes the live broadcast room sharing password; The receiving of activity sharing requests includes: Receive the third sharing request transmitted by the client through the fourth link; the fourth link is an activity and / or general password sharing path associated with the target live room; When it is detected that the time-limited activity has ended, the sharing information is fed back according to the predetermined downgrade method, including: When it is detected that the time-limited event has ended, a general sharing password for the target live room is generated based on the live room sharing text, the live room identifier, and the sharing user identifier. The general sharing password is returned through the fourth link.

5. The method according to any one of claims 1 to 4, characterized in that, The method further includes: When it is detected that the limited-time event is still valid, the target live stream room is queried based on the live stream room identifier to see whether it belongs to the activity live stream room corresponding to the limited-time event; the limited-time event is participated in by at least one of the activity live stream rooms. If the target live stream room does not belong to the activity live stream room, a second error code will be returned. The second error code is used to indicate that the sharing has been rejected.

6. The method according to any one of claims 1 to 5, characterized in that, The method further includes: If a system anomaly occurs while the timed activity is still valid, a third error code will be returned. The third error code is used to indicate that an anomaly has occurred and to guide a retry. The system anomaly includes at least one of request timeout and system error.

7. The method according to claim 6, characterized in that, The method further includes: During the valid activity period of the limited-time event, obtain response information associated with the activity sharing request, the response information including at least the response time and response result; Determine the percentage of requests that return the third error code within the sliding time window relative to the total number of requests; If the error ratios for a predetermined number of consecutive sliding time windows all exceed the ratio threshold, then for the received activity sharing request, the sharing information will be fed back according to the predetermined degradation method.

8. A method for sharing live stream content, characterized in that, The method includes: When the limited-time event sharing entry of the target live room is triggered, an event sharing request is generated based on the live room identifier, the sharing user identifier, and the sharing entry identifier; the live room identifier is used to identify the target live room, the sharing user identifier is used to identify the user who initiated the event sharing request, and the sharing entry identifier is used to identify the limited-time event sharing entry. Send the activity sharing request; the activity sharing request is used to trigger a query of the valid activity period of the limited-time activity based on the sharing entry identifier; The system receives feedback sharing information, which is associated with the live stream identifier and the sharing user identifier; the sharing information is obtained according to a predetermined downgrade method when it is detected that the limited-time event has ended; the predetermined downgrade method is used to downgrade the event sharing of the target live stream to the general sharing of the target live stream.

9. The method according to claim 8, characterized in that, The activity sharing request includes a first sharing request of image type; The shared information includes an empty sharing code generated based on the first error code; Sending the activity sharing request includes: The first sharing request is sent via the first link; the first sharing request carries a source marker during transmission via the first link, the source marker being used to indicate that the sharing information is returned via the first link; the first link is an activity image sharing path associated with the target live stream room; The shared information received in the feedback includes: The first link receives the empty sharing code generated based on the first error code, and automatically switches to the second link to resend the first sharing request based on the empty sharing code; the first error code is fed back when it is detected that the time-limited event has ended; the second link is a general image sharing path associated with the target live room; Receive a generic shareable image of the target live stream room fed back through the second link. The generic shareable image is associated with the live stream room identifier and the sharing user identifier.

10. The method according to claim 8, characterized in that, The activity sharing request includes a second sharing request of the link type; the sharing information includes a live stream sharing link; Sending the activity sharing request includes: The second sharing request is sent via a third link; the third link is an activity and / or general link sharing path associated with the target live stream room; The shared information received in the feedback includes: The general sharing link of the target live room is received through the third link; the general sharing link is generated based on the live room identifier and the sharing user identifier when it is detected that the time-limited event has ended.

11. The method according to claim 8, characterized in that, The activity sharing request includes a third-party sharing request of the password type; the sharing information includes the live broadcast room sharing password; Sending the activity sharing request includes: The third sharing request is sent via a fourth link; the fourth link is an activity and / or general password sharing path associated with the target live streaming room; The shared information received in the feedback includes: The universal sharing password for the target live room is received through the fourth link. The universal sharing password is generated based on the live room sharing text, the live room identifier, and the sharing user identifier when it is detected that the time-limited event has ended.

12. A live streaming sharing device, characterized in that, The device includes: The request receiving module is used to receive activity sharing requests. The activity sharing request is generated when the limited-time activity sharing entry of the target live room is triggered. The activity sharing request includes a live room identifier, a sharing user identifier, and a sharing entry identifier. The live room identifier is used to identify the target live room, the sharing user identifier is used to identify the user who initiated the activity sharing request, and the sharing entry identifier is used to identify the limited-time activity sharing entry. The activity query module is used to query the valid activity period of the limited-time activity based on the sharing entry identifier; The information feedback module is used to provide sharing information according to a predetermined downgrade method when it is detected that the time-limited event has ended. The predetermined downgrade method is used to downgrade the event sharing of the target live room to the general sharing of the target live room. The sharing information is associated with the live room identifier and the sharing user identifier.

13. A live streaming sharing device, characterized in that, The device includes: The request generation module is used to generate an activity sharing request based on the live room identifier, the sharing user identifier, and the sharing entry identifier when the limited-time activity sharing entry of the target live room is triggered; the live room identifier is used to identify the target live room, the sharing user identifier is used to identify the user who initiates the activity sharing request, and the sharing entry identifier is used to identify the limited-time activity sharing entry. The request sending module is used to send the activity sharing request; the activity sharing request is used to trigger a query of the valid activity period of the limited-time activity based on the sharing entry identifier; An information receiving module is used to receive feedback sharing information, which is associated with the live room identifier and the sharing user identifier; the sharing information is obtained according to a predetermined downgrade method when it is detected that the limited-time event has ended; the predetermined downgrade method is used to downgrade the event sharing of the target live room to the general sharing of the target live room.

14. A live streaming room sharing system, characterized in that, The system includes: a client and a server; The client is configured to generate an activity sharing request based on the live room identifier, the sharing user identifier, and the sharing entry identifier when the limited-time activity sharing entry of the target live room is triggered, and send the activity sharing request to the server and receive sharing information from the server; the live room identifier is used to identify the target live room, the sharing user identifier is used to identify the user who initiated the activity sharing request, and the sharing entry identifier is used to identify the limited-time activity sharing entry. The server is configured to receive the activity sharing request, query the valid activity period of the limited-time activity based on the sharing entry identifier, and when it is detected that the limited-time activity has ended, to return the sharing information to the client according to a predetermined degradation method; the predetermined degradation method is used to downgrade the activity sharing of the target live room to the general sharing of the target live room, and the sharing information is associated with the live room identifier and the sharing user identifier.

15. A computer device, characterized in that, The computer device includes a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein when the processor executes the computer program, it is able to implement the method as described in any one of claims 1 to 11.

16. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer instructions that, when executed by a processor, enable the implementation of the method as described in any one of claims 1 to 11.

17. A computer program product, characterized in that, It includes a computer program that, when at least a portion of the computer program is executed by a processor, enables the implementation of the method as described in any one of claims 1 to 11.

Images