Dish label processing method, device and equipment, medium and program product

Abstract

The invention provides a dish label processing method and device, equipment, a medium and a program product. Relates to the technical field of data processing. The method is applied to the computer equipment, a pre-created label type model and store information of a to-be-configured store are obtained by responding to a menu configuration request, first label class generation processing is carried out according to the store information and the pre-created label type model, and at least one personalized label class corresponding to the to-be-configured store is obtained. And obtaining to-be-configured dish information, performing object creation processing according to the to-be-configured dish information and the at least one personalized tag class corresponding to the to-be-configured store to obtain at least one tag object corresponding to the to-be-configured store, and generating menu information of the to-be-configured store according to the at least one tag object corresponding to the to-be-configured store. The privatization of the store menu is realized, and the flexibility of menu processing, the accuracy of the store menu and the configuration efficiency are improved.

Description

Technical Field

[0001] The present application relates to the field of data processing technology, and in particular to a method, device, equipment, medium and program product for processing a dish label. Background Art

[0002] Menu labels play an important role in the catering industry. They not only provide basic information about the dishes, but also help customers better understand and choose the dishes. With the development of Internet technology and the advent of the big data era, in the catering industry, automated menus can be configured based on menu labels, and automated ordering based on automated menus has gradually become the mainstream.

[0003] At present, automated ordering is based on the catering management information system, which is mainly implemented in the following ways: Method 1, providing a simple dish note column, which is filled in by the waiter or customer, and the kitchen prepares the meal according to the note. Method 2, the business operator configures the dish label attributes in the system by himself, which can be displayed and selected when ordering.

[0004] However, the prior art dish labels have poor processing flexibility and low menu configuration efficiency. Summary of the invention

[0005] The present application provides a method, device, equipment and storage medium for processing dish labels, so as to solve the problems of poor processing flexibility and low efficiency of menu configuration of dish labels in the prior art.

[0006] In a first aspect, the present application provides a method for processing a dish label, which is applied to a computer device, comprising:

[0007] In response to the menu configuration request, obtaining a pre-created label type model;

[0008] Get the store information of the store to be configured;

[0009] Perform a first label class generation process according to the store information and the pre-created label type model to obtain at least one personalized label class corresponding to the store to be configured;

[0010] Get the dish information to be configured;

[0011] Performing object creation processing according to the dish information to be configured and at least one personalized label class corresponding to the store to be configured, so as to obtain at least one label object corresponding to the store to be configured;

[0012] Menu information of the store to be configured is generated according to at least one label object corresponding to the store to be configured.

[0013] The present application provides a method for processing dish labels, which generates a personalized label class for the store based on a label type model and information of the store to be configured, and automatically creates a personalized menu based on the dishes to be configured and the personalized label class. The menu can be automatically generated based on the store information and dish information, without the need for manual configuration or exhaustive enumeration of a huge number of dish labels each time a menu is generated, and a personalized label class can be generated for each store to be configured, thereby realizing the privatization of the store menu and improving the flexibility of menu processing, the accuracy of the store menu and the configuration efficiency.

[0014] In a possible design, performing a first tag class generation process according to the store information and the pre-created tag type model to obtain at least one personalized tag class corresponding to the store to be configured includes:

[0015] Obtain at least one common tag class object preconfigured for each of the tag type models;

[0016] Inheriting the at least one public tag class object;

[0017] According to the store information, the at least one public label class object is modified to obtain at least one personalized label class corresponding to the store to be configured.

[0018] This application establishes a public label class object. When generating a store menu to be configured, the personalized label class of the store is obtained based on the inheritance and modification of the public label class object. The inheritance of the public label class object can effectively reduce the workload. Based on the modification of the public label class object, the personalization and privatization of the store menu is realized. Based on the above scheme, the redundant steps of re-establishing the label class are saved, the configuration speed and efficiency of the store menu are improved, and the accuracy of the menu is improved.

[0019] In a possible design, the tag type model includes multiple tag type information;

[0020] The first label class generation process is performed according to the store information and the pre-created label type model to obtain at least one personalized label class corresponding to the store to be configured, including:

[0021] According to the store information, matching is performed in the pre-created tag type model to determine the tag type information corresponding to the store information;

[0022] At least one personalized label class corresponding to the store to be configured is generated according to the label type information corresponding to the store information.

[0023] The present application can also obtain the label type information corresponding to the store information by directly matching the store information in the label type model, and directly generate personalized label classes based on the store information and the label type model, thereby saving the redundant steps of summarizing and establishing label classes based on the store information, and improving the configuration speed and efficiency of the store menu.

[0024] In a possible design, before obtaining a pre-created label type model in response to a menu configuration request, the method further includes:

[0025] Get multiple tag type information;

[0026] A tag type model is created according to the multiple tag type information.

[0027] This application creates a tag type model in advance through multiple tag type information, which is convenient for subsequent calling when configuring the store menu, thereby improving the configuration efficiency of the store menu.

[0028] In a possible design, after creating a tag type model according to the plurality of tag type information, the method further includes:

[0029] A tag class object extraction process is performed on the tag type information in the tag type model to obtain at least one common tag class object corresponding to the tag type model.

[0030] This application can extract the common tag class object through the tag type information in the pre-created tag type model, saving the redundant steps of recreating the tag class when generating store menus for different stores, thereby improving the configuration efficiency of the store menu.

[0031] In a possible design, the obtaining of multiple tag type information includes:

[0032] Acquire multiple historical orders; and classify the multiple historical orders to obtain multiple tag type information.

