Information processing method, apparatus, device, storage medium, and program product

Abstract

This application relates to an information processing method, apparatus, device, storage medium, and program product, belonging to the field of computer technology. It includes: displaying a dialogue page with a smart object in response to an interactive operation involving a target item related to a target object; displaying recommended product information generated by the smart object based on the product recommendation request in response to sending a product recommendation request on the dialogue page; and sending a product creation request for the target product information to the target object in response to determining target product information based on the recommended product information. The target product information is used by the target object to create the target product. This method significantly reduces the decision-making burden and time cost during offline consumption, improves overall consumer satisfaction, and enables merchants to simultaneously obtain users' product needs, thereby preparing products in advance and improving operational efficiency and user experience.

Description

Technical Field

[0001] This application relates to the field of computer technology, and in particular to an information processing method, apparatus, computer equipment, computer-readable storage medium, and computer program product. Background Technology

[0002] In recent years, with the accelerated integration of online and offline consumption scenarios, users generally face difficulties in making choices when consuming offline, especially when they need to consider the personalized preferences of their companions, making it even more difficult to make a satisfactory consumption decision quickly. For example, when ordering food in a physical store, users often find it difficult to make a quick choice when faced with a dazzling array of menus, while also needing to coordinate the different needs of their companions in terms of taste, dietary restrictions, and preferences, further increasing the complexity of ordering. Summary of the Invention

[0003] Therefore, it is necessary to provide an information processing method, apparatus, computer equipment, computer-readable storage medium, and computer program product to address the aforementioned technical problems, which can significantly reduce the decision-making burden and time cost during offline consumption and improve overall consumer satisfaction.

[0004] Firstly, this application provides an information processing method, including:

[0005] In response to interactive actions involving target items related to the target object, a dialogue page with the smart object is displayed;

[0006] In response to a product recommendation request sent on the dialog page, the smart object displays recommended product information generated based on the product recommendation request on the dialog page;

[0007] In response to determining the target product information based on the recommended product information, a product creation request for the target product information is sent to the target object; the target product information is used by the target object to create the target product.

[0008] Secondly, this application also provides an information processing method, including:

[0009] Displays the object details page for the target object, which includes an entry point for product creation;

[0010] In response to a triggered action on the product creation entry point, a dialog page with the smart object is displayed;

[0011] In response to a product recommendation request sent on the dialog page, the smart object displays recommended product information generated based on the product recommendation request on the dialog page;

[0012] In response to determining the target product information based on the recommended product information, a product creation request for the target product information is sent to the target object; the target product information is used by the target object to create the target product.

[0013] Thirdly, this application also provides an information processing apparatus, comprising:

[0014] The first display module is used to display a dialogue page with the smart object in response to interactive operations on target items related to the target object;

[0015] The first recommendation module is used to respond to a product recommendation request sent on the dialogue page and display recommended product information generated by the smart object based on the product recommendation request on the dialogue page;

[0016] The first processing module is used to respond to the determination of target product information based on recommended product information and send a product creation request for the target product information to the target object; the target product information is used by the target object to create the target product.

[0017] Fourthly, this application also provides an information processing apparatus, comprising:

[0018] The second display module is used to display the object details page of the target object, which includes a product creation entry point; in response to a trigger operation on the product creation entry point, a dialogue page with the smart object is displayed;

[0019] The second recommendation module is used to respond to a product recommendation request sent on the dialogue page and display recommended product information generated by the smart object based on the product recommendation request on the dialogue page.

[0020] The second processing module is used to respond to the determination of target product information based on recommended product information and send a product creation request for the target product information to the target object; the target product information is used by the target object to create the target product.

[0021] Fifthly, this application also provides a computer device, including a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to implement the steps of the method described in the first aspect above.

[0022] In a sixth aspect, this application also provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the steps of the method described in the first aspect above.

[0023] In a seventh aspect, this application also provides a computer program product, including a computer program that, when executed by a processor, implements the steps of the method described in the first aspect above.

[0024] The aforementioned information processing method, apparatus, computer equipment, computer-readable storage medium, and computer program product, in response to interactive operations on target items related to a target object, display a dialogue page with a smart object; in response to sending a product recommendation request on the dialogue page, display recommended product information generated by the smart object based on the product recommendation request on the dialogue page; in response to determining target product information based on the recommended product information, send a product creation request for the target product information to the target object; the target product information is used by the target object to create the target product. Through this method, by displaying a dialogue page in response to interactive operations on the target item and calling the smart object to generate recommended product information based on the product recommendation request, users can quickly obtain recommendations that match their own and their companions' preferences without having to compare numerous options one by one, significantly reducing the decision-making burden and time cost during offline consumption and improving overall consumer satisfaction. By sending a product creation request to the target object, merchants can simultaneously obtain users' product needs, thereby preparing products in advance and improving operational efficiency and user experience. Attached Figure Description

[0025] To more clearly illustrate the technical solutions in the embodiments of this application or related technologies, the drawings used in the description of the embodiments of this application or related technologies will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other related drawings can be obtained based on these drawings without creative effort.

[0026] Figure 1 This is an application environment diagram of an information processing method in one embodiment;

[0027] Figure 2 This is a flowchart illustrating an information processing method in one embodiment;

[0028] Figure 3 This is a flowchart illustrating the steps for displaying recommended product information in one embodiment;

[0029] Figure 4 This is a flowchart illustrating the information processing method in another embodiment;

[0030] Figure 5 This is a flowchart illustrating the customization of the menu in one embodiment;

[0031] Figure 6 This is a flowchart illustrating the process of modifying a menu in one embodiment;

[0032] Figure 7 This is a schematic diagram of the process of sharing to a friend to modify the menu in one embodiment;

[0033] Figure 8This is a flowchart illustrating the process of generating a menu based on friends' preferences in one embodiment.

[0034] Figure 9 This is a flowchart illustrating the order completion progress in one embodiment;

[0035] Figure 10 This is a flowchart illustrating the order completion progress in another embodiment;

[0036] Figure 11 This is a flowchart illustrating the process of modifying an order in one embodiment;

[0037] Figure 12 This is a flowchart illustrating the process of modifying an order in another embodiment;

[0038] Figure 13 This is a schematic diagram illustrating the interaction between a terminal and a server in one embodiment;

[0039] Figure 14 This is a structural block diagram of an information processing device in one embodiment;

[0040] Figure 15 This is a structural block diagram of the information processing device in another embodiment;

[0041] Figure 16 This is an internal structural diagram of a computer device in one embodiment. Detailed Implementation

[0042] To make the objectives, technical solutions, and advantages of this application clearer, the following detailed description is provided in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the scope of this application.

[0043] Before describing the embodiments of this application, it should be noted that the term "in response to" used in the embodiments of this application refers to a state in which a corresponding event occurs or a condition is met. It is understood that the timing of the subsequent action performed in response to the event or condition is not necessarily strongly correlated with the time when the event occurs or the condition is met. For example, in some cases, the subsequent action can be performed immediately when the event occurs or the condition is met; while in other cases, the subsequent action can be performed some time after the event occurs or the condition is met. A "trigger operation" refers to an operation performed on information (such as controls) provided by a computer device. Through this operation, corresponding instructions can be issued to the computer device, triggering the computer device to execute the next task. The next task triggered by different trigger operations for different information can all be pre-set in the program. This trigger operation can be manually executed by the user, such as clicking, double-clicking, long-pressing, or swiping operations performed by the user on the content displayed on the screen of the computer device. In some cases, the trigger operation can also be executed by the computer device based on a set program.

[0044] In this application, "control" refers to any element in a computer user interface that a user can directly interact with. These elements allow users to input data, select options, or trigger certain actions. Controls can be graphical (such as buttons, text boxes, checkboxes, etc.) or more abstract (such as voice commands). Buttons are typically used to perform an operation or open a new interface. Text boxes allow users to input or edit text information. Checkboxes represent a Boolean value (yes / no), which users can select or deselect. Drop-down lists provide a list of options for users to choose from, typically displaying only one selected value. List boxes display multiple options, allowing users to select one or more items. Labels display static text, typically used to explain the function of other controls, and can also be used as buttons. Scrollbars allow users to navigate large datasets, such as browsing long documents or lists. Images display static pictures and can sometimes be used as buttons. Combo boxes combine the functionality of text boxes and drop-down lists, allowing users to both input text and select from a list.

[0045] In this application, "goods" refers to objects that users can acquire, purchase, or use. These include both tangible products and intangible services. Services are non-physical items provided by service providers (such as merchants, institutions, or individuals) to users to meet their diverse needs in specific scenarios. Services can cover various categories such as catering services (e.g., dine-in, takeout), leisure and entertainment services (e.g., KTV, movie watching, fitness), lifestyle services (e.g., housekeeping, beauty salons), and travel services (e.g., taxis, car rentals). Tangible products include, but are not limited to, various physical items such as food, beverages, daily necessities, electronic products, clothing, and gifts. Goods typically have clearly defined specifications, prices, inventory, and display information, and can be displayed and traded through online or offline channels. In offline consumption scenarios, goods may be presented in the form of displays, trials, or immediate purchase; users can complete personalized recommendations and place orders for goods based on relevant target items. Tangible products can be sold individually or combined with services to meet the overall needs of users in specific consumption scenarios.

[0046] The "intelligent object" involved in this application refers to a programmatic entity with data processing, logical reasoning, and content generation capabilities, used to output recommended product information or decision support based on user input demand information. Intelligent objects can manifest as algorithmic models (such as recommendation models or large language models), intelligent agents (such as AI assistants), rule engines, or combinations thereof, capable of analyzing multidimensional preferences of users and peers to generate personalized recommendation results. Intelligent objects can be either cloud-based artificial intelligence services or lightweight models running on terminal devices, supporting data interaction with applications to provide users with accurate and interpretable recommendation content to assist in making consumption decisions.

[0047] It should be noted that the terms "first," "second," etc., used in this application can be used to describe various elements, but these elements are not limited by these terms. These terms are only used to distinguish the first element from the second element. The terms "comprising" and "having," and any variations thereof, used in this application, are intended to cover non-exclusive inclusion. The term "multiple" used in this application refers to two or more. The term "and / or" used in this application refers to one of the embodiments, or any combination of multiple embodiments.

[0048] Understandably, in recent years, with the accelerated integration of online and offline consumption scenarios, users generally face difficulties in making choices when consuming offline, especially when they need to consider the personalized preferences of their companions, making it even more difficult to make a satisfactory consumption decision quickly. For example, when ordering food in a physical store, users often find it difficult to make a quick choice when faced with a dazzling array of menus, while also needing to coordinate the different needs of their companions in terms of taste, dietary restrictions, and preferences, further increasing the complexity of ordering food.

[0049] Therefore, for offline interaction scenarios, there is an urgent need to build a lightweight product that supports personalized recommendations for users, so as to reduce the decision-making cost for users when making offline purchases, while helping merchants to perceive user preferences in advance, achieve precise services and advance preparation, and thus be applicable to various offline consumption scenarios.

[0050] Based on this, embodiments of the present invention propose an information processing method, apparatus, computer device, computer-readable storage medium, and computer program product. In response to an interactive operation involving a target item related to a target object, a dialogue page with a smart object is displayed; in response to sending a product recommendation request on the dialogue page, recommended product information generated by the smart object based on the product recommendation request is displayed on the dialogue page; in response to determining target product information based on the recommended product information, a product creation request for the target product information is sent to the target object; the target product information is used for the target object to create the target product. Through the above method, by displaying a dialogue page in response to an interactive operation involving a target item, and calling a smart object to generate recommended product information based on a product recommendation request, users can quickly obtain recommendations that match their own and their companions' preferences without having to compare numerous options one by one, significantly reducing the decision-making burden and time cost during offline consumption and improving overall consumer satisfaction. By sending a product creation request to the target object, merchants can simultaneously obtain users' product needs, thereby preparing products in advance and improving operational efficiency and user experience.

[0051] The information processing method provided in this application embodiment can be applied to, for example... Figure 1 In the application environment shown, terminal 102 can be categorized as a user terminal or a merchant terminal based on user type. Terminal 102 communicates with server 104 via a network. A data storage system can store the data that server 104 needs to process. The data storage system can be integrated onto server 104 or placed on a cloud or other network server. Optionally, terminal 102 has an application installed. This application can be, but is not limited to, a social media platform client, a lifestyle service application, a payment application, a mini-program application, etc. The information processing method provided in this embodiment can be implemented through this application.

[0052] Specifically, terminal 102, in response to interactive operations related to target items, displays a dialogue page with the smart object; in response to sending a product recommendation request on the dialogue page, displays recommended product information generated by the smart object based on the product recommendation request; in response to determining target product information based on the recommended product information, sends a product creation request for the target product information to the target object; the target product information is used by the target object to create the target product. Server 104 receives the product creation request sent by terminal 102, sends the product creation request to the merchant, and completes the corresponding product creation process.

