Server and method for preventing repeated generation of permanent QR codes

Abstract

An embodiment of the present application provides a server and a method for preventing repeated generation of permanent QR codes. The server is configured to: receive a permanent access link acquisition request including a first fixed scenario code sent by an operation end; detect whether there is a permanent access link corresponding to the first fixed scenario code in a preset mapping relationship; if so, feedback the first permanent access link so that the operation end can generate a permanent QR code according to the first permanent access link; if not, request a third-party server to add a second permanent access link. After receiving the second permanent access link, write the mapping relationship between the second permanent access link and the first fixed scenario code in the preset mapping relationship, and feedback the second permanent access link to the operation end. By defining a fixed scenario code for a fixed service scenario in the present application, each service scenario can only match a single permanent QR code, avoiding the waste of resources caused by generating multiple permanent QR codes for the same service scenario.

Description

Technical Field

[0001] This application relates to the field of Internet technologies, and in particular, to a server and a method for preventing duplicate generation of permanent QR codes. Background Art

[0002] A public account is an application account applied by an operator on the public platform of a social application (such as WeChat), and is a mainstream online and offline social interaction marketing method. Through the public account, users can achieve all-round communication and interaction of text, pictures, voices, and videos with a specific group on the public platform of the social application. The public account contains many services, and many services can be promoted through corresponding QR codes. QR codes have played a huge role in the Internet era. Users can quickly enter the service page they need to use by scanning the QR code with a smart terminal.

[0003] According to different usage scenarios, QR codes can be roughly divided into temporary QR codes and permanent QR codes. For service scenarios that require real-time data, temporary QR codes are mostly needed, while for some fixed service scenarios, they can be promoted through permanent QR codes. For the operation end of the public account, it can directly request a permanent QR code from the service background corresponding to the social platform. The service background corresponding to the social platform feeds back the QR code information to the operation end of the public account according to the received request. However, the service background of the social application has a limit on the generation of permanent QR codes. Exemplarily, each public account can generate at most 100,000 permanent QR codes. Therefore, permanent QR codes are limited resources. For public accounts that want to operate for a long time, how to effectively utilize limited resources is an urgent problem to be solved. Summary of the Invention

[0004] This application provides a server and a method for preventing duplicate generation of permanent QR codes to solve the technical problem of resource waste caused by generating multiple permanent QR codes for the same service scenario in the prior art.

[0005] In a first aspect, this application provides a server, which is configured to:

[0006] Receive a permanent access link acquisition request sent by an operation end, which includes a first fixed scenario code. The first fixed scenario code is determined by the operation end according to the service scenario, and different fixed scenario codes correspond to different service scenarios;

[0007] Detect whether there is a permanent access link corresponding to the first fixed scenario code in the preset mapping relationship according to the first fixed scenario code and the preset mapping relationship. In the preset mapping relationship, the fixed scenario code and the permanent access link are in one-to-one correspondence;

[0008] When there is a first permanent access link corresponding to the first fixed scenario code, feedback the first permanent access link so that the operation end generates a permanent QR code according to the first permanent access link;

[0009] When there is no first permanent access link corresponding to the first fixed scenario code, request a third-party server to add a second permanent access link. After receiving the second permanent access link, write the mapping relationship between the second permanent access link and the first fixed scenario code in the preset mapping relationship, and feedback the second permanent access link to the operation end so that the operation end generates a permanent QR code according to the second permanent access link.

[0010] In some embodiments, in the step of requesting a third-party server to add a second permanent access link, the server is configured to:

[0011] Send a request to add a second permanent access link to the third-party server. The request to add a second permanent access link includes a login token and a first scenario identifier. The login token is used to enable the third-party server to identify the server's identity to generate the second permanent access link. The first scenario identifier is used by the third-party server to establish the mapping between the second permanent access link and the first scenario identifier, and send the first scenario identifier to the server after receiving the access of the mobile terminal to the second permanent access link;

[0012] Establish a mapping relationship between the first fixed scenario code and the first scenario identifier in the preset mapping relationship.