[0033] This application obtains multiple tag type information by classifying historical orders, and realizes the comprehensive and accurate creation of public tag classes, which is convenient for subsequent calling when configuring store menus, thereby improving the configuration efficiency of store menus.

[0034] In a possible design, after generating the menu information of the store to be configured according to at least one tag object corresponding to the store to be configured, the method further includes:

[0035] In response to the order request, obtaining menu information of the store to be configured;

[0036] Generate an ordering interface based on the menu information of the store to be configured.

[0037] This application triggers the ordering operation through the ordering request, directly obtains the menu information of the configured store and generates a menu instance, and presents it in the form of an ordering interface. The merchant only needs to perform simple personalized processing for the store to be configured, and the rest of the menu parts are directly generated according to the menu information, which improves the efficiency of menu configuration and ordering efficiency.

[0038] In a possible design, after generating an ordering interface according to the menu information of the store to be configured, the method further includes:

[0039] In response to an ordering operation performed by a user on the ordering interface, determining target menu information corresponding to the ordering operation;

[0040] Output a target order according to the target menu information.

[0041] This application generates and outputs a target order through the target menu information corresponding to the user's ordering operation, thereby realizing active ordering, improving the flexibility of ordering, saving the merchant's time for one-to-one manual ordering, avoiding the error-prone manual ordering, and improving the efficiency of ordering.

[0042] In a second aspect, the present application provides a device for processing a dish label, comprising:

[0043] A first acquisition module, configured to acquire a pre-created label type model in response to a menu configuration request;

[0044] The second acquisition module is used to acquire the store information of the store to be configured;

[0045] A first processing module, configured to perform a first label class generation process according to the store information and the pre-created label type model, so as to obtain at least one personalized label class corresponding to the store to be configured;

[0046] The third acquisition module is used to obtain the dish information to be configured;

[0047] A second processing module is used to perform object creation processing according to the dish information to be configured and at least one personalized label class corresponding to the store to be configured, so as to obtain at least one label object corresponding to the store to be configured;

[0048] A generation module is used to generate menu information of the store to be configured according to at least one label object corresponding to the store to be configured.

[0049] Optionally, the first processing module is specifically configured to:

[0050] Obtain at least one common tag class object preconfigured for each of the tag type models;

[0051] Inheriting the at least one public tag class object;

[0052] According to the store information, the at least one public label class object is modified to obtain at least one personalized label class corresponding to the store to be configured.

[0053] Optionally, the tag type model includes multiple tag type information;

[0054] Accordingly, the first processing module is specifically used for:

[0055] The first label class generation process is performed according to the store information and the pre-created label type model to obtain at least one personalized label class corresponding to the store to be configured, including:

[0056] According to the store information, matching is performed in the pre-created tag type model to determine the tag type information corresponding to the store information;

[0057] At least one personalized label class corresponding to the store to be configured is generated according to the label type information corresponding to the store information.

[0058] Optionally, before acquiring a pre-created label type model in response to the menu configuration request, the apparatus further comprises a model creation module, which is used to:

[0059] Get multiple tag type information;

[0060] A tag type model is created according to the multiple tag type information.

[0061] Optionally, after creating the tag type model according to the plurality of tag type information, the apparatus further comprises a tag type acquisition module, which is used to:

[0062] A tag class object extraction process is performed on the tag type information in the tag type model to obtain at least one common tag class object corresponding to the tag type model.

[0063] Optionally, the model creation module is specifically used to:

[0064] Acquire multiple historical orders; and classify the multiple historical orders to obtain multiple tag type information.

[0065] Optionally, after generating the menu information of the store to be configured according to at least one label object corresponding to the store to be configured, the device further includes an ordering module, which is used to:

[0066] In response to the order request, obtaining menu information of the store to be configured;

[0067] Generate an ordering interface based on the menu information of the store to be configured.

[0068] Optionally, after generating an ordering interface according to the menu information of the store to be configured, the device further includes an ordering module for:

[0069] In response to an ordering operation performed by a user on the ordering interface, determining target menu information corresponding to the ordering operation;

[0070] Output a target order according to the target menu information.

[0071] In a third aspect, the present application provides a device for processing a dish label, comprising:

[0072] at least one processor;

[0073] and a memory communicatively coupled to the at least one processor;

[0074] Among them, the memory stores instructions that can be executed by the at least one processor, and the instructions are executed by the at least one processor so that the at least one processor can execute the method for processing dish labels as described in the first aspect and various possible designs of the first aspect.

[0075] In a fourth aspect, the present application provides a computer-readable storage medium, in which computer execution instructions are stored. When the computer execution instructions are executed by a processor, they are used to implement the method for processing dish labels as described in the first aspect and various possible designs of the first aspect.

[0076] In a fifth aspect, the present application provides a computer program product, including a computer program, which, when executed by a processor, implements the method for processing dish labels as described in the first aspect and various possible designs of the first aspect.

[0077] The present application provides a method, device, equipment, medium and program product for processing dish labels. The method is applied to a computer device, and by responding to a menu configuration request, a pre-created label type model and store information of a store to be configured are obtained. According to the store information and the pre-created label type model, a first label class generation process is performed to obtain at least one personalized label class corresponding to the store to be configured, and then the dish information to be configured is obtained. According to the dish information to be configured and at least one personalized label class corresponding to the store to be configured, an object creation process is performed to obtain at least one label object corresponding to the store to be configured, and the menu information of the store to be configured is generated according to the at least one label object corresponding to the store to be configured. The present application does not require manual configuration, nor does it require exhaustive enumeration of a huge number of dish labels each time a menu is generated, and can generate a personalized label class for each store to be configured, thereby realizing the privatization of store menus, and improving the flexibility of menu processing, the accuracy of store menus and the configuration efficiency. BRIEF DESCRIPTION OF THE DRAWINGS

