Data acquisition method and device, electronic equipment, storage medium and program product

Abstract

The embodiment of the invention provides a data acquisition method and device, electronic equipment, a storage medium and a program product. The method comprises the steps that a special effect enabling request for a target special effect is received through a client side, program running data corresponding to the target special effect are obtained, and the program running data comprise a data obtaining method predefined in a data obtaining layer; the data acquisition method is used for calling a data acquisition interface which is pre-created in the data acquisition layer and corresponds to the client; and executing the data acquisition method to call the data acquisition interface through the data acquisition method to obtain target data corresponding to the target special effect. According to the technical scheme provided by the embodiment of the invention, the technical problem that the timeliness of acquiring the data during the operation of the special effect is poor in the prior art is solved, and the data during the operation of the special effect can be acquired in time, so that the special effect can be optimized and adjusted in time.

Description

Technical Field

[0001] This disclosure relates to the field of computer processing technology, and in particular to a data acquisition method, apparatus, electronic device, storage medium, and program product. Background Technology

[0002] With the development of computer vision technology, special effects technology is widely used in various fields, such as film and television production, game development, and advertising design. The operation of special effects involves a large amount of data processing and computation; therefore, timely and accurate acquisition of data during the operation of special effects is crucial to ensuring the quality of the effects.

[0003] In related technologies, data on the runtime of special effects is typically obtained through special effects log files. However, the generation of special effects log files is often delayed, meaning that the corresponding log files are only generated after the special effects have finished running. This prevents developers from obtaining data on the runtime of special effects in real time, thus hindering timely optimization and adjustments to the special effects. Summary of the Invention

[0004] This disclosure provides a data acquisition method, apparatus, electronic device, storage medium, and program product to enable timely acquisition of data during special effects operation, thereby allowing for timely optimization and adjustment of the special effects.

[0005] In a first aspect, embodiments of this disclosure provide a data acquisition method, the method comprising:

[0006] The client receives a request to enable a target effect and obtains program running data corresponding to the target effect. The program running data includes a predefined data acquisition method in the data acquisition layer, which is used to call a data acquisition interface pre-created in the data acquisition layer corresponding to the client.

[0007] The data acquisition method is executed to call the data acquisition interface to obtain target data corresponding to the target effect.

[0008] Secondly, embodiments of this disclosure also provide a data acquisition device, the device comprising:

[0009] The special effects enable request module is used to receive a special effects enable request for a target special effects through a client, and obtain program running data corresponding to the target special effects. The program running data includes a data acquisition method predefined in the data acquisition layer. The data acquisition method is used to call a data acquisition interface pre-created in the data acquisition layer corresponding to the client.

[0010] The target data acquisition module is used to execute the data acquisition method to call the data acquisition interface through the data acquisition method to obtain target data corresponding to the target effect.

[0011] Thirdly, embodiments of this disclosure also provide an electronic device, the electronic device comprising:

[0012] One or more processors;

[0013] Storage device for storing one or more programs.

[0014] When the one or more programs are executed by the one or more processors, the one or more processors implement the data acquisition method as described in any of the embodiments of this disclosure.

[0015] Fourthly, embodiments of this disclosure also provide a storage medium containing computer-executable instructions, which, when executed by a computer processor, are used to perform the data acquisition method as described in any of the embodiments of this disclosure.

[0016] Fifthly, embodiments of this disclosure also provide a computer program product, including a computer program that, when executed by a processor, implements the data acquisition method as described in any of the embodiments of this disclosure.

[0017] The technical solution of this disclosure embodiment receives a special effect activation request for a target special effect from a client, and obtains program running data corresponding to the target special effect. Since the program running data includes a predefined data acquisition method in the data acquisition layer, and this data acquisition method is used to call a data acquisition interface pre-created in the data acquisition layer corresponding to the client, a protocol for acquiring data can be provided by pre-defining the data acquisition method in the program running data and pre-creating the data acquisition interface in the data acquisition layer. This allows the data acquisition method to call the data acquisition method, thereby achieving data acquisition. Moreover, in scenarios requiring the acquisition of multiple special effect data, the data acquisition interface can be called by the data acquisition method corresponding to the object special effect data, supporting the extension of data acquisition methods in the program running data and multi-scenario applications. Subsequently, by executing the data acquisition method, the target data corresponding to the target special effect is obtained by calling the data acquisition interface through the data acquisition method, enabling automatic, convenient, and timely acquisition of the target data. The technical solution of this disclosure embodiment solves the technical problem of poor timeliness in acquiring data during special effect runtime in related technologies, achieving timely acquisition of data during special effect runtime, thereby enabling timely optimization and adjustment of the special effect. Attached Figure Description

[0018] 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. Throughout the drawings, the same or similar reference numerals denote the same or similar elements. It should be understood that the drawings are schematic, and the originals and elements are not necessarily drawn to scale.

[0019] Figure 1 A flowchart illustrating a data acquisition method provided in an embodiment of this disclosure;

[0020] Figure 2 A flowchart illustrating another data acquisition method provided in this embodiment of the disclosure;

[0021] Figure 3 A flowchart illustrating another data acquisition method provided in this embodiment of the disclosure;

[0022] Figure 4 A flowchart illustrating another data acquisition method provided in this embodiment of the disclosure;

[0023] Figure 5 This is a schematic diagram of the structure of a data acquisition device provided in an embodiment of the present disclosure;

[0024] Figure 6 This is a schematic diagram of the structure of an electronic device for implementing an embodiment of the present disclosure. Detailed Implementation

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

[0026] It should be understood that the steps described in the method embodiments of this disclosure may be performed in different orders and / or in parallel. Furthermore, the method embodiments may include additional steps and / or omit the steps shown. The scope of this disclosure is not limited in this respect.

[0027] The term "comprising" and its variations as used herein are open-ended inclusions, meaning "including but not limited to". The term "based on" means "at least partially based on". The term "one embodiment" means "at least one embodiment"; the term "another embodiment" means "at least one additional embodiment"; the term "some embodiments" means "at least some embodiments". Definitions of other terms will be given in the description below.

[0028] It should be noted that the concepts of "first" and "second" mentioned in this disclosure are used only to distinguish different devices, modules or units, and are not used to limit the order of functions performed by these devices, modules or units or their interdependencies.

[0029] It should be noted that the terms "a" and "a plurality of" used in this disclosure are illustrative rather than restrictive, and those skilled in the art should understand that, unless otherwise expressly indicated in the context, they should be understood as "one or more".

[0030] The names of messages or information exchanged between multiple devices in the embodiments of this disclosure are for illustrative purposes only and are not intended to limit the scope of such messages or information.

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

[0032] For example, upon receiving a user's active 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.

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

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

[0035] It is understood that the data involved in this technical solution (including but not limited to the data itself, the acquisition or use of the data) shall comply with the requirements of relevant laws, regulations and related provisions.

[0036] Figure 1This is a flowchart illustrating a data acquisition method provided in an embodiment of the present disclosure. This embodiment is applicable to scenarios where target data corresponding to a target effect is acquired. The method can be executed by a data acquisition device, which can be implemented in the form of software and / or hardware. Optionally, it can be implemented by an electronic device, such as a mobile terminal, a PC, or a server.

[0037] like Figure 1 As shown, the method in this embodiment may specifically include:

[0038] S110. Receive an effect activation request for a target effect through the client, and obtain program running data corresponding to the target effect. The program running data includes a predefined data acquisition method in the data acquisition layer, which is used to call a data acquisition interface pre-created in the data acquisition layer corresponding to the client.

[0039] In this context, the target effect can be understood as the effect that the client needs to enable. In this embodiment, the target effect can be selected according to actual needs, and no specific limitation is made here. The target effect can be applied to the entire screen content of the client's live stream; or, it can be applied to a target object included in the client's live stream screen content to decorate the target object. The target object can be a person or an animal, etc. The effect enable request can be understood as a request to enable the target effect. In this embodiment, the effect enable request can be generated based on an effect triggering operation (e.g., long press, click, or swipe) acting on the target effect. The effect enable request can at least include the effect identifier of the target effect. It is understood that the effect identifier can be used to distinguish different effects. In this embodiment, program running data can be understood as the program code data necessary to support the operation of the target effect. The program running data can include a predefined data acquisition method in the data acquisition layer. It should be noted that a data acquisition method is predefined in the data acquisition layer to obtain the data of the target effect during runtime by executing the data acquisition method.

[0040] In this embodiment, the data acquisition layer can be understood as a software construction layer used to acquire various data generated, used, or processed during the process of a target effect's activation from start to finish. The data acquisition layer can predefine data acquisition methods. These methods can be used to call a pre-created data acquisition interface corresponding to the client within the data acquisition layer. In this embodiment, the number of pre-defined data acquisition methods in the data acquisition layer can be one, two, or more. The position of the data acquisition methods in the data acquisition layer can be set according to actual needs and is not specifically limited here. For example, the data acquisition method can be nested within other methods defined in the data acquisition layer, or it can be relatively independent of other methods defined in the data acquisition layer. In this embodiment, the method parameters of data acquisition methods defined at different positions in the data acquisition layer can be the same or different. It should be noted that the number of method parameters for data acquisition methods defined at different positions in the data acquisition layer is the same.

[0041] The data acquisition interface can be understood as a protocol for acquiring target data corresponding to the target effect. In this embodiment, pre-creating the data acquisition interface in the data acquisition layer not only standardizes data formats and protocols but also allows for customized processing of the target data corresponding to the target effect according to specific needs. Furthermore, it avoids rewriting the data acquisition logic every time a new client is developed, thus saving time and effort and decoupling the client and backend. In this embodiment, the data acquisition interface can be pre-created in the data acquisition layer. Target data can be understood as the data that needs to be acquired from various data generated, used, or processed during the process of the target effect's activation from start to end. In short, it refers to the data during the target effect's runtime; for example, target data could be the target effect's loading time, initialization time, etc.

[0042] In this embodiment of the disclosure, for the program execution data corresponding to the target effect, a data acquisition interface corresponding to the client can be pre-created in the data acquisition layer of the program data. Then, a data acquisition method for calling the data acquisition interface can be pre-defined in the data acquisition layer. Based on this, after the client receives an effect activation request for the target effect, it can obtain program execution data including the data acquisition method pre-defined in the data acquisition layer for calling the pre-created data acquisition interface in the data acquisition layer.

[0043] In this embodiment of the disclosure, before or after acquiring the program running data corresponding to the target effect, the method may further include: receiving a method editing operation on a data acquisition method in the program running data, and updating the data acquisition method in the program running data according to the method editing operation. The method editing operation may include at least one of a method addition operation, a method modification operation, and a method deletion operation. A method addition operation can be understood as adding a data acquisition method to the data acquisition layer in the program running data. A method modification operation can be understood as modifying a data acquisition method already defined in the data acquisition layer of the program running data. Specifically, a method modification operation can be used to modify the method parameters of a data acquisition method from the current method parameters to target method parameters, where the target method parameters can be understood as the modified method parameters of the data acquisition method. A method deletion operation can be understood as deleting a data acquisition method already defined in the data acquisition layer of the program running data.

[0044] Optionally, updating the data acquisition method in the program running data according to the method editing operation may include: displaying a target list, wherein the target list may include method identifiers of at least one candidate data acquisition method; and in response to an identifier triggering operation for the method identifier, adding the data acquisition method corresponding to the triggered method identifier to the target position in the program running data, thereby enabling the function of adding data acquisition methods in the program running data in a visual manner.

[0045] The target list can be understood as a list of method identifiers for providing candidate data acquisition methods. Candidate data acquisition methods can be understood as predefined data acquisition methods that can call the data acquisition interface. The number of candidate data acquisition methods can be one, two, or more. The method identifier can be used to distinguish different data acquisition methods. In this embodiment, the method identifier can be the concatenation result of the method parameters of the data acquisition method; or, it can be the functional description information of the data acquisition method. The identifier triggering operation can be understood as a triggering operation used to add the data acquisition method corresponding to the triggered method identifier to the target position in the program running data. Optionally, the identifier triggering operation can be an identifier selection operation (e.g., a click operation, a long press operation, etc.). The target position can be understood as the position in the program running data where the data acquisition method corresponding to the triggered method identifier needs to be added. In this embodiment, the target position can be the position in the data acquisition layer of the program running data. The target position can be represented by line information of the program code.

[0046] In this embodiment of the disclosure, the method of displaying the target list can specifically involve pre-defining one or more data acquisition methods that can call the data acquisition interface, i.e., candidate data acquisition methods. Then, the method identifiers of the candidate data acquisition methods can be determined. Subsequently, a target list can be generated based on the method identifiers. After generating the target list, the target list can be displayed. Based on this, upon receiving an identifier trigger operation for a method identifier, the triggered method identifier and the target position in the program execution data can be determined. Therefore, based on the correspondence between the method identifier and the data acquisition method, the data acquisition method corresponding to the triggered method identifier can be determined. After determining the data acquisition method corresponding to the triggered method identifier, the data acquisition method corresponding to the triggered method identifier can be added to the target position in the program execution data.

[0047] Based on the above embodiments, after displaying the target list, it may further include: receiving a method editing operation for the data acquisition method through the target list, and updating the data acquisition method associated with the target list and / or the method identifier in the target list based on the method editing operation.

[0048] Specifically, a preset interface is displayed, which may include a target list and a method editing control. In response to a control trigger operation on the method control, the data acquisition methods associated with the target list and / or the method identifiers in the target list are updated based on the control trigger operation.

[0049] As an optional implementation of this invention, the method editing control may include a method adding control. After receiving a control trigger operation applied to the method adding control, a method editing area for editing data acquisition methods is displayed in the preset interface. Edited data acquisition methods can be received through the method editing area; or, in response to a selection operation of a method component for generating a data acquisition method applied to the method editing area, a new data acquisition method is obtained, and the method identifier of the new data acquisition method is added to the target list; wherein, the method component can be used to edit the method parameters of the data acquisition method. Based on this, after adding the method identifier of the new data acquisition method to the target list, the new data acquisition method can also be modified and / or deleted; if the method identifier of the modified data acquisition method changes, or if a new data acquisition method is deleted, the method identifier in the target list can be updated. If the method identifier of the modified data acquisition method does not change, the method identifier in the target list does not need to be updated.

[0050] As another optional implementation of this disclosure, the method editing control may include a method modification control, which corresponds to a method identifier in the target list. After receiving a control trigger operation applied to the method modification control, the method identifier corresponding to the triggered method modification control can be determined. This allows the display of the data acquisition method corresponding to the method identifier. After receiving a method modification operation for the data acquisition method, the modified data acquisition method can be obtained. If the method identifier of the modified data acquisition method has changed, the target list can be updated based on the modified method identifier. If the method identifier of the modified data acquisition method has not changed, the method identifiers in the target list do not need to be updated.

[0051] As another optional implementation of this disclosure, the method editing control may include a method deletion control, which corresponds to a method identifier in the target list. Upon receiving a control trigger operation applied to the method deletion control, the method identifier corresponding to the triggered method deletion control can be determined, and the method identifier in the target list can be deleted.

[0052] S120. Execute the data acquisition method to call the data acquisition interface through the data acquisition method to obtain target data corresponding to the target effect.

[0053] Specifically, the data acquisition method is executed, and its method parameters are passed to the interface parameters of the data acquisition interface, so that the interface parameters of the data acquisition interface become the method parameters of the data acquisition method. After the parameter passing is complete, the method parameters of the data acquisition method can be passed as actual parameters to the formal parameters of the implementation method of the data acquisition interface through the data acquisition interface. After the parameter passing is complete, the target data corresponding to the target effect can be obtained by executing the implementation method of the data acquisition interface.

[0054] In this embodiment of the disclosure, the data acquisition method can be nested within other methods defined in the data acquisition layer, or it can be relatively independent of other methods defined in the data acquisition layer.

[0055] As an optional implementation in this disclosure, when the data acquisition method is nested within other methods defined in the data acquisition layer, and the other methods are executed, the data acquisition method can be executed when the data acquisition method is reached, so as to obtain the target data corresponding to the target effect by calling the data acquisition interface through the data acquisition method.

[0056] As another optional implementation method in this disclosure embodiment, if the data acquisition method is not nested within other methods defined in the data acquisition layer, the data acquisition method is executed according to the top-to-bottom execution order of the program code, and when the code statement of the data acquisition method is executed, the data acquisition method is called through the data acquisition method to obtain the target data corresponding to the target effect.

[0057] In this embodiment of the disclosure, the data acquisition layer may include a software development kit (SDK) layer. It is understood that the software development kit layer can be understood as the level at which the software development kit (SDK) is located during the software development process. Before executing the data acquisition method, the method may further include: creating a data acquisition interface corresponding to the client in the software development kit layer according to a preset data acquisition protocol and the program runtime environment corresponding to the client.

[0058] The preset data acquisition protocol can be understood as a data format pre-set for different program operating environments. The preset data acquisition protocol can be used to create data acquisition interfaces in different program environments. In this embodiment, the preset data acquisition protocol can be set according to actual needs and is not limited thereto. The program operating environment may include the client's operating system. In this embodiment, data acquisition protocols can be set for different operating systems, and a data acquisition interface corresponding to the client can be created in the software development kit layer. This setting improves the compatibility of acquiring target data corresponding to the target effect and ensures the stability and reliability of the data acquisition method in different environments.

[0059] The technical solution of this disclosure embodiment receives a special effect activation request for a target special effect from a client, and obtains program running data corresponding to the target special effect. Since the program running data includes a predefined data acquisition method in the data acquisition layer, and this data acquisition method is used to call a data acquisition interface pre-created in the data acquisition layer corresponding to the client, a protocol for acquiring data can be provided by pre-defining the data acquisition method in the program running data and pre-creating the data acquisition interface in the data acquisition layer. This allows the data acquisition method to call the data acquisition method, thereby achieving data acquisition. Moreover, in scenarios requiring the acquisition of multiple special effect data, the data acquisition interface can be called by the data acquisition method corresponding to the object special effect data, supporting the extension of data acquisition methods in the program running data and multi-scenario applications. Subsequently, by executing the data acquisition method, the target data corresponding to the target special effect is obtained by calling the data acquisition interface through the data acquisition method, enabling automatic, convenient, and timely acquisition of the target data. The technical solution of this disclosure embodiment solves the technical problem of poor timeliness in acquiring data during special effect runtime in related technologies, achieving timely acquisition of data during special effect runtime, thereby enabling timely optimization and adjustment of the special effect.