[0013] In some embodiments, after receiving the second permanent access link, the server is further configured to:

[0014] Receive a second scenario identifier sent by the third-party server;

[0015] Determine a second fixed scenario code corresponding to the second scenario identifier in the preset mapping relationship according to the second scenario identifier;

[0016] Feedback the page data corresponding to the second fixed scenario code to the third-party server so that the third-party server can send the page data to the mobile terminal.

[0017] In a second aspect, the present application provides a method for preventing the repeated generation of permanent QR codes. The method includes:

[0018] Receive a request for obtaining a permanent access link sent by the operation end and containing a first fixed scenario code. Here, the first fixed scenario code is determined by the operation end according to the service scenario, and different fixed scenario codes correspond to different service scenarios;

[0019] Detect whether there is a permanent access link corresponding to the first fixed scenario code in the preset mapping relationship according to the first fixed scenario code and the preset mapping relationship, wherein in the preset mapping relationship, the fixed scenario code and the permanent access link are in one-to-one correspondence;

[0020] When there is a first permanent access link corresponding to the first fixed scenario code, feedback the first permanent access link so that the operation end generates a permanent two-dimensional code according to the first permanent access link;

[0021] When there is no first permanent access link corresponding to the first fixed scenario code, request the third-party server to add a second permanent access link. After receiving the second permanent access link, write the mapping relationship between the second permanent access link and the first fixed scenario code in the preset mapping relationship, and feedback the second permanent access link to the operation end so that the operation end generates a permanent two-dimensional code according to the second permanent access link.

[0022] Compared with the prior art, the beneficial effects of the present application are:

[0023] The present application provides a server and a method for preventing the repeated generation of permanent two-dimensional codes. The operation personnel define corresponding fixed scenario codes for each service scenario and send a permanent access link acquisition request to the server with the fixed scenario code as a parameter. There is a preset mapping relationship stored in the server, in which the fixed scenario code and the permanent access link are in one-to-one correspondence. After receiving the permanent access link acquisition request, the server detects whether there is a first permanent access link corresponding to the first fixed scenario code. If it exists, directly feedback the first permanent access link to the operation end, and the operation end generates a permanent two-dimensional code according to the first permanent access link. If it does not exist, request the third-party server to add a second permanent access link. The server maps and stores the newly added second permanent access link and the first fixed scenario code, and feedbacks the second permanent access link to the operation end. By defining fixed scenario codes for fixed service scenarios, the present application enables each service scenario to only match a corresponding unique permanent two-dimensional code, avoiding the waste of resources caused by the generation of multiple permanent two-dimensional codes for the same service scenario. Description of the Drawings

[0024] In order to more clearly illustrate the technical solutions of the present application, the accompanying drawings required for the embodiments will be briefly introduced below. Obviously, for those of ordinary skill in the art, other accompanying drawings can be obtained based on these drawings without creative efforts.

[0025] Figure 1An exemplary display effect diagram of the home page of a public account according to some embodiments is shown;

[0026] Figure 2 An exemplary display effect diagram of the promotion service of a public account according to some embodiments is shown;

[0027] Figure 3 A flowchart of a method for preventing the repeated generation of permanent QR codes according to some embodiments is shown exemplarily;

[0028] Figure 4 A timing diagram of a method for preventing the repeated generation of permanent QR codes according to some embodiments is shown exemplarily. Detailed implementation manners

[0029] To make the purpose and implementation manners of this application clearer, the following will clearly and completely describe the exemplary implementation manners of this application with reference to the accompanying drawings in the exemplary embodiments of this application. Obviously, the described exemplary embodiments are only a part of the embodiments of this application, rather than all the embodiments.

[0030] It should be noted that the brief description of the terms in this application is only for the convenience of understanding the following described implementation manners, rather than intending to limit the implementation manners of this application. Unless otherwise specified, these terms should be understood in their ordinary and general meanings.

[0031] The terms "first", "second", "third", etc. in the specification, claims and above-mentioned drawings of this application are used to distinguish similar or the same kind of objects or entities, and do not necessarily mean to limit a specific order or sequence, unless otherwise noted. It should be understood that such terms can be interchanged under appropriate circumstances.

