Service processing, two-dimensional code information processing method and computer equipment

Abstract

Embodiments of the present disclosure provide a service processing method, device and system associated with a two-dimensional code based on a uniform resource locator (URL). In one embodiment, a URL is received from a first service agency. The URL is obtained by a mobile device by scanning a two-dimensional code provided by a service provider and sent to the first service agency. The URL is then parsed to identify one or more data elements including a service network identifier, a service agency identifier and a payload including a service object identifier. The one or more data elements are sent to a second service agency based on the service agency identifier. Service information associated with a service object is received from the second service agency based on the service object identifier, and the service information is sent to the first service agency for presentation on a mobile device.

Description

Technical Field

[0001] The present application relates to the field of mobile transaction processing. Background Art

[0002] Machine-readable codes (hereinafter referred to as "codes") are used to encode information in a specific visual format that can be read by an electronic device to extract the encoded information. Such codes can be physically printed on a surface (such as a product package) or displayed on the screen of an electronic device (such as a mobile phone). Example codes include barcodes and Quick Response (QR) codes.

[0003] In the early days, these codes were one-dimensional (1D), where information was encoded in only one spatial dimension. For example, a standard barcode is a 1D code because the encoded symbols (bars) are modulated only on the horizontal axis of the code. This means that the code is read on this horizontal axis to get the encoded information, and no information is encoded by modulation of the symbols on the vertical axis.

[0004] Two-dimensional (2D) codes, which modulate symbols on both the vertical and horizontal axes, were first used in the manufacturing and transportation fields. The QR code is an example of a 2D code. Summary of the invention

[0005] The embodiments of this specification provide a service processing method, a two-dimensional code information processing method and a computer device.

[0006] In a first aspect, a service processing method is provided, the method comprising:

[0007] Scan the QR code provided by the service provider, which is embedded with a uniform resource locator URL;

[0008] Requesting the service information of the service provider from the first service agency based on the URL, so that the first service agency obtains the service information of the service provider pre-bound to the URL;

[0009] The service information of the service provider returned by the first service organization is received and presented.

[0010] In a second aspect, a service processing method is provided, the method comprising:

[0011] Receiving a request initiated by a user client based on a uniform resource locator URL after scanning a QR code, wherein the QR code has the URL embedded therein; the QR code has the uniform resource locator URL embedded therein; and the QR code does not have service information to be presented of the service provider embedded therein;

[0012] Obtaining service information of a service provider pre-bound to the URL; wherein, if it is determined by parsing the URL that the QR code is issued by the local side, obtaining service information maintained by the local side; if it is determined by parsing the URL that the QR code is not issued by the local side, sending one or more data elements obtained by parsing the URL to a digital service network, so as to obtain service information returned by the digital service network based on the data elements of the URL;

[0013] The service information is returned to the user client so that the user client presents the service information.

[0014] In a third aspect, a service processing method is provided, the method comprising:

[0015] Receiving one or more data elements in a URL sent by a first service agency; the URL is sent to the first service agency after a user client scans a QR code, and the first service agency sends the one or more data elements in the URL after parsing the URL to determine that the QR code is not issued by the first service agency; the QR code is embedded with a uniform resource locator URL; the QR code is not embedded with service information to be presented by the service provider;

[0016] Acquire service information of a service provider pre-bound to the URL based on one or more data elements in the URL;

[0017] The service information is returned to the first service agency, so that the first service agency provides the service information to the user client.

[0018] In a fourth aspect, a two-dimensional code information processing method is provided, the method comprising:

[0019] Generate an idle QR code and provide it to a service provider, wherein the URL embedded in the idle QR code is not bound to service information;

[0020] Receiving service information submitted by the service provider after scanning the QR code;

[0021] The URL is bound to the service information, so that after the two-dimensional code is scanned by the user client, the user client requests the service information of the service provider through the URL embedded in the two-dimensional code.

[0022] In a fifth aspect, a two-dimensional code information processing method is provided, the method comprising:

[0023] Scanning an idle QR code of a service provider, wherein a uniform resource locator URL embedded in the idle QR code is not bound to service information;

[0024] The service information input by the service provider is obtained and submitted to the service agency so that the service agency binds the URL with the service information, so that after the QR code is scanned by the user client, the user client requests the service information of the service provider through the URL embedded in the QR code.

[0025] In a sixth aspect, a computer device is provided, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements a method embodiment of any of the preceding aspects when executing the program.

[0026] The subject matter described in this specification can be implemented in specific embodiments to achieve one or more of the following advantages. First, by issuing a temporary trusted login token, the first server can use service authorization to provide limited access to the service page of the target application from the originating application without performing additional login steps. Second, the limited access allowed by the service authorization can protect the use of trusted login to access unauthorized service pages, which improves data security. Third, by returning the service page to the original application after the trusted login, there is no need to redirect the trusted user to the target application to perform the service, thereby improving the user experience.

[0027] The details of one or more embodiments of the subject matter of this specification are described in the detailed description, claims and drawings. For those of ordinary skill in the art, other features, aspects and advantages of the subject matter will become apparent from the detailed description, claims and drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0028] Figure 1 Detailed description is a schematic diagram showing an example of a service processing workflow of a digital service system according to an embodiment of the present disclosure.