[0078] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and, together with the description, serve to explain the principles of the present application.

[0079] Figure 1 A schematic diagram of a system architecture for processing dish labels provided in an embodiment of the present application;

[0080] Figure 2 A schematic diagram of a method for processing a dish label provided in an embodiment of the present application Figure 1 ;

[0081] Figure 3 A schematic diagram of a method for processing a dish label provided in an embodiment of the present application Figure 2 ;

[0082] Figure 4 A schematic diagram of a method for processing a dish label provided in an embodiment of the present application Figure 3 ;

[0083] Figure 5 A schematic diagram of a method for processing a dish label provided in an embodiment of the present application Figure 4 ;

[0084] Figure 6 A schematic diagram of a method for processing a dish label provided in an embodiment of the present application Figure 5 ;

[0085] Figure 7 A schematic diagram of a method for processing a dish label provided in an embodiment of the present application Figure 6 ;

[0086] Figure 8 A schematic diagram of the structure of a dish label processing device provided in an embodiment of the present application;

[0087] Fig. 9 A schematic diagram of the structure of a dish label processing device provided in an embodiment of the present application.

[0088] The above drawings have shown clear embodiments of the present application, which will be described in more detail later. These drawings and text descriptions are not intended to limit the scope of the present application in any way, but to illustrate the concept of the present application to those skilled in the art by referring to specific embodiments. DETAILED DESCRIPTION

[0089] Exemplary embodiments will be described in detail herein, examples of which are shown in the accompanying drawings. When the following description refers to the drawings, the same numbers in different drawings represent the same or similar elements unless otherwise indicated. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present disclosure. Instead, they are merely examples of devices and methods consistent with some aspects of the present disclosure as detailed in the appended claims.

[0090] The terms "first", "second", "third", and "fourth", etc. (if any) in the specification and claims of the present application and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchangeable where appropriate, so that the embodiments of the present application described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any of their variations are intended to cover non-exclusive inclusions, for example, a process, method, system, product, or device that includes a series of steps or units is not necessarily limited to those steps or units that are clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products, or devices.

[0091] In the technical solution of this application, the collection, storage, use, processing, transmission, provision and disclosure of information such as financial data or user data involved shall comply with the provisions of relevant laws and regulations and shall not violate public order and good morals.

[0092] It should be noted that in the embodiments of the present application, certain software, components, models and other existing solutions in the industry may be mentioned, and they should be regarded as exemplary. Their purpose is only to illustrate the feasibility of implementing the technical solution of the present application, but it does not mean that the applicant has or will necessarily use the solution.

[0093] In the existing technology, modern consumers are no longer satisfied with standardized menu selections, but prefer to customize dishes according to their tastes, health needs or special eating habits. Catering merchants need to be able to provide a variety of choices to meet this demand. Traditional manual records or simple electronic ordering systems can no longer meet the complex and changing needs of personalized customization, which can easily lead to misunderstandings and errors in the ordering process, thus affecting the customer experience. Therefore, catering merchants need to use business management information systems to achieve the function of dish label configuration management.

[0094] The mainstream catering management information system has the following implementation methods: Method 1: Provide a simple dish note column, which is filled in by the waiter or customer, and the kitchen prepares the meal according to the note. Method 2: The business operator configures the dish label attributes in the system, which can be displayed and selected when ordering. Method 3: The management information system designs the dish label items, and the business operator selects the required label items for the dish in the menu management interface, and then displays and fills in the established style.

[0095] In the catering management information system provided by the first method, customers do not have enough understanding of the optional customization content and rely on the assistance of waiters, which affects the efficiency and autonomy of ordering. Manually filling in the ordering information is not fast, convenient, error-prone and inefficient. At the same time, there are inconsistencies and ambiguities when customers describe their customization needs, which may lead to misunderstandings by chefs and ultimately affect the quality of dishes and customer satisfaction. In the catering management information system provided by the second method, merchants need to have a high level of information system management knowledge and experience when configuring dish attribute labels to ensure the accuracy of the labels and the matching degree with the dishes. In addition, since each label content needs to be created from scratch, the workload of merchants in the initial setting stage is increased, requiring merchants to invest more time and energy in meticulous operations. In the catering management information system provided by the third method, system developers or service providers need to have a deep insight into the needs of industry customers, accurately analyze and configure and maintain various attribute labels in the system to support merchants in efficient operation. At the same time, merchants face the challenge of screening from a massive label library and accurately matching labels for their dishes. This process requires a high degree of meticulousness and professionalism. Based on the above solutions, it can be seen that the existing technology has technical problems such as the inability to achieve flexible processing of dish labels and low efficiency of menu configuration.

[0096] In order to solve the above problems, the embodiments of the present application provide a method, device, equipment and storage medium for processing dish labels, wherein the method generates a personalized label class through a pre-created label type model and the store information of the store to be configured, and generates the menu information of the store to be configured through the personalized label class and the dish information to be configured. The flexibility of menu processing, the accuracy of store menus and the configuration efficiency are improved.

[0097] Optional, Figure 1This is a schematic diagram of a system architecture for processing dish labels provided in an embodiment of the present application, wherein the system for processing dish labels is a computer device. Figure 1 In the above architecture, the above architecture includes at least one of a data acquisition device 101, a processing device 102 and a display device 103.

[0098] It is understandable that the structure illustrated in the embodiment of the present application does not constitute a specific limitation on the architecture of the system for processing dish labels. In other feasible implementations of the present application, the above architecture may include more or fewer components than shown in the figure, or combine certain components, or divide certain components, or arrange components differently, which can be determined according to the actual application scenario and is not limited here. Figure 1 The components shown may be implemented in hardware, software, or a combination of software and hardware.

[0099] In a specific implementation process, the data acquisition device 101 may include an input / output interface and may also include a communication interface. The data acquisition device 101 may be connected to the processing device via the input / output interface or the communication interface.

[0100] The processing device 102 may slice the object file into multiple file blocks, and retrieve the entire object file by searching the file blocks in parallel.

[0101] The display device 103 may also be a touch display screen or a screen of a terminal device, which is used to receive user instructions while displaying the above content to achieve interaction with the user.

[0102] It should be understood that the above-mentioned processing device can be implemented by a processor reading instructions in a memory and executing the instructions, or it can be implemented by a chip circuit.

[0103] In addition, the network architecture and business scenarios described in the embodiments of the present application are intended to more clearly illustrate the technical solutions of the embodiments of the present application, and do not constitute a limitation on the technical solutions provided in the embodiments of the present application. Ordinary technicians in this field can know that with the evolution of network architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of the present application are also applicable to similar technical problems.

[0104] The technical solution of the present application is described in detail below in conjunction with specific embodiments:

[0105] Optionally, Figure 2 A schematic diagram of a method for processing a dish label provided in an embodiment of the present application Figure 1 The execution entity of the embodiment of the present application may be Figure 1 The processing device 102 in the embodiment may be a computer device determined according to the actual application scenario. Figure 2 As shown, the method comprises the following steps:

[0106] S201: In response to a menu configuration request, obtain a pre-created label type model.

[0107] The pre-created tag type models may be multiple or one.

[0108] S202: Obtain store information of the store to be configured.

[0109] Optionally, the store information of the store to be configured is uploaded or input by the merchant, including relevant information about the menu.

[0110] S203: Perform a first label class generation process according to the store information and the pre-created label type model to obtain at least one personalized label class corresponding to the store to be configured.

[0111] Optionally, based on the store information and a pre-created label type model, the merchant performs a first label class generation process to obtain at least one personalized label class corresponding to the store to be configured.

[0112] Among them, the first label type generation process is that the merchant customizes the label type object, including operations such as adding, deleting and changing.

[0113] S204: Obtain information of dishes to be configured.

[0114] Optionally, obtain the dish information to be configured based on the store information.

[0115] S205: Perform object creation processing according to the dish information to be configured and at least one personalized label class corresponding to the store to be configured, so as to obtain at least one label object corresponding to the store to be configured.

[0116] Optionally, object creation processing is performed based on the dish information to be configured and at least one personalized label class corresponding to the store to be configured that is related to the dish information to be configured to obtain at least one label object corresponding to the store to be configured.

[0117] Among them, the label object is a label instance obtained by personalizing the personalized label class according to the dish information.

[0118] S206: Generate menu information of the store to be configured according to at least one label object corresponding to the store to be configured.

[0119] Optionally, during the ordering operation, menu information of the store to be configured is generated based on at least one label object corresponding to the store to be configured, and displayed for the user to select and fill in.

[0120] It should be noted that, in a preferred embodiment, the dish label processing system provided in the embodiment of the present application includes storage module 1, storage module 2, storage module 3 and storage module 4.

[0121] It should also be noted that storing various data in the storage module can facilitate subsequent calls and improve the efficiency of menu configuration.

[0122] Optionally, the storage module 1 is used to store the core system tag type model, that is, to store the pre-created tag type model.

[0123] For example, the pre-created tag class model is as shown in Table 1, which is a pre-created tag class model table provided in an embodiment of the present application.

[0124] Table 1

[0125]

[0126] Optionally, the storage module 2 is used to store the core system tag class object library, that is, to store the common tag class objects of the storage system.

[0127] For example, the common tag class objects are shown in Table 2 and Table 3, which are respectively a common tag class object table 1 and a common tag class object table 2 provided in an embodiment of the present application.

[0128] Table 2

[0129]

[0130] Table 3

[0131]

[0132] Optionally, the storage module 3 is used to store a merchant private tag library, that is, to store tag objects customized by store merchants, also called personalized tag objects.

[0133] For example, examples after inheritance modification according to Table 2 and Table 3 are shown in Table 4 and Table 5, which are respectively Table 1 and Table 2 of the label class objects of the store provided in the embodiment of the present application.

[0134] Table 4

[0135]

[0136] Table 5

[0137]

[0138] Optionally, the storage module 4 is used to store a merchant menu information label instance table, that is, to store label instance objects configured by store merchants for dishes.

[0139] Optionally, the related label objects in the four storage modules correspond to each other, and a menu information label instance table is created according to the corresponding label objects in storage module 1, storage module 2 and storage module 3.

[0140] For example, examples of creating instances based on Table 1, Table 2, Table 3, Table 4 and Table 5 are shown in Table 6 and Table 7. Table 6 and Table 7 are respectively Store Instance Table 1 and Store Instance Table 2 provided in the embodiments of the present application.

[0141] Table 6

[0142]

[0143] Table 7

[0144]

