CN113268287A - Small program starting method and device based on graphic code - Google Patents

Small program starting method and device based on graphic code Download PDF

Info

Publication number
CN113268287A
CN113268287A CN202110797302.6A CN202110797302A CN113268287A CN 113268287 A CN113268287 A CN 113268287A CN 202110797302 A CN202110797302 A CN 202110797302A CN 113268287 A CN113268287 A CN 113268287A
Authority
CN
China
Prior art keywords
merchant
identification information
graphic code
target
applet
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
CN202110797302.6A
Other languages
Chinese (zh)
Inventor
严飞
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Zhejiang Koubei Network Technology Co Ltd
Original Assignee
Zhejiang Koubei Network Technology Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Zhejiang Koubei Network Technology Co Ltd filed Critical Zhejiang Koubei Network Technology Co Ltd
Priority to CN202110797302.6A priority Critical patent/CN113268287A/en
Publication of CN113268287A publication Critical patent/CN113268287A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/445—Program loading or initiating
    • G06F9/44505—Configuring for program initiating, e.g. using registry, configuration files
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06K—GRAPHICAL DATA READING; PRESENTATION OF DATA; RECORD CARRIERS; HANDLING RECORD CARRIERS
    • G06K17/00—Methods or arrangements for effecting co-operative working between equipments covered by two or more of main groups G06K1/00 - G06K15/00, e.g. automatic card files incorporating conveying and reading operations
    • G06K17/0022—Methods or arrangements for effecting co-operative working between equipments covered by two or more of main groups G06K1/00 - G06K15/00, e.g. automatic card files incorporating conveying and reading operations arrangements or provisious for transferring data to distant stations, e.g. from a sensing device
    • G06K17/0025—Methods or arrangements for effecting co-operative working between equipments covered by two or more of main groups G06K1/00 - G06K15/00, e.g. automatic card files incorporating conveying and reading operations arrangements or provisious for transferring data to distant stations, e.g. from a sensing device the arrangement consisting of a wireless interrogation device in combination with a device for optically marking the record carrier

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Software Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Information Transfer Between Computers (AREA)

Abstract

One or more embodiments of the present specification provide a method and an apparatus for starting an applet based on a graphic code. The method is applied to a graphic code management server side and comprises the following steps: acquiring merchant identification information of merchants and applet identification information of various merchant applets corresponding to the merchants, wherein the various merchant applets are issued to user client programs of corresponding categories in advance; generating a graphic code containing the merchant identification information, and establishing a mapping relation between the merchant identification information and the applet identification information of various merchant applets, wherein the mapping relation is used for determining target applet identification information corresponding to target merchant identification information obtained by analyzing the target merchant identification information by any type of user client program, so that the merchant applet corresponding to the target applet identification information is started by any type of user client program, and the target merchant identification information is obtained by analyzing the graphic code displayed by the target merchant by any type of user client program.

Description