[0029] Figure 2 is a diagram showing an example of a URL-based QR code generated based on STM according to an embodiment of the present disclosure.

[0030] Figure 3 is a schematic diagram showing an example of a “paste once” concept based on STM according to an embodiment of the present disclosure.

[0031] Figure 4 is a schematic diagram showing an example of interoperability of a service with a URL-based QR code according to an embodiment of the present disclosure.

[0032] Figure 5 is a swim lane diagram illustrating an example of a QR code binding process according to an embodiment of the present disclosure.

[0033] Figure 6The flowchart shows an example of a method for providing a URL-based two-dimensional code processing service according to an embodiment of the present disclosure.

[0034] Like reference numbers and designations in the various drawings represent like elements. DETAILED DESCRIPTION

[0035] With the development of mobile Internet, QR codes are increasingly used in various service scenarios due to the fast and accurate scanning and decoding capabilities of smartphones. With the emergence of more and more online-to-offline (O2O) platforms, users are able to scan QR codes to access various services such as online ordering, payment, and product tracking. The widespread use of QR codes has in turn greatly promoted the integration process of O2O. In many cases, the QR codes deployed by service providers are not just information carriers, but interactive media for service initiation, processing, and information exchange.

[0036] QR codes presented by merchants are commonly used for mobile payments. Commonly used QR codes presented by merchants may include merchant codes, order codes, interoperability codes, or aggregation codes. In order to unify users' mobile payment experience, reduce the cost of QR code deployment, and standardize the mobile payment market, regulators in some countries (or regions) have established their own regional unified QR code standards to manage the formats of these QR codes. However, different merchants may use different payment institutions or service platforms to collect payments or provide back-end services. Accordingly, the QR codes presented by merchants may be associated with or issued by different service institutions. As a result, the management of QR code service processing may be complex and may lack consistency.

[0037] The present disclosure describes a method for managing services associated with a QR code based on a uniform resource locator (URL), and the disclosure is introduced to enable any technician in the field to make and use the disclosed subject matter in the context of one or more specific embodiments. Various modifications, changes and substitutions may be made to the disclosed embodiments, and such modifications, changes and substitutions are obvious to those of ordinary skill in the art, and the general principles defined may be applied to other embodiments and applications without departing from the scope of the present disclosure. In some cases, one or more technical details that are not necessary for understanding the described subject matter and are within the skill range of those of ordinary skill in the art may be omitted so as not to blur the focus of the described one or more embodiments. The present disclosure is not intended to be limited to the described or illustrated embodiments, but rather to the widest scope consistent with the described principles and features.

[0038] A user can use a mobile device to scan a QR code to obtain corresponding service information for starting a service. Instead of embedding service information in a QR code, a QR code can be generated based on a Slim terminal model (STM) carrying a URL. The URL can be used to identify a data interface associated with the service information. By scanning the QR code, the mobile device can obtain the embedded URL and forward it to a backend service system. The digital service network in the backend service system can perform the role of a central hub for managing and facilitating services across different service agencies or platforms. The digital service network can identify a service agency that manages or maintains service information based on data elements included in the URL. The backend service system can then obtain the service information and return it to the mobile device to start the service. Since the QR code does not carry service information, it can be scanned and parsed faster. When the service information needs to be updated, the update can be performed by the service agency at the backend instead of updating the QR code itself at the front end. Regardless of how many service agencies are involved, the digital service network can effectively coordinate service processing. In this way, service processing based on a QR code can be performed more efficiently and securely. Various embodiments and technical effects according to the present disclosure are discussed in the following description.

[0039] Figure 1 1 is a schematic diagram showing an example of a service processing workflow of a digital service system 100 according to one embodiment of the present disclosure. At a high level, the digital service system 100 may include a user side 102 and an acquisition side 104. The user side 102 may include a front-end application (APP) 106 installed on a mobile device and a back-end user-side service agency 110. The acquisition side 104 may include a service provider, such as a merchant 108 and an acquisition-side service agency 114. In some embodiments, the service agency of the user side 102 and the service agency of the acquisition side 104 may be interconnected through a digital service network 112 or a central transmission platform (CTP). It is to be understood that the digital service network 112 may serve multiple service agencies on the user side and multiple service agencies on the merchant side. The services facilitated by the service agency 110, the service agency 114, and the digital service network 112 may be any suitable services, such as payment services, Internet of Things (IOT) information, location-based services (LBS), content services, or APP installation services. For example, if the service is a payment service, the APP 106 may be a digital payment APP, the user-side service agency 110 and the acquisition-side service agency 114 may be a user-side payment agency and a service-side agency, and the digital service network 112 may be a digital payment network. The service processing workflow of the digital service system 100 may be described by the following example.

[0040] In step 116, the URL-based QR code presented by the merchant is scanned by using the mobile APP 106 installed on the mobile device. The URL-based QR code can be in the form of any QR code, such as a QR code. Depending on the specific application scenario, the URL-based QR code can be deployed as a merchant code, an order code, an interoperability code, a regional unified code, or other types of codes. These codes are explained in more detail below.

