Smart watch aggregation code service processing method, device and equipment

Abstract

The embodiment of the invention discloses a smart watch aggregation code service processing scheme. Comprising the steps that an application server side receives a service triggering instruction sent by a smart watch side through scanning an aggregation code displayed by a target merchant; according to the service triggering instruction, a merchant information query request is sent to an aggregation code service provider by calling a first SPI interface, so that the intelligent watch end obtains information of a target merchant; receiving a service execution request sent by the smart watch end according to the information of the target merchant; according to the business execution request, a second SPI interface is called to send a corresponding merchant business order creation request to an aggregation code service provider, so that the aggregation code service provider correspondingly places an order to an open platform corresponding to the application server side, and the first SPI interface and the second SPI interface are defined by an application service provider to which the application server side belongs and are realized by the aggregation code service provider; and receiving a merchant business list generated and returned by the open platform in response to the order, and promoting the completion of the business processing process according to the merchant business list.

Description

[0001] This application is a divisional application of the invention patent application with the application number 202411557045.9 and the invention title "Intelligent Watch Aggregate Code Service Processing Method, Device and Equipment" filed with the China National Patent Office on November 4, 2024. The full text of this application is incorporated herein by reference. Technical Field

[0002] This specification relates to the field of payment technologies, and particularly to an intelligent watch aggregate code service processing method, device and equipment. Background Art

[0003] With the development of Internet technologies and the popularization of the use of smart phones, more and more services can be carried out through applications on smart phones, bringing great convenience to people's lives.

[0004] In the field of services such as payment, two-dimensional codes have been widely used at present. When users may use two-dimensional code payment services provided by different payment service providers in their daily lives, they will use different two-dimensional codes for payment. Users need to scan the two-dimensional code of a certain payment service provider in accordance with the correct corresponding relationship using an application of that payment service provider (referring to the user device side, usually the application client) to make a payment. If the application of that payment service provider is used to scan the two-dimensional code of other payment service providers, the payment may not be carried out normally. Based on this, in order to provide convenience and fault tolerance for users to scan codes, aggregate codes have emerged. They aggregate the two-dimensional code services of two or more different payment service providers. Merchants can generate their own aggregate codes and provide them to users for payment. Users can use the application of any of these payment service providers to scan the aggregate code and can all carry out normal payments.

[0005] In a current aggregate code payment scheme, when scanning the aggregate code displayed by a merchant on a smart phone through the application of a payment service provider, the aggregate code H5 page of the merchant will be opened in the H5 container of the application, and the user can then operate to place an order and make a payment on the aggregate code H5 page.

[0006] However, the above-mentioned aggregate code payment scheme has problems on smart watches. Because of the limited capabilities of the smart watch operating system, it is often impossible to implement the H5 container environment, and thus it is difficult to implement smart watch aggregate code payment using this scheme. Similar problems may also exist for other smart watch aggregate code services.

[0007] Based on this, an aggregate code service processing scheme more suitable for smart watches is needed. Summary of the Invention

[0008] One or more embodiments of this specification provide a method, device, and equipment for processing the aggregated code service of a smart watch to solve the following technical problem: a more suitable aggregated code service processing solution for smart watches is needed.

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

[0010] A method for processing the aggregated code service of a smart watch provided by one or more embodiments of this specification is applied to a payment server. The method includes:

[0011] Receiving a service trigger instruction sent by the smart watch end through scanning an aggregated code displayed by a target merchant;

[0012] According to the service trigger instruction, by calling a first SPI interface (Service Provider Interface), sending a merchant information query request to the aggregated code service provider, so that the smart watch end can obtain the information of the target merchant queried by the aggregated code service provider;

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

[0014] According to the service execution request, by calling a second SPI interface, sending a corresponding merchant service order creation request to the aggregated code service provider, so that the aggregated code service provider places an order with the corresponding open platform of the application server. Among them, the first SPI interface and the second SPI interface are interfaces defined by the application service provider to which the application server belongs but implemented by the aggregated code service provider;

[0015] Receiving the merchant service order generated and returned by the open platform in response to the order placement, and completing the service processing process according to the merchant service order.

[0016] Another method for processing the aggregated code service of a smart watch provided by one or more embodiments of this specification is applied to the smart watch end. The method includes:

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

[0018] Obtain the information of the target merchant queried by the aggregation code service provider, and send a service execution request to the application server according to the information of the target merchant, so that the application server, according to the service execution request, sends a corresponding merchant service order creation request to the aggregation code service provider by calling the second SPI interface, and receives the merchant service order, and completes the service processing process according to the merchant service order, where the merchant service order is generated and returned to the aggregation code service provider by the aggregation code service provider in response to the service order creation request and placing an order with the open platform corresponding to the application server. The first SPI interface and the second SPI interface are interfaces defined by the application service provider to which the application server belongs but implemented by the aggregation code service provider.

[0019] An intelligent watch aggregation code service processing device provided by one or more embodiments of this specification is applied to a payment server. The device includes:

[0020] A trigger receiving module that receives a service trigger instruction sent by the intelligent watch end by scanning the aggregation code displayed by the target merchant;

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

[0022] An execution receiving module that receives the service execution request sent by the intelligent watch end according to the information of the target merchant;

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

[0024] A service promotion module that receives the merchant service order generated and returned by the open platform in response to the order placement, and completes the service processing process according to the merchant service order.

