CN112732366B

CN112732366B - Small program starting system, method and device based on graphic code

Info

Publication number: CN112732366B
Application number: CN202110337281.XA
Authority: CN
Inventors: 严飞; 蒋娇; 陈海港; 胡环康
Original assignee: Zhejiang Koubei Network Technology Co Ltd
Current assignee: Zhejiang Koubei Network Technology Co Ltd
Priority date: 2021-03-30
Filing date: 2021-03-30
Publication date: 2021-08-31
Anticipated expiration: 2041-03-30
Also published as: CN112732366A

Abstract

One or more embodiments of the present specification provide a system, a method, and an apparatus for starting an applet based on a graphic code. The method is applied to a graphic code management server; the method comprises the following steps: receiving graphic code information and applet information which are sent by a merchant client in an associated mode, and creating an information mapping relation between the graphic code information and the applet information; the graphic code information is obtained by analyzing a graphic code by the merchant client, the applet information is specified by a merchant for at least one merchant applet, and the merchant applet of the merchant is issued to the user client in advance; and determining target small program information corresponding to target graphic code information contained in an information acquisition request initiated by the user client according to the information mapping relation, wherein the information acquisition request is generated by the user client according to the target graphic code information obtained by analyzing a graphic code, and the target small program information is used for indicating the user client to start a target merchant small program which is issued in advance.

Description

Small program starting system, method and device based on graphic code

Technical Field

One or more embodiments of the present disclosure relate to the field of computer technologies, and in particular, to a system, a method, and an apparatus for starting an applet based on a graphic code.

Background

A Mini Program (Mini Program) is an application that can be used without downloading and installing, does not need to be manually installed in an operating system, and is generally run by relying on an application installed on a user terminal, and a user can open an application by scanning or searching for the applet. For users, the small program can save the use time cost and the storage space of the mobile terminal; for developers, applets can save development and promotion costs. The graphic code is a pattern which is distributed by a plurality of specific geometric figures according to a certain rule to record information, and the terminal equipment can start the small program by scanning the graphic code recorded with the related information of the small program.

In order to transfer the service provided by the physical store for the user to the online state, a merchant can paste a graphic code in the physical store, so that the user who enters the store can recognize the graphic code through a user client and start a merchant applet, the applet can display a function page related to the physical store, and the user can conveniently enjoy online services such as ordering, payment and the like aiming at the physical store in the function page.

Disclosure of Invention

In view of this, one or more embodiments of the present disclosure provide a system, a method and an apparatus for starting an applet based on a graphic code.

To achieve the above object, one or more embodiments of the present disclosure provide the following technical solutions:

according to a first aspect of one or more embodiments of the present specification, there is provided a small program starting system of a graphic code, including: the merchant client analyzes the graphic code information contained in the graphic code, determines the applet information of at least one merchant applet appointed by the merchant, and associates the graphic code information and the applet information to send to the graphic code management server, wherein the merchant applet of the merchant is issued to the user client in advance;

the graphic code management server side is used for creating an information mapping relation between the graphic code information and the small program information, and the information mapping relation is used for determining target small program information corresponding to target graphic code information contained in an information acquisition request initiated by the user client side;

the user client analyzes the graphic code to obtain the target graphic code information and generates the information acquisition request according to the target graphic code information; and starting a pre-issued target merchant applet according to the determined target applet information.

Optionally, the method further includes:

the application server receives the information mapping relation sent by the graphic code management server; and responding to the information acquisition request initiated by the user client, determining target small program information corresponding to the target graphic code information according to the information mapping relation, and returning the target small program information to the user client.

According to a second aspect of one or more embodiments of the present specification, a method for starting an applet based on a graphic code is provided, which is applied to a graphic code management server; the method comprises the following steps:

receiving graphic code information and applet information which are sent by a merchant client in an associated mode, and creating an information mapping relation between the graphic code information and the applet information; the graphic code information is obtained by analyzing a graphic code by the merchant client, the applet information is specified by a merchant for at least one merchant applet, and the merchant applet of the merchant is issued to the user client in advance;

and determining target small program information corresponding to target graphic code information contained in an information acquisition request initiated by the user client according to the information mapping relation, wherein the information acquisition request is generated by the user client according to the target graphic code information obtained by analyzing a graphic code, and the target small program information is used for indicating the user client to start a target merchant small program which is issued in advance.

Optionally, the method further includes:

obtaining order placing information determined by the user client in response to an order placing operation implemented by the user through the target merchant applet;

and generating and outputting a target order according to the order placing information.

Optionally, the graphic code information includes a primary graphic code identifier and a secondary graphic code identifier;

the creating of the information mapping relationship between the graphic code information and the applet information includes: creating a first mapping relation between the primary graphic code identifier and the applet information;

the method further comprises the following steps: under the condition that the secondary graphic code identification is the global identification, creating a second mapping relation between the secondary graphic code identification contained in the graphic code information and the shop related information appointed by the merchant; or under the condition that at least part of the plurality of secondary graphic code identifications corresponding to different primary graphic code identifications are the same, creating a second mapping relation among the primary graphic code identifications, the secondary graphic code identifications and the store related information appointed by the merchant, wherein the primary graphic code identifications and the secondary graphic code identifications are contained in the graphic code information; the second mapping relationship is used for determining the relevant information of the target store corresponding to the target graphic code information contained in the information acquisition request.

Optionally, the method further includes:

locally maintaining the created first mapping relation for responding to the information acquisition request; or sending the created first mapping relation to an application server side so that the application server side responds to the information acquisition request; and/or the presence of a gas in the gas,

the second mapping relation established in local maintenance is used for determining the target store information; or sending the created second mapping relation to an application server, so that the application server determines the target store information.

Optionally, the outputting the target order includes at least one of:

sending the target order to the user client side so that the user client side can display the target order to the user;

sending the target order to the merchant client so that the merchant client displays the target order to the merchant and/or counts the target order;

and sending the target order to a business acceptance terminal deployed in an entity store of the merchant, so that the payment terminal executes corresponding business acceptance operation according to the target order, wherein the business acceptance operation comprises order printing operation and/or collection operation.

Optionally, the graphic code further includes a graphic code address, where the graphic code address is used to indicate the merchant client to start an information-specifying page, and the information-specifying page is used to collect applet information of at least one merchant applet specified by a merchant.

According to a third aspect of one or more embodiments of the present specification, a method for starting an applet based on a graphic code is provided, which is applied to a merchant client; the method comprises the following steps:

analyzing the graphic code information contained in the graphic code;

determining applet information of at least one merchant applet designated by a merchant, the merchant applet of the merchant being issued to a user client in advance;

the graphic code information and the applet information are sent to a graphic code management server side in an associated mode, so that an information mapping relation between the graphic code information and the applet information is established by the graphic code management server side; the information mapping relation is used for determining target small program information corresponding to target graphic code information contained in an information acquisition request initiated by the user client, the information acquisition request is generated by the user client according to the target graphic code information obtained by analyzing a graphic code, and the target small program information is used for indicating the user client to start a target merchant small program which is issued in advance.

Optionally, the merchant client scans the graphic code through a native graphic code recognition program or a graphic code management applet provided by the graphic code management server.

Optionally, the determining the applet information of at least one merchant applet designated by a merchant includes:

analyzing a graphic code address contained in the graphic code, starting an information designation page according to the graphic code address, and displaying an information designation component for at least one business home program issued to the user client by a business in the information designation page;

and in the case of detecting the triggering operation aiming at the information specifying component, taking the applet identification of at least one merchant applet corresponding to the triggered information specifying component as the applet information specified by the merchant.

Optionally, the method further includes:

starting an information entry page according to a secondary graphic code identifier contained in the graphic code information, and displaying an information entry component aiming at an entity store corresponding to the merchant in the information entry page;

under the condition that the entry operation aiming at the information entry component is detected, acquiring the entered store related information, and sending a secondary graphic code identifier contained in the graphic code information and the store related information appointed by the merchant to the graphic code management server in an associated manner, so that under the condition that the secondary graphic code identifier is a global identifier, the graphic code management server creates a second mapping relation between the secondary graphic code identifier contained in the graphic code information and the store related information appointed by the merchant; or, the graphic code management server creates a second mapping relationship between the primary graphic code identifier and the secondary graphic code identifier contained in the graphic code information and the relevant information of the store appointed by the merchant under the condition that at least parts of the plurality of secondary graphic code identifiers corresponding to different primary graphic code identifiers are the same; the second mapping relationship is used for determining the relevant information of the target store corresponding to the target graphic code information contained in the information acquisition request.

According to a fourth aspect of one or more embodiments of the present specification, a method for starting an applet based on a graphic code is provided, which is applied to a user client; the method comprises the following steps:

analyzing target graphic code information contained in a graphic code, and generating an information acquisition request according to the target graphic code information;

acquiring target small program information corresponding to the target graphic code information determined according to the information mapping relation and responding to the information acquisition request, and starting a target merchant small program which is issued in advance according to the target small program information; the information mapping relation is established by the graphic code management service terminal according to graphic code information and applet information sent by a merchant client, the graphic code information is obtained by analyzing a graphic code by the merchant client, the applet information is appointed by a merchant for at least one merchant applet, and the merchant applet of the merchant is issued to the user client in advance.

Optionally, the method further includes:

and determining ordering information in response to an ordering operation implemented by the user through the target merchant applet, wherein the ordering information is used by the graphic code management server side for generating and outputting a target order.

According to a fifth aspect of one or more embodiments of the present specification, a graphic code recognition apparatus is provided, which is applied to a graphic code management server; the device comprises:

the information receiving unit is used for receiving graphic code information and applet information which are sent by a merchant client in a correlation manner and creating an information mapping relation between the graphic code information and the applet information; the graphic code information is obtained by analyzing a graphic code by the merchant client, the applet information is specified by a merchant for at least one merchant applet, and the merchant applet of the merchant is issued to the user client in advance;

and the information determining unit is used for determining target small program information corresponding to target graphic code information contained in an information acquisition request initiated by the user client according to the information mapping relation, wherein the information acquisition request is generated by the user client according to the target graphic code information obtained by analyzing a graphic code, and the target small program information is used for indicating the user client to start a target merchant small program which is issued in advance.

Optionally, the method further includes:

the information acquisition unit is used for acquiring order placing information determined by the user client in response to an order placing operation implemented by the user through the target merchant applet;

and the order generating unit generates and outputs the target order according to the order placing information.

the information receiving unit is further configured to: creating a first mapping relation between the primary graphic code identifier and the applet information;

the device also comprises a mapping establishing unit, wherein under the condition that the secondary graphic code identification is the global identification, a second mapping relation between the secondary graphic code identification contained in the graphic code information and the shop related information appointed by the merchant is established; or under the condition that at least part of the plurality of secondary graphic code identifications corresponding to different primary graphic code identifications are the same, creating a second mapping relation among the primary graphic code identifications, the secondary graphic code identifications and the store related information appointed by the merchant, wherein the primary graphic code identifications and the secondary graphic code identifications are contained in the graphic code information; the second mapping relationship is used for determining the relevant information of the target store corresponding to the target graphic code information contained in the information acquisition request.