[0041] A URL-based QR code can be generated based on STM. STM refers to a user-merchant interaction scenario in which a small amount of information is exchanged during the interaction. When using STM, the collection of service information is not limited to the data interaction period from the scanning of the QR code presented by the merchant, because the amount of information encoded into the QR code is relatively small. This contrasts with the Rich Terminal Model (RTM) in which most of the service information used to process the service is encoded into the QR code. Because a small portion of service information is obtained by scanning the STM QR code, most service information acquisition can be performed by the back-end server. In this way, the main party involved in executing the service is the user associated with the service APP 106 that scans the QR code, regardless of how many service platforms or institutions are associated with the user's account. Because a relatively small amount of information is encoded in the QR code, the collection of most of the service information can be entrusted to the back-end server, so that the data interaction between the APP 106 and the QR code can be faster, and because less information is exposed on the front end, the data security is stronger. In addition, since most of the service information can be managed and maintained at the back end, when the service information needs to be updated, the merchant 108 does not have to request and redeploy a new QR code in the STM scenario. In some cases, such updates can be made on the back end to reduce the deployment and material costs of redeploying new QR codes.

[0042] In some embodiments, the QR code generated based on STM may have the information format of a URL. Table 1 shows exemplary data elements of a URL encoded in a QR code. It should be understood that a URL according to the present disclosure may include only a portion of the data elements listed below or may also include additional data elements.

[0043]

[0044] Table 1

[0045] As shown in Table 1, the data elements of the URL include "protocol header", "domain name", "network ID", "version ID", "service type ID", "service organization ID", "payload", and one or more parameters. These data elements can be expressed in text form or in digital form. "Protocol header" can indicate the protocol used for data communication. For example, if Hypertext Transfer Protocol Secure (HTTPS) is the data communication protocol associated with the URL, "protocol header" can be "https". In some embodiments, the domain name can be applied for and managed by the operator of the digital service network 112. For example, the domain name can be expressed in text form as "qr.demodigitalnetwork.com". The network ID can identify the digital service network used to manage or promote services. The network ID can have different lengths. For example, the network ID in text form can be expressed as "demodigitalnetwork", and the network ID expressed in digital form can take an integer value between 25 and 30. The version ID can have different lengths. The version ID can be defined by the digital service network 112 to identify the version number of the digital service network 112. For example, the version ID may be represented in text form as “v2” to identify the second version of the digital service network 112 .

[0046] The service type ID may identify the applicable service associated with the URL-based QR code. Table 2 illustrates exemplary services and their corresponding URL expressions in text and numeric form.

[0047]

[0048] Table 2

[0049] The service institution ID may identify a service institution 114 of the acquisition side 104 that acquires services for the merchant 108. For example, if the service is a payment service, the service institution ID may identify a payment institution that is used to collect payments for the merchant 108. In some embodiments, a URL-based QR code may be issued by the service institution 114 identified by the service institution ID. For example, the service institution ID in text form may be represented as "demopaymentinstitution", and the network ID represented in digital form may take an integer value between 001 and 999. In some embodiments, the service institution ID may be set to "default" or a null value (e.g., "000") to indicate a default service institution or no service institution is specified.

[0050] The payload may include an identifier of a service object that identifies the digital service network 112. The service object may be an interface for linking service information managed and maintained by the acquisition-side service organization 114. In some embodiments, the service information may include merchant information, such as merchant name, merchant type, merchant nationality code or zip code, merchant address, one or more supported languages, and one or more supported currencies. In some embodiments, the service information may also include order information or transaction information, such as order amount, supported currencies, order ID, order or transaction instructions. It is understood that the service information may include other information related to performing the service.

[0051] The parameter may identify one or more additional services provided by the backend server of the acquisition side service mechanism 114. The parameter may be in the format of a key-value pair. The additional services may include, but are not limited to, additional order information, sales information, or other information, such as one or more credit values, digital voucher information, coupon information, lucky drawing information, global positioning system (GPS) location, table number, seat number, etc.

[0052] Thus, an example URL in a text format encoded in a QR code according to the present disclosure may be represented as:

[0053] https: / / qr.demodigitalnetwork.com / demodigitalnetwork / v2 / merchant_qr_payment / demopaymentinstitution / 012345678901234

[0054] An example URL in a digital format encoded in a QR code according to the present disclosure may be represented as:

[0055] https: / / qr.demodigitalnetwork.com / 28 / 2 / 05 / 001 / 012345678901234

[0056] The corresponding visual depiction of an exemplary URL-based QR code is in Figure 2 Shown in. Figure 2 is a diagram showing an example of a URL-based QR code 200 generated based on STM according to one embodiment of the present disclosure. A visual depiction of a text URL-based QR code 210 is shown in Figure 2 The visual depiction of the QR code 220 based on the digital URL is shown on the left side. Figure 2 is shown on the right side.

[0057] In step 118, service information is requested by sending a URL decoded from a scanned URL-based QR code. Using a payment service as an example, a user can make a mobile payment to a merchant by scanning a URL-based QR code presented by the merchant. The user can open a digital payment APP 106 installed on a mobile device, such as ALIPAY, log in to a service or payment account associated with the APP 106, and scan the code through the camera of the mobile device using the scanning function of the APP. In some embodiments, the mobile device can decode the QR code into a string in URL format, which includes one or more data elements as discussed in the description of step 116. The mobile device can then send the decoded URL as a string to the user-side service agency 110. In some embodiments, the user-side service agency can be a payment agency that provides services or payment accounts to APP 106 users.

[0058] At step 120, the URL is parsed by the user-side service agency 110, and at least a portion of the URL is sent to the digital service network 112. The URL may include data elements such as a service network ID, a service agency ID, a version ID, a payload, and a service type ID. The purpose of parsing the URL includes determining whether the URL-based code is issued by the user-side service agency 110. For example, this can be accomplished by parsing the URL to identify the service agency ID data element. If the service agency ID matches the ID of the user-side service agency 110, the user-side service agency 110 can determine that it maintains the corresponding service information and returns the service information to the mobile device. Otherwise, the user-side service agency 110 can send at least a portion of the URL as a data string to the digital service network 112 based on the service network ID parsed from the URL to identify the service agency associated with the service agency ID included in the URL. In some cases, the portion of the URL includes at least the service agency ID and the service type ID. In some embodiments, the user-side service agency 110 can identify the service agency associated with the service agency ID. In this case, the user-side service agency can directly request service information from the corresponding service agency by sending at least the service type ID and the payload to the service agency.

[0059] At step 122, a portion of the URL is parsed by the digital service network 112, and the service type ID and payload included in the portion of the URL are sent to the acquisition-side service 114. The digital service network 112 parses the received URL to determine the service agency ID, service type ID, and payload. The digital service network 112 may maintain a list of service agency IDs corresponding to one or more service agencies. The digital service network 112 may send the service type ID and payload of the received URL to the acquisition-side service 114 that matches the service agency ID.

[0060] In step 124, the acquisition side service agency 114 returns the requested service information to the digital service network 112 based on the service type ID and the payload. The acquisition side service agency 114 can determine the code type of the URL-based QR code based on the service type ID. The code type can determine the service information to be returned to the mobile device based on the service type ID. For example, if the code type is a fund transfer, the service information to be returned can be order information including the name of the other party to whom the funds will be transferred, the transaction ID, the supported currency, etc. If the code type is an order code, the service information to be returned to the mobile device may include the name of the merchant to whom the payment is to be made and the payment amount, so that the user can confirm the order using the mobile device. If the code type is a merchant code, the service information to be returned to the mobile device may include the merchant name, so if the merchant name is correct, the user can verify and enter the payment amount.

[0061] The payload may include an identification of a service object of the digital service network 112. The service object may be an interface that links to different service information managed and maintained by the acquisition-side service organization 114. If the URL data element sent to the acquisition-side service organization 114 also includes one or more parameters, information of one or more additional services provided by the backend server of the acquisition-side service organization 114 may be returned. The additional services may include additional order information, merchant information, sales information, or other information, such as one or more reputation values, digital voucher information, coupon information, lucky drawing information, GPS location, table number, seat number, or other information.

[0062] As can be seen from the above description, the URL decoded from the QR code generated under STM provides an identifier for locating and returning service information. The QR code itself does not carry service information. Therefore, compared with the RTM QR code that carries service information, the STM QR code is separated from the service information. The advantages of separating the QR code from the service information can be found in Figure 3 The description is as follows.

[0063] Figure 3 is a schematic diagram illustrating an example 300 of a "paste once" concept based on STM according to an embodiment of the present disclosure. After issuing a QR code to a service provider such as a merchant, the service provider only needs to paste the QR code once 320. In the event that the service information associated with the QR code changes, the QR code does not need to be replaced. The change of service information can be made by the background or backend 330 (e.g., the acquisition side service agency 114 or the digital service network 112) and linked to the service object identified by the identifier included in the payload, such as in Figure 1As discussed in the description of . After the mobile device 310 scans the QR code, the URL decoded from the QR code can be used to retrieve the updated service information. In this example 300, the QR code is a merchant code for collecting payments, and the merchant has changed its merchant information, such as the merchant name and supported payment currencies, and the corresponding merchant information can be updated by the payment institution used by the merchant. The mobile device 310 can obtain the updated merchant name and supported payment currencies by scanning the same QR code. Compared with the RTM QR code, the RTM QR code needs to be replaced when the service information is updated because it is embedded with service information. In addition, since the RTM QR code carries service information, scanning the RTM QR code may be slower than scanning the STM QR code that does not carry service information.

[0064] Various types of service information can be updated by using a URL-based QR code. Figure 4 4 is a schematic diagram showing an example 400 of interoperability of services and URL-based QR codes according to an embodiment of the present disclosure. In this example 400, the URL decoded from the scanned QR code 410 can be used to initiate services such as dining services 420, payment services 430, IOT information 440, web content 450, APP download 460, or LBS 470. By associating different services with service type IDs and service objects identified in the URL, the mobile device can obtain different types of services or service information from the scanned QR code 410.

[0065] Reference again Figure 1 In step 126, the service information is returned to the service account provider by the digital service network 112. In step 128, a service confirmation page including the returned service information is provided by the user-side service organization 110 and pushed to the APP 106 on the mobile device. In some embodiments, the user-side service organization 110 returns the service information forwarded by the digital service network 112 to the mobile device. The APP 106 installed on the mobile device can provide the service information on the service confirmation page.

[0066] Using mobile payment as an example, if the service information (e.g., merchant name) is correct, the user can confirm the service information or provide input (e.g., enter the payment amount) when necessary to initiate a payment request in step 130. In step 132, the user-side service organization 110 receives the payment request and deducts the corresponding payment amount from the user's account. In step 134, the user-side service organization 110 sends the payment to the digital service network 112. In step 136, the digital service network 112 forwards the payment to the acquisition-side service organization 114. The acquisition-side service organization 114 processes the payment and credits the merchant 108 in step 138, sends a payment confirmation to the merchant 108 in step 140a, and sends the payment confirmation to the digital service network 112 in step 140b. In step 142, the digital service network forwards the payment confirmation to the user-side service organization 110, and the user-side service organization 110 forwards the payment confirmation to the APP 106 or provides a payment confirmation page and pushes it to the APP 106.

[0067] In the service processing workflow, the direct information exchange between APP 106 and the acquisition side 104 is relatively limited. Most of the information is exchanged in the backend between the user-side service agency 110, the digital service network 112, and the acquisition-side service agency 114. The information exchange environment has a high degree of trust and can better protect the data security between all parties.

[0068] Figure 5 is a swim lane diagram showing an example of a two-dimensional code binding process 500 according to an embodiment of the present disclosure. The code binding process can be used to quickly generate a batch of regional unified two-dimensional codes.

[0069] In step 514, the service system I 508 generates a batch of idle codes and sends them to the code platform 506. The idle code can be a URL-based STM QR code, such as Figure 1 The QR code is empty because the embedded URL is not associated with any service information. In some embodiments, the service system I 508 can be as follows Figure 1 In some embodiments, the service system 1 508 can collect merchant information, such as the number of merchants to be served, to determine the number of idle codes to be generated. The code platform 506 can be part of the service system 1 508 or independent of the service system 1 508.

[0070] At step 516, the service system I 508 sends the batch of idle codes to the material platform 512 for printing and sending back to the service system I 508. The material platform 512 can be part of the service organization or independent of the service system I 508.

[0071] In step 518, the merchant 502 served by the service system 1 508 scans the batch of idle codes to submit merchant information to be bound to the idle codes. The merchant information may include Figure 1 By sending the merchant information to the code platform, the code platform can bind the corresponding service type and service object identified in the URL of the idle code to the merchant information.

[0072] In step 520, the code platform 506 binds the merchant information to the batch of free codes. After binding, the URL-based QR code is no longer empty, but is associated with the corresponding merchant information. Then, the service system I 508 can distribute the printed code to the corresponding merchant 502 it serves.

[0073] At step 522, user 504 scans the URL-based QR code presented by merchant 502 to initiate the corresponding service process. At step 524, the service process can proceed to service organization II 510, for example, at Figure 1 The remaining service processing can be performed based on the exemplary workflow 100, as shown in Figure 1 as discussed in the description of .

[0074] Figure 6 6 is a flowchart illustrating an example of a method 600 for a URL-based QR code processing service according to an embodiment of the present disclosure. For clarity of presentation, the following description generally describes the method 600 in the context of other figures in this specification. However, it should be understood that the method 600 can be performed, for example, by any suitable system, environment, software and hardware, or a combination of systems, environments, software and hardware. In some embodiments, the various steps of the method 600 can be run in parallel, in combination, in a loop, or in any order.

[0075] In step 602, a URL is received from a first service organization, wherein the URL is obtained by a mobile device by scanning a QR code provided by a service provider and sent by the mobile device. The method 600 may be performed by a digital service network 112, which is connected to and serves one or more service organizations, such as Figure 1As discussed in the description of . The first service agency may be a user-side service agency 110. The QR code may be a QR code based on a URL, such as a QR code presented by a merchant based on a regional uniformity generated by an STM. The QR code may be presented by a service provider (e.g., a merchant) to initiate a service (e.g., a payment service). The user may open an APP associated with the user account to scan the QR code. The URL may be obtained by scanning the QR code and sent to a service agency that provides the user account. The service agency may parse the URL to identify a network ID and send at least a portion of the URL to a digital service network corresponding to the network ID. Starting from step 602, method 600 proceeds to step 604.

[0076] In step 604, the URL is parsed to identify one or more data elements, wherein the one or more data elements include a service network ID, a service agency ID of a second service agency that identifies the release of a QR code, and a payload including an identifier of a service object of the service network. In some embodiments, the one or more data elements also include at least one of the following: a domain name, a version number of the service network, a service type ID that identifies the service type, or one or more key-value pairs that identify one or more additional items of the service to be processed. The one or more data elements included in the URL can be in digital format or text format. The one or more additional items of the service to be processed include at least one of a credibility value, voucher information, coupon information, lucky drawing information, a global positioning system (GPS) location, a table number, or a seat number. Starting from step 604, method 600 proceeds to step 606.

[0077] In step 606, one or more data elements are sent to a second service based on the service ID. The second service may be the acquisition-side service 114, which issues a URL-based QR code, such as Figure 1 Starting from step 606 , method 600 proceeds to step 608 .

[0078] At step 608, service information associated with the service object is received from the second service organization. In some embodiments, the service information includes at least one of service provider information or order information. Exemplary service provider information includes service provider name, service provider type, nationality code, zip code, service provider address, order information, one or more supported languages, or one or more supported currencies. Exemplary order information includes transaction amount, transaction currency, order identification, or order description. Starting from step 608, method 600 proceeds to step 610.

[0079] In step 610, the service information is sent to the first service agency for presentation on the mobile device. In some embodiments, after the user of the mobile device verifies the service information, the mobile device may send a service request to initiate the service. In this case, the digital service network may receive the service request from the first service agency. The digital service network may then send the service request to the second service agency for processing the service. After processing, the service processing result is received from the second service agency. The digital service network may then send the service processing result to the first service agency for presentation on the mobile device. After step 610, the method 600 stops.

[0080] The embodiments of the subject matter described in this specification can be implemented to achieve specific advantages or technical effects. For example, since most service information can be managed and maintained at the back end, when the service information needs to be updated, the service provider does not have to request and redeploy a new QR code in the RTM scenario. Updates can sometimes be performed at the back end to reduce deployment and material costs. The URL decoded from the QR code generated under STM provides an identifier for locating and returning service information. The QR code itself does not carry service information. Therefore, the STM QR code is separated from its underlying service. STM can also allow rapid batch generation of URL-based QR codes.

[0081] The method described above improves the processing efficiency and data security of various mobile computing devices. Because the amount of information encoded in the QR code based on STM is relatively small, the collection of most service information can be entrusted to the back-end server, the data interaction between the mobile device and the QR code is faster, and the data security is higher because the information exposure at the front end is reduced. Therefore, the credibility of the information interaction environment is high, and the data security between the parties can be better protected.

[0082] The above described method can ensure the effective use of computer resources (e.g., processing cycle, network bandwidth and memory usage) by effectively scanning, generating a two-dimensional code and reducing the amount of two-dimensional code regeneration. At least these actions can minimize or completely avoid the waste of available computer resources in the mobile Internet service environment. When the service information is updated, it is not to replace the existing two-dimensional code, but to make the two-dimensional code remain unchanged by associating the existing two-dimensional code with the updated service information.

[0083] The embodiments and operations described in this specification may be implemented in digital electronic circuits, or in computer software, firmware or hardware (including the structures disclosed in this specification or a combination of one or more thereof). Operations may be implemented as operations performed by a data processing device on data stored on one or more computer-readable storage devices or received from other sources. A data processing device, a computer or a computing device may include devices, devices and machines for processing data, including, for example, a programmable processor, a computer, a system on a chip, or a plurality or combination of the foregoing. The device may include a dedicated logic circuit, such as a central processing unit (CPU), a field programmable gate array (FPGA) or an application-specific integrated circuit (ASIC). The device may also include code for creating an execution environment for the computer program in question, such as code constituting a processor firmware, a protocol stack, a database management system, an operating system (such as an operating system or a combination of operating systems), a cross-platform operating environment, a virtual machine or a combination of one or more thereof. The device and the execution environment may implement a variety of different computing model infrastructures, such as web services, distributed computing and grid computing infrastructures.

[0084] A computer program (also referred to as a program, software, software application, software module, software unit, script, or code) may be written in any form of programming language, including compiled or interpreted languages, declarative or procedural languages, and it may be deployed in any form, including as a stand-alone program or as a module, component, subroutine, object, or other unit suitable for a computing environment. A program may be stored in a portion of a file that contains other programs or data (e.g., one or more scripts stored in a markup language document), in a single file dedicated to the program in question, or in multiple coordinated files (e.g., files storing one or more modules, subroutines, or portions of code). A computer program may be executed on one computer or on multiple computers that are located at one site or distributed over multiple sites and interconnected by a communications network.

[0085] As an example, processors for executing computer programs include general and special microprocessors, and any one or more processors of any type of digital computer. Typically, the processor will receive instructions and data from a read-only memory or a random access memory or both. The basic elements of a computer are a processor for performing actions according to instructions and one or more memory devices for storing instructions and data. Typically, a computer will also include or be operably connected to receive data from one or more mass storage devices or transfer data to one or more mass storage devices for storing data. The computer can be embedded in another device, such as a mobile device, a personal digital assistant (PDA), a game console, a global positioning system (GPS) receiver, or a portable storage device. Devices suitable for storing computer program instructions and data include non-volatile memory, media, and memory devices, such as semiconductor memory devices, disks, and magneto-optical disks. The processor and memory can be supplemented with or incorporated into a dedicated logic circuit.

[0086] Mobile devices may include cell phones, user equipment (UE), mobile phones (e.g., smartphones), tablet computers, wearable devices (e.g., smart watches and smart glasses), implanted devices in the human body (e.g., biosensors, cochlear implants), or other types of mobile devices. Mobile devices may communicate wirelessly (e.g., using radio frequency (RF) signals) with various communication networks (described below). Mobile devices may include sensors for determining characteristics of the current environment of the mobile device. Sensors may include cameras, microphones, proximity sensors, GPS sensors, motion sensors, accelerometers, ambient light sensors, humidity sensors, gyroscopes, compasses, barometers, fingerprint sensors, facial recognition systems, RF sensors (e.g., Wi-Fi and cellular radios), thermal sensors, or other types of sensors. For example, a camera may include a forward or backward camera with a movable or fixed lens, a flash, an image sensor, and an image processor. The camera may be a megapixel camera capable of capturing details of facial and / or iris recognition. The camera, together with a data processor and authentication information stored in a memory or accessed remotely, may form a facial recognition system. A facial recognition system or one or more sensors (eg, a microphone, motion sensor, accelerometer, GPS sensor, or RF sensor) may be used for user authentication.

[0087] To provide interaction with a user, embodiments may be implemented on a computer having a display device and an input device, such as a liquid crystal display (LCD) or organic light emitting diode (OLED) / virtual reality (VR) / augmented reality (AR) display for displaying information to the user and a touch screen, keyboard, and pointing device through which the user can provide input to the computer. Other types of devices may also be used to provide interaction with the user; for example, the feedback provided to the user may be any form of sensory feedback, such as visual feedback, auditory feedback, or tactile feedback; and input from the user may be received in any form, including acoustic, verbal, or tactile input. In addition, the computer may interact with the user by sending documents to and receiving documents from a device used by the user; for example, by sending a web page to a web browser on a user's client device in response to a request received from the web browser.

[0088] Embodiments may be implemented using computing devices interconnected by any form or medium of wired or wireless digital data communication (or a combination thereof), such as a communication network. Examples of interconnected devices are a client and a server that is typically remote from one another and that typically interacts via a communication network. A client (e.g., a mobile device) may perform transactions with or through a server, such as buying, selling, paying, giving, sending, or loaning transactions or authorizing transactions. Such transactions may be real-time, such that actions and responses are close in time; for example, an individual perceives that an action and response occur substantially simultaneously, the time difference in response after an individual's action is less than 1 millisecond (ms) or less than 1 second (s), or there is no deliberate delay in response to account for limitations of the account processing system.

[0089] Examples of communication networks include a local area network (LAN), a radio access network (RAN), a metropolitan area network (MAN), and a wide area network (WAN). A communication network may include all or a portion of the Internet, another communication network, or a combination of communication networks. Information may be sent over a communication network according to various protocols and standards, including Long Term Evolution (LTE), 5G, IEEE 802, Internet Protocol (IP), or other protocols or combinations of protocols. A communication network may transmit voice, video, biometric or authentication data, or other information between connected computing devices.

[0090] Features described as separate implementations may be implemented in combination in a single implementation, and features described as a single implementation may be implemented in multiple implementations individually or in any suitable subcombination. Operations described and claimed in a particular order should not be understood as requiring a particular order, nor is it necessary to require that all illustrated operations be performed (some operations may be optional). Multitasking or parallel processing (or a combination of multitasking and parallel processing) may be performed where appropriate.

Claims

1. A service processing method, the method comprising: Scan the QR code provided by the service provider, which is embedded with a uniform resource locator URL; The two-dimensional code does not embed the service information to be presented by the service provider; The data elements encoded in the URL include: a payload, a target service agency identifier, and a target service type identifier; the payload includes a service object identifier corresponding to a service object of the digital service network; Based on the URL, the first service agency is requested to provide the service information of the service provider; wherein the first service agency is used to: if the target service agency identifier matches the service agency identifier, determine the maintained service information and return it; otherwise, The data element is sent to the digital service network; The digital service network is used to: send the target service type identifier and the payload to an acquisition-side service agency that matches the target service agency identifier; The acquisition-side service mechanism is used to: determine the code type of the two-dimensional code based on the target service type identifier and the payload, and determine the service information of the service provider associated with the service object based on the determined code type; The service information of the service provider is pre-bound to the URL in the QR code in the following manner: after the service provider scans a pre-generated idle code embedded in the URL but not associated with the service information, the service information is submitted and bound to the corresponding service type and service object identified in the URL of the idle code; The service information of the service provider returned by the first service organization is received and presented.

2. The method according to claim 1, further comprising: After presenting the service information for user confirmation, sending a service request to the first service agency according to the user's operation, so that the first service agency uses the service request to obtain the service processing result of the service provider for the service request; Receive and present the service processing result returned by the first service agency.

3. According to the method of claim 1, the two-dimensional code includes any of the following: Merchant code, order code, transfer code, social media group code, interoperability code, aggregation code or regional unified code.

4. The method according to claim 1, wherein the service provided by the service provider comprises any of the following: Payment services, dining services, location-based services, content services or APP installation services. The method according to claim 1 , wherein the service information comprises at least one of service provider information or order information.

6. The method according to claim 5, wherein the service provider information comprises any one of the following: Service Provider name, Service Provider type, country code, postal code, Service Provider address, order information, one or more supported languages, or one or more supported currencies; and / or, The order information includes any of the following: transaction amount, transaction currency, order identification or order description.

7. The method according to claim 1, wherein requesting the service information of the service provider from the first service organization based on the URL comprises: Decode the QR code to obtain a string in URL format; The string in the URL format is sent to the first service agency, so that the first service agency parses the URL and obtains the service information of the service provider according to the parsing result.

8. The method according to claim 1, wherein the URL carries one or more data elements, and the data elements are used for the digital service network to manage the service information and / or manage a second service organization corresponding to the service provider.

9. The method according to claim 8, wherein the data element further comprises: The service network identifier corresponding to the digital service network.

10. The method according to claim 9, wherein the data element further comprises at least one of the following: a domain name, a version number of a service network, or one or more key-value pairs for identifying one or more additional items of a service to be processed. The method according to claim 8 , wherein the data element is in a digital format or a text format.

12. The method according to claim 10, wherein: The one or more additional items of the service to be processed include at least one of the following: a reputation value, voucher information, coupon information, lucky drawing information, a global positioning system GPS location, a table number or a seat number.

13. A service processing method, the method being applied to a first service organization, the method comprising: Receiving a request based on a uniform resource locator URL initiated by a user client after scanning a QR code, wherein the URL is embedded in the QR code; The QR code is embedded with a uniform resource locator URL; The two-dimensional code does not embed the service information to be presented by the service provider; The data elements encoded in the URL include: a payload, a target service agency identifier, and a target service type identifier; the payload includes a service object identifier corresponding to a service object of the digital service network; Obtaining service information of a service provider pre-bound to the URL; wherein, In the case where the target service agency identifier matches the service agency identifier, determining the maintained service information and returning it; otherwise, sending the data element to the digital service network; The digital service network is used to: send the target service type identifier and the payload to an acquisition-side service agency that matches the target service agency identifier; The acquisition-side service mechanism is used to: determine the code type of the two-dimensional code based on the target service type identifier and the payload, and determine the service information of the service provider associated with the service object based on the determined code type; The service information of the service provider is pre-bound in the following manner: after the service provider scans a pre-generated idle code embedded in the URL but not associated with the service information, the service information is submitted and bound to the corresponding service type and service object identified in the URL of the idle code; The service information is returned to the user client so that the user client presents the service information.

14. The method according to claim 13, wherein the request comprises a string in a URL format; The obtaining of service information of a service provider pre-bound to the URL includes: The URL-formatted character string is parsed, and service information of a service provider pre-bound to the URL is acquired according to the parsing result.

15. The method according to claim 14, wherein the data element further comprises: The service network identifier corresponding to the digital service network. 16 . The method according to claim 15 , wherein the data element further comprises at least one of the following: a domain name, a version number of a service network, or one or more key-value pairs for identifying one or more additional items of a service to be processed. The method according to claim 14 , wherein the data element is in a digital format or a text format.

18. The method according to claim 13, further comprising: A service request sent by the user client after presenting the service information is received, a service processing result of the service provider on the service request is obtained and returned to the user client, so that the user client presents the service processing result.

19. The method according to claim 13, further comprising: Obtain updated service information provided by the service provider; The service information bound to the URL is replaced with the updated service information.

20. A service processing method, the method being applied to a digital service network, the method comprising: Receiving one or more data elements in the URL sent by the first service organization; The URL is sent to the first service agency after the user client scans the QR code; The QR code is embedded with a uniform resource locator URL; The two-dimensional code does not embed the service information to be presented by the service provider; the data elements include: payload, target service agency identifier and target service type identifier; The payload includes a service object identifier corresponding to a service object of the digital service network; The first service agency is used to: if the target service agency identifier matches the service agency identifier, determine and return the maintained service information; otherwise, send the data element to the digital service network; The digital service network is used to: send the target service type identifier and the payload to an acquisition-side service agency that matches the target service agency identifier; The acquisition-side service mechanism is used to: acquire service information associated with a service object of a service provider pre-bound to the URL based on the target service type identifier and the payload in the URL; The service information of the service provider is pre-bound in the following manner: after the service provider scans a pre-generated idle code embedded in the URL but not associated with the service information, the service information is submitted and bound to the service type and service object identified in the URL of the idle code; The service information is returned to the first service agency, so that the first service agency provides the service information to the user client.

21. The method according to claim 20, further comprising: receiving a service request initiated by a user client forwarded by the first service agency, sending the service request to an acquisition-side service agency, and receiving a service processing result from the acquisition-side service agency; The service processing result is sent to the first service agency, so that the first service agency provides the service processing result to the user client.

22. A computer device, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein: When the processor executes the program, the method according to any one of claims 1 to 21 is implemented.

Images