[0025] An intelligent watch aggregation code service processing device provided by one or more embodiments of this specification is applied to the intelligent watch end. The device includes:

[0026] A scanning trigger module scans the aggregated code displayed by a target merchant and sends a service trigger instruction to an application server, so that the application server sends a merchant information query request to an aggregated code service provider by calling a first SPI interface according to the service trigger instruction;

[0027] An execution request module obtains the information of the target merchant queried by the aggregated code service provider, and sends a service execution request to the application server according to the information of the target merchant, so that the application server sends a corresponding merchant service order creation request to the aggregated code service provider by calling a second SPI interface according to the service execution request, and receives the merchant service order, and completes the service processing process according to the merchant service order. The merchant service order is generated and returned to the aggregated code service provider by the aggregated code service provider in response to the service order creation request and placing an order with the open platform corresponding to the application server. The first SPI interface and the second SPI interface are interfaces defined by the application service provider to which the application server belongs but implemented by the aggregated code service provider.

[0028] An intelligent watch aggregated code service processing device provided by one or more embodiments of this specification is applied to a payment server. The device includes:

[0029] At least one processor; and,

[0030] A memory communicatively connected to the at least one processor; wherein,

[0031] The memory stores instructions executable by the at least one processor. The instructions are executed by the at least one processor, so that the at least one processor can execute:

[0032] Receive a service trigger instruction sent by the intelligent watch end by scanning the aggregated code displayed by a target merchant;

[0033] According to the service trigger instruction, send a merchant information query request to the aggregated code service provider by calling a first SPI interface, so that the intelligent watch end obtains the information of the target merchant queried by the aggregated code service provider;

[0034] Receive a service execution request sent by the intelligent watch end according to the information of the target merchant;

[0035] According to the service execution request, by invoking the second SPI interface, send a corresponding merchant service order creation request to the aggregation code service provider, so that the aggregation code service provider places an order with the open platform corresponding to the application server. Among them, the first SPI interface and the second SPI interface are interfaces defined by the application service provider to which the application server belongs, but implemented by the aggregation code service provider;

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

[0037] An intelligent watch aggregation code service processing device provided by one or more embodiments of this specification is applied to the intelligent watch side. The device includes:

[0038] At least one processor; and,

[0039] A memory communicatively connected to the at least one processor; wherein,

[0040] The memory stores instructions executable by the at least one processor. The instructions are executed by the at least one processor so that the at least one processor can execute:

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

[0042] Obtain the information of the target merchant queried by the aggregation code service provider, and according to the information of the target merchant, send a service execution request to the application server, so that the application server, according to the service execution request, by invoking the second SPI interface, sends a corresponding merchant service order creation request to the aggregation code service provider, and receive the merchant service order, and complete the service processing process according to the merchant service order. Among them, the merchant service order is generated and returned to the aggregation code service provider by the aggregation code service provider in response to the service order creation request and placing an order with the open platform corresponding to the application server. The first SPI interface and the second SPI interface are interfaces defined by the application service provider to which the application server belongs, but implemented by the aggregation code service provider.

[0043] The above at least one technical solution adopted by one or more embodiments of this specification can achieve the following beneficial effects: By using an application service provider (represented by the application server) to define the SPI interface for querying and placing orders, and having one or more aggregator code service providers implement these SPI interfaces correspondingly, the interaction between the application service provider and the aggregator code service provider is standardized. Without relying on the H5 container, it has better stability compared to the H5 container-based solution, which helps improve the business success rate. Moreover, it reduces the access cost between the application service provider and the aggregator code service provider, and also gives the aggregator code service provider better flexibility, enabling the smart watch to still reliably and conveniently implement services such as payment based on the aggregator code even if it does not support the H5 container. Therefore, it has good applicability to smart watches and helps improve the user experience of smart watches. BRIEF DESCRIPTION OF THE DRAWINGS

[0044] In order to more clearly illustrate the technical solutions in the embodiments of this specification or the prior art, the following will briefly introduce the drawings required for use in the description of the embodiments or the prior art. Obviously, the drawings in the following description are only some embodiments recorded in this specification. For those of ordinary skill in the art, without creative efforts, other drawings can also be obtained based on these drawings.

[0045] Figure 1 It is a schematic flowchart of a method for processing aggregator code services on a smart watch provided by one or more embodiments of this specification;

[0046] Figure 2 It is a schematic flowchart of a call decision scheme for a first SPI interface provided by one or more embodiments of this specification;

[0047] Figure 3 It is a schematic flowchart of a control scheme for a watch face theme interface provided by one or more embodiments of this specification;

[0048] Figure 4 For one or more embodiments of this specification, in an application scenario Figure 1 It is a schematic flowchart of an implementation scheme of the method;

[0049] Figure 5 For one or more embodiments of this specification, in an application scenario Figure 4 Some schematic diagrams of the watch face display content on the smart watch side are involved in the solution;

[0050] Figure 6 It is a schematic flowchart of another method for processing aggregator code services on a smart watch provided by one or more embodiments of this specification;

[0051] Figure 7Schematic structural diagram of an intelligent watch aggregated code service processing device provided for one or more embodiments of this specification;

[0052] Figure 8 Schematic structural diagram of another intelligent watch aggregated code service processing device provided for one or more embodiments of this specification;

