Front-end service integration method, system, equipment and medium

Abstract

The invention discloses a front-end service integration method, system and device and a medium. According to the method, standardized configuration is generated according to front-end service scene requirements; constructing an initial front-end service interaction scene based on the standardized configuration; responding to a multi-mode dialogue message generated by a front end, and packaging the multi-mode dialogue message into a standardized data object; sending the standardized data object to a back end based on the communication related setting so as to receive a data stream fed back by the back end; extracting effective to-be-rendered content from the data stream fed back by the back end; and rendering the effective to-be-rendered content according to the interface related setting and the component mapping related setting so as to update the initial front-end service interaction scene and obtain the target front-end service scene, thereby being capable of generating standardized configuration according to the front-end service scene requirement so as to configure and drive the construction of the front-end service interaction scene, reducing the front-end development threshold, and improving the development efficiency. Therefore, the development efficiency is improved and business innovation is facilitated.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of front-end development, in particular to a front-end business integration method, system, device and medium. BACKGROUND

[0002] With the popularization of artificial intelligence technology, artificial intelligence dialogue systems have been widely used in customer service consultation, product guide, leisure and entertainment and other business scenarios, becoming the core carrier of efficient interaction between enterprises and users, and the efficiency, adaptability and cross-platform consistency of the front-end integration directly affect the business landing speed and user experience, and the related technical requirements are increasingly urgent.

[0003] However, the interface adaptation of the existing front-end integration scheme depends on customized development, the code reuse rate is low, it is difficult to quickly respond to the style and layout requirements of different businesses, and the input and output modes are fixed, the development involves complex links such as communication and state management, not only the development cycle is long and the efficiency is low, but also the business innovation and online speed are seriously restricted. SUMMARY

[0004] The following is a summary of the subject matter described in detail in this document. This summary is not intended to limit the scope of protection of the claims.

[0005] The main purpose of the embodiments of the present disclosure is to provide a front-end business integration method, system, device and storage medium, which can generate standardized configurations according to the front-end business scenario requirements to configure and drive the construction of front-end business interaction scenarios, reduce the development threshold of the front-end, and thus improve the development efficiency, which is conducive to business innovation.

[0006] The first aspect of the embodiments of the present application provides a front-end business integration method, which comprises: generating a standardized configuration according to the front-end business scenario requirements; the business scenario requirements include interface adaptation requirements, communication docking requirements and functional component requirements; the standardized configuration includes interface-related settings, communication-related settings and component mapping-related settings, and the component mapping-related settings are used to associate various types of messages with corresponding rendering components; based on the standardized configuration, an initial front-end business interaction scenario is constructed; in response to the multi-modal dialogue message generated by the front-end, the multi-modal dialogue message is encapsulated into a standardized data object; based on the communication-related settings, the standardized data object is sent to the back-end to receive the data stream fed back by the back-end; extracting valid content to be rendered from the data stream fed back by the back-end; according to the interface-related settings and the component mapping-related settings, the valid content to be rendered is rendered to update the initial front-end business interaction scenario, and a target front-end business scenario is obtained.

[0007] In some embodiments of this application, the step of constructing an initial front-end business interaction scenario based on standardized configuration includes: introducing a software development kit (SDK) into the front-end, and calling the initialization method of the SSD to pass the standardized configuration to the front-end to construct the initial front-end business interaction scenario.

[0008] In some embodiments of this application, the communication-related settings include the backend's interface address, request header information, and authentication key. The step of sending the standardized data object to the backend based on the communication-related settings to receive the data stream returned by the backend includes: Based on the backend's interface address, request header information, and authentication key, a real-time data stream connection is established with the backend; The standardized data object is sent to the backend via the real-time data stream connection to receive the data stream fed back by the backend.

[0009] In some embodiments of this application, the multimodal dialogue message includes at least one of text information, image information, file information, and voice information. In response to the multimodal dialogue message generated by the front end, after encapsulating the multimodal dialogue message into a standardized data object, the method further includes: encapsulating the metadata corresponding to the multimodal dialogue message into the standardized data object, wherein the metadata includes a message creation timestamp and a sender identifier.

[0010] In some embodiments of this application, after extracting valid content to be rendered from the data stream fed back from the backend, the method further includes: adding a corresponding status message prompt in the status management center of the frontend based on the valid content to be rendered.

[0011] In some embodiments of this application, rendering the valid content to be rendered according to the interface-related settings and the component mapping-related settings includes: If the message type of the valid content to be rendered is plain text, the text bubble component is invoked to render the valid content to be rendered. If the message type of the valid content to be rendered is a structured data type, the corresponding structured data rendering component is called according to the component mapping settings to render the valid content to be rendered into an interactive interface element.

[0012] In some embodiments of the present application, the interactive interface element includes a clickable menu button, and in the case where the message type of the valid content to be rendered is a structured data type, the method further comprises, after rendering the valid content to be rendered into an interactive interface element according to the corresponding structured data rendering component based on the component mapping related setting: In response to the operation instruction of the interactive interface element, extracting the multi-modal dialogue message in the operation instruction; Packaging the multi-modal dialogue message in the operation instruction into an updated standardized data object; Based on the communication related setting in the standardized configuration, sending the updated standardized data object to the backend to receive the updated data stream fed back by the backend; Extracting the updated valid content to be rendered from the updated data stream fed back by the backend; According to the interface related setting and the component mapping related setting, rendering the updated valid content to be rendered to update the initial front-end business interaction scene to obtain a first front-end business scene.

[0013] The first aspect of the embodiments of the present application provides a front-end business integration method, which generates a standardized configuration according to the business scene requirements of the front-end, constructs an initial front-end business interaction scene based on the standardized configuration, encapsulates a multi-modal dialogue message into a standardized data object in response to the multi-modal dialogue message generated by the front-end, sends the standardized data object to the backend based on the communication related setting to receive the data stream fed back by the backend, extracts the valid content to be rendered from the data stream fed back by the backend, and renders the valid content to be rendered according to the interface related setting and the component mapping related setting to update the initial front-end business interaction scene to obtain a target front-end business scene. The front-end business interaction scene can be configured and driven by generating a standardized configuration according to the business scene requirements of the front-end, which reduces the development threshold of the front-end and improves the development efficiency, and is conducive to business innovation.