Optionally, the method further includes:

the first maintenance unit locally maintains the created first mapping relation and is used for responding to the information acquisition request; or sending the created first mapping relation to an application server side so that the application server side responds to the information acquisition request; and/or the presence of a gas in the gas,

the second maintenance unit is used for locally maintaining the created second mapping relation and determining the information of the target store; or sending the created second mapping relation to an application server, so that the application server determines the target store information.

Optionally, the order generating unit is further configured to at least one of:

According to a sixth aspect of one or more embodiments of the present specification, there is provided a pattern code recognition apparatus, applied to a merchant client; the device comprises:

the information analysis unit is used for analyzing the graphic code information contained in the graphic code;

the information determining unit is used for determining the applet information of at least one merchant applet appointed by a merchant, wherein the merchant applet of the merchant is issued to the user client in advance;

the information sending unit is used for sending the graphic code information and the applet information to a graphic code management server in an associated mode so as to create an information mapping relation between the graphic code information and the applet information by the graphic code management server; the information mapping relation is used for determining target small program information corresponding to target graphic code information contained in an information acquisition request initiated by the user client, the information acquisition request is generated by the user client according to the target graphic code information obtained by analyzing a graphic code, and the target small program information is used for indicating the user client to start a target merchant small program which is issued in advance.

Optionally, the graphic code information includes a primary graphic code identifier and a secondary graphic code identifier, the information mapping relationship is a first mapping relationship between the information graphic code identifier and the applet information, and the information determining unit is further configured to:

Optionally, the method further includes:

the information entry unit starts an information entry page according to a secondary graphic code identifier contained in the graphic code information, and displays an information entry component aiming at the entity store corresponding to the merchant in the information entry page;

the store information acquisition unit is used for acquiring the entered store related information under the condition that the entry operation aiming at the information entry component is detected, and sending a secondary graphic code identifier contained in the graphic code information and the store related information appointed by the merchant to the graphic code management service terminal in an associated manner, so that a second mapping relation between the secondary graphic code identifier contained in the graphic code information and the store related information appointed by the merchant is established under the condition that the secondary graphic code identifier is a global identifier by the graphic code management service terminal; or, the graphic code management server creates a second mapping relationship between the primary graphic code identifier and the secondary graphic code identifier contained in the graphic code information and the relevant information of the store appointed by the merchant under the condition that at least parts of the plurality of secondary graphic code identifiers corresponding to different primary graphic code identifiers are the same; the second mapping relationship is used for determining the relevant information of the target store corresponding to the target graphic code information contained in the information acquisition request.

According to a seventh aspect of one or more embodiments of the present specification, a graphic code recognition apparatus is provided, which is applied to a user client; the device comprises:

the request generating unit is used for analyzing the target graphic code information contained in the graphic code and generating an information acquisition request according to the target graphic code information;

the small program jumping unit is used for acquiring target small program information corresponding to the target graphic code information determined according to the information mapping relation and responding to the information acquisition request, and starting a target merchant small program which is issued in advance according to the target small program information; the information mapping relation is established by the graphic code management service terminal according to graphic code information and applet information sent by a merchant client, the graphic code information is obtained by analyzing a graphic code by the merchant client, the applet information is appointed by a merchant for at least one merchant applet, and the merchant applet of the merchant is issued to the user client in advance.

Optionally, the method further includes:

and the ordering information determining unit is used for responding to ordering operation implemented by the user through the target merchant applet and determining ordering information, and the ordering information is used by the graphic code management server side for generating and outputting a target order.

According to an eighth aspect of one or more embodiments herein, there is provided an electronic apparatus, comprising:

a processor;

a memory for storing processor-executable instructions;

wherein the processor executes the executable instructions to implement the small program starting method based on the graphic code as described in any one of the above embodiments.

According to a ninth aspect of one or more embodiments of the present specification, there is provided a computer readable storage medium having stored thereon computer instructions which, when executed by a processor, implement the steps of the graphic code based applet launching method as described in any one of the above embodiments.

According to the scheme, the user client can start the pre-issued merchant applet. The merchant client can determine the graphic code information by scanning the graphic code and acquire the applet information designated by the merchant, the graphic code management server can generate an information mapping relation according to the graphic code information and the applet information sent by the merchant client, and the target applet information determined according to the information mapping relation can be used for indicating the user client to start the target merchant applet.

Through the scheme, a popularizing personnel of the graphic code can print the physical material of the graphic code in advance without acquiring information of a merchant, and after the graphic code is pasted in the physical store, the merchant of the physical store can activate the graphic code to start the small program of the merchant only by implementing binding operation through a merchant client to bind the graphic code and the small program information of the physical store. Compared with the related scheme of printing and paving the entity material of the graphic code according to the pre-acquired merchant information, the scheme effectively reduces the interaction times between the popularizing personnel and the merchant through the graphic code of the pre-printed uniform format, thereby simplifying the popularization operation, improving the paving and pasting efficiency of the graphic code and being beneficial to reducing the popularization cost of the graphic code.

Drawings

Fig. 1 is a schematic architecture diagram of an applet starting system based on a graphic code according to an exemplary embodiment.

Fig. 2 is a flowchart of an activation process of a graphic code according to an exemplary embodiment.

Fig. 3 is a flowchart of an applet starting method based on a graphic code according to an exemplary embodiment.

Fig. 4 is a flowchart of another small program starting method based on graphic codes according to an exemplary embodiment.

Fig. 5 is a flowchart of another small program starting method based on a graphic code according to an exemplary embodiment.

Fig. 6 is an interaction diagram of an applet starting method based on a graphic code according to an exemplary embodiment.

FIG. 7A is a binding hints page schematic of a merchant applet as provided in an exemplary embodiment.

Fig. 7B is a schematic diagram of a binding hint page for another merchant applet as provided in an exemplary embodiment.

FIG. 8A is a schematic diagram of an information-bearing page for a merchant applet as provided in an exemplary embodiment.

FIG. 8B is a diagram illustrating a binding result for a merchant applet, according to an illustrative embodiment.

FIG. 9 is a schematic view of an information entry page for a merchant applet as provided in an exemplary embodiment.

Fig. 10 is a schematic structural diagram of an electronic device according to an exemplary embodiment.

Fig. 11 is a block diagram of an applet starting apparatus based on graphic codes according to an exemplary embodiment.

Fig. 12 is a block diagram of another applet launching device based on graphic codes according to an exemplary embodiment.

Fig. 13 is a block diagram of another applet starting apparatus based on graphic codes according to an exemplary embodiment.

Detailed Description

Reference will now be made in detail to the exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, like numbers in different drawings represent the same or similar elements unless otherwise indicated. The implementations described in the following exemplary embodiments do not represent all implementations consistent with one or more embodiments of the present specification. Rather, they are merely examples of apparatus and methods consistent with certain aspects of one or more embodiments of the specification, as detailed in the claims which follow.

It should be noted that: in other embodiments, the steps of the corresponding methods are not necessarily performed in the order shown and described herein. In some other embodiments, the method may include more or fewer steps than those described herein. Moreover, a single step described in this specification may be broken down into multiple steps for description in other embodiments; multiple steps described in this specification may be combined into a single step in other embodiments.

In the related art, when a graphic code is promoted to an offline entity store, a promoter often needs to visit a merchant to collect store information of the entity store, then the store information collected offline is printed on an entity material as graphic code information, and the entity material such as a table sticker, a table card and the like only suitable for the entity store is produced and obtained, and further the produced entity material is paved at a proper position of the entity store, so that a complete graphic code promotion process is realized.

However, since the actually printed graphic code information in the solid material corresponds to the solid store (i.e. store information of the solid store), the popularizing personnel needs to acquire the store information first, and complete graphic code popularizing process can be completed after completing the processes of printing, paving and pasting materials and the like in sequence, which leads to a complicated popularizing process of the graphic code, long time consumption and low popularizing efficiency.

To this end, the embodiment of this specification proposes a popularization scheme of a prefabricated code: the graphic code with the uniform format and irrelevant to the physical store is printed in advance, and then the merchant scans the code by using the merchant client to bind the prefabricated code with the merchant applet of the physical store after the paving is finished, so that the popularization process of the graphic code (namely the prefabricated code) is finished. Furthermore, after the merchant binding is completed, the user who enters the store for consumption can utilize the user client to scan the graphic code and implement the order placing operation in the jumped merchant applet, so that the order corresponding to the order placing operation of the user can be generated through the cooperation of the user client and the graphic code management server and other related parties, namely the user can realize the online order placing through scanning the graphic code.

Just because the graphic code information contained in the graphic code in the scheme is irrelevant to the entity store before binding, the entity material of the graphic code can be printed in advance. In the promotion process, a promotion person only needs to lay and paste the manufactured solid materials in a solid store and guide a merchant to finish binding, so that the promotion process can be realized, the promotion flow is obviously simplified, the promotion duration is shortened, and the promotion efficiency of the graphic code is promoted. This scheme is explained in detail below by means of specific examples.

Fig. 1 is a schematic architecture diagram of an applet starting system based on a graphic code according to an exemplary embodiment. As shown in fig. 1, the system may include a graphic code management server 11, an application server 12, an electronic device (e.g., a mobile phone 13) used by a merchant in a physical store, an electronic device (e.g., a mobile phone 14) used by a user in the physical store, a service acceptance terminal (e.g., a POS machine 15) provided in the physical store, and a network 10.

The graphic code management server 11 and the application server 12 may be physical servers including an independent host, or may also be virtual servers carried by a host cluster. In the operation process, the server may operate a server-side program of a certain application to serve as a corresponding server to implement a related service function of the application. For example, the graphic code management server 11 may run a server-side program of the graphic code management platform to implement a graphic code management server of the graphic code management platform; the application server 12 may run a server-side program of a user client used by the user to implement as a server for the application program.

Cell phones 13-14 represent one type of electronic device that may be used by merchants and users. Indeed, electronic devices of the type such as the following may also be used: tablet devices, notebook computers, Personal Digital Assistants (PDAs), wearable devices (e.g., smart glasses, smart watches, etc.), etc., which are not limited by one or more embodiments of the present disclosure. During operation, the electronic device may run a client-side program of an application to implement a related service function of the application. For example, the cell phone 13 may run a client-side program of a merchant to implement as a merchant client; accordingly, the handset 14 may run a client-side program of the user to be implemented as a user client.

The network 10 may include various types of wired or wireless networks. For example, the Network 10 may include the Public Switched Telephone Network (PSTN) and the Internet (Internet). The graphic code management server 11 and the mobile phones 13 to 14, the application server 12 and the mobile phones 13 to 14, and the graphic code management server 11 and the application server 12 can establish long connection through the network 10 for communication.

Certainly, through cooperation between relevant parties in the applet starting system, the system can also implement other functions related to the merchant applet, such as commodity shopping, order generation, order payment, consumption evaluation, besides the starting of the merchant applet, and this is not limited in the embodiments of this specification.

Based on the architecture of the applet starting system, the description provides an applet starting system based on a graphic code, which comprises a merchant client, a graphic code management server and a user client.

The merchant client analyzes the graphic code information contained in the graphic code, determines the applet information of at least one merchant applet appointed by a merchant, and associates the graphic code information and the applet information to send to the graphic code management server, wherein the merchant applet of the merchant is issued to the user client in advance;

the graphic code management server side is used for creating an information mapping relation between the graphic code information and the small program information, and the information mapping relation is used for determining target small program information corresponding to the target graphic code information contained in an information acquisition request initiated by a user client side;

the user client analyzes the graphic code to obtain target graphic code information, and generates an information acquisition request according to the obtained target graphic code information; and starting the pre-issued target merchant applet according to the determined target applet information.

It should be noted that the graphic codes involved in the processing processes of the merchant client, the graphic code management server and the user client in the system are all graphic codes to be pasted or completed in the physical store (i.e. the prefabricated codes); in other words, the above processing processes involved by the parties in the system are performed on the physical materials of the graphic codes which are already pasted or to be pasted in the physical store.

In addition, the system can also comprise an application server side for receiving the information mapping relation sent by the graphic code management server side; and responding to the information acquisition request initiated by the user client, determining target small program information corresponding to the target graphic code information according to the information mapping relation, and returning the target small program information to the user client.

The following describes the promotion and use process of the graphic code realized by the applet starting system with reference to fig. 2.

Referring to fig. 2, fig. 2 is a flowchart illustrating an activation process of a graphic code according to an exemplary embodiment. As shown in fig. 2, the method may include the steps of:

step 202, preprinting the physical material of the graphic code.

In the order generation scheme of the present specification, a graphic code may be pre-printed by a promoter of the graphic code, for example, the promoter may pre-generate graphic code data including a graphic code address, first graphic code information, and second graphic code information according to a preset rule, and print the graphic code according to the data by itself; alternatively, a plurality of popularizing personnel can submit the generated graphic code data to the same printing party to print the graphic code uniformly, which is not limited in this specification. In order to reduce logistics cost of graphic code materials, corresponding physical stores to be promoted can be divided according to regions, for example, the regions are divided according to multiple dimensions of communities, commercial districts, cities, countries and the like, and different promoting personnel are used for promoting graphic codes to the physical stores in different regions. And for any graphic code, printing the graphic code according to the data, namely printing the generated graphic code data on the entity material according to a preset graphic format, thereby forming the graphic code on the entity material. The printed graphic code can be scanned and the information contained in the graphic code can be analyzed through the client with the graphic code identification function, so that the identification of the graphic code is realized.

The graphic Code related to the order generation scheme in the present specification may be in various forms such as a bar Code, a two-dimensional Code (or QR Code), and a three-dimensional Code. Taking a two-dimensional Code as an example, the two-dimensional Code can adopt various standards such as Data Matrix, MaxiCode, Aztec, QR Code, PDF417 and the like; the solid material may be paper, plastic, metal, etc., and the printing form of the graphic code may be a one-dimensional form, a two-dimensional planar form, a three-dimensional form, etc., which is not limited in this specification.

In addition, the graphic codes can be printed according to groups, for example, the graphic code data can be generated according to two-stage identification combination of code groups and code values, and then the entity materials of the graphic codes are printed according to the graphic code data. The code group may correspond to a primary graphic code identifier in this specification, and the code value may correspond to a secondary graphic code identifier in this specification. For example, the graphic code data recorded in the printed graphic code may follow the following URL rule "", where "XXX" may be an instance name of a graphic code management instance created by the graphic code management server; "https:// aaa.XXX.com/pre" is a graphic code address for instructing a merchant client to jump to a specified page for merchant applet information; the code values may be globally unique identifiers, or there may be a plurality of code groups corresponding to different code groups respectively, which are partially identical (i.e. the code values are globally non-unique), and thus, the above code values, or a combination of code groups and code values is used to uniquely characterize the graphic code. After the merchant client identifies any code group of the graphic code, the merchant client can jump to an information designated page of the merchant applet for the merchant to designate the applet information of the merchant applet in the page, so as to realize the binding of the merchant applet; after the merchant client identifies the code value of any graphic code, the merchant client can jump to an information entry page corresponding to the entity store under the condition that the merchant applet information is acquired, so that the merchant can enter store related information of the entity store in the page, and the merchant related information is bound. After the user client identifies the code group of the target graphic code, the merchant applet bound by the code group can be started, so that the user can enjoy the online service of the merchant through the applet; after the user client identifies the code value of any graphic code, the code value and order placing information corresponding to order placing operation implemented by the user can be sent to the graphic code management server in an associated mode, and therefore an order containing relevant store information corresponding to the code value is generated. For the specific use process of the code groups and code values, reference may be made to the following detailed description of the embodiments, which is not repeated herein.

In addition, the code group and the code value may be numbers or random codes, or tokens (or tokens) generated according to the data or the random codes, and the description does not limit this.

Taking the case that a plurality of code groups respectively corresponding to different code groups have the same part, and the code group and the code value are token as an example, the corresponding graphic code data can be referred to the following table 1.

In table 1, the code group and the code value are recorded in the graphic code URL corresponding to any code value in any code group. And a graphic code URL corresponding to any code group may be used to print a graphic code (i.e., one row in table 1 corresponds to one graphic code).

In order to better meet the quantity requirements of physical stores with different scales on graphic codes, various material specifications can be formulated in advance, for example, different specifications correspond to different quantities of physical materials. Each code group at least corresponds to a code value, that is, at least one graphic code can be printed on the physical material, obviously, each graphic code corresponding to any code group has the same code group and different code values. And a plurality of graphic codes respectively belonging to different groups, having different code groups, may have the same code value (not all locally unique code values) or different code values (globally unique code values). The pre-specified material specifications can be seen in table 2 below:

taking the material specification shown in table 2 as an example, if a certain small-scale physical store has 10 dining tables and needs the table subsides, then can adopt a set of material group that contains 10 table subsides and 1 platform card to spread and paste, if a certain larger-scale physical store has 70 dining tables and needs the table subsides, then can adopt two sets of material groups that contain 10 table subsides and 1 platform card to and a set of material group that contains 50 table subsides and 5 platform cards to spread and paste. Obviously, the materials with different specifications are flexibly combined, so that different material requirements of stores with different scales can be met, and the waste of the materials when only the materials with the single specification are adopted for paving is avoided.

And step 204, paving the physical material of the graphic code at a physical store corresponding to the merchant.

After the entity materials of the graphic codes are printed, the popularizing personnel can lay and paste the entity materials in the entity stores corresponding to the merchants in the popularizing process, for example, the entity materials are placed in the front desk of the entity stores, are pasted on the dining table in the entity stores, are placed in the rooms in the entity stores, are pasted in the display areas of the sold commodities in the entity stores, and the like, and the embodiment of the specification does not limit the situation. In addition, a service acceptance terminal such as a Point of sale (POS) machine may be installed in the physical store to complete acceptance of a service related to an order, such as printing an order, collecting a money of the order, and the like.

Since the physical material to be laid is printed with the graphic code, the process of laying the physical material is the process of laying the graphic code, which is described below as the laying graphic code.

At step 206, the merchant scans and activates the graphical code through the merchant client.

After the laying is finished, the merchant is required to scan the graphic code through the merchant client to designate the applet information and input store related information of the entity store, so that the graphic code is activated. And the process of activating the graphic code is a process of binding the graphic code information contained in the graphic code with the merchant applet and store related information. For a specific activation process, reference may be made to the following detailed description of the embodiments, which is not repeated herein.

In step 208, the user scans the activated graphic code through the user client to start the merchant applet.

After a merchant activates a graphic code laid in an entity store, a user who enters the store for consumption can scan a certain graphic code through a user client, so that the user client starts a merchant applet to display related information of goods or services of the entity store to the user, and the user can purchase the goods or enjoy other online services and the like.

Referring to fig. 3, fig. 3 is a flowchart of an applet starting method based on a graphic code according to an exemplary embodiment. As shown in fig. 3, the method is applied to a graphic code management server, and may include the following steps:

step 302, receiving graphic code information and applet information which are sent by a merchant client in a correlation manner, and creating an information mapping relation between the graphic code information and the applet information; the graphic code information is obtained by analyzing a graphic code by the merchant client, the applet information is specified by a merchant for at least one merchant applet, and the merchant applet of the merchant is issued to the user client in advance;

and step 304, the information mapping relationship is used for determining target applet information corresponding to target graphic code information contained in an information acquisition request initiated by the user client, the information acquisition request is generated by the user client according to the target graphic code information obtained by analyzing a graphic code, and the target applet information is used for indicating the user client to start a target merchant applet which is issued in advance.

In this embodiment, a merchant may register, through a merchant client, information related to a physical store, such as brand information, commodity-related information, activity-related information, and the like, on a corresponding e-commerce platform. Taking the commodity-related information of the commodities sold in the physical store as an example, the commodity-related information is registered, namely the commodity-related information is put on the e-commerce platform. For example, the commodity-related information may be commodity information (price, commodity specification parameters, style, etc.) of a commodity sold by a merchant, commodity sales information (such as a time period for putting the commodity on shelf, specific contents of a commodity sales activity, etc.), store information (a store name, an address, business hours, etc.) of the merchant, and the like. Of course, the merchant may cooperate with a plurality of e-commerce platforms, so that the merchant client corresponding to each e-commerce platform registers the commodity-related information of the store at the corresponding e-commerce platform. For example, the relevant information of the goods registered by the merchant is bound with the merchant account of the merchant on the corresponding e-commerce platform.

In this embodiment, a developer of the software platform may develop a graphic code recognition program integrated in a merchant client program, or develop a graphic code management applet that operates with the merchant client program as a carrier, and develop a corresponding user applet that operates with the user client program as a carrier. For example, the merchant client may be a merchant-side application corresponding to each e-commerce platform, and the user client may be a buyer-side application corresponding to each e-commerce platform, or a user-side application corresponding to each payment platform. Of course, this description is not intended to be limiting.

In addition, developers of the software platform can also develop small business programs which operate by taking the user client programs as carriers, and the small business programs can be used for providing related functions such as commodity inquiry, order placing, order inquiry and display, order payment and the like for users. And the merchant applet may be pre-published to the user client so that a user entering a physical store for consumption may initiate the merchant applet by scanning the graphical code.