[0060] Figure 2 This is a flowchart illustrating another data acquisition method provided in this embodiment. Based on the above embodiments, this embodiment further refines the method of executing the data acquisition method to obtain target data corresponding to the target effect by calling the data acquisition interface through the data acquisition method. Optionally, the data acquisition layer includes a software development kit (SDK) layer; executing the data acquisition method to obtain target data corresponding to the target effect by calling the data acquisition interface through the data acquisition method includes: executing the data acquisition method predefined in the SSD layer to call the data acquisition interface in the SSD layer through the data acquisition method, and obtaining the target data corresponding to the target effect from the SSD layer. For detailed implementation, please refer to the description of this embodiment. Technical features that are the same as or similar to those in the foregoing embodiments will not be repeated here. Figure 2 As shown, the method in this embodiment may specifically include:

[0061] S210. Receive an effect activation request for a target effect through the client, and obtain program running data corresponding to the target effect. The program running data includes a predefined data acquisition method in the data acquisition layer. The data acquisition method is used to call a data acquisition interface pre-created in the data acquisition layer corresponding to the client. The data acquisition layer includes a software development kit layer.

[0062] S220. Execute the data acquisition method predefined in the software development kit layer to call the data acquisition interface in the software development kit layer through the data acquisition method, and obtain the target data corresponding to the target effect from the software development kit layer.

[0063] In this embodiment of the invention, the data acquisition interface corresponding to the client is pre-created in the software development kit layer, which can help realize effective communication between the client and the backend service or data source, improve development efficiency, and enhance data security.

[0064] In this embodiment, a data acquisition method and a pre-created data acquisition interface corresponding to the client are predefined in the software development kit (SDK) layer. When the data acquisition method predefined in the SSD layer is executed, the method parameters of the data acquisition method are passed to the interface parameters of the data acquisition interface, so that the interface parameters of the data acquisition interface are the method parameters of the data acquisition method. After the parameter passing is completed, the method parameters of the data acquisition method can be passed as actual parameters to the formal parameters of the implementation method of the data acquisition interface through the data acquisition interface. After the parameter passing is completed, the target data corresponding to the target effect in the SSD layer can be obtained by executing the implementation method of the data acquisition interface, thus realizing the acquisition of runtime data of the target effect through the data acquisition method predefined in the SSD layer.

[0065] The technical solution of this disclosure embodiment, by executing the data acquisition method predefined in the software development kit layer, calls the data acquisition interface in the software development kit layer through the data acquisition method, and obtains the target data corresponding to the target effect from the software development kit layer, thereby realizing the function of obtaining the target data corresponding to the target effect data through the predefined data acquisition method in the software development kit layer.

[0066] Figure 3This is a flowchart illustrating another data acquisition method provided in this embodiment. Based on the above embodiments, this embodiment further refines the method of executing the data acquisition method to obtain target data corresponding to the target effect by calling the data acquisition interface through the data acquisition method. Optionally, the data acquisition layer includes a software development kit (SDK) layer and a script layer; the data acquisition interface is created in the SSD layer and bound to the script layer; the data acquisition method is predefined in the script layer; executing the data acquisition method to obtain target data corresponding to the target effect by calling the data acquisition interface through the data acquisition method includes: executing the predefined data acquisition method in the script layer to call the data acquisition interface in the software toolkit through the data acquisition method, and obtaining the target data corresponding to the target effect from the script layer. For detailed implementation, please refer to the description of this embodiment. Technical features that are the same as or similar to those in the foregoing embodiments will not be repeated here. Figure 3 As shown, the method in this embodiment may specifically include:

[0067] S310. Receive an effect activation request for a target effect through the client, and obtain program running data corresponding to the target effect. The program running data includes a predefined data acquisition method in the data acquisition layer. The data acquisition method is used to call a pre-created data acquisition interface corresponding to the client in the data acquisition layer. The data acquisition layer includes a software development kit layer and a script layer. The data acquisition interface is created in the software development kit layer and bound to the script layer. The data acquisition method is predefined in the script layer.

[0068] The data acquisition layer can include a software development kit (SDK) layer and a script layer. The script layer can be understood as the level at which the special effects file for the target effect resides during software development. It's important to note that the SSD layer lies below the script layer. The SSD layer provides various tools and libraries to the script layer, allowing developers to directly use these tools and libraries without writing code from scratch, thus simplifying the special effects development process. The SSD layer can be understood as the layer containing the basic processing logic for implementing the target special effects. This basic processing logic can be common to multiple special effects. The script layer can be understood as the layer containing the private (custom) special effects processing logic for implementing the target special effects.

[0069] In this embodiment of the disclosure, the data acquisition interface is created in the software development kit (SDK) layer. If a data acquisition method is predefined in the script layer, to reduce repetitive coding, the data acquisition interface created in the SSD layer can be bound to the script layer. This allows the predefined data acquisition method in the script layer to call the SSD layer's data acquisition interface to obtain the target data corresponding to the target effect.

[0070] S320. Execute the data acquisition method predefined in the script layer to call the data acquisition interface in the software toolkit through the data acquisition method to obtain the target data corresponding to the target effect from the script layer.

[0071] Specifically, when the data acquisition method predefined in the script layer is executed, the script layer interface corresponding to the data acquisition method can be determined. This script layer interface is bound to the data acquisition interface in the software toolkit via a binding method. Based on this, the method parameters of the data acquisition method can be passed to the interface parameters of the data acquisition interface in the software toolkit through the binding method. After the parameter passing is complete, the method parameters of the data acquisition method can be passed to the implementation method of the data acquisition interface through the data acquisition interface in the software toolkit. After the parameter passing, the target data corresponding to the target effect can be obtained from the script layer by executing the implementation method of the data acquisition interface.

[0072] Based on the above embodiments, in this embodiment, a data acquisition method can be predefined in the software toolkit layer. This data acquisition method can then call a pre-created data acquisition interface in the software toolkit to obtain target data corresponding to the target effect from the software development kit layer. The advantage of this approach is that it allows the data acquisition methods predefined in the script layer and those predefined in the software development kit layer to use a unified data acquisition interface, ensuring data consistency.

[0073] The technical solution of this disclosure embodiment includes a data acquisition layer comprising a software development kit (SDK) layer and a script layer; a data acquisition interface is created in the SSD layer and bound to the script layer; a data acquisition method is predefined in the script layer; by executing the predefined data acquisition method in the script layer, the data acquisition interface in the SSD is called through the data acquisition method to obtain target data corresponding to the target effect from the script layer, thereby realizing the function of obtaining target data corresponding to the target effect data by predefining a data acquisition method in the script layer.