[0053] Terminal 102 can be, but is not limited to, various personal computers, laptops, smartphones, tablets, drones, low-altitude aircraft, IoT devices, and portable wearable devices. IoT devices can include smart speakers, smart TVs, smart air conditioners, smart in-vehicle devices, and projection equipment. Portable wearable devices can include smartwatches, smart bracelets, and head-mounted displays. Head-mounted displays can be virtual reality (VR) devices, augmented reality (AR) devices, and smart glasses. Server 104 can be a standalone physical server, a server cluster or distributed system composed of multiple physical servers, or a cloud server providing cloud computing services.

[0054] A method according to an embodiment of the present invention, such as Figure 2 As shown, an information processing method is provided, which is applied to... Figure 1 Taking terminal 102 as an example, the explanation includes:

[0055] Step 202: In response to an interaction with a target item related to the target object, display a dialogue page with the smart object.

[0056] The terminal has an application (such as a lifestyle service application or a social media platform client) installed on it, and the information processing method provided in this embodiment can be implemented through this application. It is understood that a server-side application corresponding to this application is deployed on the server. This server-side application provides services to multiple user accounts and merchant accounts, allowing users to complete operations such as information acquisition, personalized recommendations, order placement and payment, while also providing merchants with functions such as order management and service pre-service preparation. In this embodiment, a first account is logged into the client, and the terminal communicates with the server based on this first account. The server can distinguish different users according to their accounts and record their preference information and order data.

[0057] The target entity refers to the provider of the goods, which can be a merchant operating in the form of a physical store or online shop, or an individual service provider with a professional account (such as a personal verified account, creator account, or service provider account). The target item refers to the physical or digital medium used to trigger information interaction, i.e., the information carrier, which can be a Near Field Communication (NFC) tag, a Radio Frequency Identification (RFID) tag, a QR code, a barcode, a Bluetooth beacon, or other media with unique identification capabilities. The target item stores identification information associated with the merchant providing the goods (such as merchant ID, store ID, device ID, etc.). When a terminal approaches or scans the target item, the application can read the identification information and request the corresponding service configuration data from the server. For example, the target item is an NFC sticker attached to a dining table. When a user brings an NFC-enabled terminal close to the sticker, the terminal can read the merchant identification written in the sticker.

[0058] Optionally, the target item refers to a physical or digital medium placed at the product provision location (such as a store counter, cashier, shelf, entrance, etc.) and used to trigger information interaction. The product provision location refers to a physical space or area within a physical business premises where users can obtain services or purchase goods. It can be understood that the product provision location can be the place where a merchant's business activities take place, where users can actually touch, experience, or consume related goods. Product provision locations include, but are not limited to, dining areas in restaurants, display and sales areas in retail stores, service areas in leisure and entertainment venues, reception areas in lifestyle service venues, and public areas in hotels. Optionally, the product provision location can also be a temporary, mobile service location, such as a market stall, pop-up store, or exhibition booth.

[0059] Understandably, the target object, as the source of the goods, has its relevant information (such as name, location, service scope, reviews, etc.) associated with a target item (such as an NFC tag, QR code, or other information carrier) located at the goods' place of origin. When a user interacts with the target item, the application can identify the target object associated with that item and establish a dialogue page with the corresponding smart object. For example, the target object could be a restaurant; after the user touches the NFC tag on the table, the smart object in the dialogue page interacts with the user as the restaurant's assistant. For example, the target object could be a professional photographer; after the user scans the studio's QR code, the smart object in the dialogue page interacts with the user as the photographer's appointment assistant, used to collect shooting needs and recommend service plans.

[0060] Interactive operations targeting a target item refer to the operational instructions executed by a user through a terminal on the target item to establish communication or trigger business processes. Users can perform interactive operations targeting a target item on the terminal in the following ways: For NFC or RFID tags, the user brings the terminal close to or lightly touches the target item, and the terminal's near-field communication module reads the tag data; for QR codes or barcodes, the user scans the target item using the application's built-in scanning function; for Bluetooth beacons, the terminal automatically detects and triggers interaction when entering the beacon's signal coverage area. Interactive operations can be performed manually by the user, such as actively bringing the phone close to an NFC tag or actively scanning a QR code; in some cases, interactive operations can also be automatically executed by the terminal based on location awareness or signal detection, such as automatically triggering when the terminal detects entering the range of a preset Bluetooth beacon.