[0053] Figure 9 Schematic structural diagram of an intelligent watch aggregated code service processing device provided for one or more embodiments of this specification;

[0054] Figure 10 Schematic structural diagram of another intelligent watch aggregated code service processing device provided for one or more embodiments of this specification. Detailed implementation manners

[0055] Embodiments of this specification provide an intelligent watch aggregated code service processing method, device, equipment, and storage medium.

[0056] In order to enable those skilled in the art to better understand the technical solutions in this specification, the following will clearly and completely describe the technical solutions in the embodiments of this specification in conjunction with the accompanying drawings in the embodiments of this specification. Obviously, the described embodiments are only a part of the embodiments of this application, rather than all of the embodiments. Based on the embodiments of this specification, all other embodiments obtained by those of ordinary skill in the art without creative efforts shall fall within the scope of protection of this application.

[0057] The services described in this application are typically payment services, which are the target services that users need to perform. For the convenience of description, some of the following embodiments mainly use the scenario of payment services as an example for illustration. Of course, some other services with similar problems may also adopt the solutions of this application to solve, such as e-commerce services, event registration services, health service services, advertising services, etc.

[0058] As understood from the background technology, compared with smartphones, intelligent watches have more limited capabilities. For example, due to limitations in their operating system capabilities, it is difficult to implement an H5 container environment locally on an intelligent watch (intelligent watch manufacturers often remove this part of the H5 container function in order to improve the watch's operating efficiency and reduce resource consumption). Therefore, it is difficult to implement an aggregated code payment solution based on the H5 container. In this way, it is easy to cause intelligent watch payment failures. For payment service providers, this can further easily lead to the loss of users and payment services. Especially in the scenario of children's intelligent watches, children's intelligent watches are often the only mobile payment devices for children. If they fail to make an aggregated code payment using this device, it is very easy for them to be lost and difficult to recover, let alone bring about secondary payments. This is a pity for the platform and also a loss of improvement opportunities for users.

[0059] In view of the problems mentioned in the background art, in order to enable a smart watch to better support aggregated code payment, the applicant initially tried to create the following solution: The smart watch scans the aggregated code. When the scanning is successful, a H5 container is synchronously opened in the cloud, and at the same time, the aggregated code link is loaded in the container. When the smart watch user operates to input the amount and clicks to pay, the relevant operations are synchronized to the cloud. The cloud container can intercept the payment request and then return the order information to the smart watch side to promote the payment. However, it is found during testing that there are still problems with this solution, mainly including: The cloud container needs to adapt to various types of aggregated codes, identify the amount input and payment UI thereon, and intercept the corresponding operations. The compatibility is not good enough and the cost is relatively high.

[0060] In view of these above problems, the applicant created and provided in this application a more suitable aggregated code service processing solution for smart watches, such as an aggregated code payment solution, to solve these problems.

[0061] Based on such an overall situation, the solution of this application will be further described below.

[0062] Figure 1 It is a schematic flowchart of a method for processing an aggregated code service of a smart watch provided for one or more embodiments of this specification. The execution subject of this process may include an application server, which is the server corresponding to the smart watch side. At the software level, the smart watch side mainly refers to the software side for providing the target service (for example, a payment application client or a small program, etc. In this case, the application server is the payment server). Of course, at the hardware level, it is the smart watch mobile device itself.

[0063] The smart watch mentioned in this application has a hardware module 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 two-dimensional codes within the application.

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

[0065] S102: Receive a service trigger instruction sent by the smart watch side through scanning an aggregated code displayed by a target merchant.

[0066] An aggregated code, as a code, can support the same type of services of multiple different channels at the same time (of course, it also has the ability to support multiple different types of services at the same time). For example, a payment aggregated code supports different payment methods provided by two or more different payment service providers at the same time. When the user scans the code, the payment method corresponding to the application used for scanning can be automatically recognized. Currently, the aggregated code is mainly still presented in the form of a two-dimensional code and may also evolve into a higher-dimensional code in the future.

[0067] Different merchants have their own proprietary aggregation codes, which can be pre-generated with the support of the aggregation code service provider and presented to users for scanning and use. The aggregation code service provider can master the correct correspondence between different aggregation codes and different merchants.

[0068] The user scans and identifies the aggregation code presented by the target merchant through the code scanning function provided in a certain application client or applet on the smart watch side, and sends a service trigger instruction to the corresponding application server according to the scanning and identification result.

[0069] In one or more embodiments of this 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, and then 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.

[0070] It should be noted that the merchant mentioned in this application can be understood as a broader concept. A merchant is a subject that uses the platform of the application service provider to provide services to users. In addition to the merchants selling goods in the common e-commerce scenarios, the subjects that use the platform to organize other activities for users, or provide non-commodity services, or conduct management and assessment can also be broadly regarded as merchants from the perspective of the application service provider.

[0071] S104: According to the service trigger instruction, send a merchant information query request to the aggregation code service provider by calling the first SPI interface, so that the smart watch side can obtain the information of the target merchant queried by the aggregation code service provider.

[0072] In one or more embodiments of this specification, the SPI interface mentioned in this application, that is, the service supply interface, is defined at the interface level by the application service provider, but at the implementation level, it is on the side of the independent software developer or merchant cooperating with the application service provider. In the aggregation code scenario, specifically, it is implemented by the aggregation code service provider. In this way, for the same SPI interface defined by the application service provider, different aggregation code service providers can implement it differently according to their actual needs, with good compatibility, which helps to efficiently access more aggregation code service providers without the need for the application service provider to frequently change. Therefore, from the perspective of the application service provider, it is sufficiently standardized and shields these differences for the user side.

[0073] The first SPI interface can be mainly used to request and query information of a target merchant, that is, it can be used as a merchant information query interface. The information of the target merchant obtained by the aggregator code service provider can be directly returned by the aggregator code service provider to the smart watch side, or indirectly returned to the smart watch side through the application server for transit. It should be noted that there may not be only one first SPI interface, and it can also be a set composed of multiple SPI interfaces. Each SPI interface in the set can be responsible for more refined functions. For example, there can be a first SPI interface for initiating a merchant information query request, and there can also be another first SPI interface for returning the merchant information query result, and so on.

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

[0075] The smart watch side displays a confirmation interface to the user according to the information of the target merchant. The confirmation interface can prompt what specific merchant is currently targeted, such as the merchant name, merchant LOGO, etc. Of course, the services of this merchant can also be described, such as the information of the goods to be paid, the amount to be paid, etc. The user can perform a confirmation operation on the confirmation interface (more specific service selection functions can also be provided to the user so that the user can confirm which service to execute among multiple selectable services), thereby triggering the smart watch side to send a service execution request to the application server.

[0076] In one or more embodiments of this specification, the smart watch may not support the H5 container, and may even not support the H5 page. In this case, the solution of this application can especially reflect its advantages compared with the prior art. In this case, the confirmation interface does not belong to the page in the H5 container, and may not even belong to the H5 page.

[0077] Further, considering that the application server can shield the differences in the implementation of interfaces by different aggregator code service providers through the SPI interface (for example, differences in input and output parameters, data formats, field meanings, compliance requirements, algorithms used, etc.), it is also possible to make the confirmation interface presented more standardly. In this case, the confirmation interface may not be a page or interface obtained from the aggregator code service provider, thus reducing the implementation cost of the aggregator code service provider and also helping to avoid possible compatibility issues between the confirmation interface and the smartwatch side. At the same time, considering the case of supporting both the direct return of merchant information and the indirect return of merchant information by the aggregator code service provider, the smartwatch side can be generated locally according to the information of the target merchant instead of a page obtained from the application server. In this way, the smartwatch side can more flexibly adapt to its own capabilities to generate a confirmation interface, especially a page with a more concise form suitable for display and viewing on the smartwatch. From the perspective of the application service provider, such an operation is also more standardized and takes into account personalization, and can avoid being overly restricted by the aggregator code service provider or the application server.

[0078] S108: According to the service execution request, send a corresponding merchant service order creation request to the aggregator code service provider by calling the second SPI interface, so that the aggregator code service provider places an order with the open platform corresponding to the application server. Among them, the first SPI interface and the second SPI interface are interfaces defined by the application service provider to which the application server belongs but implemented by the aggregator code service provider.

[0079] Refer to the previous first SPI interface to understand the second SPI interface similarly. The main difference between the two lies in their uses. The second SPI interface is mainly used for creating merchant service orders.

[0080] The service execution request sent by the smartwatch side can also be regarded as a kind of order placement operation. Here, the order placement (for the sake of distinction, called user order placement) is for the user of the smartwatch for the merchant, while the merchant service order is for the merchant (or executed by the aggregator code service provider on behalf of the merchant) for the service provider. The service provider is a third party between the user and the merchant, providing a service platform for these two parties. User order placement is used by the user to request a service, and the merchant service order is based on providing the service corresponding to the service, requesting to obtain corresponding benefits (usually paid by the user). For example, in a payment scenario, the user order placement can be to pay an order for the merchant service, and the merchant service order can be the merchant's cash register receipt. It can be seen that these two order placement operations are corresponding and unified, and essentially belong to the same business transaction.

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

[0082] S110: Receive the merchant business order generated and returned by the open platform in response to the order placement, and advance the business processing process to completion according to the merchant business order.

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

[0084] By Figure 1 the method, the application service provider (represented by the application service side) defines the SPI interface for querying and placing orders, and one or more aggregator code service providers correspondingly implement these SPI interfaces. This standardizes the interaction between the application service provider and the aggregator code service provider, does not rely on the H5 container, has better stability than the H5 container-based solution, helps to improve the business success rate, and reduces the access cost between the application service provider and the aggregator code service provider. It also gives the aggregator code service provider better flexibility, enabling the smart watch to reliably and conveniently implement services such as payment based on the aggregator code even if it does not support the H5 container. Therefore, it has good applicability to smart watches and helps to improve the user experience of smart watches.

[0085] Based on Figure 1 the method, this specification also provides some specific implementation schemes and extended schemes of this method, which will be further described below.

[0086] According to the principle of the above solution, one or more embodiments of this specification provide a schematic flow diagram of a call decision scheme for a first SPI interface. See Figure 2 .

[0087] Figure 2 The process in

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

[0089] In the case of not supporting the H5 container, a solution based on the SPI interface is preferred. If the H5 container is supported, then switching to a solution based on the H5 container and service interception can be considered.

[0090] For the convenience of judgment, the service trigger instruction may carry the capability information of the smartwatch. Of course, if the type of the sending device can be determined according to the service trigger instruction, a more concise judgment can also be made, and in this way, the efficiency is better. For example, according to the service trigger instruction, determine whether the sending device is a smartwatch or a smartphone. If it is a smartwatch, then continue to execute the subsequent steps.

[0091] S204: If not, then according to the service trigger instruction, send a merchant information query request carrying the code value of the aggregation code and the identifier of the smartwatch to the aggregation code service provider by calling the first SPI interface, 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 smartwatch according to the identifier of the smartwatch.

[0092] If the aggregation code service provider indirectly returns the information of the target merchant to the smartwatch through the application server, the merchant information query request may not carry the identifier of the smartwatch.

[0093] In the case where the smartwatch does not support the H5 container, or even does not support the H5 interface, for the confirmation interface, the present application considers not using a separate additional page, but using the watch face theme (at least including the desktop of the smartwatch) for display. In this way, it can clearly and unobtrusively prompt the user, and it is convenient for persistent accumulation and dynamic display of the business situation of the user within a period of time, without entering specific business applications, and the processing resources occupied are small.

[0094] Based on such an idea, one or more embodiments of this specification provide a flow schematic diagram of a watch face theme interface control solution. Refer to Figure 3 .

[0095] Figure 3 The process in

[0096] S302: Define the dial theme feature parameters for the first SPI interface in advance. 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 presented by the assigned dial theme feature parameters and returned to the smart watch end through the first SPI interface (directly returned by the aggregation code service provider or indirectly returned through the application server).

[0097] The dial theme feature parameters can include, for example, control layout, desktop, style, icons, text, etc. For the merchant information of different merchants, different dial theme feature parameters can be assigned differently. After assignment, it can reflect the merchant and / or the current business to be carried out from one or more of the above parameter dimensions, so that users can understand it intuitively.

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

[0099] In one or more embodiments of this 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, users can clearly perceive that they are currently in the service interaction process with the corresponding merchant, and can more clearly feel which merchant it is currently, which is also helpful for promoting the merchant. In this case, users can stay on the desktop on the smart watch without having to display a separate page covering the desktop, with low resource consumption and no impact on other operations performed by users during this period. The temporary dial theme interface can be attached with controls for performing confirmation operations, such as a certain icon on the desktop, or even the physical buttons or knobs on the smart watch can be directly used as confirmation buttons or knobs.

[0100] S306: After the business processing process of the merchant business form is completed, send a dial theme interface restoration instruction to the smart watch end to enable the smart watch end to switch back from the temporary dial theme interface to the default dial theme interface.

[0101] Similarly, the smart watch end can also automatically switch and restore the dial theme interface, without necessarily being triggered by the application server.

[0102] In one or more embodiments of the present specification, the default watch face theme interface can be dynamically updated accordingly based on the user's business operations with different merchants on the smart watch, so as to display (for example, on a daily basis, display all the merchants involved on that day) the situations of these merchants. In this way, the default watch face theme interface itself is equivalent to an accumulated merchant interaction record poster, which can be continuously displayed on the smart watch for easy viewing, and such continuity does not consume additional processing resources, improving the actual value of the watch face theme for users.

[0103] In this case, in step S306, the switched-back default watch face theme interface can be obtained by updating the previous default watch face theme interface (adding the situation of the current merchant) based on the temporary watch face theme interface.

[0104] Furthermore, for the default watch face theme interface dynamically updated based on merchant information, the user can select different modes for presentation according to needs. For example, if the user pays more attention to information volume, the "information mode" is adopted for presentation to more clearly reflect the merchant information involved. If the user pays more attention to aesthetics, the "artistic mode" is adopted for presentation. In this case, the merchant information can be presented after being blurred and artistically processed, with reduced intuitiveness, but it may be more aesthetically pleasing.

[0105] In addition, even after the business is completed, according to the user's needs, the temporary watch face theme interface can continue to be used instead of necessarily switching back.

[0106] Based on the above description, for the sake of easy understanding, taking the application scenario of payment business as an example, one or more embodiments of the present specification provide a Figure 1 flow schematic diagram of an implementation scheme of the method in this scenario, see Figure 4 .

[0107] In this scenario, the above-mentioned application server is specifically a payment server (the application is specifically a payment application), the smart watch end is specifically a payment client, the application service provider is specifically a payment service provider, the business execution request is specifically a payment request, and the merchant business form is specifically a merchant cash register form.

[0108] For Figure 4 the solution in, preparatory work needs to be carried out in advance. This includes defining two SPI interfaces, which are respectively used to query merchant information and create a merchant cash register form in the scenario of creating an aggregated code. These two interfaces are implemented by the aggregated code service provider and serve as the above-mentioned first SPI interface and second SPI interface. The entire process is also mainly divided according to the work involved in these two interfaces.

[0109] Regarding querying merchant information, the main logic includes: The user opens the payment client on the smart watch and scans the aggregated code displayed by the current merchant. After that, it will trigger the payment server to call the first SPI interface to pass relevant information such as the merchant aggregated code value to the aggregated code service provider. The aggregated code service provider then queries merchant information such as the merchant name, merchant logo, merchant ID, payment amount, etc. corresponding to the code based on this information, and then passes this information back to the payment client through the first SPI interface. After receiving this information, the payment client renders and displays the confirmation interface corresponding to the merchant for the user to confirm and check the merchant information, and then confirm it if it is correct.

[0110] Regarding the merchant cashier receipt in the scenario of the aggregated code, the main logic includes: The user clicks the confirmation in the confirmation interface corresponding to the merchant. After that, it will trigger the payment server to call the second SPI interface to pass information such as the paying user and payment amount to the aggregated code service provider. The aggregated code service provider can then place an order on the open platform of the payment service provider based on this information to obtain the merchant cashier receipt. After the order placement is completed, relevant information such as the order number is passed back to the payment server through the second SPI interface. After receiving the order information, the payment server can initiate and complete the payment.

[0111] Intuitively, one or more embodiments of this specification also provide a solution in an application scenario Figure 4 involving some schematic diagrams of the display content on the smart watch end. Please refer to Figure 5 .

[0112] Figure 5 It contains five sub - diagrams. In the order from left to right and top to bottom, the first sub - diagram shows prompting the user to scan the QR code. Assuming the user scans the aggregated code displayed by a certain merchant, then a confirmation interface is rendered and displayed locally, as shown in the second sub - diagram. This is a simple page for the smart watch, rather than an H5 page in an H5 container. For example, it contains the name of the merchant "XX Grocery Store". The user can click the "Pay him" button, then enter the interface in the third sub - diagram, which shows that the payment amount can be manually specified when initiating the payment. After confirming the payment amount, enter the interface in the fourth sub - diagram, where the user can further click the "Confirm payment" button to place an order and initiate the payment. After the payment process is completed, enter the interface in the fifth sub - diagram, which prompts the user that the payment is successful. The entire display process and content are clear, consume less resources, are very friendly to the smart watch, and are also convenient for users to understand and operate.

[0113] Through Figure 4The solution, based on the SPI interface defined for querying merchant information and creating an aggregated cashier receipt and implemented by the aggregated code service provider, avoids compatibility issues and effectively improves the stability and success rate of aggregated code payment. Compared with the aggregated code payment solution based on the H5 container, it has better stability and a higher payment success rate, which helps the connected aggregated code service providers and effectively retains more users, especially children's smartwatch users.

[0114] The above mainly describes from the perspective of the application server. Based on the same idea, one or more embodiments of this specification also provide another method for processing the aggregated code service of smartwatches, which is described from the perspective of the smartwatch side. Figure 6 It is a schematic flowchart of the other method.

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

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

[0117] S604: Obtain the information of the target merchant queried by the aggregated code service provider, and according to the information of the target merchant, send a service execution request to the application server, so that the application server, according to the service execution request, sends a corresponding merchant service order creation request to the aggregated code service provider by calling the second SPI interface, and receive the merchant service order, and complete the service processing process according to the merchant service order. Among them, the merchant service order is generated and returned to the aggregated code service provider by the aggregated code service provider in response to the service order creation request and placing an order with the open platform corresponding to the application server. 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 aggregated code service provider.

[0118] Specifically, it can be understood by referring to the previous description and will not be elaborated here.

[0119] Based on the same idea, one or more embodiments of this specification also provide the corresponding device and equipment for the above method, as Figures 7 - 10 shown. The device and equipment can correspondingly execute the above method and related optional solutions.

[0120] The trigger receiving module 702 receives the service trigger instruction sent by the smartwatch side by scanning the aggregated code displayed by the target merchant;

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

[0122] The execution receiving module 706 receives the service execution request sent by the smart watch terminal according to the information of the target merchant;

[0123] The second calling module 708, according to the service execution request, sends a corresponding merchant service order creation request to the aggregation code service provider by calling the second SPI interface, so that the aggregation code service provider places an order with the corresponding open platform of the application server. Among them, the first SPI interface and the second SPI interface are interfaces defined by the application service provider to which the application server belongs, but implemented by the aggregation code service provider;

[0124] The service promotion module 710 receives the merchant service order generated and returned by the open platform in response to the order placement, and completes the service processing process according to the merchant service order.

[0125] 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 terminal 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.

[0126] Optionally, before 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 service trigger instruction, it judges whether the smart watch terminal supports the H5 container according to the service trigger instruction, and determines that the result of the judgment is no.

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

[0128] Among them, the confirmation interface does not belong to the page in the H5 container.

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

[0130] Optionally, the first SPI interface defines the feature parameters of the watch face theme, which are used by the aggregation code service provider to assign values according to the queried merchant information. The information of the target merchant is presented by the assigned feature parameters of the watch face theme and returned to the smart watch terminal through the first SPI interface.

[0131] The execution receiving module 706 receives the service execution request sent by the smart watch terminal in response to the confirmation operation performed on the temporary watch face theme interface serving as the confirmation interface, where the temporary watch face theme interface is generated according to the assigned feature parameters of the watch face theme and automatically switched from the default watch face theme interface for use.

[0132] Optionally, after the merchant service order completes the service processing process, the service promotion module 710 sends a watch face theme interface restoration instruction to the smart watch terminal, so that the smart watch terminal switches back from the temporary watch face theme interface to the default watch face theme interface.

[0133] Optionally, the open platform is a platform provided for the application service provider and is used for the aggregation code service provider or the merchant to place an order. The open platform and the application service terminal are different entities.

[0134] Optionally, the application service terminal includes a payment service terminal, the application service provider includes a payment service provider, the service execution request includes a payment request, and the merchant service order includes a merchant cashier order.

[0135] Figure 8 The following is a schematic structural diagram of another smart watch aggregation code service processing device provided for one or more embodiments of this specification. The device is applied to the smart watch terminal and includes:

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

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

[0138] Figure 9 FIG. is a schematic structural diagram of an intelligent watch aggregation code service processing device provided by one or more embodiments of the present specification. The device is applied to a payment server, and the device includes:

[0139] At least one processor; and,

[0140] A memory communicatively connected to the at least one processor; wherein,

[0141] The memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor, so that the at least one processor can execute:

[0142] Receive a service trigger instruction sent by the intelligent watch end by scanning the aggregation code displayed by the target merchant;

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

[0144] Receive the service execution request sent by the intelligent watch end according to the information of the target merchant;

[0145] According to the service execution request, send a corresponding merchant service order creation request to the aggregation code service provider by calling the second SPI interface, so that the aggregation code service provider places an order with the open platform corresponding to the application server. The first SPI interface and the second SPI interface are interfaces defined by the application service provider to which the application server belongs, but implemented by the aggregation code service provider;

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

[0147] Figure 10 A structural schematic diagram of another intelligent watch aggregation code service processing device provided for one or more embodiments of this specification. The device is applied to the intelligent watch side, and the device includes:

[0148] At least one processor; and,

[0149] A memory communicatively connected to the at least one processor; wherein,

[0150] The memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor so that the at least one processor can execute:

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

[0152] Obtain the information of the target merchant queried by the aggregation code service provider, and according to the information of the target merchant, send a service execution request to the application server, so that the application server, according to the service execution request, sends a corresponding merchant service order creation request to the aggregation code service provider by calling the second SPI interface, and receive the merchant service order, and complete the service processing process according to the merchant service order, wherein the merchant service order is generated and returned to the aggregation code service provider by the aggregation code service provider in response to the service order creation request and placing an order with the open platform corresponding to the application server. The first SPI interface and the second SPI interface are interfaces defined by the application service provider to which the application server belongs but implemented by the aggregation code service provider.

[0153] Based on the same idea, one or more embodiments of this specification also provide a non-volatile computer storage medium, which is applied to the payment server. The medium stores computer-executable instructions, and the computer-executable instructions are set to:

[0154] Receive a service trigger instruction sent by the intelligent watch side by scanning the aggregation code displayed by the target merchant;

[0155] According to the service trigger instruction, send a merchant information query request to the aggregation code service provider by calling the first SPI interface, so that the intelligent watch side can obtain the information of the target merchant queried by the aggregation code service provider;

[0156] Receive the service execution request sent by the intelligent watch side according to the information of the target merchant;

[0157] According to the business execution request, by invoking the second SPI interface, send a corresponding merchant service order creation request to the aggregation code service provider, so that the aggregation code service provider places an order with the open platform corresponding to the application server. Among them, the first SPI interface and the second SPI interface are interfaces defined by the application service provider to which the application server belongs, but implemented by the aggregation code service provider;

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

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

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

[0161] Obtain the information of the target merchant queried by the aggregation code service provider, and according to the information of the target merchant, send a business execution request to the application server, so that the application server, according to the business execution request, by invoking the second SPI interface, sends a corresponding merchant service order creation request to the aggregation code service provider, and receive the merchant service order, and complete the business processing process according to the merchant service order. Among them, the merchant service order is generated and returned to the aggregation code service provider by the aggregation code service provider placing an order with the open platform corresponding to the application server in response to the service order creation request. The first SPI interface and the second SPI interface are interfaces defined by the application service provider to which the application server belongs, but implemented by the aggregation code service provider.

[0162] In the 1990s, it was obvious to distinguish whether an improvement in a technology was a hardware improvement (e.g., improvement in circuit structures such as diodes, transistors, switches, etc.) or a software improvement (improvement in method flows). However, with the development of technology, many method flow improvements today can be regarded as direct improvements in hardware circuit structures. Almost all designers obtain the corresponding hardware circuit structure by programming the improved method flow into the hardware circuit. Therefore, it cannot be said that an improvement in a method flow cannot be implemented with a hardware entity module. 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 programming the device. The designer can program by himself to "integrate" a digital system on a PLD, without having to ask a chip manufacturer to design and fabricate a dedicated integrated circuit chip. Moreover, nowadays, instead of manually fabricating integrated circuit chips, this programming is mostly implemented using "logic compiler" software, which is similar to the software compiler used in program development and writing. The original code before compilation also has to be written in a specific programming language, which is called Hardware Description Language (HDL). And 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. Currently, the most commonly used are VHDL (Very-High-Speed Integrated Circuit Hardware Description Language) and Verilog. Those skilled in the art should also be aware that by simply making a little logical programming of the method flow with the above-mentioned several hardware description languages and programming it into the integrated circuit, it is easy to obtain the hardware circuit that implements the logical method flow.

[0163] The controller can be implemented in any suitable manner. For example, the controller can take the form of, for example, a microprocessor or a processor and a computer-readable medium storing computer-readable program code (such as software or firmware) executable by the (micro)processor, logic gates, switches, an application specific integrated circuit (ASIC), a programmable logic controller, and an embedded microcontroller. Examples of the controller include, but are not limited to, the following microcontrollers: ARC 625D, Atmel AT91SAM, Microchip PIC18F26K20, and Silicone Labs C8051F320. The memory controller can also be implemented as part of the control logic of the memory. Those skilled in the art also know that, in addition to implementing the controller in the form of pure computer-readable program code, it is entirely possible to make the controller implement the same function in the form of logic gates, switches, application specific integrated circuits, programmable logic controllers, and embedded microcontrollers by logically programming the method steps. Therefore, such a controller can be considered a hardware component, and the devices included therein for implementing various functions can also be regarded as the structures within the hardware component. Or even, the devices for implementing various functions can be regarded as either software modules for implementing the method or the structures within the hardware component.

[0164] The systems, devices, modules, or units illustrated in the above embodiments can be specifically implemented by computer chips or entities, or by products with certain functions. A typical implementation device is a computer. Specifically, the computer can 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 any combination of these devices.

[0165] For the convenience of description, when describing the above devices, they are described separately as 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.

[0166] Those skilled in the art should understand that the embodiments of this specification can be provided as a method, a system, or a computer program product. Therefore, the embodiments of this specification can take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware aspects. Moreover, the embodiments of this specification can take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk memories, CD-ROMs, optical memories, etc.) containing computer-usable program code.