[0074] Figure 4 This is a flowchart illustrating another data acquisition method provided in this embodiment. Based on the above embodiments, this embodiment further refines the method of executing the data acquisition method to obtain target data corresponding to the target effect by calling the data acquisition interface through the data acquisition method. Optionally, executing the data acquisition method to obtain target data corresponding to the target effect by calling the data acquisition interface through the data acquisition method includes: executing the data acquisition method to obtain a response message corresponding to the data acquisition method by calling the data acquisition interface through the data acquisition method; wherein the response message includes a message identifier and a message content; the message content includes an effect identifier and effect data; when the client receives the response message, the message identifier and the effect identifier in the response message are verified; if both the message identifier and the effect identifier pass verification, the target data corresponding to the target effect is determined according to the response message. For detailed implementation, please refer to the description of this embodiment. Technical features that are the same as or similar to those in the foregoing embodiments will not be repeated here. Figure 4 As shown, the method in this embodiment may specifically include:

[0075] S410. Receive an effect activation request for a target effect through the client, and obtain program running data corresponding to the target effect. The program running data includes a predefined data acquisition method in the data acquisition layer, which is used to call a data acquisition interface pre-created in the data acquisition layer corresponding to the client.

[0076] S420. Execute the data acquisition method to call the data acquisition interface through the data acquisition method to obtain a response message corresponding to the data acquisition method, wherein the response message includes a message identifier and a message content, and the message content includes an effect identifier and effect data.

[0077] The response message can be understood as the response result obtained after executing the data acquisition method. The response message may include a message identifier and message content. In this embodiment, the data structure of the response message is determined based on the interface parameters of the data acquisition interface. In this embodiment, the interface parameters of the data acquisition interface include a message identifier and message content. Accordingly, the response message consists of a message identifier and message content. In this embodiment, the message identifier can be used to distinguish the type of response message. The message content may include an effect identifier and effect data. The effect identifier can be used to distinguish different effects.

[0078] In this embodiment of the disclosure, special effects data can be obtained based on the method parameters of the data acquisition method defined in the data acquisition layer. For example, if there is only one piece of data corresponding to the method parameter of the data acquisition method, then the data corresponding to the method parameter can be determined as special effects data. If there are multiple pieces of data corresponding to the method parameter of the data acquisition method, the data corresponding to the method parameter can be concatenated using a preset concatenation operator (e.g., "+", "-", etc.), and the concatenated result can be used as special effects data.

[0079] Specifically, executing the data acquisition method involves calling the data acquisition interface to first obtain special effects identifiers and special effects data, and then combining the obtained special effects identifiers and data to obtain the message content. Subsequently, based on the message content and the message identifier set for the message, a response message can be generated, i.e., the response message corresponding to the data acquisition method is obtained.

[0080] S430. When the client receives the response message, the message identifier and the effect identifier in the response message are verified. If both the message identifier and the effect identifier pass the verification, the target data corresponding to the target effect is determined according to the response message.

[0081] Specifically, when the client receives the response message, it can verify the message identifier and the effect identifier in the response message. If both the message identifier and the effect identifier pass verification, the response message can be identified as the target data corresponding to the target effect. Alternatively, the message content can be extracted from the response message, and the target data corresponding to the target effect can be obtained based on the extracted message content.

[0082] In this embodiment of the disclosure, verifying the message identifier and the effect identifier in the response message may include: verifying the message identifier in the response message according to a preset identifier, and verifying the effect identifier in the response message according to the effect identifier of the target effect. The preset identifier can be used to verify the message identifier in the response message to determine the type of the response message. The preset identifier corresponds to the data type of the data obtained from the data acquisition layer.

[0083] For example, a consistency comparison can be performed between the preset identifier and the message identifier in the response message, and a consistency comparison can be performed between the effect identifier of the target effect and the effect identifier in the response message. If the comparisons are consistent, it can be determined that both the message identifier and the effect identifier have passed verification.

[0084] The technical solution of this disclosure embodiment, by executing the data acquisition method, calls the data acquisition interface through the data acquisition method to obtain a response message corresponding to the data acquisition method; wherein, the response message includes a message identifier and a message content; the message content includes an effect identifier and effect data; when the client receives the response message, the message identifier and the effect identifier in the response message are verified; if both the message identifier and the effect identifier pass the verification, the target data corresponding to the target effect is determined according to the response message, thereby realizing the function of verifying the message identifier and the effect identifier before obtaining the target data corresponding to the target effect, so as to ensure the data security of the target data.

[0085] Figure 5 This is a schematic diagram of the structure of a data acquisition device provided in an embodiment of the present disclosure, as shown below. Figure 5 As shown, the device includes: a special effects activation request module 510 and a target data acquisition module 520. The special effects activation request module 510 is used to receive a special effects activation request for a target special effects through a client, and acquire program running data corresponding to the target special effects. The program running data includes a predefined data acquisition method in a data acquisition layer, which is used to call a pre-created data acquisition interface corresponding to the client in the data acquisition layer. The target data acquisition module 520 is used to execute the data acquisition method to call the data acquisition interface through the data acquisition method to obtain target data corresponding to the target special effects.

[0086] The technical solution of this embodiment involves a special effects activation request module 510 receiving a special effects activation request for a target special effects through a client, and obtaining program running data corresponding to the target special effects. Since the program running data includes a predefined data acquisition method in the data acquisition layer, and this data acquisition method is used to call a data acquisition interface pre-created in the data acquisition layer corresponding to the client, a protocol for acquiring data can be provided by pre-defining data acquisition methods in the program running data and pre-creating data acquisition interfaces in the data acquisition layer. This allows the data acquisition method to be called, thereby achieving data acquisition. Furthermore, in scenarios requiring the acquisition of multiple special effects data, the data acquisition interface can be called by the data acquisition method corresponding to the object special effects data, supporting the extension of data acquisition methods in the program running data and multi-scenario applications. Subsequently, the target data acquisition module 520 executes the data acquisition method to call the data acquisition interface, obtaining the target data corresponding to the target special effects, enabling automatic, convenient, and timely acquisition of target data. The technical solution of this disclosure addresses the technical problem of poor timeliness in obtaining data during special effects operation in related technologies, and enables timely acquisition of data during special effects operation, thereby allowing for timely optimization and adjustment of special effects.

[0087] Based on any optional technical solution in the embodiments of this disclosure, the data acquisition layer may optionally include a software development kit (SDK) layer; the target data acquisition module 520 may be used to execute the data acquisition method predefined in the SSD layer, so as to call the data acquisition interface in the SSD layer through the data acquisition method to obtain target data corresponding to the target effect from the SSD layer.

[0088] Based on any optional technical solution in the embodiments of this disclosure, optionally, the data acquisition layer includes a software development kit (SDK) layer and a script layer; the data acquisition interface is created in the SSD layer and bound to the script layer; the data acquisition method is predefined in the script layer; the target data acquisition module 520 can be used to execute the data acquisition method predefined in the script layer, so as to call the data acquisition interface in the SSD layer through the data acquisition method to obtain target data corresponding to the target effect from the script layer.

[0089] Optionally, based on any of the optional technical solutions in the embodiments of this disclosure, the data acquisition device further includes an interface creation module. The interface creation module can be used to create a data acquisition interface corresponding to the client in the software development kit layer, according to a preset data acquisition protocol and the program runtime environment corresponding to the client, before executing the data acquisition method, in the software development kit layer.

[0090] Optionally, based on any of the optional technical solutions in the embodiments of this disclosure, the data acquisition device further includes a method editing module. The method editing module can be used to receive a method editing operation on a data acquisition method in the program running data before or after acquiring the program running data corresponding to the target effect, and update the data acquisition method in the program running data according to the method editing operation. The method editing operation includes at least one of a method addition operation, a method modification operation, and a method deletion operation.

[0091] Based on any optional technical solution in the embodiments of this disclosure, optionally, the method editing module can be used to display a target list, wherein the target list includes method identifiers of at least one candidate data acquisition method; in response to an identifier triggering operation for the method identifier, the data acquisition method corresponding to the triggered method identifier is added to the target position in the program running data.

[0092] Optionally, based on any of the optional technical solutions in the embodiments of this disclosure, the data acquisition device further includes a list update module. The list update module is configured to, after the target list is displayed, receive a method editing operation for the data acquisition method through the target list, and update the data acquisition method associated with the target list and / or the method identifier in the target list based on the method editing operation.

[0093] Based on any optional technical solution in the embodiments of this disclosure, optionally, the target data acquisition module 520 is specifically used to execute the data acquisition method to call the data acquisition interface through the data acquisition method to obtain a response message corresponding to the data acquisition method; wherein, the response message includes a message identifier and a message content; the message content includes an effect identifier and effect data; when the client receives the response message, the message identifier and the effect identifier in the response message are verified, and if both the message identifier and the effect identifier pass the verification, the target data corresponding to the target effect is determined according to the response message.

[0094] Optionally, based on any of the optional technical solutions in the embodiments of this disclosure, the target data acquisition module 520 includes a message verification unit. The message verification unit is configured to verify the message identifier in the response message according to a preset identifier, and to verify the effect identifier in the response message according to the effect identifier of the target effect.

[0095] The data acquisition device provided in this disclosure can execute the data acquisition method provided in any embodiment of this disclosure, and has the corresponding functional modules and beneficial effects for executing the data acquisition method.

[0096] It is worth noting that the various units and modules included in the above-mentioned device are only divided according to functional logic, but are not limited to the above division, as long as the corresponding functions can be realized; in addition, the specific names of each functional unit are only for easy differentiation and are not used to limit the protection scope of the embodiments of this disclosure.

[0097] The following is for reference. Figure 6 The diagram illustrates a structural schematic of an electronic device (e.g., a terminal device or a server) 600 suitable for implementing embodiments of the present disclosure. The terminal device in the embodiments of the present disclosure may include, but is not limited to, mobile terminals such as mobile phones, laptops, digital broadcast receivers, PDAs (personal digital assistants), PADs (tablet computers), PMPs (portable multimedia players), in-vehicle terminals (e.g., in-vehicle navigation terminals), and fixed terminals such as digital TVs and desktop computers. Figure 6 The electronic device shown is merely an example and should not be construed as limiting the functionality and scope of the embodiments disclosed herein.

[0098] like Figure 6 As shown, electronic device 600 may include a processing device (e.g., a central processing unit, a graphics processor, etc.) 601, which can perform various appropriate actions and processes according to a program stored in read-only memory (ROM) 602 or a program loaded from storage device 606 into random access memory (RAM) 603. RAM 603 also stores various programs and data required for the operation of electronic device 600. Processing device 601, ROM 602, and RAM 603 are interconnected via bus 604. Input / output (I / O) interface 605 is also connected to bus 604.

[0099] Typically, the following devices can be connected to I / O interface 605: input devices 606 including, for example, touchscreens, touchpads, keyboards, mice, cameras, microphones, accelerometers, gyroscopes, etc.; output devices 607 including, for example, liquid crystal displays (LCDs), speakers, vibrators, etc.; storage devices 608 including, for example, magnetic tapes, hard disks, etc.; and communication devices 609. Communication device 609 allows electronic device 600 to communicate wirelessly or wiredly with other devices to exchange data. Although Figure 6 An electronic device 600 with various devices is shown; however, it should be understood that it is not required to implement or possess all of the devices shown. More or fewer devices may be implemented or possessed alternatively.

[0100] In particular, according to embodiments of this disclosure, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, embodiments of this disclosure include a computer program product comprising a computer program carried on a non-transitory computer-readable medium, the computer program containing program code for performing the methods shown in the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network via a communication device 609, or installed from a storage device 608, or installed from a ROM 602. When the computer program is executed by the processing device 601, it performs the functions defined in the methods of embodiments of this disclosure.

[0101] The names of messages or information exchanged between multiple devices in the embodiments of this disclosure are for illustrative purposes only and are not intended to limit the scope of such messages or information.

[0102] The electronic device provided in this disclosure and the data acquisition method provided in the above embodiments belong to the same inventive concept. Technical details not described in detail in this disclosure can be found in the above embodiments, and this embodiment has the same beneficial effects as the above embodiments.

[0103] This disclosure provides a computer storage medium storing a computer program that, when executed by a processor, implements the data acquisition method provided in the above embodiments.

[0104] It should be noted that the computer-readable medium described in this disclosure can be a computer-readable signal medium or a computer-readable storage medium, or any combination thereof. A computer-readable storage medium can be, for example,—but not limited to—an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of a computer-readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer disk, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination thereof. In this disclosure, a computer-readable storage medium can be any tangible medium containing or storing a program that can be used by or in connection with an instruction execution system, apparatus, or device. In this disclosure, a computer-readable signal medium can include a data signal propagated in baseband or as part of a carrier wave, carrying computer-readable program code. Such propagated data signals can take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. A computer-readable signal medium can be any computer-readable medium other than a computer-readable storage medium, which can send, propagate, or transmit a program for use by or in connection with an instruction execution system, apparatus, or device. The program code contained on the computer-readable medium can be transmitted using any suitable medium, including but not limited to: wires, optical fibers, RF (radio frequency), etc., or any suitable combination thereof.

[0105] According to one or more embodiments of this disclosure, [Example 1] provides a data acquisition method, including:

[0106] The client receives a request to enable a target effect and obtains program running data corresponding to the target effect. The program running data includes a predefined data acquisition method in the data acquisition layer, which is used to call a data acquisition interface pre-created in the data acquisition layer corresponding to the client.

[0107] The data acquisition method is executed to call the data acquisition interface to obtain target data corresponding to the target effect.

[0108] According to one or more embodiments of this disclosure, Example 2 provides the method of Example 1, further comprising: optionally,

[0109] The data acquisition layer includes a software development kit (SDK) layer; the execution of the data acquisition method to call the data acquisition interface through the data acquisition method to obtain target data corresponding to the target effect includes: executing the data acquisition method predefined in the SSD layer to call the data acquisition interface in the SSD layer through the data acquisition method to obtain target data corresponding to the target effect from the SSD layer.

[0110] According to one or more embodiments of this disclosure, Example 3 provides the method of Example 1, further comprising: optionally,

[0111] The data acquisition layer includes a software development kit (SDK) layer and a script layer; the data acquisition interface is created in the SSD layer and bound to the script layer; the data acquisition method is predefined in the script layer; executing the data acquisition method to call the data acquisition interface through the data acquisition method to obtain target data corresponding to the target effect includes: executing the data acquisition method predefined in the script layer to call the data acquisition interface in the SSD layer through the data acquisition method to obtain target data corresponding to the target effect from the script layer.

[0112] According to one or more embodiments of this disclosure, Example 4 provides the method of Example 1, further comprising: optionally,

[0113] The data acquisition layer includes a software development kit layer; prior to executing the data acquisition method, it also includes:

[0114] Based on the preset data acquisition protocol and the program runtime environment corresponding to the client, a data acquisition interface corresponding to the client is created in the software development kit layer.

[0115] According to one or more embodiments of this disclosure, Example 5 provides the method of Example 1, further comprising: optionally,

[0116] Before or after acquiring the program running data corresponding to the target effect, the method further includes: receiving a method editing operation for the data acquisition method in the program running data, and updating the data acquisition method in the program running data according to the method editing operation, wherein the method editing operation includes at least one of a method addition operation, a method modification operation, and a method deletion operation.

[0117] According to one or more embodiments of this disclosure, Example Six provides the method of Example One, further comprising: optionally,

[0118] The method for updating the data acquisition method in the program running data according to the method editing operation includes: displaying a target list, wherein the target list includes method identifiers of at least one candidate data acquisition method; and, in response to an identifier triggering operation for the method identifier, adding the data acquisition method corresponding to the triggered method identifier to the target position in the program running data.

[0119] According to one or more embodiments of this disclosure, Example 7 provides the method of Example 1, which further includes: optionally,

[0120] After displaying the target list, the method further includes: receiving a method editing operation for the data acquisition method through the target list, and updating the data acquisition method associated with the target list and / or the method identifier in the target list based on the method editing operation.

[0121] According to one or more embodiments of this disclosure, Example 8 provides the method of Example 1, further comprising: optionally,

[0122] The step of executing the data acquisition method to obtain target data corresponding to the target effect by calling the data acquisition interface through the data acquisition method includes: executing the data acquisition method to obtain a response message corresponding to the data acquisition method by calling the data acquisition interface through the data acquisition method; wherein, the response message includes a message identifier and a message content; the message content includes an effect identifier and effect data; when the client receives the response message, the message identifier and the effect identifier in the response message are verified, and if both the message identifier and the effect identifier pass the verification, the target data corresponding to the target effect is determined according to the response message.

[0123] According to one or more embodiments of this disclosure, Example 9 provides the method of Example 1, further comprising: optionally,

[0124] The verification of the message identifier and the effect identifier in the response message includes: verifying the message identifier in the response message according to a preset identifier, and verifying the effect identifier in the response message according to the effect identifier of the target effect.

[0125] According to one or more embodiments of this disclosure, [Example 10] provides a data acquisition apparatus, including:

[0126] The special effects enable request module is used to receive a special effects enable request for a target special effects through a client, and obtain program running data corresponding to the target special effects. The program running data includes a data acquisition method predefined in the data acquisition layer. The data acquisition method is used to call a data acquisition interface pre-created in the data acquisition layer corresponding to the client.

[0127] The target data acquisition module is used to execute the data acquisition method to call the data acquisition interface through the data acquisition method to obtain target data corresponding to the target effect.

[0128] In some implementations, clients and servers can communicate using any currently known or future-developed network protocol such as HTTP (Hypertext Transfer Protocol) and can interconnect with digital data communication (e.g., communication networks) of any form or medium. Examples of communication networks include local area networks (“LANs”), wide area networks (“WANs”), the Internet (e.g., the Internet of Things), and peer-to-peer networks (e.g., ad hoc peer-to-peer networks), as well as any currently known or future-developed networks.

[0129] The aforementioned computer-readable medium may be included in the aforementioned electronic device; or it may exist independently and not assembled into the electronic device.

[0130] The aforementioned computer-readable medium carries one or more programs. When the one or more programs are executed by the electronic device, the electronic device causes the following: receiving an effect activation request for a target effect through a client; obtaining program running data corresponding to the target effect, wherein the program running data includes a predefined data acquisition method in a data acquisition layer, the data acquisition method being used to call a pre-created data acquisition interface corresponding to the client in the data acquisition layer; and executing the data acquisition method to obtain target data corresponding to the target effect by calling the data acquisition interface through the data acquisition method.