Small program starting 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 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. 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, the merchant can paste the graphic code in the physical store, so that the user who enters the store for consumption can recognize the graphic code through the user client and start the merchant applet. The activated merchant applet can display a function page related to the physical store, so that a user can conveniently enjoy online services such as ordering and payment for the physical store in the function page.
Disclosure of Invention
In view of this, one or more embodiments of the present disclosure provide 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 graphic code-based applet starting system, including:
the graphic code management server side acquires merchant identification information of merchants and applet identification information corresponding to various merchant applets of the merchants, the various merchant applets are issued to user client side programs of corresponding categories in advance, and a mapping relation is established between the merchant identification information and the applet identification information of the various merchant applets, and the mapping relation is used for determining target applet identification information corresponding to target merchant identification information obtained by analyzing any type of user client side program; responding to a graphic code acquisition request initiated by a merchant client, generating a graphic code containing the merchant identification information, and returning the graphic code to the merchant client;
the merchant client initiates the graphic code acquisition request to a graphic code management server and acquires the graphic code returned by the graphic code management server;
the user client program of any type analyzes the graphic code displayed by the target merchant to obtain the identification information of the target merchant, and sends the identification information of the target merchant to the graphic code management server; and starting the merchant applet corresponding to the target applet identification information.
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:
acquiring merchant identification information of a merchant and applet identification information of various merchant applets corresponding to the merchant;
generating a graphic code containing the merchant identification information, and establishing a mapping relation between the merchant identification information and the applet identification information of various merchant applets, wherein the mapping relation is used for determining target applet identification information corresponding to target merchant identification information obtained by analyzing the target merchant identification information by any type of user client program, so that the merchant applet corresponding to the target applet identification information is started by any type of user client program, and the target merchant identification information is obtained by analyzing the graphic code displayed by the target merchant by any type of user client program.
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 any type of user client program; the method comprises the following steps:
analyzing the graphic code displayed by the target merchant to obtain target merchant identification information, and sending the target merchant identification information to a graphic code management server;
acquiring target small program identification information, and starting a target merchant small program corresponding to the target small program identification information; the target applet identification information is determined according to a mapping relation and the target merchant identification information, and the mapping relation is established by the graphic code management server according to the obtained merchant identification information of the merchant and the applet identification information of various merchant applets corresponding to the merchant.
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 merchant client; the method comprises the following steps:
initiating a graphic code acquisition request to a graphic code management server, wherein the graphic code management server is used for determining target small program identification information corresponding to target business identification information obtained by analyzing any type of user client program according to a mapping relation generated by the acquired business identification information and small program identification information of various business small programs corresponding to the business, so that the target business small program corresponding to the target small program identification information is started by the user client program of any type;
and acquiring the graphic code which is generated by the graphic code management server in response to the graphic code acquisition request and contains the merchant identification information, wherein the graphic code is used for being displayed by the merchant.
According to a fifth aspect of one or more embodiments of the present specification, a small program starting device based on a graphic code is provided, which is applied to a graphic code management server; the device comprises:
the information acquisition unit is used for acquiring merchant identification information of merchants and applet identification information of various merchant applets corresponding to the merchants;
the graphic code generating unit is used for generating a graphic code containing the merchant identification information, and establishing a mapping relation between the merchant identification information and the applet identification information of various merchant applets, wherein the mapping relation is used for determining target applet identification information corresponding to target merchant identification information obtained by analyzing of any type of user client program, so that the merchant applet corresponding to the target applet identification information is started by any type of user client program, and the target merchant identification information is obtained by analyzing the graphic code displayed by the target merchant by any type of user client program.
According to a sixth aspect of one or more embodiments of the present specification, a graphic code-based applet starting apparatus is provided, which is applied to any type of user client program; the device comprises:
the information sending unit is used for analyzing the graphic code displayed by the target merchant to obtain the identification information of the target merchant and sending the identification information of the target merchant to the graphic code management server;
the small program starting unit is used for acquiring target small program identification information and starting a target merchant small program corresponding to the target small program identification information; the target applet identification information is determined according to a mapping relation and the target merchant identification information, and the mapping relation is established by the graphic code management server according to the obtained merchant identification information of the merchant and the applet identification information of various merchant applets corresponding to the merchant.
According to a seventh aspect of one or more embodiments of the present specification, a small program starting device based on a graphic code is provided, which is applied to a merchant client; the device comprises:
the request initiating unit initiates a graphic code acquisition request to a graphic code management server, and the graphic code management server is used for determining target small program identification information corresponding to target business identification information obtained by analyzing any type of user client program according to a mapping relation generated by the acquired business identification information and small program identification information of various business small programs corresponding to the business, so that the target business small program corresponding to the target small program identification information is started by the user client program of any type;
and the graphic code acquisition unit is used for acquiring a graphic code which is generated by the graphic code management server side in response to the graphic code acquisition request and contains the merchant identification information, and the graphic code is used for being displayed by the merchant.
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 method for initiating an applet based on a graphic code according to any one of the embodiments of the first, second or third aspects.
According to a ninth aspect of one or more embodiments herein, there is provided a computer readable storage medium having stored thereon computer instructions which, when executed by a processor, implement the steps of the method for initiating a small program based on graphic codes as described in any of the above first, second or third aspects.
In the above embodiment, the same merchant may access a plurality of different service platforms, and then for the same merchant, merchant applets of corresponding types may be developed for each different service platform and distributed to the user client programs of each service platform, and each applet corresponding to the merchant may provide a function of performing an operation (such as a product display, an order information acquisition, an order display, an order placement, and the like) for the merchant entity store to the user.
Further, the graphic code management service end can acquire merchant identification information and applet identification information of various merchant applets corresponding to the merchant, establish a mapping relation between the merchant identification information and the applet identification information, and generate a graphic code containing the merchant identification information of the merchant. Because the graphic code generated by the graphic code management server contains the merchant identification information, the graphic code displayed by the user scanning the target merchant by using any user client program can be analyzed to obtain the target merchant identification information, so that the target applet identification information corresponding to the target merchant identification information determined according to the mapping relation can be obtained, and the merchant applet corresponding to the target applet identification information is further started.
Obviously, just because of the existence of the mapping relationship between the merchant identification information and the plurality of applet identification information, for a certain graphic code displayed by a merchant, no matter what type of user client program the user uses to scan the graphic code, the merchant applet issued by the merchant in the user client program can be started correspondingly. Therefore, a user can start the small program of the merchant corresponding to the same merchant by using different user client programs to scan the same graphic code, and the operation is implemented in the started small program of the merchant aiming at the entity store of the merchant, so that the problems that the condition that the user is only allowed to use the code scanning starting small program of a single user client program of a specified type is harsh and the user experience is poor are solved.
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 illustrating a process for scanning a code start applet, 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. 7 is a flowchart of a process for sending a trusted child mapping relationship from a graphics code management server to an application server according to an exemplary embodiment.
Fig. 8 is a schematic structural diagram of an electronic device according to an exemplary embodiment.
Fig. 9 is a block diagram of an applet starting apparatus based on graphic codes according to an exemplary embodiment.
Fig. 10 is a block diagram of another applet launching device based on graphic codes according to an exemplary embodiment.
Fig. 11 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.
Generally, the same merchant can access a plurality of different service platforms, for the same merchant, merchant applets of corresponding types can be developed for the different service platforms respectively and distributed to user client programs of the service platforms, and the applets corresponding to the merchant can provide functions for the user to implement operations (such as commodity display, order information acquisition, order display, order placement and the like) for the entity stores of the merchant.
At present, the same graphic code can only contain related information of one applet, that is, the same graphic code can only support code scanning to open one applet. Under the condition that the merchant respectively issues a plurality of applets on a plurality of service platforms, the merchant needs to respectively display each graphic code aiming at each applet for scanning by users, so that the merchant has higher paving and maintaining costs for the graphic codes. And the user needs to determine the graphic code corresponding to the user client program used by the user firstly and then scan the graphic code to start the corresponding merchant applet, namely, the user is only allowed to start the applet by scanning the code existing in the single user client program of the specified type, so the code scanning condition is harsh, and the user experience is poor.
In contrast, an embodiment of the present specification provides a scheme for starting an applet through a graphic code: for a plurality of merchant applets which are issued by merchants in various types of user client programs and have the same function, the graphic code relation service end establishes a mapping relation between merchant identification information and applet identification information of each merchant applet and generates a graphic code containing the merchant identification information for the merchant to display to a user. Therefore, for the target merchant identification information obtained by scanning the graphic code displayed by the target merchant by different user client programs and analyzing the graphic code, the target applet identification information corresponding to the information can be determined through the mapping relation, and then the user client program can start the merchant applet corresponding to the target applet identification information, namely the started merchant applet is the merchant applet issued by the target merchant in the user client program. Therefore, the user can open different merchant applets by scanning the same graphic code by using different user client programs, and the 'one-code multi-scanning' for the merchant applets is realized. For a merchant, even if a plurality of merchant applets are released, only one graphic code needs to be displayed for scanning by a user, so that the number of graphic codes needing to be laid and maintained is greatly reduced; for the user, the problems that conditions for starting the small program by scanning the code are harsh and experience is poor due to the fact that only a single user client program of a specified type is allowed to be used are effectively avoided. 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 (such as a first mobile phone 13) used by a merchant in a physical store, an electronic device (such as a second mobile phone 14) used by a user entering the physical store, a service acceptance terminal (such as 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.
The first handset 13 and the second handset 14 represent one type of electronic device that may be used by a merchant and a user, respectively. 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 first mobile phone 13 may run a merchant client program to be implemented as a merchant client; accordingly, the second handset 14 may run a user client program to be implemented as a user client.
The network 10 may include various types of wired or wireless networks. For example, Network 10 may include the Public Switched Telephone Network (PSTN) and/or the Internet (Internet). The graphic code management server 11 and the first mobile phone 13 and the second mobile phone 14, the application server 12 and the second mobile phone 14, and the graphic code management server 11 and the application server 12 may establish long connections through the network 10 for communication.
Certainly, through the cooperation between the relevant parties in the applet starting system, the system can realize the starting of the applet of the merchant, and can also realize other functions related to the applet of the merchant, such as graphic code generation, graphic code downloading, mapping relation generation and maintenance, order generation, order payment, consumption evaluation, and the like, which is not limited in the embodiment of the present 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 graphic code management server, a merchant client and a plurality of user client programs.
The graphic code management server acquires merchant identification information of merchants and applet identification information corresponding to various merchant applets of the merchants, wherein the various merchant applets are issued to user client programs of corresponding categories in advance, and a mapping relation is established between the merchant identification information and the applet identification information of the various merchant applets, and the mapping relation is used for determining target applet identification information corresponding to target merchant identification information obtained by analyzing any type of user client programs; responding to a graphic code acquisition request initiated by a merchant client, generating a graphic code containing the merchant identification information, and returning the graphic code to the merchant client;
the merchant client initiates the graphic code acquisition request to a graphic code management server and acquires the graphic code returned by the graphic code management server;
the user client program of any type analyzes the graphic code displayed by the target merchant to obtain the identification information of the target merchant, and sends the identification information of the target merchant to the graphic code management server; and starting a merchant itinerary corresponding to the target applet identification information.
It should be noted that, in the above system, the merchant client, the graphic code management server, and the graphic code involved in the processing process of the user client are all required to be displayed in the corresponding physical store by the merchant.
In addition, the system can also comprise an application server side, which receives and maintains a sub-mapping relation generated by the graphic code management server side, wherein the sub-mapping relation is used for recording the corresponding relation between merchant identification information and an applet identification of a merchant applet issued by a merchant in a user client program corresponding to the application server side; responding to an information acquisition request initiated by a user client program, determining target applet information corresponding to target merchant identification information contained in the information acquisition request according to the sub-mapping relation, and returning target applet data corresponding to the target applet information acquired from the graphic code relation management server to the user client program so that the user client program displays the target applet data (namely, starts the target applet).
The overall process of the applet starting system to realize the scanning of the graphic code starting applet will be briefly described with reference to fig. 2. Referring to fig. 2, fig. 2 is a flowchart illustrating a code scanning start applet according to an exemplary embodiment. As shown in fig. 2, the method may include the steps of:
at step 202, the merchant issues the applet.
The merchant can respectively release a plurality of merchant applets with the same function in a plurality of different user client programs through the service platforms respectively corresponding to the plurality of application service terminals in advance. Wherein the publication may be performed in a variety of ways.
As an exemplary embodiment, a merchant may submit relevant information in each service platform by itself to apply for issuing merchant applets, for example, submit merchant names, qualification and other applet relevant information through a merchant client, and may select or configure relevant functions of the merchant applets to be issued, such as commodity display, order information acquisition, order display and the like, so that the merchant applets are issued to user client programs of corresponding categories (i.e., user client programs provided by the application server for users) through the service platform (actually, the application server corresponding to the service platform). As another exemplary embodiment, the merchant authorization graphic code management server may also be used to issue the merchant applet, for example, the merchant may submit the related information of the applet to the graphic code management server through the merchant client (corresponding authorization operation may be completed in the uploading process), so that the graphic code management server initiates an applet issue application to the application server by using the information, and completes the issuance of the corresponding merchant applet. The merchant identification information may be an account identification of a merchant account registered by the merchant at the merchant client, where the identification may be set by the user or allocated to the merchant by the merchant client.
It can be understood that the process of "a merchant issues each merchant applet at a plurality of user clients under different service platforms" is a process of issuing each merchant applet to a user terminal device operating a corresponding user client. The relevant data (such as the parameter definition, the data display format, the program frame, and the like of the applet) of the successfully issued merchant applet is included in the user client corresponding to the merchant applet (or may be acquired and analyzed by the user client from the corresponding application server). Therefore, after the target applet data of the merchant applet are acquired, the target applet data can be analyzed through the related data, and the target applet data is displayed according to the definition and/or format, so that the target applet is started.
It should be noted that, each merchant applet issued by a plurality of user clients of a merchant under different service platforms can provide at least one same service function for a user. For example, each merchant applet may have exactly the same business function, such as merchant applet 1 and merchant applet 2 having both ordering function and commodity recommendation function; or, the merchant applet 1 and the merchant applet 2 may have only partially the same business functions, such as an order placing function and a commodity recommending function, and an order placing function and a commodity scoring function (in this case, both the merchant applet 1 and the merchant applet 2 have the business function of an order placing function). Of course, the business function realized by each merchant applet can be flexibly adjusted by a developer according to the specific conditions of the service platform type, the applet version and the like, which is not limited in this specification.
And step 204, requesting the graphic code management service end by the merchant to acquire the graphic code, and acquiring the graphic code which is generated by the graphic code management service end and contains merchant identification information.
The merchant can respectively release a plurality of merchant applets with the same function in a plurality of different user client programs through the service platforms respectively corresponding to the plurality of application service terminals in advance. As an exemplary embodiment, a merchant may submit relevant information in each service platform by itself to apply for issuing merchant applets, for example, submit merchant names, qualification and other applet relevant information through a merchant client, and may select or configure relevant functions of the merchant applets to be issued, such as commodity display, order information acquisition, order display and the like, so that the merchant applets are issued to user clients of corresponding categories (i.e., user client programs provided by the application server to users) through the graphic code management server of the service platform. As another exemplary embodiment, the merchant authorization graphic code management server may also be used to issue a merchant applet, for example, a merchant may submit the related information of the applet to the graphic code management server through a merchant client (corresponding authorization operation may be completed in an uploading process), so that the graphic code management server initiates an applet issuing request to the application server by using the information, and completes issuing of the corresponding merchant applet. The merchant identification information may be an account identification of a merchant account registered by the merchant at the merchant client, where the identification may be set by the user or allocated to the merchant by the merchant client.
It should be understood that "a merchant issues each merchant applet respectively by a plurality of user client programs under different service platforms," which is to be understood as issuing each merchant applet respectively to a user terminal device running a corresponding user client program; furthermore, a "merchant issuing applet" should be understood as a merchant issuing a merchant applet to an application server by a corresponding graphic code management server using a merchant client, and a merchant applet issued to an application server is developed based on a user client program corresponding to the application server. The relevant data (such as the parameter definition, the data display format, the program frame, and the like of the applet) of the successfully issued merchant applet is included in the user client program corresponding to the merchant applet (or may be acquired and analyzed from the corresponding application server by the user client program). Therefore, after the target applet data of the merchant applet are acquired, the target applet data can be analyzed through the related data, and then the target applet data are displayed according to the definition and/or format, so that the target applet is started in the user client program.
It should be noted that each merchant applet issued by the merchant through the plurality of user client programs under different service platforms can provide at least one same service function for the user. For example, each merchant applet may have exactly the same business function, such as merchant applet 1 and merchant applet 2 having both ordering function and commodity recommendation function; or, the merchant applet 1 and the merchant applet 2 may have only partially the same business functions, such as an order placing function and a commodity recommending function, and an order placing function and a commodity scoring function (in this case, both the merchant applet 1 and the merchant applet 2 have the business function of an order placing function). Of course, the business function realized by each merchant applet can be flexibly adjusted by a developer according to the specific conditions of the service platform type, the applet version and the like, which is not limited in this specification.
In the code scanning start applet scheme of the present specification, a merchant client may initiate a graphic code acquisition request to a graphic code management server, so that the graphic code management server may generate a graphic code including merchant identification information and return the graphic code to the merchant client.
When the merchant initiates the graphic code acquisition request, store information can be specified for the graphic code to be acquired. For example, when a request for acquiring a graphic code is made for a certain physical store, the graphic code management server may be designated to acquire a corresponding number of graphic codes according to the number of positions where the graphic codes are to be laid in the physical store. If the physical store is a restaurant and 50 dining tables are in the store, the merchant may designate to acquire 50 graphic codes, so that the graphic code management server may generate and record 50 graphic codes sequentially including merchant identifiers and various code values, for example, a first graphic code includes "merchant identifier and code value 1"), a second graphic code includes "merchant identifier and code value 2", … … a fiftieth graphic code includes "merchant identifier and code value 50", and the like.
Or the code value may be generated by the graphic code management server, for example, when a merchant corresponds to multiple physical stores, the merchant may select any physical store from the multiple physical stores displayed in the merchant client to obtain a corresponding graphic code. As in a merchant corresponding to 3 brick and mortar stores: under the conditions of the physical store S1 (30 dining tables), the physical store S2 (100 dining tables) and the physical store S3 (50 dining tables), if a merchant selects the physical store S1 through a merchant client, the graphic code management server may determine that 30 dining tables exist in the physical store S1 according to locally pre-stored store information, and may further generate 30 graphic codes corresponding to the physical store S1 in response to a graphic code acquisition request, where, for example, the first graphic code includes "merchant identifier and code value 1", the second graphic code includes "merchant identifier and code value 2", the … … thirty graphic code includes "merchant identifier and code value 30", and the like. Of course, if the merchant selects the physical store S1 and the physical store S2 at the same time, the graphic code management server may generate the graphic codes corresponding to the physical store S1 at 30 and the graphic codes corresponding to the physical store S2 at 100 respectively, which is not described again.
For example, the following URL information "https" may be recorded in the graphic code generated by the graphic code management server:
the method comprises the steps of// aaa.X1. com/mini/merchant identification/physical store information ", wherein" https:// aaa.X1. com/mini/"can be a platform identification of a service platform to which a graphic code management service end belongs, such as an instance name and an instance number of a graphic code management instance created by the graphic code management service end; the "merchant identifier" is a unique identifier that is different from other merchants for a certain merchant, such as an account identifier of a merchant account registered in the service platform for the certain merchant; the "store information" is information such as the code value used for identifying the corresponding resource in the physical store. The merchant identifier and the store information may be numbers or random codes, or tokens (or tokens) generated from the data or the random codes, which is not limited in this specification.
Taking the case that the merchant identifier and store information are tokens as an example, the information related to the graphic codes of the merchant 1 and the merchant 2 generated by the merchant client can be referred to the following table 1.
Figure 325924DEST_PATH_IMAGE002
The store information in table 1 may be a table number of a dining table where the user sits, a room number selected by the user, and the like, and the merchant identifier and the store information are recorded in the graphic code URL corresponding to the store information under any merchant identifier. And a graphic code URL corresponding to any merchant identifier may be used to print a graphic code (i.e., one row in table 1 corresponds to one graphic code). By the method, the graphic codes in corresponding quantity can be generated according to the specific store information of the entity store corresponding to the merchant.
For the specific use process of the above merchant identification information and store information, reference may be made to the detailed description of the following embodiments, which is not repeated herein. After the graphic code is generated, the graphic code management server side can pack and send the graphic code to the merchant client side, or can store the graphic code locally and download the graphic code by the merchant after the merchant confirms that the graphic code is correct through the merchant client side.
And step 206, displaying the acquired graphic code in a corresponding physical store by the merchant.
After the merchant acquires the graphic code through the merchant client, the graphic code can be directly displayed in the display device, for example, on a screen of a guest greeting platform of an entity store, on ordering terminals respectively placed on each dining table, on an electronic price tag corresponding to each commodity, and the like, and the description is omitted. Alternatively, the graphic code may be printed on the surface of the physical object, for example, printed on paper, engraved on the surface of a label, or the like, and the printed graphic code may be displayed in a physical store, for example, placed on the front desk of the physical store, adhered to a dining table in the physical store, placed in a room in the physical store, adhered to a display area of a product sold in the physical store, or the like, which is not limited in the embodiments of the present specification. 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.
Correspondingly, after the graphic codes are laid or directly displayed, the merchant can also scan and identify each graphic code through the merchant client at one time, so that the resources in the entity store corresponding to each graphic code are bound. Such as binding a first graphic code containing "merchant identification and code value 1" to a first table in a brick and mortar store. Of course, the resources in the entity store corresponding to each graphic code may also be designated when the graphic code acquisition request is initiated, so as to implement the binding, which is not described again.
The graphic Code referred to in this specification may take 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, 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.
In step 208, the user scans the graphic code displayed by the merchant through the user client program to start the merchant applet.
After a merchant displays the acquired graphic code in a physical store and finishes information binding, a user who enters the store for consumption can scan a certain graphic code through a user client program and initiate an information acquisition request according to the analyzed target merchant identification information, so that the acquired applet data of a merchant applet (hereinafter referred to as a target merchant applet) corresponding to the target merchant identification information is displayed, and the starting of the target merchant applet is finished. The started target merchant applet shows the relevant information of the goods or services of the physical store to the user, so that the user can buy the goods or enjoy other online services and the like through the applet.
The above method is described in detail with reference to the following examples. 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, acquiring merchant identification information of a merchant and applet identification information of various merchant applets corresponding to the merchant;
in this embodiment, a merchant may register a merchant account in a service platform to which the graphic code management service side belongs through a merchant client, and further register related information of a physical store under the account, such as store information (store name, address, business hours, and the like) of the merchant, and may also register related information of a commodity, related information of an activity, and the like. Taking the information related to the goods sold in the physical store as an example, the information related to the goods is registered, that is, the information related to the goods is put on the service platform. For example, the commodity-related information may include basic 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.), and the like. Of course, the merchant may cooperate with a plurality of service platforms, so that the merchant client corresponding to each service platform registers the commodity-related information of the entity store corresponding to the merchant client in the corresponding service platform. It can be understood that the information related to the commodities registered by the merchant under the merchant account of a certain service platform is bound with the merchant account.
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 service platform, and the user client may be a buyer-side application corresponding to each service 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 run 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 after being started by the user client programs. And the merchant applet is pre-published to the user client program so that a user entering a physical store for consumption can use the user client program to start the merchant applet by scanning the graphical code.
In this embodiment, for merchants respectively issuing a plurality of merchant applets with the same function in different user client programs, the graphic code management service end may obtain merchant identification information of the merchants; for each merchant applet, the graphic code management server can obtain corresponding applet identifiers respectively. For the merchant identification information, the graphic code management service end may obtain the merchant identification information after the merchant registers the merchant account, or may obtain the merchant identification information after receiving a graphic code obtaining request initiated by a merchant client, which is not limited in this specification.
As described above, the merchant may issue user client programs having the same function in advance in a plurality of types of user client programs in a plurality of ways. Corresponding to different issuing modes, the graphic code management service end can acquire merchant identification information of merchants in various modes. Corresponding to the foregoing embodiment, if the merchant issues the merchant applet in the application service end by itself through the merchant client, the graphic code management service end may determine the applet identification information of the merchant applet designated by the merchant client after receiving the graphic code acquisition request initiated by the merchant client, that is, obtaining the authorization of the merchant for the applet identification information, and then obtain the designated applet identification information. Or, if the merchant authorizes the graphic code management server to replace the issued merchant applet, the graphic code management server may obtain the applet identification information of the issued merchant applet after the successful issuance, and of course, the graphic code management server may also obtain the applet identification information after receiving the graphic code acquisition request initiated by the merchant client, which is not described again.
Step 304, generating a graphic code containing the merchant identification information, and establishing a mapping relationship between the merchant identification information and the applet identification information of various merchant applets, where the mapping relationship is used to determine target applet identification information corresponding to target merchant identification information obtained by analyzing of any type of user client program, so that the merchant applet corresponding to the target applet identification information is started by any type of user client program, and the target merchant identification information is obtained by analyzing the graphic code displayed by the target merchant by any type of user client program.
In this embodiment, after acquiring the merchant identification information, the graphic code management server may generate a graphic code including the merchant identification information, and return the graphic code to the merchant client in response to a graphic code acquisition request initiated by the merchant client, so that the merchant client displays the graphic code in a corresponding physical store. In addition, after acquiring the merchant identification information of the merchant and the applet identification information of each merchant applet, the graphic code management service end also establishes a mapping relationship between the merchant identification information and each applet identification information. Therefore, a user entering the physical store can scan and analyze the graphic code (hereinafter referred to as a target graphic code) displayed by the target merchant by using the user client program to obtain the merchant identification information (hereinafter referred to as target merchant identification information) contained in the graphic code, and further can initiate an information acquisition request (information acquisition request) containing the target merchant identification information. The mapping relationship is used to determine the target applet identification information corresponding to the target merchant identification information, so that the user client program can start the merchant applet (hereinafter referred to as the target merchant applet) corresponding to the target applet identification information.
The graphic code management server may establish the mapping relationship in various ways, and accordingly, the maintainer and the using way of the mapping relationship are different. In an embodiment, the graphic code management server may also establish a total mapping relationship between the identification information and the obtained applet identification information of each type of applet, and maintain the total mapping relationship locally, so that after receiving an information acquisition request directly initiated by a user client program or forwarded by the user client program, target applet identification information (obtained by analyzing the user client program) included in the information acquisition request may be extracted from the information acquisition request, and further determine target applet identification information corresponding to the target applet identification information according to the locally maintained total mapping relationship, where the determined applet identification information is the same as that for starting the corresponding applet by the user client program (i.e., the applet represented by the target applet identification information). At the moment, the graphic code management service end generates and maintains the mapping relation between one merchant identifier and each merchant applet corresponding to each merchant applet issued by the merchant in a unified manner, so that no matter what user client program the user uses to scan the target graphic code, the graphic code management service end can determine corresponding target applet identifier information according to the total mapping relation, and then the user client program starts the corresponding merchant applet. Therefore, the total mapping relation is generated and maintained in a unified mode, the fact that the mapping relation related to the small program cannot be disclosed to the graphic code management server side is guaranteed, the privacy of merchants is protected to a certain extent, the identification information of the target small program is determined in a unified mode, and the use efficiency of the mapping relation is guaranteed.
In another embodiment, the graphic code management server may respectively establish sub-mapping relationships between the identifier information and the obtained applet identifier information of each merchant applet, and further may respectively send each generated sub-mapping relationship to an application server corresponding to a corresponding user client program for maintenance, so that each application server determines, according to the sub-mapping relationship maintained by itself, target applet identifier information corresponding to target merchant identifier information obtained by analysis of the respective user client program. And for the sub-mapping relation generated according to the applet identification information of a certain merchant applet, the 'corresponding user client program' is the user client program with the merchant applet distributed therein. By the method, the user client program used by the user only needs to finish analyzing the graphic code, initiate an information acquisition request to the corresponding graphic code management server and display the graphic code management server after receiving the corresponding target applet data, so that the user client program only needs the corresponding graphic code management server to communicate in the execution process, the processing logic is simple, and the execution efficiency of starting the applet by scanning the code by the user client program is favorably ensured. Moreover, the sub-mapping relation is sent to the application server for maintenance and response to the information acquisition request, and the application server realizes hosting of the sub-mapping relation, so that the processing load of the graphic code management server is reduced, the jump efficiency of the target business cookie is improved, and the user experience is further improved.
For example, when a merchant corresponding to the merchant identification information issues a user client program 1 and a user client program 2, the graphic code management server may generate sub-mapping relationships: the system comprises a sub-mapping relation 1 and a sub-mapping relation 2, wherein the sub-mapping relation 1 is a mapping relation between merchant identification information and applet identification information of a user client program 1, and the sub-mapping relation 2 is a mapping relation between the merchant identification information and the applet identification information of the user client program 2. Further, the graphic code management server may send the sub-mapping relationship 1 to the graphic code management server 1 corresponding to the user client program 1, and send the sub-mapping relationship 2 to the graphic code management server 2 corresponding to the user client program 2, so that the graphic code management server 1 and the graphic code management server 2 maintain the sub-mapping relationship 1 and the sub-mapping relationship 2, respectively. Correspondingly, under the condition that a certain user uses the user client program 1 to scan a target graphic code to determine the identification information of a target merchant and initiate an information acquisition request, the graphic code management server 1 can determine the identification information of the target applet corresponding to the identification information of the target merchant according to the self-maintained sub-mapping relation 2; or, under the condition that a certain user uses the user client program 2 to scan the target graphic code to determine the target merchant identification information and initiate an information acquisition request, the graphic code management server 2 may determine the target applet identification information corresponding to the target merchant identification information according to the self-maintained sub-mapping relationship 2.
Of course, the two embodiments can be alternatively implemented, so that the application server does not need to maintain the sub-mapping relationship under the condition that the graphic code management server maintains the total mapping relationship; and under the condition that the application server side maintains the sub-mapping relationship, the graphic code management server side does not need to maintain the total mapping relationship. As can be seen from the two embodiments, the total mapping relationship maintained by the graphic code management server is the total mapping relationship between the merchant identifier and (all) the applet identifier information, and the sub-mapping relationship maintained by the application server is the component mapping relationship between the merchant identifier and each applet identifier information, so that the set of the sub-mapping relationships respectively corresponding to the applet identifier information of each merchant applet issued by the same merchant is the total mapping relationship. In the embodiment where the user client program 1 and the user client program 2 are issued by the merchant corresponding to the merchant identification information, the total mapping relationship maintained by the graphic code management server may include the sub-mapping relationship 1 and the sub-mapping relationship 2.
Further, under the condition that the application server maintains the sub-mapping relationship, the application server needs to ensure the validity of the application server corresponding to each graphic code management server. Therefore, for the sub-mapping relationship sent by the graphic code management server, the application server can maintain the sub-mapping relationship (i.e. save the sub-mapping relationship and set the sub-mapping relationship to be valid) under the condition that the verification is passed. Taking any one of the application servers corresponding to various user client programs as an example, the graphic code management server may send a corresponding sub-mapping relationship to the any one graphic code management server, and provide authority certification information for configuring the mapping relationship issued by the any one application server to the graphic code management server to the any one graphic code management server, so that the received sub-mapping relationship is maintained by the any one application server under the condition that the verification authority certification information passes. The authority certification information may be a token (token) generated by the application server, where the token may be generated by the application server according to information such as a server identifier of the graphic code management server or a platform identifier of the service platform of the graphic code management server, or may be generated by the application server according to the server identifier, the platform identifier, a sub-mapping relationship, and/or sending time when the graphic code management server directly sends a sub-mapping relationship to the application server. Of course, the authority certification information may be other information, and the specific form and generation method of the authority certification information are not limited in this specification. Moreover, the authority certification information may be stored in an authority certification file in a format of txt, pdf, or in an authority certification sentence in a format of json, so that the application server may verify the authority certification file or the authority certification sentence. Therefore, the authority certification information is issued to the graphic code management server by any application server, and the graphic code management server provides the authority certification information to any application server for verification, so that the sub-mapping relationship sent to the application server by the graphic code management server is maintained by the application server only when the authority certification information passes the verification, and the real effectiveness of the sub-mapping relationship maintained by the application server is ensured through the certification of the authority of the graphic code management server.
And any application server side can verify the authority certification information in an information comparison mode. For example, when issuing the authority certification information to the graphic code management server, the application server may locally maintain a piece of standard certification information that is the same as the authority certification information (the standard certification information may be regarded as a local backup of the authority certification information). Therefore, the graphic code management server side can determine a first storage address according to the merchant identification information and the authority certification information after receiving the authority certification information, and store the authority certification information in the first storage address (of course, under the condition that the sub-mapping relation is sent to the application server side firstly, the graphic code management server side can inform the application server side after storing the authority certification information, or the graphic code management server side can also send the sub-mapping relation to the application server side after storing the authority certification information); correspondingly, the application server side can determine a second storage address according to the received merchant identification information and the locally maintained standard certification information in the sub-mapping relationship, and tries to read the authority certification information from the address: if the permission certification information is successfully read from the second storage address and the read permission certification information is consistent with the locally maintained standard certification information, the application server side can determine that the permission certification information passes verification; otherwise, if the permission certification information cannot be read from the second storage address or the read permission certification information is inconsistent with the locally maintained standard certification information, the application server side can determine that the permission certification information is not verified.
According to the process, on one hand, if the graphic code management server side has legal ownership over the first storage address, the graphic code management server side can smoothly upload the authority certification information to the address; on the other hand, because the standard certification information locally maintained by the application server is the same as the authority certification information issued to the graphic code management server, under normal conditions, the second storage address determined by the application server should be the same as the first storage address, so that if the authority certification information read by the application server from the second storage address is consistent with the locally maintained authority certification information, it can be determined that the graphic code management server really has a legal ownership over the first storage address, and it is further indicated that the merchant client corresponding to the merchant identification information recorded in the sub-mapping relationship is really a legal merchant client at the graphic code management server, so that the validity of the graphic code management server and the sub-mapping relationship sent by the graphic code management server can be fully proved under the condition that the authority certification information is verified.
In an embodiment, for the above embodiment in which each application server maintains the sub-mapping relationship, any application server may be simultaneously docked with multiple service platforms, that is, the application server may be connected with multiple graphic code management servers, so that the application server may further determine a corresponding merchant applet in the graphic code management server indicated by the merchant identification information. For example, the merchant identification information may include a platform identifier of a service platform to which the graphic code management service terminal belongs and a merchant identifier of the merchant, so that the merchant identification information may be used for querying, by an application service terminal corresponding to any type of user client program, a merchant applet corresponding to the merchant identifier in an applet distributed by the service platform corresponding to the platform identifier.
Taking the case that the application server is simultaneously connected with the graphic code management server 1 and the graphic code management server 2 which belong to different service platforms, suppose that the merchant 11 and the merchant 12 corresponding to the graphic code management server 1 respectively issue the merchant applet 1 and the merchant applet 2 in the user client program corresponding to the application server, and the merchant 21 and the merchant 22 corresponding to the graphic code management server 2 respectively issue the applet identification information 1 and the applet identification information 2 in the user client program corresponding to the application server. If the application server receives the sub-mapping relationship sent by the graphic code management server 1, the application server can determine all merchant applets issued by the graphic code management server 1 in the user client program corresponding to the application server according to the platform identifiers in the sub-mapping relationship, and then can query merchant applets (namely merchant applets 1) issued by merchants 11 in the merchant applets according to merchant identifiers (such as merchant identifiers of the merchants 11) in the sub-mapping relationship, and determine the merchant applets 1 as merchant applets corresponding to the merchant identifiers. In fact, the sub-mapping relationship received by the application server is the sub-mapping relationship between the merchant identification information of the merchant 11 and the applet identification information of the merchant applet 1. Therefore, by the method, the merchant applets issued by a certain platform can be determined through the platform identification, and the merchant applets issued by the sub-mapping relationship are further determined in the merchant applets, so that the query efficiency of the merchant applets is improved, and the waiting time after code scanning of a user is reduced.
After the graphic code management server generates a graphic code and a merchant displays the graphic code in an entity store, a user entering the entity store can scan a target graphic code through a user client program running in terminal equipment of the user, analyze target merchant identification information from the target graphic code, and then generate an information acquisition request containing the target merchant identification information. By means of the foregoing embodiment, the graphic code management server or the application server may determine, according to the secondary mapping relationship or the sub-mapping relationship, the target applet identification information corresponding to the target merchant identification information, so that the graphic code management server may determine the target applet data of the target merchant applet indicated by the target applet identification information, and return the data to the user client program directly or through the corresponding application server to the user client program.
In this embodiment, the user client program may display the target applet data received by the user client program, and it can be understood that the target applet data displayed for the first time after the user client program 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 program 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 client, so as to further display commodity related information of the entity store registered in advance by the merchant on the service 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.
In an embodiment, the graphic code management server may obtain order placing information determined by any type of user client program in response to an order placing operation implemented by a user, and generate a target order according to the order placing information. For example, after the user client program starts the merchant applet and displays information such as commodities, the user can perform corresponding ordering operation through the merchant applet. After detecting the order placing operation performed by the user, the user client program may determine order placing information at this time, such as information about the model (e.g., SKU, Stock Keeping Unit, etc.) and quantity of the goods purchased by the user, and may further include coupon information about a coupon (e.g., a discount coupon, a voucher, a token, etc.) specified by the user, which is not limited in this specification.
In fact, as described above, the graphic code management server may generate the graphic code according to the merchant identification information and the store information of the merchant, so that the target graphic code analyzed by the user using the user client program may include the store information. Furthermore, the graphic code management server can receive target store information obtained by analyzing the graphic code displayed in the physical store by the target merchant through any type of user client program, and generate a target order corresponding to the physical store according to the order placing information and the target store information, so as to ensure that the order corresponds to the user one by one.
Further, after the graphic code management client 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 scanning a service acceptance terminal by a user client program, and finally the consumption process in the physical store is completed.
In addition, when the service acceptance terminal is a payment terminal such as a POS machine, 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 applet starting scheme in this specification, the same merchant may issue multiple merchant applets having the same function (such as commodity display, order information acquisition, order display, and the like) at multiple different user client programs, respectively, and the mapping relationship generated by the graphic code management server is the corresponding relationship between one merchant identification information for representing the merchant and the applet identification information of the multiple merchant applets. Because the graphic code generated by the graphic code management server contains the merchant identification information, the graphic code displayed by the user scanning the target merchant by using any user client program can be analyzed to obtain the target merchant identification information, so that the target applet identification information corresponding to the target merchant identification information determined according to the mapping relation can be obtained, and the merchant applet corresponding to the target applet identification information is further started.
Obviously, because the mapping relationship between the merchant identification information and the plurality of applet identification information exists, for a certain graphic code displayed by a merchant, no matter what type of user client program the user uses to scan the graphic code, the merchant applet issued by the merchant in the user client program can be correspondingly started. Therefore, the user scans the same graphic code by using different user client programs, and can start different merchant applets (with the same function) issued by the same merchant, namely, the starting effect of one-code multi-scan is presented in the process of directly starting the applets by scanning the graphic codes.
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 any type of user client program, and may include the following steps:
step 402, analyzing the graphic code displayed by the target merchant to obtain the identification information of the target merchant, and sending the identification information of the target merchant to the graphic code management server.
Step 404, acquiring identification information of a target small program, and starting a target merchant small program corresponding to the identification information of the target small program; the target applet identification information is determined according to a mapping relation and the target merchant identification information, and the mapping relation is established by the graphic code management server according to the obtained merchant identification information of the merchant and the applet identification information of various merchant applets corresponding to the merchant.
As mentioned above, the method further comprises:
analyzing a graphic code displayed in an entity store by a target merchant to obtain target store information; and the number of the first and second groups,
and determining ordering information in response to an ordering operation implemented by a user, wherein the target store information and the ordering information are used by the graphic code management server to generate a target order corresponding to the physical store.
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 merchant client may include the following steps:
step 502, initiating a graphic code acquisition request to a graphic code management server, wherein the graphic code management server is used for determining target applet identification information corresponding to target merchant identification information obtained by analyzing any type of user client program according to a mapping relation generated by the acquired merchant identification information and the applet identification information of various merchant applets corresponding to the merchant, so that the target merchant applet corresponding to the target applet identification information is started by the user client program of any type.
Step 504, acquiring the graphic code containing the merchant identification information generated by the graphic code management server in response to the graphic code acquisition request, where the graphic code is used for being displayed by the merchant.
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 entity store and store information as a table number as an example, a process in which a merchant acquires and displays a graphic code, and a user scans a target graphic code through a user client program corresponding to any application server i to start an applet is described in detail, where the interaction process may include the following steps:
step 602, the graphic code management service end obtains merchant identification information and applet identification information.
As described above, the merchant may issue the merchant applet with the same service function to the multiple user client programs corresponding to the multiple user clients respectively through the graphic code management server, and the specific issuing process is not described again, and the following step is a starting process of the issued merchant applet.
For merchants respectively issuing a plurality of merchant applets with the same function in different user client programs, the graphic code management service end can acquire merchant identification information of the merchants; for each merchant applet, the graphic code management server can obtain corresponding applet identifiers respectively. For the merchant identification information, the graphic code management service end may obtain the merchant identification information after the merchant registers the merchant account, or may obtain the merchant identification information after receiving a graphic code obtaining request initiated by a merchant client, which is not limited in this specification.
As described above, the merchant may issue user client programs having the same function in advance in a plurality of types of user client programs in a plurality of ways. Corresponding to different issuing modes, the graphic code management service end can acquire merchant identification information of merchants in various modes. Corresponding to the foregoing embodiment, if the merchant issues the merchant applet in the application service end by itself through the merchant client, the graphic code management service end may determine the applet identification information of the merchant applet designated by the merchant client after receiving the graphic code acquisition request initiated by the merchant client, so as to obtain the authorization of the merchant for the applet identification information, and further obtain the designated applet identification information. Or, if the merchant authorizes the graphic code management server to replace the issued merchant applet, the graphic code management server may obtain the applet identification information of the issued merchant applet after the successful issuance, and of course, the graphic code management server may also obtain the applet identification information after receiving the graphic code acquisition request initiated by the merchant client, which is not described again.
And step 604, the graphic code management service side generates a mapping relation between the merchant identification information and each small program identification information.
Step 606, the graphic code management server sends the corresponding sub-mapping relation to the application server.
Step 608, the application server maintains the sub-mapping relationship after the verification is passed.
After acquiring the merchant identification information and the applet identification information of each merchant applet issued by the merchant, the graphic code management server can establish a corresponding mapping relationship. For example, sub-mapping relationships between merchant identification information and each applet identification information may be established, and each sub-mapping relationship may be sent to each application server. The following steps are described by taking any application server i in the plurality of application servers as an example, and for brevity, the following steps will refer to the "application server i" as an "application server". The application server receives and maintains the sub-mapping relationship sent by the graphic code management server after the authority certification information issued by the graphic code management server passes the verification, and can also verify the authority certification information issued by the graphic code management server after receiving the sub-mapping relationship sent by the graphic code management server and maintain the authority certification information under the condition that the authority certification information passes the verification. For a specific verification process corresponding to step 606-608, reference may be made to the following embodiment corresponding to fig. 7, which is not repeated herein.
Of course, the embodiment described in fig. 6 is only exemplary, and actually, the graphic code management service end may also generate a total mapping relationship between the merchant identifier and each applet identifier, and locally maintain the total mapping relationship, and accordingly, in the process of determining the target applet identifier corresponding to the target merchant identifier in the subsequent step 622, the graphic code management service end determines the target applet identifier according to the locally maintained total mapping relationship, and the specific process is not repeated.
Step 610, the merchant client sends a graphic code acquisition request to the graphic code management server.
Step 612, the graphic code management server generates a graphic code.
And step 614, the graphic code management service end returns the generated graphic code to the merchant client.
In step 616, the merchant client displays the obtained graphic code.
After issuing the small programs, the merchant can initiate a graphic code acquisition request to the graphic code management server through the merchant client, so that the graphic code management server can determine a corresponding merchant according to an initiator of the request, further generate a graphic code acquisition request containing merchant identification information of the merchant, and return the graphic code to the merchant client. Therefore, the merchant can directly display the graphic code acquired by the merchant client in the display equipment of the physical store, or print the graphic code on the physical material and display the graphic code in the physical store. The user entering the store can use a user client program (provided with small programs corresponding to the merchant in advance) with a graphic code analysis function running in the device to scan a certain target graphic code, and starts a corresponding (locally issued) target merchant small program through analyzed target merchant identification information.
It should be noted that, the execution sequence of steps 610-616 and 602-608 is not limited in this specification. For example, step 610-.
Step 618, the user client program scans the target graphic code displayed by the merchant client and analyzes the target graphic code to obtain the target merchant identification information.
Step 620, the user client program sends an information acquisition request containing the target merchant identification information to the application server.
At step 622, the application server determines the target applet identification information corresponding to the target merchant identification information according to the locally maintained sub-mapping relationship.
After the target merchant applet is scanned and analyzed to obtain corresponding target merchant identification information, the user client program initiates an information acquisition request containing the target merchant identification information to the application server, so that the application server can determine the target applet identification information corresponding to the target merchant identification information according to a locally maintained sub-mapping relation.
The target merchant identification information may include a target platform identification of a service platform to which the graphic code management server belongs and a target merchant identification of a target merchant, so that the application server may determine, through the target platform identification, an applet issued by the application server corresponding to the user client program on the service platform corresponding to the target platform identification under the condition that the application server locally maintains a sub-mapping relationship for a plurality of service platforms, and query a merchant applet corresponding to the target merchant identification therein.
It is not assumed that the target URL of the target graphic code is "https:// aaa.x1.com/mini/0001/002", where "https:// aaa.x1.com/mini" is the target platform identification, "0001" is the target merchant identification, and "0020" is the target store information. Thus, after the user client program parses the target URL, an information acquisition request containing target merchant identification information "https:// aaa. X1. com/mini/0001" may be generated. Therefore, the application server can determine all applets issued by the service platform X1 (to be distinguished from other service platforms such as X2 and X3) according to the target platform identifiers in the information, and further determine the target applet identifier corresponding to the target merchant identifier "0001" according to the locally maintained sub-mapping relationship.
Step 624, the application server requests the graphic code management server and obtains the target applet data of the target merchant applet corresponding to the target applet identification information.
In step 626, the application server sends the target applet data to the user client program.
After determining the target applet identification information, the application server may send the target applet identification information to the graphic code management server to request the graphic code management server to acquire corresponding target applet data, such as applet home page data, and after receiving the data returned by the graphic code management server, forward the data to the user client program. Of course, the application server may also associate the target applet identification information with the client identification of the user client program and send the associated information to the graphic code management server, so that the graphic code management server may directly send the target applet data to the user client program, thereby reducing the forwarding workload of the graphic code management server and increasing the starting speed of the applet.
Step 628, the user client program displays the target applet data to implement starting the target merchant applet.
The user client program may display the target applet data received by the user client program, and it can be understood that the target applet data displayed for the first time after the user client program 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 program 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 client, so as to further display commodity related information of the entity store registered in advance by the merchant on the service 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.
In step 630, the user client detects the order placing operation performed by the user and determines order placing information.
Step 632, the user client program parses the target graphic code to obtain the target store information.
In step 634, the user client sends the order information and the target store information to the graphic code management server.
The user can implement ordering operation in the started small program and provide corresponding ordering information to the graphic code management server so that the graphic code management server can generate a target order. The order placing information may be information such as the model and number of commodities selected by the user, and may further include coupon information of a coupon (such as a discount coupon, a voucher, a token, and the like) designated by the user. In addition, in order to ensure that the generated order corresponds to the current physical store, the user client program may further parse the target store information in the target URL, so that the target store information and the order information may be provided to the graphic code management server in an associated manner, so that the graphic code management server generates a target order containing the target store information, so that the target store information contained in the target order corresponds to the target physical store.
The user client program provides the order information or associates the order information and the target store information to the graphic code management server, and the order information or the target store information may be directly sent to the graphic code management server, or may also be sent to the application server and forwarded to the graphic code management server by the application server, which is not limited in this specification. Of course, the target store information may also be included in the information acquisition request and provided to the graphic code management server, where the information acquisition request carries the complete content of the target URL.
In step 636, the graphic code management server determines the target table number.
In an embodiment, after the merchant displays each graphic code in the physical store, the merchant may further use the merchant client to scan each graphic code one by one, so as to bind the target store information in each graphic code with the actual resource in the physical store, for example, bind the target store information "0001" in the target URL with "table 1" and the like. Correspondingly, the graphic code management server can maintain the binding relationship, so that the graphic code management server can determine the corresponding table number according to the received target store information.
At step 638, the graphic code management server generates a target order corresponding to the target table number.
In step 640, the graphic code management server sends the generated target order to the user client program.
The graphic code management server side can generate the target order after receiving the information. Corresponding to the steps, if only order placing information is received, a target order only containing the order placing information can be generated; if the target store information is received, a target order corresponding to the target entity store may be further generated, for example, a target order including the order placing information and the target store information is directly generated, or a target order including the order placing information and the target table number is generated, and the like.
In this embodiment, after the target order is generated, the graphic code management server 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 program, so that the user client program 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 the physical store 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.
Through the embodiment, the same merchant can respectively issue a plurality of merchant applets with the same functions (such as commodity display, order information acquisition, order display and the like) at a plurality of different user client programs, and the mapping relation generated by the graphic code management server is the corresponding relation between one merchant identification information for representing the merchant and the applet identification information of the merchant applets. Because the graphic code generated by the graphic code management server contains the merchant identification information, the graphic code displayed by the user scanning the target merchant by using any user client program can be analyzed to obtain the target merchant identification information, so that the target applet identification information corresponding to the target merchant identification information determined according to the mapping relation can be obtained, and the merchant applet corresponding to the target applet identification information is further started.
Obviously, because the mapping relationship between the merchant identification information and the plurality of applet identification information exists, for a certain graphic code displayed by a merchant, no matter what type of user client program the user uses to scan the graphic code, the merchant applet issued by the merchant in the user client program can be correspondingly started. Therefore, the user scans the same graphic code by using different user client programs, and can start different merchant applets (with the same function) issued by the same merchant, namely, the starting effect of one-code multi-scan is presented in the process of directly starting the applets by scanning the graphic codes.
The following describes a process of sending the trusted child mapping relationship from the graphic code management server to the application server with reference to fig. 7. As shown in fig. 7, the process may include the following steps:
step 702, the graphic code management service end checks whether the merchant uploads the sub-mapping relationship.
Before uploading the sub-mapping relationship, the graphic code management server may check the mapping relationship generation record or the sub-mapping relationship uploading record to determine whether the sub-mapping relationship corresponding to the current merchant identification information has been uploaded to the application server, so as to avoid repeated uploading. Obviously, under the condition that it is determined that the sub-mapping relationship corresponding to the current merchant identification information has not been uploaded, the graphic code management server may proceed to step 702, otherwise, the merchant may be reminded that the sub-mapping relationship has been uploaded, and the subsequent process is terminated.
Of course, after receiving the sub-mapping relationship uploaded by the graphic code relationship service end or receiving the authority certification file acquisition request sent by the graphic code management service end, the application service end may also determine whether the sub-mapping relationship corresponding to the merchant identification information has been maintained locally. Similarly, under the condition that the sub-mapping relationship corresponding to the local non-maintained merchant identification information is determined, the graphic code management server may proceed to step 702, otherwise, the merchant may be reminded of uploading and the subsequent process is terminated.
Step 704, the graphic code management server sends an authority certificate file acquisition request to the application server.
Under the condition that the sub-mapping relation corresponding to the current merchant identification information is determined not to be uploaded, the graphic code management server side can send an authority certificate file acquisition request to the application server side so as to acquire an authority certificate file issued by the application server side for subsequent verification.
Step 706, the application server generates an authority certificate file for the graphic code management server.
In step 708, the application server locally backs up the standard certificate.
And step 710, the application server sends the authority certification file to the graphic code management server.
In response to the authority certification file obtaining request, the application server may generate a token (i.e., authority certification information) according to information such as a server identifier of the graphic code management server or a platform identifier of the service platform of the graphic code management server, and record the token in the authority certification file. At this time, on one hand, the application server side can issue the authority certificate file to the graphic code management server side; on the other hand, the application server side can copy the authority certificate as a standard certificate and maintain the standard certificate locally. It should be noted that the "authority certificate" and the "standard certificate" in this specification are only for distinguishing the two files, and in the practice of the scheme, the file names of the two files should be the same to ensure that the first storage address and the second storage address are the same.
The token may also be generated in other manners, for example, step 714 may be executed between steps 702 and 704, so that the graphic code management server may generate the token according to the server identifier, the platform identifier, the sub-mapping relationship, and/or the sending time. In addition, the above-mentioned authority certification file can be in the format of txt, pdf, etc.
In step 712, the graphic code management server uploads the authority certificate to the first storage address.
After receiving the authority certification file issued by the application server, the graphic code management server may determine the first storage address according to the merchant identification information and the authority certification file. And if the merchant identification information contained in the graphic code acquisition request is: under the condition that the authority certificate file name is 'certificate file x 1', the graphic code management server side can generate a first storage address of 'https:// aaa.X1. com/mini/merchant identifier/certificate file x 1', and upload the authority certificate file to the address.
In step 714, the graphic code management server uploads the sub-mapping relationship to the application server.
Furthermore, the graphic code management server can upload the sub-mapping relationship to the application server so that the application server can read and verify the sub-mapping relationship.
Of course, as mentioned above, the graphic code management server may also perform step 714 and then perform step 704 after performing step 702, which is not limited in this specification. At this time, the graphic code management server may send a notification message to the application server after uploading the authority certificate to the first storage address, so that the application server knows and reads the authority certificate.
In step 716, the application server reads the authority certificate from the second storage address.
After receiving a notification message sent by the application server (at this time, the sub-mapping relationship uploaded by the application server has been acquired) or the sub-mapping relationship uploaded by the application server, the graphic code management server may determine the second storage address according to the merchant identification information in the sub-mapping relationship and the locally stored standard certificate. In the foregoing embodiment, since the file names of the authority certificate file and the standard certificate file are the same, the application server may generate a second storage address: and the application server can read the authority certification file from the address by using the https:// aaa.X1. com/mini/merchant identification/certification file x 1'.
Step 718, the application server compares whether the authority certificate is consistent with the standard certificate.
At this time, the application server may compare whether tokens respectively recorded in the authority certificate and the standard certificate are the same: if the two are the same, the characterization graph code management service end is a legal requester which has ownership of merchant identification information (or a domain name) of https:// aaa.X1. com/mini/merchant identification, so that the verification is passed; at which point it may proceed to step 720. Otherwise, if the two are different, the graphic code management service end does not have ownership of the merchant identification information, namely 'https:// aaa. X1. com/mini/merchant identification', and is an illegal requester, and at this time, the child mapping relationship can be directly discarded, and the process is terminated. Further, an illegal request, an alarm, or the like may be recorded.
Step 720, the application server maintains the sub-mapping relationship.
And under the condition that the verification is passed, the application server side can maintain the sub-mapping relationship locally, namely, the sub-mapping relationship is stored in a locally accessible storage space, and the sub-mapping relationship is set as the sub-mapping relationship corresponding to the merchant identification information, so that the target applet identification information corresponding to the target merchant identification information is determined according to the sub-mapping relationship in the subsequent response to the information acquisition request.
Therefore, the authority certification information is issued to the graphic code management server by any application server, and the graphic code management server provides the authority certification information to any application server for verification, so that the sub-mapping relationship sent to the application server by the graphic code management server is maintained by the application server only when the authority certification information passes the verification, and the real effectiveness of the sub-mapping relationship maintained by the application server is ensured through the certification of the authority of the graphic code management server.
On one hand, if the graphic code management server side has legal ownership over the first storage address, the graphic code management server side can smoothly upload the authority certification file to the address; on the other hand, because the standard certificate locally maintained by the application server is the same as the authority certificate issued to the graphic code management server, under normal conditions, the second storage address determined by the application server should be the same as the first storage address, so that if the authority certificate read by the application server from the second storage address is consistent with the locally maintained authority certificate, the graphic code management server can be determined to really have legal ownership over the first storage address, and then the merchant client corresponding to the merchant identification information recorded in the sub-mapping relationship is really a legal merchant client at the graphic code management server, so that under the condition that the authority certificate passes verification, the validity of the graphic code management server and the sub-mapping relationship sent by the graphic code management server can be fully proved.
Fig. 8 is a schematic structural diagram of an electronic device according to an exemplary embodiment. Referring to fig. 8, at the hardware level, the apparatus includes a processor 802, an internal bus 804, a network interface 806, a memory 808, and a non-volatile memory 810, but may also include hardware required for other services. The processor 802 reads a corresponding computer program from the non-volatile memory 810 into the memory 808 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. 9, in a software implementation, the applet starting apparatus based on the graphic code is applied to a graphic code management server; the device comprises:
an information obtaining unit 901, which obtains merchant identification information of a merchant and applet identification information of various merchant applets corresponding to the merchant;
the graphic code generating unit 902 generates a graphic code including the merchant identification information, and establishes a mapping relationship between the merchant identification information and the applet identification information of each type of merchant applet, where the mapping relationship is used to determine target applet identification information corresponding to target merchant identification information obtained by analyzing by a user client program of any type, so that the merchant applet corresponding to the target applet identification information is started by the user client program of any type, and the target merchant identification information is obtained by analyzing the graphic code displayed by the target merchant by the user client program of any type.
Alternatively to this, the first and second parts may,
the graphic code generating unit 902 is further configured to: respectively establishing sub-mapping relations between the merchant identification information and the applet identification information of various merchant applets;
the device further includes a relationship sending unit 903, configured to send each sub-mapping relationship to an application server corresponding to a corresponding user client program for maintenance, so that each application server determines, according to the sub-mapping relationship maintained by itself, target applet identification information corresponding to target merchant identification information obtained by analysis of the respective user client program.
Optionally, the relationship sending unit 903 is further configured to:
aiming at any application server side in application server sides corresponding to various user client side programs, sending a corresponding sub-mapping relation to the any application server side;
and providing authority certification information aiming at the configuration mapping relationship issued by any application server side to the graphic code management server side, so that the received sub-mapping relationship is maintained by any application server side under the condition that the authority certification information is verified to pass.
Optionally, the any application server maintains standard certification information corresponding to the authority certification information; the device further comprises:
an information storage unit 904, configured to store the authority certification information in a storage space corresponding to a first storage address determined according to the merchant identification information and the authority certification information, so that the any application server accesses a storage space corresponding to a second storage address to read the authority certification information, and determines that the authority certification information passes verification when the authority certification information is consistent with the standard certification information, where the second storage address is determined by the any application server according to the standard certification information and the received merchant identification information included in the sub-mapping relationship.
Optionally, the merchant identification information includes a platform identifier of a service platform to which the graphic code management server belongs and a merchant identifier of the merchant, and the merchant identification information is used for querying, by an application server corresponding to the user client program of any type, a merchant applet corresponding to the merchant identifier in an applet issued by the service platform corresponding to the platform identifier.
Optionally, the method further includes:
the order generating unit 905 acquires order placing information determined by the user client program of any type in response to an order placing operation implemented by a user, and generates a target order according to the order placing information.
Alternatively to this, the first and second parts may,
the graphic code generating unit 902 is further configured to: generating a graphic code according to the merchant identification information and store information of the merchant;
the order generation unit 905 is further configured to: and receiving target store information obtained by analyzing a graphic code displayed by a target merchant in an entity store by the user client program of any type, and generating a target order corresponding to the entity store according to the order placing information and the target store information.
Referring to fig. 10, in another software embodiment, the applet launching apparatus based on graphic codes is applied to any type of user client program; the device comprises:
the information sending unit 1001 analyzes the graphic code displayed by the target merchant to obtain target merchant identification information, and sends the target merchant identification information to the graphic code management server;
an applet starting unit 1002, configured to acquire target applet identification information and start a target merchant applet corresponding to the target applet identification information; the target applet identification information is determined according to a mapping relation and the target merchant identification information, and the mapping relation is established by the graphic code management server according to the obtained merchant identification information of the merchant and the applet identification information of various merchant applets corresponding to the merchant.
Optionally, the method further includes:
the information analysis unit 1003 is used for analyzing the graphic code displayed by the target merchant in the physical store to obtain target store information; and the number of the first and second groups,
an information determination unit 1004, which determines order placing information in response to an order placing operation implemented by a user, wherein the target store information and the order placing information are used by the graphic code management server to generate a target order corresponding to the physical store.
Referring to fig. 11, in yet another software embodiment, the applet launching device based on graphic codes is applied to a merchant client; the device comprises:
a request initiating unit 1101 that initiates a graphic code acquisition request to a graphic code management server, where the graphic code management server is used to determine target applet identification information corresponding to target merchant identification information obtained by analyzing any type of user client program according to a mapping relationship generated by the acquired merchant identification information and applet identification information corresponding to various merchant applets of the merchant, so that the target merchant applet corresponding to the target applet identification information is started by the user client program of any type;
the graphic code obtaining unit 1102 is configured to obtain a graphic code which is generated by the graphic code management server in response to the graphic code obtaining request and contains the merchant identification information, where the graphic code is used for being displayed by the merchant.
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 (14)

