Identifier generation method, identification method, special effect acquisition method, identification device, equipment and product

Abstract

The invention relates to a method, device, equipment and product for generating an identifier and identifying and obtaining a special effect. The method is performed by a first client and includes generating first user generated content (UGC) data captured by a first user using a special effect. The method further includes sending the first UGC data to a server. The method further includes receiving a first UGC identifier corresponding to the first UGC data from the server, wherein the first UGC identifier is used for identifying the first UGC data shot using the special effect.

Description

Methods, apparatus, equipment and products for generating identifiers and obtaining special effects. Technical Field

[0001] This disclosure relates to the field of computers, and more specifically to methods, apparatus, devices and products for generating identifiers and for identifying and obtaining special effects. Background Technology

[0002] Currently, the field of special effects is undergoing innovation and development, with custom special effects technology being widely used. Custom special effects technology allows users to unleash their creativity, uploading their own materials such as images and videos, and using the tools provided by the system to transform these materials into unique special effects. Each newly generated special effect has an independent resource package, and users can further adjust and optimize these effects according to their own needs.

[0003] Building upon custom effects technology, real-time social gameplay further expands the user's gaming and social experience. This feature combines the game effects artist ecosystem with desktop infrastructure, allowing game effects artists to utilize their expertise and tools to create a variety of fun and creative effects. Simultaneously, through real-time communication technology, users can seamlessly connect with other players and enjoy a smooth multiplayer or two-player interactive gaming experience. Summary of the Invention

[0004] In a first aspect of the embodiments of this disclosure, a method for identifying special effects is provided, the method being performed by a first client. The method includes generating first user-generated content (UGC) data captured by a first user using special effects. The method also includes sending the first UGC data to a server. Furthermore, the method includes receiving from the server a first UGC identifier corresponding to the first UGC data, the first UGC identifier being used to identify the first UGC data captured using special effects.

[0005] In a second aspect of the embodiments of this disclosure, a method for generating an identifier for special effects is provided, the method being performed by a server. The method includes receiving first user-generated content (UGC) data generated by a first user using special effects from a first client. The method further includes generating a first UGC identifier corresponding to the first UGC data, the first UGC identifier being used to identify the first UGC data captured using special effects. Furthermore, the method includes sending the first UGC identifier to the first client.

[0006] In a third aspect of the embodiments of this disclosure, a method for acquiring special effects is provided, the method being performed by a second client. The method includes sending to a server a first UGC identifier corresponding to first user-generated content (UGC) data, the first UGC data being generated by a user using special effects on the first client. The method also includes receiving UGC data from the server. Furthermore, the method includes rendering special effects based on the UGC data, wherein a second user uses special effects to capture second UGC data on the second client, and the second user interacts with the special effects on the second client based on the first UGC data and the second UGC data.

[0007] In a fourth aspect of the embodiments of this disclosure, an apparatus for identifying special effects is provided, the apparatus being deployed on a first client. The apparatus includes a UGC data generation module configured to generate first user-generated content (UGC) data captured by a first user using special effects. The apparatus also includes a UGC data transmission module configured to transmit the first UGC data to a server. Furthermore, the apparatus includes a UGC identifier receiving module configured to receive from the server a first UGC identifier corresponding to the first UGC data, the first UGC identifier being used to identify the first UGC data captured using special effects.

[0008] In a fifth aspect of the embodiments of this disclosure, an apparatus for generating an identifier for special effects is provided, the apparatus being deployed on a server. The apparatus includes a UGC data receiving module configured to receive first user-generated content (UGC) data generated by a first user using special effects from a first client. The apparatus also includes a UGC identifier generation module configured to generate a first UGC identifier corresponding to the first UGC data based on the first UGC data, the first UGC identifier being used to identify the first UGC data captured using special effects. Furthermore, the apparatus includes a UGC identifier sending module configured to send the first UGC identifier to the first client.

[0009] In a sixth aspect of the embodiments of this disclosure, an apparatus for acquiring special effects is provided, the apparatus being deployed on a third client. The apparatus includes a UGC identifier sending module configured to send a first UGC identifier corresponding to first user-generated content (UGC) data, which is generated by the first user using special effects to capture images on the first client. The apparatus also includes a UGC data receiving module configured to receive the first UGC data from the server. Furthermore, the apparatus includes a special effects rendering module configured to render special effects based on the first UGC data, wherein a second user uses special effects to capture second UGC data on the second client, and the second user interacts with the special effects on the second client based on the first and second UGC data.

[0010] In a seventh aspect of the embodiments of this disclosure, an electronic device is provided. The electronic device includes one or more processors; and a storage device for storing one or more programs, which, when executed by the one or more processors, cause the one or more processors to implement a method for identifying special effects. The method includes generating first user-generated content (UGC) data captured by a first user using special effects. The method also includes sending the first UGC data to a server. Furthermore, the method includes receiving from the server a first UGC identifier corresponding to the first UGC data, the first UGC identifier being used to identify the first UGC data captured using special effects.

[0011] In an eighth aspect of the embodiments of this disclosure, an electronic device is provided. The electronic device includes one or more processors; and a storage device for storing one or more programs, which, when executed by the one or more processors, cause the one or more processors to implement a method for generating an identifier for special effects. The method includes receiving first user-generated content (UGC) data generated by a first user using special effects from a first client. The method further includes generating a first UGC identifier corresponding to the first UGC data based on the first UGC data, the first UGC identifier being used to identify the first UGC data captured using special effects. Furthermore, the method includes sending the first UGC identifier to the first client.

[0012] In a ninth aspect of the embodiments of this disclosure, an electronic device is provided. The electronic device includes one or more processors; and a storage device for storing one or more programs, which, when executed by the one or more processors, cause the one or more processors to implement a method for acquiring special effects. The method includes sending to a server a first UGC identifier corresponding to first user-generated content (UGC) data, the first UGC data being generated by a first user using special effects to capture images on a first client. The method also includes receiving the first UGC data from the server. Furthermore, the method includes rendering special effects based on the first UGC data, a second user capturing second UGC data using special effects on a second client, and the second user interacting with special effects on the second client based on the first UGC data and the second UGC data.

[0013] In a tenth aspect of the embodiments of this disclosure, a computer program product is provided. The computer program product is tangibly stored on a non-transitory computer-readable medium and includes machine-executable instructions that, when executed, cause a machine to implement a method for identifying special effects. The method includes generating first user-generated content (UGC) data captured by a first user using special effects. The method also includes sending the first UGC data to a server. Furthermore, the method includes receiving from the server a first UGC identifier corresponding to the first UGC data, the first UGC identifier being used to identify the first UGC data captured using special effects.

[0014] In an eleventh aspect of the embodiments of this disclosure, a computer program product is provided. The computer program product is tangibly stored on a non-transitory computer-readable medium and includes machine-executable instructions that, when executed, cause a machine to implement a method for generating an identifier for special effects. The method includes receiving first user-generated content (UGC) data generated by a first user using special effects from a first client. The method further includes generating a first UGC identifier corresponding to the first UGC data based on the first UGC data, the first UGC identifier being used to identify the first UGC data captured using special effects. Furthermore, the method includes sending the first UGC identifier to the first client.

[0015] In a twelfth aspect of embodiments of this disclosure, a computer program product is provided. The computer program product is tangibly stored on a non-transitory computer-readable medium and includes machine-executable instructions that, when executed, cause a machine to implement a method for acquiring special effects. The method includes sending to a server a first UGC identifier corresponding to first user-generated content (UGC) data, the first UGC data being generated by a first user using special effects to capture images on a first client. The method also includes receiving the first UGC data from the server. Furthermore, the method includes rendering special effects based on the first UGC data, a second user capturing second UGC data using special effects on a second client, and the second user interacting with special effects on the second client based on the first and second UGC data.

[0016] The summary section is provided to present the chosen concepts in a simplified form, which will be further described in the detailed description below. The summary section is not intended to identify key or principal features of the claimed subject matter, nor is it intended to limit the scope of the claimed subject matter. Attached Figure Description

[0017] The above and other features, advantages, and aspects of the embodiments of this disclosure will become more apparent from the accompanying drawings and the following detailed description. In the drawings, the same or similar reference numerals denote the same or similar elements, wherein:

[0018] Figure 1 illustrates a schematic diagram of an example environment in which various embodiments of the present disclosure may be implemented;

[0019] Figure 2A shows a flowchart of a method for identifying special effects according to some embodiments of the present disclosure;

[0020] Figure 2B shows a flowchart of a method for generating special effects identifiers according to some embodiments of the present disclosure;

[0021] Figure 2C shows a flowchart of a method for obtaining special effects according to some embodiments of the present disclosure;

[0022] Figure 3 shows a timing diagram of generating user-generated content (UGC) identifiers according to some embodiments of the present disclosure;