[0014] To achieve the above-mentioned purpose, the second aspect of the embodiments of the present application provides a front-end business integration system, which comprises: A generation module is configured to generate a standardized configuration according to the business scene requirements of the front-end; the business scene requirements include interface adaptation requirements, communication docking requirements and functional component requirements; the standardized configuration includes interface related settings, communication related settings and component mapping related settings, and the component mapping related settings are used to associate each type of message with a corresponding rendering component; A construction module is configured to construct an initial front-end business interaction scene based on the standardized configuration; A response module is configured to encapsulate a multi-modal dialogue message into a standardized data object in response to the multi-modal dialogue message generated by the front-end. a sending module, configured to send the standardized data object to a backend based on the communication-related settings, to receive a data stream fed back by the backend; an extracting module, configured to extract valid content to be rendered from the data stream fed back by the backend; a rendering module, configured to render the valid content to be rendered according to the interface-related settings and the component mapping-related settings, to update the initial front-end service interaction scene, and obtain a target front-end service scene.

[0015] To achieve the above object, a third aspect of the embodiments of the present application provides an electronic device, comprising: at least one control processor and a memory connected with the at least one control processor; the memory stores instructions executable by the at least one control processor, and the instructions are executed by the at least one control processor to enable the at least one control processor to execute the front-end service integration method.

[0016] To achieve the above object, a fourth aspect of the embodiments of the present application provides a computer readable storage medium, which stores computer executable instructions, and the computer executable instructions are used to enable a computer to execute the front-end service integration method.

[0017] It can be understood that the beneficial effects of the second aspect to the fourth aspect and the related technologies compared with the first aspect and the related technologies are the same, and can be referred to the related description in the first aspect, which will not be repeated here. BRIEF DESCRIPTION OF DRAWINGS

[0018] The above and / or additional aspects and advantages of the present application will become apparent and more readily appreciated from the following description of the embodiments, taken in conjunction with the accompanying drawings, in which: Figure 1 is a flow diagram of a front-end service integration method provided by the embodiments of the present application; Figure 2 is a case diagram provided by the embodiments of the present application; Figure 3 is a structural diagram of a front-end service integration system provided by the embodiments of the present application; Figure 4 is a hardware structural diagram of an electronic device provided by the embodiments of the present application. DETAILED DESCRIPTION

[0019] Embodiments of the present application are described below in detail, examples of which are shown in the accompanying drawings, wherein the same or similar notations represent the same or similar elements or elements having the same or similar functions throughout. The embodiments described below by referring to the accompanying drawings are exemplary only, and are used only for explanation of the present application, and cannot be understood as a limitation of the present application.

[0020] In the description of the present application, if there is a description to first, second, etc., it is only for the purpose of distinguishing technical features, and cannot be understood as indicating or implying relative importance or implicitly indicating the number of indicated technical features or the order of indicated technical features.

[0021] In the description of the present application, it is to be understood that the orientation description, such as the orientation or position relationship indicated by up, down, etc., is based on the orientation or position relationship shown in the drawings, only for the purpose of facilitating the description of the present application and simplifying the description, and is not to indicate or imply that the device or element referred to must have a particular orientation, be constructed and operated in a particular orientation, and therefore cannot be understood as a limitation of the present application.

[0022] In the description of the present application, it is to be understood that, unless otherwise explicitly limited, the words such as setting, installing, connecting, etc. should be broadly understood, and the person skilled in the art can reasonably determine the specific meaning of the above words in the present application in combination with the specific content of the technical solution.

[0023] With the popularization of artificial intelligence technology, artificial intelligence dialogue systems are widely used in customer service, shopping guide, entertainment and other business scenarios. However, front-end developers face many common technical challenges when integrating such systems: 1. User interface adaptation is complex: different business scenarios have different needs for chat interface style, layout, etc. Existing solutions are mostly custom developed, with low code reuse rate, and a lot of repetitive work is required for each access, making it difficult to quickly respond to business changes.

[0024] 2. Input and output modes are fixed: the input of artificial intelligence dialogue is not limited to text, but may also include pictures, files, voice, etc.; the output mode is also diverse, such as streaming response, structured data (such as product cards), plain text, etc. Traditional software development kits often support limited modes, and extending new input / output types requires modifying underlying code, which is not flexible.

[0025] 3. Poor cross-platform compatibility: existing integration solutions often provide different traditional software development kits for specific platforms (such as WorldWide Web (Web), applet, Application (APP)), resulting in a doubling of development, testing and maintenance costs, and making it impossible to achieve "one code, multiple platforms".

[0026] 4. Low development efficiency: building a stable, beautiful and fully functional artificial intelligence chat interface from scratch involves complex aspects such as communication, state management, component development, etc., which usually takes several weeks of time and seriously restricts business innovation and online speed.

[0027] 5. Difficult to process streaming responses: large model artificial intelligence dialogue usually uses streaming output, such as Server-Sent Events (SSE), which requires processing real-time data streams, typewriter effects, interruption control and other complex logic. Traditional solutions lack a unified streaming data processing mechanism.

[0028] Therefore, an embodiment of the present application provides a front-end business integration method and system, electronic equipment and medium, which aims to generate standardized configurations according to the needs of front-end business scenarios, to configure and drive the construction of front-end business interaction scenarios, reduce the development threshold of front-end, and thus improve the development efficiency, which is conducive to business innovation.

[0029] The front-end business integration method, system, electronic equipment and medium provided by the embodiment of the present application are specifically explained by the following embodiments. First, the front-end business integration method in the embodiment of the present application is described.

[0030] The embodiment of the present application can acquire and process related data based on artificial intelligence technology. Among them, artificial intelligence (AI) is to use digital computers or computer-controlled machines to simulate, extend and expand human intelligence, perceive the environment, acquire knowledge and use knowledge to obtain the best results. Theory, method, technology and application system.

[0031] The basic technology of artificial intelligence generally includes technologies such as sensors, special artificial intelligence chips, cloud computing, distributed storage, big data processing technology, operation / interaction system, mechatronics, etc. Artificial intelligence software technology mainly includes computer vision technology, robot technology, biometric technology, speech processing technology, natural language processing technology, and machine learning / deep learning, etc. Several major directions.

[0032] The front-end service integration method provided in the embodiments of the present application relates to the technical field of front-end development. The front-end service integration method provided in the embodiments of the present application can be applied to a terminal, can be applied to a server side, and can also be software running in the terminal or the server side. In some embodiments, the terminal can be a smart phone, a tablet computer, a notebook computer, a desktop computer, or the like; the server side can be configured as a stand-alone physical server, can be configured as a server cluster or a distributed system formed by multiple physical servers, or can be configured as a cloud server providing basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, CDNs, and big data and artificial intelligence platforms; and the software can be an application that implements the front-end service integration method, but is not limited to the above forms.

[0033] The present application can be used in many general or special computer system environments or configurations. For example: personal computers, server computers, handheld or portable devices, tablet devices, multiprocessor systems, microprocessor-based systems, set-top boxes, programmable consumer electronics, network PCs, minicomputers, mainframe computers, distributed computing environments including any of the above systems or devices, and the like. The present application can be described in the general context of computer-executable instructions executed by a computer, such as program modules. Generally, program modules include routines, programs, objects, components, data structures, and the like that perform specific tasks or implement specific abstract data types. The present application can also be practiced in a distributed computing environment, in which tasks are performed by remote processing devices connected by a communication network. In a distributed computing environment, program modules can be located in local and remote computer storage media, including storage devices.

[0034] It should be noted that in each specific embodiment of the present application, when relevant processing needs to be performed on data related to the identity or characteristics of a user, such as user information, user behavior data, user history data, and user location information, the user's permission or consent will be obtained first, and the collection, use, and processing of such data will comply with relevant laws, regulations, and standards. In addition, when the embodiments of the present application need to obtain sensitive personal information of a user, the user's separate permission or separate consent will be obtained through a pop-up window or by jumping to a confirmation page, and after obtaining the user's separate permission or separate consent, the necessary user-related data for enabling the embodiments of the present application to function normally will be obtained.

[0035] To this end, reference is made to Figure 1The embodiment of the application provides a front-end service integration method, the method is applied to a central controller, the controller can be a server, can be an electronic device, can also be a mobile terminal, and the like, and here is not specifically limited, and the method comprises the following steps S110 to S160.

[0036] In step S110, a standardized configuration is generated according to a service scene requirement of a front end; the service scene requirement comprises an interface adaptation requirement, a communication docking requirement and a functional component requirement; the standardized configuration comprises an interface-related setting, a communication-related setting and a component mapping-related setting, and the component mapping-related setting is used for associating various types of messages with corresponding rendering components; In step S120, an initial front-end service interaction scene is constructed based on the standardized configuration. In step S130, a multi-modal dialogue message generated by the front end is encapsulated into a standardized data object. In step S140, the standardized data object is sent to a back end based on the communication-related setting, so as to receive a data stream fed back by the back end. In step S150, valid content to be rendered is extracted from the data stream fed back by the back end. In step S160, the valid content to be rendered is rendered according to the interface-related setting and the component mapping-related setting, so as to update the initial front-end service interaction scene and obtain a target front-end service scene.

[0037] In this step, first, abstract service scene requirements are converted into declarative standardized configurations that can be recognized and executed by a system. Among them, the three dimensions of service scene requirements each have a clear direction: the interface adaptation requirement covers the differentiated demands of different businesses on the style, layout and visual presentation of the chat window (such as the simple style of the customer service scene and the lively style of the shopping guide scene); the communication docking requirement focuses on the interaction rules of the front end and the back end artificial intelligence service, including the docking service address, the identity authentication method, the security specification of data transmission, etc.; the functional component requirement clearly indicates the specific functional modules (such as whether to support file uploading and voice input) and custom interaction elements (such as structured menus and product cards) that need to be enabled by the business.

[0038] Further, the standardized configuration generated based on the service scene requirement is not a simple list of parameters, but a complete scheme containing more than 120 fine-tuned settings, thereby realizing accurate conversion of “requirements-configuration”, allowing the business party to adapt to diversified scenes only by adjusting the configuration without modifying the underlying code of the software development kit, and completely getting rid of the repetitive labor of traditional customized development.

[0039] Specifically, the interface-related settings correspond to interface adaptation requirements, clearly defining visual and layout rules such as chat window theme color, font size, message bubble style, layout size, etc. Communication-related settings match communication interface requirements, including backend interface address, request header information, and authentication key. Component mapping-related settings precisely respond to functional component requirements, establishing an association between multiple types of messages (such as ordinary text, pictures, and structured data) and corresponding rendering components, laying the foundation for subsequent dynamic component scheduling.

[0040] Further, a software development kit is introduced in the front end to call the initialization method of the software development kit to pass in the standardized configuration to the front end, and to build an initial front-end business interaction scene. Specifically, the developer needs to first introduce the software development kit of the application front-end business integration method in the front-end project (such as a project based on the React framework), and by calling the initialization method provided by the tool kit, the standardized configuration is passed in as a parameter. The tool kit will automatically parse each rule in the configuration and complete system initialization.

[0041] Among them, the software development kit (SDK) is the core carrier for realizing the rapid, flexible, and cross-end integration of front-end business (the core is the front-end business integration method), and is a one-stop solution based on the React framework, component-based development, and server-sent events. Its essence is to encapsulate complex front-end communication, state management, component rendering, cross-end adaptation, and other logic into a set of directly callable tools. It has seven core functional modules built-in, including configuration parsing module, input processing module, communication module, streaming processing module, state management center, dynamic rendering module, and cross-end adaptation module, thus forming a complete automatic processing pipeline.

[0042] Specifically, the configuration parsing module can read and parse the declarative standardized configuration covering more than 120 interface, communication, component mapping, etc. settings, and convert business requirements into executable rules of the system; the input processing module is responsible for intercepting user multi-modal interaction (text, picture, file, voice, interactive element operation, etc.), and encapsulating the original message and metadata (timestamp, sender identification) into a standardized data object with a unified structure according to the predefined standardized protocol, solving the problem of inconsistent formats of multiple input types; the communication module supports secure connection establishment based on interface address, request header, authentication key, adopts a transmission mechanism that adapts to the backend streaming response, realizes real-time data flow connection and data transmission between the front and back ends, and is compatible with multi-end communication adaptation; the streaming processing module continuously listens to the data stream returned by the backend, analyzes the data block in real time, extracts the effective content, and synchronously updates to the state management center, providing support for real-time interaction such as "typewriter effect"; the state management center uniformly maintains data such as dialogue message list, component state, and interaction context, ensuring the consistency of system data flow; the dynamic rendering module relies on the component dynamic registration system, dispatches the matching rendering components (50+ atomic components and custom components) to complete content presentation according to the message type and component mapping rules, while complying with interface-related settings to ensure visual uniformity; the cross-end adaptation module can identify the front-end running environment (web page, applet, application, etc.), call the corresponding underlying adapter component, and realize "one code, multiple running".

[0043] Further, during the construction process, the component dynamic registration system is activated synchronously, and 50+ atomic components and custom registration components declared in the configuration are loaded to ensure that the component resources required for subsequent rendering are ready; at the same time, based on the cross-end adaptation mechanism of context awareness, the toolkit can automatically identify the running environment of the current front-end project (such as web page, applet, application), call the underlying adapter component of the corresponding environment, and ensure the consistency of the basic functions and interaction logic of the initial scene on different platforms, finally realize the rapid generation of an initial interactive scene with complete functions and adaptation to the target environment only by configuration driving, greatly shortening the scene building cycle.

