A method, device, medium, and product for generating digital invitations.

Abstract

This specification provides a method, device, medium, and product for generating digital invitations. The method for generating digital invitations may include: determining dining needs information related to a group meal; based on the dining needs information, determining at least one matching target dish and an invitation template matching the desired dining atmosphere; embedding the target dish information into the invitation template to obtain a digital invitation containing the target dish information and corresponding to the desired dining atmosphere, for provision to the invitee. This eliminates the need for users to switch between multiple platforms or perform other operations, simplifying user operations and enabling users to generate invitations more efficiently and accurately.

Description

Technical Field

[0001] This specification relates to the field of computer technology, and in particular to a method, device, medium, and product for generating digital invitations. Background Technology

[0002] With the increasing frequency of social gatherings and dining events, e-invitations have become a common tool for organizers. Currently, mainstream e-invitation platforms offer fixed templates, supporting only the replacement of static elements such as text and images, resulting in significant content homogenization.

[0003] Therefore, how to enable users to generate invitations more efficiently and accurately is a technical problem that urgently needs to be solved. Summary of the Invention

[0004] In view of this, embodiments of this specification provide a method for generating digital invitations. One or more embodiments of this specification also relate to an electronic device, a computer-readable storage medium, and a computer program product for enabling users to generate invitations more efficiently and accurately.

[0005] According to a first aspect of the embodiments of this specification, a method for generating a digital invitation is provided, comprising: Determine dining needs information related to group meals, including dining atmosphere requirements; Based on the dining needs information, at least one target dish information is determined, as well as an invitation template that matches the dining atmosphere requirements; the invitation template includes at least one or more of the following: a background image with a preset visual style that matches the dining atmosphere requirements, background music, and invitation text information; The target dish information is embedded into the invitation template to obtain a digital invitation that contains the target dish information and corresponds to the dining atmosphere requirements, which is then provided to the invitee.

[0006] According to a second aspect of the embodiments of this specification, a method for generating a digital invitation is provided, comprising: In response to a trigger command used to generate a digital invitation, a requirements configuration page for configuring dining needs is displayed; Determine the user's specified dining requirements; the dining requirements include requirements for the dining atmosphere. Based on the dining needs information, a digital invitation is displayed that includes at least one target dish and corresponds to the dining atmosphere requirements; the target dish information is determined based on the dining needs information, and the digital invitation includes at least one or more of the following: a background image with a preset visual style that matches the dining atmosphere requirements, background music, and invitation text.

[0007] According to a third aspect of the embodiments of this specification, an electronic device is provided, comprising: A memory and a processor, the memory and the processor being connected via a bus; The memory is used to store computer programs / instructions, and the processor is used to execute the computer programs / instructions, which, when executed by the processor, implement the steps of the above-described method for generating digital invitations.

[0008] According to a fourth aspect of the embodiments of this specification, a computer-readable storage medium is provided that stores a computer program / instructions that, when executed by a processor, implement the steps of the above-described digital invitation generation method.

[0009] According to a fifth aspect of the embodiments of this specification, a computer program product is provided, including a computer program / instructions that, when executed by a processor, implement the steps of the above-described digital invitation generation method.

[0010] In one or more embodiments of this specification, target dish information matching the desired dining atmosphere is determined by parsing dining demand information related to group meals. This generates a dining invitation containing the target dish information and conforming to the desired atmosphere, effectively solving problems such as the separation of menus and invitations and static content in traditional tools. It eliminates the need for users to switch between multiple platforms or perform other operations, simplifying user operations and enabling users to generate invitations more efficiently and accurately. It also improves the organizational efficiency of dining events, enhances the immersive experience, and fosters a more social and emotional connection. Attached Figure Description

[0011] Figure 1 This is a schematic diagram illustrating an application scenario of a digital invitation generation method provided in one embodiment of this specification. Figure 2 This is a flowchart illustrating a method for generating a digital invitation letter according to one embodiment of this specification; Figure 3 This is a schematic diagram of a requirement configuration page provided in one embodiment of this specification; Figure 4 This is a schematic diagram of a digital invitation page provided in one embodiment of this specification; Figure 5 This is a flowchart illustrating a method for generating a digital invitation letter according to one embodiment of this specification. Figure 6 This is a schematic diagram of a target page provided in one embodiment of this specification; Figure 7 This is a schematic diagram of a digital invitation generation device provided in one embodiment of this specification; Figure 8 This is a schematic diagram of a digital invitation generation device provided in one embodiment of this specification; Figure 9 A structural block diagram of a computing device provided in one embodiment of this specification; Figure 10 This is a structural block diagram of an electronic device provided in one embodiment of this specification. Detailed Implementation

[0012] Many specific details are set forth in the following description to provide a full understanding of this specification. However, this specification can be implemented in many other ways than those described herein, and those skilled in the art can make similar extensions without departing from the spirit of this specification. Therefore, this specification is not limited to the specific implementations disclosed below.

[0013] The terminology used in one or more embodiments of this specification is for the purpose of describing particular embodiments only and is not intended to be limiting of the one or more embodiments of this specification. The singular forms “a,” “described,” and “the” as used in one or more embodiments of this specification and the appended claims are also intended to include the plural forms unless the context clearly indicates otherwise. It should also be understood that the term “and / or” as used in one or more embodiments of this specification refers to and includes any or all possible combinations of one or more associated listed items.

[0014] It should be understood that although the terms first, second, etc., may be used to describe various information in one or more embodiments of this specification, such information should not be limited to these terms. These terms are only used to distinguish information of the same type from one another. For example, first may also be referred to as second without departing from the scope of one or more embodiments of this specification, and similarly, second may also be referred to as first. Depending on the context, the word "if" as used herein may be interpreted as "when," "when," or "in response to a determination."

[0015] Furthermore, it should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, data stored, data displayed, etc.) involved in one or more embodiments of this specification are obtained through open-source datasets or public datasets that comply with their license agreements, or are obtained with full authorization from the relevant parties. Moreover, the collection, use and processing of the relevant data must comply with the relevant laws, regulations and standards of the relevant countries and regions, and corresponding operation entry points are provided for users to choose to authorize or refuse.

[0016] In one or more embodiments of this specification, AI (Artificial Intelligence) models can be used for product recommendations or to generate digital invitations. These AI models can include large-scale models, which are deep learning models with a massive number of parameters, typically containing hundreds of millions, tens of billions, trillions, or even tens of trillions of parameters. Large-scale models can also be called foundation models. They are pre-trained using large-scale unlabeled corpora to produce pre-trained models with hundreds of millions of parameters. Such models can adapt to a wide range of downstream tasks and have good generalization capabilities. Examples include Large Language Models (LLMs) and multi-modal pre-training models.

[0017] In practical applications, large models only require a small number of samples to fine-tune the pre-trained model before they can be applied to different tasks. Large models can be widely used in fields such as Natural Language Processing (NLP) and Computer Vision. Specifically, they can be applied to computer vision tasks such as Visual Question Answering (VQA), Image Captioning (IC), and Image Generation, as well as natural language processing tasks such as text-based sentiment classification, text summarization, and machine translation. The main application scenarios of large models include digital assistants, intelligent robots, search, online education, office software, e-commerce, and intelligent design.

[0018] First, the terms and concepts used in one or more embodiments of this specification will be explained.

[0019] An AI model (Artificial Intelligence Model), also known as an artificial intelligence model, refers to the mathematical or algorithmic structure used to implement artificial intelligence tasks. It learns patterns from data and uses them for reasoning, prediction, or decision-making. It can include traditional machine learning models such as linear regression, decision trees, and SVM (Support Vector Machine), as well as deep learning models such as CNN (Convolutional Neural Network), RNN (Recurrent Neural Network), and Transformer. It can also include large-scale speech models with a large number of parameters.

[0020] A digital invitation, also known as an electronic invitation, electronic invitation card, or electronic invitation, is a multimedia invitation created using digital technology and sent through electronic channels. It can be used for various events such as weddings, birthdays, business meetings, and exhibitions. It supports elements such as text, images, audio, video, background music, and dynamic effects, and can be shared or sent via instant messaging, SMS, email, web links, QR codes, etc. In one or more embodiments of this specification, a method for generating a digital invitation is provided. This specification also relates to an electronic device, a computer-readable storage medium, and a computer program product, which will be described in detail in the following embodiments.

[0021] Considering that recommendation engines or AI models that determine target dishes or digital invitations based on user-provided user demand information have a large number of model parameters, and that mobile terminals have limited computing resources, the digital invitation generation method provided in one embodiment of this application can be applied to, for example... Figure 1 The application scenarios shown are not limited to these. In, for example... Figure 1 In the application scenario shown, the recommendation engine or AI model can be deployed on server 10. Server 10 can connect to one or more client devices 20 via a local area network (LAN), wide area network (WAN), internet connection, or other types of data network. These client devices 20 may include, but are not limited to, smartphones, tablets, laptops, PDAs, personal computers, smart home devices, and in-vehicle devices. Client devices 20 can interact with users through a graphical user interface to implement the methods provided in the embodiments of this specification.