In this embodiment, for a graphic code posted in a brick and mortar store, the merchant may scan in a variety of ways to bind it with the merchant applet. For example, in a case where a native graphic code recognition program provided by the graphic code management service is integrated in the merchant client, the merchant may scan the graphic code in the merchant client through the native graphic code recognition program. Because the native program integrated in the merchant client generally has good running stability, the method can ensure the stability of graphic code identification and avoid the occurrence of code scanning failure as much as possible. Or, in a case that a graphic code management applet is integrated in a merchant client (that is, the graphic code management applet takes the merchant client as a carrier), the merchant may scan the graphic code through the graphic code management applet. By the mode, developers can flexibly and conveniently develop and adjust the functions of the small programs, and can correspondingly adjust the functions of the graphic code management small programs according to actual conditions such as the program versions of the merchant clients, so that richer and diversified graphic code management functions can be realized conveniently.

In this embodiment, after scanning the graphic code, the merchant client may analyze the graphic code to obtain information contained therein, such as address information of the graphic code, and the like. For example, the above-mentioned graphic code may include a graphic code address, so that after the merchant client analyzes the graphic code address, the information-specifying page indicated by the address may be started, and then the applet information of at least one merchant applet specified by the merchant is determined in the page. The information-specific page may be a native page of a merchant client, an applet page of a graphic code management applet issued to the merchant client, a browser webpage, or the like, which is not limited in this specification.

Further, after the information-specifying page is started, the merchant client may display, in the page, an information-specifying component for at least one merchant applet that has been issued to the user client by the merchant, so that the merchant may perform preset triggering operations such as clicking, long-pressing, and the like for the information-specifying component; correspondingly, the merchant client may use the applet identifier of the at least one merchant applet corresponding to the triggered information specification component as the applet information specified by the merchant in the case that the triggering operation is detected. After the graphic code address is analyzed, the merchant client can automatically detect the merchant applet corresponding to the currently logged-in merchant account, and display the information specifying component corresponding to the detected merchant applet in the page for the merchant to specify. Or, under the condition that it is detected that the current merchant account is not logged in, the merchant client may start a login page of the merchant account after analyzing the graphic code address, and further start an information designation page after the merchant completes the login of the merchant account. In addition, under the condition that it is detected that a certain merchant applet is not yet published to the user client, the merchant client may also display a publishing skip component for the merchant applet in an information specifying page, so that, under the condition that it is detected that the merchant triggers the component, the publishing page of the merchant applet is started, and after the merchant completes publishing for the merchant applet (successfully publishes the merchant applet to the user client), the information specifying page is skipped back (of course, under the condition that publishing is successful, the publishing component for the merchant applet is no longer displayed in the information specifying page that is skipped back). It is understood that the applet information specified by the merchant for a certain merchant applet may be an applet identifier, such as an applet id of the merchant applet maintained at the graphic code management service end, a combination of the applet id and the merchant id, and the like, and this specification does not limit this.

In this embodiment, the graphic code information obtained by the merchant client scanning and analyzing the graphic code may include a primary graphic code identifier (such as the foregoing code group) and a secondary graphic code identifier (such as the foregoing code value), so that the merchant server may associate the first graphic code information with the applet information specified by the user and send the first graphic code information to the graphic code management server, so that the graphic code management server creates a first mapping relationship between the first graphic code identifier and the applet information specified by the merchant, and uses the first mapping relationship as the merchant mapping relationship. The first mapping relation generated by the graphic code management server is used for responding to an information acquisition request initiated by a user client and determining target small program information corresponding to a first target graphic code identifier contained in the request. For a specific process of the graphic code management server or the service server responding to the information acquisition request by using the first mapping relationship, reference may be made to the detailed description of the following embodiments, which is not repeated herein.

In this embodiment, after the secondary graphic code identifier is obtained through analysis, the merchant client may start an information entry page according to the secondary graphic code identifier, and display an information entry component for an entity store corresponding to the merchant on the page. Correspondingly, the merchant can implement the entry operation for the component, and then the merchant client can acquire the entered store-related information and send the store-related information and the secondary graphic code identifier contained in the graphic code information to the graphic code management server in an associated manner under the condition that the entry operation is detected, so that the graphic code management server generates a second mapping relationship based on the store-related information and the secondary graphic code identifier. For example, in the case that the secondary graphic code identifier is a global identifier, the graphic code management server may create a second mapping relationship between the secondary graphic code identifier included in the graphic code information and store-related information specified by a merchant; or, the graphic code management server creates a second mapping relationship among the primary graphic code identifiers, the secondary graphic code identifiers and the store-related information specified by the merchant, which are contained in the graphic code information, under the condition that at least part of the secondary graphic code identifiers corresponding to different primary graphic code identifiers exist (namely the secondary graphic code identifiers are not global identifiers). The second mapping relation created by the graphic code management server is used for determining the relevant information of the target store corresponding to the target graphic code information contained in the information acquisition request. For a specific process of the graphic code management server or the service server determining the relevant information of the target store by using the second mapping relationship, reference may be made to the following detailed description of the embodiments, which is not repeated herein. The store-related information may be a store identifier of a physical store under the brand name, a region number of an activity region in the physical store (e.g., a room number, a table and chair number), a product identifier of a product sold in the store, and the like, and the description is not limited thereto.

The graphic code management server creates a first mapping relation and a second mapping relation, namely the graphic code is bound with a merchant applet corresponding to the entity store, and then a user who enters the store for consumption can scan the graphic code through the user client to start a target merchant applet and realize related operations such as ordering, consumption, payment and the like through the target merchant applet. The following describes a specific process for starting the target merchant applet.

After a user scans a bound graphic code (hereinafter referred to as a target graphic code) by using a user client, the user client can analyze target graphic code information contained in the graphic code, such as a first target graphic code identifier and a second target graphic code identifier. In this embodiment, the user client may generate an information obtaining request according to the first target graphic code identifier, and start a target merchant applet corresponding to the target applet information when obtaining the target applet information determined by the graphic code management server or the application server in response to the request.

In this embodiment, since there may be a plurality of storage locations of the first mapping relationship, the response procedure of the graphic code management server to the information acquisition request is also different. As an exemplary embodiment, after generating the first mapping relationship, the graphic code management server may locally maintain the first mapping relationship, and after receiving the information acquisition request created by the user client, respond to the request according to the locally stored first mapping relationship. For example, the user client may directly send the created information acquisition request to the graphic code management server, or send the information acquisition request to the graphic code management server through the application server corresponding to the user client, so that the graphic code management server may determine, according to the first mapping relationship, target applet information corresponding to the first target graphic code identifier included in the information acquisition request, and directly return the information to the user client or return the information to the user client through the application server corresponding to the user client. Because the user can scan the graphic code through the user applet developed on the basis of the software platform corresponding to the graphic code management server, the user applet operated on the basis of the user client directly communicates with the graphic code management server, the request processing efficiency can be improved, and merchant information is prevented from being leaked to the application server.

As another exemplary embodiment, after the first mapping relationship is generated, the graphic code management server may send the first mapping relationship to an application server corresponding to the user client, so as to be maintained by the application server, and after receiving an information acquisition request sent by the user client, the application server may determine, according to the locally maintained first mapping relationship, target applet information corresponding to a first target graphic code identifier included in the information acquisition request, and directly return the information to the user client. The first mapping relation is sent to the application server side for maintenance and response to the request, the application server side realizes hosting of the first mapping relation, order processing load of the graphic code management server side is reduced, jump efficiency of the target business small program is improved, and user experience is improved.

In this embodiment, after receiving the target applet information, the user client may generate a data acquisition request according to the information, and directly send the request to the graphic code management server or send the request to the graphic code management server through the application server, so that the graphic code management server may determine the target merchant applet according to the target applet information in the request, further acquire target applet data of the target merchant applet, and directly return the data to the user client or return the data to the user client through the application server. The target applet data and the corresponding relationship between the target applet data and the target applet information may be stored locally at the graphic code management server or in a storage device accessible to the graphic code management server, which is not limited in this specification.

In addition, because the same merchant may have different merchant applets distributed at user clients of different application programs, the request may also carry identification information of the user client or the application program, so that the graphic code management server or the application server determines the type of the application program to be sent according to the identification information, and further determines the data format of target applet data to be returned in subsequent steps, and the like, which is not described again. The application program may be any type of application, such as an instant messaging application, a payment application, and the like, which is not limited in this specification.

The foregoing embodiment discusses that the graphic code management server returns the acquired target applet information to the user client (or the application server), and receives the data acquisition request sent by the user client (or the application server). However, the graphic code management server and the user client (or the application server) need to interact at least twice in the above process, and the efficiency still needs to be improved. Therefore, after the target applet information is determined according to the first mapping relationship maintained locally, the graphic code management server may also determine corresponding target applet data directly according to the target applet information without returning to the user client or the application server, and further return the data directly to the user client or return the data to the user client through the application server. By the method, the graphic code management server and the user client (or the application server) only need to interact once, the interaction process is effectively simplified, the target applet data acquisition efficiency and the target merchant applet skip efficiency are further improved, and the user experience is facilitated to be improved.

In this embodiment, the user client may display the target applet data received by the user client, and it can be understood that the target applet data displayed for the first time after the user client scans the target graphic code may generally be page data of a home page or a default page of the applet, so a process of displaying the data by the user client is a process of starting the target merchant applet.

Certainly, the activated target merchant applet can further acquire related data from the graphic code management server to further display commodity related information of the entity store registered by the merchant in advance on the e-commerce platform, such as commodity names, selling prices, multimedia information for introducing characters, pictures, videos and the like of the commodities, to the user; merchant activity information, such as coupon information, full deactivation information, etc., may also be presented; merchant introduction, reminding information and the like of the physical store can be displayed, and the description does not limit the information. The user can shop for goods through the information displayed in the merchant applet by the user client.

As is well known to those skilled in the art, the same merchant applet can only provide a preset number (e.g., 10, 5, etc.) of access interfaces, that is, the same merchant applet can only be accessed through a preset number of graphic codes, so that in a case where a physical store is large in size (e.g., a large number of commodities, a large number of tables, etc.), to implement full coverage of access interfaces for objects such as commodities or tables, the merchant is required to issue a large number of merchant applets, which results in high operation and maintenance costs and low efficiency.

According to the scheme of the embodiment, when the graphic code is printed, the graphic code information is divided into two levels to be printed, and the first mapping relation and the second mapping relation are respectively created according to the first-level graphic code identification and the second-level graphic code identification, so that the graphic code management server (or the application server) can perform fuzzy matching (namely matching is performed according to the first mapping relation) only according to the first target graphic code identification contained in an information acquisition request sent by a user who enters a store after scanning the graphic code through the user client, thereby determining the target applet information of the target merchant applet, and returning the corresponding target applet data to the user client for starting the target merchant applet. Because the same first graphic code identifier can correspond to a plurality of second graphic code identifiers (namely, the graphic code information of a plurality of graphic codes comprises the same first graphic code identifier and different second graphic code identifiers), the number of the first graphic code identifiers can be adjusted flexibly according to the actual requirements of the physical store as long as the number of the first graphic code identifiers does not exceed the preset number. Therefore, the number of user access entrances of the same business applet is remarkably increased, and the method is favorable for meeting various requirements of entity stores with different scales on graphic codes in low cost and high efficiency.