[0145] It can be understood that the above Tables 1 to 7 are all schematic, and the labels established in the embodiment of the present application and the tables corresponding to the store instances can be determined according to actual conditions, and no specific limitations are made here.

[0146] The present application provides a method for processing dish labels, which generates a personalized label class for the store based on a label type model and information of the store to be configured, and automatically creates a personalized menu based on the dishes to be configured and the personalized label class. The menu can be automatically generated based on the store information and dish information, without the need for manual configuration or exhaustive enumeration of a huge number of dish labels each time a menu is generated, and a personalized label class can be generated for each store to be configured, thereby realizing the privatization of the store menu and improving the flexibility of menu processing, the accuracy of the store menu and the configuration efficiency.

[0147] Optional, Figure 3 A schematic diagram of a method for processing a dish label provided in an embodiment of the present application Figure 2 ,exist Figure 2 Based on the embodiment of the present invention, a specific implementation step of S203 includes:

[0148] S301: Acquire at least one common tag class object preconfigured for each tag type model.

[0149] Optionally, when configuring a store menu, first obtain at least one public tag class object from a preconfigured tag type model.

[0150] S302: Inherit at least one public tag class object.

[0151] Optionally, the store menu to be configured inherits at least one public tag class object.

[0152] S303: modify at least one public label class object according to the store information to obtain at least one personalized label class corresponding to the store to be configured.

[0153] Optionally, at least one acquired public label class object is modified based on the store information, so as to obtain at least one personalized label class corresponding to the configured store menu.

[0154] For example, the standard tag class is read from storage module 2, inheritance modification is performed, a personalized tag class is generated, and the personalized tag class is saved in storage module 3.

[0155] For a further example, store 1 obtains the public tag class object "dish specifications" from the preconfigured tag type model. Then, based on the store 1 information, the public tag class object "dish specifications" is changed to the personalized tag class "store 1 dish specifications".

[0156] This application establishes a public label class object. When generating a store menu to be configured, the personalized label class of the store is obtained based on the inheritance and modification of the public label class object. The inheritance of the public label class object can effectively reduce the workload. Based on the modification of the public label class object, the personalization and privatization of the store menu is realized. Based on the above scheme, the redundant steps of re-establishing the label class are saved, the configuration speed and efficiency of the store menu are improved, and the accuracy of the menu is improved.

[0157] Optionally, the tag type model includes multiple tag type information. Accordingly, Figure 4 A schematic diagram of a method for processing a dish label provided in an embodiment of the present application Figure 3 ,exist Figure 2 and Figure 3 Based on the example, Figure 4 As shown, another specific implementation step of S203 includes:

[0158] S401: Matching is performed in a pre-created tag type model according to the store information to determine the tag type information corresponding to the store information.

[0159] The tag type information is the header “tag type name” in Table 1.

[0160] Optionally, the store information is matched in a pre-created tag type model to obtain tag type information corresponding to the store information.

[0161] S402: Generate at least one personalized label class corresponding to the store to be configured according to the label type information corresponding to the store information.

[0162] Optionally, the label type information corresponding to the store information and the store information are personalized to generate at least one personalized label class corresponding to the store to be configured.

[0163] For example, the tag type model is read from storage module 1, and a personalized tag class is generated according to the tag type model, and the personalized tag class is directly generated and stored in storage module 3.

[0164] The embodiment of the present application can also obtain the label type information corresponding to the store information by directly matching the store information in the label type model, and directly generate a personalized label class according to the store information and the label type model, thereby saving the redundant steps of summarizing and establishing the label class according to the store information and improving the configuration speed and efficiency of the store menu.

[0165] Optional, Figure 5 A schematic diagram of a method for processing a dish label provided in an embodiment of the present application Figure 4 ,exist Figure 2 , Figure 3 and Figure 4 Based on the example, Figure 5 As shown, before S201, it also includes:

[0166] S501: Acquire multiple tag type information.

[0167] Optionally, get multiple historical orders.

[0168] Further optionally, multiple historical orders are classified to obtain multiple label type information.

[0169] It should be noted that there are many ways to classify multiple historical orders:

[0170] Method 1: Through decision trees, naive Bayes, support vector machines, and K-nearest neighbors, etc. Use the labeled data as a training set, build a model through a machine learning algorithm, and then apply the model to unlabeled data for classification.

[0171] Method 2: Use K-means clustering and hierarchical clustering methods to perform cluster analysis using unlabeled data sets and group similar data samples.

[0172] Method 3: Combine labeled and unlabeled data for classification. Use labeled data to build a model, then apply the model to unlabeled data for prediction, and further expand the labeled data set.

[0173] Method 4: Obtain multiple label type information through binary association, label combination, algorithm adaptation, ensemble learning, and deep learning.

[0174] S502: Create a tag type model according to multiple tag type information.

[0175] It should be noted that the historical orders are analyzed and a label type model is created, and the created label type model is stored in the storage module 1 .

[0176] It should also be noted that analyzing historical orders and creating label type models are generally completed during the design and development of the entire system.

[0177] S503: Perform tag class object extraction processing on the tag type information in the tag type model to obtain at least one common tag class object corresponding to the tag type model.

[0178] It should be noted that the tag type model is read from the storage module 1 , the tag type information in the tag type model is subjected to tag class object extraction processing to generate a public tag class, and the public tag class is stored in the storage module 2 .

[0179] Optionally, the public label class can be any table such as Table 2 or Table 3; or any specific object in Table 2 and Table 3.

[0180] It should also be noted that the generation of public tag classes is generally performed once when the entire system is initialized.