[0023] Figure 4 shows a timing diagram of tracking using UGC identifiers according to some embodiments of the present disclosure;

[0024] Figure 5A shows a flowchart of a method for writing UGC data to a temporary resource folder from the effects side according to some embodiments of the present disclosure;

[0025] Figure 5B illustrates a schematic diagram of writing UGC data to a temporary resource folder according to some embodiments of the present disclosure;

[0026] Figure 6A shows a flowchart of a method for obtaining UGC data according to some embodiments of the present disclosure;

[0027] Figure 6B shows a schematic diagram of receiving UGC data according to some embodiments of the present disclosure;

[0028] Figure 7 illustrates a flowchart of a method for obtaining a UGC identifier on a client and writing the UGC identifier into a message according to some embodiments of the present disclosure;

[0029] Figure 8 shows a flowchart of a method for rendering special effects and user avatars based on UGC identifiers on a client-side according to some embodiments of the present disclosure;

[0030] Figure 9 illustrates a schematic diagram of the overall chain of generating UGC identifiers and rendering effects based on UGC identifiers according to some embodiments of the present disclosure;

[0031] Figure 10 shows a schematic diagram of the overall link of the server issuing UGC identifiers and UGC data according to some embodiments of the present disclosure;

[0032] Figure 11 shows a diagram illustrating the effect of a method for obtaining special effects according to some embodiments of the present disclosure;

[0033] Figure 12A shows a block diagram of an apparatus for identifying special effects according to some embodiments of the present disclosure;

[0034] Figure 12B shows a block diagram of an apparatus for generating special effects logos according to some embodiments of the present disclosure;

[0035] Figure 12C shows a block diagram of an apparatus for obtaining special effects according to some embodiments of the present disclosure; and

[0036] Figure 13 shows a block diagram of a device capable of implementing several embodiments of the present disclosure. Detailed Implementation

[0037] It is understood that all user-related data involved in this technical solution should be obtained and used only after authorization from the user. This means that if it is necessary to use a user's personal information in this technical solution, the user's explicit consent and authorization are required before obtaining this data; otherwise, no related data collection and use will be carried out. It should also be understood that when implementing this technical solution, relevant laws and regulations should be strictly followed in the process of data collection, use, and storage, and necessary technical measures should be taken to protect user data security and ensure the secure use of data.

[0038] It is understood that before using the technical solutions disclosed in the various embodiments of this disclosure, users should be informed of the types, scope of use, and usage scenarios of the personal information involved in this disclosure in an appropriate manner in accordance with relevant laws and regulations, and user authorization should be obtained.

[0039] For example, upon receiving a user's proactive request, a prompt message is sent to the user to explicitly inform them that the requested operation will require the acquisition and use of the user's personal information. This allows the user to independently choose whether to provide personal information to the software or hardware, such as the electronic device, application, server, or storage medium performing the operations of this disclosed technical solution, based on the prompt message.

[0040] As an optional but non-limiting implementation, in response to a user's active request, sending a prompt message to the user can be done via a pop-up window, where the prompt message can be presented in text format. Furthermore, the pop-up window can also include a selection control allowing the user to choose "agree" or "disagree" to provide personal information to the electronic device.

[0041] It is understood that the above notification and user authorization process are merely illustrative and do not constitute a limitation on the implementation of this disclosure. Other methods that comply with relevant laws and regulations may also be applied to the implementation of this disclosure.

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

[0043] In the description of embodiments of this disclosure, the term "comprising" and similar terms should be understood as open-ended inclusion, i.e., "including but not limited to". The term "based on" should be understood as "at least partially based on". The term "one embodiment" or "the embodiment" should be understood as "at least one embodiment". The terms "first", "second", etc., may refer to different or the same objects unless explicitly stated. Other explicit and implicit definitions may also be included below.

[0044] As mentioned above, custom effects technology can bring creativity to users, but it also has some drawbacks. Since each custom effect can potentially spawn multiple sub-effects, resulting in a large number of effect resource packs, this not only increases the system load but also makes it extremely difficult to aggregate user gameplay data. For example, with many different effects, and each effect having multiple versions and variations, the cost and resource consumption of managing these effects and resource packs are enormous.

[0045] Similarly, while real-time social gameplay offers a superior gaming and social experience, its implementation costs are relatively high. This is primarily due to the challenges of technology development and maintenance. Ensuring smooth and stable real-time communication requires significant resources to optimize network architecture and server performance.

[0046] To address this, this disclosure provides a method for generating identifiers and for identifying and acquiring special effects. First, when a user captures a video using special effects on one client, UGC data is acquired and sent to the server. The server then generates a UGC identifier based on the UGC data and sends it to the client. Once the UGC data is identified, another client can acquire the UGC data by sending the UGC identifier to the server, thus rendering special effects on the UGC data. This approach not only achieves intelligent management of special effects data and reduces system load, but also enables the aggregation of UGC data, thereby increasing the diversity of user gameplay data aggregation and fission methods, improving the utilization rate of special effects, and further enriching the user's gaming experience.

[0047] Figure 1 illustrates a schematic diagram of an example environment 100 in which various embodiments of the present disclosure may be implemented. As shown in Figure 1, the example environment 100 may include a client 103 (also referred to as a first client). The client 103 can display special effects 105 through various devices, such as smartphones, tablets, televisions, etc. The special effects 105 may be pre-stored locally on the client 103 or downloaded from a server 107. The client 103 can decode, render, and process the special effects, and finally present the special effects 105 to the user 101 (also referred to as the first user) in a visual manner. It should be understood that the special effects 105 are used to change or enhance media such as videos and images to provide users with a novel shooting experience and make the shooting works more unique. In the embodiments of the present disclosure, the special effects 105 may be a simple filter or a complex animation effect, and the present disclosure does not limit this. When the user 101 uses the special effects 105 to shoot, the client 103 will display the special effects 105 and apply them to the video or image that the user is shooting. For example, if user 101 selects a "face-changing" effect, then user 101's face will be replaced with another preset face image in real time during the shooting process.

[0048] In some embodiments, client 103 can acquire UGC data generated by user 101. UGC data refers to the data generated and recorded by user 101 when using special effects 105 on client 103, indicating the user's operations, behaviors, or results. UGC data may include image objects, trajectories, texture information, text information, and spatial information, etc. For example, when using the face-changing effect, the UGC data is the user's facial image or video processed by special effects 105. As another example, when user 101 uses special effects 105 to create artwork, the UGC data could be user 101's handwriting data.

[0049] As shown in Figure 1, after acquiring UGC data, client 103 sends the UGC data to server 107. Server 107 generates a UGC identifier based on the received UGC data. The UGC identifier is used to uniquely identify and distinguish each piece of UGC data. In some embodiments, server 107 can associate the generated UGC identifier with the corresponding UGC data and store it in a database system. This way, whenever it is necessary to search for or access specific UGC data, it can be quickly located using its UGC identifier. After generating the UGC identifier, server 107 sends the UGC identifier to client 103, so that in client 103, the UGC identifier is associated with the UGC data. When user 101 wants to share or submit a video or image shot using special effects 105, the UGC identifier, as a field circulating throughout the entire scene, will be sent out along with the special effects work.

[0050] In some embodiments, when another user 109 (also referred to as the second user) shares or distributes user 101's special effects work on client 111 (also referred to as the second client), the user can find and trigger the follow-up special effects operation through links such as special effects anchors, sharing panels, similar special effects, friend messages, music details pages, or plus sign transformations displayed on client 111. Since the UGC identifier is sent or distributed along with the special effects work, when user 109 initiates the follow-up operation, client 111 will extract the UGC identifier from the special effects work and send this UGC identifier to server 107. After receiving the UGC identifier, server 107 will search for the UGC data corresponding to this UGC identifier in the database system. After finding the corresponding UGC data, server 107 will send the UGC data back to client 111. After receiving this data, client 111 can render the UGC data on the screen to realize the follow-up and aggregation of special effects data of user 101 and user 109.

[0051] For example, when users 101 and 109 use the same face-changing effect, client 111 can display two screens: the top screen shows user 101's face-changing effect as a reference, and the bottom screen shows user 109's own live camera feed. This feed changes in real-time with user 109's facial movements and applies the same face-changing effect as user 101. User 109 can view the reference screen above and adjust their expressions and movements to achieve better results during the follow-up shot. When user 109 finishes filming, client 111 sends new UGC data, i.e., user 109's face-changing effect, to server 107 to generate a new UGC identifier.

[0052] This approach not only enables intelligent management of special effects data and reduces system load, but also achieves the aggregation of UGC data, thereby increasing the diversity of user gameplay data aggregation and fission methods, improving the utilization rate of special effects, and further enriching the user's gaming experience.

[0053] Figure 2A shows a flowchart of a method 200A for identifying special effects according to some embodiments of the present disclosure. Method 200A can be performed by a first client. Method 200A includes blocks 202, 204, and 206.

[0054] As shown in Figure 2A, in box 202, the first user-generated content (UGC) data captured by the first user using special effects is generated. Referring to Figure 1, client 103 (also called the first client) can obtain the UGC data (also called the first UGC data) generated and recorded by user 101 when using special effects 105 on client 103, which is used to indicate the user's operation, behavior, or result. For example, when using the face-changing effect, the UGC data is the user's facial image or video processed by special effects 105. As another example, when user 101 uses special effects 105 to create artwork, the UGC data can be user 101's handwriting data. During the process of user 101 capturing images using special effects, the generated UGC data can be written to a temporary resource folder by the special effects side of client 103 to save the real-time generated UGC data locally on client 103.

[0055] In box 204, the first UGC data is sent to the server. Referring to Figure 1, after user 101 completes the shooting, that is, after obtaining all the UGC data of the special effects work, the UGC data can be compressed and then sent from client 103 to server 107. Client 103 obtains the interface created by server 107 for UGC data and uploads the UGC data to server 107 through the interface.

[0056] In box 206, a first UGC identifier corresponding to the first UGC data is received from the server. The first UGC identifier is used to identify the first UGC data captured using special effects. Referring to Figure 1, after the server 107 receives the UGC data, it generates a UGC identifier (also called the first UGC identifier) ​​to uniquely identify and distinguish each piece of UGC data. After the UGC identifier is generated, the client 103 receives the UGC identifier from the server 107. Thus, in the client 103, the UGC identifier is associated with the UGC data. When user 101 wants to share or submit a video or image captured using special effects 105, the UGC identifier will be sent out along with the special effects work.

[0057] Figure 2B illustrates a flowchart of a method 200B for generating special effects identifiers according to some embodiments of the present disclosure. Method 200B can be performed by a server. Method 200B includes blocks 208, 210, and 212.

[0058] As shown in Figure 2B, in box 208, the first user-generated content (UGC) data generated by the first user using special effects is received from the first client. Referring to Figure 1, the client 103 can obtain the UGC data generated and recorded by the user 101 when using the special effects 105 on the client 103, which is used to indicate the user's operation, behavior, or result. After the user 101 completes the shooting, that is, after obtaining all the UGC data of the special effects work, the UGC data can be compressed, and then the server 107 receives the UGC data from the client 103.

[0059] In box 210, based on the first UGC data, a first UGC identifier corresponding to the first UGC data is generated. The first UGC identifier is used to identify the first UGC data captured using special effects. Referring to Figure 1, the server 107 generates a UGC identifier based on the received UGC data. The UGC identifier is used to uniquely identify and distinguish each piece of UGC data. In some embodiments, the server 107 can associate the generated UGC identifier with the corresponding UGC data and store it in a database system. In this way, whenever it is necessary to find or access specific UGC data, it can be quickly located through its UGC identifier.

[0060] In box 212, the first UGC identifier is sent to the first client. Referring to Figure 1, on server 107, after the UGC identifier is generated, it is sent from server 107 to client 103. Thus, on client 103, the UGC identifier is associated with the UGC data. When user 101 wants to share or submit a video or image taken using effect 105, the UGC identifier will be sent along with the effect.

[0061] Figure 2C illustrates a flowchart of a method 200C for obtaining special effects according to some embodiments of the present disclosure. Method 200C can be performed by a first client. Method 200C includes blocks 214, 216, and 218.

[0062] In box 214, a first UGC identifier corresponding to the first user-generated content (UGC) data is sent to the server. The first UGC data is generated by the first user using special effects to shoot on the first client. Referring to Figure 1, when another user 109 shares or distributes user 101's special effects work on client 111 (also known as the second client), the user can find and trigger the follow-up special effects operation through links such as special effects anchors, sharing panels, similar special effects, friend messages, music details pages, or plus sign transformations displayed on client 111. Since the UGC identifier is sent or distributed along with the special effects work, when user 109 initiates the follow-up operation, client 111 will extract the UGC identifier from the special effects work and send this UGC identifier to server 107.

[0063] In box 216, the first UGC data is received from the server. Referring to Figure 1, after receiving the UGC identifier, the server 107 searches for the UGC data corresponding to this UGC identifier in the database system. After finding the corresponding UGC data, the server 107 sends the UGC data back to the client 111.

[0064] In box 218, based on the first UGC data, special effects of the first UGC data are rendered. A second user uses these effects to capture the second UGC data on the second client. The second user then interacts with the effects on the second client based on the first and second UGC data. Referring to Figure 1, after receiving this data, client 111 can render the UGC data on the screen to achieve follow-up shooting and aggregation of special effects data from users 101 and 109. For example, when users 101 and 109 use the same face-changing effect, client 111's screen can display two images: the upper image is user 101's face-changing effect work as a reference, and the lower image is user 109's own real-time camera view. This image changes in real-time with user 109's facial movements and applies the same face-changing effect as user 101. User 109 can view the upper reference image while adjusting their own expressions and movements to achieve better results during follow-up shooting, thus realizing special effects interaction between different users. When user 109 finishes shooting, client 111 will send new UGC data, namely user 109's face-changing special effects work, to server 107 to generate a new UGC identifier.

[0065] This approach not only enables intelligent management of special effects data and reduces system load, but also achieves the aggregation of UGC data, thereby increasing the diversity of user gameplay data aggregation and fission methods, improving the utilization rate of special effects, and further enriching the user's gaming experience.

[0066] Figure 3 illustrates a timing diagram of generating user-generated content (UGC) identifiers according to some embodiments of this disclosure. Referring to Figure 1, the process of generating UGC identifiers includes communication between user 101, client 103, and server 107. Therefore, user 301 in Figure 3 is consistent with user 101 in Figure 1, client 303 is consistent with client 103, and server 307 is consistent with server 107. Figure 3 also includes a special effects package 305 and a security audit platform 309. The special effects package 305 is used to decode and render special effects on client 303, allowing the effects to be displayed on client 303's device. The security audit platform 309 is used to audit the generated UGC data and intercept sensitive text and images. The specific steps of generating UGC identifiers and sending UGC identifiers along with UGC data will be explained below.

[0067] At step 311, when user 301 wants to use special effects for shooting, they can send a special effects usage command to client 303 through controls or links displayed on client 303. At step 313, after receiving the command to use special effects, client 303 sends a message to special effects package 305 to render the special effects. At step 315, after receiving the message to render the special effects, special effects package 305 displays the special effects on the display screen or interface of client 303 and applies them to the video or image that the user wants to shoot. At step 317, user 301 can see the special effects on the display screen or interface of client 303 to start shooting. At step 319, when user 301 starts shooting, client 303 can obtain the real-time generated UGC data. At step 321, client 303 provides the address of a temporary resource folder for storing UGC data to special effects package 305. At step 323, special effects package 305 writes the UGC data to the temporary resource folder. At step 325, client 103 can obtain UGC data in segments according to preset time periods. When multiple segments are captured consecutively, at step 327, client 303 can generate an empty address (i.e., an invalid address) for segments other than the first one. At step 329, when effects package 305 receives an empty address from client 303, it does not write any empty UGC data. In other words, whether or not to store UGC data is controlled by client 303. When it is not necessary to store UGC data, an empty address can be sent to effects package 305.

[0068] At step 331, when client 303 detects that user 301 has finished taking photos, it means that no new UGC data will be generated. At step 333, client 303 packages and compresses the saved UGC data. At step 335, client 303 sends the compressed UGC data to server 307. At step 337, server 307 stores the received UGC data in the established database system and generates a UGC identifier based on the UGC data. At step 339, server 307 sends the UGC identifier to client 303. At step 341, server 307 sends the UGC data to security audit platform 309 for auditing to intercept sensitive information. At step 343, security audit platform 309 can use an audit model to audit the UGC data. The type of audit model can be selected according to actual needs, and this disclosure does not limit it. At step 345, security audit platform 309 returns the audit result to server 307. When the audit result does not meet the predetermined conditions, server 307 can reject the UGC data sending request.

[0069] At step 347, user 301 selects to submit a special effects video. At step 349, client 303 writes the special effects video and its corresponding UGC identifier into the submission interface of server 307. At step 351, server 307 writes the special effects video into the video processing model. At step 353, user 301 selects to share the video with another user. At step 355, the UGC identifier is written into the message sent to the other user's client. At step 357, server 307 sends the UGC identifier to the other user to enable subsequent follow-up shooting.

