Data processing method, information display method, device, storage medium and program product

Abstract

Provided in the embodiments of the present disclosure are a data processing method, an information display method, a device, a storage medium and a program product. In the embodiments of the present disclosure, the data processing method comprises: in response to a first interaction request, determining a first component, the first interaction request being generated on the basis of a user trigger operation in a component orchestration interface; generating first description information on the basis of first component information of the first component; and inputting the first description information into a first large model, so as to use the first large model to determine orchestration related information corresponding to the first component. The technical solutions of the embodiments of the present disclosure reduce configuration costs of interaction between components, and improve configuration efficiency.

Description

[0001] TECHNICAL FIELD: Embodiments of the present disclosure relate to the field of data processing, and more particularly to a data processing method, information display method, device, storage medium, and program product. Background: Data visualization is the theory, methods, and techniques for converting data into graphics or images, displaying them on a screen, and then interactively processing them using computer graphics and image processing techniques. To facilitate data visualization, numerous visualization building tools have emerged. These tools typically provide a variety of visualization components. Users can select the desired visualization component in the component editing interface, configure the component to associate it with the original data, and then use the visualization component to render the original data into the corresponding graphics. After configuring visual components, actual applications often require interaction between different components. For example, when an event is triggered on one component, it may be desirable to execute an action in another component based on its associated data, such as display or movement. Currently, visual building tools also provide component orchestration functionality, allowing users to select multiple components for interaction within the component orchestration interface. Each component is configured with executable actions and triggerable events, and users can establish connections between nodes by connecting them. Furthermore, visual building tools also provide data configuration functionality, allowing users to configure interaction content for different components requiring interaction, such as setting interaction time, execution order, and functions for data format conversion. Combining these orchestration and / or configuration operations, component orchestration information can be generated, enabling interaction between components based on this component orchestration information. As can be seen from the above description, implementing interaction between components requires significant manual effort, resulting in high costs and low efficiency. SUMMARY OF THE INVENTION Embodiments of the present disclosure provide a data processing method, an information display method, a device, a storage medium, and a program product to address the high cost and low efficiency of manually configuring interactive content when implementing interactions between different components in data visualization. In a first aspect, the present disclosure provides a data processing method, comprising: determining a first component in response to a first interaction request; the first interaction request being generated based on a user-triggered operation in a component orchestration interface; generating first description information based on first component information of the first component; and inputting the first description information into a first large model to determine orchestration-related information corresponding to the first component using the first large model.In a second aspect, the present disclosure provides an information display method, comprising: generating a first interaction request in response to a user triggering operation on a component orchestration interface; and sending the first interaction request to a server, wherein the first interaction request is used to identify a first component, first component information of the first component is used to generate first description information, and the first description information is input into a first large model to determine orchestration-related information corresponding to the first component using the first large model. In a third aspect, the present disclosure provides a computing device, comprising a storage component and a processing component, wherein the storage component stores one or more computer program instructions, the computer program instructions being invoked and executed by the processing component, and the processing component executing the one or more computer program instructions to implement the data processing method of the first aspect and the information display method of the second aspect. In a fourth aspect, the present disclosure provides a computer-readable storage medium storing a computer program, wherein the computer program is executed by a computer to implement the data processing method of the first aspect or the information display method of the second aspect. In a fifth aspect, the present disclosure provides a computer program product storing a computer program, wherein the computer program, when executed by a computer, implements the data processing method of the first aspect or the information display method of the second aspect. In an embodiment of the present disclosure, a first component can be determined in response to a first interaction request. The first interaction request can be generated based on a user-triggered operation in a component orchestration interface. First description information can be generated based on the first component information of the first component. This first description information is then input into a first large model, and the first large model is used to determine orchestration-related information corresponding to the first component. By utilizing the first large model, orchestration-related information for the first component with an interaction requirement can be determined based on the first description information without requiring manual user intervention. This reduces the configuration cost of interactions between components, improves configuration efficiency, and thereby improves the efficiency of interactions between components. These and other aspects of the present disclosure will be more readily understood in the following description of the embodiments. BRIEF DESCRIPTION OF THE DRAWINGS To more clearly illustrate the embodiments of the present disclosure or the technical solutions in the prior art, the following briefly introduces the drawings required in the embodiments or the description of the prior art. Obviously, the drawings described below represent some embodiments of the present disclosure. Persons skilled in the art can derive other drawings based on these drawings without inventive effort.Figure 1 shows a schematic diagram of the structure of an embodiment of a system architecture provided by the present disclosure; Figure 2 shows a flow chart of an embodiment of a data processing method provided by the present disclosure; Figure 3 shows a schematic diagram of an embodiment of a component arrangement effect diagram provided by the present disclosure; Figure 4 shows a flow chart of another embodiment of a data processing method provided by the present disclosure; Figure 5 shows a flow chart of an embodiment of an information display method provided by the present disclosure; Figure 6 shows a schematic diagram of the structure of an embodiment of a component interaction scenario provided by the present disclosure; Figure 7 shows a schematic diagram of the structure of another embodiment of a component interaction scenario provided by the present disclosure; Figure 8 shows a schematic diagram of the structure of an embodiment of a data processing device provided by the present disclosure; Figure 9 shows a schematic diagram of the structure of an embodiment of an information display device provided by the present disclosure; Figure 10 shows a schematic diagram of the structure of an embodiment of a computing device provided by the present disclosure. Specific implementation methods In order to enable people in this technical field to better understand the scheme of the present disclosure, the technical scheme in the embodiments of the present disclosure will be clearly and completely described below in conjunction with the drawings in the embodiments of the present disclosure. Some processes described in the specification and claims of this disclosure, as well as in the aforementioned figures, include multiple operations that appear in a specific order. However, it should be understood that these operations may be executed in a different order than the order in which they appear herein, or in parallel. Operation numbers such as 101 and 102 are merely used to distinguish between different operations and do not represent any specific order of execution. Furthermore, these processes may include more or fewer operations, and these operations may be executed sequentially or in parallel. It should be noted that terms such as "first" and "second" are used herein to distinguish between different messages, devices, modules, etc., and do not imply a sequential order, nor do they limit "first" and "second" to different types. Data visualization is the theory, method, and technique of using computer graphics and image processing techniques to convert data into graphics or images, display them on a screen, and then perform interactive processing. To facilitate data visualization, many visualization building tools have emerged. Visualization building tools usually provide a variety of visualization components. Users can select the required visualization components in the component editing interface and configure the components to associate with the original data. The original data can then be rendered into corresponding graphics through the visualization components.After configuring visual components, in actual applications, there may be a need for interaction between different components. For example, when an event is triggered in one component, it may be desirable to execute an action in another component based on its associated data, such as display or movement. Currently, visual building tools also provide component orchestration functionality. Within the component orchestration interface, users can select multiple components to interact with. Each component is configured with executable actions and triggerable events, and users can establish connections between nodes by connecting them. Furthermore, visual building tools also provide data configuration functionality, allowing users to configure interaction content for different components requiring interaction, such as setting interaction time, execution order, and functions for implementing data format conversion. Combining these orchestration and / or configuration operations, component orchestration information can be generated, enabling interaction between components based on this component orchestration information. As can be seen from the above description, implementing interaction between components requires significant manual effort, resulting in high costs and low efficiency. To address the above-mentioned technical problems, the inventors have proposed the technical solutions of the present disclosure, including a data processing method, comprising: determining a first component in response to a first interaction request; the first interaction request being generated based on a user-triggered operation in a component orchestration interface; generating first description information based on first component information of the first component; and inputting the first description information into a first large model to determine orchestration-related information corresponding to the first component using the first large model. In the embodiments of the present disclosure, by utilizing the first large model to generate orchestration-related information for the first component with an interaction requirement based on the first description information, manual user operation is eliminated, thereby reducing the configuration cost of interactions between components, improving configuration efficiency, and thereby improving the efficiency of interactions between components. The technical solutions of the embodiments of the present disclosure will be described clearly and completely below, in conjunction with the accompanying drawings. It should be understood that the described embodiments are merely some, and not all, of the embodiments of the present disclosure. All other embodiments derived by those skilled in the art based on the embodiments of the present disclosure without inventive effort are intended to fall within the scope of protection of the present disclosure. The technical solutions of the embodiments of the present disclosure can be applied to a system architecture including a client and a server. FIG1 is a schematic diagram of an embodiment of the system architecture provided by the present disclosure, which may include a client 101 and a server 102. A connection is established between the client 101 and the server 102 via a network, and the client 101 can interact with the server 102 via the network to receive or send messages. The client 101 may be a visualization building tool that provides a variety of visualization components.A component editing interface is also provided, supporting component-specific orchestration operations. For example, users can establish associations between different components through connections to enable cross-component interaction. The user terminal 101 can be deployed in an electronic device and rely on the device or certain apps within the device to function. The server terminal 102 may include servers that provide various services, such as a server that processes interaction information sent by the user terminal 101. It should be noted that the server terminal can be implemented as a distributed server cluster consisting of multiple servers, or as a single server. The server can also be a server in a distributed system or a server integrated with blockchain. The server can also be a cloud server, or an intelligent cloud computing server or intelligent cloud host equipped with artificial intelligence technology. It should be noted that the data processing methods provided in the embodiments of the present disclosure are generally executed by the server terminal. However, in other embodiments of the present disclosure, the user terminal may have similar functions to the server terminal, thereby executing the data processing methods provided in the embodiments of the present disclosure. In other embodiments, the data processing methods provided in the embodiments of the present disclosure may also be jointly executed by the user terminal and the server terminal. It should be noted that the embodiments of this disclosure may involve the use of user data. In actual applications, user-specific personal data may be used in the solutions described herein, subject to compliance with applicable laws and regulations of the country in which the application is located (for example, with the user's explicit consent, effective notification to the user, etc.), and within the scope permitted by applicable laws and regulations. It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, and displayed data, etc.) involved in this disclosure are all authorized by the user or fully authorized by all parties. The collection, use, and processing of relevant data must comply with the relevant laws, regulations, and standards of the relevant countries and regions, and corresponding operation portals are provided for users to choose to authorize or deny. It should be noted that the technical solutions of the embodiments of this disclosure are applicable to virtual network environments. The users described are generally "virtual users." Real users can register user accounts on the server through registration to obtain user identities in the network environment. Figure 2 is a flowchart of an embodiment of a data processing method provided by the embodiments of this disclosure, which can be applied to the server. The method may include the following steps:

[0002] 201: Determine a first component in response to a first interaction request. The first interaction request may be generated based on a user-triggered operation in the component arrangement interface. Specifically, the first interaction request may be generated by the user in response to a user-triggered operation in the component arrangement interface, such as a click or drag operation, and sent to the server. The server then receives the first interaction request sent by the user and determines a first component with an interaction requirement. In practical applications, visualization building tools may provide a variety of components, such as map components and chart components, including line charts and jade jade charts. Each component may be configured with triggerable events and executable actions. Triggerable events may include click events, selection events, and switch events, while executable actions may include display actions, hide actions, and move actions. In the disclosed embodiments, for a first component with an interaction requirement, the triggerable event of the first component may be executed by executable actions of other components in conjunction with associated raw data, thereby enabling interaction between components. Specifically, a component can be configured with multiple triggerable events and multiple executable actions. For ease of description, the associated raw data is referred to as target data, the triggerable event in the first component being interacted with is referred to as the target event, the component interacting with it is referred to as the second component, and the executable action in the second component is referred to as the target action. In other words, for a first component requiring interaction, the target data can be combined with the target action of the second component to execute the target event of the first component.

[0003] 202: Generate first description information based on the first component information of the first component. The first component information may include one or more of the following: identification information, version number, basic configuration information, and detailed configuration information of the first component. Basic configuration information may include, for example, identification information and version number of each triggerable event and executable action. Detailed configuration information may include, for example, anchor information, data format, and configuration information of each triggerable event and executable action. Data format may include data types, such as coordinate data and longitude and latitude data, and configuration item specifications, such as the Data V specification (a specification applicable to the visualization building tool Data V) and the JSON Schema specification. Based on the determined first component information of the first component, first description information (prompt) may be generated. The description information (prompt) is a form of input used to prompt or guide the large model to produce expected output, instructing the large language model on what actions to take or what output to generate when performing a specific task. The description information is a natural language input, similar to a command or instruction, that informs the large model what it needs to do. In this embodiment, the first description information can be used to instruct the first large model to determine the orchestration-related information corresponding to the first component. The first description information may, for example, be: Please analyze in conjunction with the first component information and return the orchestration-related information corresponding to the first component. Of course, this is merely an example, and the present disclosure is not limited thereto. The first description information can, for example, be generated based on a preconfigured prompt template, by entering the prompt template with the first component information to obtain the first description information. The orchestration information corresponding to the first component may include, for example, the second component that interacts with the first component, the target event corresponding to the first component, the target action corresponding to the second component, and the like. Alternatively, it may include the interaction content between the first and second components, such as the interaction time between the first and second components, a data conversion function that converts the first data format corresponding to the first component into the second data format corresponding to the second component, and the like.

[0004] 203: Input the first description information into the first large model, and use the first large model to determine the orchestration-related information corresponding to the first component. The large model (also called the foundation model) involved in the embodiments of this disclosure, including the first large model and the second, third, fourth, fifth, and sixth large models described below, refers to a machine learning model with a large number of parameters and a complex structure. It can process massive amounts of data and complete various complex tasks, such as natural language processing, computer vision, and speech recognition. It is an AI (artificial intelligence) model. The large model can be implemented using a large language model (LLM) or a multimodal large model (MLM). For example, GPT-3 (Generative Pre-Trained Transformer-3), GPT-4 (Generative Pre-Trained Transformer-4), BERT (Bidirectional Encoder Representation from Transformers), Turing NLG (Turing Natural Language Generation), and the like. This disclosure does not limit this. In this embodiment, for ease of description, the large model that processes the first description information may be referred to as the first large model. The first large model receives the first description information as input, generates, and outputs orchestration-related information corresponding to the first component. Taking the data conversion function that converts a first data format into a second data format for arranging related information as an example, this data conversion function can be used to convert the target data in the first data format in the target event of the first component into the second data format corresponding to the target action of the second component, thereby realizing the use of the target action of the second component to execute the target event of the first component.For example, the first component is a chart component, the target event for the first component is a selection event, and the corresponding data format is coordinate data. The second component is a map component, the target action for the second component is a display action, and the corresponding data format is longitude and latitude data. In this case, the data conversion function output by the first large model can convert the coordinate data into longitude and latitude data. When the user selects the chart component, the selected chart data is converted from coordinate data into longitude and latitude data using this data conversion function and displayed using the map component, thereby enabling interaction between the chart component and the map component. Optionally, the first large model can be pre-trained. Therefore, in some embodiments, the above method may further include: obtaining training samples and training labels; and training the first large model using the training samples and training labels. The training samples may include sample description information, which may be generated based on the first sample component information of the first sample component. The training labels may include sample arrangement-related information corresponding to the first sample component. Specifically, training samples can be input into the first large model, and calculations can be performed using the output actual orchestration-related information and the sample orchestration-related information in the training labels to determine a loss function. The loss function can then be used to adjust the model parameters of the first large model. The specific implementation method can refer to the model training method in conventional solutions and will not be described in detail. In this embodiment, a first component can be identified in response to a first interaction request. The first interaction request can be generated based on a user-triggered operation in the component orchestration interface. First description information can be generated based on first component information of the first component. This first description information is input into the first large model, and the first large model is used to determine the orchestration-related information corresponding to the first component. By utilizing the first large model, orchestration-related information for the first component with interaction requirements is generated based on the first description information, eliminating the need for manual user operation. This reduces the configuration cost of interactions between components, improves configuration efficiency, and thereby improves the efficiency of interactions between components. The technical solutions of this disclosure will be described in detail below, taking as an example the case where the orchestration-related information corresponding to the first component identified is interaction content between the first component and a second component. In some embodiments, the above method may further include: determining a second component that interacts with the first component. Determining the second component that interacts with the first component can be implemented in various ways, which will be described in subsequent embodiments. In this case, generating the first description information based on the first component information of the first component may include generating the first description information based on the first component information of the first component and the second component information of the second component.In this embodiment, the first component information may include identification information, version number, and configuration information of the first component. The configuration information may include, for example, anchor information, a first data format corresponding to the first component, and configuration information of each triggerable event and executable action in the first component. The second component information may include identification information, version number, and configuration information of the second component. The configuration information may include, for example, anchor information, a second data format corresponding to the second component, and configuration information of each triggerable event and executable action in the second component. First description information may be generated based on the determined first component information of the first component and the second component information of the second component. In this embodiment, the first description information may be used to instruct the first large model to determine the interactive content for interaction between the first component and the second component. The first description information may, for example, be: "Please analyze the first component information and the second component information together, and return the interactive content for interaction between the first component and the second component." Furthermore, inputting the first description information into the first large model to determine the orchestration-related information corresponding to the first component using the first large model may include: inputting the first description information into the first large model to determine the interactive content for interaction between the first component and the second component using the first large model. In this embodiment, by utilizing the first large model and generating interactive content for interaction between the first and second components based on the first description information, manual user operation is eliminated, reducing the configuration cost of interactive content for interaction between components and improving the efficiency of interactive content configuration, thereby improving the efficiency of interaction between components. The following describes the process of determining the second component to interact with the first component. In some embodiments, the first interaction request may be generated for the first and second components selected in the component arrangement interface. Thus, in response to the first interaction request, the first component and the second component to interact with the first component may be determined. Specifically, the component arrangement interface may display multiple components, and the user may perform operations such as clicking and dragging to select the two components to interact with. Alternatively, the first and second components may be determined based on the order in which the user selects the components, such as determining the component selected first by the user as the first component and the component selected later as the second component. Alternatively, the first and second components may be determined based on the position of the components dragged into the component arrangement interface, such as determining the component on the left as the first component and the component on the right as the second component. This disclosure is not limited to this aspect. In actual applications, as the demand for customized interactions between components becomes increasingly strong, for a specific component that the user requests to interact with, the components that implement the interaction can be recommended to the user for selection.Therefore, in some embodiments, the first interaction request may be generated based on a first component selected by a user in a group arrangement interface. In this case, determining the first component in response to the first interaction request may include: determining the first component selected by the user in the component arrangement interface in response to the first interaction request. Furthermore, determining the second component that interacts with the first component may include: generating second description information based on first component information of the first component, user arrangement information, and component information of multiple configured components; and inputting the second description information into a second large model to use the second large model to determine the second component that interacts with the first component from the multiple configured components. The user arrangement information may include historical arrangement information, such as components that have interacted with the first component, i.e., components whose set executable actions have executed events that can trigger events in the first component. In this embodiment, the first component information of the first component may include the first component's identification information, version number, and basic configuration information, and the component information of the multiple configured components may include the identification information, version numbers, and basic configuration information of the multiple configured components. Therefore, the second description information generated based on the user orchestration information, the first component's first component information, and the component information of multiple configured components can, for example, be: Please analyze the user orchestration information, the first component's identification information, version number, and basic configuration information, as well as the identification information, version number, and basic configuration information of multiple configured components, and return a second component from the multiple configured components that interacts with the first component. Optionally, the second large model can be implemented as the same large model as the first large model, or as a different large model. In this embodiment, by determining the first component selected by the user in the component orchestration interface, generating the second description information based on the first component's first component information, the user orchestration information, and the component information of multiple configured components, and then using the second large model to determine the second component from the multiple configured components that interacts with the first component based on the second description information, this automatically predicts the user's interaction needs for a specific component during component interaction, thereby improving the user experience. To further enhance the user experience and improve prediction accuracy, the process of using the large model to predict interaction needs for a specific component can be combined with user feedback.Therefore, in some embodiments, inputting the second description information into the second large model to use the second large model to determine a second component that interacts with the first component from among the multiple configured components may include: inputting the second description information into the second large model to use the second large model to determine, from among the multiple configured components, candidate components that interact with the first component, candidate events corresponding to the first component, and candidate actions corresponding to the candidate components, and generating first prompt information based on the candidate components, candidate events, and candidate actions; outputting the first prompt information; obtaining a first feedback request triggered by a user in response to the first prompt information; and determining, based on the first feedback request, the second component that interacts with the first component, the target event corresponding to the first component, and the target action corresponding to the second component. In this embodiment, the second large model may prioritize candidate predictions using the second description information. Optionally, the second large model may determine one or more candidate components that interact with the first component, one or more candidate events for the first component, and candidate actions corresponding to each candidate component, and generate the first prompt information. Furthermore, the first prompt information can be sent to the user terminal for display in the component arrangement interface of the user terminal, prompting the user to execute the candidate event of the first component using the candidate action of the candidate component. The first prompt information can be implemented in various forms, such as text information and graphical information, without limitation. Specifically, the first feedback request can include a first confirmation request or a first update request. The first confirmation request can be generated based on a first confirmation operation performed by the user on the first prompt information, such as a user clicking a confirmation control in the component arrangement interface. The first update request can be generated based on a first update operation performed by the user on the first prompt information, such as a text modification performed by the user on the text information when the first prompt information is text information.At this time, in combination with the first feedback request, determining the second component that interacts with the first component, the target event corresponding to the first component, and the target action corresponding to the second component may include: when the first feedback request is a first confirmation request, generating third description information based on the first prompt information, and inputting the third description information into the third large model, so as to use the third large model to determine that the candidate component is the second component that interacts with the first component, the candidate event corresponding to the first component is the target event corresponding to the first component, and the candidate action corresponding to the candidate component is the target action corresponding to the second component; when the first feedback request is a first update request, obtaining update information in the first update request, updating the first prompt information based on the update information, generating third description information based on the updated prompt information, and inputting the third description information into the third large model, so as to use the third large model to determine the second component that interacts with the first component, the target event corresponding to the first component, and the target action corresponding to the second component. It is understood that if the first feedback request received is a first confirmation request, this may indicate that the user's interaction requirements for the first component are consistent with the candidate prediction results of the second large model. In this case, third description information may be generated based on the first prompt information. The third large model, combined with the third description information, may be used to determine that the candidate component is the second component that interacts with the first component, the candidate event corresponding to the first component is the target event corresponding to the first component, and the candidate action corresponding to the candidate component is the target action corresponding to the second component. If the first feedback request received is a first update request, this may indicate that the user's interaction requirements for the first component are inconsistent with the candidate prediction results of the second large model. In this case, the first prompt information may be updated using the update information provided by the user. The updated first prompt information may then be used to generate third description information. The third large model, combined with the third description information, may be used to determine the second component that interacts with the first component, the target event corresponding to the first component, and the target action corresponding to the second component. In this embodiment, the third description information may be used to instruct the third large model to determine, from multiple configured components, the second component that interacts with the first component, the target event corresponding to the first component, and the target action corresponding to the second component. The third description information may, for example, be: "Please analyze the information in conjunction with the first prompt information or the updated first prompt information, and return a second component that interacts with the first component, a target event corresponding to the first component, and a target action corresponding to the second component, among multiple configured components." Specifically, the third large model may parse the third description information and, using the parsed content, determine the second component, the first component's target event, and the second component's target action from among the configured components.Optionally, the third description information can be implemented as text information. The third large model can specifically parse the text prompt information based on a natural language processing algorithm and use the parsed content to determine the second component, the target event of the first component, and the target action of the second component from the configured components. Optionally, the third large model, the first large model, and the second large model can be implemented as the same large model or different large models. In this embodiment, by preferentially utilizing the second large model to perform candidate predictions based on the second description information, candidate components that interact with the first component, candidate events for the first component, and candidate actions for the candidate components are determined from multiple configured components, and the first prompt information is generated. Combined with the user's first feedback request in response to the first prompt information, the second component that interacts with the first component, the target event of the first component, and the target action of the second component are determined, thereby improving prediction accuracy and further enhancing the user experience. In practical applications, after determining the first component, the second component, and the interactive content between the first and second components, in some embodiments, the method may further include: sending the first component, the second component, and the interactive content to the user terminal, so that a component arrangement interface provided by the user terminal displays an arrangement rendering generated based on the first component, the second component, and the interactive content. The server may send the first component, the second component, the interactive content, and the connection information to the user terminal to generate and display the arrangement rendering. Figure 3 shows a schematic diagram of an embodiment of an arrangement rendering. As shown in Figure 3, the interactive content between the first and second components is implemented as a data conversion function. The interaction between the first and second components specifically involves executing an executable action 2 of the second component to trigger an event 10 of the first component. Furthermore, in some embodiments, the method may further include: obtaining a second feedback request triggered by the user regarding the arrangement rendering. Specifically, the second feedback request may include a second confirmation request or a second update request. The second confirmation request may be generated based on a confirmation operation triggered by the user on the orchestration rendering, such as a user clicking a confirmation control in the component orchestration interface. The second update request may be generated based on an update operation triggered by the user on the orchestration rendering, such as a user clicking a blank location in the component orchestration interface.If the second feedback request is a second confirmation request, component orchestration information can be generated based on the first component, the second component, and the interactive content. This component orchestration information can be used to generate visual images corresponding to the first component and the second component, respectively, based on the raw data associated with the first component or the second component, and to generate the interaction effect corresponding to the first component and the second component, based on the interactive content. If the second feedback request is a second update request, the process returns to the step of outputting the first prompt information and continues, i.e., re-predicting candidate components, candidate events, and candidate actions until a user-confirmed orchestration effect diagram is obtained. In this embodiment, by generating component orchestration information or re-predicting the user's interaction needs in conjunction with the user's second feedback request regarding the orchestration effect diagram, the user experience is further enhanced. To further improve the user experience and the efficiency of interaction between components, for a specific component requested by the user for interaction, multiple components can be recommended to the user, including downstream components that implement interaction with the component and downstream components with which the downstream component interacts when it is an upstream component, for user selection. Therefore, in some embodiments, the above method may further include: determining an initial component selected by a user in a component arrangement interface; generating fourth description information based on component information of the initial component, user arrangement information, and component information of multiple configured components; inputting the fourth description information into a fourth large model to use the fourth large model to determine the downstream component corresponding to the initial component when it is an upstream component, the downstream component corresponding to the downstream component when it is an upstream component, the target event corresponding to the upstream component, and the target action corresponding to the downstream component; selecting any two components having an upstream-downstream relationship as the first component and the second component; and generating a first interaction request based on the first component and the second component. In this embodiment, the fourth description information may be used to instruct the fourth large model to determine, from the multiple configured components, the downstream component corresponding to the initial component when it is an upstream component, the downstream component corresponding to the downstream component when it is an upstream component, the target event corresponding to the upstream component, and the target action corresponding to the downstream component. The fourth description information may, for example, be: Please analyze the component information of the initial component, the user orchestration information, and the component information of multiple configured components, and return the corresponding downstream component when the initial component is the upstream component, the corresponding downstream component when the downstream component is the upstream component, the target event corresponding to the upstream component, and the target action corresponding to the downstream component. Subsequently, first description information can be generated based on the first component information of the first component and the second component information of the second component. This first description information is then input into the first large model to determine the interaction content between the first and second components using the first large model. This will not be further described.Optionally, the fourth large model and the first, second, and third large models may be implemented as the same large model or different large models. In some embodiments, inputting the fourth description information into the fourth large model to use the fourth large model to determine the downstream component corresponding to the initial component as the upstream component, the downstream component corresponding to the downstream component as the upstream component, the target event corresponding to the upstream component, and the target action corresponding to the downstream component may include: inputting the fourth description information into the fourth large model; using the fourth large model to determine, from multiple configured components, candidate downstream components that interact with the initial component when the initial component acts as the upstream component, candidate downstream components that interact with the candidate downstream components when the candidate downstream components act as the upstream component, candidate events corresponding to the initial components, and candidate actions corresponding to the candidate downstream components; generating second prompt information based on the candidate downstream components, candidate events, and candidate actions; outputting the second prompt information; obtaining a third feedback request triggered by a user in response to the second prompt information; and determining, based on the third feedback request, the downstream component corresponding to the initial component when the initial component acts as the upstream component, the downstream component corresponding to the downstream component when the downstream component acts as the upstream component, the target event corresponding to the upstream component, and the target action corresponding to the downstream component. Specifically, the third feedback request may include a third confirmation request or a third update request. If the third feedback request is a third confirmation request, fifth description information may be generated based on the second prompt information. If the third feedback request is a third update request, updated information in the third update request may be obtained, the second prompt information may be updated based on the updated information, and the fifth description information may be generated based on the updated second prompt information. Using the fifth large model and the fifth description information, the downstream component corresponding to the initial component when it serves as the upstream component, the downstream component corresponding to the downstream component when it serves as the upstream component, the target event corresponding to the upstream component, and the target action corresponding to the downstream component may be determined. Furthermore, the above method may further include: sending the initial component, the downstream component corresponding to the initial component when it serves as the upstream component, the downstream component corresponding to the downstream component when it serves as the upstream component, and the interactive content corresponding to any two components with an upstream-downstream relationship to a user terminal, so that an orchestration rendering generated based on the initial component, the downstream component corresponding to the initial component when it serves as the upstream component, the downstream component corresponding to the downstream component when it serves as the upstream component, and the interactive content corresponding to any two components with an upstream-downstream relationship is displayed on a component orchestration interface provided on the user terminal.In this embodiment, fourth description information is generated based on the initial component selected by the user on the component orchestration interface, the initial component's component information, user orchestration information, and component information of multiple configured components. The fourth description information is then input into a fourth large model. The fourth large model is used to determine the downstream component corresponding to the initial component when it serves as the upstream component, the downstream component corresponding to the downstream component when it serves as the upstream component, the target event corresponding to the upstream component, and the target action corresponding to the downstream component. Subsequently, any two components with an upstream-downstream relationship are designated as the first component and the second component. First description information is generated based on the first component's first component information and the second component's second component information. The first large model is used to determine the interaction content between the first and second components. This enables prediction of the downstream component interacting with a specific component requested by the user, the downstream component interacting with it, and a subsequent series of downstream components interacting with the downstream component, thereby improving user experience and increasing the efficiency of interaction between multiple components. The above-described one or more embodiments illustrate the case where the orchestration-related information corresponding to the first component is determined to be the interaction content between the first component and the second component. The following one or more embodiments illustrate the technical solutions of the present disclosure using the case where the orchestration-related information corresponding to the first component is determined to be the second component interacting with the first component, the target event corresponding to the first component, and the target action corresponding to the second component. Therefore, in some embodiments, inputting the first description information into the first large model to determine the orchestration-related information corresponding to the first component using the first large model may include inputting the first description information into the first large model to determine the second component interacting with the first component, the target event corresponding to the first component, and the target action corresponding to the second component using the first large model. In this embodiment, the first description information may be generated based on user orchestration information, first component information of the first component, and component information of multiple configured components. The user orchestration information may include historical orchestration information, the first component information of the first component may include the identification information, version number, and basic configuration information of the first component, and the component information of the multiple configured components may include the identification information, version number, and basic configuration information of the multiple configured components. The generated first description information may be, for example: Please analyze the user arrangement information, the identification information, version number, and basic configuration information of the first component, and the identification information, version number, and basic configuration information of multiple configured components, and return the second component among the multiple configured components that interacts with the first component, the target event corresponding to the first component, and the target action corresponding to the second component.By determining the first component selected by the user in the component arrangement interface, first description information is generated based on the first component's first component information, user arrangement information, and component information of multiple configured components. Then, based on the first description information, a first large model is used to determine, from the multiple configured components, a second component that interacts with the first component, a target event corresponding to the first component, and a target action corresponding to the second component. This automatically predicts the user's interaction needs for a specific component during component interaction, thereby improving the user experience. To further enhance user experience and improve prediction accuracy, in some embodiments, inputting the first description information into a first large model to use the first large model to determine a second component that interacts with the first component, a target event corresponding to the first component, and a target action corresponding to the second component may include: inputting the first description information into the first large model to use the first large model to determine, from multiple configured components, candidate components that interact with the first component, candidate events corresponding to the first component, and candidate actions corresponding to the candidate components, and generating first prompt information based on the candidate components, candidate events, and candidate actions; outputting the first prompt information; obtaining a first feedback request triggered by the user in response to the first prompt information; and determining, based on the first feedback request, the second component that interacts with the first component, the target event corresponding to the first component, and the target action corresponding to the second component. Specifically, the first feedback request may include a first confirmation request or a first update request. If the first feedback request is a first confirmation request, further descriptive information can be generated based on the first prompt information and input into the first macro model or another macro model to determine that the candidate component is the second component that interacts with the first component, the candidate event corresponding to the first component is the target event corresponding to the first component, and the candidate action corresponding to the candidate component is the target action corresponding to the second component. If the first feedback request is a first update request, update information in the first update request is obtained, and the first prompt information is updated based on the update information. Descriptive information is generated based on the updated prompt information and input into the macro model to determine the second component that interacts with the first component, the target event corresponding to the first component, and the target action corresponding to the second component. Furthermore, after determining the second component that interacts with the first component, the target event corresponding to the first component, and the target action corresponding to the second component using the first macro model, in some embodiments, the method may further include: generating sixth descriptive information based on the first component information of the first component and the second component information of the second component; and inputting the sixth descriptive information into a sixth macro model to determine the interaction content between the first and second components using the sixth macro model.In this embodiment, the first component information of the first component may include identification information, version number, and configuration information of the first component. The configuration information may include, for example, anchor information, a first data format corresponding to the first component, and configuration information of each triggerable event and executable action in the first component. The second component information may include identification information, version number, and configuration information of the second component. The configuration information may include, for example, anchor information, a second data format corresponding to the second component, and configuration information of each triggerable event and executable action in the second component. Based on the determined first component information of the first component and the second component information of the second component, sixth description information may be generated. In this embodiment, the sixth description information may be used to instruct the sixth large model to determine the interactive content for interaction between the first and second components. The sixth description information may include, for example, "Please analyze the interaction content between the first and second components based on the first and second component information, and return the interactive content for interaction between the first and second components." In some embodiments, the above method may further include: sending the first component, the second component, and the interactive content to a user terminal, so that a component arrangement interface provided on the user terminal displays an arrangement rendering generated based on the first component, the second component, and the interactive content. Furthermore, in some embodiments, the method may further include: obtaining a second feedback request triggered by the user regarding the choreography rendering. The second feedback request may include a second confirmation request or a second update request. The second confirmation request may be generated based on a second confirmation operation triggered by the user regarding the choreography rendering, and the second update request may be generated based on a second update operation triggered by the user regarding the choreography rendering. If the second feedback request is a second confirmation request, component choreography information may be generated based on the first component, the second component, and the interactive content. The component choreography information may be used to generate visual images corresponding to the first component and the second component, respectively, based on raw data associated with the first component or the second component, and to generate an interactive effect corresponding to the first component and the second component, based on the interactive content. If the second feedback request is a second update request, the method may return to the step of outputting the first prompt information. By generating component choreography information or re-predicting the user's interactive needs based on the user's second feedback request regarding the choreography rendering, the user experience is further improved.To further improve user experience and interaction efficiency between components, in some embodiments, inputting the first description information into a first large model to determine, using the first large model, orchestration-related information corresponding to the first component may include: inputting the first description information into the first large model to determine, using the first large model, a multi-level component interacting with the first component, a target event corresponding to an upstream component in the multi-level component, and a target action corresponding to a downstream component; the multi-level component may include a downstream component interacting with the first component, as well as downstream components when any downstream component is an upstream component. Furthermore, in some embodiments, the method may further include: using any two components with an upstream-downstream relationship as a first component and a second component; generating seventh description information based on first component information of the first component and second component information of the second component; and inputting the seventh description information into a seventh large model to determine, using the seventh large model, interaction content between the first and second components. This enables prediction of a specific component with which a user requests interaction, its interacting downstream component, and a subsequent series of downstream components that interact with the downstream component, thereby improving user experience and enhancing interaction efficiency between multiple components. As shown in FIG4 , it is a flow chart of another embodiment of a data processing method provided by the present disclosure. The method may include the following steps:

[0005] 400: In response to a first interaction request, determine a first component selected by a user in a component arrangement interface. 401: Generate second description information based on first component information of the first component, user arrangement information, and component information of multiple configured components.

[0006] 402: Input the second description information into the second large model, so as to use the second large model to determine, from multiple configured components, candidate components that interact with the first component, candidate events corresponding to the first component, and candidate actions corresponding to the candidate components, and generate first prompt information based on the candidate components, candidate events, and candidate actions.

[0007] 403: Output the first prompt information.

[0008] 404: Obtain a first feedback request triggered by the user in response to the first prompt information, and if the first feedback request is a first confirmation request, perform the operation of step 405; and if the first feedback request is a first update request, perform the operation of step 406.

[0009] 405: Generate third description information based on the first prompt information, and input the third description information into the third large model, so as to use the third large model to determine that the candidate component is the second component that interacts with the first component, the candidate event corresponding to the first component is the target event corresponding to the first component, and the candidate action corresponding to the candidate component is the target action corresponding to the second component.

[0010] 406: Obtain update information in the first update request, update the first prompt information based on the update information, generate third description information based on the updated first prompt information, and input the third description information into a third large model to use the third large model to determine a second component that interacts with the first component, a target event corresponding to the first component, and a target action corresponding to the second component.

[0011] 407: Generate first description information based on first component information of the first component and second component information of the second component. The first component information may include a first data format corresponding to the first component, and the second component information may include a second data format corresponding to the second component.

[0012] 408: Input the first description information into the first large model, so as to use the first large model to determine the interaction content between the first component and the second component.

[0013] 409: The first component, the second component, and the interactive content are sent to the user terminal, so that a component arrangement interface provided on the user terminal displays an arrangement rendering generated based on the first component, the second component, and the interactive content. The implementation process of steps 400-409 has been described in one or more of the aforementioned embodiments and will not be repeated here. In this embodiment, by determining the first component selected by the user in the component arrangement interface, generating second description information based on the first component's first component information, the user's arrangement information, and the component information of multiple configured components, and using the second large model based on the second description information, determining candidate components that interact with the first component, candidate events for the first component, and candidate actions for the candidate components from the multiple configured components, and generating first prompt information. In conjunction with the user's first feedback request for the first prompt information, the second component that interacts with the first component, the target event for the first component, and the target action for the second component are determined, thereby improving prediction accuracy. Furthermore, in conjunction with the user's second feedback request for the arrangement rendering, component arrangement information is generated or the user's interaction needs are re-predicted, thereby enhancing the user experience. The following describes the technical solution of the present disclosure from the perspective of a user terminal. FIG5 is a flowchart of an embodiment of an information display method provided by the present disclosure. The method may include the following steps:

[0014] 501: In response to a user triggering operation on a component orchestration interface, a first interaction request is generated.

[0015] 502: Send a first interaction request to the server. The first interaction request can be used to identify a first component, and the first component information of the first component can be used to generate first description information. The first description information can be input into a first large model to determine orchestration-related information corresponding to the first component using the first large model. In this embodiment, the user terminal can generate a first interaction request in response to a user triggering operation on the component orchestration interface, and send the first interaction request to the server. The server can then identify the first component, generate first description information based on the first component information, input the first description information into the first large model, and determine orchestration-related information corresponding to the first component using the first large model. By utilizing the first large model, orchestration-related information of the first component with interaction requirements can be determined based on the first description information without manual user operation, thereby reducing the configuration cost of interactions between components, improving configuration efficiency, and thereby improving interaction efficiency between components. In some embodiments, the first description information may be generated based on first component information of the first component and second component information of a second component interacting with the first component, and the first large model may be used to determine the interactive content between the first and second components. Alternatively, the orchestration-related information may include the second component interacting with the first component, the target event corresponding to the first component, and the target action corresponding to the second component, and the first component information of the first component and the second component information of the second component may also be used to generate sixth description information, and the sixth large model may be used to determine the interactive content between the first and second components. Furthermore, the method may further include: obtaining the first component, the second component, and the interactive content sent by the server; and displaying an orchestration rendering generated based on the first component, the second component, and the interactive content on a component orchestration interface. In some embodiments, the method may further include: receiving first prompt information sent by the server. The first prompt information may be generated by the server based on candidate components that interact with the first component, candidate events corresponding to the first component, and candidate actions corresponding to the candidate components. The candidate components, candidate events, and candidate actions may be determined by the server using a second large model in combination with second description information. The second description information may be generated based on first component information of the first component, user orchestration information, and component information of multiple configured components; or may be determined by the first large model in combination with the first description information. In response to a first confirmation operation or a first update operation triggered by the first prompt information, a first feedback request is generated. The first feedback request is sent to the server.The first feedback request can be used to determine a second component interacting with the first component, a target event corresponding to the first component, and a target action corresponding to the second component. When the first feedback request is a first confirmation request generated based on a user's first confirmation operation in response to first prompt information, the server can generate third description information based on the first prompt information and input the third description information into a third large model. Using the third large model, the server can determine that the candidate component is the second component interacting with the first component, the candidate event corresponding to the first component is the target event corresponding to the first component, and the candidate action corresponding to the candidate component is the target action corresponding to the second component. When the first feedback request is a first update request generated based on a user's first update operation in response to first prompt information, the server can obtain the update information in the first update request, update the first prompt information based on the update information, generate third description information based on the updated first prompt information, and input the third description information into the third large model. Using the third large model, the server can determine the second component interacting with the first component, the target event corresponding to the first component, and the target action corresponding to the second component. The specific implementation can be found in the corresponding embodiments above and will not be repeated here. In some embodiments, the method may further include generating a second feedback request in response to a second confirmation operation or a second update operation triggered on the choreography rendering, and sending the second feedback request to the server. Where the second feedback request is generated based on a second confirmation operation triggered by the user on the choreography rendering, the server may generate component choreography information based on the first component, the second component, and the interactive content, and send the information to the user. The user may then receive the component choreography information sent by the server and, based on the component choreography information, generate visualization images corresponding to the first component and the second component based on raw data associated with the first component or the second component, respectively, and generate an interactive effect corresponding to the first component and the second component based on the interactive content. If the second feedback request is generated based on a second update operation triggered by the user on the orchestration rendering, the server can return to the step of outputting the first prompt information and continue execution. The user can then again execute the first confirmation operation or first update operation triggered by the first prompt information, generating the first feedback request and sending it to the server, and continue execution until the user-confirmed orchestration rendering is obtained. The specific implementation can be found in the corresponding embodiments above and will not be repeated here. To facilitate understanding, the technical solution of the present disclosure will be described below with reference to a schematic diagram of a component interaction scenario in an actual application, in which the interaction content between components is implemented as a data conversion function. Figure 6 is a schematic diagram of an embodiment of the component interaction scenario of the present disclosure in an actual application.In response to a user's selection of component 1 in the component orchestration interface, the user generates a first interaction request and sends it to the server. The server receives and responds to the first interaction request, determining that component 1 selected by the user is the first component. Based on component 1's first component information, user orchestration information, and component information of multiple configured components, the server generates second description information and inputs this second description information into the second large model. Using the second large model, the server identifies component 2 from the multiple configured components as a candidate component for interacting with the first component, identifies triggerable event 1 of component 1 as a candidate event corresponding to the first component, and identifies executable action 1 of component 2 as a candidate action corresponding to the candidate event. Based on the determined candidate components, candidate events, and candidate actions, the server generates first prompt information, outputs it, and sends it to the user. In response to a user's click on prompt control 601 in the component orchestration interface, the server displays the first prompt information in the component orchestration interface. For example, the first prompt information is implemented as textual information such as "Use executable action 1 of component 2 to execute triggerable event 1 of component 1." Subsequently, in response to a user-triggered update operation on the first prompt information, for example, in response to a user updating "executable action 1" to "executable action 2" in the first prompt information, the user generates a first feedback request and sends it to the server. The server receives and, based on the first feedback request, updates the first prompt information based on the updated information. The updated first prompt information now contains text reading "Use executable action 2 of component 2 to execute triggerable event 1 of component 1." The server generates third description information based on the updated first prompt information and inputs this third description information into the third large model. Using the third large model, the server determines that component 2 is the second component interacting with the first component, triggerable event 1 of component 1 is the target event corresponding to the first component, and executable action 2 of component 2 is the target action corresponding to the second component. Subsequently, the server generates first description information based on the first component information of the first component and the second component information of the second component. The first component information may include the first data format corresponding to component 1 and the second data format corresponding to component 2. This first description information is then input into the first large model. A data conversion function for converting the first data format into the second data format is generated using the first large model, and component 1, component 2 and the data conversion function are output and sent to the user end.The user terminal receives and displays an orchestration rendering generated based on Component 1, Component 2, and the data conversion function on the component orchestration interface. Based on the orchestration rendering, it can be seen that Component 1's triggerable event 10 can be executed by Component 2's executable action 2. Furthermore, in response to a user-triggered update operation on the orchestration rendering, such as a user click on a preset location in the component orchestration interface, the user terminal generates a second feedback request and sends it to the server. Simultaneously, the user terminal cancels the display of Component 2 and the data conversion function. The server receives the second feedback request, returns an output, and continues to send the first prompt information to the user terminal. In response to a user click on prompt control 601 in the component orchestration interface, the user terminal again displays the first prompt information on the component orchestration interface. Subsequently, in response to another user-triggered update operation for the first prompt information, for example, in response to a user updating the first prompt information to "Use executable action 2 of component 3 to execute triggerable event 1 of component 1," the server generates another first feedback request and sends it to the server. The server again receives and combines the first feedback request with the first feedback request and updates the first prompt information. Using the updated first prompt information, the server again generates third description information and inputs it into the third large model. Using the third large model, the server determines that component 3 is the second component interacting with the first component, triggerable event 1 of component 1 is the target event corresponding to the first component, and executable action 2 of component 3 is the target action corresponding to the second component. Based on the first large model, the server then generates a new data conversion function to convert the data format corresponding to component 1 into the data format corresponding to component 3. The server then outputs components 1, 3, and the new data conversion function and sends them to the user. The user terminal receives and displays an orchestration effect diagram generated based on component 1, component 3, and the new data conversion function on the component orchestration interface. According to the orchestration effect diagram, it can be seen that the executable action 2 of component 3 can execute the triggerable event 1 of component 1, thereby realizing component interaction.By determining the first component selected by the user in the component orchestration interface, generating second description information based on the first component, user orchestration information, and multiple configured components, and using a second large model to determine candidate components that interact with the first component, candidate events for the first component, and candidate actions for the candidate components from the multiple configured components based on the second description information, and generating first prompt information, the system then determines, based on the user's first feedback request for the first prompt information, a second component that interacts with the first component, the first component's target event, and the second component's target action, thereby improving prediction accuracy. Furthermore, based on the user's second feedback request for the orchestration rendering, component orchestration information is generated or the user's interaction needs are re-predicted, thereby enhancing the user experience. Figure 7 is a schematic diagram of another embodiment of a component interaction scenario in actual application of the present disclosure. In response to a user selection operation triggered by a component 1 in the component orchestration interface, the user generates a first interaction request and sends it to the server. The server receives and responds to the first interaction request, determining that the component 1 selected by the user is the initial component. Fourth description information is generated based on component information of component 1, user orchestration information, and component information of multiple configured components, and the fourth description information is input into a fourth large model. Using the fourth large model, component 2 is determined from the multiple configured components to be a candidate component for interaction with the initial component when the initial component serves as an upstream component; component 3 is determined to be a candidate component for interaction with component 2 when component 2 serves as an upstream component; triggerable event 2 of component 1 is determined to be a candidate event corresponding to the initial component; executable action 1 of component 2 is determined to be a candidate action corresponding to the candidate event; triggerable event 2 of component 2 is determined to be a candidate event corresponding to component 2 when the initial component serves as an upstream component; and executable action 3 of component 3 is determined to be a candidate action corresponding to the candidate event. Second prompt information is generated based on the determined candidate components, candidate events, and candidate actions, and the second prompt information is output and sent to the user terminal. In response to a user clicking on prompt control 701 in the component arrangement interface, the user terminal displays the second prompt information on the component arrangement interface. For example, the second prompt information is implemented as text information such as "Use executable action 1 of component 2 to execute triggerable event 2 of component 1, and use executable action 3 of component 3 to execute triggerable event 2 of component 2." Subsequently, in response to the user confirming the second prompt information, the user terminal generates a second feedback request and sends it to the server. The server receives and combines the second feedback request with the second prompt information, generates fourth description information based on the second prompt information, and inputs the fourth description information into the fourth large model.Using the fourth large model, component 2 is determined to be the downstream component that interacts with the initial component when it is the upstream component. Component 3 is determined to be the downstream component that interacts with component 2 when it is the upstream component. Component 1's triggerable event 2 is the target event corresponding to the initial component. Component 2's executable action 1 is the target action corresponding to the target event. Component 2's triggerable event 2 is the target event corresponding to component 2 when it is the upstream component. Component 3's executable action 3 is the target action corresponding to the target event. Any two components with an upstream-downstream relationship are designated as the first component and the second component. For example, component 1 is designated as the first component and component 2 as the corresponding second component, or component 2 is designated as the first component and component 3 as the corresponding second component. The server generates first description information based on the first component information of the first component and the second component information of the second component. The first description information may include a first data format corresponding to the first component and a second data format corresponding to the second component. This first description information is input into the first large model. The first large model is used to generate a data conversion function for converting the first data format to the second data format. For example, when component 1 is the first component and component 2 is the second component, the first large model is used to generate a data conversion function for converting the data format corresponding to component 1 into the data format corresponding to component 2. Similarly, when component 2 is the first component and component 3 is the second component, the first large model is used to generate a data conversion function for converting the data format corresponding to component 2 into the data format corresponding to component 3. Component 1, component 2, component 3, and the data conversion functions corresponding to components 1 and 2, and components 2 and 3, are then output and sent to the user end. The user end receives and displays on the component orchestration interface an orchestration rendering generated based on component 1, component 2 downstream of component 1, component 3 downstream of component 2, the data conversion functions corresponding to components 1 and 2, and the data conversion functions corresponding to components 2 and 3. This rendering indicates that component 1's triggerable event 2 can be executed by component 2's executable action 1, and component 3's triggerable event 2 can be executed by component 3's executable action 3, thereby achieving multi-component interaction.Based on the initial component selected by the user on the component arrangement interface, fourth description information is generated based on the initial component, user arrangement information, and multiple configured components. The fourth description information is input into a fourth large model to use the fourth large model to determine the downstream component corresponding to the initial component when it is the upstream component, the downstream component corresponding to the downstream component when it is the upstream component, the target event corresponding to the upstream component, and the target action corresponding to the downstream component. Any two components with an upstream-downstream relationship are then used as the first component and the second component. First description information is generated based on the first component information of the first component and the second component information of the second component. The first large model is used to generate a data conversion function for converting the first data format into the second data format. This enables prediction of a specified component with which the user requests interaction, the downstream component that interacts with it, and a subsequent series of downstream components that interact with the downstream component, thereby improving user experience and increasing the efficiency of interaction between multiple components. FIG8 is a schematic diagram of an embodiment of a data processing apparatus provided by the present disclosure. The apparatus may include the following modules: a first determination module 801, configured to determine a first component in response to a first interaction request; the first interaction request is generated based on a user-triggered operation in a component orchestration interface; a first generation module 802, configured to generate first description information based on first component information of the first component; a second determination module 803, configured to input the first description information into a first large model to determine orchestration-related information corresponding to the first component using the first large model. In some embodiments, the apparatus may further include a third determination module, configured to determine a second component that interacts with the first component; the first generation module 802, specifically configured to generate first description information based on the first component information of the first component and the second component information of the second component; and the second determination module 803, specifically configured to input the first description information into the first large model to determine the interaction content between the first and second components using the first large model. In some embodiments, the first determination module 801 may be specifically configured to determine, in response to a first interaction request, a first component selected by a user in a component orchestration interface; the first interaction request is generated based on the first component selected by the user in the component orchestration interface; the third determination module may include: a first generation unit configured to generate second description information based on first component information of the first component, user orchestration information, and component information of multiple configured components; and a first determination unit configured to input the second description information into a second large model to use the second large model to determine, from the multiple configured components, a second component that interacts with the first component.In some embodiments, the first determination unit may include: a first determination subunit, configured to input the second description information into a second large model, so as to use the second large model to determine, from multiple configured components, candidate components that interact with the first component, candidate events corresponding to the first component, and candidate actions corresponding to the candidate components, and generate prompt information based on the candidate components, candidate events, and candidate actions; an output subunit, configured to output prompt information; an acquisition subunit, configured to acquire a first feedback request triggered by the user in response to the prompt information; and a second determination subunit, configured to determine, in combination with the first feedback request, a second component that interacts with the first component, a target event corresponding to the first component, and a target action corresponding to the second component. In some embodiments, the first feedback request may include a first confirmation request or a first update request, the first confirmation request being generated based on a first confirmation operation of a user on the first prompt information, and the first update request being generated based on a first update operation of a user on the first prompt information. The second determination subunit may be specifically configured to, when the first feedback request is the first confirmation request, generate third description information based on the first prompt information, and input the third description information into a third large model, so as to use the third large model to determine that the candidate component is the second component that interacts with the first component, the candidate event corresponding to the first component is the target event corresponding to the first component, and the candidate action corresponding to the candidate component is the target action corresponding to the second component; and, when the first feedback request is the first update request, obtain update information in the first update request, update the first prompt information based on the update information, generate third description information based on the updated first prompt information, and input the third description information into the third large model, so as to use the third large model to determine that the second component that interacts with the first component, the target event corresponding to the first component, and the target action corresponding to the second component. In some embodiments, the apparatus may further include: a first sending module configured to send the first component, the second component, and the interactive content to the user terminal, so as to display an arrangement effect diagram generated based on the first component, the second component, and the interactive content on a component arrangement interface provided by the user terminal.In some embodiments, the device may further include: a first acquisition module, configured to acquire a second feedback request triggered by a user for the choreography effect diagram, the second feedback request including a second confirmation request or a second update request, the second confirmation request being generated based on the second confirmation operation triggered by the user for the choreography effect diagram, and the second update request being generated based on the second update operation triggered by the user for the choreography effect diagram; a second generation module, configured to generate component choreography information based on the first component, the second component, and the interactive content when the second feedback request is the second confirmation request; the component choreography information is used to generate visual images corresponding to the first component and the second component respectively based on the original data associated with the first component or the second component, and to generate an interactive effect corresponding to the first component and the second component based on the interactive content; and a return module, configured to return to the step of outputting the first prompt information and continue execution when the second feedback request is the second update request. In some embodiments, the device may further include: a fourth determination module, configured to determine the initial component selected by the user in the component orchestration interface; a third generation module, configured to generate fourth description information based on component information of the initial component, user orchestration information, and component information of multiple configured components; a fifth determination module, configured to input the fourth description information into a fourth large model, so as to use the fourth large model to determine the downstream component corresponding to the initial component as the upstream component, the downstream component corresponding to the downstream component as the upstream component, the target event corresponding to the upstream component, and the target action corresponding to the downstream component; a sixth determination module, configured to take any two components with an upstream and downstream relationship as the first component and the second component; a fourth generation module, configured to generate a first interaction request based on the first component and the second component. In some embodiments, the device may further include: a second sending module, configured to send the initial component, the downstream component corresponding to the initial component as the upstream component, the downstream component corresponding to the downstream component as the upstream component, and the interactive content corresponding to any two components with an upstream and downstream relationship to the user end, so as to display an arrangement effect diagram generated based on the initial component, the downstream component corresponding to the initial component as the upstream component, the downstream component corresponding to the downstream component as the upstream component, and the interactive content corresponding to any two components with an upstream and downstream relationship on a component arrangement interface provided on the user end; wherein the interactive content corresponding to any two components with an upstream and downstream relationship is generated by the first large model based on the first description information, and the first description information is generated by the component information corresponding to any two components with an upstream and downstream relationship.In some embodiments, the second determination module 803 may be specifically configured to input the first description information into the first large model, and use the first large model to determine a second component that interacts with the first component, a target event corresponding to the first component, and a target action corresponding to the second component. In some embodiments, the second determination module 803 may include: a second determination unit configured to input the first description information into the first large model, and use the first large model to determine, from multiple configured components, candidate components that interact with the first component, candidate events corresponding to the first component, and candidate actions corresponding to the candidate components, and generate first prompt information based on the candidate components, candidate events, and candidate actions; a first output unit configured to output the first prompt information; a first acquisition unit configured to acquire a first feedback request triggered by a user in response to the first prompt information; and a third determination unit configured to determine, based on the first feedback request, the second component that interacts with the first component, the target event corresponding to the first component, and the target action corresponding to the second component. In some embodiments, the apparatus may further include: a fifth generation module configured to generate sixth description information based on the first component information of the first component and the second component information of the second component; and a seventh determination module configured to input the sixth description information into a sixth large model to determine, using the sixth large model, the content of the interaction between the first and second components. In some embodiments, the second determination module 803 may be specifically configured to input the first description information into the first large model to determine, using the first large model, a multi-level component interacting with the first component, a target event corresponding to an upstream component in the multi-level component, and a target action corresponding to a downstream component. The multi-level component includes a downstream component interacting with the first component and a downstream component when any downstream component is an upstream component. In some embodiments, the device may further include: an eighth determination module, configured to take any two components having an upstream and downstream relationship as the first component and the second component; a sixth generation module, configured to generate seventh description information based on the first component information of the first component and the second component information of the second component; and a ninth determination module, configured to input the seventh description information into the seventh large model to use the seventh large model to determine the interaction content between the first component and the second component.As shown in FIG9 , a schematic diagram of the structure of an embodiment of an information display device provided by the present disclosure is provided. The device may include the following modules: a seventh generation module 901, configured to generate a first interaction request in response to a user triggering operation on a component orchestration interface; a third sending module 902, configured to send the first interaction request to a server, wherein the first interaction request is used to identify a first component, first component information of the first component is used to generate first description information, and the first description information is used to input a first large model to determine orchestration-related information corresponding to the first component using the first large model. In some embodiments, the first description information is generated based on the first component information of the first component and the second component information of the second component that interacts with the first component, and the first large model is used to determine the interactive content of the interaction between the first component and the second component; or, the orchestration-related information includes the second component that interacts with the first component, the target event corresponding to the first component, and the target action corresponding to the second component, and the first component information of the first component and the second component information of the second component are also used to generate sixth description information, and the sixth large model is used to determine the interactive content of the interaction between the first component and the second component; the device may also include: a second acquisition module, which is configured to acquire the first component, the second component and the interactive content sent by the server; and a display module, which is configured to display the orchestration effect diagram generated based on the first component, the second component and the interactive content on the component orchestration interface. In some embodiments, the device may further include: a first receiving module, configured to receive a first prompt message sent by the server; the first prompt message is generated based on a candidate component that interacts with the first component, a candidate event corresponding to the first component, and a candidate action corresponding to the candidate component, the candidate component, the candidate event, and the candidate action are determined by the second large model in combination with the second description information, the second description information is generated based on the first component information of the first component, user orchestration information, and component information of multiple configured components; or is determined by the first large model in combination with the first description information; an eighth generating module, configured to generate a first feedback request in response to a first confirmation operation or a first update operation triggered by the first prompt message; a fourth sending module, configured to send the first feedback request to the server; the first feedback request is used to determine the second component that interacts with the first component, the target event corresponding to the first component, and the target action corresponding to the second component.FIG10 is a schematic diagram of the structure of an embodiment of a computing device provided by the present disclosure. The device may include a storage component 1001 and a processing component 1002. The storage component 1001 stores one or more computer program instructions, wherein the one or more computer program instructions are invoked and executed by the processing component 1002 to implement the data processing method shown in FIG2 or FIG4 and the information display method shown in FIG5. Of course, the computing device may also include other components, such as input / output interfaces and communication components. The input / output interface provides an interface between the processing component and peripheral interface modules, which may be output devices, input devices, etc. The communication component is configured to facilitate wired or wireless communication between the computing device and other devices. It should be noted that when the computing device implements the data processing method shown in FIG2 or FIG4, it may be a physical device or an elastic computing host provided by a cloud computing platform. It may be implemented as a distributed cluster consisting of multiple servers or terminal devices, or as a single server or a single terminal device. When the computing device implements the information display method shown in FIG5 , it can be specifically implemented as an electronic device. An electronic device can refer to a device used by a user that has the required functions of accessing the Internet, computing, or communicating, such as a mobile phone, tablet computer, personal computer, wearable device, etc. It is understood that the electronic device may also include a display component, input / output interface, communication component, and other components, which are not described in detail. In one or more of the above embodiments, the processing component may include one or more processors to execute computer instructions to complete all or part of the steps in the above method. Of course, the processing component may also be implemented as one or more application-specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field-programmable gate arrays (FPGAs), controllers, microcontrollers, microprocessors, or other electronic components to perform the above method. The storage component is configured to store various types of data to support operations on the terminal. The storage component can be implemented by any type of volatile or non-volatile memory device or a combination of them, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic disk or optical disk.The display component can be an electroluminescent (EL) element, a liquid crystal display, or a microdisplay with a similar structure, or a retinal direct display or similar laser scanning display. The present disclosure also provides a computer-readable storage medium storing a computer program. When executed by a computer, this computer program can implement the data processing method shown in Figure 2 or Figure 4, or the information display method shown in Figure 5. The computer-readable medium can be included in the computing device described in the above embodiments, or it can exist independently and not be incorporated into the computing device. The computer-readable storage medium can be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device, or any combination thereof. The present disclosure also provides a computer program product, comprising a computer program carried on a computer-readable storage medium. When executed by a computer, this computer program can implement the data processing method shown in Figure 2 or Figure 4, or the information display method shown in Figure 5. In such an embodiment, the computer program can be downloaded and installed from a network, and / or installed from removable media. When executed by a processor, the computer program performs the various functions defined in the system of the present disclosure. Those skilled in the art will clearly understand that, for ease and brevity of description, the specific operating processes of the systems, devices, and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be detailed here. The device embodiments described above are merely illustrative. The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, that is, they may be located in one location or distributed across multiple network units. Some or all of the modules can be selected based on actual needs to achieve the objectives of the present embodiment. Those skilled in the art will be able to understand and implement the present embodiment without inventive effort. Through the above description of the embodiments, those skilled in the art will clearly understand that each embodiment can be implemented using software plus a required general-purpose hardware platform, or alternatively, hardware. Based on this understanding, the above technical solutions, or the portion that contributes to the prior art, can be embodied in the form of a software product. This computer software product can be stored in a computer-readable storage medium, such as ROM / RAM, a magnetic disk, or an optical disk, and includes a number of instructions for enabling a computer device (which can be a personal computer, a server, or a network device, etc.) to execute the methods described in various embodiments or certain portions of the embodiments.Finally, it should be noted that the above embodiments are merely illustrative of the technical solutions of the present disclosure and are not intended to limit the present disclosure. Although the present disclosure has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they may modify the technical solutions described in the aforementioned embodiments or replace some of the technical features therein with equivalents. However, such modifications or replacements do not deviate the essence of the corresponding technical solutions from the spirit and scope of the technical solutions of the various embodiments of the present disclosure.

Claims

26 Claims 1. A data processing method, comprising: In response to a first interaction request, determine a first component; The first interaction request is generated based on a user trigger operation in the component orchestration interface; Generate first description information based on the first component information of the first component; Input the first description information into a first large model to use the first large model to determine the orchestration-related information corresponding to the first component.

2. The method according to claim 1, wherein, It further includes: determining a second component that interacts with the first component; generating the first description information based on the first component information of the first component includes: generating the first description information based on the first component information of the first component and the second component information of the second component; inputting the first description information into the first large model to use the first large model to determine the orchestration-related information corresponding to the first component includes: inputting the first description information into the first large model to use the first large model to determine the interaction content between the first component and the second component.

3. The method according to claim 2, wherein The determining the first component in response to the first interaction request includes: determining the first component selected by the user in the component orchestration interface in response to the first interaction request; the first interaction request is generated based on the first component selected by the user in the component orchestration interface; The determining the second component that interacts with the first component includes: generating second description information based on the first component information of the first component, the user orchestration information, and the component information of multiple configured components; Input the second description information into a second large model to use the second large model to determine a second component that interacts with the first component from the multiple configured components.

4. The method according to claim 3, wherein The inputting the second description information into the second large model to use the second large model to determine a second component that interacts with the first component from the multiple configured components includes: inputting the second description information into the second large model to use the second large model to determine candidate components that interact with the first component, candidate events corresponding to the first component, and candidate actions corresponding to the candidate components from the multiple configured components, and generating first prompt information based on the candidate components, the candidate events, and the candidate actions; outputting the first prompt information; obtaining a first feedback request triggered by the user for the first prompt information; combining the first feedback request to determine a second component that interacts with the first component, the target event corresponding to the first component, and the target action corresponding to the second component. The target event corresponding to the first component, and the target action corresponding to the second component.

5. The method according to claim 4, wherein The first feedback request includes a first confirmation request or a first update request. The first confirmation request is generated based on the user's first confirmation operation on the first prompt information, and the first update request is generated based on the user's first update operation on the first prompt information. Determining the second component that interacts with the first component, the target event corresponding to the first component, and the target action corresponding to the second component in combination with the first feedback request includes: when the first feedback request is a first confirmation request, generating third description information based on the first prompt information, and inputting the third description information into a third large model to use the third large model to determine that the candidate component is the second component that interacts with the first component, the candidate event corresponding to the first component is the target event corresponding to the first component, and the candidate action corresponding to the candidate component is the target action corresponding to the second component; when the first feedback request is a first update request, obtaining the update information in the first update request, updating the first prompt information based on the update information, generating third description information based on the updated first prompt information, and inputting the third description information into the third large model to use the third large model to determine the second component that interacts with the first component, the target event corresponding to the first component, and the target action corresponding to the second component.

6. The method according to claim 4, wherein The method further includes: sending the first component, the second component, and the interaction content to the user terminal to display an orchestration effect diagram generated based on the first component, the second component, and the interaction content on the component orchestration interface provided by the user terminal.

7. The method according to claim 6, wherein The method further includes: obtaining a second feedback request triggered by the user for the orchestration effect diagram. The second feedback request includes a second confirmation request or a second update request. The second confirmation request is generated based on the user's second confirmation operation triggered on the orchestration effect diagram, and the second update request is generated based on the user's second update operation triggered on the orchestration effect diagram. When the second feedback request is a second confirmation request, generating component orchestration information based on the first component, the second component, and the interaction content. The component orchestration information is used to generate the visualization images corresponding to the first component and the second component respectively based on the original data associated with the first component or the second component, and generate the interaction effect corresponding to the first component and the second component based on the interaction content. When the second feedback request is a second update request, return to the step of outputting the first prompt information and continue to execute.

8. The method according to claim 2, wherein The method further includes: determining an initial component selected by the user in the component orchestration interface; generating fourth description information based on the component information of the initial component, the user orchestration information, and the component information of multiple configured components; inputting the fourth description information into a fourth large model to use the fourth large model to determine the downstream components corresponding to the initial component as the upstream component, the downstream components corresponding to the downstream component as the upstream component, and the target events corresponding to the upstream component and the target actions corresponding to the downstream component; using any two components with an upstream-downstream relationship as the first component and the second component; and generating the first interaction request based on the first component and the second component. The method further includes: sending the initial component, the downstream components corresponding to the initial component as the upstream component, the downstream components corresponding to the downstream component as the upstream component, and the interaction content corresponding to any two components with an upstream-downstream relationship to the client to display, on the component orchestration interface provided by the client, an orchestration effect diagram generated based on the initial component, the downstream components corresponding to the initial component as the upstream component, the downstream components corresponding to the downstream component as the upstream component, and the interaction content corresponding to any two components with an upstream-downstream relationship; wherein the interaction content corresponding to any two components with an upstream-downstream relationship is generated by the first large model based on first description information, and the first description information is generated from the component information corresponding to any two components with an upstream-downstream relationship respectively.

9. The method according to claim 8, wherein The inputting the first description information into the first large model to use the first large model to determine the orchestration-related information corresponding to the first component includes: inputting the first description information into the first large model to use the first large model to determine the second component that interacts with the first component, the target event corresponding to the first component, and the target action corresponding to the second component.

10. The method according to claim 1, wherein, The inputting the first description information into the first large model to use the first large model to determine the second component that interacts with the first component, the target event corresponding to the first component, and the target action corresponding to the second component includes: inputting the first description information into the first large model to use the first large model to determine candidate components that interact with the first component, candidate events corresponding to the first component, and candidate actions corresponding to the candidate components from multiple configured components, and generating first prompt information based on the candidate components, the candidate events, and the candidate actions; outputting the first prompt information; obtaining a first feedback request triggered by the user for the first prompt information; and determining the second component that interacts with the first component, the target event corresponding to the first component, and the target action corresponding to the second component in combination with the first feedback request.

11. The method according to claim 10, wherein ​ 12. The method according to claim 10, wherein It further includes: generating sixth description information based on the first component information of the first component and the second component information of the second component; inputting the sixth description information into a sixth large model to use the sixth large model to determine the interaction content for the interaction between the first component and the second component.

13. The method according to claim 10, wherein The step of inputting the first description information into the first large model to use the first large model to determine the choreography-related information corresponding to the first component includes: 29 Inputting the first description information into the first large model to use the first large model to determine the multi-level components that interact with the first component, the target events corresponding to the upstream components in the multi-level components, and the target actions corresponding to the downstream components; the multi-level components include the downstream components that interact with the first component, and the downstream components in the case where any downstream component is used as an upstream component.

14. The method according to claim 13, wherein It further includes: using any two components with an upstream-downstream relationship as the first component and the second component; generating seventh description information based on the first component information of the first component and the second component information of the second component; inputting the seventh description information into a seventh large model to use the seventh large model to determine the interaction content for the interaction between the first component and the second component.

15. A method for information display, comprising: In response to a user trigger operation on the component choreography interface, generating a first interaction request; Sending the first interaction request to the server, the first interaction request is used to determine the first component, the first component information of the first component is used to generate the first description information, and the first description information is used to input into the first large model to use the first large model to determine the choreography-related information corresponding to the first component.

16. The method according to claim 15, wherein The first description information is generated based on the first component information of the first component and the second component information of the second component that interacts with the first component, and the first large model is used to determine the interaction content for the interaction between the first component and the second component; or, the choreography-related information includes the second component that interacts with the first component, the target event corresponding to the first component, and the target action corresponding to the second component, and the first component information of the first component and the second component information of the second component are also used to generate the sixth description information and use the sixth large model to determine the interaction content for the interaction between the first component and the second component; the method further includes: obtaining the first component, the second component, and the interaction content sent by the server; displaying on the component choreography interface a choreography effect diagram generated based on the first component, the second component, and the interaction content.

17. The method according to claim 16, wherein The method further includes: receiving a first prompt message sent by the server; the first prompt message is generated based on candidate components for interacting with the first component, candidate events corresponding to the first component, and candidate actions corresponding to the candidate components, and the candidate components, the candidate events, and the candidate actions are determined by a second large model in combination with second description information, and the second description information is generated based on first component information of the first component, user orchestration information, and component information of multiple configured components; or determined by the first large model in combination with the first description information; in response to a first confirmation operation or a first update operation triggered for the first prompt message, generating a first feedback request; sending the first feedback request to the server; the first feedback request is used to determine a second component for interacting with the first component, a target event corresponding to the first component, and a target action corresponding to the second component. 30 to implement the second component for interacting with the first component, the target event corresponding to the first component, and the target action corresponding to the second component.

18. A computing device, including a storage component and a processing component; the storage component stores one or more computer program instructions, and the computer program instructions are called and executed by the processing component, and the processing component executes the one or more computer program instructions to implement the data processing method according to any one of claims 1 to 14 and the information display method according to any one of claims 15 to 17.

19. A computer-readable storage medium storing a computer program, and the computer program is executed by a computer to implement the data processing method according to any one of claims 1 to 14, or the information display method according to any one of claims 15 to 17.

20. A computer program product storing a computer program, and when the computer program is executed by a computer, it implements the data processing method according to any one of claims 1 to 14, or the information display method according to any one of claims 15 to 17.

Images