[0022] In one or more embodiments of this specification, the system comprising a client device and a server can perform the following steps: The client device can display a visual page, specifically a configuration page for configuring dining needs, where the user can specify the required dining needs information. The server can determine matching target dishes and an invitation template based on the user-specified dining needs information, thereby generating a digital invitation that matches the dining atmosphere. The client device can display the digital invitation generated by the server and can also provide the server with the user's actions on the digital invitation so that the server can execute the corresponding process. For example, based on the user's action of sending or sharing the invitation, the server can transmit the digital invitation via the network to the invitee's client device. If the client device can transmit the digital invitation via short-range communication, the sending process of the digital invitation can also be performed without the aid of a server.

[0023] It should be noted that, provided that the client device's operating resources can meet the deployment and operation conditions of the recommendation engine or AI model, the methods provided in one or more embodiments of this specification can be performed on the client device.

[0024] See Figure 2 , Figure 2 This diagram illustrates a flowchart of a method for generating a digital invitation letter according to an embodiment of this specification. From a programming perspective, the entity executing the process can be a program hosted on a server or recommendation system. It is understood that this method can be executed by any device, equipment, platform, or cluster of devices with computing and processing capabilities. Specifically, the method may include the following steps.

[0025] Step 202: Determine the dining needs information related to group meals, including the dining atmosphere requirements.

[0026] Dining demand information can represent a multi-dimensional data set related to group dining activities, and can be information used to describe the basic requirements or preferences for dining together. This information can include structured parameters, such as the range of people and budget; or it can include unstructured descriptions, such as natural language notes.

[0027] Dining atmosphere requirements can be used to characterize users' expectations of the emotional tone of a dining environment, such as warm, cheerful, or formal. These can exist in the form of keywords, tags, or natural language descriptions.

[0028] For example, the system can determine dining needs information through one or more methods. For instance, it can provide an interactive interface for users to select or set atmosphere tags, such as a cozy family dinner or a gathering with friends. Alternatively, users can input natural language descriptions, such as "I want a romantic candlelight dinner." Furthermore, the system can combine user historical behavior data, such as past dining records and saved dishes, to make intelligent inferences, and so on.

[0029] For example, a user plans to organize a birthday party with their best friend. In the client interface, they can select the atmosphere tag "relaxed and cheerful," or choose the gathering scenario as "birthday party," and can also enter a note such as "I hope there are bright colors and upbeat music." The system can map "relaxed and cheerful" to atmosphere requirement parameters, such as atmosphere type as casual party, color preference as bright, and music style as upbeat. It can also record the user's entered notes as supplementary information, thus confirming the dining requirements.

[0030] Figure 3 This is a schematic diagram of a demand configuration page provided in one embodiment of this specification. This demand configuration page is used by users to configure dining demand information, such as... Figure 3As shown, this page can include a configuration item 302 for configuring the number of diners, a budget configuration item 304 for configuring the budget amount, and a scenario type configuration item 306 for configuring the dining scenario. Dining requirement information includes the number of diners, budget amount, and dining scenario type information. The number of diners can represent the number of participants in the gathering, and can be a specific number, such as "8 people," or a range, such as "6-10 people," which can be used to assist in planning food portion sizes and cost estimation. Users can specify the number of diners by selecting or filling in the information. To accurately provide users with target dishes and digital invitations that match their dining needs, the requirement configuration page can also include configuration items for specifying whether children or elderly people are participating, or the number of children or elderly people, or users can add notes using natural language.

[0031] The budget amount can represent a user-defined cost reference value or range, such as "100 yuan per person" or "total budget of 600 yuan". It can be used as an economic constraint parameter in the menu selection logic.

[0032] Dining scenario type information can represent a classification of the nature of the gathering, such as "birthday party," "business meeting," or "holiday family dinner." This can exist as preset tags or semantic codes and can be used to link the menu style library and the atmosphere template library. Different dining scenario types correspond to different dining atmospheres, and the aforementioned dining atmosphere requirements can also be represented using dining scenario types. Dining scenario types can be predefined scenarios available for user selection in the configuration page, such as... Figure 3 The scenarios shown can be birthday parties, business banquets, camping vacations, anniversaries, friend gatherings, New Year's Eve dinners, etc., or they can be user-defined scenarios, such as team building activities.

[0033] Optional, such as Figure 3 As shown, the requirements configuration page can also include a cuisine configuration item 308 for configuring the type of dish series. The dining requirements information can also include the required cuisine information. The requirements configuration page can include a configuration item for selecting the cuisine, from which users can select one or more cuisines. In practical applications, this cuisine information may not be a required field, and users may choose not to select a cuisine; alternatively, the cuisine information may be a required field, and the system can only proceed with the subsequent steps of determining the target dish after the user selects a cuisine.

[0034] Optionally, the dining requirements information can also include information representing the attributes of the dishes, such as classifying the dishes according to their serving temperature and cooking method, dining process and function, or kitchen division of labor, such as classifying them into attribute types like hot dishes, cold dishes, desserts, and drinks. The requirements configuration page can include configuration items for dish attributes, allowing users to select the quantity or proportion of dishes with a certain attribute.

[0035] Optionally, the dining request information may also include user-specified dish information, which will be included in the target dishes subsequently determined. For example, the request configuration page may include dish configuration items for users to select or fill in one or more dishes they want to use for the group meal. Users can select or fill in the dish name, which will be included in the target dishes.

[0036] By clearly defining the dining atmosphere requirements, an emotionally-oriented data foundation is provided for subsequent steps, which helps reduce deviations in generated content caused by ambiguous requirements and improves user satisfaction with the generated results.

[0037] Step 204: Based on the dining needs information, determine at least one matching target dish information and an invitation template that matches the dining atmosphere requirements.

[0038] The invitation template may include at least one or more of the following: a background image, background music, and invitation text information, all of which have a preset visual style that matches the desired dining atmosphere.

[0039] In practical applications, based on dining needs information, matching algorithms, rule engines, or machine learning models can be used to filter out target dishes and invitation templates that meet the criteria.

[0040] Target dish information refers to a set of dish data selected from a dish database that matches the dining needs. It can include information on one dish or multiple dishes. The dish information may include the dish name, or it may include images, brief descriptions, flavor tags, etc. For example, a dish recommendation model can be invoked, inputting the dining needs information to obtain a list of matching dishes.

[0041] Alternatively, dishes can be recommended based on user preferences. Optionally, the method in one or more embodiments of this specification may further include: determining dining preference information associated with the dining participant. Correspondingly, determining at least one matching target dish information based on the dining demand information may include: combining the dining demand information and the dining preference information, and using an intelligent model to determine at least one matching target dish information.

[0042] Dining participants can refer to individuals or groups participating in a dining event, specifically including at least one of the inviter and / or the invitee.

[0043] Meal preference information can represent structured or unstructured data related to participants’ eating habits, taboos, and preferences, such as foods to avoid, taste preferences, and allergen information.

[0044] For example, the system may obtain preference information through one or more means, such as guiding the invitee or inviter to fill out a preference form during the invitation process; or calling historical order data authorized by the user, such as dietary restrictions marked in past order records; or inferring preferences through publicly available information on social platforms.

[0045] Optionally, dining preference information can be determined based on at least one of the user's favorite dishes or added-to-cart dishes. For example, dishes that the user has purchased multiple times can be used as one of the target dishes, or the user's preferences for flavors, cuisines, etc., can be inferred from their favorite, added-to-cart, or already purchased dishes, and dishes can be recommended to the user based on this preference information.

[0046] Optionally, the dining preference information can also be determined based on user-configured preference information; the preference information includes at least one of the following: information indicating cooking frequency, information indicating dietary restrictions, information indicating dietary needs, information indicating food preferences, information indicating stove type, and information indicating the role of the diner.

[0047] For example, before generating a digital invitation, the system can guide users to configure their preferences. For instance, the client can display a preference requirements page, which may contain multiple configurable items. Users can configure their preferences using checkboxes, radio buttons, sliders, etc.

[0048] For example, the page's configuration options can include a setting for cooking frequency, representing the user's cooking habits over time. Users can choose from different cooking frequencies such as daily, only on weekends, occasionally, or never cook, based on their individual circumstances. Alternatively, users can customize their cooking frequency information. This dimension can influence the complexity of recommended dishes, the number of recommended products, and the level of detail in the tutorials. If a user cooks daily, the recommended products for frequently used items can be more numerous than needed to facilitate continued use; or the target page can prioritize displaying more complex dishes. Conversely, if a user chooses not to cook, indicating a beginner, the tutorials need to be more detailed and thorough, or key steps should be repeatedly emphasized; or the target page can prioritize displaying less complex dishes.

[0049] For example, the configuration options can include dietary restrictions, indicating foods the user dislikes. Users can choose foods they cannot eat, such as one or more of cilantro, scallions, ginger, garlic, and chili peppers. Users can also leave these options blank if they have no dietary restrictions, or they can customize their dietary restrictions. When determining the detailed list of ingredients or recommending products, if any of the required ingredients contain foods the user dislikes, these can be replaced with other foods to meet the user's needs.