[0044] Further, in response to the user's interaction information (multi-modal dialogue message, such as input text, uploaded picture, sent voice, and clicked shortcut menu) on the front-end interface, the input processing module of the software development kit encapsulates the user's original message and necessary metadata (such as message creation timestamp and sender identification) into a standardized data object with a unified structure according to the predefined standardized protocol. Among them, the multi-modal dialogue message includes at least one of text information, picture information, file information, and voice information.

[0045] Specifically, the multi-modal dialogue message and the metadata corresponding to the multi-modal dialogue message are encapsulated into a standardized data object according to a predefined standardized protocol. The standardized protocol is the key to realizing multi-input type compatibility, which defines a unified data structure specification. Regardless of the type of the original input, it will finally be converted into a format that can be uniformly recognized and processed by the system, avoiding the problem of separately adapting the processing logic due to different input types in traditional solutions, and providing a unified data basis for subsequent cross-platform transmission, backend interaction, and component rendering.

[0046] Further, the core parameters of the communication-related settings in the standardized configuration are read, including the interface address of the backend artificial intelligence service, the request header information, the authentication key, and the like. Then, the transmission mechanism (such as the Server-Sent Events protocol) of the backend streaming response is selected and adapted through the communication module of the software development kit, and a real-time data stream connection is established with the backend, thereby supporting the continuous transmission of data and perfectly adapting to the streaming output characteristics of large model artificial intelligence dialogue.

[0047] Further, after the connection is established, the encapsulated standardized data object is sent to the backend as a request body through the real-time data stream connection; at the same time, the persistence of the connection is maintained to receive the data stream fed back by the backend. The backend will gradually return response data according to the user request, forming a continuous data stream transmission, and realizing efficient processing of real-time streaming response.

[0048] Further, after extracting the valid content to be rendered from the data stream fed back by the backend, a corresponding state message prompt is added in the state management center on the front end according to the valid content to be rendered. Specifically, the streaming processing module of the software development kit continuously listens to the data stream transmitted by the backend, reads each data block in the data stream in order, and parses the valid content (such as text fragments, structured data fields, picture links, etc.) in real time. In the parsing process, instead of waiting for all data transmission to be completed and then processing all at once, a "step-by-step extraction" approach is adopted, where the valid content to be rendered corresponding to each data block is extracted as it is parsed, and the extracted content is simultaneously updated to the state management center of the system, so as to maintain the message list of the current dialogue in real time through the state management center, and add an assistant message with a state of "inputting" to provide intuitive interaction feedback to the user.

[0049] Further, the interface-related settings in the standardized configuration are read to ensure that the rendering process strictly follows the visual specifications required by the business (such as theme color, font size, message bubble style, etc.), and to ensure that the interface presentation is highly consistent with the design draft. At the same time, according to the component mapping-related settings, the rendering component that matches the message type (such as ordinary text, structured data) of the valid content to be rendered is dispatched from the component dynamic registration system.

[0050] Specifically, if it is a normal text type, a built-in text bubble component is called to render in real time with a "typewriter" effect that displays word by word, improving the user interaction experience; if it is a structured data type (such as a "guess you want to ask" menu, a product card), a pre-registered custom structured data rendering component is called to render the content into clickable and interactive interface elements.

[0051] Further, after rendering is completed, the new rendered content is integrated into the initial front-end business interaction scene to complete dynamic updating of the scene, forming a target front-end business scene with complete functions and smooth interaction, so that the entire process does not require developers to write additional rendering logic, and through reuse of atomic components, the uniformity of visual language and interaction experience in different business scenes is ensured, and the cross-end adaptation mechanism ensures consistent performance of the updated scene on each platform.

[0052] In an embodiment, taking the integration of a customer service robot scene in a Web project as an example, a developer first installs and introduces a system software development kit. Specifically, the developer uses tools such as a node package manager (Node Package Manager, npm) to install the software development kit of the present technology as a project dependency in a front-end project (for example, a project built based on a React framework), and imports the core components and function functions provided by the software development kit through an import statement in a business code file that needs to integrate a chat robot.

[0053] Further, the developer creates a standardized configuration object (usually represented in JavaScript object or JSON format), which will drive the behavior and appearance of the entire chat system to configure the driving page, and the configuration object includes but is not limited to communication configuration, interface theme configuration, function component configuration, and streaming protocol configuration, etc. key parts. Among them, the communication configuration specifies the application programming interface (Application Programming Interface, API) address, request header information, authentication key, etc. of the back-end artificial intelligence service; the interface theme configuration refers to defining the theme color, font size, message bubble style, layout size, etc. of the chat window; the function component configuration refers to declaring the function modules that need to be enabled, such as whether to enable file upload, voice input, and register custom message type rendering components (such as structured data components for rendering "guess you want to ask" menus); the streaming protocol configuration specifies the streaming protocol used for communication with the back-end service, such as server-sent events (Server-Sent Events), and configures related parameters.

[0054] Further, the developer calls an initialization method provided by the software development kit in the business component, and passes in the standardized configuration object defined in the second step. The method returns a chat component instance that has been configured. Then, the developer renders the instance to a specified location on the application page. At this point, the user can see a chat interface that is generated according to the configuration and has a unified style.

[0055] Further, the user accesses the configured interface, inputs text such as “query claim progress” in the input box of the chat interface, and clicks to send, or clicks the shortcut message bar to send a message. At the same time, the input processing module of the software development kit intercepts the user interaction event, and encapsulates the original text input by the user and necessary metadata (such as a message creation timestamp, a sender identifier) into a structured and standardized data object according to a predefined standardized protocol, so as to unify diversified inputs into a standard format that can be processed internally.

[0056] Further, the communication module of the software development kit automatically selects a server sending event protocol according to the initialization configuration, and establishes a one-way real-time data stream connection with a backend service address specified in the configuration. Specifically, the standardized data object is sent to the backend artificial intelligence service as a request body, so that the request is processed by the backend service, and a response is returned in the form of a data stream.

[0057] Further, the streaming processing module of the software development kit continuously listens to the data stream, so as to analyze the incoming data blocks in real time, extract valid text content, and immediately update the internal state management center (for example, update the message list of the current conversation, and add an assistant message with a state of “inputting”).