For example, under the condition that a certain entity catering store contains 120 dining tables, adopt above-mentioned scheme, only need adopt 1 group of every group to contain the graphic code of 100 table subsides and 2 groups of every group contain the graphic code of 10 table subsides, can realize laying the graphic code of whole 120 dining tables through utilizing 3 access interfaces (3 one-level graphic code identifications promptly), and then, the user scans the shop applet that can start this entity catering store through the table subsides on any dining table through user client and puts the order. It can be seen that this approach actually utilizes 3 access interfaces of the merchant applet to implement 120 user access entries, and the number of user access entries is significantly increased without changing the existing interface access rules. And the personalized requirements of different scales of merchants for different numbers of graphic codes can be met through the flexible combination of the graphic codes with different specifications and similar shapes.

Further, by viewing the relevant information of the goods displayed in the merchant applet, the user can select the goods of the heart instrument and place an order.

In one embodiment, the user may place an order offline. For example, a user may specify a commodity of his mood to a merchant (e.g., a service person in a physical store), and the service person selects the commodity specified by the user through a merchant applet started in a merchant client, and performs a corresponding ordering operation after the selection is completed, so that the merchant client sends ordering information to the graphic code management server for generating an order. Alternatively, the merchant may select the commodity specified by the user from an order client (in this case, the system shown in fig. 1 may further include the order server, which is not shown in fig. 1) such as a tablet pc preset in the brick and mortar store, and complete placing the order. It should be noted that, a merchant may enter relevant store information (such as a number of a table where the user sits, a number of a room selected by the user, and the like) corresponding to the user in the ordering operation, where the relevant store information is the relevant store information corresponding to the secondary graphic code identifier recorded in the graphic code scanned by the user client, so as to ensure that the generated order includes the relevant store information, and further ensure that the order corresponds to the user one to one.

Further, after the graphic code management server generates the order, the order may be output to a service acceptance terminal (such as the POS 15 shown in fig. 1) deployed in a physical store, so that the physical order is printed by the terminal and displayed to the user, so that the user can clearly know the content of the order, the amount of money related to the order, and the like. Furthermore, the physical stores can perform commodity-related processing, such as dish making, commodity packaging and the like. Finally, the user can pay at a proper time (such as after having a meal, during the process of having a meal, waiting for the package of the commodity, after taking the commodity, and the like) by means of a user client scanning service acceptance terminal, and the consumption process in the physical store is finally completed.

In the above embodiments of offline ordering and online payment, the user still needs to perform more offline communication with the merchant, and in fact, the user may also perform online ordering, which is described in detail below.

After the user client starts the merchant applet and displays the information such as commodities, the user can implement corresponding ordering operation through the merchant applet. After detecting the order placing operation performed by the user, the user client may determine order placing information at this time, such as information about the model (e.g., SKU, Stock Keeping Unit, inventory Unit, etc.) and quantity of the commodity selected and purchased by the user, and may further include coupon information about a coupon (e.g., a discount coupon, a voucher, a token, etc.) specified and used by the user, and the description does not limit this.

Furthermore, the user client can send order placing information to the graphic code management server for generating a target order. For example, the user client may send the order placing information and the scanned secondary target graphic code identifier to the graphic code management server in an associated manner; or, only ordering information may be sent, and the graphic code management server determines the secondary target graphic code identifier according to the received information acquisition request after receiving the ordering information, so as to avoid repeated sending of the same information, reduce bandwidth occupation, and improve information sending efficiency.

Correspondingly, after receiving order placing information determined by the user client, the graphic code management server can generate a target order based on the information. When the target order is generated, the related information of the target store corresponding to the secondary target graphic code identification needs to be obtained, and the specific mode of obtaining the related information of the target store by the graphic code management server can be various according to the different storage positions of the second mapping relation. As an exemplary embodiment, after the second mapping relationship is generated, the graphic code management server may locally maintain the second mapping relationship, and determine, according to the second mapping relationship, target store-related information corresponding to the secondary target graphic code identifier. For example, the user client may directly send the order placing information to the graphic code management server, or send the order placing information to the graphic code management server through the application server corresponding to the user client, so that the graphic code management server may determine, according to the second mapping relationship, the target store related information corresponding to the secondary target graphic code identifier after receiving the order placing information. Furthermore, the determined information related to the target store can be used for generating a target order.

As another exemplary embodiment, after the second mapping relationship is generated, the graphic code management server may send the second mapping relationship to an application server corresponding to the user client, so as to be maintained by the application server, and thus the application server may determine, according to the second mapping relationship, target store-related information corresponding to the secondary target graphic code identifier. For example, the user client may send the order placing information to the application server, so that the application server may determine, after receiving the order placing information, target store-related information corresponding to the secondary target graphic code identifier according to the second mapping relationship, and send the target store-related information to the graphic code management server, so that the application server generates the target order. The second mapping relation is sent to the application server for maintenance and response to the request, the application server realizes hosting of the second mapping relation, order processing load of the graphic code management server is reduced, jump efficiency of the target business small program is improved, waiting time of a user is reduced, and user experience is improved to a certain extent.

In this embodiment, the graphic code management server may output the generated target order in various ways. For example, the graphic code management server may send the target order to the user client, so that the user client displays the target order to the user, thereby facilitating the user to know the order status in time. For another example, the graphic code management server may also send the target order to the merchant client, so that the merchant client displays the target order and/or counts the target order to the merchant. Therefore, merchants can conveniently acquire target ordering content in time, and relevant commodities of orders can be prepared for users in time, such as making dishes according to the orders, packaging the commodities and the like; and the merchant can count the order, so that the merchant can manage stores conveniently.

For another example, the graphic code management server may further send the target order to a service acceptance terminal deployed in a physical store of the merchant, so that the service acceptance terminal executes a corresponding service acceptance operation according to the target order. For example, an order printing operation may be performed such that the target order is printed out for viewing by a user or a staff member of a brick and mortar store. Or, when the service acceptance terminal is a payment terminal such as a POS, the terminal may further perform a collection operation, that is, the user may interact with the payment terminal through the payment application to realize a payment operation for funds related to the target order, and accordingly, the collection operation is completed by the payment terminal. Of course, the order printing may be performed after the collection operation is completed, so that the physical order containing the payment information is directly printed for the user to view or the physical store to archive.

In the order generation scheme of the present specification, the user client may start a pre-published merchant applet. The merchant client can determine the graphic code information by scanning the graphic code and acquire the applet information designated by the merchant, the graphic code management server can generate an information mapping relation according to the graphic code information and the applet information sent by the merchant client, and the target applet information determined according to the information mapping relation can be used for indicating the user client to start the target merchant applet.

Referring to fig. 4, fig. 4 is a flowchart of another small program starting method based on a graphic code according to an exemplary embodiment. As shown in fig. 4, the method is applied to a merchant service end, and may include the following steps:

step 402, analyzing the graphic code information contained in the graphic code.

At step 404, applet information for at least one merchant applet designated by a merchant is determined, the merchant applet for the merchant being pre-published to the user client.

Step 406, sending the graphic code information and the applet information to a graphic code management server in an associated manner, so that the graphic code management server creates an information mapping relationship between the graphic code information and the applet information; the information mapping relation is used for determining target small program information corresponding to target graphic code information contained in an information acquisition request initiated by the user client, the information acquisition request is generated by the user client according to the target graphic code information obtained by analyzing a graphic code, and the target small program information is used for indicating the user client to start a target merchant small program which is issued in advance.

As mentioned above, the merchant client scans the graphic code through the native graphic code recognition program or the graphic code management applet provided by the graphic code management server.

As mentioned above, the determining of the applet information of at least one merchant applet designated by a merchant includes:

As mentioned above, the method further comprises:

Referring to fig. 5, fig. 5 is a flowchart of another small program starting method based on a graphic code according to an exemplary embodiment. As shown in fig. 5, the method applied to the user client may include the following steps:

step 502, analyzing the target graphic code information contained in the graphic code, and generating an information acquisition request according to the target graphic code information.

Step 504, acquiring target applet information corresponding to the target graphic code information determined according to the information mapping relation and responding to the information acquisition request, and starting a target merchant applet issued in advance according to the target applet information; the information mapping relation is established by the graphic code management service terminal according to graphic code information and applet information sent by a merchant client, the graphic code information is obtained by analyzing a graphic code by the merchant client, the applet information is appointed by a merchant for at least one merchant applet, and the merchant applet of the merchant is issued to the user client in advance.

As mentioned above, the method further comprises:

For easy understanding, the promotion process of the graphic code and the scheme for initiating the merchant applet and generating the order based on the promoted graphic code will be described in detail below with reference to fig. 6 to 9.

Referring to fig. 6, fig. 6 is an interaction diagram of an applet starting method based on a graphic code according to an exemplary embodiment. As shown in fig. 6, taking an entity store as a dining store and information related to the store as a table number for example, the interaction process may include the following steps:

step 602, the merchant scans the graphic code, and the merchant client analyzes the graphic code to obtain the graphic code information.

In this embodiment, the graphic code scanned by the merchant is generated in advance by a promoter and is laid on a dining table in a restaurant (where a user may be used for dining), and in a general case, one dining table may be pasted with one graphic code, but a specific laying manner may also be adjusted according to a specific dining form (such as a piecing together meal, an AA system, and the like) of the restaurant, which is not limited in this specification. The graphic code information included in the graphic code may include a first graphic code identifier and a second graphic code identifier, and the following description will take the first graphic code identifier as a code group allocated to the graphic code in advance, and take the second graphic code information as a code value allocated to the graphic code in advance as an example.

After the graphic code is laid, the merchant can scan the graphic code through the merchant client to bind the graphic code with the merchant applet of the restaurant (of course, each graphic code can be laid in sequence after the merchant completes the binding). The merchant applet can be published to the user client in advance. Certainly, the same restaurant may publish at least one merchant applet, for example, different merchant applets are respectively published in an instant messaging application, a payment application and other application programs, and the description does not limit the number of merchant applets published by the restaurant and the published application programs, but only focuses on a process of generating an order through any merchant applet.

As shown in fig. 7A, the graphic code management applet may display a binding prompt page with a graphic code, where the page may display description information 701A and a scanning trigger component 702A, and a merchant may invoke a camera component of a terminal device by triggering the scanning trigger component 702A to start scanning the graphic code. The page may also present activation records 703A for the merchant to view. Here, since the graphic code described in this specification is printed in advance, the interface diagrams of fig. 7A to 9 are referred to as "pre-code", and thus will be described.

It should be noted that, because the code values of the graphic codes corresponding to the same code group are different, when the merchant client activates the graphic codes, any one of the graphic codes in the same group may be scanned first to bind the code group in the graphic code information with the merchant applet; and in the subsequent step 610, when the code value and the table number are bound, each graphic code is scanned in sequence (of course, the scanning may be performed only once for the one scanned when the code group and the merchant applet are bound).

In step 604, the merchant client jumps to the information-specific page.

Step 606, the merchant client obtains merchant-specified applet information.