[0050] For example, the configuration options can include items representing dietary needs, as well as items representing functional or health goals. Users can choose one or more options such as lactose intolerance, low-fat and sugar control, cooling and health maintenance, and gastrointestinal regulation. Users can also leave these options blank if they have no specific dietary needs. When determining ingredient details or recommended products, ingredients can be substituted based on the user's dietary needs. Alternatively, cooking steps or time can be adjusted according to the user's dietary requirements.

[0051] For example, the configuration options for requirements can include settings indicating ingredient preferences, representing the food the user likes. For instance, the user can choose their preferred ingredients from beef, chicken, seafood, leafy greens, etc. When determining the ingredient details for a dish, the proportion of the user's preferred ingredients can be increased based on this preference information, so that the prepared dish better matches the user's preferences, or dishes with the user's preferred ingredients can be recommended.

[0052] For example, the configuration items for the requirements can include configuration items that indicate the type of stove, representing the hardware devices the user owns, such as only having an induction cooker, having an air fryer, having a steam oven, etc. The system can recommend dishes to the user based on the stove they own, or generate corresponding tutorials based on the stoves they own.

[0053] For example, the configuration options can include settings representing the diner's role, such as baby food, elderly meals, or meals for pregnant women. This information can be used to determine the texture, saltiness, and nutritional balance of the food, and then to determine detailed ingredient information or recommend products or dishes.

[0054] The content of the configuration items can also be customized by the user, such as the user manually editing the specific content of the configuration items, which is not limited here.

[0055] Intelligent models can represent trained machine learning models, such as collaborative filtering models and deep learning recommendation networks, used to learn the mapping relationship between dish features and multi-dimensional needs to make dish recommendations. Alternatively, intelligent models can also be generative models, such as large language models, which can combine a dish knowledge base to recommend dishes that meet user needs. Intelligent models can combine dining needs information and dining preference information to recommend target dishes that match the atmosphere of the gathering and satisfy the user's dining preferences.

[0056] For example, when organizing a family dinner, if one member indicates "seafood allergy" and another member prefers "light diet", the system can use this information to exclude seafood dishes or reduce the proportion of seafood dishes in the subsequent dish selection, and give priority to recommending dishes cooked by steaming or boiling.

[0057] For example, if the desired atmosphere for a gathering is a "spicy hot pot party" and the participants have a preference for "sensitive stomachs", the intelligent model can reduce the weight of high-oil and high-spicy dishes, recommend a mushroom soup + mildly spicy double-flavor hot pot base, paired with easily digestible tender meat slices and vegetable platters, and can also include phrases such as "the hot pot base has been mildly adjusted" in the invitation text.

[0058] By integrating multi-dimensional demand information through intelligent models, the accuracy and adaptability of menu recommendations can be improved. This allows the generated digital invitations to not only convey the emotional tone of the event but also meet individual needs, making them more valuable for practical application.

[0059] Invitation templates can represent a pre-defined framework for digital invitations, which may include replaceable placeholder areas, such as a food display area or a background image area, or fixed elements, such as a layout. The templates can pre-set reference paths or parameters for visual style background images, background music, invitation text, and other materials associated with specific atmosphere requirements. Background images, background music, and invitation text information can respectively represent the image materials, audio materials, and text content used in the template to create the desired atmosphere.

[0060] For example, when the desired dining atmosphere is a "warm family gathering," the system can filter dishes with flavor tags such as "homestyle" and "warmth" from the menu, such as braised pork and dumplings, as target dishes. It can also match preset "family warmth" templates, which may include warm-toned background images, such as a fireplace scene; soothing background music, such as soft background music; and heartwarming text, such as "The taste of home, a warm gathering." If the current weather is winter and snowy, the system can subtly adjust the background image to a snowy fireplace scene to reflect environmental adaptability.

[0061] One approach is to analyze and understand dining needs information or extract keywords to determine atmosphere keywords that represent the dining ambiance. Then, these atmosphere keywords are used to match invitation templates from a template library, selecting those that match the dining needs information. Template matching can employ methods such as keyword matching and vector similarity calculation. In the matched templates, background images, music, text, and other elements are pre-set to correspond to the atmosphere requirements.

[0062] For example, an atmosphere knowledge base can be pre-built, associating different visual styles of images, background music, and invitation templates for various scenarios. The visual styles of the images can include warm tones, fresh, retro, and other atmospheric images, with one or more background images for each type. The background music can include different types of music such as jazz, guzheng, and light music, with one or more pieces for each type. The invitation templates can contain invitation messages of different styles. In practical applications, the invitation messages can also be associated with the target dish. For example, the invitation message can include highlighting information about the dish; if the target dish includes "braised pork belly with preserved mustard greens," the invitation message could include information such as "We have prepared our secret-recipe braised pork belly with preserved mustard greens for you."

[0063] As another implementation, the invitation template can be an invitation template generated using a large model that matches the dining needs information. Optionally, in one or more embodiments of this specification, determining an invitation template that matches the dining atmosphere requirements based on the dining needs information may include: providing the dining needs information to a generative model to obtain an invitation template generated by the generative model that matches the dining atmosphere requirements.

[0064] Generative models can be deep learning architectures with content creation capabilities, such as diffusion models and multimodal large models, which can generate original visual, textual, or layout data based on input conditions.

[0065] For example, the system can construct structured prompts from dining needs information, such as the atmosphere keyword "retro" and the scene type "birthday party," and input them into a multimodal generative model. This model can then generate background images, text snippets, layout parameters, etc., to obtain an invitation template.

[0066] By dynamically creating invitation templates using generative models, the style and semantic fit of the templates can be expanded, the visual uniqueness and emotional accuracy of the generated digital invitations can be improved, and users can be provided with more creative freedom for personalized expression.

[0067] In practical applications, the target dishes and dining needs information can be provided to the generative model. The generative model can then combine features such as the quantity or style of the target dishes to generate a digital invitation that matches the target dishes and dining needs.

[0068] Step 206: Embed the target dish information into the invitation template to obtain a digital invitation that contains the target dish information and corresponds to the dining atmosphere requirements, for use in providing to the invitee.

[0069] Embedding can represent inserting data content of the target dish information, such as dish name, pictures, etc., into the specified placeholder area of ​​the invitation template and completing the format adaptation process.

[0070] A digital invitation is an electronic information carrier generated by the system, containing information about the target dish and atmosphere. Its format can be HTML, JSON, image sequences, etc., and it is used for sharing through digital channels, such as via link sharing or file transfer, to the invitee. The digital invitation can be visually displayed on the client device.

[0071] Figure 4 This is a schematic diagram of a digital invitation page provided in one embodiment of this specification. Figure 4 As shown, assuming a user wants to host a wedding anniversary dinner, a digital invitation containing wedding anniversary elements can be generated. The page that generates the digital invitation can display its style, including recommended target dishes information 402, a background image matching the dinner atmosphere 404, music controls 406 for playing and pausing music, and invitation text information 408. The page can also include a sending control 410 for sending the digital invitation. To facilitate users purchasing the items needed for the dishes included in the invitation, the page can also include a control 412 for adding the corresponding items to their shopping cart.

[0072] The invitee indicates that the user who generated the digital invitation will send the digital invitation to the user, and the invitee can view the received digital invitation through the client device.

[0073] For example, the system can parse the structure of the invitation template, locate the embedded area for menu information, such as the menu display area; then, it fills the fields in the target menu information, such as the menu name, into the corresponding positions according to the template's required format. If the template supports dynamic interaction, such as clicking to expand details, it can generate corresponding interactive control code. The filled template is then rendered into a shareable file format, such as generating an H5 page or image sequence, and generating an access link or file package.

[0074] Continuing with the family dinner example above, the system can embed dish information such as "braised pork" and "dumplings" into the invitation template. The template's dish area will display the dish names sequentially, or alternatively, images or recommended descriptions. The text area can display phrases like "The Taste of Home," and background music can be set to clickable soft music. The generated digital invitation can be an H5 page; invitees can open it to view the dishes, play background music, or expand the page through interactive elements to see more dish information.

[0075] The above Figure 4 This illustrates the generated digital invitation displayed on the inviting party's client device. The target dish information displayed on this page can include the name of the target dish, the approximate time required to prepare the dish, the corresponding price, and the total price of the dish.

[0076] In practical applications, the content displayed in the digital invitation received by the invitee can be identical to the content displayed in the invitation from the inviter. This includes information about the target dish, background image, background music, and invitation text. The dish information may also include the dish's name, preparation time, price, and total price. Alternatively, the content displayed in the digital invitation may not be entirely identical to the content displayed by the inviter. For example, the target dish information in the digital invitation may include the dish's name, but may not include information about preparation time, price, or total price. The background image, background music, invitation text, dish names, and the order of the dishes can be the same.