[0070] Figure 4 illustrates a timing diagram of follow-up filming using UGC identifiers according to some embodiments of the present disclosure. Referring to Figure 1, the follow-up filming process includes communication between user 109, client 111, and server 107. Therefore, user 401 in Figure 4 corresponds to user 109 in Figure 1, client 403 corresponds to client 111, and server 409 corresponds to server 107. When user 401 views the special effects work filmed by user 301 on client 403, since user 301's UGC data is sent along with the special effects work, client 403 can obtain the UGC identifier from server 409 or client 303 when acquiring the special effects work. Figure 4 also includes a special effects package 405, which is used to decode, render, and process the special effects on client 403, allowing the special effects to be displayed on client 403's device. The specific steps for acquiring the special effects will be explained below. At 411, when user 401 wants to use special effects for shooting, they can send a special effects usage command to client 403 through controls or links displayed on client 403. At 413, after receiving the command to use special effects, client 403 sends a message to special effects package 405 to render the special effects. At 415, after receiving the message to render the special effects, special effects package 405 displays the special effects on the display screen or interface of client 403 and applies them to the video or image that the user wants to shoot. At 417, user 401 can see the same effect as the special effects used by user 301 on the display screen or interface of client 403.

[0071] In some embodiments, after rendering the same special effect used by user 301, client worker thread 407 can request user 301's UGC data from server 409 to aggregate different user special effect works. At 419, client worker thread 407 sends a UGC identifier to server 409. At 421, server 409 queries the database system for the resource locator (URL) and review status of the UGC data corresponding to the UGC identifier. At 423, after determining the URL and review status of the UGC data, server 409 sends the URL to client worker thread 407. At 425, after receiving the URL, client worker thread 407 can download the compressed UGC data via the URL. At 427, after successful download, server 409 sends the compressed UGC data to client worker thread 407. At 429, client worker thread 407 decompresses the UGC data. At 431, after decompressing the UGC data, client worker thread 407 sends the file address of the UGC data to special effects package 405. At 433, UGC data is parsed by effects package 405 based on the file address. At 447, UGC data is processed by effects package 405. At 449, UGC data is rendered on the screen or interface of client 403 by effects package 405. At 451, user 401 can view user 301's UGC data through client 403.

[0072] In some embodiments, client 403 may also display the avatar image of user 301. At 435, when a request message for a specified avatar is detected, the user identifier is passed from effects package 405 to client 403. At 437, client 403 obtains the avatar image link through server interface 409. At 439, server 409 sends the avatar image link to client 403. At 441, based on the avatar image link, client 403 downloads the specified avatar. At 443, client 403 sends the local path of the avatar to effects package 405. At 445, effects package 405 renders the specified avatar using the local path.

[0073] Figure 5A illustrates a flowchart of a method for writing UGC data to a temporary resource folder by the effects side according to some embodiments of the present disclosure. Referring to Figure 3, the effects side corresponds to the effects package 305 and is used to process and render effects on the client 303. In box 501, the whitelist path is obtained. Referring to Figure 3, when the user 301 starts shooting, the client 303 can obtain the real-time generated UGC data. At this time, the client 303 provides the effects package 305 with the address of a resource folder temporarily used to store UGC data and grants read and write permissions to the resource folder. Obtaining the whitelist address can also be referred to as obtaining the address of a readable and writable resource folder. In box 503, the UGC data is updated. Through the address of the writable resource folder, i.e., the whitelist path, the real-time generated UGC data can be written to the resource folder in segments. In box 505, a recording end message is received. Referring to Figure 3, when client 303 detects that user 301 has finished recording, it means that no new UGC data will be generated, and recording ends. The recording end message can be triggered by user 301's operation of a specific control in client 303, or it can be automatically generated within a preset time after recording stops. At 507, it checks whether an accessible whitelist path exists, i.e., whether the address of a resource folder that can be written to exists. If no accessible whitelist path exists, execution box 509 is executed to end execution. If an accessible whitelist path exists, execution box 511 is executed to write the UGC data to the resource folder. Finally, execution box 513 destroys the effects package instance.

[0074] Figure 5B illustrates a schematic diagram of writing UGC data to a temporary resource folder according to some embodiments of the present disclosure. As shown in Figure 5B, after obtaining UGC data, the UGC data can be classified and structured. For example, it can be divided into two categories: user information 515 and user operation data 517. The classified and structured UGC data is then categorized under each username 519. When UGC data needs to be obtained, it can be quickly located and retrieved using username 519 as an index.

[0075] Figure 6A shows a flowchart of a method for obtaining UGC data according to some embodiments of the present disclosure. In box 601, the whitelist path is initialized. Referring to Figure 4, the whitelist path is the address of the resource folder for reading UGC data provided by client 403 to special effects package 405. The whitelist path needs to be initialized before obtaining it. In box 603, it is determined whether a fallback avatar needs to be displayed. In some embodiments, this can be determined based on the parsed UGC data. In some embodiments, the fallback avatar is only displayed when the system initiates an avatar display request but cannot retrieve avatar data. Referring to Figure 4, before client 403 renders the UGC data captured by user 301 using special effects and user 301's avatar, the fallback avatar can be rendered first. The fallback avatar may include a preset avatar image, such as an avatar on a blank page; this disclosure does not limit this. In box 605, the whitelist path is obtained. Obtaining the whitelist path can also be referred to as obtaining the address of the resource folder for readable UGC data. In box 607, it is determined whether an accessible whitelist path exists. If no accessible whitelist path exists, proceed to box 609 to end execution. If an accessible whitelist path exists, proceed to box 611 to read and parse UGC data in order to render UGC data effects.

[0076] In some embodiments, the user's avatar image can also be displayed. In box 613, it is determined whether the avatar data has been consumed, i.e., whether a request message for a specified avatar has been detected. In box 615, when a request message for a specified avatar is detected, the effects package can request the avatar from the client, and the client can send the local path of the avatar to the effects package. In box 617, the effects package obtains the avatar through the local path and renders the specified avatar. In box 619, the effects retrieval of the next node is triggered.

[0077] Figure 6B illustrates a schematic diagram of receiving UGC data according to some embodiments of the present disclosure. As shown in Figure 6B, when UGC data needs to be rendered, the username can be used as an index to determine whether the UGC data corresponding to the user needs to be executed. When it is determined that the UGC data needs to be rendered, the information stored under the username can be assigned to the image to achieve rendering. For example, the texture information stored under username 623 is rendered onto the image, and interface 621 is the display interface when rendering the UGC data corresponding to username 623. As another example, the texture information stored under username 627 is rendered onto the image, and interface 625 is the display interface when rendering the UGC data corresponding to username 627.

[0078] Figure 7 illustrates a flowchart of a method for obtaining a UGC identifier on a client side and writing the UGC identifier into a message according to some embodiments of the present disclosure. Referring to Figure 7, obtaining a UGC identifier on a client side and writing the UGC identifier into a message may include a shooting process 737, an editing process 739, and a publishing process 741. The shooting process 737 includes frames 701, 703, 705, 707, and 709. In frame 701, shooting begins. The client can determine whether to start shooting by detecting the user's shooting operation. In frame 703, it is determined whether the shooting data is the first segment of a video. When the shooting data is not the first segment of a video, frame 705 is executed, and no operation is performed; when the shooting data is the first segment of a video, frame 707 is executed, and an address is sent to the effects package. The client sends the address of a resource folder containing readable and writable data to the effects package, enabling the effects package to write UGC data into the resource folder. Shooting ends when frame 709 is detected.

[0079] Referring again to Figure 7, the editing process 739 may include boxes 711, 713, 715, 717, and 719. In box 711, data is compressed. In response to the end of shooting, the client can package and compress the saved UGC data. In box 713, an access key / security key (ak / sk) is obtained. ak / sk authentication ensures that only authorized users can access and invoke specific application programming (API) interfaces. In box 715, the client can obtain the URL of the UGC identifier from the server via the ak / sk. In box 717, the UGC identifier is obtained. After obtaining the URL, the client can obtain the UGC identifier from the server via the URL. In box 719, the UGC identifier is exposed so that the UGC identifier can be a universally applicable string across all scenarios.

[0080] Referring again to Figure 7, the publishing process 741 may include boxes 721, 723, 725, 727, 729, 731, 733, and 735. In box 721, the user selects to submit their special effects artwork. Before submission, box 723 is executed to determine if the artwork has a corresponding UGC identifier. If a UGC identifier exists, box 725 is executed to encapsulate the UGC identifier, allowing it to be distributed along with the artwork. If no UGC identifier exists, box 727 is executed, and the submission proceeds directly. In box 729, the user selects to share their special effects artwork with another user via instant messaging (IM). Before sharing, box 731 is executed to determine if the artwork has a corresponding UGC identifier. If a UGC identifier exists, box 733 is executed to encapsulate the UGC identifier, allowing it to be distributed along with the artwork. If no UGC identifier exists, box 735 is executed, and a sharing timer begins.

[0081] Figure 8 illustrates a flowchart of a method for rendering special effects and user avatars on a client based on UGC identifiers according to some embodiments of the present disclosure. Referring to Figure 7, a user can choose to submit and share special effects works. Returning to Figure 8, in box 801, another user can follow up on a special effects work shared via IM message. In box 805, another user can also follow up on a submitted special effects work. In boxes 803 and 807, for submitted or shared special effects works, the corresponding UGC identifier is obtained. In the sharing scenario, a user shares content with a designated friend and wants the friend to follow up. Therefore, in this scenario, there is a strong demand for carrying the UGC identifier. The client waits for the UGC data processing flow to complete to ensure that the UGC identifier can be carried. However, in the submission scenario, considering that the increased posting time may reduce the submission success rate, the submission scenario only monitors the generation of the UGC identifier and does not force the waiting for the generation of the UGC identifier to complete.

[0082] In box 809, begin shooting with special effects. The special effects used at this point are the same as those in the follow-up special effects video. In box 811, determine if the UGC data corresponding to the acquired UGC identifier is locally cached. If the UGC data is not locally cached, execute box 815 to update the resource cache usage time. If the UGC data is locally cached, execute box 813 to pull the Loki server interface. The Loki server interface is used to download the resource files of the UGC data. In box 817, determine if the pull was successful. If the pull fails, execute box 819 for failure monitoring. The client uses a timeout monitoring mechanism to control whether to block the entire process in different distribution scenarios. If the pull is successful, execute box 821 to download the resource files of the UGC data from the Loki server via the Loki server interface. In box 823, determine if the download was successful. If the download fails, execute box 825 for failure monitoring. If the download is successful, execute box 827 to update the cached UGC data. In box 829, the client sends the resource path to the effects package, enabling the effects package to read updated UGC data from the client's resource folder. In box 831, after obtaining the UGC data via the resource path, the effects package renders the UGC data on the client.

[0083] In some embodiments, the client can also display the user's avatar in the captured special effects artwork. In box 833, the system listens for special effects package messages to determine if a request message for a specified avatar exists. In box 835, when a request message for a specified avatar is detected, the user identifier is passed from the special effects package to the client, triggering box 837 to obtain the avatar image link. In box 839, the system determines whether obtaining the avatar link was successful. If obtaining the avatar link fails, box 841 is executed for monitoring on the failure side. If obtaining the avatar link is successful, box 843 is executed, and the client downloads the specified avatar based on the avatar link. In box 845, the system determines whether the download was successful. If the download fails, box 847 is executed to render a fallback image. The fallback image is consistent with the fallback avatar in Figure 6A and will not be described further here. If the download is successful, box 949 is executed, and the client 403 sends the local image path of the avatar to the special effects package, triggering box 851 to render the specified avatar using the local image path.

[0084] Figure 9 illustrates a schematic diagram of the overall chain for generating UGC identifiers and rendering special effects based on UGC identifiers according to some embodiments of the present disclosure. Referring to Figure 9, the process of generating UGC identifiers includes a shooting process 939 and an editing process 941. The shooting process includes frames 901, 903, and 905. In frame 901, user A enters the camera. In frame 903, the user begins shooting with special effects. In frame 905, UGC data is generated along with user A's shooting operation. The editing process 941 includes frames 907 and 909. In frame 907, the client obtains the ak / sk interface to execute frame 909, uploading UGC data to server 929. After receiving the UGC data, server 929 can store the UGC data in database system 931 and send it to review platform 933 for review. After receiving the UGC data, server 929 can also share or distribute it according to user A's instructions. The special effects work may include video content 911, which may include data such as trajectory, image texture, and text information.

[0085] Referring to Figure 9, the special effects work can be shared with user B via IM message body 915. After receiving message 921, user B can inherit user A's UGC data to perform follow-up shooting. In some embodiments, the IM message body may include message content 919 and UGC identifier 917. IM sharing scenarios have strong privacy requirements and lower content security requirements for UGC resources. When following up shooting in the IM message sharing link, if the UGC data is under review, there is no need to wait for the review result; the data can be sent directly. Therefore, in the IM message follow-up shooting link, the client adds a scene identifier, performs secondary encapsulation of the UGC identifier, and then transmits it to the camera. This scene identifier is used when requesting the Loki server to send UGC resources. Continuing to refer to Figure 9, the special effects work can be published to user C via submission data package 927, which includes UGC identifier 923 and vid data content 925. When user C watches the special effects video 935, triggering the follow-up shooting operation 937, user C can inherit user A's UGC data to perform follow-up shooting.

[0086] Figure 10 illustrates a schematic diagram of the overall link of UGC identifiers and UGC data issued by the Loki server according to some embodiments of this disclosure. Referring to Figure 10, UGC data generation may include boxes 1003 and 1005. The method and process of obtaining AK / SK in box 1003 and generating UGC data in box 1005 are consistent with the description above and will not be repeated here. After the UGC data is generated, the video cloud storage generates storage address information. The client calls the UGC creation interface 1007 of the Loki server issuing platform to send UGC data and information such as user identifiers and special effect identifiers to the database system 1009 of the Loki server for storage, and the identifier generator 1011 in the Loki server generates UGC identifiers 1013. Through the UGC interface 1007, the transmission of UGC data and UGC identifiers between the client and the Loki server can be realized.

[0087] Referring again to Figure 10, after receiving the UGC data, the Loki server will execute box 1017, submitting the Function as a Service (FaaS) data for review. Before submission, the UGC data is converted into the specified format required for review, and then the converted UGC data is sent from the Loki server to the review platform 1019. In box 1021, the review status of the UGC data is received from the review platform 1019. In some embodiments, after the UGC data and information such as user identifiers and effect identifiers are sent to the database system 1009 of the Loki server for storage, the data stored in the database system 1009 can also be queried and analyzed through data warehouse software 1015.

[0088] Referring back to Figure 10, the Loki server receives UGC data creation information and review system change information, then packages the latest UGC data (1027) and stores it in the database system (1009). The client implements sharing inheritance (1035) or follow-up inheritance (1037) through the IM sharing message interface (1029) or anchor point interface (1031). When a user uses the inheritance effect, the client obtains the download address of the UGC data through Loki's UGC data retrieval interface (1025). After downloading, the tool loads the UGC data, allowing the user to inherit the data information created by the previous user.

[0089] Figure 11 illustrates the effect of a method for obtaining special effects according to some embodiments of the present disclosure. As shown in Figure 11, display interface 1101 is a display interface for a video of user A playing a racing game. When user A performs game operations, the client can generate user A's UGC data such as driving trajectory, vehicle position, time, and race result. When user A's game video is distributed or shared to user B's client device, user B's client can render user A's UGC data, so user B's client display interface 1103 simultaneously displays the data of user A and user B. User B can view user A's reference screen while adjusting their own operations.

[0090] Referring again to Figure 11, display interface 1105 shows the video of user A playing a drawing game. While user A is playing the game, the client can generate user A's UGC data, such as handwriting. When user A's game video is distributed or shared to user B's client device, user B's client can render user A's UGC data, thus displaying both user A's and user B's data simultaneously in user B's client display interface 1107. Compared to custom effects methods, this publication introduces a completely new, highly flexible, scalable, and reusable social effects viral marketing approach. This solution achieves the virality of effects by transmitting UGC data, ensuring that each user produces a unique effect when using social effects. Simultaneously, users can share these effects with friends for collaborative creation, greatly enriching the gameplay options for effects.

[0091] Figure 12A shows a block diagram of an apparatus 1200A for identifying special effects according to some embodiments of the present disclosure. The apparatus 1200A is deployed on a first client. As shown in Figure 1200A, the apparatus 1200A includes a UGC data generation module 1202 configured to generate first user-generated content (UGC) data captured by a first user using special effects. The apparatus 1200A also includes a UGC data sending module 1204 configured to send the first UGC data to a server. The apparatus 1200A further includes a UGC identifier receiving module 1206 configured to receive a first UGC identifier corresponding to the first UGC data from the server, the first UGC identifier being used to identify the first UGC data captured using special effects.

[0092] Figure 12B shows a block diagram of an apparatus 1200B for generating special effects identifiers according to some embodiments of the present disclosure. The apparatus 1200B is deployed on a server. As shown in Figure 1200B, the apparatus 1200B includes a UGC data receiving module 1208, configured to receive first user-generated content (UGC) data generated by a first user using special effects from a first client. The apparatus 1200B also includes a UGC identifier generation module 1210, configured to generate a first UGC identifier corresponding to the first UGC data based on the first UGC data. The first UGC identifier is used to identify the first UGC data captured using special effects. The apparatus 1200B also includes a UGC identifier sending module 1212, configured to send the first UGC identifier to the first client.

[0093] Figure 12C shows a block diagram of an apparatus 1200C for acquiring special effects according to some embodiments of the present disclosure. The apparatus 1200C is deployed on a second client. As shown in Figure 1200C, the apparatus 1200C includes a UGC identifier sending module 1214, configured to send a first UGC identifier corresponding to first user-generated content (UGC) data to a server. The first UGC data is generated by a user using special effects to capture images on the first client. The apparatus 1200C also includes a UGC data receiving module 1216, configured to receive the first UGC data from the server. The apparatus 1200C further includes a special effects rendering module 1218, configured to render special effects based on the first UGC data, wherein a second user uses special effects to capture second UGC data on the second client, and the second user interacts with special effects on the second client based on the first and second UGC data.

[0094] Figure 13 shows a block diagram of a device 1300 capable of implementing various embodiments of the present disclosure. As shown in Figure 13, the device 1300 includes a central processing unit (CPU) and / or a graphics processing unit (GPU) 1301, which can perform various appropriate actions and processes according to computer program instructions stored in read-only memory (ROM) 1302 or loaded from storage unit 1308 into random access memory (RAM) 1303. Various programs and data required for the operation of the device 1300 may also be stored in RAM 1303. The CPU / GPU 1301, ROM 1302, and RAM 1303 are interconnected via bus 1304. An input / output (I / O) interface 1305 is also connected to bus 1304. Although not shown in Figure 13, the device 1300 may also include a coprocessor.

[0095] Multiple components in device 1300 are connected to I / O interface 1305, including: input unit 1306, such as keyboard, mouse, etc.; output unit 1307, such as various types of monitors, speakers, etc.; storage unit 1308, such as disk, optical disk, etc.; and communication unit 1309, such as network card, modem, wireless transceiver, etc. Communication unit 1309 allows device 1300 to exchange information / data with other devices through computer networks such as the Internet and / or various telecommunications networks.

[0096] The various methods or processes described above can be executed by CPU / GPU 1301. For example, in some embodiments, the methods may be implemented as computer software programs tangibly contained in a machine-readable medium, such as storage unit 1308. In some embodiments, part or all of the computer program may be loaded and / or installed on device 1300 via ROM 1302 and / or communication unit 1309. When the computer program is loaded into RAM 1303 and executed by CPU / GPU 1301, one or more steps or actions in the methods or processes described above can be performed.

[0097] In some embodiments, the methods and processes described above can be implemented as a computer program product. The computer program product may include a computer-readable storage medium having computer-readable program instructions loaded thereon for performing various aspects of this disclosure.

[0098] Computer-readable storage media can be tangible devices capable of holding and storing instructions for use by an instruction execution device. Computer-readable storage media can be, for example, but not limited to, electrical storage devices, magnetic storage devices, optical storage devices, electromagnetic storage devices, semiconductor storage devices, or any suitable combination thereof. More specific examples (a non-exhaustive list) of computer-readable storage media include: portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), static random access memory (SRAM), portable compact disc read-only memory (CD-ROM), digital multifunction disc (DVD), memory sticks, floppy disks, mechanical encoding devices, such as punch cards or recessed protrusions storing instructions thereon, and any suitable combination thereof. The computer-readable storage media used herein are not to be construed as transient signals themselves, such as radio waves or other freely propagating electromagnetic waves, electromagnetic waves propagating through waveguides or other transmission media (e.g., light pulses through fiber optic cables), or electrical signals transmitted through wires.

[0099] The computer-readable program instructions described herein can be downloaded from computer-readable storage media to various computing / processing devices, or downloaded via a network, such as the Internet, a local area network (LAN), a wide area network (WAN), and / or a wireless network, to an external computer or external storage device. The network may include copper cables, fiber optic cables, wireless transmission, routers, firewalls, switches, gateway computers, and / or edge servers. A network adapter card or network interface in each computing / processing device receives the computer-readable program instructions from the network and forwards them to the computer-readable storage media in the respective computing / processing device.

[0100] Computer program instructions used to perform the operations of this disclosure may be assembly instructions, instruction set architecture (ISA) instructions, machine instructions, machine-dependent instructions, microcode, firmware instructions, status setting data, or source code or object code written in any combination of one or more programming languages, including object-oriented programming languages ​​and conventional procedural programming languages. The computer-readable program instructions may execute entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving a remote computer, the remote computer may be connected to the user's computer via any type of network—including a local area network (LAN) or a wide area network (WAN)—or may be connected to an external computer (e.g., via the Internet using an Internet service provider). In some embodiments, electronic circuitry, such as programmable logic circuitry, field-programmable gate arrays (FPGAs), or programmable logic arrays (PLAs), is personalized by utilizing the status information of the computer-readable program instructions to implement various aspects of this disclosure.

[0101] These computer-readable program instructions can be provided to a processing unit of a general-purpose computer, a special-purpose computer, or other programmable data processing apparatus to produce a machine such that, when executed by the processing unit of the computer or other programmable data processing apparatus, they create means for implementing the functions / actions specified in one or more blocks of the flowchart and / or block diagram. These computer-readable program instructions can also be stored in a computer-readable storage medium that causes a computer, programmable data processing apparatus, and / or other device to operate in a particular manner. Thus, the computer-readable medium storing the instructions comprises an article of manufacture that includes instructions for implementing aspects of the functions / actions specified in one or more blocks of the flowchart and / or block diagram.

[0102] Computer-readable program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other device to cause a series of operational steps to be performed on the computer, other programmable data processing apparatus, or other device to produce a computer-implemented process, thereby causing the instructions executed on the computer, other programmable data processing apparatus, or other device to perform the functions / actions specified in one or more boxes of a flowchart and / or block diagram.

[0103] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of devices, methods, and computer program products according to various embodiments of the present disclosure. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of an instruction containing one or more executable instructions for implementing a specified logical function. In some alternative implementations, the functions marked in the blocks may occur in a different order than those marked in the drawings. For example, two consecutive blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, may be implemented using a dedicated hardware-based system that performs the specified function or action, or using a combination of dedicated hardware and computer instructions.

[0104] The various embodiments of this disclosure have been described above. These descriptions are exemplary and not exhaustive, nor are they limited to the disclosed embodiments. Many modifications and variations will be apparent to those skilled in the art without departing from the scope and spirit of the described embodiments. The terminology used herein is chosen to best explain the principles, practical applications, or technical improvements to the technology in the market, or to enable others skilled in the art to understand the embodiments disclosed herein.

[0105] The following are some example implementations of this disclosure.

[0106] Example 1. A method for identifying special effects, the method being executed by a first client, the method comprising:

[0107] Generate first-user-generated content (UGC) data captured by the first user using special effects;

[0108] Send the first UGC data to the server; and

[0109] The server receives a first UGC identifier corresponding to the first UGC data, the first UGC identifier being used to identify the first UGC data shot using the special effects.

[0110] Example 2. According to the method described in Example 1, generating the first UGC data captured by the first user using special effects includes:

[0111] In response to the first user starting to shoot using the special effect, a temporary resource folder is generated on the first client.

[0112] Grant permissions to the temporary resource folder on the special effects side;

[0113] Provide the address of the temporary resource folder to the effects side; and

[0114] The special effects side writes the first UGC data into the temporary resource folder.

[0115] Example 3. The method according to any one of Examples 1-2, wherein sending the first UGC data to the server includes:

[0116] In response to the completion of the shooting, the first UGC data is compressed; and

[0117] The first client sends compressed first UGC data to the server.

[0118] Example 4. The method according to any one of Examples 1-3 further includes:

[0119] In response to the first user sharing the first UGC data with the second user of the second client, the first UGC identifier is written into the message; and

[0120] The message carrying the first UGC identifier is sent from the first client to the second client.

[0121] Example 5. A method for generating identifiers for special effects, the method comprising:

[0122] Receive user-generated content (UGC) data generated by the first user using special effects from the first client.

[0123] Based on the first UGC data, a first UGC identifier corresponding to the first UGC data is generated. The first UGC identifier is used to identify the first UGC data shot using the special effects; and

[0124] Send the first UGC identifier to the first client.

[0125] Example 6. The method described in Example 5 further includes:

[0126] In response to receiving the first UGC data, the first UGC data is converted into the specified form required for review;

[0127] Sending the converted first UGC data from the server to the review platform; and

[0128] Receive the review status of the first UGC data from the review platform.

[0129] Example 7. The method according to any one of Examples 5-6 further includes:

[0130] In response to receiving the first UGC identifier, the resource address and review status of the first UGC data corresponding to the first UGC identifier are determined; and

[0131] In response to the audit status meeting predetermined conditions, the first UGC data is obtained through the resource address; and

[0132] Decompress and send the first UGC data to the second client.

[0133] Example 8. The method according to any one of Examples 5-7 further includes:

[0134] In response to the fact that the audit status does not meet the predetermined conditions, the second client's access to the first UGC data is denied.

[0135] Example 9. The method according to any one of Examples 5-8 further includes:

[0136] Listen for messages from the second client requesting a specified avatar; and

[0137] In response to receiving a message requesting a specified avatar, the server sends an image link of the specified avatar to the second client.

[0138] Example 10. A method for obtaining special effects, the method being executed by a second client, the method comprising:

[0139] Send a first UGC identifier corresponding to the first user-generated UGC data to the server. The first UGC data is generated by the first user using special effects to shoot on the first client.

[0140] Receive the first UGC data from the server; and

[0141] Based on the first UGC data, render the special effects of the first UGC data.

[0142] The second user uses the special effects to capture the second UGC data on the second client.

[0143] The second user performs special effects interaction on the second client based on the first UGC data and the second UGC data.

[0144] Example 11. The method according to Example 10 further includes:

[0145] The second client receives the first UGC identifier shared by the first user from the first client.

[0146] Example 12. The method according to any one of Examples 10-11 further includes:

[0147] The second client receives the first UGC identifier distributed by the server from the server.

[0148] Example 13. The method according to any one of Examples 10-12, wherein sending the first UGC identifier corresponding to the first UGC data to the server includes:

[0149] In response to the second user of the second client initiating the operation of purchasing the same item, the first UGC identifier is sent from the second client to the server.

[0150] Example 14. The method according to any one of Examples 10-13, wherein receiving the first UGC data from the server comprises:

[0151] The resource address from which the second client receives the first UGC data from the server; and

[0152] Based on the resource address, the first UGC data is received.

[0153] Example 15. The method according to any one of Examples 10-13 further includes:

[0154] In response to receiving a touch operation of the second user on the avatar control from the second client, a message specifying an avatar is sent from the second client to the server;

[0155] The second client receives the image link of the specified avatar from the server;

[0156] Download the specified avatar based on the image link of the specified avatar; and

[0157] Upon successful download of the specified avatar, the specified avatar is displayed on the second client.

[0158] Example 16. An apparatus for identifying special effects, the apparatus being deployed, the apparatus comprising:

[0159] The UGC data generation module is configured to generate user-generated content (UGC) data captured by the first user using special effects.

[0160] The UGC data sending module is configured to send the first UGC data to the server; and

[0161] The UGC identifier receiving module is configured to receive a first UGC identifier corresponding to the first UGC data from the server. The first UGC identifier is used to identify the first UGC data shot using the special effects.

[0162] Example 17. The apparatus according to Example 16, wherein the UGC data generation module comprises:

[0163] The temporary resource folder generation module is configured to generate a temporary resource folder on the first client in response to the first user starting to shoot using the special effect;

[0164] The permission granting module is configured to grant permissions to the temporary resource folder to the special effects side;

[0165] The address providing module is configured to provide the address of the temporary resource folder to the effects side; and

[0166] The UGC data writing module is configured to write the first UGC data to the temporary resource folder by the effects side.

[0167] Example 18. The apparatus according to any one of Examples 16-17, wherein the UGC data sending module comprises:

[0168] The UGC data compression module is configured to compress the first UGC data in response to the completion of the shooting; and

[0169] The first UGC data sending module is configured to send compressed first UGC data from the first client to the server.

[0170] Example 19. The apparatus according to any one of Examples 16-18 further includes:

[0171] The UGC identifier writing module is configured to write the first UGC identifier into a message in response to a first user sharing the first UGC data with a second user on a second client; and

[0172] The message sending module is configured to send the message carrying the first UGC identifier from the first client to the second client.

[0173] Example 20. An apparatus for generating identifiers for special effects, the apparatus being deployed on a server, the apparatus comprising:

[0174] The UGC data receiving module is configured to receive user-generated content (UGC) data generated by the first user using special effects from the first client.

[0175] The UGC identifier generation module is configured to generate a first UGC identifier corresponding to the first UGC data based on the first UGC data. The first UGC identifier is used to identify the first UGC data captured using the special effects.

[0176] The UGC identifier sending module is configured to send the first UGC identifier to the first client.

[0177] Example 21. The apparatus according to Example 20 further includes:

[0178] The UGC data conversion module is configured to convert the first UGC data into a specified form required for review in response to receiving the first UGC data.

[0179] The second UGC data sending module is configured to send the converted first UGC data to the review platform; and

[0180] The review status receiving module is configured to receive the review status of the first UGC data from the review platform.

[0181] Example 22. The apparatus according to any one of Examples 20-21 further includes:

[0182] The resource address determination module is configured to, in response to receiving the first UGC identifier from the second client, determine the resource address and review status of the first UGC data corresponding to the first UGC identifier; and

[0183] The UGC data acquisition module is configured to acquire the first UGC data via the resource address in response to the audit status meeting predetermined conditions; and

[0184] The third UGC data sending and receiving module is configured to decompress and send the first UGC data from the server to the second client.

[0185] Example 23. The apparatus according to any one of Examples 20-22 further includes:

[0186] The access denial module is configured to deny the second client access to the first UGC data in response to the audit status not meeting the predetermined conditions.

[0187] Example 24. The apparatus according to any one of Examples 20-23 further includes:

[0188] The listening module is configured to listen for messages from the second client requesting a specified avatar; and

[0189] The avatar request module is configured to, in response to receiving a message requesting a specified avatar, send an image link of the specified avatar from the server to the second client.

[0190] Example 25. An apparatus for obtaining special effects, the apparatus being deployed on a second client, the apparatus comprising:

[0191] The UGC identifier sending module is configured to send a first UGC identifier corresponding to the first user-generated content UGC data to the server. The first UGC data is generated by the first user using special effects to shoot on the first client.

[0192] The UGC data receiving module is configured to receive the first UGC data from the server; and

[0193] The special effects rendering module is configured to render special effects based on the first UGC data.

[0194] The second user uses the special effects to capture the second UGC data on the second client.

[0195] The second user performs special effects interaction on the second client based on the first UGC data and the second UGC data.

[0196] Example 26. The apparatus according to Example 25 further includes:

[0197] The first identifier receiving module is configured to receive the first UGC identifier shared by the first user from the first client by the second client.

[0198] Example 27. The apparatus according to any one of Examples 25-26 further includes:

[0199] The second identifier receiving module is configured to receive the first UGC identifier distributed by the server from the server by the second client.

[0200] Example 28. The apparatus according to any one of Examples 25-27, wherein the UGC identifier sending module comprises:

[0201] The first identifier sending module is configured to send the first UGC identifier from the second client to the server in response to a second user on the second client initiating an operation to purchase the same item.

[0202] Example 29. The apparatus according to any one of Examples 25-28, wherein the UGC data receiving module comprises:

[0203] The address receiving module is configured to receive the resource address of the first UGC data from the server by the second client; and

[0204] The first data receiving module is configured to receive the first UGC data from the server by the second client based on the resource address.

[0205] Example 30. The apparatus according to any one of Examples 25-29 further includes:

[0206] The avatar message sending module is configured to send a message specifying an avatar from the second client to the server in response to receiving a touch operation of the avatar control from the second user of the second client;

[0207] The image link receiving module is configured to receive the image link of the specified avatar from the server by the second client;

[0208] A designated avatar download module is configured to download the designated avatar based on an image link of the designated avatar; and

[0209] The designated avatar display module is configured to display the designated avatar on the second client in response to a successful download of the designated avatar.

[0210] Example 31. An electronic device comprising:

[0211] Processor; and

[0212] A memory coupled to the processor, the memory having instructions stored therein, which, when executed by the processor, cause the electronic device to perform actions, the actions including:

[0213] Generate first-user-generated content (UGC) data captured by the first user using special effects;

[0214] Send the first UGC data to the server; and

[0215] The server receives a first UGC identifier corresponding to the first UGC data, the first UGC identifier being used to identify the first UGC data shot using the special effects.

[0216] Example 32. The electronic device according to Example 30, wherein generating first UGC data captured by a first user using special effects includes:

[0217] In response to the first user starting to shoot using the special effect, a temporary resource folder is generated on the first client.

[0218] Grant permissions to the temporary resource folder on the special effects side;

[0219] Provide the address of the temporary resource folder to the effects side; and

[0220] The special effects side writes the first UGC data into the temporary resource folder.

[0221] Example 33. An electronic device according to any one of Examples 31-32, wherein sending the first UGC data to the server includes:

[0222] In response to the completion of the shooting, the first UGC data is compressed; and

[0223] The first client sends compressed first UGC data to the server.

[0224] Example 34. The electronic device according to any one of Examples 31-33 further includes:

[0225] In response to the first user sharing the first UGC data with the second user of the second client, the first UGC identifier is written into the message; and

[0226] The message carrying the first UGC identifier is sent from the first client to the second client.

[0227] Example 35. An electronic device comprising:

[0228] Processor; and

[0229] A memory coupled to the processor, the memory having instructions stored therein, which, when executed by the processor, cause the electronic device to perform actions, the actions including:

[0230] Receive user-generated content (UGC) data generated by the first user using special effects from the first client.

[0231] Based on the first UGC data, a first UGC identifier corresponding to the first UGC data is generated. The first UGC identifier is used to identify the first UGC data shot using the special effects; and

[0232] Send the first UGC identifier to the first client.

[0233] Example 36. The electronic device according to Example 35 further includes:

[0234] In response to receiving the first UGC data, the first UGC data is converted into the specified form required for review;

[0235] Sending the converted first UGC data from the server to the review platform; and

[0236] Receive the review status of the first UGC data from the review platform.

[0237] Example 37. The electronic device according to any one of Examples 35-36 further includes:

[0238] In response to receiving the first UGC identifier from the second client, the resource address and review status of the first UGC data corresponding to the first UGC identifier are determined; and

[0239] In response to the audit status meeting predetermined conditions, the first UGC data is obtained through the resource address; and

[0240] The first UGC data is decompressed and sent from the server to the second client.

[0241] Example 38. The electronic device according to any one of Examples 35-37 further includes:

[0242] In response to the fact that the audit status does not meet the predetermined conditions, the second client's access to the first UGC data is denied.

[0243] Example 39. The electronic device according to any one of Examples 35-38 further includes:

[0244] Listen for messages from the second client requesting a specified avatar; and

[0245] In response to receiving a message requesting a specified avatar, the server sends an image link of the specified avatar to the second client.

[0246] Example 40. A method for obtaining special effects, comprising:

[0247] Send a first UGC identifier corresponding to the first user-generated UGC data to the server. The first UGC data is generated by the first user using special effects to shoot on the first client.

[0248] Receive the first UGC data from the server; and

[0249] Based on the first UGC data, render the special effects of the first UGC data.

[0250] The second user uses the special effects to capture the second UGC data on the second client.

[0251] The second user performs special effects interaction on the second client based on the first UGC data and the second UGC data.

[0252] Example 41. The electronic device according to Example 40 further includes:

[0253] The second client receives the first UGC identifier shared by the first user from the first client.

[0254] Example 42. The electronic device according to any one of Examples 40-41 further includes:

[0255] The second client receives the first UGC identifier distributed by the server from the server.

[0256] Example 43. An electronic device according to any one of Examples 40-42, wherein sending a first UGC identifier corresponding to the first UGC data to a server includes:

[0257] In response to the second user of the second client initiating the operation of purchasing the same item, the first UGC identifier is sent from the second client to the server.

[0258] Example 44. An electronic device according to any one of Examples 40-43, wherein receiving the first UGC data from the server includes:

[0259] The resource address from which the second client receives the first UGC data from the server; and

[0260] Based on the resource address, the second client receives the first UGC data from the server.

[0261] Example 45. The electronic device according to any one of Examples 40-44 further includes:

[0262] In response to receiving a touch operation of the second user on the avatar control from the second client, a message specifying an avatar is sent from the second client to the server;

[0263] The second client receives the image link of the specified avatar from the server;

[0264] Download the specified avatar based on the image link of the specified avatar; and

[0265] Upon successful download of the specified avatar, the specified avatar is displayed on the second client.

[0266] Example 46. A computer-readable storage medium having stored thereon computer-executable instructions, wherein the computer-executable instructions are executed by a processor to implement the method according to any one of Examples 1 to 15.

[0267] Example 47. A computer program product tangibly stored on a computer-readable medium and comprising computer-executable instructions that, when executed by a device, cause the device to perform the method according to any one of Examples 1 to 15.

[0268] Although this disclosure has been described using language specific to structural features and / or methodological logic, it should be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or actions described above. Rather, the specific features and actions described above are merely illustrative examples of implementing the claims.

Claims

1. A method for identifying special effects, the method being executed by a first client, the method comprising: Generate first-user-generated content (UGC) data captured by the first user using special effects; Send the first UGC data to the server; And receive from the server a first UGC identifier corresponding to the first UGC data, the first UGC identifier being used to identify the first UGC data shot using the special effects.

2. The method according to claim 1, wherein generating the first UGC data captured by the first user using special effects comprises: In response to the first user starting to shoot using the special effect, a temporary resource folder is generated on the first client. Grant permissions to the temporary resource folder on the special effects side; The address of the temporary resource folder is provided to the special effects side; and the first UGC data is written to the temporary resource folder by the special effects side.

3. The method according to claim 1, wherein sending the first UGC data to the server comprises: In response to the completion of the shooting, the first UGC data is compressed; And sending compressed first UGC data from the first client to the server.

4. The method according to claim 1, further comprising: In response to the first user sharing the first UGC data with the second user of the second client, the first UGC identifier is written into the message; And sending the message carrying the first UGC identifier from the first client to the second client.

5. A method for generating identifiers for special effects, the method being executed by a server, the method comprising: Receive user-generated content (UGC) data generated by the user using special effects from the first client; Based on the first UGC data, a first UGC identifier corresponding to the first UGC data is generated, and the first UGC identifier is used to identify the first UGC data shot using the special effects; and the first UGC identifier is sent to the first client.

6. The method according to claim 5, further comprising: In response to receiving the first UGC data, the first UGC data is converted into the specified form required for review; The server sends the converted first UGC data to the review platform; and the review platform receives the review status of the first UGC data.

7. The method according to claim 6, further comprising: In response to receiving the first UGC identifier from the second client, determine the resource address and review status of the first UGC data corresponding to the first UGC identifier; In response to the audit status meeting predetermined conditions, the system obtains the first UGC data through the resource address; and decompresses and sends the first UGC data from the server to the second client.

8. The method according to claim 7, further comprising: In response to the fact that the audit status does not meet the predetermined conditions, the second client's access to the first UGC data is denied.

9. The method according to claim 7, further comprising: Listen for messages from the second client requesting a specified avatar; And in response to receiving a message requesting a specified avatar, the server sends an image link of the specified avatar to the second client.

10. A method for obtaining special effects, the method being executed by a second client, the method comprising: Send a first UGC identifier corresponding to the first user-generated content (UGC) data to the server, the first UGC data being generated by the first user using special effects to shoot on the first client; receive the first UGC data from the server; and render special effects based on the first UGC data, the second user using the special effects to shoot second UGC data on the second client, and the second user performing special effects interaction on the second client based on the first UGC data and the second UGC data.

11. The method of claim 10, further comprising: The second client receives the first UGC identifier shared by the user from the first client.

12. The method of claim 10, further comprising: The second client receives the first UGC identifier distributed by the server from the server.

13. The method of claim 10, wherein sending the first UGC identifier corresponding to the first UGC data to the server comprises: In response to the user of the second client sending a second bid for the same item, the first UGC identifier is sent from the second client to the server.

14. The method of claim 13, wherein receiving the first UGC data from the server comprises: The resource address from which the second client receives the first UGC data from the server; And based on the resource address, the second client receives the first UGC data from the server.

15. The method of claim 10, further comprising: In response to receiving a touch operation of the second user on the avatar control from the second client, a message specifying an avatar is sent from the second client to the server; The second client receives the image link of the specified avatar from the server; Download the specified avatar based on the image link of the specified avatar; And in response to the successful download of the specified avatar, the specified avatar is displayed on the second client.

16. An apparatus for identifying special effects, the apparatus being deployed on a first client, the apparatus comprising: The UGC data generation module is configured to generate user-generated content (UGC) data captured by the first user using special effects. The UGC data sending module is configured to send the first UGC data to the server; The UGC identifier receiving module is configured to receive a first UGC identifier corresponding to the first UGC data from the server. The first UGC identifier is used to identify the first UGC data shot using the special effects.

17. An apparatus for generating identifiers for special effects, the apparatus being deployed on a server, the apparatus comprising: The UGC data receiving module is configured to receive user-generated content (UGC) data generated by the first user using special effects from the first client. The UGC identifier generation module is configured to generate a first UGC identifier corresponding to the first UGC data based on the first UGC data. The first UGC identifier is used to identify the first UGC data shot using the special effects. And a UGC identifier sending module, configured to send the first UGC identifier to the first client.

18. An apparatus for acquiring special effects, the apparatus being deployed on a second client, the apparatus comprising: The UGC identifier sending module is configured to send a first UGC identifier corresponding to the first user-generated content UGC data to the server, wherein the first UGC data is generated by the user using special effects to shoot on the first client; the UGC data receiving module is configured to receive the first UGC data from the server. The special effects rendering module is configured to render special effects based on the first UGC data, and the second user uses the special effects to capture the second UGC data on the second client. The second user interacts with the special effects based on the first UGC data and the second UGC data on the second client.

19. An electronic device comprising: processor; And a memory coupled to the processor, the memory having instructions stored therein, which, when executed by the processor, cause the electronic device to perform the method according to any one of claims 1-15.

20. A computer-readable storage medium having stored thereon computer-executable instructions, wherein the computer-executable instructions are executed by a processor to implement the method according to any one of claims 1-5.

Images