The graphic code can contain a graphic code address, so that after the merchant client analyzes the graphic code address, the merchant client can jump to an information designated page indicated by the address. The information-specific page may be a native page of a merchant client, an applet page of a graphic code management applet issued to the merchant client, a browser webpage, or the like, which is not limited in this specification. For example, in the case that the graphic code data obtained by scanning is "1 n1n1," https:// aaa. xxx. com/pre "may be a graphic code address, and" m1m1m1 "and" n1n1n1 "are respectively a code group and a code value, so that the merchant client may determine that the graphic code is a pre-code when recognizing the graphic code address, and then jump to an information designation page corresponding to the address for the merchant to designate small program information, as shown in fig. 8A.

And if the merchant client cannot analyze the obtained graphic code address, the scanned graphic code is not a prefabricated code, and the merchant client can jump to another binding prompt page. As shown in fig. 7B, the binding hint page may include a binding failure hint component 701B and a return component 702B, so that the merchant may learn the binding failure information from the binding failure hint component 701B and may return to the page shown in fig. 7A by clicking the return component 702B.

After the graphic code address is analyzed, the merchant client can automatically detect the merchant applet corresponding to the currently logged-in merchant account, and display the information specifying component corresponding to the detected merchant applet in the page for the merchant to specify the applet information. Or, under the condition that it is detected that the current merchant account is not logged in, the merchant client may jump to a login page of the merchant account after analyzing the graphic code address, and further jump to an information designation page after the merchant completes the login of the merchant account.

As shown in fig. 8A, the information-designated page entered by the merchant client jump may show identified code group information 801A, such as a code group, a number of graphic codes (i.e., a number of code values) corresponding to the code group, and the like; information specific components of at least one merchant applet may also be exposed, such as S1 applet 802A for application AA and S2 applet 803A for application BB. The merchant may click on activation trigger component 804A after selecting the above-mentioned applet to bind the applet information of the selected merchant applet with the code group.

Of course, the merchant applet described above may be an applet that has been published to the user client, such as the S1 applet 802A. Or, the foregoing merchant applet may be an applet that has not been published to the user client, such as the applet 803A of S2, at which point the merchant may jump to the applet publishing page to publish the applet by clicking the "go process" component, and jump back to the information specifying page after the merchant completes publishing the applet for the merchant (successfully publishes the applet for the merchant to the user client) (of course, in the case of successful publishing, the publishing component for the applet for the merchant may no longer be displayed in the information specifying page that jumps back, and a word similar to the word "publish successful" shown in the applet 802A of S2 is displayed).

After the merchant selects the applet and clicks the activation triggering component 804A, the merchant client may send the code group and the applet information of the selected applet to the graphic code management server for generating a first mapping relationship, and determine that the code group and the merchant applet are successfully bound under the condition that a creation success notification message returned by the graphic code management server is received. In fact, the code group and the code value may also be sent to the graphic code management service end in association with the applet information specified by the merchant and the table number entered by the merchant (as shown in step 612), which is the manner described in this embodiment.

After the activation is successful, the merchant client may jump to the binding result page shown in fig. 8B, and display the binding success prompt message 801B and the binding record 802B, at this time, the merchant may click the return component 803B to return to the page shown in fig. 8A, which is not described again.

At step 608, the merchant client jumps to the information entry page.

Step 610, the merchant client obtains the table number entered by the merchant.

Step 612, the merchant client sends the acquired graphic code information, the applet information and the table number to the graphic code management server.

Further, the merchant client may jump to an information entry page according to the code value under the condition that the code value is obtained through analysis (or the code group is determined to be successfully bound with the merchant applet), and display an information entry component for an entity store corresponding to the merchant in the page to obtain the table number entered by the merchant.

As shown in fig. 9, the information entry page entered by the merchant client jump may show identified graphic code information 901, such as code group, code value serial number, and the like; an information type alternative component 902 and an information input component 903 can also be shown, after a merchant selects a certain information type alternative component and inputs information in the information input component 903, the merchant client can associate the information with a code value and send the information to the graphic code management server. For example, after the merchant selects "table number" and inputs the number "1", the code value "i 61Sg7 i" of the current graphic code may be associated with the number and sent to the graphic code management server (of course, the type corresponding to the number may also be sent at the same time as the table number). After the merchant selects the "commodity" and inputs the name "xxx children's garments" in the form of characters, the code value "i 61Sg7 i" of the current graphic code can be associated with the name and sent to the graphic code management server (of course, the type corresponding to the name can also be sent to the commodity at the same time). The following examples are given by way of example only.

And step 614, the graphic code management server side creates a first mapping relation and a second mapping relation according to the received information.

And the merchant client associates and sends the identified code group and code value, the applet information specified by the merchant and the recorded table number to the graphic code management server so as to establish a first mapping relation and a second mapping relation by the graphic code management server. After receiving the code group sent by the merchant client, the graphic code management server may first determine whether the code group has already established the first mapping relationship by querying the first mapping relationship or querying a creation record of the first mapping relationship: and under the condition that the code group has established the first mapping relation, a reminding message can be returned to the merchant client to inform the merchant, and under the condition that the code group does not establish the first mapping relation, the first mapping relation corresponding to the code group is established. Certainly, the merchant client may also directly send the code value to the graphic code management server after identifying the code value, and the graphic code management server determines whether the code value has already created a corresponding first mapping relationship, and returns a prompting message to the merchant client under the condition that the code value has not yet been created, so that the merchant client may display an information-specifying page to the merchant after receiving the prompting message, so as to avoid that the merchant invalidates specified applet information.

The first mapping relationship may be a mapping relationship between a code group and an applet identifier; under the condition that the code value is the global identifier, the graphic code management server side can establish a second mapping relation between the code value contained in the graphic code information and the table number appointed by the merchant; or, the graphic code management server creates a second mapping relationship among the code groups contained in the graphic code information, the code values and the table numbers specified by the merchants when at least part of the code values corresponding to different code groups are the same (that is, the code values are not global identifiers). The second mapping relation created by the graphic code management server is used for determining a target table number corresponding to the target graphic code information contained in the information acquisition request. For a specific process of the graphic code management server or the business server determining the target table number by using the second mapping relationship, reference may be made to the detailed description of the following embodiments, which is not repeated herein.

In step 616, the graphic code management server sends the first mapping relationship to the application server.

At step 618, the application server maintains the received first mapping relationship.

In this embodiment, after the first mapping relationship is generated, the graphic code management server may send the first mapping relationship to an application server corresponding to the user client, so as to be maintained by the application server, and after receiving an information acquisition request sent by the user client, the application server may determine, according to the locally maintained first mapping relationship, target applet information corresponding to a code group included in the information acquisition request, and directly return the information to the user client. The first mapping relation is sent to the application server side for maintenance and response to the request, the application server side realizes hosting of the first mapping relation, order processing load of the graphic code management server side is reduced, jump efficiency of the target business small program is improved, and user experience is improved.

The graphic code management server creates a first mapping relation and a second mapping relation, namely the graphic code is bound with a merchant applet corresponding to the entity store, and then a user who enters the store for consumption can scan the graphic code through the user client to start a target merchant applet and realize online operations such as ordering, consumption, payment and the like through the target merchant applet. The order generation process after the user client scans the graphic code will be described with reference to steps 620 and 646 c.

Step 620, the user client scans the graphic code and analyzes to obtain the target graphic code information.

After scanning the bound graphic code (hereinafter referred to as a target graphic code), the user client may analyze target graphic code information, such as a target code group and/or a target code value, contained in the graphic code.

In step 622, the user client sends an information acquisition request containing the target code group to the application server.

In step 624, the application server determines the target applet information according to the target code group.

In step 626, the application server sends the target applet information to the user client.

The user client can generate an information acquisition request according to the target code group and send the request to the application server, and after receiving the information acquisition request sent by the user client, the application server can determine target applet information corresponding to the target code group contained in the information acquisition request according to a first mapping relation maintained locally and directly return the information to the user client.

In step 628, the user client sends a data acquisition request containing the target applet information to the graphic code management server.

And step 630, the graphic code management server side determines the target applet data according to the target applet information.

In step 632, the graphic code management server returns the target applet data to the user client.

After receiving the target applet information, the user client can generate a data acquisition request according to the information, and directly send the request to the graphic code management server or send the request to the graphic code management server through the application server, so that the graphic code management server can determine a target merchant applet according to the target applet information in the request, further acquire target applet data of the target merchant applet, and directly return the data to the user client or return the data to the user client through the application server. The target applet data and the corresponding relationship between the target applet data and the target applet information may be stored locally at the graphic code management server or in a storage device accessible to the graphic code management server, which is not limited in this specification. In addition, because the same merchant may have different merchant applets distributed at user clients of different application programs, the request may also carry identification information of the user client or the application program, so that the graphic code management server or the application server determines the type of the application program to be sent according to the identification information, and further determines the data format of target applet data to be returned in subsequent steps, and the like, which is not described again.

In fact, after the first mapping relationship is generated, the graphic code management server may also locally maintain the first mapping relationship, and after receiving the information acquisition request created by the user client, respond to the request according to the first mapping relationship (at this time, there may be no application server in fig. 6). For example, the user client may directly send the created information acquisition request to the graphic code management server, or send the information acquisition request to the graphic code management server through the application server corresponding to the user client, so that the graphic code management server may determine, according to the first mapping relationship, target applet information corresponding to a target code group included in the information acquisition request, and directly return the information to the user client or return the information to the user client through the application server corresponding to the user client. At this time, after the user client scans and analyzes the graphic code to obtain the target graphic code information, the user client can directly request the graphic code management server to obtain the target applet information, so that the information obtaining process of the application server is simplified, the information obtaining efficiency is improved, the information safety risk possibly brought to a merchant by introducing the application server is reduced, and the merchant information and the graphic code information are prevented from being leaked to a certain extent.

In addition, after the graphic code management server determines the target applet information according to the first mapping relationship maintained locally, the graphic code management server may directly determine corresponding target applet data without returning to the user client or the application server, and return the data to the user client directly or through the application server. By the method, the interaction process among all parties can be effectively simplified, the acquisition efficiency of target applet data and the skip efficiency of the target merchant applet are further improved, and the user experience is further improved.

In step 634, the user client launches the target merchant applet.

And after receiving the target applet data, the user client displays the data. It is understood that the target applet data first presented by the user client after scanning the target graphic code may be the page data of the first page or default page of the applet, so that the process of presenting the data by the user client is the process of starting the target merchant applet. Certainly, the target merchant applet after the jump is started can further acquire related data from the graphic code management server to further display commodity related information of the physical store, such as commodity names, selling prices, multimedia information for introducing characters, pictures, videos and the like of the commodities to the user; merchant activity information, such as coupon information, full deactivation information, etc., may also be presented; merchant introduction, reminding information and the like of the physical store can be displayed, and the description does not limit the information.

In step 636, the user client detects the order placing operation implemented by the user and determines the corresponding order placing information.