[0077] To further enhance the atmosphere of the gathering, the invitation template can be fine-tuned based on environmental information to obtain a digital invitation that better matches the atmosphere. Optionally, the method in one or more embodiments of this specification may further include: adjusting the invitation template based on environmental information to obtain a target invitation template that conforms to the environmental information; the environmental information includes the local time information and / or weather information of the location of the dining participants. Correspondingly, embedding the target dish information into the invitation template may include: embedding the target dish information into the target invitation template.

[0078] In this scenario, the participant can be the party generating the digital invitation, also known as the inviter. The user's location or local time can be determined based on their client device. Alternatively, the user can set the time and location of the meal; the local time information can represent the user's chosen time, and weather information can be used to obtain environmental information. Alternatively, the participant can be the party receiving the digital invitation, also known as the invitee. Before generating the digital invitation, the inviter can fill in the invitee's information, such as the invitee's location, meal time, and meal location.

[0079] For example, the system can obtain the location information of the participants through user authorization, call the meteorological access interface and time service to obtain environmental data, and then adjust the template parameters according to the preset rule base, such as warm color background corresponding to rainy days, or lightweight adaptation model, to obtain a template instance adapted to environmental information, whose visual or textual elements have semantic association with the environmental state.

[0080] For example, suppose the dinner is scheduled for an evening during the rainy season in a certain location. If the system detects light rain and a temperature of 22°C, the template background image can be replaced with an illustration of warm light coming from a window and light rain outside. The text can be slightly adjusted to phrases like "Light rain soothes the heart, delicious food warms the heart," and the background music can be a soft rain sound effect. If the participants are located in multiple locations, the template can be adapted based on the location of the main inviter or the locations of most participants.

[0081] In practical applications, users can also customize or select text information to describe the dining activity, such as naming the gathering or setting a theme. To better suit user needs, the generated digital invitation may include at least a portion of the text information set by the user to describe the dining activity. Optionally, the method in one or more embodiments of this specification may further include: determining the text information provided by the user to describe the dining activity; determining target text information based on the text information; the target text information being at least a portion of the invitation text information.

[0082] Text information describing the dining event can represent statements entered by the user in natural language that express the theme, emotions, or details of the gathering. Target copy information can represent text snippets extracted from, rewritten, or directly used from the user's text to fill in the invitation copy area.

[0083] For example, the system can provide a text input box or a speech-to-text entry point in the interactive interface, or the user can modify text information such as the theme of the gathering; then, it can perform natural language processing on the text information provided by the user, extract keywords or perform sentiment analysis to mark core elements, and can also generate concise copy through computer models, or directly extract key sentences from the user's text; the processing results are integrated with the template's preset copy framework, or the copy in the template is modified to form the target copy information.

[0084] By converting user text into invitation copy, the generated digital invitations can better meet user needs and help enhance user acceptance of the generated results.

[0085] To make the generated invitation more tailored to the user's needs, the user can also modify the system's recommended dishes. Optionally, the method in one or more embodiments of this specification may further include: determining the updated dish information based on the user's editing operation on the target dish; the editing operation includes at least one of deleting a dish, increasing the number of servings of a dish, and decreasing the number of servings of a dish.

[0086] Correspondingly, embedding the target dish information into the invitation template to obtain a digital invitation that contains the target dish information and corresponds to the dining atmosphere requirements can include: embedding the updated dish information into the invitation template to obtain a digital invitation that contains the updated dish information and corresponds to the dining atmosphere requirements.

[0087] The "edit" operation represents a user's modification command initiated through the interactive interface for a selected target dish. The "delete" operation represents an instruction to remove a specific dish from the target menu. The "increase or decrease" operation represents an instruction to adjust the order quantity of a single dish, such as increasing the number of "Kung Pao Chicken" portions from 1 to 2.

[0088] For example, the client interface can display a list of target dishes and portion control, such as "+ / -" buttons, delete icons, etc.; then listen for user operation events, such as clicking delete, adjusting portion, etc.; then update the dish data structure, such as removing deleted dishes, modifying the portion number field, etc., to obtain the updated dish information.

[0089] For example, the client interface displays the target dishes and operation controls in a visual list, such as delete icons and buttons to increase or decrease the quantity; it listens for user interaction events, such as clicks and swipes, and updates the dish data structure based on these events to obtain the updated dish information. Optionally, it can also provide operation undo or redo functions. Optionally, if a critical change is detected, such as deleting a highly relevant dish or a significant difference from the budget, the user can be prompted for confirmation or an alternative can be recommended.

[0090] The specific page for performing editing operations can be set according to actual needs. As one implementation, before embedding the target dish information into the invitation template, a menu page containing recommended target dish information can be generated first. On this page, users can edit the dishes; this editing is optional, and users can choose whether to edit based on their needs. After the user confirms or generates the invitation on this page, the system can embed the user-defined target dish information into the invitation template to obtain the required digital invitation. As another implementation, before sending the digital invitation to the invitee, the user can edit the dish information displayed in the digital invitation to obtain updated dish information, thus obtaining a digital invitation containing the updated dish information.

[0091] To further enhance the atmosphere of a gathering, users may want to cook the dishes themselves. To simplify the preparation process, the system can recommend the necessary ingredients for the target dish and support user purchases. This eliminates the need for users to manually determine the exact ingredients, further improving the dining experience. Optionally, the method in one or more embodiments of this specification may further include: determining the ingredient details of the target dish represented by the target dish information; the ingredient details include the category and quantity of the required ingredients; based on the ingredient details, selecting the minimum stock unit (SKU) and quantity information of the corresponding ingredients from an associated product information database, and generating recommended product SKU information so that users can perform a purchase operation based on the recommended product SKU information.

[0092] The target dish information may include at least one of the following: the name of the target dish and an image of the dish. The ingredient details may include information on the ingredients required to prepare the target dish. The ingredient category may indicate the specific type of ingredient, such as "rice," "cabbage," "pork," or "green beans." The required quantity information may be in units of weight, volume, or number, such as "1" egg or "500g" of cabbage.

[0093] A Stock Keeping Unit (SKU), also known as an inventory unit, stock unit, goods storage unit, inventory preservation unit, unitized unit, single item, or variety, represents an indivisible sales unit. In practical applications, based on the task, it may also be referred to as the smallest retail unit, smallest sales unit, smallest management unit, or inventory counting unit. Each product can have a unique SKU number. For a given product, if any attribute—brand, model, configuration, packaging capacity, unit, shelf life, use, price, or place of origin—differences exist between it and other products, its SKU number may also differ.

[0094] A product information database can represent a database or data structure that stores product data, including information such as product name, specifications, price, and inventory. A linked product information database represents a product information database that has established a data connection or mapping relationship with the current system. The product information database serves as a bridge connecting food demand and commercial transactions, ensuring the system can query product availability and prices in real time through association. Association methods can include one or more of the following: a proprietary e-commerce database, a third-party platform API (Application Programming Interface), or a partner merchant database, ensuring the reliability and timeliness of the data source.

[0095] For example, a connection to the product information database can be established through API interfaces, direct database connections, or data synchronization. Once the ingredient details are generated, the database can be queried to find matching SKUs, such as matching "rice" with "Wuchang rice 5kg pack," to obtain the current price, inventory status, calculate the purchase quantity, and generate a recommendation list.

[0096] For example, matching can be based on standardized classification codes. For instance, a unified classification system for ingredients and SKUs can be established, comparing the category field in the ingredient details with the classification code in the SKU metadata to determine the recommended SKU information. Alternatively, multi-dimensional textual semantic matching can be used. The categories of the required ingredients in the ingredient details can be used as keywords for distance similarity and deep semantic understanding, matching the recommended SKU information from the product information database. Furthermore, matching can be performed from the product information database based on the required quantity of the ingredients, selecting products that are greater than or equal to the required quantity and close to the required quantity.

[0097] In practical applications, a single ingredient can correspond to a recommended product SKU. Alternatively, to better meet user needs, multiple product SKUs that fulfill the functions of a single ingredient can be provided, allowing users to select the desired product. For example, for the ingredient "soy sauce," multiple brands such as Brand A and Brand B can be offered for users to choose from.

[0098] In one or more embodiments of this specification, a precise mapping from food ingredients to finished products is achieved by associating with a product information database. This ensures that recommended products are actually available for purchase, improving conversion rates, and also guarantees the real-time availability of price and inventory information. Furthermore, through precise mapping and intelligent quantity calculation, the user's purchasing decision time can be shortened, eliminating the need for manual switching between multiple platforms and improving user experience.

[0099] In practical applications, users may have a preference for certain ingredients or dietary restrictions on them. To better meet users' actual needs, the method in one or more embodiments of this specification may further include: determining the dining preference information associated with the dining participants.

[0100] The aforementioned determination of the ingredient details for the target dish information may include: retrieving the dish preparation knowledge corresponding to the target dish information; based on the dish preparation knowledge, determining the standard ingredient list information required to prepare the target dish represented by the target dish information; and adjusting the quantity and / or category of ingredients in the standard ingredient list information in conjunction with the dining preference information to determine the ingredient details information required to prepare the target dish that conforms to the dining preference information.