1. An applet starting system based on graphic codes, comprising:
the graphic code management server side acquires merchant identification information of merchants and applet identification information corresponding to various merchant applets of the merchants, the various merchant applets are issued to user client side programs of corresponding categories in advance, and a mapping relation is established between the merchant identification information and the applet identification information of the various merchant applets, and the mapping relation is used for determining target applet identification information corresponding to target merchant identification information obtained by analyzing any type of user client side program; responding to a graphic code acquisition request initiated by a merchant client, generating a graphic code containing the merchant identification information, and returning the graphic code to the merchant client;
the merchant client initiates the graphic code acquisition request to a graphic code management server and acquires the graphic code returned by the graphic code management server;
the user client program of any type analyzes the graphic code displayed by the target merchant to obtain the identification information of the target merchant, and sends the identification information of the target merchant to the graphic code management server; and starting the merchant applet corresponding to the target applet identification information.
2. 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:
acquiring merchant identification information of a merchant and applet identification information of various merchant applets corresponding to the merchant;
generating a graphic code containing the merchant identification information, and establishing a mapping relation between the merchant identification information and the applet identification information of various merchant applets, wherein the mapping relation is used for determining target applet identification information corresponding to target merchant identification information obtained by analyzing the target merchant identification information by any type of user client program, so that the merchant applet corresponding to the target applet identification information is started by any type of user client program, and the target merchant identification information is obtained by analyzing the graphic code displayed by the target merchant by any type of user client program.
3. The method of claim 2,
the establishing of the mapping relation between the merchant identification information and the applet identification information of various merchant applets comprises the following steps: respectively establishing sub-mapping relations between the merchant identification information and the applet identification information of various merchant applets;
the method further comprises the following steps: and respectively sending each sub-mapping relation to an application server corresponding to the corresponding user client program for maintenance, so that each application server determines target small program identification information corresponding to target merchant identification information obtained by analyzing the respective user client program according to the self-maintained sub-mapping relation.
4. The method according to claim 3, wherein the step of sending each sub-mapping relationship to an application server corresponding to a corresponding user client program for maintenance comprises:
aiming at any application server side in application server sides corresponding to various user client side programs, sending a corresponding sub-mapping relation to the any application server side;
and providing authority certification information aiming at the configuration mapping relationship issued by any application server side to the graphic code management server side, so that the received sub-mapping relationship is maintained by any application server side under the condition that the authority certification information is verified to pass.
5. The method of claim 4, wherein any application server maintains standard attestation information corresponding to the attestation-of-rights information; the method further comprises the following steps:
and storing the authority certification information to a storage space corresponding to a first storage address determined according to the merchant identification information and the authority certification information, so that any application server accesses a storage space corresponding to a second storage address to read the authority certification information, and determines that the authority certification information passes verification under the condition that the authority certification information is consistent with the standard certification information, wherein the second storage address is determined by any application server according to the standard certification information and the received merchant identification information contained in the sub-mapping relationship.
6. The method according to claim 2, wherein the merchant identification information includes a platform identifier of a service platform to which the graphic code management server belongs and a merchant identifier of the merchant, and the merchant identification information is used for querying, by an application server corresponding to the user client program of any type, merchant applets corresponding to the merchant identifier among applets issued by the service platform corresponding to the platform identifier.
7. The method of claim 2, further comprising:
and obtaining order placing information determined by the user client program of any type in response to order placing operation implemented by the user, and generating a target order according to the order placing information.
8. The method of claim 7,
the generating of the graphic code containing the merchant identification information includes: generating a graphic code according to the merchant identification information and store information of the merchant;
the generating of the target order according to the order placing information comprises: and receiving target store information obtained by analyzing a graphic code displayed by a target merchant in an entity store by the user client program of any type, and generating a target order corresponding to the entity store according to the order placing information and the target store information.
9. A small program starting method based on graphic codes is characterized in that the method is applied to any type of user client programs; the method comprises the following steps:
analyzing the graphic code displayed by the target merchant to obtain target merchant identification information, and sending the target merchant identification information to a graphic code management server;
acquiring target small program identification information, and starting a target merchant small program corresponding to the target small program identification information; the target applet identification information is determined according to a mapping relation and the target merchant identification information, and the mapping relation is established by the graphic code management server according to the obtained merchant identification information of the merchant and the applet identification information of various merchant applets corresponding to the merchant.
10. The method of claim 9, further comprising:
analyzing a graphic code displayed in an entity store by a target merchant to obtain target store information; and the number of the first and second groups,
and determining ordering information in response to an ordering operation implemented by a user, wherein the target store information and the ordering information are used by the graphic code management server to generate a target order corresponding to the physical store.
11. A small program starting method based on graphic codes is characterized by being applied to a merchant client; the method comprises the following steps:
initiating a graphic code acquisition request to a graphic code management server, wherein the graphic code management server is used for determining target small program identification information corresponding to target business identification information obtained by analyzing any type of user client program according to a mapping relation generated by the acquired business identification information and small program identification information of various business small programs corresponding to the business, so that the target business small program corresponding to the target small program identification information is started by the user client program of any type;
and acquiring the graphic code which is generated by the graphic code management server in response to the graphic code acquisition request and contains the merchant identification information, wherein the graphic code is used for being displayed by the merchant.
12. A small program starting device based on graphic codes is characterized by being applied to a graphic code management server; the device comprises:
the information acquisition unit is used for acquiring merchant identification information of merchants and applet identification information of various merchant applets corresponding to the merchants;
the graphic code generating unit is used for generating a graphic code containing the merchant identification information, and establishing a mapping relation between the merchant identification information and the applet identification information of various merchant applets, wherein the mapping relation is used for determining target applet identification information corresponding to target merchant identification information obtained by analyzing of any type of user client program, so that the merchant applet corresponding to the target applet identification information is started by any type of user client program, and the target merchant identification information is obtained by analyzing the graphic code displayed by the target merchant by any type of user client program.
13. The small program starting device based on the graphic code is characterized by being applied to any type of user client programs; the device comprises:
the information sending unit is used for analyzing the graphic code displayed by the target merchant to obtain the identification information of the target merchant and sending the identification information of the target merchant to the graphic code management server;
the small program starting unit is used for acquiring target small program identification information and starting a target merchant small program corresponding to the target small program identification information; the target applet identification information is determined according to a mapping relation and the target merchant identification information, and the mapping relation is established by the graphic code management server according to the obtained merchant identification information of the merchant and the applet identification information of various merchant applets corresponding to the merchant.
14. The small program starting device based on the graphic code is characterized by being applied to a merchant client; the device comprises:
the request initiating unit initiates a graphic code acquisition request to a graphic code management server, and the graphic code management server is used for determining target small program identification information corresponding to target business identification information obtained by analyzing any type of user client program according to a mapping relation generated by the acquired business identification information and small program identification information of various business small programs corresponding to the business, so that the target business small program corresponding to the target small program identification information is started by the user client program of any type;
and the graphic code acquisition unit is used for acquiring a graphic code which is generated by the graphic code management server side in response to the graphic code acquisition request and contains the merchant identification information, and the graphic code is used for being displayed by the merchant.
CN202110797302.6A 2021-07-14 2021-07-14 Small program starting method and device based on graphic code Pending CN113268287A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202110797302.6A CN113268287A (en) 2021-07-14 2021-07-14 Small program starting method and device based on graphic code

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202110797302.6A CN113268287A (en) 2021-07-14 2021-07-14 Small program starting method and device based on graphic code