And step 638, the user client sends the ordering information and the target code value to the graphic code management server.

After the user client starts the merchant applet and displays the information such as commodities, the user can implement corresponding ordering operation through the merchant applet. After detecting the order placing operation performed by the user, the user client may determine corresponding order placing information, such as information about the model and number of commodities selected and purchased by the user, and may further include coupon information about a coupon (such as a discount coupon, a voucher, a token, and the like) selected and used by the user, and the like, which is not limited in this specification. Furthermore, the user client can send the order placing information to the graphic code management server to be used for generating a target order.

In this embodiment, the user client may send the order placing information and the scanned target code value to the graphic code management server in an associated manner; or, only the ordering information may be sent, and the graphic code management server determines the target code value according to the received information acquisition request after receiving the ordering information, so as to avoid repeated sending of unified information, reduce bandwidth occupation, and improve information sending efficiency.

And step 640, the graphic code management server determines the target table number according to the target code value.

When the graphic code management server generates a target order, a target table number corresponding to a target code value needs to be obtained. In this embodiment, after the second mapping relationship is generated, the graphic code management server may locally maintain the second mapping relationship, and determine the target table number corresponding to the target code value according to the second mapping relationship. For example, the user client may directly send the order placing information to the graphic code management server, or send the order placing information to the graphic code management server through the application server corresponding to the user client.

In an embodiment, after the second mapping relationship is generated, the graphic code management server may also send the second mapping relationship to an application server corresponding to the user client, so as to be maintained by the application server, and thus the application server may determine a target table number corresponding to the target code value according to the second mapping relationship. For example, the user client may send the order placing information to the application server, so that the application server may determine, after receiving the order placing information, a target table number corresponding to the target code value according to the second mapping relationship, send the target table number to the graphic code management server according to the target table number, and generate the target order by the application server. The second mapping relation is sent to the application server side for maintenance and response to the request, the application server side realizes hosting of the second mapping relation, order processing load of the graphic code management server side is reduced, jump efficiency of the target business small program is improved, and user experience is improved.

And 642, generating a target order by the graphic code management server according to the target table number and the ordering information.

The graphic code management server side can determine a target table number corresponding to the target code value according to the second mapping relation after receiving the ordering information, and generate a target order according to the target table number.

At step 644a, the graphic code management server sends the target order to the merchant client.

In step 644b, the graphic code management server sends the target order to the user client.

In step 644c, the graphic code management server sends the target order to the POS machine.

At step 646a, the merchant client displays and/or tallies the target order.

In step 646b, the user client displays the target order.

In step 646c, the POS prints the target order.

In this embodiment, after the target order is generated, the server side may further output the order. The graphic code management server may output the target order in a plurality of ways, for example, the graphic code management server may send the target order to the user client, so that the user client displays the target order to the user, thereby facilitating the user to know the state of the order in time. For another example, the graphic code management server may also send the target order to the merchant client, so that the merchant client displays the target order and/or counts the target order to the merchant. Therefore, merchants can conveniently acquire target ordering content in time, and relevant commodities of orders can be prepared for users in time, such as food preparation according to the orders; and the merchant can count the order, so that the merchant can manage stores conveniently. For another example, the graphic code management server may further send the target order to a POS deployed in a physical store of the merchant, so that the payment terminal performs a corresponding service acceptance operation according to the target order. For example, an order printing operation may be performed, whereby a target order is printed out for viewing by a user or a staff member of a brick and mortar store; and a money receiving operation can be executed, namely, the user can interact with the POS machine through the payment application to realize the payment operation of the funds related to the target order, and correspondingly, the POS machine completes the money receiving operation. Of course, the order printing may be performed after the collection operation is completed, so that the physical order containing the payment information is directly printed for the user to view or the physical store to archive.

As can be seen from the above embodiments, a user client may initiate a pre-published merchant applet. The merchant client can determine graphic code information by scanning a graphic code and acquire applet information designated by the merchant, the graphic code management server can generate an information mapping relation according to the graphic code information and the applet information sent by the merchant client, the target applet information determined according to the information mapping relation can be used for indicating the user client to start a target merchant applet, and the graphic code management server can generate and output a target order according to order placing information corresponding to order placing operation implemented by the user through the target merchant applet.

Fig. 10 is a schematic structural diagram of an electronic device according to an exemplary embodiment. Referring to fig. 10, at the hardware level, the apparatus includes a processor 1002, an internal bus 1004, a network interface 1006, a memory 1008, and a non-volatile memory 1010, although it may also include hardware required for other services. The processor 1002 reads the corresponding computer program from the non-volatile memory 1010 to the memory 1008 and then runs the computer program to form an applet starting device based on graphic codes on a logic level. Of course, besides software implementation, the one or more embodiments in this specification do not exclude other implementations, such as logic devices or combinations of software and hardware, and so on, that is, the execution subject of the following processing flow is not limited to each logic unit, and may also be hardware or logic devices.

Referring to fig. 11, in a software implementation, the applet starting apparatus based on the graphic code is applied to a graphic code management server; the method can comprise the following steps:

the information receiving unit 1101 is used for receiving graphic code information and applet information which are sent by a merchant client in a correlation manner, and creating an information mapping relationship between the graphic code information and the applet information; the graphic code information is obtained by analyzing a graphic code by the merchant client, the applet information is specified by a merchant for at least one merchant applet, and the merchant applet of the merchant is issued to the user client in advance;

a request information determining unit 1102, configured to determine, according to the information mapping relationship, target applet information corresponding to target graphic code information included in an information acquisition request initiated by the user client, where the information acquisition request is generated by the user client according to the target graphic code information obtained by parsing a graphic code, and the target applet information is used to instruct the user client to start a target merchant applet that is issued in advance.

Optionally, the method further includes:

an information obtaining unit 1103, configured to obtain ordering information determined by the user client in response to an ordering operation performed by the user through the target merchant applet;

and an order generating unit 1104 for generating and outputting the target order according to the order placing information.

the information receiving unit 1101 is further configured to: creating a first mapping relation between the primary graphic code identifier and the applet information;

the apparatus further includes a mapping creating unit 1105, configured to create a second mapping relationship between a secondary graphic code identifier included in the graphic code information and store-related information specified by the merchant, when the secondary graphic code identifier is a global identifier; or under the condition that at least part of the plurality of secondary graphic code identifications corresponding to different primary graphic code identifications are the same, creating a second mapping relation among the primary graphic code identifications, the secondary graphic code identifications and the store related information appointed by the merchant, wherein the primary graphic code identifications and the secondary graphic code identifications are contained in the graphic code information; the second mapping relationship is used for determining the relevant information of the target store corresponding to the target graphic code information contained in the information acquisition request.

Optionally, the method further includes:

a first maintenance unit 1106, configured to locally maintain the created first mapping relationship, and configured to respond to the information acquisition request; or sending the created first mapping relation to an application server side so that the application server side responds to the information acquisition request; and/or the presence of a gas in the gas,

a second maintenance unit 1107, which locally maintains the created second mapping relationship, and is configured to determine the target store information; or sending the created second mapping relation to an application server, so that the application server determines the target store information.

Optionally, the order generating unit 1104 is further configured to at least one of:

Referring to fig. 12, in another software embodiment, the applet launching device based on graphic code is applied to a merchant client; the method can comprise the following steps:

an information analysis unit 1201 for analyzing the graphic code information included in the graphic code;

an appointed information determining unit 1202, configured to determine applet information of at least one merchant applet appointed by a merchant, where the merchant applet of the merchant is issued to a user client in advance;

an information sending unit 1203, configured to send the graphic code information and the applet information to a graphic code management server in an associated manner, so that the graphic code management server creates an information mapping relationship between the graphic code information and the applet information; the information mapping relation is used for determining target small program information corresponding to target graphic code information contained in an information acquisition request initiated by the user client, the information acquisition request is generated by the user client according to the target graphic code information obtained by analyzing a graphic code, and the target small program information is used for indicating the user client to start a target merchant small program which is issued in advance.

Optionally, the graphic code information includes a primary graphic code identifier and a secondary graphic code identifier, the information mapping relationship is a first mapping relationship between the information graphic code identifier and the applet information, and the specific information determining unit 1202 is further configured to:

Optionally, the method further includes:

the information entry unit 1204 is configured to start an information entry page according to a secondary graphic code identifier included in the graphic code information, and display an information entry component for an entity store corresponding to the merchant on the information entry page;

a store information obtaining unit 1205, configured to obtain, when an entry operation for the information entry component is detected, store-related information that is entered, and send, to the graphic code management server, a secondary graphic code identifier included in the graphic code information and store-related information that is specified by the merchant in an associated manner, so that the graphic code management server creates, when the secondary graphic code identifier is a global identifier, a second mapping relationship between the secondary graphic code identifier included in the graphic code information and the store-related information that is specified by the merchant; or, the graphic code management server creates a second mapping relationship between the primary graphic code identifier and the secondary graphic code identifier contained in the graphic code information and the relevant information of the store appointed by the merchant under the condition that at least parts of the plurality of secondary graphic code identifiers corresponding to different primary graphic code identifiers are the same; the second mapping relationship is used for determining the relevant information of the target store corresponding to the target graphic code information contained in the information acquisition request.

Referring to fig. 13, in yet another software embodiment, the applet launching device based on graphic codes is applied to a user client; the method can comprise the following steps:

the request generating unit 1301 analyzes target graphic code information contained in a graphic code, and generates an information acquisition request according to the target graphic code information;

an applet skipping unit 1302, configured to obtain target applet information corresponding to the target graphic code information determined according to an information mapping relationship in response to the information obtaining request, and start a target merchant applet issued in advance according to the target applet information; the information mapping relation is established by the graphic code management service terminal according to graphic code information and applet information sent by a merchant client, the graphic code information is obtained by analyzing a graphic code by the merchant client, the applet information is appointed by a merchant for at least one merchant applet, and the merchant applet of the merchant is issued to the user client in advance.

Optionally, the method further includes:

and the order information determining unit 1303, configured to determine order information in response to an order placing operation performed by the user through the target merchant applet, where the order information is used by the graphic code management server to generate and output a target order.

The systems, devices, modules or units illustrated in the above embodiments may be implemented by a computer chip or an entity, or by a product with certain functions. A typical implementation device is a computer, which may take the form of a personal computer, laptop computer, cellular telephone, camera phone, smart phone, personal digital assistant, media player, navigation device, email messaging device, game console, tablet computer, wearable device, or a combination of any of these devices.

In a typical configuration, a computer includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.

The memory may include forms of volatile memory in a computer readable medium, Random Access Memory (RAM) and/or non-volatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). Memory is an example of a computer-readable medium.

Computer-readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), Read Only Memory (ROM), Electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), Digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic disk storage, quantum memory, graphene-based storage media or other magnetic storage devices, or any other non-transmission medium that can be used to store information that can be accessed by a computing device. As defined herein, a computer readable medium does not include a transitory computer readable medium such as a modulated data signal and a carrier wave.