[0101] Meal preference information can represent structured or unstructured data related to participants’ eating habits, taboos, and preferences. For details, please refer to the description in the aforementioned embodiments, which will not be repeated here.

[0102] A knowledge base can be a pre-configured database for storing recipe-making knowledge, or it can be one or more data sources that provide recipe-making knowledge. The knowledge in the knowledge base can be publicly available knowledge or private data that is authorized for use. Recipe-making knowledge can represent a collection of knowledge related to recipe preparation. For example, it can include information such as standard recipes, cooking steps, and baseline quantities.

[0103] Standard ingredient lists can be based on information from a knowledge base, without taking into account users' personalized needs. For example, an ingredient list from a restaurant's recipe, or an ingredient list for a specific dish publicly available on a social network.

[0104] By employing a two-step processing logic of "standardization first, then personalization," the core flavor of the recipe can be preserved while adapting to individual needs. First, authoritative or standard benchmark data is obtained as an anchor point, and then user preference variables are added for correction. This ensures both the scientific nature of the cooking and flexibility, avoiding logical errors that might result from direct generation.

[0105] For example, the system can first search the knowledge base using the name of the target dish as an index to extract the standard recipe. Then, it reads the user's personalized cooking information, executes calculation logic, adjusts the quantity of ingredients in the standard recipe, or adjusts the variety of ingredients according to the user's preferences, and finally generates detailed ingredient information containing the adjusted data.

[0106] For example, if the target dish is "braised pork belly," the knowledge base retrieves a standard list of "500g pork belly, 30g sugar," which is a serving size for two people. If the user's personalized information shows "sugar control" and "for 3 people," the system can adjust the sugar to 10g or use a sugar substitute, and adjust the pork belly to 750g, generating the final ingredient list instead of directly recommending the original standard amounts.

[0107] When making product recommendations, user preference information can also be considered. The method in one or more embodiments of this specification may further include: determining the dining preference information associated with the dining participant. The above-mentioned selection of the minimum stock unit (SKU) and quantity information corresponding to the ingredients in the ingredient details information from an associated product information database based on the ingredient details information of the target dish may include: combining the dining preference information and the ingredient details information to select the minimum stock unit (SKU) and quantity information corresponding to the ingredients in the ingredient details information from an associated product information database.

[0108] For example, SKUs can be initially screened based on ingredient details, followed by personalized filtering. For instance, dietary conflict detection can be performed by iterating through candidate SKUs; SKUs containing user dietary restrictions are removed from the candidate set. Similarly, for equipment incompatibility filtering, if an SKU is marked "Oven Required" but the user has configured "No Oven," it is marked as low priority. If multiple SKUs matching the same ingredient exist within the initially filtered SKUs, personalized weighted sorting can be applied. This can be done using a scoring model combining ingredient matching degree, sales volume, rating, user brand preference matching, and packaging specification compatibility. Afterward, the minimum inventory unit SKU corresponding to the required ingredient and the purchase quantity information are determined. Alternatively, the dietary conflict detection can be omitted; if dietary conflict detection is performed before generating ingredient details, the resulting ingredient details will not include ingredients the user avoids.

[0109] For example, a recipe might require "1000g of potatoes," and the standard recommendation would be "1 bag of 2kg potatoes." However, if a user's personalized information shows that they "have only made stew once recently" and "prefer fresh ingredients," the system can adjust its strategy accordingly, recommending "2 boxes of 500g net potatoes." This satisfies both the total quantity requirement and the user's personalized habit of ordering small portions frequently and prioritizing freshness, rather than simply matching large packages.

[0110] For example, a user's personalized cooking information includes: brand preference "Brand A", peanut allergy, and 2 cooks; the target dish's ingredients include: 150ml light soy sauce and 20g crushed peanuts. The candidate light soy sauces include 300ml of Brand A, 500ml of Haitian light soy sauce of Brand B, and 300ml of light soy sauce of Brand C; the nut mixture includes 50g of plain crushed peanuts and 50g of crushed cashews. Through personalized filtering, crushed peanuts are filtered out because they conflict with the user's dietary restrictions; the light soy sauces have no direct conflict and can be included in the ranking. Then, a weighted ranking is performed, and Brand A's light soy sauce matches the user's preferences, so it receives a higher score. Afterwards, the purchase quantity and alternative recommendations are made, confirming the use of 300ml of Brand A's light soy sauce and using crushed cashews instead of crushed peanuts. The client can then display a purchase page containing 300ml of Brand A's light soy sauce and 50g of crushed cashews.

[0111] By integrating users' personalized cooking needs into the product selection process of the supply chain, the product recommendation has become more refined and dynamic, effectively resolving the contradiction between standardized product specifications and personalized cooking needs, significantly reducing users' decision-making costs and food waste rate, and improving shopping conversion rate.

[0112] In practical applications, pre-trained computer models can be used in conjunction with the target dish and the user's personalized cooking information to determine the detailed ingredient information. For example, a large speech model can be used in conjunction with RAG (Retrieval-augmented Generation) technology to generate the detailed ingredient information for the target dish that meets the user's needs.

[0113] To facilitate users in cooking dishes, the method in one or more embodiments of this specification may further include: generating a tutorial for making the target dish based on the ingredient details.

[0114] The tutorial information can be represented as a dynamic guidance data stream for a "watch and do" scenario design. It is dynamically generated, interactive cooking guidance content bound to the user's personalized replication plan. This tutorial information is matched with each ingredient in the determined ingredient list, and the dosage and step prompts in the tutorial reflect the determined personalized ingredient data.

[0115] For example, the system can extract key parameters from the ingredient list, such as the weight of the main ingredient, the brand of the auxiliary ingredients, and the substitute ingredients, and fill these parameters as variables into the preset teaching script or video metadata. For instance, if the list shows that the user purchased "500g of pre-cut vegetables," the voice prompt in the tutorial can be adjusted to "Please pour in the whole package of ingredients" instead of "Please weigh 500g." If the user selected "low-sodium soy sauce," the seasoning prompt in the tutorial can be updated to "Add low-sodium soy sauce," and the subsequent salt addition suggestions can be adjusted. For example, if the target dish is "Kung Pao Chicken," and the ingredient list shows that the user replaced "peanuts" with "cashews" due to dietary restrictions, and purchased "200g of chicken breast," the generated follow-up tutorial will display a visual or text prompt to "Add cashews" at the corresponding step. It can also add a special reminder for "quick stir-fry" to address the characteristic that "chicken breast is easy to overcook," instead of playing the original video clip using chicken thigh meat and peanuts.

[0116] Traditional video tutorials are often recorded based on standard recipes, which cannot be adapted to the actual quantity or type of ingredients purchased by the user. This forces users to make calculations or judgments themselves when following the instructions, increasing their cognitive load. In one or more embodiments of this specification, the solution injects specific "ingredient details" into the tutorial generation logic, generating a customized tutorial that matches the user's actual ingredients. This eliminates the information gap between standard instruction and personalized preparation, reducing the user's calculation costs and operational error rate during the cooking process, and improving the success rate of replication.

[0117] The tutorial information includes step-by-step instructions for making the target dish; these step-by-step instructions may include at least one of video information, image information, and text information.

[0118] Step-by-step instructions can represent guidance data that breaks down the entire cooking process into discrete units. For example, making braised pork belly may include steps such as cutting pork belly into chunks, caramelizing sugar, and simmering over low heat. For each step, information in at least one format, such as video, images, or text, can be configured.

[0119] In practical applications, tutorials can include various forms of information. For example, a tutorial might include a step-by-step explanation of the preparation process of the target dish using text and images. This explanation could be played at a preset speed, accompanied by corresponding audio or background music tailored to the user's preferences. Alternatively, a tutorial could include a video demonstrating the preparation of the target dish. This video could contain subtitles or display reminders for key steps.

[0120] For example, the system can parse the preparation process of a target dish into a sequence of steps (such as: preparing ingredients, sautéing, stir-frying, reducing sauce, etc.). For each step, it calls up the corresponding short video clip, high-definition images of key steps, and concise text descriptions. The user terminal client can support switching view modes or synchronously highlighting the key text points of the current step while the video is playing.

[0121] In one or more embodiments of this specification, users can achieve a one-stop experience of selecting dishes and purchasing ingredients on the same platform, and can also obtain cooking tutorials that match the ingredients used, which is more conducive to users replicating dishes and improving the success rate of cooking. Optionally, the cooking tutorials may include reminders on the heat level during the cooking process.

[0122] This reminder message can be a proactive prompt embedded in the tutorial, targeting key points in cooking temperature control. It can be triggered based on the step timeline or user action events, such as "2 minutes after step 3 begins." The reminder content can include descriptions of the temperature status (e.g., "oil temperature reaches 160℃"), judgment methods (e.g., "small bubbles appear when chopsticks are inserted"), and adjustment suggestions (e.g., "set the induction cooker to medium-high heat"). Reminders can be delivered through pop-up windows, voice prompts, or step highlighting.