[0058] Further, the renderer of the software development kit dynamically schedules and loads corresponding rendering components from the registered component library according to the type of the current message (for example, ordinary text, pictures, card components, product cards, etc.). Specifically, for ordinary text, a built-in text bubble component is used for rendering, and a “typewriter” effect is simulated to display the text character by character; for specific types of data returned by the backend (such as the “guess you want to ask” menu shown in FIG. 8B), the renderer schedules and enables a custom structured data rendering component registered in advance in the configuration, and renders it as a clickable button menu. Figure 2

[0059] ​Further, after the user clicks the menu item, the operation triggers the process again, starting from "the communication module of the software development kit automatically selects the server sending event protocol according to the initialization configuration, and establishes a one-way real-time data stream connection with the backend service address specified in the configuration". The entire process does not require developers to write additional communication or rendering logic, and is completed by configuration and the automatic pipeline of the software development kit. Moreover, although the present example takes the Web environment as an example, the software development kit of the present embodiment is based on cross-end technology. When the same set of business code needs to run on the Mini Program or Application (APP) platform, the software development kit will automatically identify the current running environment during the initialization stage and call the underlying adapter component optimized for the corresponding platform, thereby ensuring consistent behavior and user experience of the chat function on different platforms, and truly realizing "one set of code, multiple-end running".

[0060] Therefore, in the present embodiment, the developer does not need to pay attention to complex communication details, state management and component rendering logic. By means of a declarative configuration file, a complete, smooth and customizable artificial intelligence customer service dialogue system can be quickly and high-quality integrated in a Web project, thereby improving the development efficiency, ensuring flexibility and realizing cross-end consistency.

[0061] In an embodiment of the present embodiment, based on the React framework, component-based development and server-sent event technology, a front-end artificial dialogue system rapid integration system based on configurable components is realized by referring to the front-end business integration method. The core is to build an automatic processing pipeline driven by configuration and with one-way data flow.

[0062] Specifically, the front-end artificial dialogue system rapid integration system is first driven by a declarative standardized configuration (covering more than 120 settings such as interface, communication, component mapping, etc.) to initialize the entire system. When a message is generated by user interaction, the system will encapsulate it into a standardized data object using a unified multi-modal message protocol, and then communicate with the backend service through a multi-protocol adaptive streaming exchange mechanism to stably process the streaming response. The message content is updated to the state management center of the system in real time, and the renderer drives the rendering component to present according to the message type from a hot-pluggable component dynamic registration system. The entire process is assisted by an intelligent cross-end adaptation scheme based on context awareness to ensure consistent experience in different running environments.

[0063] Therefore, the present embodiment, through the synergy of the above five technical features, changes the development of artificial intelligence dialogue function from traditional "hard coding" to "configuration driving", and systematically solves the industry common technical challenges such as complex page adaptation, fixed input and output mode, and poor cross-platform compatibility, so that the development efficiency is improved by more than 90%.

[0064] In some embodiments, in step S120, based on the communication-related settings, the standardized data object is sent to the backend to receive the data stream fed back by the backend, including steps S210 to S220: Step S210, based on the interface address of the backend, the request header information and the authentication key, a real-time data stream connection is established with the backend; Step S220, the standardized data object is sent to the backend through the real-time data stream connection to receive the data stream fed back by the backend.

[0065] In this embodiment, the core logic is to establish a safe and continuous real-time data stream connection based on the communication core parameters in the standardized configuration through a specialized communication mechanism. Specifically, relying on the communication module of the preset software development kit (SDK), the three key parameters of the interface address, the request header information and the authentication key of the backend are first accurately read from the standardized configuration, wherein the interface address specifies the specific communication target of the backend artificial intelligence service, providing accurate pointing for data transmission; the request header information contains the format specification, encoding method and other interaction rules of data transmission, ensuring consistent data analysis logic between the front and back ends; the authentication key undertakes the security verification function, avoids illegal access through identity verification, and ensures the security of data transmission.

[0066] Further, through the communication module, the transmission mechanism (such as the server-sent event protocol) adapted to the backend streaming response is selected to realize one-way continuous transmission of data from the backend to the frontend through the transmission mechanism, perfectly matching the streaming output characteristics of large model artificial intelligence dialogue. At the same time, combined with the cross-end adaptation capability built-in software development kit, the current front-end running environment (such as web page, applet and application) is identified through the communication module, and the corresponding environment underlying communication adapter is called to solve the communication protocol difference problem of different platforms, ensuring the stability and compatibility of the connection in various environments.

[0067] Further, first, follow the predefined standardized protocol to encapsulate multi-modal dialogue messages (text, pictures, files, voice, etc.) and metadata (message creation timestamp, sender identification) into a unified structured data to obtain a standardized data object, ensuring that the backend service can directly identify and analyze, avoiding the interaction failure caused by non-uniform data format in traditional solutions.

[0068] Further, the standardized data object is sent as a request body through the communication module of the software development kit to the backend interface through the established real-time data stream connection. The transmission process strictly follows the security specifications and data format requirements in the communication-related settings, ensuring the integrity and security of data transmission. At the same time, the connection is not interrupted after data transmission, and the listening state is maintained to receive the data stream feedback from the backend. The response results are split into multiple data blocks for real-time processing based on user requests, and returned to the front end in a streaming manner, realizing the mode of continuous transmission and real-time reception, adapting to the streaming output characteristics of large model artificial intelligence dialogue. At the same time, the continuous transmission of data stream also provides data support for subsequent front-end implementation of "typewriter effect" and other smooth interaction experiences. The entire process does not require human intervention and is automatically completed by the kit, significantly reducing the processing cost of communication logic for developers.

[0069] In some embodiments, in step S160, the valid content to be rendered is rendered according to the interface-related settings and the component mapping-related settings, including the following steps S310 to S320: Step S310, in the case that the message type of the valid content to be rendered is a normal text type, a text bubble component is called to render the valid content to be rendered; Step S320, in the case that the message type of the valid content to be rendered is a structured data type, according to the component mapping-related settings, a corresponding structured data rendering component is called to render the valid content to be rendered into an interactive interface element.

[0070] In this embodiment, during the rendering process, first, all parameters of the interface-related settings in the standardized configuration are read, including the theme color of the chat window, the font size, the shape of the message bubble, the round angle, the spacing, and other visual rules, to ensure that the text rendering strictly matches the design requirements of the business scenario and realizes high-fidelity restoration of the design draft. At the same time, combined with the characteristics of the backend streaming response, the text rendering is not presented in one time, but is displayed in real time word by word in a "typewriter" effect, to realize deep linkage with the streaming data extraction logic. The streaming processing module synchronizes the text bubble component to the state management center every time a text segment is parsed, to drive the text bubble component to update and display word by word, so that the user obtains a smooth interaction experience similar to real conversation. In addition, the text bubble component adapts to the current front-end running environment (web page, applet, application program, etc.), and maintains consistent rendering effect and interaction logic on different platforms, without the need for developers to adapt to different platforms individually, which not only guarantees the uniformity of user experience, but also significantly reduces the multi-end development and maintenance cost.