Publications (1)

Publication Number Publication Date
CN113268287A true CN113268287A (en) 2021-08-17

Family

ID=77236692

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202110797302.6A Pending CN113268287A (en) 2021-07-14 2021-07-14 Small program starting method and device based on graphic code

Country Status (1)

Country Link
CN (1) CN113268287A (en)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN117708447A (en) * 2024-02-06 2024-03-15 杭州数云信息技术有限公司 Parameter transmission method and device based on graphic code, readable storage medium and terminal

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106302546A (en) * 2016-10-18 2017-01-04 青岛海信电器股份有限公司 The method and apparatus realizing server access
CN108052663A (en) * 2017-01-17 2018-05-18 海南亚元防伪技术研究所（普通合伙） A kind of application process and device of shared Quick Response Code
CN110569947A (en) * 2019-09-02 2019-12-13 紫光云技术有限公司 method for realizing multi-code integration of two-dimensional codes
CN111639279A (en) * 2020-05-27 2020-09-08 浙江口碑网络技术有限公司 Graphic code generation method, target page loading method and device
CN112732366A (en) * 2021-03-30 2021-04-30 浙江口碑网络技术有限公司 Small program starting system, method and device based on graphic code

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106302546A (en) * 2016-10-18 2017-01-04 青岛海信电器股份有限公司 The method and apparatus realizing server access
CN108052663A (en) * 2017-01-17 2018-05-18 海南亚元防伪技术研究所（普通合伙） A kind of application process and device of shared Quick Response Code
CN110569947A (en) * 2019-09-02 2019-12-13 紫光云技术有限公司 method for realizing multi-code integration of two-dimensional codes
CN111639279A (en) * 2020-05-27 2020-09-08 浙江口碑网络技术有限公司 Graphic code generation method, target page loading method and device
CN112732366A (en) * 2021-03-30 2021-04-30 浙江口碑网络技术有限公司 Small program starting system, method and device based on graphic code

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN117708447A (en) * 2024-02-06 2024-03-15 杭州数云信息技术有限公司 Parameter transmission method and device based on graphic code, readable storage medium and terminal
CN117708447B (en) * 2024-02-06 2024-05-14 杭州数云信息技术有限公司 Parameter transmission method and device based on graphic code, readable storage medium and terminal