[0123] For example, reminder anchors can be embedded in the step template. When generating the tutorial, reminder information can be set at the anchor point. After the user enters the step, a timer starts, and a prompt is triggered when the reminder time is reached. For example, when a user is using an induction cooker to recreate braised pork, a reminder pops up 1 minute after the step of caramelizing sugar begins: "Induction cooker temperature reminder: The current setting should be medium-high (power 1800W). Add the meat immediately when the sugar syrup turns dark red (approximately 2 minutes). Judgment criteria: The sugar syrup produces dense small bubbles and the color is uniform." Simultaneously, a voice prompt can be played (which can be turned off). The client-side tutorial page can also include operation controls. If the user clicks the "Adjusted" control, the system records the completion of that node.

[0124] For example, the cooking time indicator can be dynamically linked to the tutorial progress bar. The system can advance the progress at a constant speed according to the preset total time and trigger reminders at specific percentage points. For instance, when the progress reaches 50% in the 60-minute simmering step, a reminder message such as "Check the consistency of the soup" will be displayed.

[0125] For example, the page displaying tutorial information may include a control for confirming a step or action (this control can be manually activated or activated by voice, etc.). When the tutorial reaches the position of this control, or when the corresponding tutorial playback time is reached, the tutorial can automatically pause. After user confirmation, the tutorial can resume playback. The client can listen for user confirmation events and can also start a countdown or directly trigger a reminder based on the confirmation event. For example, at the step of adjusting the heat to low, the tutorial pauses. If the user clicks to continue playback, it can indicate that the user has completed the step of adjusting to high heat, and a reminder message "Please check the hardness" will be displayed after 5 minutes.

[0126] For example, if the terminal or system displaying the tutorial information can access the user's cooking screen, it can also analyze the screen to display corresponding reminders. For instance, a reminder can be triggered when a key cooking point is detected (such as when the sugar syrup turns a deep reddish-brown).

[0127] For example, if the terminal or system displaying the tutorial information can be connected to smart stoves and other kitchen appliances, it can receive information such as fire level and pot bottom temperature in real time. It can use a rule engine to trigger reminders based on preset thresholds (such as pot temperature ≥160℃ for 30 seconds), or it can dynamically calibrate parameters based on the user's stove type.

[0128] Optionally, the tutorial information may include a prompt indicating the remaining time for preparing the target dish; this prompt may include at least one of a countdown timer or a progress bar; the page displaying the tutorial information may also include a cooking process control component, which is used to dynamically adjust the display status of the tutorial information in response to user commands.

[0129] The remaining time can represent the dynamically calculated estimated completion time, or the difference between the total time and the time already elapsed. It can be displayed as a countdown timer or as a progress bar.

[0130] The cooking process control component can represent a set of user interaction controls, which may include one or more of the following: pause or continue controls, skip step controls, fast forward step controls, rewind step controls, or speed adjustment controls.

[0131] For example, a progress bar and a countdown timer for the current step or the total cooking time can be displayed at the top, bottom, or other locations on the page. If the user provides a "pause" command, the video will stop playing and the timer will freeze; if the user provides a "skip" command, the tutorial can automatically jump to the next step (the next step or the next action).

[0132] Dynamic remaining time indicators reduce time anxiety, while progress control components adapt the tutorial to real-world interruption scenarios. A visual progress bar enhances the sense of task completion, improving the user experience from various angles. Furthermore, visual progress management and flexible control components empower users with control over the cooking pace, effectively addressing the pain point of mismatch between tutorial pacing and actual operation time, and improving the smoothness of the interactive experience.

[0133] Optionally, the tutorial information may include a timer control for a preset step; the preset step is a step in the process of making the target dish that does not require user intervention; if the time corresponding to the timer control is completed, a prompt message indicating that the preset step has been completed will be played.

[0134] Preset steps can represent waiting stages in the cooking process that do not require continuous user intervention, such as marinating, fermentation, stewing, and resting. The timer control can represent a timer component, which can display timing information on the front end or execute the timing process in the background. The prompt message represents the notification message triggered when the timer ends, which can be displayed through one or more methods such as pop-ups, sounds, vibrations, or step highlighting.

[0135] For example, when generating a tutorial, an independent timer object can be generated for the preset steps. When the front end is rendering, an independent countdown can be displayed in the step area. When the preset step is executed, the countdown is triggered. When the countdown reaches zero, a prompt message is triggered.

[0136] For example, when the tutorial reaches the "marinate for 20 minutes" step, the system can start a background timer, and the timer can be displayed on the client page. After 20 minutes, a prompt message "Marinating complete, please proceed to the next step" can be played, and the system can continue to display instructions for the next step after the user confirms.

[0137] In practical applications, users are prone to forgetting or becoming distracted during the intervention-free steps, leading to overcooking or missing optimal cooking times. Automated timing and proactive notification mechanisms act as a virtual assistant, freeing up user attention while ensuring precise control of key time points. This eliminates the memory burden of waiting time, prevents cooking accidents caused by forgetfulness, and also improves the success rate of dish replication, ensuring the quality of gatherings and meals.

[0138] Based on the same approach, this manual also provides a method for generating digital invitations with the client as the executing entity.

[0139] See Figure 5 , Figure 5 A flowchart illustrating a method for generating a digital invitation letter according to an embodiment of this specification is shown. From a programming perspective, the execution entity of the process can be an application terminal program, specifically a client program, and may include the following steps.

[0140] Step 502: In response to the trigger command for generating a digital invitation, display the requirements configuration page for configuring dining requirements.

[0141] Trigger commands can be user-initiated commands that trigger the invitation generation process. Specifically, this could be a command to launch a specific app or mini-program, or a pre-defined operation performed on a specific page within an app or mini-program. For example, a user clicking the "Create Invitation" button or selecting the "Gathering Invitation" function.

[0142] The requirements configuration page can be an interactive interface component used to collect parameters for the gathering, and it can contain structured controls. The requirements configuration page can be in the form of a webpage, an in-app page, a pop-up, an H5 page, etc.

[0143] like Figure 3 As shown, this configuration page can be a page within the terminal application (app), specifically, it can be the configuration page displayed after the user selects the "Special Circumstances" control. The trigger instruction mentioned above can be the user clicking the "Special Circumstances" control.

[0144] Step 504: Determine the dining requirements specified by the user; the dining requirements include the desired dining atmosphere.

[0145] Dining needs information can include details about the desired dining atmosphere that users specify through selection or customization on the needs configuration page. These details may include the dining location, number of diners, and budget.

[0146] Step 506: Based on the dining needs information, display a digital invitation that contains information on at least one target dish and corresponds to the dining atmosphere requirements.

[0147] The target dish information is determined based on the dining needs information, and the digital invitation includes at least one or more of the following: a background image, background music, and invitation text information that match the dining atmosphere requirements.

[0148] The specific process for determining the target dish information and the digital invitation can be found in the description in the aforementioned embodiments, and will not be repeated here.

[0149] like Figure 4 This diagram illustrates a digital invitation. Users can send this digital invitation to the invitee through preset operations.

[0150] To help users better understand the recommended target dishes, the method in one or more embodiments of this specification may further include: displaying a target page containing information about the target dish; the target page includes the dish name and cooking information of the target dish; the cooking information includes at least one of cooking time information and required ingredient information; the required ingredient information includes at least one of ingredient quantity, ingredient category, and product SKU information corresponding to the ingredient.

[0151] The above-mentioned display of a digital invitation containing information on at least one target dish and corresponding to the dining atmosphere requirements may include: in response to an invitation generation instruction submitted to the target page, displaying a digital invitation containing the names of at least one target dish and corresponding to the dining atmosphere requirements.

[0152] The target page represents a separate menu display interface from the requirements configuration page and invitation preview page. This page can contain more information about the target dish. The dish name can be a standardized term (e.g., "Braised Pork Belly with Preserved Mustard Greens") for user identification. Cooking information can represent information related to cooking the dish, specifically including cooking time (e.g., 50 minutes) and information about the ingredients needed, such as quantity, type, and corresponding SKU.

[0153] Figure 6 This is a schematic diagram of a target page provided in one embodiment of this specification. For example... Figure 6As shown, this page includes area 602 for displaying information about target dishes. This area can display information about each dish that matches this gathering, such as the dish's name, its price (which may be determined based on the SKU of the ingredients required for the dish), preparation time (e.g., 15 minutes), and the total price for all dishes (e.g., total amount).

[0154] This page can also display the ingredient information corresponding to the target dish. If the target dish includes multiple dishes, the ingredient information of each dish can be displayed according to a preset structure, such as columns, regions, or by using separators to divide different dish display areas. For a certain dish, the area can display the name of the dish, as well as the details of the ingredients or the product SKU information of the ingredients.

[0155] If the target dish includes multiple dishes, the dishes can also be categorized and displayed, such as dividing the dishes into appetizers, main courses, desserts, drinks, etc., to display each dish in a structured manner.

[0156] like Figure 6 As shown, the page can also include an area 604 for displaying descriptive information about the theme of the gathering, such as "Weekend Gathering Menu with Friends" or "1st Wedding Anniversary Ceremony Menu". The specific description can vary depending on the gathering scenario or can be set according to the user's preferences.