[0181] The embodiment of the present application obtains multiple tag type information by classifying and processing historical orders, thereby creating a tag type model in advance, which not only realizes the comprehensive and accurate creation of public tag classes, but also facilitates the subsequent call when configuring store menus. Then, the public tag class object is extracted from the tag type model, saving the redundant steps of recreating the tag class when generating store menus for different stores. This improves the configuration efficiency of the store menu.

[0182] Optional, Figure 6 A schematic diagram of a method for processing a dish label provided in an embodiment of the present application Figure 5 ,exist Figure 2 , Figure 3 , Figure 4 and Figure 5 Based on the example, Figure 6 As shown, after S206, the following steps are also included:

[0183] S601: In response to a meal order request, obtain menu information of the store to be configured.

[0184] S602: Generate an ordering interface based on the menu information of the store to be configured.

[0185] S603: In response to the user's ordering operation on the ordering interface, determine the target menu information corresponding to the ordering operation.

[0186] Among them, the ordering operation includes selection and / or input operation.

[0187] S604: Output the target order according to the target menu information.

[0188] It should be noted that when ordering food, label object instances are obtained from the storage module 4 according to the dishes for display, so that the user can select and fill in them to form a specific order.

[0189] It should also be noted that the target order can be sent to the terminal device of the staff so that the staff can view it to avoid errors and make it efficiently; it can also be displayed on the terminal device of the person who takes the order so that the person who takes the order can confirm the order and improve the user experience.

[0190] The embodiment of the present application triggers the ordering operation through the ordering request, directly obtains the menu information of the configured store and generates a menu instance, and presents it in the form of an ordering interface. The merchant only needs to perform simple personalized processing for the store to be configured, and the rest of the menu parts are directly generated according to the menu information, which improves the efficiency of menu configuration. At the same time, through the target menu information corresponding to the user's ordering operation, the target order is generated and output, which realizes active ordering, improves the flexibility of ordering, saves the merchant's one-to-one manual ordering time, avoids the easy error of manual ordering, and improves the efficiency of ordering.

[0191] Figure 7 A schematic diagram of a method for processing a dish label provided in an embodiment of the present application Figure 6 ,exist Figure 2 , Figure 3 , Figure 4 , Figure 5 and Figure 6 Based on the example, Figure 7 As shown, the specific process is as follows:

[0192] S701: Analyze historical orders and create a label type model, and store the created label type model in storage module 1.

[0193] S702: Read the tag type model from storage module 1, perform tag class object extraction processing on the tag type information in the tag type model, generate a public tag class, and store the public tag class in storage module 2.

[0194] S703: Read the standard tag class from storage module 2, perform inheritance modification, generate a personalized tag class, and save the personalized tag class to storage module 3.

[0195] S704: Obtain the dish information to be configured from the store information to be configured, obtain the corresponding personalized label class from the storage module 3 according to the dish information to be configured, modify the personalized label class, create a label object instance, and save it in the storage module 4.

[0196] S705: When ordering food, obtain a label object instance from the storage module 4 according to the food and display it for the user to select and fill in to form a specific order.

[0197] The present application provides a method for processing dish labels, which generates a personalized label class for the store based on a label type model and information of the store to be configured, and automatically creates a personalized menu based on the dishes to be configured and the personalized label class. The menu can be automatically generated based on the store information and dish information, without the need for manual configuration or exhaustive enumeration of a huge number of dish labels each time a menu is generated, and a personalized label class can be generated for each store to be configured, thereby realizing the privatization of the store menu and improving the flexibility of menu processing, the accuracy of the store menu and the configuration efficiency.

[0198] Figure 8 A schematic diagram of a device for processing dish labels provided in an embodiment of the present application is shown in FIG. Figure 8 As shown, the device of the embodiment of the present application includes: a first acquisition module 81, a second acquisition module 82, a first processing module 83, a third acquisition module 84, a second processing module 85 and a generation module 86. The processing device for the dish label here can be the above-mentioned dish label processing system itself, or a chip or integrated circuit that realizes the function of the processing device in the dish label processing system. It should be noted here that the division of the first acquisition module 81, the second acquisition module 82, the first processing module 83, the third acquisition module 84, the second processing module 85 and the generation module 86 is only a division of logical functions, and the two can be physically integrated or independent.

[0199] The first acquisition module is used to acquire a pre-created label type model in response to a menu configuration request;

[0200] The second acquisition module is used to acquire the store information of the store to be configured;

[0201] A first processing module, configured to perform a first label class generation process according to the store information and a pre-created label type model, so as to obtain at least one personalized label class corresponding to the store to be configured;

[0202] The third acquisition module is used to obtain the dish information to be configured;

[0203] The second processing module is used to perform object creation processing according to the dish information to be configured and at least one personalized label class corresponding to the store to be configured, so as to obtain at least one label object corresponding to the store to be configured;

[0204] The generation module is used to generate menu information of the store to be configured according to at least one label object corresponding to the store to be configured.

[0205] Optionally, the first processing module is specifically used for:

[0206] Get at least one common tag class object pre-configured for each tag type model;

[0207] Inherit at least one public tag class object;

[0208] According to the store information, at least one public label class object is modified to obtain at least one personalized label class corresponding to the store to be configured.

[0209] Optionally, the tag type model includes multiple tag type information;

[0210] Accordingly, the first processing module is specifically used for:

[0211] According to the store information and the pre-created label type model, a first label class generation process is performed to obtain at least one personalized label class corresponding to the store to be configured, including:

[0212] According to the store information, match it in the pre-created tag type model to determine the tag type information corresponding to the store information;

[0213] At least one personalized label class corresponding to the store to be configured is generated according to the label type information corresponding to the store information.

[0214] Optionally, before obtaining a pre-created label type model in response to a menu configuration request, the apparatus further includes a model creation module, which is used to:

[0215] Get multiple tag type information;

[0216] Create a tag type model based on multiple tag type information.

[0217] Optionally, after creating a tag type model according to the multiple tag type information, the apparatus further includes a tag type acquisition module, which is used to:

[0218] A tag class object extraction process is performed on the tag type information in the tag type model to obtain at least one common tag class object corresponding to the tag type model.

[0219] Optionally, the model creation module is specifically used to:

[0220] Get multiple historical orders;

[0221] Multiple historical orders are classified and processed to obtain multiple tag type information.

[0222] Optionally, after generating menu information of the store to be configured according to at least one label object corresponding to the store to be configured, the apparatus further includes an ordering module, which is used to:

[0223] In response to the order request, obtain menu information of the store to be configured;

[0224] Generate an ordering interface based on the menu information of the store to be configured.

[0225] Optionally, after generating an ordering interface according to the menu information of the store to be configured, the above device further includes an ordering module for:

[0226] In response to an ordering operation performed by a user on an ordering interface, determining target menu information corresponding to the ordering operation;

[0227] Output the target order according to the target menu information.

[0228] Fig. 9 This is a schematic diagram of a dish label processing device provided in an embodiment of the present application. Fig. 9 As shown, the electronic device 90 includes: at least one processor 91 and a memory 92. The electronic device 90 also includes a communication component 93. The processor 91, the memory 92 and the communication component 93 are connected via a bus 94.

[0229] In the specific implementation process, at least one processor 91 executes the computer execution instructions stored in the memory 92, so that at least one processor 91 executes any one of the dish label processing methods executed by the above-mentioned dish label processing device side.

[0230] The specific implementation process of the processor 91 can refer to the above method embodiment, and its implementation principle and technical effect are similar, so this embodiment will not be repeated here. In the above embodiment, it should be understood that the processor can be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), etc. The general-purpose processor can be a microprocessor or the processor can be any conventional processor, etc. The steps of the method disclosed in the invention can be directly embodied as being executed by a hardware processor, or can be executed by a combination of hardware and software modules in the processor.

[0231] The memory may include a high-speed RAM memory, and may also include a non-volatile storage NVM, such as at least one disk storage.

[0232] The bus may be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus, etc. The bus may be divided into an address bus, a data bus, a control bus, etc. For ease of representation, the bus in the drawings of the present application is not limited to only one bus or one type of bus.

[0233] The functions implemented by the processing device and the main control device for the dish labels are described above, and the scheme provided by the embodiment of the present invention is introduced. It can be understood that in order to realize the above functions, the processing device or the main control device of the dish label includes a hardware structure and / or software module corresponding to the execution of each function. In combination with the units and algorithm steps of each example described in the embodiment disclosed in the embodiment of the present invention, the embodiment of the present invention can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is executed in the form of hardware or computer software driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered to exceed the scope of the technical solution of the embodiment of the present invention.

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

[0235] The computer-readable medium may be included in the dish label processing device; or may exist independently without being assembled into the dish label processing device.

[0236] The computer-readable medium carries one or more programs. When the one or more programs are executed by the dish label processing device, the dish label processing device executes the method shown in the above embodiment.

[0237] Computer program code for performing the operations of the present disclosure may be written in one or more programming languages ​​or a combination thereof, including object-oriented programming languages ​​such as Java, Smalltalk, C++, and conventional procedural programming languages ​​such as "C" or similar programming languages. The program code may be executed entirely on the user's computer, partially on the user's computer, as an independent software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer via any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0238] The flow chart and block diagram in the accompanying drawings illustrate the possible architecture, function and operation of the system, method and computer program product according to various embodiments of the present disclosure. In this regard, each square box in the flow chart or block diagram can represent a module, a program segment or a part of a code, and the module, the program segment or a part of the code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some implementations as replacements, the functions marked in the square box can also occur in a sequence different from that marked in the accompanying drawings. For example, two square boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each square box in the block diagram and / or flow chart, and the combination of the square boxes in the block diagram and / or flow chart can be implemented with a dedicated hardware-based system that performs a specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.

[0239] The units involved in the embodiments described in the present disclosure may be implemented by software or hardware. The name of a unit does not limit the unit itself in some cases. For example, the first acquisition unit may also be described as a "unit for acquiring at least one pre-created tag type model".

[0240] The functions described above herein may be performed at least in part by one or more hardware logic components. For example, without limitation, exemplary types of hardware logic components that may be used include: field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), application specific standard products (ASSPs), systems on chips (SOCs), complex programmable logic devices (CPLDs), and the like.

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

[0242] The dish label processing device of the embodiment of the present application can be used to execute the technical solutions in the above-mentioned method embodiments of the present application. Its implementation principles and technical effects are similar and will not be repeated here.

[0243] An embodiment of the present application also provides a computer-readable storage medium, in which computer-executable instructions are stored. When the computer-executable instructions are executed by a processor, they are used to implement any of the above-mentioned methods for processing dish labels.

[0244] An embodiment of the present application also provides a computer program product, including a computer program, which, when executed by a processor, is used to implement any of the above-mentioned methods for processing dish labels.

[0245] In the several embodiments provided in the present application, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic, for example, the division of modules is only a logical function division, and there may be other division methods in actual implementation, such as multiple modules can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be an indirect coupling or communication connection through some interfaces, devices or modules, which can be electrical, mechanical or other forms.

[0246] The modules described as separate components may or may not be physically separated, and the components shown as modules may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the modules may be selected according to actual needs to implement the solution of this embodiment.

[0247] In addition, each functional module in each embodiment of the present application can be integrated into one processing unit, or each module can exist physically separately, or two or more modules can be integrated into one unit. The above-mentioned module-composed unit can be implemented in the form of hardware or in the form of hardware plus software functional units.

[0248] The above-mentioned integrated module implemented in the form of a software function module can be stored in a computer-readable storage medium. The above-mentioned software function module is stored in a storage medium, including a number of instructions for enabling a computer device (which can be a personal computer, a server, or a network device, etc.) or a processor to perform some steps of the methods of various embodiments of the present application.

[0249] The above storage medium can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic disk or optical disk. The storage medium can be any available medium that can be accessed by a general or special purpose computer.

[0250] An exemplary storage medium is coupled to a processor so that the processor can read information from the storage medium and write information to the storage medium. Of course, the storage medium can also be a component of the processor. The processor and the storage medium can be located in an application specific integrated circuit (ASIC). Of course, the processor and the storage medium can also exist as discrete components in an electronic control unit or a main control device.

[0251] Those skilled in the art can understand that all or part of the steps of implementing the above-mentioned method embodiments can be completed by hardware related to program instructions. The aforementioned program can be stored in a computer-readable storage medium. When the program is executed, the steps of the above-mentioned method embodiments are executed; and the aforementioned storage medium includes: ROM, RAM, disk or optical disk and other media that can store program codes.

[0252] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present application, rather than to limit it. Although the present application has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or replace some or all of the technical features therein with equivalents. However, these modifications or replacements do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of the present application.

Claims

1. A method for processing a dish label, characterized in that: Applicable to computer equipment, including: In response to the menu configuration request, obtaining a pre-created label type model; Get the store information of the store to be configured; Performing a first label class generation process according to the store information and the pre-created label type model to obtain at least one personalized label class corresponding to the store to be configured; Get the dish information to be configured; Performing object creation processing according to the dish information to be configured and at least one personalized label class corresponding to the store to be configured, so as to obtain at least one label object corresponding to the store to be configured; Menu information of the store to be configured is generated according to at least one label object corresponding to the store to be configured.

2. The method according to claim 1, characterized in that The first label class generation process is performed according to the store information and the pre-created label type model to obtain at least one personalized label class corresponding to the store to be configured, including: Obtain at least one common tag class object preconfigured for each of the tag type models; Inheriting the at least one public tag class object; According to the store information, the at least one public label class object is modified to obtain at least one personalized label class corresponding to the store to be configured.

3. The method according to claim 1, characterized in that The tag type model includes multiple tag type information; The first label class generation process is performed according to the store information and the pre-created label type model to obtain at least one personalized label class corresponding to the store to be configured, including: According to the store information, matching is performed in the pre-created tag type model to determine the tag type information corresponding to the store information; At least one personalized label class corresponding to the store to be configured is generated according to the label type information corresponding to the store information.

4. The method according to any one of claims 1 to 3, characterized in that: Before obtaining the pre-created label type model in response to the menu configuration request, the method further includes: Get multiple tag type information; A tag type model is created according to the multiple tag type information.

5. The method according to claim 4, characterized in that After creating a tag type model according to the plurality of tag type information, the method further includes: A tag class object extraction process is performed on the tag type information in the tag type model to obtain at least one common tag class object corresponding to the tag type model.

6. The method according to claim 4, characterized in that The obtaining of multiple tag type information includes: Get multiple historical orders; The multiple historical orders are classified to obtain multiple label type information.

7. The method according to any one of claims 1 to 3, characterized in that: After generating menu information of the store to be configured according to at least one label object corresponding to the store to be configured, the method further includes: In response to the order request, obtaining menu information of the store to be configured; Generate an ordering interface based on the menu information of the store to be configured.

8. The method according to claim 7, characterized in that After generating an ordering interface according to the menu information of the store to be configured, the method further includes: In response to an ordering operation performed by a user on the ordering interface, determining target menu information corresponding to the ordering operation; Output a target order according to the target menu information.

9. A device for processing dish labels, characterized in that: include: A first acquisition module, configured to acquire a pre-created label type model in response to a menu configuration request; The second acquisition module is used to acquire the store information of the store to be configured; A first processing module, configured to perform a first label class generation process according to the store information and the pre-created label type model, so as to obtain at least one personalized label class corresponding to the store to be configured; The third acquisition module is used to obtain the dish information to be configured; A second processing module is used to perform object creation processing according to the dish information to be configured and at least one personalized label class corresponding to the store to be configured, so as to obtain at least one label object corresponding to the store to be configured; A generation module is used to generate menu information of the store to be configured according to at least one label object corresponding to the store to be configured.

10. A dish label processing device, characterized in that: include: at least one processor; and a memory communicatively coupled to the at least one processor; The memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor so that the at least one processor can execute the method for processing a dish label as described in any one of claims 1 to 8.

11. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer-executable instructions, which, when executed by a processor, are used to implement the method for processing a dish label according to any one of claims 1 to 8.

12. A computer program product, comprising a computer program, characterized in that When the computer program is executed by a processor, the method for processing a dish label according to any one of claims 1 to 8 is implemented.

Images