[0061] The dialogue page refers to the interface that presents the interaction between the user and the intelligent object in the form of a message stream. For example, the dialogue page may include the following elements: message bubbles sent by the user (displaying the user's input in natural language), message bubbles replying to the intelligent object (displaying the dialogue content, questions, recommendations, etc. generated by the intelligent object), input boxes (for users to input natural language text), voice input controls (supporting voice-to-text input), and quick reply options (common answer options displayed as buttons for quick selection by the user). On this dialogue page, users can express their needs, preferences, questions, or suggestions for modification to the intelligent object through text input, voice input, or by clicking quick reply options; the intelligent object, based on its understanding of the user's input, generates corresponding replies, follow-up questions, confirmations, or product recommendations, which are then displayed on the dialogue page in the form of message bubbles.

[0062] For example, in an offline store ordering scenario, after a user triggers the target item by tapping it with NFC, the terminal displays a dialogue page. On this page, the smart object sends a welcome message; the user can enter natural language content in the input box; the terminal sends the user's input dialogue information to the smart object on the server; the smart object uses natural language understanding technology to analyze the dialogue information, extracting details such as the number of diners, dietary restrictions, budget, and consumption scenario; the smart object can further pursue missing information or clarify ambiguous expressions through multiple rounds of dialogue; the smart object continues to extract supplementary demand information. Through these multiple rounds of dialogue, the smart object obtains complete demand information, which is then used to generate recommended product information.

[0063] In one optional implementation, the dialogue page can support voice input to obtain dialogue information. The terminal provides a voice input control; after the user clicks it, they record their voice through the microphone. The terminal then transcribes the voice into text and sends it as dialogue information to the smart object. Voice input is suitable for scenarios where users' hands are inconvenient to operate or who are more accustomed to voice expression, further enhancing the naturalness and convenience of the interaction.

[0064] In one optional implementation, quick reply options can be preset in the dialogue page to guide users to quickly provide key information. These quick reply options can be displayed as buttons above the input box or in the dialogue message stream. When a user clicks a quick reply option, the system automatically sends the corresponding text content as dialogue information. The quick reply options can dynamically change according to the current stage of the dialogue. For example, in the initial stage, options for the number of diners such as "1 person," "2-4 people," "5-6 people," and "6 or more people" can be displayed; in the taste preference stage, options such as "less spicy," "mildly spicy," and "medium spicy" can be displayed. Quick reply options reduce the user's input burden while guiding them to provide more structured information.

[0065] In one alternative implementation, the smart object can proactively display preview data of recommended product information to the user during the conversation. For example, after the user expresses some of their needs, the smart object can output preliminary recommendations for the user's reference, while continuing to inquire about other dimensions of preference. The user can then provide feedback or make adjustments based on the preliminary recommendations. This combination of progressive recommendations and dialogue helps users clarify their needs more quickly and shortens the number of conversation rounds.

[0066] In one optional implementation, the responses from smart objects on the dialogue page can include rich media elements, such as images, videos, and links, to enhance information delivery. For example, in a physical store ordering scenario, smart objects can include images of dishes when recommending them; in a retail scenario, smart objects can include product cards when recommending goods. Through rich media elements, users can more intuitively understand the recommended content, aiding their decision-making.

[0067] For example, a client logged into with the first account continuously monitors interaction events such as near-field communication, camera scanning, or Bluetooth signals. When an interaction with a target item is detected, the client reads the merchant identification information from the target item, requests page data (such as page configuration information, a list of desired information options, etc.) from the server, and renders and displays the dialogue page based on the page data returned by the server. This dialogue page provides an entry point for subsequent user input of desired information and triggering personalized recommendations.

[0068] For example, after responding to an interactive operation targeting a specific item, a client logged into the first account requests dialogue page data from the server. The server returns initial data for the dialogue page (such as opening remarks and initial quick reply options) based on the merchant type and configuration strategy corresponding to the target item. The client renders the dialogue page, displaying the smart object's opening message and input area. The user enters dialogue information on the dialogue page (text input, voice input, or clicking quick reply options), and the client sends the dialogue information to the smart object on the server. The smart object performs natural language understanding on the dialogue information, extracts structured demand information, and generates response content (including follow-up questions, confirmations, and recommended previews) based on the current dialogue state. The server returns the response content generated by the smart object to the client, and the client displays the smart object's response message on the dialogue page. This process can be repeated until the smart object confirms that it has obtained sufficiently complete demand information and can proceed to the recommendation generation stage. Once the demand information collection is complete, the server can associate and store the extracted structured demand information with the first account and use it in subsequent steps for the smart object to generate recommended product information.

[0069] Step 204: In response to sending a product recommendation request on the dialog page, display recommended product information generated by the smart object based on the product recommendation request on the dialog page.

[0070] The product recommendation request refers to a natural language or structured instruction issued by a user on the dialogue page to request a smart object to recommend products. Optionally, the product recommendation request includes demand information, which refers to parameter data input or selected by the user through the dialogue page during the consumption decision-making process, describing their own and their companions' personalized preferences, needs, or constraints. It can be understood that demand information serves as the input basis for the smart object's recommendation calculation, describing the user's personalized needs in a specific consumption scenario. Taking the offline store ordering scenario as an example, demand information may include, but is not limited to, the following dimensions: taste preferences (such as spiciness level, sweetness / sourness, and contraindicated ingredients), dining scenario (such as the number of diners and budget range), and attribute preferences (such as value-for-money experience and luxury experience). Demand information can be collected through different types of controls on the dialogue page, such as: inputting contraindications or special requirements through text boxes; selecting preference tags through checkboxes; selecting the number of diners or budget range through drop-down lists or sliders; and selecting the consumption scenario type through radio buttons. Optionally, demand information can also be pre-filled or intelligently recommended based on the first account's historical behavior data, historical order information, or preset user profiles to reduce the workload of manual input by the user. For example, demand information includes dialogue information, which refers to the content expressed by the user in natural language on the dialogue page. This can be text input, voice input, or structured input generated by clicking quick reply options. Dialogue information can cover various demands expressed by the user during the consumption decision-making process, such as taste preferences, number of diners, consumption scenario, product attribute preferences, and service expectations. Dialogue information can be a sentence, a description, or contextual information accumulated over multiple rounds of dialogue.

[0071] For example, in response to interactive actions on a dialog page, request information is obtained. Users can perform interactive actions on the dialog page on the terminal in the following ways: for text boxes, users enter text information via keyboard or voice input; for checkboxes or radio buttons, users select or deselect via touch; for drop-down lists, users expand the list and select from options by clicking; for sliders, users adjust values ​​by dragging the slider; for date pickers, users select dates by scrolling or clicking. Interactive actions can be performed manually by the user, such as clicking the confirmation button to submit the entered information; in some cases, interactive actions can also be automatically executed by the terminal based on preset logic, such as automatically filling in some request information based on historical behavior data or historical order information before submission.

[0072] Understandably, the methods for collecting demand information can be flexibly configured according to different consumption scenarios. The following explanation will be provided in conjunction with various application scenarios.

[0073] For example, in an offline store ordering scenario, the dialog page may include the following controls: a text box for entering dietary restrictions or special requirements; a checkbox for selecting preference tags; a drop-down list for selecting the number of diners or spiciness level; and a slider for selecting a budget range. After the user interacts with the above controls, the terminal obtains the user's input information such as taste preferences, dining scenario, and attribute preferences, which serves as the basis for subsequent recommendation calculations.

[0074] For example, in a retail scenario, the dialog page may include the following controls: a drop-down list for selecting product categories; checkboxes for selecting feature preferences; radio buttons for selecting sizes or specifications; and text boxes for entering color preferences or special needs. After the user interacts with the above controls, the terminal obtains the user's needs information regarding product attributes, functional requirements, specifications, and dimensions, so that the intelligent object can recommend products that meet the user's personalized needs.

[0075] For example, in a leisure and entertainment scenario, the dialogue page may include the following controls: a drop-down list for selecting a session or time slot; radio buttons for selecting the number of attendees or ticket type; checkboxes for selecting additional services; and text boxes for entering special requests. After the user interacts with the above controls, the terminal obtains information about the user's needs regarding entertainment options, time slot preferences, and additional services, so that the intelligent object can recommend suitable entertainment options and related services.

[0076] Understandably, the client with the primary account continuously monitors user interaction events on the chat page. When it detects a user interacting with controls on the chat page, the client collects the user's input or selection information in real time. Optionally, after the user completes all required information, the client, in response to the user's confirmation button on the chat page, encapsulates the collected information into a product recommendation request and sends it to the server. Optionally, the client can also upload incremental information to the server in real time after the user interacts with a single control, allowing the server to dynamically update the user's request status.

[0077] During the process of obtaining demand information, the client or server can also perform information verification and supplementation. Optionally, before sending the demand information to the server, the client can perform non-empty validation on the required fields. If any required fields are missing, the client can prompt the user to supplement the relevant information. Optionally, after receiving the demand information, the server can intelligently complete or correct the demand information based on the historical behavior data or historical order information of the first account. For example, if the user has not filled in any dietary restrictions, the server can automatically add "less spicy" as the default dietary restriction preference based on the records of the user selecting "less spicy" multiple times in historical orders. Optionally, the server can also verify the validity of the demand information based on the merchant information corresponding to the target item. For example, if the number of diners included in the user's input demand information exceeds the maximum capacity of the merchant's private room, the server can return a prompt to the client, informing the user that the currently selected number of diners exceeds the capacity of the private room.

[0078] Recommended product information refers to the content output by the intelligent object after analyzing and processing demand information, used to assist users in making consumption decisions. Recommended product information may include combinations of one or more products, and each type of recommended product information may include specific product name, specifications, quantity, price, reasons for recommendation, and matching degree descriptions. The presentation format of recommended product information can be diverse, such as a menu combination list, set meal options, product list, and service options. The intelligent object can generate at least one type of recommended product information based on demand information, allowing users to select the target product information that best matches their own and their companions' preferences.

[0079] For example, as a programmatic entity with data processing, logical reasoning, and content generation capabilities, the deployment location of a smart object can be flexibly selected based on the actual application scenario, computing resources, response latency requirements, and data privacy protection needs. Smart objects can be located locally on the terminal, or on a server, or in the cloud that communicates with the server.

[0080] It is understandable that the process of generating recommended product information in this step involves combining the user's input needs with the capabilities of the intelligent object to achieve an efficient transformation from user needs to recommended results. The intelligent object can generate recommended product information based on various algorithmic strategies, including but not limited to content-based recommendation algorithms, deep learning models, large language model inference, and rule matching engines. The following examples illustrate the process of inputting needs information into the intelligent object and outputting recommended product information, using various application scenarios as examples.

[0081] For example, in an offline store ordering scenario, the terminal encapsulates the acquired demand information (such as 2-4 people dining, budget range 200-500, no dietary restrictions, and value for money) into a product recommendation request and sends it to the server. The server inputs this demand information into a cloud-based intelligent object (such as a restaurant recommendation model). The intelligent object performs comprehensive matching calculations based on the merchant's menu database, combined with taste preferences, dining scenarios, and attribute preferences from the demand information. For example, the intelligent object filters suitable dish portions or set meal types based on the number of diners; filters dishes based on dietary restrictions; weights and sorts the remaining dishes based on preference information; and prioritizes recommending dish combinations suitable for multiple people to share and with broad flavor appeal based on the consumption scenario. The intelligent object outputs at least one recommended product. The server returns the generated recommended product information to the terminal, which displays it on the dialog page for the user to browse and select. For example, refer to... Figure 3 The terminal displays menu cards on the dialog page, showing two lists of dish combinations (i.e., recommended product information). Each menu card also displays the reason for recommending each dish combination, an "Edit Menu" button, and a "Send Menu" button. The "Edit Menu" button allows users to manually edit the dish combination list, while the "Send Menu" button allows users to confirm their selection.

[0082] For example, in a retail scenario, the terminal encapsulates the acquired demand information into a product recommendation request and sends it to the server. The server inputs this demand information into a smart object (such as a product recommendation model). The smart object matches the product based on a product database, combining the category, price range, functional preferences, and usage scenarios from the demand information. For example, the smart object filters wearable devices such as headphones and smartwatches based on the category (electronic products); filters out products that exceed the budget based on the price range; scores the matching degree of the remaining products based on functional preferences (noise cancellation); and prioritizes recommending products with good portability and long battery life based on the usage scenario (commuting). The smart object outputs at least one recommended product, such as: Recommended product information 1: a brand of active noise-canceling true wireless headphones, recommended because "it has noise cancellation, 30 hours of battery life, and is suitable for commuting"; Recommended product information 2: a brand of over-ear noise-canceling headphones, recommended because "it is comfortable to wear, has excellent noise cancellation, and supports fast charging". The server returns the recommended product information to the terminal, where the user can view product details, compare parameters, and select their preferred product to place an order on the dialogue page.

[0083] For example, in a leisure and entertainment scenario, the terminal encapsulates the acquired demand information into a product recommendation request and sends it to the server. The server inputs this demand information into a smart object. The smart object matches the demand information based on the venue database and session schedule, combined with the number of people, time slot, activity type, theme preference, and service requirements. The smart object outputs at least one recommended product. The server returns the recommended product information to the terminal, where users can view details of each theme, remaining sessions, and user reviews on the chat page, and select suitable target products for booking.

[0084] In one alternative implementation, the smart object can incorporate a multi-turn interaction mechanism when generating recommended product information. For example, the initial recommended product information generated by the smart object may include multiple options. The terminal displays at least one recommended product by showing a recommendation card on a dialog page. The user can provide feedback on the recommended product information on this dialog page (e.g., not interested, too expensive, request a different selection). The terminal sends this feedback to the smart object, which then optimizes the recommendation based on the feedback and outputs the adjusted recommended product information. Through multi-turn interactions, the smart object can more accurately capture user preferences and improve recommendation satisfaction.

[0085] In one alternative implementation, the intelligent object can dynamically adjust its product recommendations based on real-time data. For example, in a physical store ordering scenario, the intelligent object can query the real-time preparation status of the restaurant's kitchen and prioritize recommending dishes with sufficient inventory and fast preparation speed. In a retail scenario, the intelligent object can query the real-time inventory of goods to avoid recommending out-of-stock items. In a leisure and entertainment scenario, the intelligent object can query the real-time reservation status of the venue and only recommend currently available bookings. By incorporating real-time data, the product recommendations output by the intelligent object have higher executability and timeliness.

[0086] In one alternative implementation, the intelligent object can incorporate a collaborative processing mechanism based on peer preferences when generating recommended product information. For example, if the demand information includes the preferences of peer A and peer B, the intelligent object can prioritize recommending dishes that satisfy multiple preferences when filtering and sorting dishes, generating multiple sets of alternatives for the user to choose from. The server can then present the specific details of each alternative to the user as a recommendation reason (e.g., "This option includes fish dishes, satisfying peer B's preference for fish, and it is not spicy, meeting peer A's dietary restrictions").

[0087] In one optional implementation, after receiving the request information, the server preprocesses the information and inputs the preprocessed data into the smart object. Preprocessing may include the following operations: semantically parsing the text-based request information input by the user to extract structured tags; normalizing the numerical request information selected by the user; and integrating the user's historical behavior data or historical order information with the current request information to complete any preference dimensions not explicitly filled in by the user. Through preprocessing, the smart object can obtain more organized and richer input data, thereby generating more accurate recommended product information.

[0088] Understandably, after obtaining the user's needs, the client with the initial account encapsulates these needs into a product recommendation request and sends it to the server. The server then inputs the needs into a smart object, which performs reasoning and calculations, outputting at least one recommended product. The server returns the recommended product information to the client, which displays it on a dialog page for the user to browse, compare, and select their final target product. This process efficiently transforms personalized user needs into intelligent recommendation results, providing users with consumption decision-making references tailored to their own and their companions' preferences, significantly reducing decision-making costs in offline consumption scenarios.

[0089] Step 206: In response to determining the target product information based on the recommended product information, a product creation request for the target product information is sent to the target object; the target product information is used by the target object to create the target product.

[0090] The target product information refers to the specific recommendation scheme that the user selects from at least one set of recommended product information and ultimately decides to create or customize. The target product information is determined by performing a confirmation operation on the target product information within the recommended product information. The confirmation operation refers to the user's instruction on the target product information executed through the terminal to express acceptance and trigger the product creation process. Users can perform confirmation operations on the target product information on the terminal in the following ways: for recommended product information displayed in a list or card format, the user triggers confirmation by touching the target product information area; for recommended product information items containing a confirmation control, the user clicks the control to confirm; for scenarios supporting voice interaction, the user confirms via voice command (such as selecting the first option).

[0091] A product creation request is an instruction sent by the terminal to the server (or directly to the target object) after the user has selected target product information. This instruction instructs the target object to create an order for an actual product or service based on the target product information. The product creation request may include data such as the target product identifier, user account information, customized parameters (e.g., quantity, specifications, special requirements), and the target object identifier. Product creation requests are suitable for scenarios involving customized products or services, where the target object needs to perform further configuration, production, or preparation based on the user's selection. For example, the terminal sends a product creation request to the server, the server generates an order record based on the request, and notifies the target object to create the target product.

[0092] A target product refers to a product instance created or generated for a user based on a product creation request and the target product information specified by the user. A target product can be a physical product (such as a product customized according to the user's selected specifications), a service order (such as a reservation record generated based on the user's selected service plan), or digital content (such as a song list configured based on the user's selected playlist). The creation process of a target product can be completed automatically by the target object's server or generated manually by the merchant's personnel.

[0093] In practice, the confirmation operation and the process of sending the product creation request can be flexibly configured according to different consumption scenarios. The following examples illustrate the process of responding to the confirmation operation and sending the product creation request in combination with various application scenarios.

[0094] For example, refer to Figure 3 In offline store ordering scenarios, the terminal receives at least one recommended product information (such as dish combination A and dish combination B) returned by a smart object and displays it in the form of a card list on the dialog page. The recommended card includes details of the dish combination, total price, reason for recommendation, and a confirmation button. After browsing the various recommendations, the user selects a dish combination that matches their own and their companion's preferences and clicks the confirmation button on the recommended card. In response to this confirmation, the terminal sends a product creation request to the target object (merchant). The product creation request includes the identifier of the target product information, user account information, and the merchant information associated with the target item. The merchant or server (with confirmation from the merchant) performs the following operations: queries the corresponding dish details and price based on the identifier of the target product information; verifies the inventory status of the selected dish; if the inventory is sufficient, generates a specific order record and sets the product status to "ordered." The merchant is notified to create the target product, and the merchant prepares the meal and serves it accordingly. If the user's selected dish is sold out or in short supply, the server returns an insufficient inventory warning to the terminal and suggests that the user choose another recommended option or contact the merchant for a replacement.

[0095] For example, in a retail scenario, the terminal displays at least one recommended product information generated by a smart object, including a product image, name, price, recommendation reason, and a confirmation button. The user confirms the target product information by clicking the confirmation button. In response to this confirmation, the terminal sends a product creation request to the merchant. Upon receiving the request, the merchant or server verifies the product's real-time inventory; if the verification passes, an order record is generated, and the product status is set to "ordered." The merchant is then notified to create the target product, and the merchant prepares the product based on its description.

[0096] For example, in a leisure and entertainment scenario (such as a KTV), the terminal displays at least one recommended product information (such as a personalized playlist) generated by a smart object, including a song list, recommendation reasons, and a confirmation button. The user confirms the target product information (such as a playlist of classic hits) by clicking the confirmation button. In response to this confirmation, the terminal sends a playlist configuration request to the merchant. Upon receiving the request, the merchant or server verifies the room number or room status associated with the current user; if the verification passes, a playlist configuration instruction is generated, the playlist is pushed to the corresponding room's song selection system queue, and the playlist is automatically configured according to the playback order set by the user. The server returns a successful configuration status and confirmation that the playlist has been added to the terminal, and the user can view the current playlist in real time through the room's song selection screen or the terminal page.

[0097] In one alternative implementation, the client or server can perform a secondary confirmation or information supplementation process before or after the user's confirmation operation. For example, in a physical store ordering scenario, after the user clicks the confirmation button for the target product information, a secondary confirmation pop-up appears on the terminal, displaying the menu details and total price, asking the user whether to confirm the order, and providing both confirm and cancel options. Only after the user confirms again can the product creation request be generated. This secondary confirmation or information supplementation process avoids user errors and ensures the completeness and accuracy of the target product information.

[0098] In one optional implementation, the confirmation operation can support batch selection or merging of multiple product information. For example, in a retail scenario, a user can simultaneously select multiple recommended products on a dialog page (e.g., purchase headphones and a protective case at the same time), click the batch order or merge checkout button, and the terminal will merge the multiple target product information into a single product order, initiating a product creation request to the server. For example, in an offline store ordering scenario, a user can select recommended main dishes while simultaneously choosing drinks or snacks from the additional recommendations area, merging them and confirming the order all at once.

[0099] In one optional implementation, after the target product is created, the client or server can execute subsequent interactive processes. For example, in an offline store ordering scenario, after a user completes their order and payment, the terminal displays a product details interface, showing the product status, estimated preparation time, and pickup method (e.g., dine-in, self-pickup), as well as a pickup code or order number. For example, in a retail scenario, after a user completes their order, the terminal displays a product progress interface, allowing the user to view the real-time progress of the target product. For example, in a leisure and entertainment scenario, after a user completes a reservation, the terminal displays an electronic ticket.

[0100] In one optional implementation, after the target product is created, the server can associate and store the target product information and the user's preference data expressed in the demand information with the primary account. The server can then store the order details in the primary account's historical order database and update the user's preference tags in the primary account's user profile, providing a more accurate data foundation for subsequent personalized recommendations.

[0101] Understandably, after displaying at least one recommended product, the client with the initial account continuously monitors user interaction events on the chat page. When it detects a user confirming a request for a specific product, the client encapsulates the relevant data of the target product, along with the user's account information and merchant information, into a product creation request and sends it to the target object or server. The target object or server responds to the product creation request, generates the target product based on the target product information, and returns the processing result to the client for display.

[0102] In the above information processing method, in response to interactive operations on target items related to the target object, a dialogue page with the smart object is displayed; in response to sending a product recommendation request on the dialogue page, recommended product information generated by the smart object based on the product recommendation request is displayed on the dialogue page; in response to determining target product information based on the recommended product information, a product creation request for the target product information is sent to the target object; the target product information is used by the target object to create the target product. Through this method, by displaying a dialogue page in response to interactive operations on the target item and calling the smart object to generate recommended product information based on the product recommendation request, users can quickly obtain recommendations that match their own and their companions' preferences without having to compare numerous options one by one, significantly reducing the decision-making burden and time cost during offline consumption and improving overall consumer satisfaction. By sending a product creation request to the target object, merchants can simultaneously obtain users' product needs, thereby preparing products in advance and improving operational efficiency and user experience.

[0103] A method according to an embodiment of the present invention, such as Figure 4 As shown, an information processing method is provided, which is applied to... Figure 1 Taking terminal 102 as an example, the explanation includes:

[0104] Step 402: Display the object details page of the target object, which includes the product creation entry point.

[0105] The object details page refers to the user interface used to display the core information of the target object. It may include the following: merchant name, store location, business hours, product thumbnails or video descriptions, popular recommendations or signature products, promotional information, service ratings, and user review summaries. The object details page is designed to give users an initial understanding of the merchant or product before they enter the recommendation process, allowing them to decide whether to continue to the customization stage based on their needs. The object details page may contain one or more interactive controls, such as entry points for creating a product, viewing the full menu, contacting the merchant, and viewing reviews.

[0106] A product creation entry point refers to an interactive control located on the product details page that guides users through the personalized recommendation process. This entry point can be represented as a button, icon, link, card area, or other triggerable UI element. The text accompanying the entry point can be customized based on the scenario, such as "Customize the menu according to my preferences" or "Personalized ordering."

[0107] In one optional implementation, in response to a triggering action on the details entry of a target object in the feed page, the object details page of the target object is displayed. A feed page refers to a user interface in an application that aggregates and displays multiple objects or content items in a list, card, or waterfall layout, such as a search page (a list of search results displayed after the user enters keywords) or a browsing page (such as a homepage recommendation stream, category browsing page, etc.). Each target object in the feed page corresponds to a details entry, which can be represented as the target object's avatar, name, brief description card, image area, or a "view details" button, etc.

[0108] For example, after a user performs a search or browsing operation, the terminal displays an information feed page containing details entry points for multiple objects. The user initiates a viewing request for a target object by clicking on its details entry point via touch. In response to this touch operation, the terminal sends a request to the server to retrieve the object details page, carrying the target object's identifier. The server queries its database based on the target object identifier, retrieves the target object's detailed information, and generates the page data for the object details page. The server returns the page data to the terminal, which then renders and displays the target object's details page based on the received data. This method is suitable for scenarios where users actively search or browse to discover new target objects, serving as an entry point for obtaining information about merchants or service providers online. For example, a user enters target keywords in the application's search box, and the terminal displays a search results information feed page listing cards for several restaurants matching the target keywords. Clicking on a restaurant's card redirects the user to that restaurant's details page.

[0109] In one alternative implementation, in response to an interaction with a target item related to the target object, the object details page of the target object is displayed. This implementation is explained in the preceding explanation of step 202 and will not be repeated here. For example, after a user enters a restaurant and is seated, they can bring their phone close to an NFC tag attached to the table. The terminal automatically reads the restaurant identifier from the tag and redirects to the restaurant's object details page. The user can quickly order food without opening an application to search for the restaurant name.

[0110] Step 404: In response to the triggered operation for the product creation entry, display the dialog page with the smart object.

[0111] Among them, the triggering operation of the product creation entry refers to the interactive command executed by the user on the control. The user can click on the product creation entry area through touch operation to trigger the process of jumping from the object details page to the dialog page.

[0112] For example, refer to Figure 5 In an offline store ordering scenario, users bring their NFC-enabled phones close to an NFC sticker affixed to the tabletop. The device reads the merchant's identification information from the sticker and requests the object details page data from the server. The server returns the object details page data for that store, which is then displayed on the device. This object details page includes the store name, signature dishes, user review summaries, and a product creation entry point (such as...). Figure 5 (See the "Customize Menu According to My Preferences" button). After a user clicks the product creation entry, the terminal requests the dialog page data from the server. The server returns the dialog page configuration information corresponding to that store, and the terminal renders and displays the dialog page.

[0113] For example, in a retail scenario, a user scans a QR code next to a product shelf using an application. The terminal reads the merchant identification information from the QR code and requests object detail page data from the server. The server returns object detail page data for that store or product category, and the terminal displays the object detail page, which includes the store name, current best-selling product rankings, new product recommendations, coupon redemption entry, and product creation entry. After the user clicks the product creation entry, the terminal requests dialog page data from the server. The server returns the dialog page configuration information corresponding to that store, and the terminal renders and displays the dialog page.

[0114] For example, in a leisure and entertainment scenario (such as a KTV), a user brings their mobile phone close to an NFC tag placed at the KTV counter or inside a private room. The terminal reads the merchant identification information from the tag and requests object details page data from the server. The server returns the object details page data for that store, and the terminal displays the object details page, which includes a store introduction, a display of the private room environment, recommended popular song lists, excerpts of user reviews, and a product creation entry (such as a "Smart Recommended Song List" button). After the user clicks the product creation entry, the terminal displays a dialog page.

[0115] Step 406: In response to sending a product recommendation request on the dialog page, display recommended product information generated by the smart object based on the product recommendation request on the dialog page.

[0116] It is understood that the explanation of step 406 can be found in the explanation of step 204 above, and will not be repeated here.

[0117] Step 408: In response to determining the target product information based on the recommended product information, a product creation request for the target product information is sent to the target object; the target product information is used by the target object to create the target product.

[0118] It is understood that the explanation of step 408 can be found in the explanation of step 206 above, and will not be repeated here.

[0119] In the aforementioned information processing method, by responding to the trigger operation of the product creation entry on the object details page and displaying a dialogue page with the smart object, and by calling the smart object to generate recommended product information based on the product recommendation request, users can quickly obtain recommendations that match their own and their companions' preferences without having to compare numerous options one by one. This significantly reduces the decision-making burden and time cost of online or offline consumption, and improves overall consumer satisfaction. By sending a product creation request to the target object, merchants can simultaneously obtain users' product needs, thereby preparing products in advance and improving operational efficiency and user experience. Using the object details page as a unified information display and interaction entry point lowers the threshold for users to discover and understand the target object, achieving a seamless connection from information browsing and personalized recommendations to product creation.

[0120] According to an embodiment of the present invention, a dialog page includes at least one requirement retrieval control; the method further includes: in response to a triggering operation on the at least one requirement retrieval control, retrieving requirement information; and in response to a confirmation operation on the requirement information, sending a product recommendation request including the requirement information on the dialog page.

[0121] The dialogue page can include one or more demand retrieval controls, each corresponding to a specific preference or demand dimension, used to collect user-input demand information through different types of controls. For example, the dialogue page includes a form-type interface, where users convey their own and their companions' personalized needs to the system by filling in or selecting various customized content. The layout and content of the dialogue page can be dynamically configured based on the merchant type, service, or product category corresponding to the target item. For example, in an offline store ordering scenario, the dialogue page can display controls for inputting information such as taste preferences, dining scenarios, and attribute preferences; in a retail scenario, the dialogue page can display controls for inputting product demands.

[0122] Demand retrieval controls refer to interactive units on a dialog page used to collect preference information in specific dimensions. Each demand retrieval control can correspond to a preference dimension, such as taste preference, dietary restrictions, number of diners, consumption scenario, budget range, etc. Demand retrieval controls can implement data collection functions through different types of controls, including but not limited to: text boxes (e.g., inputting dietary restrictions or special requirements), checkboxes (e.g., selecting preference tags or additional options), drop-down lists (e.g., selecting the number of diners or spiciness level), sliders (e.g., selecting the budget range), etc. Triggering an operation for a demand retrieval control refers to the interactive instruction executed by the user on the demand retrieval control to express demand selection. Users can execute triggering operations on the dialog page in the following ways: for option buttons, users select an option by touch or mouse click; for drop-down lists, users click to expand and select a list item; for sliders, users drag the slider to adjust the value; for date pickers, users click and select a date or time period. Triggering operations can be executed manually by the user, and the terminal responds to the operation by acquiring the content selected or entered by the user as part of the demand information.

[0123] The confirmation operation for request information refers to the action command that triggers the sending of a product recommendation request after the user has selected or filled in the request retrieval controls, confirming the currently entered request information. The confirmation operation can be manifested by the user clicking the "Confirm" or "Generate Recommendation" buttons on the dialog page, or by the user confirming via voice command. In some implementations, the confirmation operation may also be automatically triggered after the user completes their action on the last request retrieval control.

[0124] For example, refer to Figure 5 In an offline store ordering scenario, the dialogue page can include the following requirements retrieval controls: number of diners, budget range, dietary restrictions, taste preferences, and companion preferences. After the user interacts with each requirement retrieval control, the terminal obtains the user's input requirements information, which is then used by the intelligent object to generate recommended product information. The terminal responds to the user's confirmation button (e.g., ... Figure 5 The "Start Menu Customization" button in the menu triggers a product recommendation request, including the user's needs, on the dialog page. The server inputs the needs information into the smart object, which then performs reasoning and calculations to output at least one recommended product.

[0125] For example, in a retail scenario, the dialog page displayed on the terminal may include the following requirements acquisition controls: product category requirements acquisition control, functional preference requirements acquisition control, specification and size requirements acquisition control, budget range requirements acquisition control, color preference requirements acquisition control, and usage scenario requirements acquisition control. After the user interacts with each requirements acquisition control, the terminal obtains the user's requirements information regarding product attributes, functional needs, specifications, and dimensions, so that the intelligent object can recommend products that meet the user's personalized needs.

[0126] For example, in a leisure and entertainment scenario (such as a karaoke bar), the dialogue page displayed on the terminal may include the following demand acquisition controls: a demand acquisition control for the number of participants, a demand acquisition control for music style preferences, a demand acquisition control for language preferences, and a demand acquisition control for playlist duration. After the user interacts with each demand acquisition control, the terminal acquires the user's demand information regarding music style, scene type, etc., so that the intelligent object can recommend suitable playlists.

[0127] In one optional implementation, the request retrieval controls on the dialog page can support dynamic loading or step-by-step display. For example, the terminal can dynamically adjust the displayed content or option list of subsequent request retrieval controls based on the user's selection of a particular control. For instance, in an offline restaurant ordering scenario, if a user selects "dining alone" when choosing the consumption scenario request retrieval control, the subsequent companion preference request retrieval control can be hidden or marked as optional; if the user selects 6 or more people when choosing the number of diners request retrieval control, the system can automatically add a request retrieval control for whether a private room is needed. Through dynamic adjustment, the dialog page can streamline the displayed content according to the user's actual needs, reducing the user's workload.

[0128] In one alternative implementation, the request retrieval controls on the chat page can be pre-populated based on the first account's historical behavior data or historical order information. For example, when the server returns chat page data, it can carry the first account's historical preference tags (such as a preference for less spicy food shown in historical order records). When the client renders the chat page, it sets the corresponding request retrieval controls to the default selected state. Users can modify or confirm based on the pre-populated data, eliminating the need to repeatedly enter the same preference information for each purchase, further reducing decision-making costs.

[0129] In this embodiment, structured controls reduce the difficulty for users to express their needs, improve the accuracy and efficiency of demand information collection, and at the same time preserve the naturalness of dialogue interaction, providing users with a flexible and efficient way to input their needs.

[0130] According to an embodiment of the present invention, the method further includes: in response to a modification operation on target product information in recommended product information, displaying the modified target product information on a dialog page; and in response to a confirmation operation on the modified target product information, sending a product creation request for the modified target product information to a target object.

[0131] Before sending a product creation request to the target audience, users may need to fine-tune or modify the selected product information to better suit their own and their companions' needs. Modification operations refer to interactive commands executed by the user through the terminal to adjust one or more aspects of the target product information. Modification operations can target different dimensions of the target product information, including but not limited to: modifying specific items of the product or service (such as changing dishes or replacing products), modifying quantity (such as increasing or decreasing the number of servings), modifying specifications (such as changing size, color, or flavor), and modifying additional services (such as adding or removing complementary services). Users can perform modification operations on the target product information on the terminal in the following ways: in a dialog page displaying recommended product information, the user clicks the edit or modify control corresponding to the target product information; the user clicks a specific item in the target product information (such as a dish or product specification), triggering the display of the modification interface for that item; the user directly adjusts parameters such as quantity and specifications using sliders, add / delete buttons, or drop-down lists; and the user makes modifications via voice commands. Modification operations can also be performed manually by the user, and the terminal responds by updating the target product information accordingly.

[0132] For example, in an offline store ordering scenario, a smart object generates at least one recommended product, which is then displayed on the dialog page. The user initially selects target product A. After browsing the details of this target product on the dialog page, the user discovers that their companion is not interested in dish B and wishes to change it. The user clicks the edit button corresponding to target product A, and the terminal redirects to the edit page. The edit page displays a list of dishes in target product A, with each dish accompanied by a replace and delete control. The user clicks the replace control next to dish B, and the terminal displays a list of replaceable dishes (this list can be dynamically generated by the smart object based on the user's expressed needs). The user selects dish C from the replace list, and the terminal replaces dish C in the target product information and recalculates the total price. After the user confirms the changes are correct, they click the confirm button, and the terminal returns to the dialog page, displaying the modified target product information. If the user wishes to make further adjustments, they can also modify the quantity, such as changing dish D from one serving to two. The terminal responds to the quantity change operation by updating the total price.

[0133] For example, refer to Figure 6 The dialog page displays two recommended product information generated by the smart object. The user initially selects option two and clicks the corresponding modify button for option two (e.g., ...). Figure 6 (As shown by the "Edit Menu" button), the terminal redirects to the edit page. The edit page displays the menu list from Option 2 and a "Continue Adding Items" button, with quantity adjustment controls next to each item. When the user clicks the "Continue Adding Items" button, the terminal displays the full menu page, allowing the user to select to add or delete items. In response to the user's confirmation button on the full menu page, the terminal returns to the dialog page, displaying the modified target item information.

[0134] In one alternative implementation, the modification operation can support batch modification or combined adjustment of multiple items in the target product information. For example, in an offline store ordering scenario, a user can simultaneously replace multiple dishes on the modification page, or replace an entire set of dishes using the regenerate button. The system regenerates a set of alternatives based on the user's expressed needs for the user to choose from. For example, in a retail scenario, a user can simultaneously adjust the quantity and specifications of multiple items on the shopping cart modification interface.

[0135] In one alternative implementation, the modification operation can be linked with a smart object to provide intelligent modification suggestions. For example, when a user replaces a dish in a modification operation, the smart object can automatically recommend the most suitable replacement option based on the user's expressed needs (such as dietary restrictions or preferences) and the pairing relationship between the replaced dish and the remaining dishes, and indicate the reason for the recommendation next to the replacement option. For example, when a user changes the number of participants, the smart object can automatically adjust the quantity or portion size of each item in the target product information, or add recommended pairing dishes and provide prompts (e.g., after adjusting the number of participants to 5, it is suggested to upgrade the main course to a large portion).

[0136] In one alternative implementation, after the modification operation is completed, the client or server can perform auxiliary processing related to the modification. For example, when a user modifies product specifications, resulting in a price change, the server can re-verify the applicability of coupons and notify the user of the change in discount information on the interface. For example, when a user modifies service hours, causing the selected service provider to become unavailable, the server can verify and notify the user in real time, and automatically recommend other available service providers or adjacent time slots for that period.

[0137] In one alternative implementation, the modification operation can support multiple rounds of iterative modifications, allowing users to continue with the next modification after the previous one. The client can record the user's modification history and provide undo or restore default functions in the modification interface, allowing users to revert to the state before the modification.

[0138] Understandably, after logging in with an initial account, the client displays at least one recommended product, from which the user initially selects a target product. The client continuously monitors user interaction events on the chat page. When it detects that the user has modified the target product information, the client responds to this modification and initiates the modification process. The client can either navigate to a dedicated modification page or expand an embedded modification panel on the recommended product card, displaying the modifiable items for the target product information. After the user adjusts the items, the client updates the modified data locally and requests data support from the server (such as a list of replacement options, updated prices, inventory verification results, etc.). The server returns the corresponding data based on the modifications, and the client updates the interface display accordingly. After the user completes all modifications and confirms to exit the modification mode, the client displays the modified target product information. The user can then proceed with subsequent confirmation operations, thereby sending a product creation request for the modified target product information to the target object.

[0139] In this embodiment, users are provided with the ability to flexibly adjust the recommendation scheme before sending a product creation request, so that the final target product more accurately meets the user's actual needs, further improving the satisfaction and flexibility of consumption decision-making.

[0140] According to an embodiment of the present invention, the modified target product information is obtained by modifying the target product information based on modification information and supplementary modification information; the modification information is obtained in response to the modification operation of the first account on the target product information in the recommended product information, and the supplementary modification information is obtained in response to the modification operation of the second account on the target product information in the recommended product information, wherein the first account and the second account are different.

[0141] In scenarios involving multiple consumers or requiring coordination of preferences among various parties, this step involves interaction and collaboration between multiple user accounts. By having different accounts initiate modification operations or provide supplementary modification information, joint adjustments to the target product information can be achieved.

[0142] Modified information refers to the specific content entered by the primary account (i.e., the entity initiating the modification) through a modification operation, used to adjust the information of the target product. Modified information may include, but is not limited to: replacing a product or service, adjusting the quantity, changing specifications, modifying service hours, adding or removing additional services, etc. Modified information can be obtained through interactive controls on the dialog page, or it can be the intent to modify entered in natural language on the dialog page.

[0143] Supplementary modification information refers to modifications initiated by a second account, different from the primary account, to adjust the target product information. Supplementary modification information can be obtained through interactive controls on the dialog page, or by inputting modification intent in natural language on the dialog page. Supplementary modification information, together with the modification information, constitutes a complete adjustment plan for the target product information, reflecting the interactive characteristics of multi-person collaborative decision-making.

[0144] In one optional implementation, a client logged in with a first account responds to a user action by sharing target product information with a client logged in with a second account. The client logged in with the second account displays a sharing page containing the target product information. The sharing page may include detailed information about the target product and interactive controls for submitting modification suggestions. The first account can send the target product information to the second account via the application's built-in sharing function as a link, card, or message. After logging into their respective clients, the second account clicks on the shared content to enter the sharing page, where they can view the target product information and input modification suggestions through interactive operations. Optionally, the server integrates the supplementary modification information input by other accounts with the modification information from the first account to form the final modification plan.

[0145] For example, refer to Figure 7In an offline store ordering scenario, the first account (user A) initially selects the target product information (e.g., ...) on the chat page. Figure 7 (Scheme 2 shown). User A believes the combination basically meets expectations but wants their companion, User B, to participate in the decision-making process. The first account clicks the "Share with Friends" button on the recommended product information card, sharing the target product information with the second account (User B) via instant messaging. The second account clicks the share link to enter the sharing page. The sharing page displays the menu, total price, and reasons for recommendation for the target product information, and includes a "Add More Products" button. The second account clicks this button to enter the full menu page to delete, add, or replace dishes. After the second account submits modification suggestions, the server associates the supplementary modification information with the first account's original target product information. The first account receives real-time update notifications from the server in the chat page, and the menu in the chat page automatically refreshes to the combination modified by the second account, synchronously updating the total amount. After reviewing the modification results, if the first account is satisfied, they can click the "Confirm Order" button to send a product creation request; if further adjustments are needed, the first account can continue to make further modifications in the chat page or share it again with the second account for a second round of collaborative adjustments. During this process, the first account initiated the modification operation and obtained the modification information, while the second account provided supplementary modification information through interactive operations on the sharing page. The two accounts collaborated to complete the modification of the target product information.

[0146] In another alternative implementation, both the modification information and supplementary modification information can be obtained through a dialogue page that interacts with the smart object. Furthermore, the dialogue information used to provide the modification information and the dialogue information used to provide supplementary modification information are sent through different accounts. In this implementation, collaborative modification by multiple users is completed through dialogue interaction. The smart object acts as the dialogue hub, engaging in dialogue with different accounts to collect modification opinions from all parties and integrate them to generate the final modification plan.

[0147] For example, in an offline store ordering scenario, the first account (User A) and the intelligent object engage in multiple rounds of dialogue on a chat page, expressing initial modification requests. The intelligent object confirms and updates the target product information. Subsequently, the first account sends a sharing link of the chat page to a companion account (User B). After the second account enters the chat page, it engages in dialogue with the intelligent object. The intelligent object recognizes that User B's account is different from User A's account and records User B's modification suggestions as supplementary modification information. Based on the supplementary modification information, the intelligent object further modifies the updated target product information and provides the modified target product information to the first account for review. After the first account confirms, the terminal sends a product creation request based on the modified target product information. In this process, the modification information originates from the first account's chat information, and the supplementary modification information originates from the second account's chat information. The two different accounts collaborate through the chat page to modify the target product information.

[0148] In one optional implementation, the server can maintain the modification status of the target product information, recording the processing status of modifications and supplementary modifications submitted by each account. When multiple accounts submit modification suggestions simultaneously, the server can handle them according to a preset conflict resolution strategy. For example, the final confirmation from the main account that initiated the sharing may prevail, or a voting mechanism may be used to determine the adopted solution, or an intelligent object may automatically recommend a compromise solution based on the matching degree of preferences of each party. After integrating the modification information, the server can also synchronize the updated target product information to all participating accounts to ensure that the content seen by each account is consistent.

[0149] In one optional implementation, the sharing page can support multiple rounds of interaction. This means that after a second account submits supplementary modifications on the sharing page, it can continue to view the changes and make further modifications until satisfied. The server can record the version history of each modification, supporting rollback to any historical version, allowing users to easily trace the modification process.

[0150] In one optional implementation, in a multi-user collaborative scenario on a dialogue page, the intelligent object can maintain a shared dialogue context, merging dialogue information sent by different accounts into a unified session, allowing each participating account to see the complete dialogue history. The intelligent object can proactively solicit opinions from other accounts during the dialogue. For example, after collecting modification information from the first account, the intelligent object can send a request for feedback to the second account. Through this proactive solicitation, the intelligent object can more efficiently collect opinions from multiple parties. This implementation can be further extended to an AI group chat mode, where the intelligent object interacts with multiple accounts simultaneously in a multi-user dialogue group, merging scattered modification opinions into a unified session context to achieve efficient group decision-making. Optionally, after the main account performs a confirmation operation, the intelligent object submits the final modification plan to the server. The server updates the target product information and synchronizes the updated menu list and total amount to all participating accounts. Optionally, after all participating accounts perform a confirmation operation, the intelligent object submits the final modification plan to the server. The server updates the target product information and synchronizes the updated menu list and total amount to all participating accounts. All participating accounts can see the modified menu details on their respective chat pages without needing to navigate back. Through AI group chat, the intelligent object acts as the central hub, collecting opinions from multiple parties in real time, generating alternative solutions, resolving conflicts, integrating modifications, and ultimately outputting a recommended solution that is acceptable to all parties.

[0151] Understandably, after the user with the first account logs in and displays at least one recommended product, they initially select a target product. When multiple users need to collaborate on modifications, the first account can share the target product information with a second account. The second account then inputs supplementary modification information through the sharing page or chat page, using interactive operations or natural language dialogue. The server collects the modification information from the first account and the supplementary modification information from the second account, integrates them, and returns the integrated modification result to the first account's client. The first account's client updates the displayed content of the target product information based on the modification result returned by the server. After the user confirms the modification result, they can continue to send a product creation request. This step provides a mechanism to support collaborative modification by multiple users, allowing different accounts to propose adjustments to the target product information, and through the integration of the modified information and supplementary modification information, a final recommendation scheme acceptable to all parties is formed.

[0152] In this embodiment, the joint modification of target product information is realized in a multi-person collaborative scenario, so that the final confirmed recommendation can take into account the personalized preferences of multiple participants, thereby improving decision-making efficiency and satisfaction in multi-person consumption scenarios.

[0153] According to one embodiment of the method of the present invention, the recommended product information is generated by the smart object based on the demand information in the product recommendation request and the supplementary demand information in the target recommendation request; the product recommendation request is sent by a first account on the dialogue page with the smart object, and the target recommendation request is sent by a second account on the dialogue page with the smart object, wherein the first account and the second account are different.

[0154] In scenarios involving multiple people making joint purchases or requiring coordination of preferences among various parties, this step involves multiple user accounts providing their respective needs information to form a more comprehensive understanding of those needs.

[0155] Demand information refers to the personalized preference data entered or selected by the primary account through the dialogue page. Supplementary demand information refers to additional preference data provided by accounts other than the primary account (such as a secondary account) to supplement or correct the initial demand information. The introduction of supplementary demand information aims to address the problem that demand information provided by a single account in a multi-person consumption scenario cannot fully represent the preferences of all participants. By collecting demand information from multiple accounts, the intelligent object can more comprehensively understand the overall needs of the consumer group, thereby outputting more inclusive and satisfying recommended product information.

[0156] In practice, supplementary requirement information can be obtained in two ways: through interaction with the same target item using a second account; and through interaction with the sharing page using a second account. The following sections provide detailed explanations of these two methods and their processing procedures.

[0157] In a multi-user consumption scenario, multiple users can interact with the same target item using their respective devices. The first account interacts with the target item first, enters the dialogue page, and provides its requirements. Subsequently, one or more second accounts can also interact with the same target item, each entering supplementary requirements. The server associates the requirements submitted by different accounts for the same target item, forming a complete set of requirements for the current consumption scenario.

[0158] For example, in an offline store ordering scenario, an NFC tag is attached to the tabletop as the target item. The first account touches the NFC tag with their phone to enter a dialogue page and provide their request information. After the first account submits their request information, the server records this interaction and the corresponding request information. Subsequently, the second account also touches the same NFC tag with their phone to enter a dialogue page. The server recognizes that this interaction is for the same target item as user A's interaction, and that the second account's account is different from the first account's. Therefore, the server collects the request information submitted by the second account as supplementary request information. The server summarizes the request information submitted by the first account, the second account, and other accounts that touched the same NFC tag (if any), forming a complete request set. The server inputs this complete request set into a smart object, which generates at least one recommended product based on this information. Through multiple interactions with the same target item, different accounts supplement their personalized needs, enabling the final recommendation to take into account the preferences of multiple parties.

[0159] In one optional implementation, the client logged in with the first account responds to user interaction by sharing a chat page with the client logged in with the second account. The client logged in with the second account displays the chat page and provides supplementary requirements through it. After entering the chat page, the first account can send the chat page to the second account via the application's built-in sharing function as a link, card, or message. After logging into their respective clients, the second account clicks on the shared content to enter the chat page, views the current requirements, and enters their supplementary requirements through interactive operations. The server associates the supplementary requirements submitted by the second account with the initial requirements of the first account to form a complete set of requirements.

[0160] For example, in an offline store ordering scenario, the first account enters a dialogue page by touching an NFC tag and inputs some request information. The first account wants a companion to also participate in the ordering decision, so it clicks the share button on the dialogue page and sends the share link to the second account via instant messaging. The second account clicks the share link and enters the dialogue page. The dialogue page can display the currently entered request information and includes controls or dialogue entry points for supplementing preferences. The second account provides supplementary request information on the shared page. The server aggregates the supplementary request information submitted by the second account through the dialogue page with the initial request information from the first account, forming a complete request set, which is then input into the smart object to generate recommended product information that takes into account the preferences of multiple parties. By sharing the page, even if other users are not physically present to touch the target item, they can remotely participate in supplementing the request information.

[0161] For example, refer to Figure 8The first account enters the chat page by touching the NFC tag, inputs the required information, and a share button is displayed on the chat page (e.g., ...). Figure 8 The "Generate Menu Based on Friend Preferences" button shown above, in response to the first account's trigger action on the share button, sends the share link of the chat page to the second account via instant messaging. The terminal of the first account displays the status of other accounts in real time (e.g., adding information, adding information completed). After the second account submits the supplementary request information, the first account clicks the submit control in the chat page (e.g., ...). Figure 8 (As shown by the "Start Menu Customization" button), the server responds to this operation by inputting the demand information provided by the first account and the supplementary demand information provided by the second account into the smart object, and generating recommended product information that takes into account the preferences of multiple parties.

[0162] In one alternative implementation, the two methods of obtaining supplementary requirement information can be combined. For example, some teammates supplement the requirement information on-site through other interactive operations on the same target item, while others supplement the requirement information remotely through a shared chat page. The server then aggregates and deduplicates all requirement information from all sources to form a complete requirement set.

[0163] In one optional implementation, the server can maintain a demand information session for the current consumption scenario, grouping demand information from multiple interactions associated with the same target item or from multiple accounts associated with the same sharing link into the same session. The server can aggregate the demand information submitted by each account based on the session identifier, and after all accounts have submitted their demand information (or after a preset timeout period, or after the main account confirms the submission), input the complete demand information into the smart object to generate recommended product information. Alternatively, the server can use an incremental update approach, where whenever new supplementary demand information is received, the smart object is invoked again in real time to generate updated recommended product information, and the updated results are synchronized to the terminals of all participating accounts. This implementation can be further extended to an AI group chat mode, where the smart object interacts simultaneously with multiple accounts in a multi-person dialogue group, guiding each account to input their personalized preferences through dialogue, and merging scattered demand information into a unified session context to achieve efficient group demand collection.

[0164] In one optional implementation, the server can record the order and timestamps of the requests submitted by each account and prioritize them based on this information. For example, if the first account is the primary account (such as the account that initiated the sharing), its request information can be used as the basis, and the supplementary request information from other accounts can be used as additional constraints. If there are conflicts in the supplementary request information from multiple accounts, the server can handle them according to preset rules (such as majority rule or primary account priority rule), or generate a compromise solution using a smart object and display a conflict explanation to each account.

[0165] Understandably, after the client with the first account logs in displays the dialogue page and obtains initial request information, the server continuously monitors for other interactions targeting the same item or the shared dialogue page. When the server detects that the second account has submitted supplementary request information through any of the above methods, it collects and stores this supplementary request information, associating and integrating it with the initial request information of the first account. The server then inputs the integrated complete request information (including the initial and supplementary request information) into the smart object. The smart object performs inference calculations based on the complete request information and outputs at least one recommended product. The server returns the recommended product information output by the smart object to the clients of both the first and second accounts, and each client displays the recommended product information on the dialogue page for users to browse and select.

[0166] In this embodiment, collaborative collection of preferences from multiple parties in a multi-person consumption scenario is realized, enabling intelligent objects to generate recommended product information based on complete group needs. This effectively solves the problems of difficulty in coordinating preferences and information asymmetry when multiple people consume together, and improves the group satisfaction and decision-making efficiency of the recommendation results.

[0167] In one alternative implementation, after step 206 or step 408, the completion progress of the target product is displayed on the dialog page.

[0168] In a physical store ordering scenario, after a user completes their request by inputting their needs, selecting their desired product, and sending a product creation request through a chat interface, the device displays the product's progress in the chat interface's progress display area. (Refer to...) Figure 9 The diagram on the left shows the merchant's status at the top of the chat page, indicating that the product information has been successfully submitted to the merchant and processing has begun. The middle of the page displays an overall progress bar, including four stages: Order Placed, Preparing Ingredients, Cooking, and Completed. The "Order Placed" stage is highlighted, indicating the target product is in the "Order Placed, Waiting for Preparation" stage. The bottom of the page displays a list of details for each dish within the target product, including dish name, unit price, and status tag. Through this page, users can clearly understand that the target product has been successfully submitted and the merchant is preparing the dish, but actual cooking has not yet begun. As the preparation progresses, the server receives real-time feedback from the merchant on the preparation status of each dish and pushes the status updates to the client. Figure 9As shown in the middle diagram, the progress display area on the chat page updates accordingly when some dishes are prepared or enter the next stage. In the overall progress bar, nodes in the preparation stage are highlighted, indicating that the target item has entered the preparation stage. The completion rate is visually displayed in the dish list using a percentage or circular progress bar. Users can obtain the real-time preparation progress of each dish by refreshing the page or through automatic polling in the client, allowing them to plan their meal pickup or dining time accordingly. Once all dishes have been prepared and cooked, as shown... Figure 9 As shown in the diagram on the right, completed nodes are highlighted in the overall progress bar, indicating that all target products have been completed. The status of all dishes in the menu list is updated to "completed".

[0169] In one optional implementation, the completion progress of the target product can support aggregated display of progress for multiple dishes. When the target product includes multiple dishes, the server can calculate the overall completion progress (e.g., the percentage of completed dishes out of the total number of dishes) and display it through an overall progress bar or percentage value. Individual status can be displayed next to each dish in the form of progress percentage, progress ring, status label, etc., making it easy for users to understand the preparation status of each dish.

[0170] In one optional implementation, the progress display area on the dialog page can be collapsed and expanded. By default, the progress display area is presented in a simplified form (e.g., only showing the overall progress bar and total amount). After the user clicks to view details, the full list of dishes and individual statuses are expanded to save page space while meeting the user's need to view as needed.

[0171] According to an embodiment of the present invention, after step 206, the method further includes: in response to a further interaction with a target item related to a target object, displaying the completion progress of the target item in a dialogue page with the smart object.

[0172] The "re-interaction" refers to the operation command executed again by the user on the same target item after sending a product creation request, which triggers a product status query. Users can perform re-interactions on the target item on the terminal in the following ways: for NFC tags, the user brings the terminal close to or taps the target item again; for QR codes, the user scans the target item again using the application's built-in scanning function; for Bluetooth beacons, the terminal automatically detects and triggers interaction when it re-enters the beacon's signal coverage area. Re-interactions can be performed manually by the user, such as bringing the phone close to an NFC tag on the desktop to check the completion progress of the target product while waiting for service after sending a product creation request; in some cases, re-interactions can also be automatically triggered by the terminal based on location awareness, such as automatically querying the product status when the terminal detects that the user has re-entered the merchant's Bluetooth beacon range.

[0173] The completion progress of a target product refers to the real-time status information of each key stage in the process from creation to final delivery. Completion progress reflects the processing stage of the target product, helping users understand the estimated waiting time and subsequent processes. The completion progress of a target product may include, but is not limited to, the following status dimensions: product information receipt status (e.g., ordered), preparation / stocking status (e.g., preparing ingredients, cooking, picking), and serving / shipping status (e.g., served, completed). The display format for the completion progress of a target product may include a progress bar, a list of status nodes, and estimated remaining time.

[0174] For example, in an offline store ordering scenario, after a user sends a product creation request, the merchant creates the target product and begins preparation. While the user waits, they bring their phone close to the NFC tag on the table again. In response to this second interaction, the terminal sends a progress query request to the server, carrying the user's account information and the target item's identifier. The server locates the current table and order information in the store based on the target item's identifier (or queries currently valid incomplete product information based on the user's account), and returns the completion progress data for the target product. The terminal displays the completion progress of the target product on the dialogue page with the smart object. This page may include: product status nodes (ordered, preparing, cooking, completed) and a detailed list of dishes. For specific display content, please refer to [link to relevant documentation]. Figure 9 As shown.

[0175] For example, in a retail scenario (such as in-store pickup), after a user sends a product creation request, the merchant creates the target product and picks and packs it. While browsing in the store, the user scans the QR code next to the product shelf again. The terminal responds to this second interaction by displaying the completion progress of the target product on a dialogue page with the smart object. This page may include: product status, a list of picked products, estimated completion time, and pickup instructions.

[0176] In one optional implementation, the completion progress of the target product can be displayed visually, such as a progress bar, timeline, or dynamic icons, to enhance the user's intuitive understanding of the progress. For example, in an offline store ordering scenario, the progress bar gradually advances from 0% to 100%, with each stage labeled; when the dish is about to be completed, the terminal can provide a vibration or sound notification to attract the user's attention.

[0177] In one optional implementation, the completion progress of the target product can be queried synchronously across multiple devices. For example, in a multi-person dining scenario, after the first account sends a product creation request, other user accounts can also query the completion progress of the target product when they access the same item again. Through multi-device synchronization, any member of the same consumer group can check the product status at any time without relying on notifications from the main account.

[0178] In one optional implementation, the completion progress of the target product can be differentiated into paid and unpaid states. If the user has not completed payment upon subsequent interaction, the terminal can guide the user to complete payment before displaying the completion progress of the target product. For example, after the user touches the target item, the terminal first displays the order information pending payment; after the user completes payment, it automatically redirects to a dialog page to display the completion progress of the target product.

[0179] In one optional implementation, the completion progress of the target product can include interactive controls, allowing users to perform subsequent operations on the created product. For example, in an offline store ordering scenario, the progress page can include an "Extend Order" button, which sends an order reminder to the merchant when clicked by the user; an "Add to Order" button, which returns the user to the ordering page to add more dishes; and a "Contact Merchant" button, which allows the user to communicate with the merchant. In a retail scenario, the progress page can include a button to change the pickup method, allowing users to switch from self-pickup to delivery.

[0180] In one alternative implementation, when a user touches the target item again after the order is completed, the terminal can display an order confirmation page and invite the user to rate or share the item. This allows merchants to collect user feedback.

[0181] In one alternative implementation, the server can automatically match the most relevant created product based on the target item's identifier and the primary account. For example, if the same target item is associated with multiple created products (such as multiple orders for the same meal), the server can automatically match the most relevant created product based on the product's creation time, product status (incomplete orders take priority), and the primary account, and then display the completion progress of that created product to the terminal.

[0182] Understandably, after sending a product creation request, the client with the initial account continuously monitors interaction events such as near-field communication, camera scanning, or Bluetooth signals. When it detects that the user is interacting with the same target item again, the client sends a progress query request to the server. The server responds to this request by querying the current valid progress data of the target product (such as product status, completion time of each stage, estimated remaining time, etc.) based on the user account information and the target item identifier, and returns the progress data to the client. The client then renders and displays the completion progress of the target product based on the returned data, providing the user with a clear view of the target product's current status and subsequent processes.

[0183] In this embodiment, a convenient entry point for checking the status of goods in offline consumption scenarios is provided to users. Users do not need to open the order list or contact the merchant. They can quickly understand the completion progress of the goods by simply touching the target item again, which improves service transparency and user experience.

[0184] According to an embodiment of the present invention, after step 408, the method further includes: in response to a triggering operation on a progress entry in the object details page, displaying the completion progress of the target product in a dialogue page with the smart object.

[0185] The object details page also includes a progress entry point, allowing users to quickly check the completion progress of the currently created target product. The progress entry point is an interactive control on the object details page that guides users through the progress query process. It can be a button, icon, link, card area, or other triggerable UI element.

[0186] In one alternative implementation, in the scenario of ordering food at an offline store, refer to... Figure 10 If a user has already ordered and paid for food at a restaurant and wants to know the preparation status of the dish, they can open the application to access the restaurant's item details page, or display the item's item details page in response to further interaction with the target item. In response to a triggering action on a progress entry point (such as a "Check Order Progress" button) on the item details page, the completion progress of the created target item can be displayed in a dialog box. Optionally, a progress card can be displayed in the dialog box, showing the completion progress of the created target item.

[0187] In one optional implementation, the completion progress displayed on the dialogue page can be updated in real time. After the user enters the dialogue page, the client can continuously receive progress updates pushed by the server. The smart object can automatically send new messages to update the progress without requiring the user to manually refresh. The user can also actively send a refresh progress command, and the smart object will immediately return to the latest status.

[0188] In this embodiment, users are provided with a convenient channel to quickly check the completion progress of a target product from the object details page. By using a unified interactive experience through a dialog page, service transparency and query efficiency are improved.

[0189] According to an embodiment of the present invention, after step 206 or step 408, the method further includes: in response to a notification message of an abnormal product sent by the target object, displaying a modification control for the abnormal product on a dialog page; and in response to an interactive operation on the modification control, sending a product modification request for the abnormal product to the target object.

[0190] The notification message for abnormal products refers to the information sent to the user by the server or merchant after the target product is created, when factors such as inventory changes, insufficient materials, temporary changes in service personnel, equipment failure, or weather effects prevent one or more items in the order from being delivered as originally planned. This notification message is used to promptly inform the user of the abnormal product situation, avoiding prolonged waiting or misunderstandings due to lack of awareness. The notification message for abnormal products may include the following information: the specific details of the unfulfilled item (e.g., dish A is sold out) and an interactive entry point to guide the user to subsequent actions.

[0191] Notification messages can be pushed via various methods, including but not limited to: in-app push notifications (such as message center notifications and pop-up alerts), system-level notifications (such as push notifications from the phone's status bar), and instant messaging messages. Notification messages can be presented as interactive cards, allowing users to directly navigate to a dialog page with edit controls after clicking the card. Notification messages can be sent immediately after the merchant confirms an order cannot be fulfilled, or proactively pushed by the server after detecting a change in the product's status.

[0192] Edit controls refer to interactive controls placed on a dialog page to guide users through the editing process. Edit controls can manifest as buttons, links, card areas, or other triggerable interface elements. Optionally, an edit control is an interactive control used to trigger a jump from the current interface to the edit page. Users can enter the edit page to perform editing operations by touching and clicking the area of ​​the edit control. Optionally, edit controls include delete and replace controls placed on the dialog page. The delete control is used to delete unachievable items from the target product (i.e., cancel the corresponding abnormal product order), and the replace control is used to select and replace an option. In this way, product modifications can be performed directly on the current page without entering a separate page, enabling quick product modification.

[0193] Replacement solutions refer to alternative options generated by the merchant or intelligent objects for abnormal products within the target product category, based on factors such as the target product content, demand information, and current available inventory. Replacement solutions can include one or more alternative options, each containing information such as the alternative's name, specifications, price (if any price difference exists), and the reason for recommendation. Replacement solutions can be personalized by intelligent objects based on user needs, ensuring that the alternatives closely match the user's original requirements.

[0194] A product modification request refers to an instruction sent by the terminal to the server (or the target object) to update the product content after the user selects a replacement option or deletes an unachievable item through modification controls. A product modification request can include the following operations: removing unachievable items from the target product, adding replacement items, recalculating the total price of the product, handling price differences (such as charging or refunding price differences), and updating the product status. After the product modification request is completed, the transaction contract between the user and the target object is updated accordingly, and the target object delivers services or goods based on the modified product content.

[0195] For example, in an offline store ordering scenario, a merchant discovers during food preparation that dish A cannot be prepared due to a temporary shortage of ingredients. The merchant marks dish A as unavailable through the merchant application. Upon receiving this mark, the server pushes an abnormal product notification message to the primary account, presented as an in-app pop-up. After the user clicks this button, the terminal displays modification controls for the abnormal product on a dialog page. The modification controls include deletion and replacement controls, with at least one alternative option displayed. The server generates at least one alternative option based on the user's request information provided on the dialog page and the current available product inventory. After browsing the various alternative options, the user selects any one and clicks the "Confirm Replacement" button. The terminal sends a product modification request to the server. The server replaces dish A in the target product list with the user-selected alternative, recalculates the total product price, updates the product status to "Modified," and returns a success message to the user's terminal. The merchant simultaneously receives the updated target product information and prepares the meal according to the modified dish. If users are not satisfied with any of the generated replacement options, they can click on "Other Options" on the replacement option selection page to enter the full menu page and choose alternative dishes themselves.

[0196] In one alternative implementation, refer to Figure 11The process of selecting a replacement option can be initiated by the merchant. After discovering that one or more items in the target menu cannot be fulfilled, the merchant communicates with the user to confirm and completes the replacement operation via a page provided by the merchant. The server then pushes the updated data to the user's device for display. The merchant provides an order details page that displays the progress of the order and offers multiple handling options for unfulfilled items, such as recommended replacement options, refund, etc. Optionally, when the merchant selects a recommended replacement option, the merchant can invoke a smart object to generate one or more recommended replacement options for the merchant's reference, based on the target product content, the user's request information provided in the dialogue page, and the current available inventory. The merchant's page displays these replacement options in a list format, with each option including the name, specifications, price, and reasons for recommendation. The merchant can select one replacement option based on the results of communication with the user, or choose an alternative from the full menu. After confirming the replacement option, the merchant sends a product modification request to the server, which includes the target product identifier, the unfulfilled item identifier, and details of the replacement item. After receiving a product modification request, the server generates a product update record, replacing any unachievable items in the target product with the selected alternatives. Once the server completes the update, it pushes the updated product information to the user's device in real time via a push mechanism. Upon receiving the push, the user's device displays a notification that the product has been modified in the progress display area of ​​the chat page, along with the updated product content (such as the menu list and new total price). Simultaneously, the server synchronizes the modification results to the merchant's device, which displays a message indicating that the product has been successfully modified. The merchant can then continue preparing meals or providing services according to the updated product content.

[0197] For example, refer to Figure 12The system generates alternative dishes using intelligent objects, allowing users to choose between returning the dish and receiving a refund or confirming the replacement. Upon receiving a notification message about an abnormal product on the user's end, the system displays replacement options for the unachievable item in a dialog box. These replacement options are generated by the intelligent object based on the target product's content, the user's needs, and the merchant's available inventory. When generating replacement options, the intelligent object considers factors such as similarity to the original dish's flavor, price matching, user preference matching, and merchant recommendation priority, generating at least one replacement option for the user to choose from. If the user selects a replacement dish, they click the corresponding option and then click the "Confirm Replacement" button. In response to this confirmation, the user's end sends a product modification request to the server, including the identifier of the selected replacement item. Upon receiving the request, the server replaces the unachievable item in the original target product with the selected replacement item and updates the target product's total price and status. After the target product update is complete, the server pushes the updated product information to both the user's and the merchant's ends. The user's end displays a message indicating that the product has been successfully modified, and the merchant prepares the meal according to the updated product content. If a user clicks the "Refund / Cancel Dish" button, the user's app responds to this confirmation by sending a product modification request to the server. Upon receiving the request, the server removes the unachievable item from the target product and updates the total price and status of the target product. The merchant simultaneously receives the product update notification and can then prepare the remaining dishes according to the modified product details.

[0198] For example, in a retail scenario, a user places an order for a brand of noise-canceling headphones (black). After successful payment, the merchant discovers during the order picking process that black headphones are out of stock, with only white and blue headphones available. The merchant marks the product as unavailable on their end, and the server sends a notification message to the user about the unavailable product. The user can view alternative options on the chat page, such as alternative option one: the same white model at the same price, recommended with the reason "same model and configuration, white is versatile." The user selects alternative option one and clicks the confirm button. The server updates the product specification in the target product to white, the product status is updated, and the user receives a confirmation message.

[0199] In one alternative implementation, the edit control can be persistently displayed on the dialog page. Even if the user does not click the notification message in time, when the user actively opens the dialog page, the edit control can be displayed at the top of the page or next to the unachievable item, guiding the user to make the edit.

[0200] In one alternative implementation, refer to Figure 12 The modification control can be displayed in the progress card on the dialog page. In the specific implementation, the modification control is displayed next to the unachievable items on the progress card to guide the user to make the modification operation.

[0201] In one alternative implementation, the server can provide personalized recommendations based on smart objects when generating replacement solutions. The smart object can sort candidate replacements based on the user's needs provided in the chat window and the user's historical behavior data, prioritizing the replacement solution that best matches the user's needs. The smart object can also consider price matching principles when generating replacement solutions, prioritizing recommendations for alternatives with the same or similar prices to avoid negatively impacting user experience due to price differences.

[0202] In one optional implementation, the replacement options can support multiple rounds of selection. If the user is not satisfied with the initially generated replacement option, they can click the "Regenerate" button on the dialog page, and the server will call a smart object to generate a new replacement option. The dialog page can also provide a self-selection entry, allowing users to choose alternatives from the merchant's full menu or product list.

[0203] In one alternative implementation, when multiple unachievable items exist for the target product, the server can generate a combined replacement solution, packaging and displaying the replacement options for the multiple unachievable items. For example, in an offline store ordering scenario, if neither dish A nor dish B can be made, the server can generate a combined replacement solution, such as dish C and dish D as a single replacement solution, ensuring that the user completes all replacement operations at once, without needing to process them multiple times.

[0204] Understandably, after sending a product creation request, the client logged in with the primary account continuously listens for push notifications from the server. When the server detects that one or more items of the target product cannot be fulfilled, it uses smart objects to generate at least one alternative solution based on factors such as the target product, demand information, and available inventory at the current merchant. It then generates a notification message for the abnormal product, pushes this message to the terminal associated with the primary account, and sends the alternative solution data. Upon receiving the notification message, the client displays it to the user as an in-app pop-up, system notification, or message center entry. The dialog page displays modification controls for the unfulfillable items, including delete and replace controls, which are generated and displayed based on the alternative solution data. The user deletes the unfulfillable item or selects a replacement solution using the modification controls. The client then sends a product modification request to the server. The server responds to this request by removing the unfulfillable item from the target product, adding a replacement item, recalculating the total price, processing price differences, updating the target product status, and returning the modification results to the client. The client displays a success message and shows the updated target product details.

[0205] In this embodiment, when an anomaly occurs in the created target product, a timely and convenient processing channel is provided for the user, reducing the negative experience caused by the unavailability of the product and ensuring the smooth completion of the consumption process.

[0206] According to an embodiment of the present invention, referring to Figure 13 This invention provides a data interaction method involving a first user terminal (logged in with a first account), a second user terminal (logged in with a second account), and a server. Applications are installed on both the first and second user terminals, and a server-side application is deployed on the server. The data interaction method includes: 1. The first user terminal, in response to an interactive operation on a target item (such as touching an NFC tag or scanning a QR code), reads the target object identifier stored in the target item and sends a request for a dialogue page to the server. This request carries the first account identifier and the target object identifier. 2. After receiving the request for the dialogue page, the server obtains the corresponding dialogue page configuration information based on the target object identifier and returns the page data of the dialogue page to the first user terminal. 3. The first user terminal displays the dialogue page with the smart object based on the received page data. 4. The first account performs an interactive operation on the dialogue page, inputting demand information; the first user terminal, in response to this interactive operation, encapsulates the demand information into a product recommendation request and sends it to the server. 5. The server, based on the product recommendation request, inputs the demand information into the smart object; the smart object performs inference calculations based on the demand information to generate at least one recommended product information. 6. The server returns at least one recommended product information to the first user client. 7. The first user client displays the received recommended product information on the dialog page for the first account to browse and select. 8. In response to the interactive operation, the first user client confirms the target product information selected by the user. 9. In response to the modification operation on the target product information, the first user client displays the modified target product information. 10. In response to the user operation, the first user client sends a product creation request for the target product information. 11. The server creates the target product based on the target product information.

[0207] The data interaction method further includes: 12. After the first account inputs requirement information on the dialogue page, it can send the dialogue page to the second account as a share link through the sharing function set in the application. The share link carries a session identifier, a target object identifier, and the first account information. 13. In response to the second account's trigger operation on the share link, the second user terminal sends a request for the dialogue page to the server. This request carries the second account identifier, the session identifier, and the parameters from the share link. 14. After receiving the request, the server queries the existing requirement information of the current session based on the session identifier and returns the dialogue page data to the second user terminal; the second user terminal displays the dialogue page, through which the second account can input supplementary requirement information. 15. After the second account submits the supplementary requirement information, the second user terminal sends the supplementary requirement information to the server; the server associates the supplementary requirement information with the session identifier and updates the requirement information set in the session. The server inputs the requirement information set (including the requirement information and supplementary requirement information) into the smart object; the smart object performs reasoning calculations based on the requirement information set to generate at least one recommended product information.

[0208] The data interaction method further includes: 16. After the first account initially selects the target product information on the dialogue page, it can send the target product information to the second account as a share link by clicking the share button. 17. In response to the second account's trigger operation on the share link, the second user terminal displays the detailed content of the target product information on the dialogue page and provides interactive controls for adding, deleting, and replacing products. 18. In response to the user's operation, the second user terminal obtains supplementary modification information for the target product information and sends the supplementary modification information to the server or the first user terminal. The first user terminal displays the target product information modified based on the modification operation and the supplementary modification information.

[0209] It should be understood that although the steps in the flowcharts of the embodiments described above are shown sequentially according to the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some steps in the flowcharts of the embodiments described above may include multiple steps or multiple stages. These steps or stages are not necessarily completed at the same time, but can be executed at different times. The execution order of these steps or stages is not necessarily sequential, but can be performed alternately or in turn with other steps or at least some of the steps or stages in other steps. It is understood that the steps in different embodiments can be freely combined as needed, and all non-contradictory solutions formed by such combinations are within the scope of protection of this application.

[0210] Based on the same inventive concept, this application also provides an information processing apparatus for implementing the information processing method described above. The solution provided by this apparatus is similar to the implementation scheme described in the above method; therefore, the specific limitations in one or more information processing apparatus embodiments provided below can be found in the limitations of the information processing method described above, and will not be repeated here.

[0211] An apparatus according to an embodiment of the present invention, such as Figure 14 As shown, an information processing apparatus is provided, comprising:

[0212] The first display module 1402 is used to display a dialogue page with the smart object in response to interactive operations on target items related to the target object;

[0213] The first recommendation module 1404 is used to respond to a product recommendation request sent on the dialog page and display recommended product information generated by the smart object based on the product recommendation request on the dialog page.

[0214] The first processing module 1406 is used to respond to determining the target product information based on the recommended product information and send a product creation request for the target product information to the target object; the target product information is used by the target object to create the target product.

[0215] In the aforementioned information processing device, a dialog page is displayed in response to interactive operations on the target item. Based on the product recommendation request, a smart object is invoked to generate recommended product information. This allows users to quickly obtain recommendations tailored to their own and their companions' preferences without having to compare numerous options one by one, significantly reducing the decision-making burden and time cost during offline consumption and improving overall consumer satisfaction. By sending a product creation request to the target object, merchants can simultaneously obtain users' product needs, thereby preparing products in advance and improving operational efficiency and user experience.

[0216] An apparatus according to an embodiment of the present invention, such as Figure 15 As shown, an information processing apparatus is provided, comprising:

[0217] The second display module 1502 is used to display the object details page of the target object, which includes a product creation entry; in response to a trigger operation on the product creation entry, a dialogue page with the smart object is displayed;

[0218] The second recommendation module 1504 is used to respond to a product recommendation request sent on the dialog page and display recommended product information generated by the smart object based on the product recommendation request on the dialog page.

[0219] The second processing module 1506 is used to respond to determining the target product information based on the recommended product information and send a product creation request for the target product information to the target object; the target product information is used by the target object to create the target product.

[0220] According to an embodiment of the present invention, the dialog page includes at least one demand acquisition control; a first recommendation module 1404 or a second recommendation module 1504 is further configured to acquire demand information in response to a trigger operation on the at least one demand acquisition control; and to send a product recommendation request including the demand information on the dialog page in response to a confirmation operation on the demand information.

[0221] According to an embodiment of the present invention, the information processing apparatus further includes a modification module, which is configured to, in response to a modification operation on target product information in the recommended product information, display the modified target product information on a dialog page; and, in response to a confirmation operation on the modified target product information, send a product creation request for the modified target product information to a target object.

[0222] According to an embodiment of the present invention, the modified target product information is obtained by modifying the target product information based on modification information and supplementary modification information; the modification information is obtained in response to a modification operation of the target product information in the recommended product information by a first account, and the supplementary modification information is obtained in response to a modification operation of the target product information in the recommended product information by a second account, wherein the first account and the second account are different.

[0223] According to an embodiment of the present invention, the recommended product information is generated by an intelligent object based on the demand information in the product recommendation request and the supplementary demand information in the target recommendation request; the product recommendation request is sent by a first account on the dialogue page with the intelligent object, and the target recommendation request is sent by a second account on the dialogue page with the intelligent object, wherein the first account and the second account are different.

[0224] According to an embodiment of the present invention, the first display module 1402 is further configured to display the completion progress of the target product in a dialogue page with the smart object in response to a further interaction operation with the target item related to the target object.

[0225] According to an embodiment of the present invention, the second display module 1502 is further configured to display the completion progress of the target product in a dialogue page with the smart object in response to a trigger operation on a progress entry in the object details page.

[0226] According to an embodiment of the present invention, the information processing device further includes a product modification module, which is configured to display modification controls for the abnormal product on a dialog page in response to a notification message of an abnormal product sent by a target object; and to send a product modification request for the abnormal product to the target object in response to an interactive operation on the modification controls.

[0227] Each module in the aforementioned information processing device can be implemented entirely or partially through software, hardware, or a combination thereof. These modules can be embedded in or independent of the processor in a computer device, or stored in the memory of a computer device as software, so that the processor can call and execute the operations corresponding to each module.

[0228] In one exemplary embodiment, a computer device is provided, which may be a terminal, and its internal structure diagram may be as follows: Figure 16 As shown, the computer device includes a processor, memory, input / output interface, communication interface, display unit, and input device. The processor, memory, and input / output interface are connected via a system bus, and the communication interface, display unit, and input device are also connected to the system bus via the input / output interface. The processor provides computing and control capabilities. The memory includes non-volatile storage media and internal memory. The non-volatile storage media stores the operating system and computer programs. The internal memory provides an environment for the operation of the operating system and computer programs stored in the non-volatile storage media. The input / output interface is used for exchanging information between the processor and external devices. The communication interface is used for wired or wireless communication with external terminals; wireless communication can be achieved through Wi-Fi, mobile cellular networks, Near Field Communication (NFC), or other technologies. When the computer program is executed by the processor, it implements an information processing method. The display unit is used to form a visually visible image and can be a display screen, projection device, or virtual reality imaging device. The display screen can be an LCD screen or an e-ink screen. The input device of the computer device can be a touch layer covering the display screen, or buttons, trackballs, or touchpads set on the casing of the computer device, or external keyboards, touchpads, or mice, etc.

[0229] Those skilled in the art will understand that Figure 16 The structure shown is merely a block diagram of a portion of the structure related to the present application and does not constitute a limitation on the computer device to which the present application is applied. Specific computer devices may include more or fewer components than those shown in the figure, or combine certain components, or have different component arrangements.

[0230] In one exemplary embodiment, a computer device is also provided, including a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to implement the steps in the above-described method embodiments.

[0231] In one exemplary embodiment, a computer-readable storage medium is provided having a computer program stored thereon that, when executed by a processor, implements the steps in the above-described method embodiments.

[0232] In one exemplary embodiment, a computer program product is provided, including a computer program that, when executed by a processor, implements the steps in the above-described method embodiments.

[0233] Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. The computer program can be stored in a non-volatile computer-readable storage medium, and when executed, it can include the processes of the embodiments of the above methods. Any references to memory, databases, or other media used in the embodiments provided in this application can include at least one of non-volatile memory and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. By way of illustration and not limitation, RAM can take many forms, such as Static Random Access Memory (SRAM) or Dynamic Random Access Memory (DRAM). The databases involved in the embodiments provided in this application may include at least one type of relational database and non-relational database. Non-relational databases may include, but are not limited to, blockchain-based distributed databases. The processors involved in the embodiments provided in this application may be general-purpose processors, central processing units, graphics processing units, digital signal processors, programmable logic devices, quantum computing-based data processing logic devices, artificial intelligence (AI) processors, etc., and are not limited to these.

[0234] The technical features of the above embodiments can be combined in any way. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this application.

[0235] The embodiments described above are merely illustrative of several implementation methods of this application, and while the descriptions are specific and detailed, they should not be construed as limiting the scope of this patent application. It should be noted that those skilled in the art can make various modifications and improvements without departing from the concept of this application, and these all fall within the protection scope of this application. Therefore, the protection scope of this application should be determined by the appended claims.

Claims

1. An information processing method, characterized in that, The method includes: In response to interactive actions involving target items related to the target object, a dialogue page with the smart object is displayed; In response to sending a product recommendation request on the dialog page, the smart object displays recommended product information generated based on the product recommendation request on the dialog page. In response to determining target product information based on the recommended product information, a product creation request for the target product information is sent to the target object; the target product information is used by the target object to create the target product.

2. An information processing method, characterized in that, The method includes: Displays the object details page of the target object, which includes a product creation entry point; In response to a triggered operation targeting the product creation entry, a dialogue page with the smart object is displayed; In response to sending a product recommendation request on the dialog page, the smart object displays recommended product information generated based on the product recommendation request on the dialog page. In response to determining target product information based on the recommended product information, a product creation request for the target product information is sent to the target object; the target product information is used by the target object to create the target product.

3. The method according to claim 1 or 2, characterized in that, The dialog page includes at least one requirement retrieval control; the method further includes: In response to a trigger operation on the at least one requirement acquisition control, requirement information is acquired; In response to the confirmation operation for the requested information, a product recommendation request including the requested information is sent on the dialog page.

4. The method according to claim 1 or 2, characterized in that, The method further includes: In response to a modification operation on the target product information in the recommended product information, the modified target product information is displayed on the dialog page; In response to the confirmation operation for the modified target product information, a product creation request for the modified target product information is sent to the target object.

5. The method according to claim 4, characterized in that, The modified target product information is obtained by modifying the target product information based on the modification information and supplementary modification information; the modification information is obtained in response to the modification operation of the first account on the target product information in the recommended product information, and the supplementary modification information is obtained in response to the modification operation of the second account on the target product information in the recommended product information, wherein the first account and the second account are different.

6. The method according to claim 1 or 2, characterized in that, The recommended product information is generated by the smart object based on the demand information in the product recommendation request and the supplementary demand information in the target recommendation request; the product recommendation request is sent by the first account on the dialogue page with the smart object, and the target recommendation request is sent by the second account on the dialogue page with the smart object, wherein the first account and the second account are different.

7. The method according to claim 1, characterized in that, After sending a product creation request for the target product information to the target object, the method further includes: In response to a subsequent interaction with a target item related to the target object, the completion progress of the target item is displayed on the dialogue page with the smart object.

8. The method according to claim 2, characterized in that, After sending a product creation request for the target product information to the target object, the method further includes: In response to a triggered operation on the progress entry in the object details page, the completion progress of the target product is displayed in the dialogue page with the smart object.

9. The method according to claim 1 or 2, characterized in that, After sending a product creation request for the target product information to the target object, the method further includes: In response to the notification message for the abnormal product sent by the target object, the modification control for the abnormal product is displayed on the dialog page; In response to an interactive operation on the modification control, a product modification request for the abnormal product is sent to the target object.

10. An information processing device, characterized in that, The device includes: The first display module is used to display a dialogue page with the smart object in response to interactive operations on target items related to the target object; The first recommendation module is used to respond to sending a product recommendation request on the dialog page and display recommended product information generated by the smart object based on the product recommendation request on the dialog page. The first processing module is configured to, in response to determining target product information based on the recommended product information, send a product creation request for the target product information to the target object; the target product information is used by the target object to create the target product.

11. An information processing device, characterized in that, The device includes: The second display module is used to display the object details page of the target object, the object details page including a product creation entry; in response to a trigger operation on the product creation entry, a dialogue page with the smart object is displayed; The second recommendation module is used to respond to sending a product recommendation request on the dialog page and display recommended product information generated by the smart object based on the product recommendation request on the dialog page. The second processing module is used to respond to determining target product information based on the recommended product information and send a product creation request for the target product information to the target object; the target product information is used by the target object to create the target product.

12. A computer device comprising a memory and a processor, wherein the memory stores a computer program, characterized in that, When the processor executes the computer program, it implements the steps of the method according to any one of claims 1 to 9.

13. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 9.

14. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 9.

Images