[0167] This specification is described with reference to the flowcharts and / or block diagrams of methods, apparatuses (systems), and computer program products according to embodiments of the specification. It should be understood that each flow and / or block in the flowchart and / or block diagram, and combinations of flows 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 the processors of general-purpose computers, special-purpose computers, embedded processors, or other programmable data processing devices to generate a machine, such that the instructions executed by the processors of the computer or other programmable data processing devices produce means for implementing the functions specified in one process Figure 1 one process or multiple processes and / or blocks Figure 1 or means for implementing the functions specified in multiple blocks.

[0168] These computer program instructions can also be stored in a computer-readable memory that can direct a computer or other programmable data processing device to work in a specific manner, such that the instructions stored in the computer-readable memory produce a manufactured article including instruction means that implement the functions specified in one process Figure 1 one process or multiple processes and / or blocks Figure 1 or means for implementing the functions specified in multiple blocks.

[0169] These computer program instructions can also be loaded onto a computer or other programmable data processing device, such that a series of operation steps are executed on the computer or other programmable device to generate a computer-implemented process, so that the instructions executed on the computer or other programmable device provide steps for implementing the functions specified in one process Figure 1 one process or multiple processes and / or blocks Figure 1 or means for implementing the functions specified in multiple blocks.

[0170] In a typical configuration, a computing device includes one or more processors (CPUs), an input / output interface, a network interface, and memory.

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