[0071] Further, the structured data is accurately converted to the interactive interface elements through the component mapping mechanism, meeting the functional requirements of complex business scenarios. The interactive interface elements include clickable menu buttons, and the structured data types cover common non-text data in business scenarios, such as the quick menu of “Guess you want to ask”, product recommendation cards, and claim material lists, which need to be presented through specific interactive components to have practical value.

[0072] Specifically, first, according to the component mapping related settings in the standardized configuration, the preset rendering component corresponding to the current structured data type is queried, and then the target component is determined. After that, the structured data rendering component is called from the component dynamic registration system, the structured data returned by the backend (such as menu options, product parameters, link addresses, etc.) is parsed and visually presented according to the rendering rules preset by the component, and finally converted into interface elements that can be directly operated by the user, such as clickable menu buttons, product cards with jump function, and checkable material lists, etc. During the rendering process, the visual specifications of the interface related settings are strictly followed to ensure that the theme color, font, layout of the structured component are consistent with the overall chat interface, and the unified visual language is maintained.

[0073] Among them, the registration information of various structured data identifiers and corresponding components has been pre-associated in the component mapping settings, including both the standardized structured components built-in the toolkit and the custom components registered by the business party according to the needs, which has strong flexibility. In addition, when the user clicks, checks, or performs other operations on these interactive interface elements, the operation will be intercepted by the input processing module of the toolkit, and automatically converted into a new multi-modal dialogue message. The complete process of “standardized encapsulation-backend transmission-data stream reception-content extraction-rendering update” is repeated to form a closed loop of business interaction, so that the underlying code of the toolkit does not need to be changed, greatly improving the adaptation efficiency and functional expansibility of the business scenario.

[0074] In some embodiments, in the case where the message type of the valid content to be rendered is a structured data type in step S320, according to the component mapping related settings, the corresponding structured data rendering component is called to render the valid content to be rendered into an interactive interface element, and then the following steps S410 to S450 are included: Step S410, in response to the operation instruction of the interactive interface element, extracting the multi-modal dialogue message in the operation instruction; Step S420, encapsulating the multi-modal dialogue message in the operation instruction into an updated standardized data object; Step S430, based on the communication related settings in the standardized configuration, sending the updated standardized data object to the backend to receive the updated data stream fed back by the backend; Step S440: Extract the updated valid content to be rendered from the updated data stream returned by the backend; Step S450: Render the updated valid content to be rendered according to the interface-related settings and component mapping-related settings to update the initial front-end business interaction scenario and obtain the first front-end business scenario.

[0075] In this embodiment, after the structured data is rendered into interactive interface elements (such as the "Guess What You May Ask" menu button, product recommendation card, and claim material checklist), when the user performs operations such as clicking or checking these elements, the input processing module of the software development kit (SDK) will intercept the operation command in real time, and then parse the core intent of the operation command to extract the corresponding multimodal dialogue message.

[0076] For example, such as Figure 2 As shown, when the "Check Claim Progress" button is clicked, the text-based dialogue message associated with that button is extracted; when a certain type of claim material is selected, the structured dialogue message containing the material name is extracted. The extraction process strictly follows a predefined standardized protocol to ensure that the format of the obtained messages is consistent with the multimodal messages actively entered by the user, providing a unified data foundation for subsequent encapsulation and transmission. This also ensures the continuity and consistency of the interaction logic, allowing user operations to seamlessly connect to the backend service call process.

[0077] Furthermore, the pre-defined encapsulation rules in the standardized configuration are first read, and the extracted multimodal dialogue messages and newly generated metadata (including the message creation timestamp, sender identifier, etc. corresponding to the operation) are encapsulated together according to the predefined standardized protocol to form a standardized updated data object with a unified structure.

[0078] Furthermore, by reading the pre-set communication settings in the standardized configuration (including backend interface address, request header information, authentication keys, and other core parameters), there is no need to reconfigure communication rules. The real-time data stream connection is reused (or the connection is automatically rebuilt based on the connection status). Adopting a transmission mechanism adapted to the backend streaming response, the updated standardized data object is used as the request body and accurately sent to the backend artificial intelligence service through this connection. By reusing communication configuration and connection resources, network overhead is reduced while ensuring the real-time performance of data transmission. At the same time, the continued validity of the authentication key ensures the security of secondary transmission, and the cross-platform adaptation mechanism continues to play its role. Regardless of whether the current frontend operating environment is a web page, a mini-program, or an application, the communication link can be kept stable and compatible, laying a reliable foundation for receiving updated data streams in the future.

[0079] Further, continuously monitor the updated data stream returned by the backend, and parse the valid information in each data stream in real time according to the transmission order of the data blocks. During the parsing process, the updated valid content to be rendered is extracted step by step to avoid interaction delay caused by waiting for complete data stream; at the same time, the extracted content is synchronized to the state management center of the SDK in real time, the message list of the current conversation is updated, and the "inputting" assistant message prompt is automatically added to provide intuitive interaction feedback for the user.

[0080] Further, read the interface-related settings to ensure that the rendering effect is consistent with the visual specifications of the overall chat interface, maintain a unified visual language, and then dispatch the matching rendering component from the component dynamic registration system according to the message type of the updated valid content to be rendered based on the component mapping-related settings.

[0081] Specifically, if it is ordinary text, the text bubble component is called to render in real time with a "typewriter" effect; if it is new structured data (such as a claim settlement progress detail card or a list of materials to be supplemented), the corresponding custom structured data rendering component is called to render as a new interactive or display interface element.

[0082] Further, after rendering is complete, the new rendering content is integrated into the current front-end business interaction scene (i.e., the state of the initial front-end business interaction scene after the first update described above), completing the dynamic iteration of the scene, forming a first front-end business scene that is more user-friendly, and achieving the entire process without the need for developers to write additional rendering or scene update code, ensuring consistent user experience across different interaction links, while significantly improving the dynamic adaptation capability and development efficiency of the business scene.