[0131] Computer program code for performing the operations of this disclosure can be written in one or more programming languages ​​or a combination thereof, including but not limited to object-oriented programming languages ​​such as Java, Smalltalk, and C++, as well as conventional procedural programming languages ​​such as the "C" language or similar programming languages. The program code can be executed 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 remote computers, the remote computer can 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 can be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0132] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of this disclosure. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated 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, can be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.

[0133] The units described in the embodiments of this disclosure can be implemented in software or in hardware. The names of the units are not necessarily limiting in certain circumstances; for example, a target data acquisition module can also be described as "a module for acquiring target data corresponding to the target effect".

[0134] The functions described above in this document can be performed, at least in part, by one or more hardware logic components. For example, exemplary types of hardware logic components that can be used, without limitation, include: Field Programmable Gate Arrays (FPGAs), Application-Specific Integrated Circuits (ASICs), Application Standard Products (ASSPs), System-on-Chip (SoCs), Complex Programmable Logic Devices (CPLDs), and so on.

[0135] In the context of this disclosure, a machine-readable medium can be a tangible medium that may contain or store a program for use by or in conjunction with an instruction execution system, apparatus, or device. A machine-readable medium can be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium can be, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination of the foregoing. More specific examples of machine-readable storage media include electrical connections based on one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing.

[0136] The above description is merely a preferred embodiment of this disclosure and an explanation of the technical principles employed. Those skilled in the art should understand that the scope of this disclosure is not limited to technical solutions formed by specific combinations of the above-described technical features, but should also cover other technical solutions formed by arbitrary combinations of the above-described technical features or their equivalents without departing from the above-described concept. For example, technical solutions formed by substituting the above features with (but not limited to) technical features disclosed in this disclosure that have similar functions.

[0137] Furthermore, while the operations are described in a specific order, this should not be construed as requiring these operations to be performed in the specific order shown or in a sequential order. In certain environments, multitasking and parallel processing may be advantageous. Similarly, while several specific implementation details are included in the above discussion, these should not be construed as limiting the scope of this disclosure. Certain features described in the context of individual embodiments may also be implemented in combination in a single embodiment. Conversely, various features described in the context of a single embodiment may also be implemented individually or in any suitable sub-combination in multiple embodiments.

[0138] Although the subject matter 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 data acquisition method, characterized in that, include: The client receives a request to enable a target effect and obtains program running data corresponding to the target effect. The program running data includes a predefined data acquisition method in the data acquisition layer, which is used to call a data acquisition interface pre-created in the data acquisition layer corresponding to the client. The data acquisition method is executed to call the data acquisition interface to obtain target data corresponding to the target effect.

2. The data acquisition method according to claim 1, characterized in that, The data acquisition layer includes a software development kit layer; the execution of the data acquisition method, to call the data acquisition interface through the data acquisition method to obtain target data corresponding to the target effect, includes: The data acquisition method predefined in the software development kit layer is executed to call the data acquisition interface in the software development kit layer through the data acquisition method, and to obtain the target data corresponding to the target effect from the software development kit layer.

3. The data acquisition method according to claim 1, characterized in that, The data acquisition layer includes a software development kit (SDK) layer and a script layer; the data acquisition interface is created in the SSD layer and bound to the script layer; the data acquisition method is predefined in the script layer. The execution of the data acquisition method, which calls the data acquisition interface through the data acquisition method to obtain target data corresponding to the target effect, includes: The predefined data acquisition method in the script layer is executed to call the data acquisition interface in the software toolkit through the data acquisition method, and to obtain the target data corresponding to the target effect from the script layer.

4. The data acquisition method according to claim 1, characterized in that, The data acquisition layer includes a software development kit layer; prior to executing the data acquisition method, it also includes: Based on the preset data acquisition protocol and the program runtime environment corresponding to the client, a data acquisition interface corresponding to the client is created in the software development kit layer.

5. The data acquisition method according to claim 1, characterized in that, Before or after acquiring the program execution data corresponding to the target special effect, the method further includes: The system receives a method editing operation on a data acquisition method in the program's runtime data, and updates the data acquisition method in the program's runtime data according to the method editing operation. The method editing operation includes at least one of a method addition operation, a method modification operation, and a method deletion operation.

6. The data acquisition method according to claim 5, characterized in that, The method for obtaining data that updates the program runtime data according to the method of editing operations includes: Display a target list, wherein the target list includes method identifiers for at least one candidate data acquisition method; In response to an identifier trigger operation for a method identifier, a data acquisition method corresponding to the triggered method identifier is added to the target location in the program runtime data.

7. The data acquisition method according to claim 6, characterized in that, Following the display of the target list, the following is also included: The target list receives method editing operations for data acquisition methods, and updates the data acquisition methods associated with the target list and / or the method identifiers in the target list based on the method editing operations.

8. The data acquisition method according to claim 1, characterized in that, The execution of the data acquisition method, which calls the data acquisition interface through the data acquisition method to obtain target data corresponding to the target effect, includes: The data acquisition method is executed to call the data acquisition interface through the data acquisition method to obtain a response message corresponding to the data acquisition method; wherein, the response message includes a message identifier and a message content; the message content includes an effect identifier and effect data; When the client receives the response message, the message identifier and the effect identifier in the response message are verified. If both the message identifier and the effect identifier pass the verification, the target data corresponding to the target effect is determined according to the response message.

9. The data acquisition method according to claim 8, characterized in that, The verification of the message identifier and the effect identifier in the response message includes: The message identifier in the response message is verified according to the preset identifier, and the effect identifier in the response message is verified according to the effect identifier of the target effect.

10. A data acquisition device, characterized in that, include: The special effects enable request module is used to receive a special effects enable request for a target special effects through a client, and obtain program running data corresponding to the target special effects. The program running data includes a data acquisition method predefined in the data acquisition layer. The data acquisition method is used to call a data acquisition interface pre-created in the data acquisition layer corresponding to the client. The target data acquisition module is used to execute the data acquisition method to call the data acquisition interface through the data acquisition method to obtain target data corresponding to the target effect.

11. An electronic device, characterized in that, The electronic device includes: One or more processors; Storage device for storing one or more programs. When the one or more programs are executed by the one or more processors, the one or more processors implement the data acquisition method as described in any one of claims 1-9.

12. A storage medium containing computer-executable instructions, characterized in that, The computer-executable instructions, when executed by a computer processor, are used to perform the data acquisition method as described in any one of claims 1-9.

13. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by a processor, it implements the data acquisition method as described in any one of claims 1-9.

Images