Similar Documents

Publication Publication Date Title
US20220335537A1 (en) Electronic receipt system, commodity sales data processing apparatus, electronic receipt management server and method
EP2789150B1 (en) Method, client device and server of accessing network information through graphic code
JP5241839B2 (en) E-commerce method, system and apparatus suitable for conventional retail
US11397927B2 (en) Electronic receipt system, electronic receipt management server, and program therefor
EP2701099A1 (en) Computer network for dynamically controlling qr-codes
CN109636435A (en) Pass through method, apparatus, computer equipment and the medium of small routine linkage marketing
US11379814B2 (en) Method and system for supporting promotion of use of digital local currency
CN109325776A (en) Return of goods code generates and return of goods method, apparatus, equipment and its storage medium
CN112948521B (en) Object handling method and device
CN112948522B (en) Object handling method and device
US20140249909A1 (en) Electronic receipt system, information processing apparatus, and program therefor
CN110852779A (en) Method, device, equipment and system for experiential sale of commodities based on lattice spread
US20150073840A1 (en) Information processing device, program and electronic receipt system
CN104766231A (en) Real-time communication information transmission method for the same commodity
US20140249998A1 (en) Electronic receipt system, electronic receipt managing server, information processing device, and information processing method
CN113268287A (en) Small program starting method and device based on graphic code
KR101782387B1 (en) Method of involving a user in shopping of the user's friend by pushing an item directly into the friend's account page
JP2018147291A (en) Merchandise purchase system, site management server, and program
CN112732366B (en) Small program starting system, method and device based on graphic code
US20220351241A1 (en) Method, apparatus, and computer program product for facilitating the activation of promotions using short codes
JP7282228B1 (en) Payment system and awarding method
US20200320572A1 (en) System and method for collecting information by using digital recognition device
JP2020187589A (en) Information processing device, information processing method and program
US20180341449A1 (en) Display control method, order management method, display control device, and recording medium
US20190122290A1 (en) Container, settlement apparatus, and shop system

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination