Smart watch aggregation code service processing method, device and equipment

Abstract

The embodiment of this specification discloses a smart watch aggregation code business processing scheme. It includes: the application service end receives the business trigger instruction sent by the smart watch end by scanning the aggregation code displayed by the target merchant; according to the business trigger instruction, by calling the first SPI interface, a merchant information query request is sent to the aggregation code service provider, so that the smart watch end obtains the information of the target merchant; the business execution request is received by the smart watch end according to the information of the target merchant; according to the business execution request, by calling the second SPI interface, a corresponding merchant business order creation request is sent to the aggregation code service provider, so that the aggregation code service provider places an order to the open platform corresponding to the application service end, the first SPI interface and the second SPI interface are defined by the application service provider to which the application service end belongs, and are implemented by the aggregation code service provider; the merchant business order generated and returned by the open platform in response to the order is received, and the business processing process is completed according to the merchant business order.

Description

Technical Field

[0001] The present invention relates to the field of payment technology, and in particular to a method, device and equipment for processing aggregation code services for smart watches. Background Art

[0002] With the development of Internet technology and the popularization of smart phone use, more and more business can be conducted through applications on smart phones, bringing great convenience to people's lives.

[0003] For payment and other business areas, QR codes are now widely used. In daily life, users may use QR code payment services provided by different payment service providers, and different QR codes for payment will be used. Users need to use the correct correspondence and use a payment service provider's application (referring to the user's device, usually the application client) to scan the QR code of the payment service provider to make payments. If the payment service provider's application is used to scan the QR code of other payment service providers, payment may not be made normally. Based on this, in order to provide convenience and fault tolerance for users to scan codes, aggregation codes have emerged. It aggregates the QR code services of two or more different payment service providers. Merchants can generate their own aggregation codes and provide them to users for payment. Users can use any of these payment service providers' applications to scan the aggregation code and make payments normally.

[0004] In a current aggregation code payment solution, when you scan the aggregation code displayed by a merchant through the payment service provider's application on a smartphone, the merchant's aggregation code H5 page will be opened in the application's H5 container, and the user can then place an order and pay on the aggregation code H5 page.

[0005] However, the above aggregation code payment solution has problems on smart watches. Due to the insufficient capabilities of the smart watch operating system, it is often unable to land in the H5 container environment, and it is difficult to use this solution to implement smart watch aggregation code payment. Similar problems may also exist for other smart watch aggregation code services.

[0006] Based on this, an aggregation code service processing solution that is more suitable for smart watches is needed. Summary of the invention

[0007] One or more embodiments of this specification provide a method, device, and equipment for processing aggregation code services for smart watches to solve the following technical problems: An aggregation code service processing solution that is more suitable for smart watches is needed.

[0008] To solve the above technical problems, one or more embodiments of this specification are implemented as follows:

[0009] One or more embodiments of this specification provide a smart watch aggregation code service processing method, which is applied to a payment service end, and the method includes:

[0010] Receive the business trigger instruction sent by the smart watch by scanning the aggregation code displayed by the target merchant;

[0011] According to the service trigger instruction, by calling the first SPI interface (Service Provider Interface), a merchant information query request is sent to the aggregation code service provider, so that the smart watch end obtains the information of the target merchant queried by the aggregation code service provider;

[0012] Receiving a service execution request sent by the smart watch according to the information of the target merchant;

[0013] According to the business execution request, by calling the second SPI interface, a corresponding merchant business order creation request is sent to the aggregation code service provider, so that the aggregation code service provider places a corresponding order to the open platform corresponding to the application server, wherein the first SPI interface and the second SPI interface are defined by the application service provider to which the application server belongs, but implemented by the aggregation code service provider;

[0014] Receive the merchant service order generated and returned by the open platform in response to the order, and complete the business processing process according to the merchant service order.

[0015] Another smart watch aggregation code service processing method provided by one or more embodiments of this specification is applied to a smart watch end, and the method includes:

[0016] By scanning the aggregation code displayed by the target merchant, a service trigger instruction is sent to the application server, so that the application server sends a merchant information query request to the aggregation code service provider by calling the first SPI interface according to the service trigger instruction;

[0017] Obtain the information of the target merchant queried by the aggregation code service provider, and send a business execution request to the application server according to the information of the target merchant, so that the application server can send a corresponding merchant business order creation request to the aggregation code service provider by calling the second SPI interface according to the business execution request, and receive the merchant business order, and promote the completion of the business processing process according to the merchant business order, wherein the merchant business order is generated and returned to the aggregation code service provider by the aggregation code service provider responding to the business order creation request and placing a corresponding order to the open platform corresponding to the application server, and the first SPI interface and the second SPI interface are defined by the application service provider to which the application server belongs, but are implemented by the aggregation code service provider.

[0018] One or more embodiments of this specification provide a smart watch aggregation code business processing device, which is applied to a payment service end, and the device includes:

[0019] A trigger receiving module receives a business trigger instruction sent by the smart watch by scanning the aggregation code displayed by the target merchant;

[0020] The first calling module sends a merchant information query request to the aggregation code service provider by calling the first SPI interface according to the business trigger instruction, so that the smart watch end obtains the information of the target merchant queried by the aggregation code service provider;

[0021] An execution receiving module receives a service execution request sent by the smart watch according to the information of the target merchant;

[0022] The second calling module sends a corresponding merchant business order creation request to the aggregation code service provider by calling the second SPI interface according to the business execution request, so that the aggregation code service provider places a corresponding order to the open platform corresponding to the application server, wherein the first SPI interface and the second SPI interface are defined by the application service provider to which the application server belongs, but implemented by the aggregation code service provider;

[0023] The business promotion module receives the merchant business order generated and returned by the open platform in response to the order, and promotes the completion of the business processing process according to the merchant business order.

[0024] One or more embodiments of this specification provide a smart watch aggregation code service processing device, which is applied to a smart watch end, and the device includes:

[0025] The scanning trigger module sends a service trigger instruction to the application server by scanning the aggregation code displayed by the target merchant, so that the application server sends a merchant information query request to the aggregation code service provider by calling the first SPI interface according to the service trigger instruction;

[0026] An execution request module obtains the information of the target merchant queried by the aggregation code service provider, and sends a business execution request to the application server according to the information of the target merchant, so that the application server sends a corresponding merchant business order creation request to the aggregation code service provider by calling the second SPI interface according to the business execution request, and receives the merchant business order, and promotes the completion of the business processing process according to the merchant business order, wherein the merchant business order is generated and returned to the aggregation code service provider by the aggregation code service provider responding to the business order creation request and placing a corresponding order to the open platform corresponding to the application server, and the first SPI interface and the second SPI interface are defined by the application service provider to which the application server belongs, but are implemented by the aggregation code service provider.

[0027] One or more embodiments of this specification provide a smart watch aggregation code business processing device, which is applied to a payment service end, and the device includes:

[0028] at least one processor; and,

[0029] a memory communicatively connected to the at least one processor; wherein,

[0030] The memory stores instructions executable by the at least one processor, the instructions being executed by the at least one processor to enable the at least one processor to execute:

[0031] Receive the business trigger instruction sent by the smart watch by scanning the aggregation code displayed by the target merchant;

[0032] According to the service trigger instruction, by calling the first SPI interface, a merchant information query request is sent to the aggregation code service provider, so that the smart watch end obtains the information of the target merchant queried by the aggregation code service provider;

[0033] Receiving a service execution request sent by the smart watch according to the information of the target merchant;

[0034] According to the business execution request, by calling the second SPI interface, a corresponding merchant business order creation request is sent to the aggregation code service provider, so that the aggregation code service provider places a corresponding order to the open platform corresponding to the application server, wherein the first SPI interface and the second SPI interface are defined by the application service provider to which the application server belongs, but implemented by the aggregation code service provider;

[0035] Receive the merchant service order generated and returned by the open platform in response to the order, and complete the business processing process according to the merchant service order.

[0036] One or more embodiments of this specification provide a smart watch aggregation code service processing device, which is applied to a smart watch end, and the device includes:

[0037] at least one processor; and,

[0038] a memory communicatively connected to the at least one processor; wherein,

[0039] The memory stores instructions executable by the at least one processor, the instructions being executed by the at least one processor to enable the at least one processor to execute:

[0040] By scanning the aggregation code displayed by the target merchant, a service trigger instruction is sent to the application server, so that the application server sends a merchant information query request to the aggregation code service provider by calling the first SPI interface according to the service trigger instruction;

[0041] Obtain the information of the target merchant queried by the aggregation code service provider, and send a business execution request to the application server according to the information of the target merchant, so that the application server can send a corresponding merchant business order creation request to the aggregation code service provider by calling the second SPI interface according to the business execution request, and receive the merchant business order, and promote the completion of the business processing process according to the merchant business order, wherein the merchant business order is generated and returned to the aggregation code service provider by the aggregation code service provider responding to the business order creation request and placing a corresponding order to the open platform corresponding to the application server, and the first SPI interface and the second SPI interface are defined by the application service provider to which the application server belongs, but are implemented by the aggregation code service provider.

[0042] At least one of the above-mentioned technical solutions adopted in one or more embodiments of the present specification can achieve the following beneficial effects: the SPI interface is defined by the application service provider (represented by the application server) for query and ordering, and one or more aggregation code service providers implement these SPI interfaces accordingly, thereby standardizing the interaction between the application service provider and the aggregation code service provider, without relying on the H5 container. Compared with the solution based on the H5 container, it has better stability and helps to improve the business success rate. Moreover, it reduces the access cost between the application service provider and the aggregation code service provider, and also gives the aggregation code service provider better flexibility, so that even if the smart watch does not support the H5 container, it can still reliably and conveniently implement services such as payment based on the aggregation code. Therefore, it has good applicability to smart watches and helps to improve the user experience of smart watches. BRIEF DESCRIPTION OF THE DRAWINGS

[0043] In order to more clearly illustrate the embodiments of this specification or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments recorded in this specification. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative labor.

[0044] Figure 1 A flowchart of a method for processing a smart watch aggregation code service according to one or more embodiments of this specification;

[0045] Figure 2 A flowchart of a calling decision scheme of a first SPI interface provided in one or more embodiments of this specification;

[0046] Figure 3 A flowchart of a dial theme interface control solution provided for one or more embodiments of this specification;

[0047] Figure 4 In an application scenario provided by one or more embodiments of this specification, Figure 1 A schematic diagram of an implementation scheme of the method;

[0048] Figure 5 In an application scenario provided by one or more embodiments of this specification, Figure 4 The solution involves some schematic diagrams of the display contents of the dials on the smartwatch;

[0049] Figure 6 A flowchart of another method for processing a smart watch aggregation code service provided in one or more embodiments of this specification;

[0050] Figure 7A schematic diagram of the structure of a smart watch aggregation code service processing device provided in one or more embodiments of this specification;

[0051] Figure 8 A schematic diagram of the structure of another smart watch aggregation code service processing device provided in one or more embodiments of this specification;

[0052] Fig. 9 A schematic diagram of the structure of a smart watch aggregation code service processing device provided in one or more embodiments of this specification;

[0053] Fig.10 A schematic diagram of the structure of another smart watch aggregation code service processing device provided in one or more embodiments of this specification. DETAILED DESCRIPTION

[0054] The embodiments of this specification provide a smart watch aggregation code service processing method, device, equipment and storage medium.

[0055] In order to enable those skilled in the art to better understand the technical solutions in this specification, the technical solutions in the embodiments of this specification will be clearly and completely described below in conjunction with the drawings in the embodiments of this specification. Obviously, the described embodiments are only part of the embodiments of this application, not all of them. Based on the embodiments of this specification, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of this application.

[0056] The business described in this application is typically a payment business, which is the target business that the user wants to conduct. For the convenience of description, some of the following embodiments are mainly explained by using the payment business scenario as an example. Of course, other businesses with similar problems may also adopt the solution of this application to solve, such as e-commerce business, event registration business, health service business, advertising business, etc.

[0057] As understood in the background technology, smart watches have more limited capabilities than smartphones. For example, due to the limitations of their operating system capabilities, it is difficult to implement the H5 container environment locally on smart watches (smart watch manufacturers often remove the H5 container function in order to improve the operating efficiency of the watch and reduce resource consumption). Therefore, it is difficult to implement the aggregation code payment solution based on the H5 container. This can easily lead to payment failures on smart watches, which in turn can easily lead to the loss of users and payment services for payment service providers, especially for children's smart watches. Children's smart watches are often the only mobile payment devices for children. If they fail to make aggregation code payments using the device, they are very likely to lose users and it is difficult to recover them, not to mention the need for secondary payments. This is a pity for the platform and a loss of improvement opportunities for users.

[0058] In response to the problems mentioned in the background technology, in order to enable smart watches to better support aggregate code payment, the applicant initially tried to create the following solution: use the smart watch to scan the aggregate code, and when the scan is successful, open an H5 container in the cloud synchronously, and load the aggregate code link in the container. When the smart watch user enters the amount and clicks to pay, the relevant operations are synchronized to the cloud. The cloud container can intercept the payment request and return the order information to the smart watch to promote payment. However, during testing, it was found that the solution still had problems, mainly including: the cloud container needs to adapt to various types of aggregate codes, identify the amount input and payment UI above, intercept the corresponding operations, the compatibility is not good enough and the cost is relatively high.

[0059] In response to the above problems, the applicant has created and provided in this application an aggregation code business processing solution that is more suitable for smart watches, such as an aggregation code payment solution, to solve these problems.

[0060] Based on this overall situation, the solution of the present application will be further described below.

[0061] Figure 1 A flowchart of a method for processing a smartwatch aggregation code service is provided for one or more embodiments of this specification. The execution subject of the process may include an application server, which is a server corresponding to a smartwatch. The smartwatch here mainly refers to a software end for providing target services at the software level (for example, a payment application client or applet, etc., in which case the application server is the payment server). Of course, at the hardware level, it is the smartwatch itself, the mobile device.

[0062] The smart watch mentioned in this application has hardware modules such as a camera for supporting the code scanning function. The applications on the smart watch can call these hardware modules to realize the scanning and recognition of the QR code within the application.

[0063] Figure 1 The process in includes the following steps:

[0064] S102: Receive a service trigger instruction sent by the smart watch by scanning the aggregation code displayed by the target merchant.

[0065] Aggregation codes, as a code, can support the same type of business in multiple different channels at the same time (of course, they can also support multiple different types of business at the same time). For example, payment aggregation codes support different payment methods provided by more than two different payment service providers at the same time. When users scan the code, they can automatically identify the payment method corresponding to the application used for scanning the code. At present, aggregation codes are still mainly expressed in the form of QR codes, and may evolve into higher-dimensional codes in the future.

[0066] Different merchants have their own proprietary aggregation codes, which can be pre-generated with the support of aggregation code service providers and displayed to users for scanning. Aggregation code service providers can grasp the correct correspondence between different aggregation codes and different merchants.

[0067] The user scans and identifies the aggregation code displayed by the target merchant through the scanning function provided by an application client or a small program on the smart watch, and sends a business trigger instruction to the corresponding application server based on the scanning and identification results.

[0068] In one or more embodiments of the present specification, the service trigger instruction can be used to request to query the information of the current target merchant, so as to prompt the user, so that the user can have sufficient perception to confirm the service to be performed. The service trigger instruction can include at least part of the code value of the aggregation code, or the parsing result obtained after parsing these code values.

[0069] It should be noted that the term "merchant" in this application can be understood as a broader concept. Merchants are entities that use the platform of application service providers to provide services to users. In addition to merchants who sell goods in common e-commerce scenarios, entities that use the platform to organize other activities for users, provide non-commodity services, or conduct management assessments can also be broadly regarded as merchants from the perspective of application service providers.

[0070] S104: According to the service trigger instruction, a merchant information query request is sent to the aggregation code service provider by calling the first SPI interface, so that the smart watch terminal obtains the information of the target merchant queried by the aggregation code service provider.

[0071] In one or more embodiments of this specification, the SPI interface mentioned in this application, i.e., the service supply interface, is defined by the application service provider at the interface level, but at the implementation level, it is on the independent software developer or merchant side that cooperates with the application service provider. In the aggregation code scenario, for example, it is implemented by the aggregation code service provider. In this way, the same SPI interface defined by the application service provider to which the application service provider belongs can be implemented differently by different aggregation code service providers according to their actual needs, with good compatibility, which helps to efficiently access more aggregation code service providers without the need for frequent changes by the application service provider. Therefore, it is sufficiently standardized from the perspective of the application service provider, shielding these differences from the user side.

[0072] The first SPI interface can be mainly used to request and query the target merchant's information, that is, it can be used as a merchant information query interface. The target merchant information queried by the aggregation code service provider can be returned directly to the smart watch end by the aggregation code service provider, or indirectly returned to the smart watch end through the application server. It should be noted that there may not be only one first SPI interface, it can also be a set of multiple SPI interfaces, each SPI interface in the set can be responsible for more detailed functions, for example, there is a first SPI interface for initiating a merchant information query request, and there can also be another first SPI interface for returning merchant information query results, and so on.

[0073] S106: Receive a service execution request sent by the smart watch according to the information of the target merchant.

[0074] The smartwatch displays a confirmation interface to the user based on the target merchant's information. The confirmation interface can indicate the specific merchant currently being targeted, such as the merchant name, merchant logo, etc. Of course, the merchant's services can also be described, such as information about the goods to be paid, the amount to be paid, etc. The user can perform a confirmation operation on the confirmation interface (a more specific service selection function can also be provided to the user, so that the user can confirm which service to execute among multiple optional services), thereby triggering the smartwatch to send a service execution request to the application server.

[0075] In one or more embodiments of this specification, the smartwatch may not support H5 containers or even H5 pages. In this case, the solution of this application can particularly demonstrate advantages over the prior art. In this case, the confirmation interface does not belong to a page in the H5 container or even an H5 page.

[0076] Furthermore, considering that the application server has the ability to shield the differences in the interfaces implemented by different aggregation code service providers through the SPI interface (for example, differences in input and output parameters, data format, field meaning, compliance requirements, algorithms used, etc.), the confirmation interface can also be presented in a more standardized manner. In this case, the confirmation interface may not be a page or interface obtained from the aggregation code service provider, which reduces the implementation cost of the aggregation code service provider and helps to avoid the possibility of compatibility between the confirmation interface and the smart watch end. At the same time, considering the simultaneous support of the aggregation code service provider to directly return merchant information and indirectly return merchant information, the smart watch end can be generated locally based on the information of the target merchant, rather than the page obtained from the application server. In this way, the smart watch end can more flexibly adapt to its own capabilities to generate a confirmation interface, especially a page with a simpler form suitable for display and viewing on a smart watch. From the perspective of the application service provider, such an operation is also more standardized and takes into account personalization, which can avoid being restricted too much by the aggregation code service provider or the application server.

[0077] S108: According to the business execution request, by calling the second SPI interface, a corresponding merchant business order creation request is sent to the aggregation code service provider, so that the aggregation code service provider places a corresponding order to the open platform corresponding to the application server, wherein the first SPI interface and the second SPI interface are defined by the application service provider to which the application server belongs, but are implemented by the aggregation code service provider.

[0078] The second SPI interface can be understood similarly with reference to the first SPI interface above. The difference between the two is mainly in the usage. The second SPI interface is mainly used to create a merchant business order.

[0079] The business execution request sent by the smartwatch can also be regarded as an order operation. The order here (for the sake of distinction, it is called user order) is from the user of the smartwatch to the merchant, while the merchant business order is from the merchant (or executed by the aggregation code service provider) to the business service provider. The business service provider is a third party between the user and the merchant, providing a business platform for both parties. User orders are used for user requests to conduct business, while merchant business orders are based on providing the corresponding services for the business and requesting corresponding benefits (usually paid by the user). For example, in the payment scenario, the user order can be a payment order for the merchant service, and the merchant business order can be a merchant cashier order. It can be seen that these two order operations are corresponding and unified, and are essentially the same business transaction.

[0080] The open platform is a platform provided by application service providers and mainly for merchants or developers. In this application, it can be used for aggregation code service providers or merchants to place orders. The open platform and the application server can be different entities. The direct interaction of users mainly involves the application server, and less likely to involve the open platform. Of course, if the corresponding functions of the open platform are integrated into the application server, the aggregation code service provider can also place orders through the application server. The process may involve the interaction of different modules in the application server; the application server can also obtain the required information from the aggregation code service provider to generate a merchant business order for the aggregation code service provider. Compared with the interaction method based on the open platform, this method has higher requirements for the application server.

[0081] S110: receiving a merchant service order generated and returned by the open platform in response to the order, and completing the service processing according to the merchant service order.

[0082] In one or more embodiments of this specification, according to the merchant business order, the price paid by the user can be obtained from the user (for example, the payment amount is deducted) and the merchant is settled accordingly. This is explained here based on the logic of common payment services. Of course, for services that do not involve payment, the application server can similarly complete the service for the user and the merchant according to the merchant business order, thereby completing its task as a third party.

[0083] pass Figure 1 The method is to define the SPI interface through the application service provider (represented by the application server) for query and ordering, and one or more aggregation code service providers implement these SPI interfaces accordingly, which standardizes the interaction between the application service provider and the aggregation code service provider. There is no need to rely on the H5 container. Compared with the solution based on the H5 container, it has better stability and helps to improve the business success rate. Moreover, it reduces the access cost between the application service provider and the aggregation code service provider, and also gives the aggregation code service provider better flexibility, so that even if the smart watch does not support the H5 container, it can still reliably and conveniently implement services such as payment based on the aggregation code. Therefore, it has good applicability to smart watches and helps to improve the user experience of smart watches.

[0084] based on Figure 1 This specification also provides some specific implementation plans and extension plans of the method, which will be described below.

[0085] According to the principle of the above scheme, one or more embodiments of this specification provide a flowchart of a call decision scheme of a first SPI interface, see Figure 2 .

[0086] Figure 2 The process in includes the following steps:

[0087] S202: After receiving the service trigger instruction sent by the smart watch, determine whether the smart watch supports the H5 container according to the service trigger instruction.

[0088] If H5 containers are not supported, the SPI interface-based solution is preferred. If H5 containers are supported, you can consider switching to a solution based on H5 containers and business interception.

[0089] For the convenience of judgment, the service trigger instruction can carry the capability information of the smart watch. Of course, if the type of the sending device can be judged according to the service trigger instruction, a simpler judgment can be made, which is more efficient. For example, according to the service trigger instruction, it is judged whether the sending device is a smart watch or a smart phone. If it is a smart watch, the subsequent steps are continued.

[0090] S204: If not, then according to the business trigger instruction, by calling the first SPI interface, a merchant information query request carrying the code value of the aggregation code and the identifier of the smart watch end is sent to the aggregation code service provider, so that the aggregation code service provider can query the information of the target merchant according to the code value of the aggregation code, and return the information of the target merchant to the smart watch end according to the identifier of the smart watch end.

[0091] If the aggregation code service provider returns the target merchant's information to the smart watch indirectly through the application server, the merchant information query request may not carry the smart watch's identification.

[0092] In the case that the smart watch does not support H5 containers or even H5 interfaces, for the confirmation interface, this application considers not using a separate additional page, but instead using a dial theme (at least including the smart watch desktop) to present it. In this way, the user can be prompted clearly and unobtrusively, and it is convenient for persistent accumulation and dynamic display of the user's business status over a period of time without having to enter specific business applications, and less processing resources are occupied.

[0093] Based on this idea, one or more embodiments of this specification provide a flowchart of a dial theme interface control solution, see Figure 3 .

[0094] Figure 3 The process in includes the following steps:

[0095] S302: Predefine dial theme feature parameters for the first SPI interface, and the dial theme feature parameters are used by the aggregation code service provider to assign values ​​according to the queried merchant information. The information of the target merchant is represented by the assigned dial theme feature parameters, which are returned to the smart watch end through the first SPI interface (directly by the aggregation code service provider or indirectly through the application server).

[0096] The dial theme characteristic parameters may include, for example, control layout, desktop, style, icon, text, etc. Different dial theme characteristic parameters may be assigned differently for merchant information of different merchants, and after assignment, the merchant and / or the current business to be conducted may be reflected from one or more of the above parameter dimensions for intuitive understanding by users.

[0097] S304: Receive a service execution request sent by the smart watch end in response to a confirmation operation performed on a temporary dial theme interface serving as the confirmation interface, wherein the temporary dial theme interface is generated based on the assigned dial theme feature parameters and is automatically switched from a default dial theme interface for use.

[0098] In one or more embodiments of the present specification, the default dial theme interface can be the dial theme interface used by the smart watch end when scanning the aggregation code displayed by the target merchant. After switching, the user can clearly perceive that he is currently in the process of service interaction with the corresponding merchant, and can more clearly feel which merchant is currently, which is also helpful to promote the merchant. In this case, the user can remain on the desktop on the smart watch without having to display a separate page covering the desktop, which consumes little resources and does not affect the user's execution of other operations during the period. The temporary dial theme interface can be accompanied by controls for performing confirmation operations, such as an icon on the desktop, etc., and even the physical buttons or knobs on the smart watch can be directly used as confirmation buttons or knobs.

[0099] S306: After the merchant business order promotion business processing process is completed, a dial theme interface restoration instruction is sent to the smart watch end, so that the smart watch end switches from the temporary dial theme interface back to the default dial theme interface.

[0100] Similarly, the smart watch can also automatically switch and restore the dial theme interface without the need for an application server to indicate a trigger.

[0101] In one or more embodiments of the present specification, the default dial theme interface can be dynamically updated according to the user's business with different merchants on the smart watch, so as to simultaneously display the conditions of these merchants (for example, on a daily basis, displaying the conditions of all merchants involved on that day). In this way, the default dial theme interface itself is equivalent to a cumulative poster recording the interaction conditions of merchants, which can be continuously displayed on the smart watch, and such continuity does not consume additional processing resources, thereby increasing the actual value of the dial theme to the user.

[0102] In this case, in step S306, the default watch dial theme interface switched back to can be obtained by updating the previous default watch dial theme interface (adding the current merchant) according to the temporary watch dial theme interface.

[0103] Furthermore, for the default watch face theme interface that is dynamically updated based on merchant information, users can choose different presentation modes according to their needs. For example, if users are more concerned about the amount of information, the "information mode" is used to more clearly reflect the merchant information involved. If users are more concerned about aesthetics, the "artistic mode" is used. In this case, the merchant information can be blurred and presented in an artistic way, which will reduce its intuitiveness, but may be more beautiful.

[0104] In addition, even after the business is completed, the user can continue to use the temporary watch face theme interface according to needs, and it is not necessary to switch back.

[0105] According to the above description, for ease of understanding, taking the application scenario of payment service as an example, one or more embodiments of this specification provide in this scenario: Figure 1 A schematic diagram of an embodiment of the method of Figure 4 .

[0106] In this scenario, the above-mentioned application server is specifically the payment server (the application is specifically the payment application), the smart watch is specifically the payment client, the application service provider is specifically the payment service provider, the business execution request is specifically the payment request, and the merchant business order is specifically the merchant cashier order.

[0107] for Figure 4 The solution in the above requires advance preparation. This includes defining two SPI interfaces, one for querying merchant information and the other for creating merchant cashier slips in the aggregation code scenario. These two interfaces are implemented by the aggregation code service provider as the first SPI interface and the second SPI interface mentioned above. The entire process is also mainly divided according to the work involved in these two interfaces.

[0108] Regarding querying merchant information, the main logic includes: the user opens the payment client on the smart watch and scans the aggregation code displayed by the current merchant; after that, it will trigger the payment server to call the first SPI interface to pass the merchant aggregation code value and other related information to the aggregation code service provider; the aggregation code service provider will query the merchant name, merchant LOGO, merchant ID, payment amount and other merchant information behind the code based on this information, and then send this information back to the payment client through the first SPI interface; after the payment client obtains this information, it renders and displays the confirmation interface corresponding to the merchant for the user to confirm and verify the merchant information, and then confirm it after it is correct.

[0109] Regarding the merchant cashier slip in the aggregation code scenario, the main logic includes: the user clicks confirm in the confirmation interface corresponding to the merchant; after that, it will trigger the payment server to call the second SPI interface to pass the payment user, payment amount and other information to the aggregation code service provider; the aggregation code service provider can then place an order on the payment service provider's open platform based on this information and obtain the merchant cashier slip. After the order is placed, the order number and other related information will be returned to the payment server through the second SPI interface; after the payment server receives the order information, it can initiate and complete the payment.

[0110] Intuitively, one or more embodiments of this specification provide another application scenario: Figure 4 The solution involves some diagrams of the display contents of the watch faces on the smartwatch side, see Figure 5 .

[0111] Figure 5 There are five sub-pictures in the figure. From left to right and from top to bottom, the first sub-picture shows that the user is prompted to scan the QR code. Assuming that the user scans the aggregation code displayed by a merchant, the confirmation interface is rendered locally, as shown in the second sub-picture. This is a simple page for smart watches, not an H5 page in an H5 container. For example, the name of the merchant "XX Grocery Store" is included. The user can click the "Pay to Ta" button to enter the interface in the third sub-picture, which shows that the payment amount can be manually specified when initiating payment. After confirming the payment amount, the user can enter the interface in the fourth sub-picture. The user can further click the "Confirm Payment" button to place an order to initiate payment. After the payment process is completed, the user enters the interface in the fifth sub-picture, prompting the user that the payment is successful. The entire display process and content are clear and concise, with less resource consumption, which is very friendly to smart watches and easy for users to understand and operate.

[0112] pass Figure 4The solution is based on the SPI interface defined for querying merchant information and creating aggregated cashier slips and implemented by the aggregation code service provider, which avoids compatibility issues and effectively improves the stability and success rate of aggregation code payment. Compared with the aggregation code payment solution based on H5 container, it has better stability and higher payment success rate, which helps the aggregation code service providers to access and effectively retain more users, especially children's smart watch users.

[0113] The foregoing description is mainly from the perspective of the application server. Based on the same idea, one or more embodiments of this specification also provide another smart watch aggregation code service processing method, which is described from the perspective of the smart watch. Figure 6 A flow chart of another method is shown in FIG.

[0114] Figure 6 The process in includes the following steps:

[0115] S602: Send a service trigger instruction to the application server by scanning the aggregation code displayed by the target merchant, so that the application server sends a merchant information query request to the aggregation code service provider by calling the first SPI interface according to the service trigger instruction.

[0116] S604: Obtain the information of the target merchant queried by the aggregation code service provider, and send a business execution request to the application server according to the information of the target merchant, so that the application server can send a corresponding merchant business order creation request to the aggregation code service provider by calling the second SPI interface according to the business execution request, and receive the merchant business order, and promote the completion of the business processing process according to the merchant business order, wherein the merchant business order is generated and returned to the aggregation code service provider by the aggregation code service provider responding to the business order creation request and placing a corresponding order to the open platform corresponding to the application server, and the first SPI interface and the second SPI interface are defined by the application service provider to which the application server belongs, but are implemented by the aggregation code service provider.

[0117] For details, please refer to the previous instructions and will not be repeated here.

[0118] Based on the same idea, one or more embodiments of this specification also provide devices and apparatuses corresponding to the above methods, such as Figure 7~Figure 10 The apparatus and device can accordingly execute the above method and related optional solutions.

[0119] The trigger receiving module 702 receives the business trigger instruction sent by the smart watch by scanning the aggregation code displayed by the target merchant;

[0120] The first calling module 704 sends a merchant information query request to the aggregation code service provider by calling the first SPI interface according to the business trigger instruction, so that the smart watch end obtains the information of the target merchant queried by the aggregation code service provider;

[0121] An execution receiving module 706 receives a service execution request sent by the smart watch according to the information of the target merchant;

[0122] The second calling module 708 sends a corresponding merchant business order creation request to the aggregation code service provider by calling the second SPI interface according to the business execution request, so that the aggregation code service provider places a corresponding order to the open platform corresponding to the application server, wherein the first SPI interface and the second SPI interface are defined by the application service provider to which the application server belongs, but implemented by the aggregation code service provider;

[0123] The business promotion module 710 receives the merchant business order generated and returned by the open platform in response to the order, and promotes the completion of the business processing process according to the merchant business order.

[0124] Optionally, the first calling module 704 sends a merchant information query request carrying the code value of the aggregation code and the identifier of the smart watch end to the aggregation code service provider, so that the aggregation code service provider queries the information of the target merchant according to the code value of the aggregation code, and returns the information of the target merchant to the smart watch end according to the identifier of the smart watch end.

[0125] Optionally, the first calling module 704, before sending a merchant information query request to the aggregation code service provider by calling the first SPI interface according to the business trigger instruction, determines whether the smart watch supports the H5 container according to the business trigger instruction, and determines that the result of the judgment is no.

[0126] Optionally, the execution receiving module 706 receives a service execution request sent by the smart watch in response to a confirmation operation performed on the confirmation interface;

[0127] The confirmation interface does not belong to a page in the H5 container.

[0128] Optionally, the confirmation interface is an interface generated locally by the smart watch according to the information of the target merchant, rather than a page obtained from the aggregation code service provider or the application server.

[0129] Optionally, the first SPI interface defines a dial theme feature parameter, the dial theme feature parameter is used by the aggregation code service provider, and is assigned according to the queried merchant information, and the information of the target merchant is represented by the dial theme feature parameter after the assignment, and is returned to the smart watch end through the first SPI interface;

[0130] The execution receiving module 706 receives a service execution request sent by the smart watch end in response to a confirmation operation performed on a temporary dial theme interface serving as the confirmation interface, wherein the temporary dial theme interface is generated based on the assigned dial theme feature parameters and is automatically switched from the default dial theme interface for use.

[0131] Optionally, the business promotion module 710 sends a dial theme interface restoration instruction to the smart watch end after the merchant business order promotion business processing process is completed, so that the smart watch end switches from the temporary dial theme interface back to the default dial theme interface.

[0132] Optionally, the open platform is a platform provided by the application service provider, used for aggregation code service providers or merchants to place orders, and the open platform and the application server are different entities.

[0133] Optionally, the application server includes a payment server, the application service provider includes a payment service provider, the business execution request includes a payment request, and the merchant business order includes a merchant cashier order.

[0134] Figure 8 A schematic diagram of the structure of another smart watch aggregation code service processing device provided in one or more embodiments of this specification, wherein the device is applied to a smart watch end, and the device includes:

[0135] The scanning trigger module 802 sends a service trigger instruction to the application server by scanning the aggregation code displayed by the target merchant, so that the application server sends a merchant information query request to the aggregation code service provider by calling the first SPI interface according to the service trigger instruction;

[0136] The execution request module 804 obtains the information of the target merchant queried by the aggregation code service provider, and sends a business execution request to the application server according to the information of the target merchant, so that the application server sends a corresponding merchant business order creation request to the aggregation code service provider by calling the second SPI interface according to the business execution request, and receives the merchant business order, and promotes the completion of the business processing process according to the merchant business order, wherein the merchant business order is generated and returned to the aggregation code service provider by the aggregation code service provider responding to the business order creation request and placing a corresponding order to the open platform corresponding to the application server, and the first SPI interface and the second SPI interface are defined by the application service provider to which the application server belongs, but are implemented by the aggregation code service provider.

[0137] Fig. 9 A schematic diagram of the structure of a smart watch aggregation code business processing device provided in one or more embodiments of this specification, the device is applied to a payment service end, and the device includes:

[0138] at least one processor; and,

[0139] a memory communicatively connected to the at least one processor; wherein,

[0140] The memory stores instructions executable by the at least one processor, the instructions being executed by the at least one processor to enable the at least one processor to execute:

[0141] Receive the business trigger instruction sent by the smart watch by scanning the aggregation code displayed by the target merchant;

[0142] According to the service trigger instruction, by calling the first SPI interface, a merchant information query request is sent to the aggregation code service provider, so that the smart watch end obtains the information of the target merchant queried by the aggregation code service provider;

[0143] Receiving a service execution request sent by the smart watch according to the information of the target merchant;

[0144] According to the business execution request, by calling the second SPI interface, a corresponding merchant business order creation request is sent to the aggregation code service provider, so that the aggregation code service provider places a corresponding order to the open platform corresponding to the application server, wherein the first SPI interface and the second SPI interface are defined by the application service provider to which the application server belongs, but implemented by the aggregation code service provider;

[0145] Receive the merchant service order generated and returned by the open platform in response to the order, and complete the business processing process according to the merchant service order.

[0146] Fig.10 A schematic diagram of the structure of another smart watch aggregation code service processing device provided in one or more embodiments of this specification, wherein the device is applied to a smart watch end, and the device includes:

[0147] at least one processor; and,

[0148] a memory communicatively connected to the at least one processor; wherein,

[0149] The memory stores instructions executable by the at least one processor, the instructions being executed by the at least one processor to enable the at least one processor to execute:

[0150] By scanning the aggregation code displayed by the target merchant, a service trigger instruction is sent to the application server, so that the application server sends a merchant information query request to the aggregation code service provider by calling the first SPI interface according to the service trigger instruction;

[0151] Obtain the information of the target merchant queried by the aggregation code service provider, and send a business execution request to the application server according to the information of the target merchant, so that the application server can send a corresponding merchant business order creation request to the aggregation code service provider by calling the second SPI interface according to the business execution request, and receive the merchant business order, and promote the completion of the business processing process according to the merchant business order, wherein the merchant business order is generated and returned to the aggregation code service provider by the aggregation code service provider responding to the business order creation request and placing a corresponding order to the open platform corresponding to the application server, and the first SPI interface and the second SPI interface are defined by the application service provider to which the application server belongs, but are implemented by the aggregation code service provider.

[0152] Based on the same idea, one or more embodiments of this specification further provide a non-volatile computer storage medium, which is applied to a payment service end, and the medium stores computer executable instructions, and the computer executable instructions are configured as follows:

[0153] Receive the business trigger instruction sent by the smart watch by scanning the aggregation code displayed by the target merchant;

[0154] According to the service trigger instruction, by calling the first SPI interface, a merchant information query request is sent to the aggregation code service provider, so that the smart watch end obtains the information of the target merchant queried by the aggregation code service provider;

[0155] Receiving a service execution request sent by the smart watch according to the information of the target merchant;

[0156] According to the business execution request, by calling the second SPI interface, a corresponding merchant business order creation request is sent to the aggregation code service provider, so that the aggregation code service provider places a corresponding order to the open platform corresponding to the application server, wherein the first SPI interface and the second SPI interface are defined by the application service provider to which the application server belongs, but implemented by the aggregation code service provider;

[0157] Receive the merchant service order generated and returned by the open platform in response to the order, and complete the business processing process according to the merchant service order.

[0158] One or more embodiments of this specification also provide another non-volatile computer storage medium, which is applied to a smart watch, and the medium stores computer executable instructions, and the computer executable instructions are set to:

[0159] By scanning the aggregation code displayed by the target merchant, a service trigger instruction is sent to the application server, so that the application server sends a merchant information query request to the aggregation code service provider by calling the first SPI interface according to the service trigger instruction;

[0160] Obtain the information of the target merchant queried by the aggregation code service provider, and send a business execution request to the application server according to the information of the target merchant, so that the application server can send a corresponding merchant business order creation request to the aggregation code service provider by calling the second SPI interface according to the business execution request, and receive the merchant business order, and promote the completion of the business processing process according to the merchant business order, wherein the merchant business order is generated and returned to the aggregation code service provider by the aggregation code service provider responding to the business order creation request and placing a corresponding order to the open platform corresponding to the application server, and the first SPI interface and the second SPI interface are defined by the application service provider to which the application server belongs, but are implemented by the aggregation code service provider.

[0161] In the 1990s, it was very clear whether the improvement of a technology was hardware improvement (for example, improvement of the circuit structure of diodes, transistors, switches, etc.) or software improvement (improvement of the method flow). However, with the development of technology, many improvements of the method flow today can be regarded as direct improvements of the hardware circuit structure. Designers almost always obtain the corresponding hardware circuit structure by programming the improved method flow into the hardware circuit. Therefore, it cannot be said that the improvement of a method flow cannot be implemented with hardware entity modules. For example, a programmable logic device (PLD) (such as a field programmable gate array (FPGA)) is such an integrated circuit whose logical function is determined by the user's programming of the device. Designers can "integrate" a digital system on a PLD by programming it themselves, without having to ask chip manufacturers to design and make dedicated integrated circuit chips. Moreover, nowadays, instead of manually making integrated circuit chips, this kind of programming is mostly implemented by "logic compiler" software, which is similar to the software compiler used when developing and writing programs, and the original code before compilation must also be written in a specific programming language, which is called hardware description language (HDL). There is not only one kind of HDL, but many kinds, such as ABEL (Advanced Boolean Expression Language), AHDL (Altera Hardware Description Language), Confluence, CUPL (Cornell University Programming Language), HDCal, JHDL (Java Hardware Description Language), Lava, Lola, MyHDL, PALASM, RHDL (Ruby Hardware Description Language), etc. The most commonly used ones are VHDL (Very-High-Speed ​​Integrated Circuit Hardware Description Language) and Verilog. Those skilled in the art should also know that it is only necessary to program the method flow slightly in the above-mentioned hardware description languages ​​and program it into the integrated circuit, and then it is easy to obtain the hardware circuit that implements the logic method flow.

[0162] The controller may be implemented in any suitable manner, for example, the controller may take the form of a microprocessor or processor and a computer-readable medium storing a computer-readable program code (e.g., software or firmware) executable by the (micro)processor, a logic gate, a switch, an application-specific integrated circuit (ASIC), a programmable logic controller, and an embedded microcontroller, examples of which include but are not limited to the following microcontrollers: ARC 625D, Atmel AT91SAM, Microchip PIC18F26K20, and Silicone Labs C8051F320, and the memory controller may also be implemented as part of the control logic of the memory. It is also known to those skilled in the art that, in addition to implementing the controller in a purely computer-readable program code manner, the controller may be implemented in the form of a logic gate, a switch, an application-specific integrated circuit, a programmable logic controller, and an embedded microcontroller by logically programming the method steps. Therefore, such a controller may be considered as a hardware component, and the devices for implementing various functions included therein may also be considered as structures within the hardware component. Or even, the devices for implementing various functions may be considered as both software modules for implementing the method and structures within the hardware component.

[0163] The systems, devices, modules or units described in the above embodiments may be implemented by computer chips or entities, or by products with certain functions. A typical implementation device is a computer. Specifically, the computer may be, for example, a personal computer, a laptop computer, a cellular phone, a camera phone, a smart phone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or a combination of any of these devices.

[0164] For the convenience of description, the above device is described in various units according to their functions. Of course, when implementing this specification, the functions of each unit can be implemented in the same or multiple software and / or hardware.

[0165] Those skilled in the art will appreciate that the embodiments of this specification may be provided as methods, systems, or computer program products. Therefore, the embodiments of this specification may take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Moreover, the embodiments of this specification may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program codes.

[0166] This specification is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the embodiments of this specification. It should be understood that each process and / or block in the flowchart and / or block diagram, as well as the combination of processes and / or blocks in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0167] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0168] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

[0169] In a typical configuration, a computing device includes one or more processors (CPU), input / output interfaces, network interfaces, and memory.

[0170] The memory may include non-permanent storage in a computer-readable medium, random access memory (RAM) and / or non-volatile memory in the form of read-only memory (ROM) or flash RAM. The memory is an example of a computer-readable medium.

[0171] Computer readable media include permanent and non-permanent, removable and non-removable media that can be implemented by any method or technology to store information. Information can be computer readable instructions, data structures, program modules or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disk read-only memory (CD-ROM), digital versatile disk (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device. As defined herein, computer readable media does not include temporary computer readable media (transitory media), such as modulated data signals and carrier waves.

[0172] It should also be noted that the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, commodity or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, commodity or device. In the absence of more restrictions, the elements defined by the sentence "comprises a ..." do not exclude the existence of other identical elements in the process, method, commodity or device including the elements.

[0173] This specification may be described in the general context of computer-executable instructions executed by a computer, such as program modules. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform specific tasks or implement specific abstract data types. This specification may also be practiced in distributed computing environments where tasks are performed by remote processing devices connected through a communication network. In a distributed computing environment, program modules may be located in local and remote computer storage media, including storage devices.

[0174] Each embodiment in this specification is described in a progressive manner, and the same or similar parts between the embodiments can be referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the device, equipment, and non-volatile computer storage medium embodiments, since they are basically similar to the method embodiments, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiment.

[0175] The above is a description of a specific embodiment of the specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recorded in the claims can be performed in an order different from that in the embodiments and still achieve the desired results. In addition, the processes depicted in the drawings do not necessarily require the specific order or continuous order shown to achieve the desired results. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.

[0176] The above description is only one or more embodiments of this specification and is not intended to limit this specification. For those skilled in the art, one or more embodiments of this specification may have various changes and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of one or more embodiments of this specification shall be included in the scope of the claims of this specification.

Claims

1. A method for processing a smart watch aggregation code service, applied to an application server, the method comprising: Receive the business trigger instruction sent by the smart watch by scanning the aggregation code displayed by the target merchant; According to the service trigger instruction, by calling the first SPI interface, a merchant information query request is sent to the aggregation code service provider, so that the smart watch end obtains the information of the target merchant queried by the aggregation code service provider; Receiving a service execution request sent by the smart watch according to the information of the target merchant; According to the business execution request, by calling the second SPI interface, a corresponding merchant business order creation request is sent to the aggregation code service provider, so that the aggregation code service provider places a corresponding order to the open platform corresponding to the application server, wherein the first SPI interface and the second SPI interface are defined by the application service provider to which the application server belongs, but implemented by the aggregation code service provider; Receive the merchant service order generated and returned by the open platform in response to the order, and complete the business processing process according to the merchant service order.

2. The method according to claim 1, wherein sending a merchant information query request to an aggregation code service provider so that the smart watch terminal obtains the information of the target merchant queried by the aggregation code service provider specifically includes: A merchant information query request carrying the code value of the aggregation code and the identifier of the smart watch terminal is sent to the aggregation code service provider, so that the aggregation code service provider can query the information of the target merchant according to the code value of the aggregation code, and return the information of the target merchant to the smart watch terminal according to the identifier of the smart watch terminal.

3. The method according to claim 1, before sending a merchant information query request to the aggregation code service provider by calling the first SPI interface according to the business trigger instruction, the method further comprises: According to the service trigger instruction, it is determined whether the smart watch supports the H5 container, and the result of the determination is determined to be no.

4. The method according to claim 1, wherein receiving the service execution request sent by the smartwatch according to the information of the target merchant comprises: receiving a service execution request sent by the smart watch in response to a confirmation operation performed on a confirmation interface; The confirmation interface does not belong to a page in the H5 container.

5. According to the method of claim 4, the confirmation interface is an interface generated locally by the smart watch end according to the information of the target merchant, rather than a page obtained from the aggregation code service provider or the application server.

6. The method according to claim 4 or 5, wherein the first SPI interface defines dial theme feature parameters, the dial theme feature parameters are used by the aggregation code service provider, and are assigned according to the queried merchant information, and the information of the target merchant is represented by the dial theme feature parameters after the assignment, and is returned to the smart watch end through the first SPI interface; The receiving the service execution request sent by the smart watch according to the information of the target merchant specifically includes: Receive a service execution request sent by the smart watch end in response to a confirmation operation performed on a temporary dial theme interface serving as the confirmation interface, wherein the temporary dial theme interface is generated based on the assigned dial theme feature parameters and is automatically switched from a default dial theme interface for use.

7. The method according to claim 6, after the merchant business order promotion business processing process is completed, the method further comprises: A dial theme interface restoration instruction is sent to the smart watch end, so that the smart watch end switches from the temporary dial theme interface back to the default dial theme interface.

8. The method according to claim 1, wherein the open platform is a platform provided by the application service provider, used for aggregation code service providers or merchants to place orders, and the open platform and the application server are different entities.

9. The method as claimed in claim 1, wherein the application server includes a payment server, the application service provider includes a payment service provider, the business execution request includes a payment request, and the merchant business order includes a merchant cashier order.

10. A method for processing a smart watch aggregation code service, applied to a smart watch, the method comprising: By scanning the aggregation code displayed by the target merchant, a service trigger instruction is sent to the application server, so that the application server sends a merchant information query request to the aggregation code service provider by calling the first SPI interface according to the service trigger instruction; Obtain the information of the target merchant queried by the aggregation code service provider, and send a business execution request to the application server according to the information of the target merchant, so that the application server can send a corresponding merchant business order creation request to the aggregation code service provider by calling the second SPI interface according to the business execution request, and receive the merchant business order, and promote the completion of the business processing process according to the merchant business order, wherein the merchant business order is generated and returned to the aggregation code service provider by the aggregation code service provider responding to the business order creation request and placing a corresponding order to the open platform corresponding to the application server, and the first SPI interface and the second SPI interface are defined by the application service provider to which the application server belongs, but are implemented by the aggregation code service provider.

11. A smart watch aggregation code business processing device, applied to a payment service end, the device comprising: A trigger receiving module receives a business trigger instruction sent by the smart watch by scanning the aggregation code displayed by the target merchant; The first calling module sends a merchant information query request to the aggregation code service provider by calling the first SPI interface according to the business trigger instruction, so that the smart watch end obtains the information of the target merchant queried by the aggregation code service provider; An execution receiving module receives a service execution request sent by the smart watch according to the information of the target merchant; The second calling module sends a corresponding merchant business order creation request to the aggregation code service provider by calling the second SPI interface according to the business execution request, so that the aggregation code service provider places a corresponding order to the open platform corresponding to the application server, wherein the first SPI interface and the second SPI interface are defined by the application service provider to which the application server belongs, but implemented by the aggregation code service provider; The business promotion module receives the merchant business order generated and returned by the open platform in response to the order, and promotes the completion of the business processing process according to the merchant business order.

12. In the device as described in claim 11, the first calling module sends a merchant information query request carrying the code value of the aggregation code and the identifier of the smart watch end to the aggregation code service provider, so that the aggregation code service provider can query the information of the target merchant according to the code value of the aggregation code, and return the information of the target merchant to the smart watch end according to the identifier of the smart watch end.

13. The device as described in claim 11, before sending a merchant information query request to the aggregation code service provider by calling the first SPI interface according to the business trigger instruction, the first calling module determines whether the smart watch end supports the H5 container according to the business trigger instruction, and determines that the result of the judgment is no.

14. The device according to claim 11, wherein the execution receiving module receives a service execution request sent by the smart watch in response to a confirmation operation performed on the confirmation interface; in, The confirmation interface does not belong to the page in the H5 container.

15. The device as claimed in claim 14, wherein the confirmation interface is an interface generated locally by the smart watch end according to the information of the target merchant, rather than a page obtained from the aggregation code service provider or the application server end.

16. The device according to claim 14 or 15, wherein the first SPI interface defines a dial theme feature parameter, the dial theme feature parameter is used by the aggregation code service provider, and is assigned according to the queried merchant information, and the information of the target merchant is represented by the dial theme feature parameter after the assignment, and is returned to the smart watch end through the first SPI interface; The execution receiving module receives a service execution request sent by the smart watch end in response to a confirmation operation performed on a temporary dial theme interface serving as the confirmation interface, wherein: The temporary dial theme interface is generated according to the assigned dial theme characteristic parameters, and is automatically switched from the default dial theme interface for use.

17. In the device as described in claim 16, the business promotion module sends a dial theme interface restoration instruction to the smart watch end after the business processing process of the merchant business order is completed, so that the smart watch end switches from the temporary dial theme interface back to the default dial theme interface.

18. The device as claimed in claim 11, wherein the open platform is a platform provided by the application service provider and is used for aggregation code service providers or merchants to place orders, and the open platform and the application server are different entities.

19. The device as claimed in claim 11, wherein the application server includes a payment server, the application service provider includes a payment service provider, the business execution request includes a payment request, and the merchant business order includes a merchant cashier order.

20. A smart watch aggregation code service processing device, applied to a smart watch end, the device comprising: The scanning trigger module sends a service trigger instruction to the application server by scanning the aggregation code displayed by the target merchant, so that the application server sends a merchant information query request to the aggregation code service provider by calling the first SPI interface according to the service trigger instruction; An execution request module obtains the information of the target merchant queried by the aggregation code service provider, and sends a business execution request to the application server according to the information of the target merchant, so that the application server sends a corresponding merchant business order creation request to the aggregation code service provider by calling the second SPI interface according to the business execution request, and receives the merchant business order, and promotes the completion of the business processing process according to the merchant business order, wherein the merchant business order is generated and returned to the aggregation code service provider by the aggregation code service provider responding to the business order creation request and placing a corresponding order to the open platform corresponding to the application server, and the first SPI interface and the second SPI interface are defined by the application service provider to which the application server belongs, but are implemented by the aggregation code service provider.

21. A smart watch aggregation code business processing device, applied to a payment service end, the device comprising: at least one processor; as well as, a memory communicatively connected to the at least one processor; wherein, The memory stores instructions executable by the at least one processor, the instructions being executed by the at least one processor to enable the at least one processor to execute: Receive the business trigger instruction sent by the smart watch by scanning the aggregation code displayed by the target merchant; According to the service trigger instruction, by calling the first SPI interface, a merchant information query request is sent to the aggregation code service provider, so that the smart watch end obtains the information of the target merchant queried by the aggregation code service provider; Receiving a service execution request sent by the smart watch according to the information of the target merchant; According to the business execution request, by calling the second SPI interface, a corresponding merchant business order creation request is sent to the aggregation code service provider, so that the aggregation code service provider places a corresponding order to the open platform corresponding to the application server, wherein the first SPI interface and the second SPI interface are defined by the application service provider to which the application server belongs, but implemented by the aggregation code service provider; Receive the merchant service order generated and returned by the open platform in response to the order, and complete the business processing process according to the merchant service order.

22. A smart watch aggregation code service processing device, applied to a smart watch end, the device comprising: at least one processor; as well as, a memory communicatively connected to the at least one processor; wherein, The memory stores instructions executable by the at least one processor, the instructions being executed by the at least one processor to enable the at least one processor to execute: By scanning the aggregation code displayed by the target merchant, a service trigger instruction is sent to the application server, so that the application server sends a merchant information query request to the aggregation code service provider by calling the first SPI interface according to the service trigger instruction; Obtain the information of the target merchant queried by the aggregation code service provider, and send a business execution request to the application server according to the information of the target merchant, so that the application server can send a corresponding merchant business order creation request to the aggregation code service provider by calling the second SPI interface according to the business execution request, and receive the merchant business order, and promote the completion of the business processing process according to the merchant business order, wherein the merchant business order is generated and returned to the aggregation code service provider by the aggregation code service provider responding to the business order creation request and placing a corresponding order to the open platform corresponding to the application server, and the first SPI interface and the second SPI interface are defined by the application service provider to which the application server belongs, but are implemented by the aggregation code service provider.

Images