[0032] The terms "comprising" and "having" and any variations thereof are intended to cover but not exclude inclusion. For example, a product or device including a series of components does not necessarily have to be limited to all the clearly listed components, but may include other components that are not clearly listed or are inherent to these products or devices.

[0033] In a social application, taking WeChat as an example, an operator can register an application account by means of the public platform of the social application. For example, the operator registers a WeChat public account on the WeChat public platform. After the account is opened, the operator can post videos, pictures, texts, etc. in the WeChat public account to promote products or share life experiences, etc. [[ID=3{]] Figure 1 An exemplary display effect diagram of the home page of a public account according to some embodiments is shown, such as Figure 1As shown, the official account can include various service contents such as the first service to the sixth service, such as orders, logins, registrations, viewing historical records, etc. The scenario corresponding to each service can be called a service scenario. The operator can apply for a QR code for the service scenario in the official account so that when the user scans the QR code through the mobile terminal, the mobile terminal directly jumps to the page of the service corresponding to the service scenario. Figure 2 An exemplary display effect diagram of the promotion service of the official account according to some embodiments is shown in combination with Figure 2 , when the user scans the QR code through the mobile terminal, the user's mobile terminal can directly jump to the recommended page of the corresponding official account. A follow control can be set on the recommended page, and the user can follow the official account after clicking the follow control. For another example, a new service is launched in the official account. To promote this service, a QR code can be applied for it. When the user scans the QR code through the mobile terminal, the user's mobile terminal can directly jump to the page of the service corresponding to the service scenario. For example, "Welcome to log in to xxx service" can be displayed on this page.

[0034] For a third party to which the social application belongs, since the permanent QR code permanently occupies its own resources, the number of permanent QR codes is restricted. Exemplarily, for a WeChat official account, there is a limit on the number of generated permanent QR codes. That is to say, for the application account corresponding to each official account, WeChat only allows it to generate a limited number of permanent QR codes. Generally speaking, each official account is allowed to generate at most 100,000 permanent QR codes.

[0035] In the existing social applications, the generation of temporary QR codes is generally that the user sends a QR code generation request to the third-party server, and the third-party server returns a temporary link. After the operator receives the temporary link, a QR code is generated and used for display in the promotion page. In the existing technical solutions, the QR code is generally requested on demand. When a permanent QR code is needed, a permanent access link is requested. If it is not permanent, a temporary access link is requested.

[0036] The inventors found that 100,000 permanent connections can basically meet the general needs of operators, but permanent QR codes are limited resources. For operators who want to operate public accounts for a long time, they should effectively utilize the limited number of permanent QR codes. During use, the inventors found that in the existing permanent QR code generation process, as long as the operator sends a request, the third-party server will feedback a permanent connection, and does not distinguish whether it corresponds to the content requested by the user. Even if it corresponds to the content of the same service, repeated requests from the operator will still send a permanent link. The reason why third-party applications do this is to meet the user's requirements as much as possible while avoiding large-capacity calculations. However, the operation and maintenance end inevitably has operations involving multiple people or multiple time periods. Based on this, the present application provides a server in some embodiments, which is configured to execute a process to prevent the repeated generation of permanent QR codes.

[0037] The process of preventing the repeated generation of permanent QR codes is described below with reference to the accompanying drawings.

[0038] Figure 3 hereinafter is a flow chart illustrating a method for preventing repeated generation of permanent QR codes according to some embodiments.

[0039] Combine Figure 3 As shown, the process of preventing the repeated generation of permanent QR codes is as follows:

[0040] S301: Receive a permanent access link acquisition request including a first fixed scenario code sent by an operator, wherein the first fixed scenario code is determined by the operator according to a service scenario, and different fixed scenario codes correspond to different service scenarios.

[0041] In some embodiments, the operator of an official account can define a fixed scene code for each fixed service scenario. For example, for the user registration service, the corresponding fixed scene code may be ZC00001, for the first promotional service, the corresponding fixed scene code may be TG00001, and for the second promotional service, the corresponding fixed scene code may be TG00002. For another example, for a new official account micro-theater service application with a permanent QR code, the fixed scene code may be defined as mediaCenterWelcome. Here, the fixed scene code can be arbitrarily defined based on the semantics of the service scenario, with different fixed scene codes corresponding to different service scenarios.

[0042] In some embodiments, when the operator wants to apply for a permanent QR code for a service scenario in an official account, it first defines a first fixed scenario code for the service scenario and sends a permanent access link acquisition request carrying the first fixed scenario code corresponding to the service scenario to the server. The server receives the permanent access link acquisition request sent by the operator.

[0043] S302: Detect whether there is a permanent access link corresponding to the first fixed scenario code in the preset mapping relationship according to the first fixed scenario code and the preset mapping relationship, where in the preset mapping relationship, the fixed scenario code and the permanent access link correspond one by one.

[0044] In some embodiments, the operation end can pre-store the preset mapping relationship in the database through the server, and in the preset mapping relationship, the fixed scenario code and the permanent access link correspond one by one. For example, in the mysql database, the corresponding relationship between the service scenario, the fixed scenario code, and the permanent access link is stored in the form of a table, and the relationship among the three is one-to-one. See Table 1.

[0045] Table 1:

[0046] Service scenario Fixed scenario code Permanent access link Registration service ZC00001 Registration access link Promotion service TG00001 Promotion access link Query service CX00001 Query access link

[0047] In some embodiments, the server can also first store only the corresponding relationship between the service scenario and the fixed scenario code, and then, after each new corresponding permanent access link is obtained, insert the permanent access link into the database and bind it to the corresponding fixed scenario code.

[0048] In some embodiments, after the server receives the permanent access link acquisition request, it acquires the first fixed scenario code carried in the request, and uses the first fixed scenario code as a query condition to query the corresponding permanent access link from the preset mapping relationship in the database.

[0049] S303: When there is a first permanent access link corresponding to the first fixed scenario code, feedback the first permanent access link so that the operation end can generate a permanent QR code according to the first permanent access link.

[0050] In some embodiments, the server uses the first fixed scenario code to search in the preset mapping relationship in the database to check whether there is a matching first permanent access link for the first fixed scenario code. If there is a matching first permanent access link for the first fixed scenario code in the preset mapping relationship, the server feeds back the corresponding first permanent access link to the operation end. After the operation end obtains the permanent access link, it generates a corresponding permanent QR code according to the permanent access link and displays the permanent QR code on the service page of the corresponding service scenario in the official account, so that when the user scans the permanent QR code, the mobile terminal directly jumps to the corresponding service page. As shown in Table 1, by querying through TG00001, it is found that there is a corresponding permanent access link. The server feeds back the permanent access link corresponding to TG00001 to the operation end, and the operation end calls the QR code generation service to generate a corresponding permanent QR code and sets the permanent QR code on the corresponding promotion page in the official account.

[0051] S304: When there is no first permanent access link corresponding to the first fixed scenario code, request the third-party server to add a second permanent access link. After receiving the second permanent access link, write the mapping relationship between the second permanent access link and the first fixed scenario code in the preset mapping relationship, and feedback the second permanent access link to the operation end so that the operation end can generate a permanent QR code based on the second permanent access link.

[0052] In some embodiments, the server uses the first fixed scenario code to search in the preset mapping relationship in the database to check whether there is a matching first permanent access link for the first fixed scenario code. If there is no matching first permanent access link for the first fixed scenario code in the preset mapping relationship, the server needs to request to generate a permanent access link corresponding to the first fixed scenario code, that is, request the third-party server to add a second permanent access link.

[0053] In some embodiments, the operation end interacts with the local server, that is, sends a request for obtaining a permanent access link to the local server. When the local server queries that there is no first permanent access link corresponding to the first fixed scenario code, the local server sends a request to the third-party server to add a second permanent access link. The request to add a second permanent access link includes a login token and a first scenario identifier. The login token is used for the third-party server to identify the identity of the local server to generate the second permanent access link. The first scenario identifier can be a globally unique character code generated by the local server according to the service scenario through the uuid (Universally Unique Identifier) toolkit, and is used for the third-party server to establish the mapping between the second permanent access link and the first scenario identifier, and send the first scenario identifier to the server after receiving the access of the mobile terminal to the second permanent access link. For example, the globally unique 36-bit character code generated by the local server according to the registration service is f7***38c-1**0-1**c-8**5-0******3. The third-party server will bind the generated second permanent access link and this character code. When the user scans the QR code corresponding to the second permanent access link through the mobile terminal, the third-party server will return this character code to the local server.

[0054] In some embodiments, to establish the mapping relationship between the first fixed scenario code and the first scenario identifier in the preset mapping relationship, the scenario identifier corresponding to the fixed scenario code can be mapped to Table 1 to obtain the corresponding relationship between the service scenario, the fixed scenario code, the permanent access link, and the scenario identifier, as shown in Table 2:

[0055]

[0056] In some embodiments, the local server receives the second scenario identifier sent by the third-party server, and determines the second fixed scenario code corresponding to the second scenario identifier in the preset mapping relationship. The local server feeds back the page data corresponding to the second fixed scenario code to the third-party server, so that the third-party server can send the page data to the mobile terminal. For example, the local server uses 76***fc0-1**5-1**c-b**1- 7******4 as the query condition to query the corresponding fixed scenario code in Table 2 as mediaCenterWelcome. The local server feeds back the page data of the micro theater service corresponding to mediaCenterWelcome to the third-party server, so that the third-party server can feed back the page data of the micro theater service to the mobile terminal.

[0057] Based on the WeChat public platform, when the third-party server is the WeChat server and the local server queries that there is no corresponding fixed scenario code for the service scenario, it sends a request for adding a second permanent access link containing the login token (WeChat token) and the scenario identifier to the WeChat server. After receiving the request for adding a second permanent access link, the WeChat server clarifies the identity of the local server that sent the request through the login token, that is, it clarifies which public account needs to request a permanent access link. The WeChat server calls the access link generation service to create a new permanent access link and feeds back the created permanent access link to the local server. Moreover, the WeChat server will also associate this scenario identifier with the generated permanent access link, so that when the user scans the permanent QR code through WeChat, the WeChat server sends the scenario identifier and the WeChat user information to the local server, that is, the public account operation background. The public account operation background can perform different processing actions according to different scenario identifiers.

[0058] The user uses WeChat on the mobile terminal to scan the permanent QR code. The WeChat client analyzes the corresponding QR code information and pushes the scene identifier carried in the permanent QR code together with the current user information to the WeChat server. The WeChat server analyzes the information pushed by the WeChat client, queries the corresponding official account according to the scene identifier information, and sends the globally unique character code generated when the QR code was generated and the user information of the scanner to the callback address bound to the corresponding official account. The local server receives the call from the WeChat server to the callback address, analyzes the data, and queries the service data required by the QR code in the database according to the globally unique character code. The local server executes the service action and pushes the service execution result to the scanner user through the official account. For example, after receiving f7***38c-1**0-1**c-8**5-0******3 sent by the WeChat server and the WeChat user information, the local server can know that the WeChat user wants to register an account for this official account, and the local server can respond to the user's registration operation.

[0059] In some embodiments, the local server stores the newly obtained second permanent access link. The server binds the corresponding fixed scene code, permanent access link, and scene identifier, and assembles them into an insert statement. The server sends a data insertion request containing the insert statement to the database, so that the database inserts the corresponding fixed scene code, permanent access link, and scene identifier into the mapping relationship.

[0060] Figure 4 The timing diagram of the method for preventing duplicate generation of permanent QR codes according to some embodiments is exemplarily shown below. In combination with Figure 4Further describe the process of preventing the repeated generation of permanent QR codes in this application. The operator carries a specific fixed scenario code and sends a request for obtaining a permanent access link to the local server to request the permanent access link corresponding to the fixed scenario code. After receiving the request for obtaining the permanent access link, the local server uses the fixed scenario code as the query condition to query from the database whether there is a permanent access link corresponding to the fixed scenario code. The database returns the query result to the local server, and the local server determines whether the query result indicates that the corresponding permanent access link has been found. If the corresponding permanent access link is found, the permanent access link is fed back to the operation end. After receiving the permanent access link, the operation end calls the QR code generation service to generate the corresponding permanent QR code and configures the permanent QR code to the recommended position required by the service scenario in the official account. If the corresponding permanent access link is not found, the local server sends a request for adding a permanent access link to the third-party server with the parameters (scenario identifier, login token) required for generating the access link. After receiving the request for adding a permanent access link, the third-party server calls the access link generation service to generate a permanent access link and feeds back the generated permanent access link to the local server. The local server feeds back the newly generated permanent access link to the operation end. The operation end calls the QR code generation service to generate the corresponding permanent QR code and configures the permanent QR code to the recommended position required by the service scenario in the official account. In addition, the local server assembles a database insertion statement using the fixed scenario code, the newly generated permanent access link, and the scenario identifier, and sends a data insertion request to the database with the insertion statement. The database executes the insertion statement, stores the corresponding fixed scenario code, permanent access link, and scenario identifier in the preset mapping relationship, and feeds back the result of successful storage to the local server.

[0061] In this application, by defining a fixed scenario code for a fixed service scenario, each service scenario can only match a unique permanent QR code. Through the one-to-one correspondence relationship among the service scenario, fixed scenario number, and permanent QR code, the phenomenon of resource waste caused by generating multiple permanent QR codes for the same service scenario is avoided.

[0062] Corresponding to the above method, some embodiments of the present application further provide a method for preventing the repeated generation of permanent QR codes. The method includes: The server receives a permanent access link acquisition request sent by the operation terminal, which includes a first fixed scenario code. The first fixed scenario code is determined by the operation terminal according to the service scenario, and different fixed scenario codes correspond to different service scenarios. According to the first fixed scenario code and the preset mapping relationship, the server detects whether there is a permanent access link corresponding to the first fixed scenario code in the preset mapping relationship, where in the preset mapping relationship, the fixed scenario code and the permanent access link are in one-to-one correspondence. When there is a first permanent access link corresponding to the first fixed scenario code, the server feeds back the first permanent access link to the operation terminal so that the operation terminal generates a permanent QR code according to the first permanent access link. When there is no first permanent access link corresponding to the first fixed scenario code, the server requests the third-party server to add a second permanent access link. After receiving the second permanent access link, the mapping relationship between the second permanent access link and the first fixed scenario code is written in the preset mapping relationship, and the second permanent access link is fed back to the operation terminal so that the operation terminal generates a permanent QR code according to the second permanent access link.

[0063] In some embodiments, the server uses the first fixed scenario code as a query condition to query the corresponding permanent access link from the preset mapping relationship.

[0064] In some embodiments, the server is a local server. The request to the third-party server to add a second permanent access link includes: The local server sends a request to add a second permanent access link to the third-party server. The request to add a second permanent access link includes a login token and a first scenario identifier. The login token is used to enable the third-party server to identify the local server to generate the second permanent access link. The first scenario identifier is used by the third-party server to establish the mapping between the second permanent access link and the first scenario identifier, and send the first scenario identifier to the server after receiving the access of the mobile terminal to the second permanent access link. Establish the mapping relationship between the first fixed scenario code and the first scenario identifier in the preset mapping relationship.

[0065] In some embodiments, after receiving the second permanent access link, the method further includes: The server receives the second scenario identifier sent by the third-party server. Determine the second fixed scenario code corresponding to the second scenario identifier in the preset mapping relationship according to the second scenario identifier. The server feeds back the page data corresponding to the second fixed scenario code to the third-party server so that the third-party server can send the page data to the mobile terminal.

[0066] In some embodiments, storing the permanent access link includes: the server binds the corresponding fixed scenario code, permanent access link, and scenario identifier, assembles them into an insert statement, and sends a data insertion request containing the insert statement to the database, so that the database inserts the corresponding fixed scenario code, permanent access link, and scenario identifier into a preset mapping relationship.

[0067] This application also provides an operation terminal. Instead of directly requesting a permanent access link from a third-party server, the operation terminal requests a permanent access link from the third-party server through the server.

[0068] In some embodiments, the operation terminal is further configured to determine the scenario code corresponding to the current content before requesting to obtain the permanent access link, and then send a request containing the scenario code to the server.

[0069] In some embodiments, the operation terminal prestores the correspondence between scenario codes and scenarios (topics). The editing of content is topic-distinguished, and different topics correspond to different scenario codes.

[0070] In some embodiments, the topic may include a parent topic and a subtopic. The editing of the scenario and the sending of requests need to be performed in the subtopic.

[0071] In some embodiments, before sending a request, obtain the current subtopic and determine whether there is a corresponding scenario code for the current subtopic. If there is, send a request containing the scenario code to the server. If not, generate a new scenario code and send an identification request containing the new scenario code to the server, and the user maps the new scenario code and the subtopic.

[0072] In some embodiments, upon receiving the permanent link feedback from the server, generate a permanent QR code based on the received permanent link.

[0073] In some embodiments, the operation terminal and the server can be different modules in the same physical server / cloud server, or can be different physical servers / cloud servers.

[0074] Since the above embodiments are all described by reference and combination on other methods, and there are identical parts among different embodiments, the same or similar parts among the various embodiments in this specification can be referred to each other. Details are not elaborated here again.

[0075] It should be noted that in this specification, relational terms such as "first" and "second" are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any actual relationship or order between these entities or operations. Moreover, the term "comprising", "including" or any other variant thereof is intended to cover non-exclusive inclusion, such that a circuit structure, article or device comprising a series of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such circuit structure, article or device. Without further limitation, an element defined by the statement "comprising an..." does not exclude the presence of additional identical elements in the circuit structure, article or device comprising the element.

[0076] Those skilled in the art will readily conceive of other embodiments of the present application after considering the specification and practicing the disclosure of the present invention herein. The present application is intended to cover any variations, uses or adaptations of the present invention, which follow the general principles of the present application and include known common knowledge or conventional technical means in the technical field not disclosed in the present application. The specification and examples are only to be regarded as exemplary, and the true scope and spirit of the present application are pointed out by the content of the claims.

[0077] The above embodiments of the present application do not constitute a limitation on the scope of protection of the present application.

Claims

1. A server, characterized in that: The server is configured to: receiving a permanent access link acquisition request including a first fixed scenario code sent by an operator, wherein the first fixed scenario code is determined by the operator according to a service scenario, and different fixed scenario codes correspond to different service scenarios; detecting, according to the first fixed scene code and a preset mapping relationship, whether a permanent access link corresponding to the first fixed scene code exists in the preset mapping relationship, wherein fixed scene codes and permanent access links have a one-to-one correspondence in the preset mapping relationship; When there is a first permanent access link corresponding to the first fixed scenario code, feeding back the first permanent access link so that the operation end generates a permanent QR code according to the first permanent access link; When there is no first permanent access link corresponding to the first fixed scene code, a request is made to a third-party server to add a second permanent access link. After receiving the second permanent access link, the mapping relationship between the second permanent access link and the first fixed scene code is written into the preset mapping relationship, and the second permanent access link is fed back to the operation end so that the operation end generates a permanent QR code based on the second permanent access link.

2. The server according to claim 1, wherein: In the step of detecting, according to the first fixed scene code and the preset mapping relationship, whether there is a permanent access link corresponding to the first fixed scene code in the preset mapping relationship, the server is configured to: The first fixed scene code is used as a query condition to query the corresponding permanent access link from the preset mapping relationship.

3. The server according to claim 1, wherein: In the step of requesting the third-party server to add a new second permanent access link, the server is configured to: Sending a request for adding a second permanent access link to the third-party server, where the request for adding a second permanent access link includes a login token and a first scenario identifier, where the login token is used to enable the third-party server to clarify the identity of the server to generate the second permanent access link, and the first scenario identifier is used by the third-party server to establish a mapping between the second permanent access link and the first scenario identifier, and sending the first scenario identifier to the server after receiving an access to the second permanent access link by the mobile terminal; A mapping relationship between the first fixed scene code and the first scene identifier is established in the preset mapping relationship.

4. The server according to claim 3, wherein: After receiving the second permanent access link, the server is further configured to: receiving a second scenario identifier sent by the third-party server; Determining, according to the second scene identifier, a second fixed scene code corresponding to the second scene identifier in the preset mapping relationship; Feedback the page data corresponding to the second fixed scene code to the third-party server, so that the third-party server sends the page data to the mobile terminal.

5. The server according to claim 3, wherein: The server is configured to: Bind the corresponding fixed scene code, permanent access link, and scene identifier, and assemble them into the insert statement; A data insert request including the insert statement is sent to the database, so that the database inserts the corresponding fixed scene code, permanent access link, and scene identifier into the preset mapping relationship.

6. A method for preventing repeated generation of permanent QR codes, characterized in that: The method comprises: receiving a permanent access link acquisition request including a first fixed scenario code sent by an operator, wherein the first fixed scenario code is determined by the operator according to a service scenario, and different fixed scenario codes correspond to different service scenarios; detecting, according to the first fixed scene code and a preset mapping relationship, whether a permanent access link corresponding to the first fixed scene code exists in the preset mapping relationship, wherein fixed scene codes and permanent access links have a one-to-one correspondence in the preset mapping relationship; When there is a first permanent access link corresponding to the first fixed scenario code, feeding back the first permanent access link so that the operation end generates a permanent QR code according to the first permanent access link; When there is no first permanent access link corresponding to the first fixed scene code, a request is made to a third-party server to add a second permanent access link. After receiving the second permanent access link, the mapping relationship between the second permanent access link and the first fixed scene code is written into the preset mapping relationship, and the second permanent access link is fed back to the operation end so that the operation end generates a permanent QR code based on the second permanent access link.

7. The method for preventing repeated generation of permanent two-dimensional codes according to claim 6, characterized in that: The detecting, according to the first fixed scene code and the preset mapping relationship, whether there is a permanent access link corresponding to the first fixed scene code in the preset mapping relationship includes: The first fixed scene code is used as a query condition to query the corresponding permanent access link from the preset mapping relationship.

8. The method for preventing repeated generation of permanent two-dimensional codes according to claim 6, characterized in that: The requesting the third-party server to add a second permanent access link includes: Sending a request for adding a second permanent access link to the third-party server, where the request for adding a second permanent access link includes a login token and a first scenario identifier, where the login token is used to enable the third-party server to clarify the identity of the server to generate the second permanent access link, and the first scenario identifier is used by the third-party server to establish a mapping between the second permanent access link and the first scenario identifier, and sending the first scenario identifier to the server after receiving an access to the second permanent access link by the mobile terminal; A mapping relationship between the first fixed scene code and the first scene identifier is established in the preset mapping relationship.

9. The method for preventing repeated generation of permanent two-dimensional codes according to claim 8, characterized in that: After receiving the second permanent access link, the method further includes: receiving a second scenario identifier sent by the third-party server; Determining, according to the second scene identifier, a second fixed scene code corresponding to the second scene identifier in the preset mapping relationship; Feedback the page data corresponding to the second fixed scene code to the third-party server, so that the third-party server sends the page data to the mobile terminal.

10. The method for preventing repeated generation of permanent two-dimensional codes according to claim 8, characterized in that: The method further comprises: Bind the corresponding fixed scene code, permanent access link, and scene identifier, and assemble them into the insert statement; A data insert request including the insert statement is sent to the database, so that the database inserts the corresponding fixed scene code, permanent access link, and scene identifier into the preset mapping relationship.

Images