[0083] As shown in Figure 3 some embodiments of the present application, a front-end business integration system is provided, which includes a generation module 310, a construction module 320, a response module 330, a sending module 340, an extraction module 350, and a rendering module 360, specifically: The generation module 310 is configured to generate standardized configurations according to the business scene requirements of the front end; the business scene requirements include interface adaptation requirements, communication interface requirements, and functional component requirements; the standardized configurations include interface-related settings, communication-related settings, and component mapping-related settings, and the component mapping-related settings are used to associate each type of message with the corresponding rendering component; The construction module 320 is configured to construct an initial front-end business interaction scene based on the standardized configurations; The response module 330 is configured to encapsulate the multi-modal conversation message as a standardized data object in response to the multi-modal conversation message generated by the front end; The sending module 340 is configured to send the standardized data object to the backend based on the communication-related setting, to receive a data stream fed back by the backend; The extracting module 350 is configured to extract valid content to be rendered from the data stream fed back by the backend; The rendering module 360 is configured to render the valid content to be rendered according to the interface-related setting and the component mapping-related setting, to update the initial front-end business interaction scene, and obtain a target front-end business scene.

[0084] It should be noted that the front-end business integration system provided in the embodiment is based on the same inventive concept as the above-described front-end business integration method, and thus the related content of the above-described front-end business integration method is also applicable to the content of the front-end business integration system, and thus will not be described herein again.

[0085] To this end, the system generates a standardized configuration according to the front-end business scene requirement, constructs an initial front-end business interaction scene based on the standardized configuration, encapsulates a multi-modal dialogue message generated by the front end into a standardized data object in response to the multi-modal dialogue message, sends the standardized data object to the backend based on a communication-related setting, to receive a data stream fed back by the backend, extracts valid content to be rendered from the data stream fed back by the backend, and renders the valid content to be rendered according to an interface-related setting and a component mapping-related setting, to update the initial front-end business interaction scene, and obtain a target front-end business scene. In this way, the standardized configuration can be generated according to the front-end business scene requirement to configure and drive the construction of the front-end business interaction scene, which reduces the front-end development threshold and thus improves the development efficiency, and is conducive to business innovation.

[0086] The embodiment of the present application also provides an electronic device, which comprises a memory and a processor, the memory stores a computer program, and the processor implements the above-mentioned front-end business integration method when executing the computer program.

[0087] As Figure 4 , Figure 4 The hardware structure schematic diagram of the electronic device provided in the embodiment of the present application is shown in FIG. 1. The electronic device comprises: at least one battery; at least one memory; at least one processor; at least one program; The program is stored in the memory, and the processor executes the at least one program to implement the above-mentioned front-end business integration method.

[0088] The electronic device can be any intelligent terminal, such as a mobile phone, a tablet computer, a personal digital assistant (PDA), a vehicle-mounted computer, etc.

[0089] The electronic devices according to embodiments of this application will now be described in detail.

[0090] The processor 1600 can be implemented using a general-purpose central processing unit (CPU), microprocessor, application-specific integrated circuit (ASIC), or one or more integrated circuits, and is used to execute relevant programs to implement the technical solutions provided in the embodiments of this disclosure. The memory 1700 can be implemented as a read-only memory (ROM), static storage device, dynamic storage device, or random access memory (RAM). The memory 1700 can store the operating system and other applications. When the technical solutions provided in the embodiments of this specification are implemented through software or firmware, the relevant program code is stored in the memory 1700 and is called and executed by the processor 1600 to perform a front-end service integration method according to an embodiment of this disclosure.

[0091] The input / output interface 1800 is used to implement information input and output. The communication interface 1900 is used to enable communication and interaction between this device and other devices. Communication can be achieved through wired means (such as USB, Ethernet cable, etc.) or wireless means (such as mobile network, WIFI, Bluetooth, etc.). Bus 2000 transmits information between various components of the device (e.g., processor 1600, memory 1700, input / output interface 1800, and communication interface 1900); The processor 1600, memory 1700, input / output interface 1800 and communication interface 1900 are connected to each other within the device via bus 2000.

[0092] This disclosure also provides a storage medium, which is a computer-readable storage medium storing computer-executable instructions for causing a computer to execute the aforementioned front-end business integration method.

[0093] Memory, as a non-transitory computer-readable storage medium, can be used to store non-transitory software programs and non-transitory computer-executable programs. In addition, the memory can include a high-speed random access memory and can also include a non-transitory memory, such as at least one magnetic disk storage device, a flash memory device, or other non-transitory solid-state memory device. In some embodiments, the memory can optionally include a memory that is remotely disposed relative to the processor, and these remote memories can be connected to the processor through a network. Examples of the above network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0094] The embodiments described in the embodiments of the present disclosure are used to more clearly illustrate the technical solutions of the embodiments of the present disclosure, and do not constitute a limitation on the technical solutions provided by the embodiments of the present disclosure. Those skilled in the art can know that, as technology evolves and new application scenarios appear, the technical solutions provided by the embodiments of the present disclosure are also applicable to similar technical problems.

[0095] Those skilled in the art can understand that the technical solutions shown in the figures do not constitute a limitation on the embodiments of the present disclosure, and can include more or fewer steps than the figures shown, or combine certain steps, or different steps.

[0096] The device embodiments described above are only schematic, and units described as separate components can or can not be physically separate, i.e., can be located in one place, or can be distributed on multiple network units. Part or all of the modules can be selected according to actual needs to achieve the purpose of the embodiments of the present disclosure.

[0097] Those skilled in the art can understand that all or some of the steps in the above disclosed method, the functional modules / units in the system and the device can be implemented as software, firmware, hardware and appropriate combinations thereof.

[0098] The terms "first", "second", "third", "fourth" and the like used in the specification of the present application and the above-described drawings, if any, are used to distinguish similar objects, and do not necessarily have to be used to describe a specific order or sequence. It should be understood that the data thus used can be interchanged under appropriate circumstances, so that the embodiments of the present application described herein can be implemented in an order other than that illustrated or described herein. In addition, the terms "include" and "have" and any variations thereof are intended to cover non-exclusive inclusion, for example, a process, method, system, product or device including a series of steps or units does not have to be limited to only those steps or units clearly listed, but can include other steps or units not clearly listed or inherent to these processes, methods, products or devices.

[0099] It should be understood that, in the application, "at least one" refers to one or more, and "multiple" refers to two or more. "And / or" is used to describe the association relationship of the associated objects, which means that there can be three relationships, for example, "A and / or B" can represent three cases of only A, only B and A and B existing at the same time, wherein A and B can be singular or plural. The character " / " generally represents an "or" relationship between the associated objects before and after it. "At least one of the following" or similar expressions means any combination of these items, including any combination of single or multiple items. For example, at least one of a, b or c can represent a, b, c, "a and b", "a and c", "b and c", or "a and b and c", wherein a, b and c can be single or multiple.

[0100] In several embodiments provided in the application, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are only illustrative, for example, the division of units is only a logical function division, and actual implementation can have another division manner, for example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the coupling or direct coupling or communication connection between the displayed or discussed units can be indirect coupling or communication connection through some interfaces, devices or units, which can be electrical, mechanical or other forms.

[0101] The units described as separate components can or can not be physically separated, and the components displayed as units can or can not be physical units, that is, they can be located in one place, or they can be distributed on multiple network units. According to actual needs, part or all of the units can be selected to achieve the purpose of the embodiment scheme.

[0102] In addition, the functional units in each embodiment of the application can be integrated in one processing unit, or each unit can be physically present separately, or two or more units can be integrated in one unit. The integrated unit can be realized in the form of hardware or in the form of a software functional unit.

[0103] If the integrated unit is implemented in the form of a software function unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on such understanding, the technical solutions of the present application essentially or say the part that contributes to the prior art or the whole or part of the technical solutions can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes multiple instructions for causing an electronic device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the embodiments of the present application. The aforementioned storage medium includes: a U disk, a mobile hard disk, a read-only memory (Read-Only Memory, ROM), a random access memory (Random Access Memory, RAM), a magnetic disk or an optical disk, and various program storage media.

[0104] The above is a specific description of the preferred implementation of the embodiments of the present application, but the embodiments of the present application are not limited to the above-mentioned implementation. Those skilled in the art can make various equivalent modifications or replacements without departing from the spirit of the embodiments of the present application, and these equivalent modifications or replacements are all included in the scope defined by the claims of the embodiments of the present application.

[0105] The embodiments of the present application have been described in detail above in combination with the drawings, but the present application is not limited to the above-mentioned embodiments. Within the scope of knowledge possessed by those skilled in the art, various changes can be made without departing from the purpose of the present application.

Claims

1. A front-end business integration method, characterized in that, The method includes: Standardized configurations are generated based on the business scenario requirements of the front end. The business scenario requirements include interface adaptation requirements, communication integration requirements, and functional component requirements. The standardized configurations include interface-related settings, communication-related settings, and component mapping-related settings. The component mapping-related settings are used to associate various types of messages with their corresponding rendering components. Based on standardized configuration, construct the initial front-end business interaction scenario; In response to the multimodal dialogue messages generated by the front end, the multimodal dialogue messages are encapsulated into standardized data objects; Based on the aforementioned communication settings, the standardized data object is sent to the backend to receive the data stream fed back by the backend; Extract the valid content to be rendered from the data stream returned by the backend; Based on the interface-related settings and the component mapping-related settings, the valid content to be rendered is rendered to update the initial front-end business interaction scenario and obtain the target front-end business scenario.

2. The front-end business integration method according to claim 1, characterized in that, The process of constructing an initial front-end business interaction scenario based on standardized configuration includes: introducing a software development kit (SDK) into the front-end, and calling the initialization method of the SSD to pass the standardized configuration to the front-end to construct the initial front-end business interaction scenario.

3. The front-end business integration method according to claim 1, characterized in that, The communication-related settings include the backend's interface address, request header information, and authentication key. The step of sending the standardized data object to the backend based on these communication-related settings, and receiving the data stream from the backend, includes: Based on the backend's interface address, request header information, and authentication key, a real-time data stream connection is established with the backend; The standardized data object is sent to the backend via the real-time data stream connection to receive the data stream fed back by the backend.

4. The front-end business integration method according to claim 1, characterized in that, The multimodal dialogue message includes at least one of text information, image information, file information, and voice information. In response to the multimodal dialogue message generated by the front end, after encapsulating the multimodal dialogue message into a standardized data object, the method further includes: encapsulating the metadata corresponding to the multimodal dialogue message into the standardized data object, wherein the metadata includes a message creation timestamp and a sender identifier.

5. The front-end business integration method according to claim 1, characterized in that, After extracting the valid content to be rendered from the data stream fed back from the backend, the method further includes: adding a corresponding status message prompt in the status management center of the frontend based on the valid content to be rendered.

6. The front-end business integration method according to claim 1, characterized in that, The step of rendering the valid content to be rendered according to the interface-related settings and the component mapping-related settings includes: If the message type of the valid content to be rendered is plain text, the text bubble component is invoked to render the valid content to be rendered. If the message type of the valid content to be rendered is a structured data type, the corresponding structured data rendering component is called according to the component mapping settings to render the valid content to be rendered into an interactive interface element.

7. The front-end business integration method according to claim 6, characterized in that, The interactive interface elements include clickable menu buttons. When the message type of the valid content to be rendered is a structured data type, after calling the corresponding structured data rendering component according to the component mapping settings to render the valid content to be rendered into an interactive interface element, the method further includes: In response to the operation instructions of the interactive interface elements, extract the multimodal dialogue messages from the operation instructions; The multimodal dialogue messages in the operation instructions are encapsulated into updated standardized data objects; Based on the communication-related settings in the standardized configuration, the updated standardized data object is sent to the backend to receive the updated data stream fed back by the backend; Extract the updated, valid content to be rendered from the updated data stream returned by the backend; Based on the interface-related settings and the component mapping-related settings, the updated valid content to be rendered is rendered to update the initial front-end business interaction scenario and obtain the first front-end business scenario.

8. A front-end business integration system, characterized in that, The system includes: The generation module is used to generate standardized configurations based on the business scenario requirements of the front end. The business scenario requirements include interface adaptation requirements, communication integration requirements, and functional component requirements. The standardized configurations include interface-related settings, communication-related settings, and component mapping-related settings. The component mapping-related settings are used to associate various types of messages with corresponding rendering components. Build modules are used to construct initial front-end business interaction scenarios based on standardized configurations; The response module is used to respond to the multimodal dialogue messages generated by the front end and encapsulate the multimodal dialogue messages into standardized data objects. The sending module is used to send the standardized data object to the backend based on the communication-related settings, and to receive the data stream fed back by the backend; The extraction module is used to extract valid content to be rendered from the data stream fed back from the backend; The rendering module is used to render the valid content to be rendered according to the interface-related settings and the component mapping-related settings, so as to update the initial front-end business interaction scenario and obtain the target front-end business scenario.

9. An electronic device, characterized in that, It includes at least one control processor and a memory for communicatively connecting to the at least one control processor; the memory stores instructions executable by the at least one control processor, which, when executed by the at least one control processor, enable the at least one control processor to perform a front-end service integration method according to any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer-executable instructions for causing a computer to perform a front-end business integration method as described in any one of claims 1 to 7.

Images