[0157] like Figure 6 As shown, the page may also include an area 606 for displaying environmental information. For example, it may display the current time and weather information, or the agreed-upon dinner time and weather information, etc.

[0158] like Figure 6 As shown, to facilitate users' purchase of ingredients for gatherings, this page can also include an add-to-cart control 608. For example, a "Add to Cart" control; if a user interacts with this control, the SKUs of the dishes displayed on the page will be associated with the user's "cart," indicating the items the user wants to purchase. Users can then make a purchase order for the added items.

[0159] like Figure 6 As shown, the page may also include a control 610 for sending an invitation generation command. If the user performs an operation on this control, the client can display the generated digital invitation.

[0160] As one implementation, the client-side configuration page can include a control for generating invitations. After the user performs a preset operation on this control, the client can display the generated digital invitation. For example, the client can first display... Figure 3As shown in the requirements configuration page, after the user configures the content and clicks the "Generate Food Plan" control, the client can then display the following: Figure 4 The page shown displays the digital invitation. Or it displays... Figure 4 Previously, a transition page could be displayed to indicate that the invitation was being generated. Optionally, the page displaying the digital invitation could also include controls for displaying a target page containing menu information, such as... Figure 4 The example page shows a back control in the upper left corner. If the user performs an action on this control, the client can display something like this: Figure 6 The target page is shown in the image.

[0161] As another implementation, the client-side display request configuration page can include controls for triggering the determination of the target dish, such as... Figure 3 The "Generate Menu Plan" control shown in the image allows the client to display a target page containing information about the desired dish after the user performs a preset operation on the control. Figure 6 As shown, the target page can contain controls for generating invitations, such as a "Send Invitation" control. If the user performs an action on this control, the client can display the generated digital invitation, such as... Figure 4 The page shown displays the digital invitation. Or it displays... Figure 4 Previously, a transition page could be displayed to indicate that the invitation was being generated.

[0162] It should be noted that the above are just some examples. The navigation relationship between different pages, the navigation method, the page layout, and the content displayed on the page can all be set according to actual needs. No specific restrictions are made here.

[0163] In practical applications, to better meet user needs, users can edit the target dish, such as... Figure 6 As shown, the target page also includes a dish editing control 612, allowing users to perform editing operations. Optionally, the method in one or more embodiments of this specification may further include: displaying an updated target page in response to a user's editing operation on any one of a plurality of target dishes on the target page; the editing operation includes at least one of deleting a dish, modifying the serving size of a dish, and modifying the quantity and / or type of ingredients required to prepare the any one target dish.

[0164] Users can delete or add dishes; alternatively, they can modify the ingredients in a dish. After a user edits a dish, the system can update the corresponding product SKU information and display the updated SKU information on the client side.

[0165] To better suit user needs, users can also fine-tune the generated digital invitation. Optionally, the method in one or more embodiments of this specification further includes: displaying an updated dining invitation in response to an editing operation on the invitation materials in the digital invitation; the invitation materials include at least one of a background image, background music, and invitation text information; the editing operation includes at least one of modification, replacement, and deletion.

[0166] The page displaying the digital invitation can include controls for editing, or users can trigger editing of the invitation through specific operations such as long press, swipe, etc., or users can also perform editing operations by inputting natural language.

[0167] To make it easier for users to cook dishes, the system can generate corresponding cooking videos for dishes that users have added to their cart, saved in their favorites, or included in digital invitations. Users can view the corresponding cooking videos through preset paths.

[0168] It is understandable that the above Figure 3 , Figure 4 as well as Figure 6 This is just a sample page. In actual applications, the specific content and style of the page can be set according to actual needs, and there are no restrictions here.

[0169] With the above Figure 2 Corresponding to the method embodiments shown, this specification also provides an embodiment of a digital invitation generation apparatus. Figure 7 A schematic diagram of a device for generating a digital invitation card according to one embodiment of this specification is shown. This device can function as a product recommendation system or a server. Figure 7 As shown, the device may include: The requirement determination module 702 is used to determine dining requirement information related to group meals, including dining atmosphere requirements.

[0170] The matching module 704 is used to determine at least one target dish information that matches the dining needs information, as well as an invitation template that matches the dining atmosphere needs, based on the dining needs information; the invitation template includes at least one or more of the following: a background image with a preset visual style that matches the dining atmosphere needs, background music, and invitation text information.

[0171] The invitation generation module 706 is used to embed the target dish information into the invitation template to obtain a digital invitation containing the target dish information and corresponding to the dining atmosphere requirements, for use in providing to the invitee.

[0172] The above is a schematic scheme of a digital invitation generation device according to this embodiment. It should be noted that the technical solution of this digital invitation generation device is similar to that described above. Figure 2 The technical solution of the digital invitation generation method shown belongs to the same concept. For details not described in detail in the technical solution of the device, please refer to the description of the technical solution of the above method.

[0173] With the above Figure 5 Corresponding to the method embodiments shown, this specification also provides an embodiment of a digital invitation generation apparatus. Figure 8 A schematic diagram of a digital invitation generation device provided in one embodiment of this specification is shown. This device can function as a client. Figure 8 As shown, the device may include: The page display module 802 is used to display a requirement configuration page for configuring dining needs in response to a trigger command for generating a digital invitation.

[0174] The information determination module 804 is used to determine the dining requirements information specified by the user; the dining requirements information includes the requirements for the dining atmosphere.

[0175] The invitation display module 806 is used to display a digital invitation that contains at least one target dish and corresponds to the dining atmosphere requirement, based on the dining demand information; the target dish information is determined based on the dining demand information, and the digital invitation includes at least one or more of the following: a background image with a preset visual style that matches the dining atmosphere requirement, background music, and invitation text information.

[0176] The above is a schematic scheme of a digital invitation generation device according to this embodiment. It should be noted that the technical solution of this digital invitation generation device is similar to that described above. Figure 5 The technical solution of the digital invitation generation method shown belongs to the same concept. For details not described in detail in the technical solution of the device, please refer to the description of the technical solution of the above method.

[0177] Figure 9 A structural block diagram of a computing device 900 provided according to one embodiment of this specification is shown.

[0178] The computing device 900 includes: Memory 910 and processor 920; The memory 910 is used to store computer programs / instructions, and the processor 920 is used to execute the computer programs / instructions. When the computer programs / instructions are executed by the processor 920, they implement the steps of the above-described method for generating digital invitations.

[0179] In one or more embodiments of this specification, the computing device can be understood as an integrated smart terminal, including but not limited to a server, desktop computer, PC (Personal Computer), all-in-one model machine, mobile phone, tablet computer or other portable smart terminal, etc., and the computing device may have the model described in the above embodiments of this application pre-installed.

[0180] Specifically, this computing device can pre-install various types of models, including but not limited to models in natural language processing, visual processing, speech processing, code processing, and multimodal task processing, thus providing diverse model selection. In different product forms, this computing device can support one or more model usage methods, including but not limited to model training, model invocation, model fine-tuning, model deployment, model inference, and application. In some product forms, this computing device also supports model management, including but not limited to multi-type model management (supporting the management of discriminative, generative, and other model types), model version control (supporting the control of different model versions), and model evaluation (evaluating model performance and effectiveness based on model evaluation tools). In other product forms, this computing device can also create applications based on models, providing API (Application Programming Interface) calling capabilities. Users can call models into created applications through the API interface, and application management tools are also provided to manage and monitor the applications.

[0181] Furthermore, the computing device can also include data management (supporting the creation and management of model tuning datasets), a training center (providing abundant training resources to help users learn and master AI (Artificial Intelligence) technology), and basic control capabilities (providing enterprise-level basic control capabilities to ensure the security and efficient operation of the system). Through the above functions, it provides a comprehensive and integrated device for AI development, training, deployment, and application.

[0182] Figure 10 A structural block diagram of an electronic device 1000 provided according to one embodiment of this specification is shown.

[0183] The memory 1010 and the processor 1020 are connected via a bus 1030; The memory 1010 is used to store computer programs / instructions, and the processor 1020 is used to execute the computer programs / instructions, which, when executed by the processor 1020, implement the steps of the method.

[0184] Specifically, the components of the electronic device 1000 include, but are not limited to, a memory 1010 and a processor 1020. The processor 1020 is connected to the memory 1010 via a bus 1030, and the database 1050 is used to store data.

[0185] Electronic device 1000 also includes access device 1040, which enables electronic device 1000 to communicate via one or more networks 1060. Examples of these networks include Public Switched Telephone Network (PSTN), Local Area Network (LAN), Wide Area Network (WAN), Personal Area Network (PAN), or combinations of communication networks such as the Internet. Access device 1040 may include one or more of any type of wired or wireless network interface (e.g., network interface card (NIC)), such as an IEEE 802.11 Wireless Local Area Network (WLAN) wireless interface, a Wi-MAX (Worldwide Interoperability for Microwave Access) interface, an Ethernet interface, a Universal Serial Bus (USB) interface, a cellular network interface, a Bluetooth interface, a Near Field Communication (NFC) interface, and so on.

[0186] In one embodiment of this specification, the above-described components of the electronic device 1000 and Figure 10 Other components, not shown, can also be connected to each other, for example, via a bus. It should be understood that... Figure 10 The block diagram of the electronic device shown is for illustrative purposes only and is not intended to limit the scope of this specification. Those skilled in the art can add or replace other components as needed.

[0187] Electronic device 1000 can be any type of stationary or mobile electronic device, including mobile computers or mobile electronic devices (e.g., tablet computers, personal digital assistants, laptop computers, notebook computers, netbooks, etc.), mobile phones (e.g., smartphones), wearable electronic devices (e.g., smartwatches, smart glasses, etc.) or other types of mobile devices, or stationary electronic devices such as desktop computers or personal computers (PCs). Electronic device 1000 can also be a mobile or stationary server.

[0188] The above is an illustrative scheme of an electronic device according to this embodiment. It should be noted that the technical solution of this electronic device and the technical solution of the above-described digital invitation generation method belong to the same concept. For details not described in detail in the technical solution of the electronic device, please refer to the description of the technical solution of the above-described digital invitation generation method.

[0189] An embodiment of this specification also provides a computer-readable storage medium storing a computer program / instructions that, when executed by a processor, implement the steps of the above-described digital invitation generation method.

[0190] The above is an illustrative scheme of a computer-readable storage medium according to this embodiment. It should be noted that the technical solution of this storage medium and the technical solution of the above-described digital invitation generation method belong to the same concept. For details not described in detail in the technical solution of the storage medium, please refer to the description of the technical solution of the above-described digital invitation generation method.

[0191] An embodiment of this specification also provides a computer program product, including a computer program / instructions that, when executed by a processor, implement the steps of the above-described digital invitation generation method.

[0192] The above is an illustrative scheme of a computer program product according to this embodiment. It should be noted that the technical solution of this computer program product and the technical solution of the above-described digital invitation generation method belong to the same concept. For details not described in detail in the technical solution of the computer program product, please refer to the description of the technical solution of the above-described digital invitation generation method.

[0193] The foregoing has described specific embodiments of this specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recited in the claims may be performed in a different order than that shown in the embodiments and may still achieve the desired result. Furthermore, the processes depicted in the drawings do not necessarily require the specific or sequential order shown to achieve the desired result. In some embodiments, multitasking and parallel processing are possible or may be advantageous.

[0194] The computer program / instructions include computer program code, which may be in the form of source code, object code, executable file, or certain intermediate forms. The computer-readable medium may include: any entity or device capable of carrying the computer program code, recording media, USB flash drive, portable hard drive, magnetic disk, optical disk, computer memory, read-only memory (ROM), random access memory (RAM), electrical carrier signals, telecommunication signals, and software distribution media, etc. It should be noted that the content included in the computer-readable medium may be appropriately added or removed according to the requirements of patent practice. For example, in some regions, according to patent practice, computer-readable media may not include electrical carrier signals and telecommunication signals.

[0195] It should be noted that, for the sake of simplicity, the foregoing method embodiments are all described as a series of actions. However, those skilled in the art should understand that the embodiments in this specification are not limited to the described order of actions, because according to the embodiments in this specification, some steps can be performed in other orders or simultaneously. Furthermore, those skilled in the art should also understand that the embodiments described in this specification are all preferred embodiments, and the actions and modules involved are not necessarily essential to the embodiments in this specification.

[0196] In the above embodiments, the descriptions of each embodiment have different focuses. For parts not described in detail in a certain embodiment, please refer to the relevant descriptions of other embodiments.

[0197] The preferred embodiments disclosed above are merely illustrative of this specification. The optional embodiments do not exhaustively describe all details, nor do they limit the invention to the specific implementations described. Clearly, many modifications and variations can be made based on the embodiments described herein. These embodiments are selected and specifically described in this specification to better explain the principles and practical applications of the embodiments, thereby enabling those skilled in the art to better understand and utilize this specification. This specification is limited only by the claims and their full scope and equivalents.

Claims

1. A method for generating a digital invitation, comprising: Determine dining needs information related to group meals, including dining atmosphere requirements; Based on the dining needs information, at least one target dish information is determined, as well as an invitation template that matches the dining atmosphere requirements; the invitation template includes at least one or more of the following: a background image with a preset visual style that matches the dining atmosphere requirements, background music, and invitation text information; The target dish information is embedded into the invitation template to obtain a digital invitation that contains the target dish information and corresponds to the dining atmosphere requirements, which is then provided to the invitee.

2. The method according to claim 1, further comprising: Determine the text information provided by the user to describe the dining activity; The target text information is determined based on the aforementioned text information; The target text information is at least a portion of the information in the invitation text information.

3. The method according to claim 1, further comprising: Identify dining preference information associated with dining participants; Based on the dining needs information, at least one matching target dish is determined, including: By combining the dining needs information and the dining preferences information, an intelligent model is used to determine at least one matching target dish.

4. The method according to claim 1, further comprising: Based on the user's editing operations on the target dish, the updated dish information is determined; The editing operations include at least one of the following: deleting dishes, increasing the number of servings of dishes, and decreasing the number of servings of dishes; The step of embedding the target dish information into the invitation template to obtain a digital invitation containing the target dish information and corresponding to the dining atmosphere requirements includes: The updated menu information is embedded into the invitation template to obtain a digital invitation that includes the updated menu information and corresponds to the desired dining atmosphere.

5. The method according to claim 1, wherein based on the dining needs information, an invitation template matching the dining atmosphere needs is determined, comprising: The dining requirements information is provided to the generative model to obtain an invitation template generated by the generative model that matches the dining atmosphere requirements.

6. The method according to claim 1, further comprising: The invitation template is adjusted based on the environmental information to obtain a target invitation template that conforms to the environmental information; The environmental information includes the local time and / or weather information of the location of the dining participants; Embedding the target dish information into the invitation template includes: embedding the target dish information into the target invitation template.

7. The method according to claim 1, further comprising: Determine the ingredient details of the target dish represented by the target dish information; The ingredient list includes the category and quantity of the required ingredients; Based on the ingredient details, the system selects the minimum stock unit (SKU) and quantity information of the product corresponding to the ingredient in the ingredient details from the associated product information database, and generates recommended product SKU information so that the user can perform the product purchase operation based on the recommended product SKU information.

8. The method according to claim 7, further comprising: Identify the dining preference information associated with dining participants; The ingredient details information used to determine the target dish information include: Retrieve the recipe preparation knowledge corresponding to the target dish information; Based on the knowledge of dish preparation, determine the standard ingredient list information required to prepare the target dish represented by the target dish information; By adjusting the quantity and / or category of ingredients in the standard ingredient list based on the dining preference information, the detailed ingredient information that conforms to the dining preference information and is required to prepare the target dish is determined.

9. The method according to claim 7, further comprising: Identify the dining preference information associated with dining participants; Based on the ingredient details of the target dish, select the minimum stock unit (SKU) and purchase quantity information of the product corresponding to the ingredient in the ingredient details from the associated product information database, including: Based on the dining preference information and the ingredient details, select the minimum stock unit (SKU) and purchase quantity information of the product corresponding to the ingredient in the ingredient details from the associated product information database.

10. The method according to any one of claims 1 to 9, wherein the dining demand information includes the number of diners, budget amount, and dining scenario type information.

11. A method for generating a digital invitation, comprising: In response to a trigger command used to generate a digital invitation, a requirements configuration page for configuring dining needs is displayed; Determine the user's specified dining requirements; The dining needs information includes dining atmosphere requirements; Based on the dining needs information, a digital invitation is displayed that includes at least one target dish and corresponds to the dining atmosphere requirements; the target dish information is determined based on the dining needs information, and the digital invitation includes at least one or more of the following: a background image with a preset visual style that matches the dining atmosphere requirements, background music, and invitation text.

12. The method according to claim 11, further comprising: Display a target page containing information about the target dish; the target page includes the dish name and cooking information of the target dish; The cooking information includes at least one of the following: cooking time information and required ingredient information; The required ingredient information includes at least one of the following: ingredient quantity, ingredient category, and corresponding product SKU information; The displayed digital invitation, which includes information on at least one target dish and corresponds to the desired dining atmosphere, includes: In response to an invitation generation command submitted for the target page, a digital invitation is displayed that contains the name of at least one target dish and corresponds to the desired dining atmosphere.

13. An electronic device, comprising: A memory and a processor, the memory and the processor being connected via a bus; The memory is used to store computer programs / instructions, and the processor is used to execute the computer programs / instructions, which, when executed by the processor, implement the steps of the method according to any one of claims 1 to 12.

14. A computer-readable storage medium storing a computer program / instructions that, when executed by a processor, implement the steps of the method according to any one of claims 1 to 12.

15. A computer program product comprising a computer program / instructions that, when executed by a processor, implement the steps of the method according to any one of claims 1 to 12.

Images