[0172] 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.

[0173] 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.

[0174] 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.

[0175] 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.

[0176] The specific embodiments of this specification have been described above. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recited in the claims may be performed in a different order than in the embodiments and still achieve the desired result. Additionally, the processes depicted in the figures do not necessarily require the particular order or sequential order shown to achieve the desired result. In certain embodiments, multitasking and parallel processing are also possible or may be advantageous.

[0177] The above description is only for one or more embodiments of this specification and is not intended to limit this specification. For those skilled in the art, various changes and modifications can be made to one or more embodiments of this specification. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principles of one or more embodiments of this specification shall be included within 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 to promote the completion of the business processing process, wherein the first SPI interface and the second SPI interface are defined by the application service provider to which the application server belongs, and at the implementation level, are on the independent software developer or merchant side cooperating with the application service provider.

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 process of advancing the business 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 according to claim 8, wherein sending a corresponding merchant business order creation request to the aggregation code service provider specifically comprises: Sending a corresponding merchant business order creation request 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; The process of advancing the business processing is completed, specifically including: Receiving a merchant service order generated and returned by the open platform in response to the order, and completing the service processing process according to the merchant service order; 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; The target merchant information queried by the aggregation code service provider is obtained, and a business execution request is sent to the application server according to the target merchant information, 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, so as to promote the completion of the business processing process. The first SPI interface and the second SPI interface are defined by the application service provider to which the application server belongs. At the implementation level, they are on the independent software developer or merchant side cooperating with the application 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, according to the business execution request, sends a corresponding merchant business order creation request to the aggregation code service provider by calling the second SPI interface, so as to promote the completion of the business processing process, wherein the first SPI interface and the second SPI interface are defined by the application service provider to which the application server belongs, and at the implementation level, are on the independent software developer or merchant side cooperating with the application service provider.

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 promotion process 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 according to claim 18, wherein the second calling module sends a corresponding merchant business order creation request 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; The process of advancing the business processing is completed, specifically including: Receiving a merchant service order generated and returned by the open platform in response to the order, and completing the service processing process according to the merchant service order; 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; The 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, so as to promote the completion of the business processing process. The first SPI interface and the second SPI interface are defined by the application service provider to which the application server belongs. At the implementation level, they are on the independent software developer or merchant side cooperating with the application 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 to promote the completion of the business processing process, wherein the first SPI interface and the second SPI interface are defined by the application service provider to which the application server belongs, and at the implementation level, are on the independent software developer or merchant side cooperating with the application service provider.

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; The target merchant information queried by the aggregation code service provider is obtained, and a business execution request is sent to the application server according to the target merchant information, 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, so as to promote the completion of the business processing process. The first SPI interface and the second SPI interface are defined by the application service provider to which the application server belongs. At the implementation level, they are on the independent software developer or merchant side cooperating with the application service provider.

Images