It should also be noted that the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.

The foregoing description has been directed to specific embodiments of this disclosure. Other embodiments are within the scope of the following claims. In some cases, the actions or steps recited in the claims may be performed in a different order than in the embodiments and still achieve desirable results. In addition, the processes depicted in the accompanying figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In some embodiments, multitasking and parallel processing may also be possible or may be advantageous.

The terminology used in the description of the one or more embodiments is for the purpose of describing the particular embodiments only and is not intended to be limiting of the description of the one or more embodiments. As used in one or more embodiments of the present specification and the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It should also be understood that the term "and/or" as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items.

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

The above description is only for the purpose of illustrating the preferred embodiments of the one or more embodiments of the present disclosure, and is not intended to limit the scope of the one or more embodiments of the present disclosure, and any modifications, equivalent substitutions, improvements, etc. made within the spirit and principle of the one or more embodiments of the present disclosure should be included in the scope of the one or more embodiments of the present disclosure.

Claims

1. An applet starting system based on graphic codes, comprising:

the merchant client analyzes the graphic code information contained in the graphic code, wherein the graphic code information contains a primary graphic code identifier and a secondary graphic code identifier; determining the applet information of at least one merchant applet appointed by a merchant, and sending the graphic code information and the applet information to a graphic code management service end in an associated manner, wherein the merchant applet of the merchant is issued to a user client in advance;

the graphic code management server side is used for creating a first mapping relation between the primary graphic code identifier and the applet information, and the first mapping relation is used for determining target applet information corresponding to target graphic code information contained in an information acquisition request initiated by the user client side; and under the condition that the secondary graphic code identification is the global identification, creating a second mapping relation between the secondary graphic code identification contained in the graphic code information and the shop related information appointed by the merchant; or under the condition that at least part of the plurality of secondary graphic code identifications corresponding to different primary graphic code identifications are the same, creating a second mapping relation among the primary graphic code identifications, the secondary graphic code identifications and the store related information appointed by the merchant, wherein the primary graphic code identifications and the secondary graphic code identifications are contained in the graphic code information; the second mapping relation is used for determining relevant information of the target store corresponding to the target graphic code information contained in the information acquisition request;

2. The system of claim 1, further comprising:

the application server receives the first mapping relation sent by the graphic code management server; and in response to the information acquisition request initiated by the user client, determining target applet information corresponding to the target graphic code information according to the first mapping relation, and returning the target applet information to the user client.

3. A small program starting method based on graphic codes is characterized by being applied to a graphic code management server; the method comprises the following steps:

receiving graphic code information and applet information which are sent by a merchant client in an associated mode, wherein the graphic code information comprises a primary graphic code identifier and a secondary graphic code identifier, and establishing a first mapping relation between the primary graphic code identifier and the applet information; the graphic code information is obtained by analyzing a graphic code by the merchant client, the applet information is specified by a merchant for at least one merchant applet, and the merchant applet of the merchant is issued to the user client in advance;

determining target small program information corresponding to target graphic code information contained in an information acquisition request initiated by the user client according to the first mapping relation, wherein the information acquisition request is generated by the user client according to the target graphic code information obtained by analyzing a graphic code, and the target small program information is used for indicating the user client to start a target merchant small program which is issued in advance;

under the condition that the secondary graphic code identification is the global identification, creating a second mapping relation between the secondary graphic code identification contained in the graphic code information and the shop related information appointed by the merchant; or under the condition that at least part of the plurality of secondary graphic code identifications corresponding to different primary graphic code identifications are the same, creating a second mapping relation among the primary graphic code identifications, the secondary graphic code identifications and the store related information appointed by the merchant, wherein the primary graphic code identifications and the secondary graphic code identifications are contained in the graphic code information; the second mapping relationship is used for determining the relevant information of the target store corresponding to the target graphic code information contained in the information acquisition request.

4. The method of claim 3, further comprising:

5. The method of claim 3, wherein the graphical code further comprises a graphical code address for instructing the merchant client to launch an information-specific page for collecting applet information for at least one merchant applet designated by a merchant.

6. A small program starting method based on graphic codes is characterized by being applied to a merchant client; the method comprises the following steps:

analyzing graphic code information contained in a graphic code, wherein the graphic code information comprises a primary graphic code identifier and a secondary graphic code identifier;

the primary graphic code identification and the applet information are sent to a graphic code management server side in an associated mode, so that a first mapping relation between the graphic code information and the applet information is established by the graphic code management server side; the first mapping relation is used for determining target small program information corresponding to target graphic code information contained in an information acquisition request initiated by the user client, the information acquisition request is generated by the user client according to the target graphic code information obtained by analyzing a graphic code, the target small program information is used for indicating the user client to start a target merchant small program which is issued in advance, a secondary graphic code identifier contained in the graphic code information and shop related information appointed by a merchant are sent to the graphic code management server in an associated mode, and a second mapping relation between the secondary graphic code identifier contained in the graphic code information and the shop related information appointed by the merchant is established by the graphic code management server under the condition that the secondary graphic code identifier is a global identifier; or, the graphic code management server creates a second mapping relationship between the primary graphic code identifier and the secondary graphic code identifier contained in the graphic code information and the relevant information of the store appointed by the merchant under the condition that at least parts of the plurality of secondary graphic code identifiers corresponding to different primary graphic code identifiers are the same; the second mapping relationship is used for determining the relevant information of the target store corresponding to the target graphic code information contained in the information acquisition request.

7. The method of claim 6, wherein determining applet information for at least one merchant applet designated by a merchant comprises:

8. The method of claim 7, further comprising:

acquiring the store-related information entered in a case where an entry operation for the information entry component is detected.

9. A small program starting method based on graphic codes is characterized in that the method is applied to a user client; the method comprises the following steps:

acquiring target small program information corresponding to the target graphic code information determined according to a first mapping relation in response to the information acquisition request, and starting a target merchant small program issued in advance according to the target small program information; the first mapping relation is created by the graphic code management service end according to the small program information sent by the merchant client and the primary graphic code identifier contained in the graphic code information, the graphic code information is obtained by the merchant client by analyzing the graphic code, the small program information is specified by the merchant for at least one merchant small program, and the merchant small program of the merchant is issued to the user client in advance; the graphic code information also comprises a secondary graphic code identifier, and under the condition that the secondary graphic code identifier is a global identifier, the secondary graphic code identifier contained in the graphic code information and the shop related information appointed by the merchant are used by the graphic code management server side for creating a second mapping relation; or, under the condition that at least part of the plurality of secondary graphic code identifiers respectively corresponding to different primary graphic code identifiers are the same, the primary graphic code identifier, the secondary graphic code identifier and the shop related information specified by the merchant contained in the graphic code information are used by the graphic code management server to create a second mapping relation; the second mapping relationship is used for determining the relevant information of the target store corresponding to the target graphic code information contained in the information acquisition request.

10. A graphic code recognition device is characterized by being applied to a graphic code management server; the device comprises:

the information receiving unit is used for receiving graphic code information and applet information which are sent by a merchant client in an associated mode, wherein the graphic code information comprises a primary graphic code identifier and a secondary graphic code identifier, and a first mapping relation between the primary graphic code identifier and the applet information is established; the graphic code information is obtained by analyzing a graphic code by the merchant client, the applet information is specified by a merchant for at least one merchant applet, and the merchant applet of the merchant is issued to the user client in advance;

the information determining unit is used for determining target applet information corresponding to target graphic code information contained in an information acquisition request initiated by the user client according to the first mapping relation, wherein the information acquisition request is generated by the user client according to the target graphic code information obtained by analyzing a graphic code, and the target applet information is used for indicating the user client to start a target merchant applet which is issued in advance;

the relationship establishing unit is used for establishing a second mapping relationship between the secondary graphic code identifier contained in the graphic code information and the shop related information appointed by the merchant under the condition that the secondary graphic code identifier is a global identifier; or under the condition that at least part of the plurality of secondary graphic code identifications corresponding to different primary graphic code identifications are the same, creating a second mapping relation among the primary graphic code identifications, the secondary graphic code identifications and the store related information appointed by the merchant, wherein the primary graphic code identifications and the secondary graphic code identifications are contained in the graphic code information; the second mapping relationship is used for determining the relevant information of the target store corresponding to the target graphic code information contained in the information acquisition request.

11. A graphic code recognition device is characterized by being applied to a merchant client; the device comprises:

the information analysis unit is used for analyzing the graphic code information contained in the graphic code, and the graphic code information comprises a primary graphic code identifier and a secondary graphic code identifier;

the information sending unit is used for sending the primary graphic code identifier and the applet information to a graphic code management server in an associated mode so that the graphic code management server can establish a first mapping relation between the graphic code information and the applet information; the first mapping relation is used for determining target small program information corresponding to target graphic code information contained in an information acquisition request initiated by the user client, the information acquisition request is generated by the user client according to the target graphic code information obtained by analyzing a graphic code, the target small program information is used for indicating the user client to start a target merchant small program which is issued in advance, a secondary graphic code identifier contained in the graphic code information and shop related information appointed by a merchant are sent to the graphic code management server in an associated mode, and a second mapping relation between the secondary graphic code identifier contained in the graphic code information and the shop related information appointed by the merchant is established by the graphic code management server under the condition that the secondary graphic code identifier is a global identifier; or, the graphic code management server creates a second mapping relationship between the primary graphic code identifier and the secondary graphic code identifier contained in the graphic code information and the relevant information of the store appointed by the merchant under the condition that at least parts of the plurality of secondary graphic code identifiers corresponding to different primary graphic code identifiers are the same; the second mapping relationship is used for determining the relevant information of the target store corresponding to the target graphic code information contained in the information acquisition request.

12. A graphic code recognition device is characterized by being applied to a user client; the device comprises:

the small program jumping unit is used for acquiring target small program information corresponding to the target graphic code information determined according to the first mapping relation and responding to the information acquisition request, and starting a target merchant small program which is issued in advance according to the target small program information; the first mapping relation is created by the graphic code management server according to the small program information sent by the merchant client and a primary graphic code identifier contained in the graphic code information, the graphic code information also contains a secondary graphic code identifier, the graphic code information is obtained by analyzing a graphic code by the merchant client, the small program information is specified by the merchant as at least one merchant small program, and the merchant small program of the merchant is pre-issued to the user client; the graphic code information also comprises a secondary graphic code identifier, and under the condition that the secondary graphic code identifier is a global identifier, the secondary graphic code identifier contained in the graphic code information and the shop related information appointed by the merchant are used by the graphic code management server side for creating a second mapping relation; or, under the condition that at least part of the plurality of secondary graphic code identifiers respectively corresponding to different primary graphic code identifiers are the same, the primary graphic code identifier, the secondary graphic code identifier and the shop related information specified by the merchant contained in the graphic code information are used by the graphic code management server to create a second mapping relation; the second mapping relationship is used for determining the relevant information of the target store corresponding to the target graphic code information contained in the information acquisition request.