A processing method, system and related apparatus

Abstract

The application relates to the technical field of terminals, and discloses a processing method, a system and related devices. A first fusion card is displayed, the first fusion card comprising a first commodity combination, the first commodity combination comprising a plurality of commodities, and the plurality of commodities belonging to different merchant platforms; a first input to the first fusion card is received; after the first input is received, a first payment request is generated, and settlement processing of the first commodity combination is triggered based on the first payment request. In this way, the first electronic device can display a commodity combination comprising commodities of a plurality of merchant platforms, meet the demand of a user for quickly purchasing a plurality of commodities across platforms, reduce the payment steps of the user for purchasing commodities of a plurality of merchant platforms, and the operation is more convenient.

Description

Technical Field

[0001] This application relates to the field of terminal technology, and in particular to a processing method, system and related apparatus. Background Technology

[0002] With the continuous development of communication technology, electronic devices (such as smartphones) are becoming increasingly common and diverse. The usability and user-friendliness of the human-computer interaction interface (HCI) for these devices are receiving increasing attention. Electronic devices can display shopping card components (also known as cards) on the desktop, the negative one screen, etc. Users can click on these card components to trigger the electronic device to display the corresponding product selection interface, facilitating product selection.

[0003] However, the various shopping card components are independent of each other, and the payment path is complex, which cannot meet the user's needs. Summary of the Invention

[0004] This application provides a processing method, system, and related apparatus that combines products from multiple merchant platforms to enable users to purchase multiple products at once, reducing the payment steps required for users to purchase products from multiple merchant platforms, making the shopping process more convenient, and meeting the diverse shopping needs of users.

[0005] In a first aspect, this application provides a processing method applied to a first electronic device, the method comprising: displaying a first integrated card, the first integrated card including a first product combination, the first product combination including multiple products, the multiple products being sourced from multiple merchant platforms; receiving a first input to the first integrated card; and, upon receiving the first input, paying for and purchasing the first product combination.

[0006] In this way, the first electronic device can meet users' needs for quickly purchasing multiple products across platforms, reducing the payment steps for users to purchase products from multiple merchant platforms, making the operation more convenient and providing a better user experience.

[0007] In one possible implementation, upon receiving the first input, a first payment request is generated, and settlement processing for the first product combination is triggered based on the first payment request. This includes: responding to the first input by displaying a payment interface, which includes the first product combination and payment controls; receiving a second input to the payment controls; responding to the second input by generating the first payment request; and triggering settlement processing for the first product combination based on the first payment request. In this way, the first electronic device can directly jump to the payment page for the first product combination upon responding to the first input, reducing operational steps, simplifying the shopping process, and improving the user's shopping experience.

[0008] In one possible implementation, displaying the first fusion card includes: obtaining configuration data of a first product combination from a first server; wherein the configuration data of the first product combination includes one or more of the following: a first display style of the first product combination and content data of all products in the first product combination, the content data including one or more of the following: product name, product category, product description, product price, product inventory, and product image; and displaying the first fusion card based on the configuration data of the first product combination. In this way, the first electronic device can obtain the configuration data of the product combination from the first server, facilitating the display of the fusion card used to purchase the product combination by the first electronic device.

[0009] In one possible implementation, a first payment request is generated, and settlement processing for the first product combination is triggered based on the first payment request. This includes sending the first payment request to a first server. The first payment request indicates that the first electronic device has purchased the first product combination and instructs the first server to transfer the payment for the first product combination from a first payment account associated with the user logged into the first electronic device to a first receiving account indicated by the first server. In this way, since the first product combination includes goods from multiple different merchant platforms, transferring payments through the first payment account allows for unified fund management, making the payment process more secure and reliable.

[0010] In one possible implementation, the method further includes: displaying multiple candidate cards, including a first candidate card and a second candidate card, where the first candidate card is used to purchase a third item and the second candidate card is used to purchase a fourth item; receiving a third input indicating that the first and second candidate cards have been selected; responding to the third input, displaying a second merged card, which includes a second product combination, comprising the third and fourth items; receiving a fourth input to the second merged card; and upon receiving the fourth input, generating a second payment request, and triggering settlement processing for the second product combination based on the second payment request. In this way, users can combine items from multiple merchant platforms into a product combination for quick and efficient purchase.

[0011] In one possible implementation, displaying multiple candidate cards includes: obtaining configuration data for multiple candidate products from a first server, the multiple candidate products including a third product and a fourth product; and displaying multiple candidate cards based on the configuration data for the multiple candidate products.

[0012] Secondly, this application provides a processing method applied to a first server. The method includes: sending configuration data of a first product combination to a first electronic device, the first product combination including multiple products belonging to multiple merchant platforms, the configuration data of the first product combination being used by the first electronic device to display a first integrated card; receiving a first payment request sent by the first electronic device, the first payment request indicating that the first electronic device is purchasing the first product combination; after receiving the first payment request, obtaining payment for the first product combination from a first payment account associated with the user logged into the first electronic device, and using the payment to settle accounts with the multiple merchant platforms for the products in the first product combination. In this way, the first server can link multiple merchant platforms, assisting the first electronic device in quickly purchasing multiple products from different merchant platforms.

[0013] In one possible implementation, multiple merchant platforms include a first merchant platform. Before sending configuration data for the first product combination to the first electronic device, the method further includes: receiving a first query request sent by the first merchant platform; sending a first product list to the first merchant platform, the first product list including products in the first product combination; and receiving the first product combination sent by the first merchant platform. In this way, merchant platforms can set up product combinations themselves, making it easier for them to bundle suitable products for group sales and increase the probability of product sales.

[0014] In one possible implementation, after receiving the first product combination sent by the first merchant platform, the method further includes: receiving a first display style for the first merchant combination sent by the first merchant platform. The first display style indicates whether to display one or more of the following when displaying the first product combination: whether to display the product package details, whether to display product coupons, and whether to display the product name. The configuration data for the first product combination includes the first display style. In this way, the merchant platform can determine how the product combination is displayed on the customer's logged-in electronic device, resulting in more diverse display effects.

[0015] In one possible implementation, before sending the configuration data of the first product combination to the first electronic device, the method further includes: receiving detailed data of one or more products uploaded by a first merchant platform, wherein the one or more products include at least one product in the first product combination, and the detailed data includes a product identifier and a merchant platform identifier, the merchant platform identifier indicating the merchant platform to which the product belongs. In this way, the merchant platform can independently decide which products to upload to the first server, facilitating the promotion of products that are easy to combine for sale.

[0016] In one possible implementation, after receiving the details of one or more products uploaded by a first merchant platform, the method further includes: receiving first permission information sent by the first merchant platform, the first permission information indicating which merchant platforms are allowed to add products from the first merchant platform to the product portfolio; and sending a first product list to the first merchant platform, including: determining the first product list based on the merchant platform identifier of the first merchant platform and the permission information of the products stored on the first server, the first product list including products that are allowed to be added to the product portfolio by the first merchant platform. In this way, merchant platforms can set permission information for uploaded products to specify which merchant platforms can add products to the product portfolio, thus preventing unwanted merchant platforms from using uploaded products.

[0017] In one possible implementation, before receiving the first product combination sent by the first merchant platform, the method further includes: receiving a first payment agreement signing request sent by the first merchant platform, the first payment agreement signing request being used to set the first server to distribute the payment for the products belonging to the first merchant platform in the product combination to the first merchant platform; storing a first payment binding relationship, the first payment binding relationship being used to indicate the first receiving account associated with the first server and the second receiving account of the first merchant platform, and to instruct the first server to transfer the payment for the products in the first merchant platform from the first payment account to the second receiving account through the first receiving account. In this way, by determining the payment binding relationship in advance, the first server can facilitate the settlement processing of the products.

[0018] In one possible implementation, sending configuration data for a first product combination to a first electronic device includes: filtering one or more product combinations from a stored pool of product combinations based on user data of the first electronic device, wherein the one or more product combinations include the first product combination; wherein the user data includes one or more of a user identifier and the location of the first electronic device; and sending the configuration data for the one or more product combinations to the first electronic device. In this way, the first server can recommend products that better suit the user's purchasing needs based on the user data.

[0019] In one possible implementation, one or more product combinations include one or more of the following: products purchased by the first electronic device, products located near the first electronic device's location, and so on. This allows for the recommendation of product combinations that include previously purchased items, as well as combinations that include items more convenient for offline pickup, making the recommended products more aligned with the user's shopping needs and improving the user experience.

[0020] In one possible implementation, the first product combination includes first products from a first merchant platform. Payment for the first product combination is obtained from a first payment account associated with a user logged into the first electronic device. This payment is then used to settle accounts with multiple merchant platforms for the products within the first product combination. This includes: transferring payment for the first product combination from the first payment account to a first receiving account indicated by the first server; and transferring payment for the first products from the first receiving account to a second receiving account indicated by the first merchant platform. Thus, since the first product combination includes products from multiple different merchant platforms, transferring payments through the first payment account allows for unified fund management, making the payment process more secure and reliable.

[0021] In one possible implementation, the first payment request carries a first payment account and a first product combination identifier; transferring the payment for the first product combination from the first payment account to a first receiving account indicated by the first server includes: determining the payment binding relationship of all products in the first product combination based on the first product combination identifier, the payment binding relationship being used to indicate the first receiving account associated with the first server and the receiving account of the merchant platform to which the products belong, and being used to instruct the first server to allocate the payment for the products from the payment account to the receiving account of the merchant platform through the first receiving account; the payment binding relationship of the first product being used to indicate the second receiving account of the first merchant platform; after determining the payment binding relationship of all products in the first product combination, transferring the payment for the first product combination from the first payment account to the first receiving account; transferring the payment for the first product from the first receiving account to the second receiving account indicated by the first merchant platform includes: after transferring the payment for the first product combination from the first payment account to the first receiving account, transferring the payment for the first product from the first receiving account to the second receiving account. In this way, the transfer path of funds can be determined through pre-set payment binding relationships, making it convenient for the first electronic device to purchase goods from multiple merchant platforms at once.

[0022] In one possible implementation, the method further includes: sending configuration data of multiple candidate products to a first electronic device, the multiple candidate products including a third product and a fourth product; receiving a first fusion request from the first electronic device, the first fusion request carrying product identifiers of the third product and the fourth product; sending configuration data of a second product combination to the first electronic device, the second product combination including the third product and the fourth product, the configuration data of the second product combination being used by the first electronic device to display a second fusion card, the second fusion card being used to purchase the second product combination. This allows users to independently select products from different merchant platforms they wish to purchase in a single transaction, broadening the application scenarios.

[0023] In one possible implementation, after sending the configuration data of the second product combination to the first electronic device, the method further includes: receiving a second payment request sent by the first electronic device, the second payment request indicating that the first electronic device has purchased the second product combination; upon receiving the second payment request, obtaining payment for the second product combination from a first payment account, and using the payment for the second product combination to settle accounts with multiple merchant platforms for the products in the second product combination. This allows users to purchase multiple products from different merchant platforms with a single payment operation, saving them the steps of purchasing multiple products.

[0024] In one possible implementation, the configuration data of the first product combination includes one or more of the following: the display style of the first product combination and the content data of all products in the first product combination. The content data includes one or more of the following: product name, product category, product description, product price, product inventory, and product image.

[0025] Thirdly, this application provides a communication system, including a first electronic device and a first server; wherein the first electronic device is used to execute the processing method in the first aspect and any possible implementation thereof; and the first server is used to execute the processing method in the second aspect and any possible implementation thereof.

[0026] Fourthly, this application provides an electronic device, including: one or more processors and one or more memories; the one or more memories are coupled to the one or more processors, and the one or more memories are used to store a computer program, which, when the one or more processors execute the computer program, performs the processing method described in the first aspect and any possible implementation thereof.

[0027] Fifthly, embodiments of this application provide a computer storage medium for storing a computer program, which, when executed by a processor, implements the processing method described in the first aspect and any possible implementation thereof.

[0028] Sixthly, embodiments of this application provide a computer program product, including a computer program that, when executed by a processor, implements the processing method described in the first aspect and any possible implementation thereof.

[0029] In a seventh aspect, this application provides a chip system including a processing circuit and an interface circuit. The interface circuit is used to receive code instructions and transmit them to the processing circuit. The processing circuit is used to run the code instructions to execute the processing method in the first aspect and any possible implementation of the first aspect.

[0030] Eighthly, this application provides a server, including: one or more processors and one or more memories; the one or more memories are coupled to the one or more processors, and the one or more memories are used to store a computer program, which, when the one or more processors execute the computer program, performs the processing method in any possible implementation of the second aspect and the first aspect described above.

[0031] Ninthly, embodiments of this application provide a computer storage medium for storing a computer program, which, when executed by a processor, implements the processing method in any of the possible implementations of the second aspect and the first aspect described above.

[0032] In a tenth aspect, embodiments of this application provide a computer program product, including a computer program that, when executed by a processor, implements the processing method in the second aspect and any possible implementation thereof.

[0033] In one aspect, this application provides a chip system including a processing circuit and an interface circuit. The interface circuit is used to receive code instructions and transmit them to the processing circuit. The processing circuit is used to run the code instructions to execute the processing method in any possible implementation of the second aspect and the first aspect. Attached Figure Description

[0034] Figure 1 A schematic diagram of a communication system 10 provided in an embodiment of this application; Figures 2A-2D A set of interface schematic diagrams provided for embodiments of this application; Figures 3A-3C Another set of interface schematic diagrams provided for embodiments of this application; Figures 4A-4C Another set of interface schematic diagrams provided for embodiments of this application; Figure 5 A flowchart illustrating a processing method provided in an embodiment of this application; Figure 6 A flowchart illustrating another processing method provided in an embodiment of this application; Figure 7 A schematic diagram illustrating a process for setting up a product combination, provided as an embodiment of this application; Figure 8 A schematic diagram illustrating a process for purchasing a combination of goods, provided as an embodiment of this application; Figure 9A A schematic diagram illustrating a process for establishing a payment binding relationship, provided as an embodiment of this application; Figure 9B A schematic diagram illustrating a process for uploading products, provided as an embodiment of this application; Figure 9CA schematic diagram illustrating a process for selecting a product combination, provided as an embodiment of this application; Figure 9D A schematic diagram of a process for determining a product combination is provided for an embodiment of this application; Figure 10 A schematic diagram illustrating another process for purchasing a combination of goods, provided as an embodiment of this application; Figure 11 A schematic diagram illustrating another process for setting up a product combination, provided as an embodiment of this application; Figure 12 A schematic diagram illustrating another process for setting up and purchasing a product combination, provided as an embodiment of this application; Figure 13 This is a schematic diagram of the structure of an electronic device 100 provided in an embodiment of this application. Detailed Implementation

[0035] The technical solutions in the embodiments of this application will be clearly and thoroughly described below with reference to the accompanying drawings. In the description of the embodiments of this application, unless otherwise stated, " / " means "or," for example, A / B can mean A or B; the word "and / or" in the text is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, and B existing alone. Furthermore, in the description of the embodiments of this application, "multiple" refers to two or more than two.

[0036] Hereinafter, the terms "first" and "second" are used for descriptive purposes only and should not be construed as implying or suggesting relative importance or implicitly indicating the number of indicated technical features. Thus, a feature defined as "first" or "second" may explicitly or implicitly include one or more of that feature, and in the description of the embodiments of this application, unless otherwise stated, "multiple" means two or more.

[0037] In some examples of this application, cards are a type of interface display component that can be embedded in various interfaces such as the desktop and the negative one screen. They can directly display content such as weather, news, to-do lists, and product information, allowing users to view relevant content through cards without opening the corresponding application or meta-service. Cards also support direct jumps to the target page of the application or meta-service, reducing page jump steps, simplifying operation steps, and achieving the effect of directly accessing the target service. Cards can be added or deleted by the user, and some cards can be called widgets.

[0038] In some examples of this application, meta-services are lightweight, atomic services that can independently provide complete business services by relying on the cloud and electronic devices. Electronic devices can directly use meta-services without having to go through the traditional application download, installation, and deployment process. The functions and interface components of meta-services can be directly integrated with desktops, service centers, and negative one screens, requiring only one development effort and enabling direct invocation across all scenarios, saving the work of repeated development, debugging, and adaptation.

[0039] In some examples of this application, the platform is a complete system with a server as the core backend and a client as the frontend entry point, including both the client and the server. The server is responsible for storing data, processing requests and performing calculations, while the client provides the user interface. The two systems work together to provide various services to users.

[0040] This application provides a processing method. A first electronic device displays a first product combination, which includes multiple products belonging to different merchant platforms. The first electronic device receives input for the first product combination. Upon receiving the input, the first electronic device generates a first payment request and triggers settlement processing for the first product combination based on the first payment request. In this way, users can purchase product combinations through the first electronic device. The first electronic device can meet users' needs for quickly purchasing multiple products across platforms, reducing the payment steps required for purchasing products from multiple merchant platforms, and making the operation more convenient.

[0041] In some examples, the first electronic device can display a first product combination in a card-like format. For instance, the first electronic device can display a first integrated card that includes the first product combination. This card-based display allows the first electronic device to simultaneously show products from multiple merchant platforms on a single card, enabling bundled sales of products from various platforms without requiring users to purchase individual items from each platform. The first electronic device can also visually display the content of the first product combination on interfaces such as the desktop, service center, and negative one screen, allowing users to quickly access information without navigating to different pages, thus improving information retrieval efficiency. Furthermore, the card can be pulled up with a single click to jump to the corresponding payment page, enabling quick purchase of the first product combination and enhancing shopping efficiency. The first electronic device can display multiple integrated cards, facilitating users to quickly select the desired product combination.

[0042] In some examples, after receiving input about a first product combination, the first electronic device can respond to the first input by displaying a payment interface. This payment interface includes the first product combination and payment controls. The first electronic device can also receive a second input about the payment controls and, in response, generate a first payment request. In a conventional process, the first electronic device responds to card operations by navigating to a product selection page, selecting products, entering a details page, and finally navigating to the payment page—a cumbersome process. In this embodiment, the first electronic device can respond to the first input by directly navigating to the payment page for the first product combination, reducing the number of steps, simplifying the shopping process, and improving the user's shopping experience.

[0043] In some examples, a first server can send configuration data for a first product combination to a first electronic device. This first product combination includes multiple products belonging to different merchant platforms. The configuration data is used by the first electronic device to display a first integrated card. The first server receives a first payment request from the first electronic device, indicating that the device is purchasing the first product combination. Upon receiving the first payment request, the first server retrieves the payment for the first product combination from the first payment account associated with the user logged into the first electronic device, and then uses this payment to settle accounts with the different merchant platforms for the products in the first product combination. In this way, the first server can link multiple merchant platforms, assisting the first electronic device in quickly purchasing multiple products from different merchant platforms.

[0044] In some examples, the first product portfolio includes first products from a first merchant platform. The first server retrieves payment for the first product portfolio from a first payment account associated with a user logged into the first electronic device, and uses this payment to settle accounts with multiple merchant platforms for the products in the first product portfolio. This includes: transferring payment for the first product portfolio from the first payment account to a first receiving account indicated by the first server; and transferring payment for the first product from the first receiving account to a second receiving account indicated by the first merchant platform. In this way, the first server can settle accounts for the products in the product portfolio through the first payment account. Since the first product portfolio includes products from multiple different merchant platforms, transferring payments through the first payment account allows for unified fund management, making the payment process more secure and reliable.

[0045] In some examples, the first payment request carries a first payment account and a first product combination identifier. The first server transfers the payment for the first product combination from the first payment account to a first receiving account indicated by the first server, including: determining the payment binding relationship of all products in the first product combination based on the first product combination identifier; the payment binding relationship is used to indicate the first receiving account associated with the first server and the receiving account of the merchant platform to which the products belong, and is used to instruct the first server to allocate the payment for the products from the payment account to the receiving account of the merchant platform through the first receiving account; the payment binding relationship of the first product is used to indicate the second receiving account of the first merchant platform. After determining the payment binding relationship of all products in the first product combination, the payment for the first product combination is transferred from the first payment account to the first receiving account.

[0046] Transferring payment for the first item from the first receiving account to the second receiving account designated by the first merchant platform includes: after transferring payment for the first item combination from the first payment account to the first receiving account, transferring payment for the first item from the first receiving account to the second receiving account. This allows for the determination of payment transfer paths through pre-set payment binding relationships, facilitating the purchase of goods from multiple merchant platforms by the first electronic device at once.

[0047] It should be noted that displaying product combinations in card form is merely an example and is not limited to card form. The first electronic device may also display product combinations in other forms (e.g., notifications, icons, etc.), and this application embodiment does not limit this. In subsequent embodiments, this application embodiment uses displaying product combinations in card form as an example to explain the processing method provided by this application embodiment.

[0048] The following describes a communication system 10 provided in an embodiment of this application.

[0049] For example, such as Figure 1 As shown, the communication system 10 may include, but is not limited to, electronic device 100 and server 200. Server 200 can provide electronic device 100 with configuration data for product combinations. Electronic device 100 can display product combinations based on the configuration data. Electronic device 100 can receive user input indicating the purchase of product combinations and purchase multiple products from multiple merchant platforms through server 200.

[0050] In some examples, server 200 may include business platform server 21. Business platform server 21 may include, but is not limited to, one or more of the following: distribution server 22, application gallery connect (AGC) server 23, and payment server 24. The application gallery connect server 23 can be used by developers of the merchant platform to upload products and set up product combinations (e.g., setting the products included in the product combination, the display style of the product combination, etc.). The distribution server 22 can be used to store product details data, related data of product combinations, etc. The payment server 24 can be used to transfer payment for purchasing product combinations. Specifically, payment server 24 can obtain payment for product combinations from the payment account corresponding to electronic device 100 and process settlement for the products in the product combinations on one or more merchant platforms based on the obtained payment.

[0051] In some examples, the business platform server 21 can filter one or more product combinations from the stored product combinations based on the user data of the electronic device 100. These one or more product combinations include a first product combination. The user data includes one or more of the following: user identifier, location of the first electronic device, etc. The business platform server 21 can send the configuration data of one or more product combinations to the electronic device 100. In this way, the business platform server 21 can recommend products that better meet the user's purchasing needs based on the user data. For example, based on the user identifier of the electronic device 100, it can identify products that the user has purchased and recommend product combinations that include those products. Based on the location of the electronic device 100, it can identify products near the electronic device and recommend product combinations that include products that are more convenient for offline pickup.

[0052] In some examples, one or more combinations of goods include one or more of the goods purchased by electronic device 100 and the goods near the location of electronic device 100.

[0053] It should be noted that the user data mentioned above is only an example. For instance, user data may also include one or more of the following: the weather at the location of electronic device 100, the system time of electronic device 100, the user's usual location, the point of origin, and the destination. The business platform server 21 can also recommend corresponding products to the user based on the above user data. For example, it may recommend a combination of food items when the system time is mealtime, a combination of frozen drinks when the weather is sunny, a combination of products from merchants near the user's usual location, a combination of products from merchants near the point of origin, and a combination of products from merchants near the destination. For example, the usual location may be a location where electronic device 100 stays for a longer period (e.g., within a week) than a preset duration (e.g., 2 hours).

[0054] For example, the business platform server 21 can determine the historical shopping orders of the electronic device 100 from the payment server 24 based on the user's identifier, and then determine the goods purchased by the electronic device 100 based on the historical shopping orders. For example, the business platform server 21 can determine the departure point and / or destination based on the travel tickets (e.g., train tickets, plane tickets, etc.) purchased by the electronic device 100. For example, the business platform server 21 can also obtain the departure point and / or destination entered by the user in the navigation application of the electronic device 100.

[0055] In some examples, the business platform server 21 can determine a specific product based on user data. The business platform server 21 can then send a product combination including the specified product to the electronic device 100.

[0056] The designated goods may include, but are not limited to, goods purchased by electronic device 100, goods offered by merchants near electronic device 100, goods from merchants near the permanent location of electronic device 100, goods from merchants near the destination of electronic device 100, goods from merchants near the departure point of electronic device 100, goods suitable for recommendation during the system time of electronic device 100 (e.g., recommending food during mealtimes, recommending travel supplies during holidays, etc.), and goods suitable for recommendation under the weather conditions of the location of electronic device 100 (e.g., recommending cold drinks in hot weather, recommending hot drinks in cold weather, etc.).

[0057] In this way, the business platform server 21 can recommend product combinations that are more likely to be purchased and more convenient to pick up to the user of the electronic device 100, thereby improving the user's shopping experience.

[0058] It should be noted that the purchased goods are not limited to the same product from the same merchant, but can also be the same product from different merchants on the same platform. In this way, for some offline self-pickup items, this application can provide the electronic device 100 with products from the merchant closest to the electronic device 100, making it convenient for the user to pick up the goods.

[0059] Optionally, the distribution server 22 and the application market connection server 23 can be the same server.

[0060] In some examples, the communication system 10 may also include an electronic device 300. The electronic device 300 can run various client programs and connect to a network server (e.g., an AGC server, a merchant platform server, etc.) to achieve data interaction and business operations. Specifically, the AGC server 23 can provide the electronic device 300 with an AGC client for setting up merchant combinations. Merchant platform staff can use the AGC client on the electronic device 300 to upload product details data to the AGC server 23, set up product combinations, etc. The AGC server 23 can store the product details data and related product combination data on the distribution server 22.

[0061] In some examples, staff at merchant platforms can register and log in to the AGC client. The AGC client can assign different merchant platform identifiers to different merchant platforms to distinguish them. This allows staff to upload and set up product combinations using electronic devices 300, facilitating user purchases of goods offered by the merchant platform.

[0062] In some examples, server 200 may also include one or more merchant platform servers. The merchant platform can be a third-party aggregation service platform or a brand-owned service platform. The third-party aggregation service platform can provide products from merchants of multiple brands, while the brand-owned service platform can provide products from merchants of only one brand.

[0063] For example, one or more merchant platform servers may include, but are not limited to, one or more of the following: travel platform server 31, shopping platform server 32, etc. For example, a travel platform may be a ticketing platform, a ride-hailing platform, or a navigation platform, etc. A shopping platform may be a food delivery platform, a group-buying platform, or an online shopping platform, etc.

[0064] Thus, the processing method provided in this application embodiment can offer combinations of goods from multiple merchant platforms, providing corresponding product combinations for various shopping scenarios. For example, server 200 can provide product combinations including beverages and food, matching dietary needs in one go, improving the consumer experience and ease of use, and so on.

[0065] In some examples, electronic device 100 can display an order details page after purchasing a first product combination. This order details page can include information about multiple products in the first product combination. For example, if the first product combination includes online-sold products, the order details page can include the delivery progress and destination of the online-sold products. If the first product combination includes offline-sold products, the order details page can include the pickup address and pickup time of the offline-sold products. In this way, communication system 10 can achieve unified management of product orders, generating a unified order entry after the electronic device 100 places an order. This allows users to view the delivery progress, pickup time, or estimated delivery time of multiple products within a single order, eliminating the need to view the logistics information of multiple orders separately, making order management simpler and clearer.

[0066] In some examples, server 200 can combine products from multiple merchants within the same delivery area into a single product bundle. This saves delivery resources, improves delivery efficiency, consolidates the delivery of multiple products, reduces redundant delivery routes, lowers delivery capacity consumption, and shortens overall delivery time.

[0067] In some examples of this application, electronic device 100 is also referred to as first electronic device. Server 200 is also referred to as first server, or business platform server 21 is also referred to as first server.

[0068] In some examples, the first server can receive detailed data of one or more products uploaded by one or more merchant platforms. This detailed data may include a stock keeping unit identifier (SKU_ID) and a merchant platform identifier (OwnerID). The SKU_ID indicates the corresponding product, and the OwnerID indicates the merchant platform providing the product. This allows merchant platforms to upload products to the first server, facilitating the subsequent combination of uploaded products to create product packages.

[0069] In some examples, a merchant platform identifier can include a developer identifier (DevID) and an application identifier (APP ID). For instance, different merchant platforms belonging to different companies may have different developer identifiers, while different merchant platforms belonging to the same company may have the same developer identifier but different application identifiers. This allows the merchant platform to identify products on different merchant platforms within the same company using both the developer and application identifiers. Furthermore, a single company can manage products on multiple merchant platforms simultaneously.

[0070] It should be noted that the use of both developer identifier and application identifier to indicate the merchant platform is merely an example. Different merchant platforms can also be distinguished by setting different merchant platform identifiers. This application does not limit this approach.

[0071] In some examples, one or more merchant platforms include a first merchant platform. The first merchant platform can send a first query request to a first server. Upon receiving the first query request, the first server sends a first product list to the first merchant platform, which includes products provided by one or more merchant platforms. The first merchant platform can select multiple products from the first product list to obtain a first product combination. The first merchant platform can then send the first product combination to the first server. The first server can receive and store the first product combination sent by the first merchant platform. In this way, merchant platforms can customize product combinations, allowing them to bundle suitable products for group sales and increase the probability of sales.

[0072] In some examples, after receiving the first product bundle from the first merchant platform, the first server can receive the first display style of the first merchant bundle sent by the first merchant platform. The first display style indicates whether to display one or more of the following when displaying the first product bundle: whether to display the bundle contents, whether to display coupons, and whether to display the product names. The configuration data for the first product bundle includes the first display style. In this way, the merchant platform can decide how devices such as electronic device 100 display the product bundle. Specifically, the merchant platform can set the display of bundle contents to inform customers which individual products are included in the bundle. The merchant platform can set the display of coupons to inform customers whether coupons can be used with the product bundle and the amount that can be reduced by the coupon. The merchant platform can set the display of product names to inform customers which products can be purchased through the product bundle.

[0073] Optionally, the first display style can also be used to indicate the arrangement of items in the product mix (e.g., from left to right, from top to bottom, etc.), whether to display images of items in the product mix, and one or more of the font, font size, etc. of the text when displaying the product mix.

[0074] In some examples, the first server can also receive permission information sent by merchant platforms. This permission information can be used to indicate which merchant platforms are allowed to add the product to the product portfolio. Upon receiving a first query request, the first server can determine a first product list based on the merchant platform's identifier and the product permission information stored on the first server. This first product list includes products that are allowed to be added to the product portfolio by the first merchant platform. In this way, merchant platforms can set permission information for uploaded products to specify which merchant platforms can add the products to the product portfolio, preventing unwanted merchant platforms from using uploaded products.

[0075] The following section presents a set of interface diagrams provided in the embodiments of this application.

[0076] For example, electronic device 300 can display the interface of the AGC client. Electronic device 300 can receive input from staff of merchant platform 1 regarding the AGC client, register, and log in to the AGC platform. After logging into the AGC platform, electronic device 300 can display, as shown below... Figure 2A The settings interface 201 is shown in (a). For example... Figure 2A As shown in (a), the settings interface 201 may include, but is not limited to, a developer identifier 202, an upload control 203, and a settings control 204. For example, the developer identifier 202 of merchant platform 1 is "123456". The settings control 204 can be used to trigger the electronic device 300 to display a settings interface for setting product combinations (e.g., Figure 2A (b) shows the settings interface 211. The upload control 203 can be used to trigger the electronic device 300 to display an upload interface for uploading goods from the merchant platform 1. For example, staff of the merchant platform can manually upload goods from the upload interface.

[0077] It should be noted that, in addition to the manual uploading of products by staff on merchant platforms, the AGC platform can also establish a communication connection with merchant platforms to obtain detailed product data. This allows the AGC platform to directly access products offered by various merchant platforms, facilitating product updates and reducing the workload of staff uploading products.

[0078] Optionally, the merchant platform can set upload rules for products. For example, upload rules may include, but are not limited to, uploading products within a preset price range, uploading products from merchants in a preset region, or uploading products in preset categories (e.g., beverages, fruits). This allows the merchant platform to automatically upload products that meet the upload rules to the AGC platform, making product uploading more convenient and efficient.

[0079] In some examples, the settings interface 201 may also include a product list 205. The product list 205 includes uploaded products and may display the product's application identifier and product identifier (stock keeping unit identifier, SKU ID). For example, the product list 205 may include, but is not limited to, products 205A and 205B. For instance, the application identifier for product 205A could be "Travel Application," and the product identifier could be "Product 001." The application identifier for product 205B could be "Travel Application," and the product identifier could be "Product 002." Here, the application identifier for merchant platform 1 is "Travel Application."

[0080] It should be noted that the content displayed in product list 205 is for illustrative purposes only and is not limited to this. Figure 2A The electronic device 300 may also display one or more of the following in the product list 205 shown in (a): product category, product name, product price, product shipping address (or pickup address), product discount information, etc. The embodiments of this application do not limit this.

[0081] Optionally, the business platform server 21 can obtain product details data from the merchant platform's server using the product's identifier. In this way, the business platform server 21 can obtain the latest product data from the merchant platform without needing to store the product details data itself.

[0082] After receiving user input to the settings control 204, the electronic device 300 can respond to the input by displaying, as shown below. Figure 2A The settings interface 211 is shown in (b). For example... Figure 2A As shown in (b), the settings interface 211 includes input boxes 212 and 213, and a search control 214. Input box 212 is used to input the developer identifier, and input box 213 is used to input the application identifier. Here, input box 212 includes the developer identifier of merchant platform 1, and input box 213 includes the application identifier of merchant platform 1.

[0083] After receiving user input to the search control 214, the electronic device 300 can retrieve a product list based on the content of input boxes 212 and 213. After retrieving the product list, the electronic device 300 can display, as shown below... Figure 2B The product list 215 shown in (a) includes one or more products that the merchant platform 1 can add to the product portfolio.

[0084] like Figure 2BAs shown in (a), the settings interface 211 includes a product list 215 and a confirmation control 216. The product list 215 includes product options 215A, 215B, and 215C. Among them, product 1 indicated by product option 215A and product 3 indicated by product option 215B belong to merchant platform 1, and product 2 indicated by product option 215C belongs to merchant platform 2. The confirmation control 216 can be used to combine the products indicated by the product options selected by the user in the product list 215 to obtain product combination 1.

[0085] For example, electronic device 300 can receive user input... Figure 2B After inputting product options 215A and 215C as shown in (a), the system receives user feedback. Figure 2B The input to the confirmation control 216 shown in (a) is processed. The electronic device 300 can respond to input to the confirmation control 216 by displaying, as shown in (a). Figure 2B The settings interface 211 shown in (b) is shown.

[0086] like Figure 2B As shown in (b), the settings interface 211 includes a selected product list 221 and a confirmation control 225. The selected product list 221 includes options for multiple products selected in the product list 215. The confirmation control 225 can be used to confirm the display style of product combination 1. For example, after receiving user input to the confirmation control 225, the electronic device 300 can, in response to the input, determine the display style of product combination 1 and store the display style of product combination 1 in the distribution server 22. Optionally, the electronic device 300 can also, after receiving user input to the confirmation control 225, display as shown in the image. Figure 2C The settings interface 241 shown in (b) is shown.

[0087] Optional, Figure 2B The settings interface 211 shown in (b) may also include one or more style options. For example, one or more style options may include, but are not limited to, one or more of style options 222, 223, and 224. Style option 222 can be used to set whether to display the names of the items in the product bundle. If style option 222 is selected, the electronic device 100 can display the names of the items when displaying product bundle 1. Style option 223 can be used to set whether to display a package deal. If style option 223 is selected, the electronic device 100 can display the specific contents of the package deal when displaying product bundle 1. Style option 224 can be used to set whether coupons can be used on the items. If style option 224 is selected, the electronic device 100 can display and use coupons for the items when displaying product bundle 1.

[0088] Optionally, the electronic device 300 can be configured with a default display style for the product combinations. If the electronic device 300 displays as follows... Figure 2B When the settings interface 211 shown in (b) receives input from the user to the confirmation control 225 without receiving input from the user for the style option, the electronic device 300 can set the display style of the product combination 1 to the default display style.

[0089] Optionally, the electronic device 300 can receive user input such as... Figure 2B After the user inputs the confirmation control 216 shown in (a), the products selected by the user in the product list 215 are grouped together to obtain product combination 1. The electronic device 300 can also set the display style of product combination 1 to the default display style. This reduces the number of operation steps for the staff of the merchant platform and saves time.

[0090] Optionally, one or more style options may include, but are not limited to, style options for setting the arrangement of products, style options for setting fonts, style options for setting font sizes, and style options for setting product images, etc., which are not limited in this embodiment.

[0091] Optional, Figure 2B The settings interface 211 shown in (b) may also include a preview control 226, which can be used to trigger the electronic device 300 to display product combination 1 according to the display style of product combination 1. The electronic device 300 can receive a request for preview control 226. Figure 2B After input to the preview control 226 shown in (b), in response to the input, the following is displayed: Figure 2C The preview interface 231 shown in (a) is shown.

[0092] like Figure 2C As shown in (a), the preview interface 231 may include a preview area 232. The preview area 232 may include, but is not limited to, the content 234 of product 1 and the content 235 of product 2. The content 234 may include, but is not limited to, one or more of the following: the name of product 1: "Ticket", details: "Train No. 123 City A->City B", and price: "155". The content 235 may include, but is not limited to, the name of product 2: "Self-pickup Hamburger Combo [Station Store]", details: "Hamburger..." 1. Cola 1”, Price: “35”, and Coupon: “2 yuan coupon available”, etc., one or more of these.

[0093] It should be noted that the product content is merely an example. The merchant platform can adjust it according to the product content uploaded by the merchant, and / or the first server can adjust it according to the product content uploaded by the merchant platform. For example, if the product details data obtained by the first server does not include the product name, the electronic device 300 may not display the product name in the preview area 232, and so on. This application embodiment does not limit this.

[0094] Optionally, the preview area 232 may also include, but is not limited to, one or more of the following: title 233, purchase control 236, etc. The title 233 can be used to indicate the title of product bundle 1. For example, electronic device 300 or the first server can generate this title based on the name of the merchant platform where the products in product bundle 1 are located. The purchase control 236 can be used to trigger a customer's electronic device (e.g., electronic device 100) to display a payment interface for making a payment for product bundle 1.

[0095] Optionally, the display style of product combination 1 may not include a purchase control (e.g., purchase control 236). When the electronic device 100 detects user input at any location on the card, it can trigger a jump to the payment interface. In this way, without relying on a dedicated purchase control, the electronic device 100 can directly jump to and display the payment interface when it receives user input at any location on card 1. This simplifies the card layout, saves card display space, makes the interface more concise and lightweight, expands the scope of interaction triggering, eliminates the need for precise clicks on controls, simplifies operation steps, reduces operation difficulty, and improves the convenience of interaction and user experience.

[0096] In this way, the merchant platform can use the preview control 226 to determine how electronic devices 100 will display product combination 1, making it easier for the merchant platform to confirm how the customer's device will display product combination 1. Since the merchant platform understands the customer's shopping needs, the merchant platform can set the display style of the product combination to provide customers with a better shopping experience.

[0097] The preview interface 231 may also include a confirmation control 237. This confirmation control 237 can be used to determine the display style of product combination 1.

[0098] Electronic device 300 can receive user input Figure 2C Upon input to the confirmation control 237 shown in (a), in response to the input, the following is displayed: Figure 2C The settings interface 241 is shown in (b). The electronic device 300 can also determine the display style of product combination 1 and store the display style of product combination 1 in the distribution server 22 after receiving input from the user to the confirmation control 237.

[0099] like Figure 2C As shown in (b), the settings interface 241 may include, but is not limited to, a prompt message 242. The prompt message 242 can be used to notify the user that the selected products have been successfully combined to obtain product combination 1. For example, the prompt message 242 may include a text message such as: "You have successfully added 2 products to the fusion card." In this way, the staff of the merchant platform can access the AGC platform through electronic device 300 and publish products and set up product combinations on the AGC platform, making the product publishing operation more convenient.

[0100] In some examples, the first server can receive product fusion conditions uploaded by the merchant platform. Based on the product fusion conditions set by the merchant platform, the first server can determine the products to be combined with the products provided by the merchant platform. These product fusion conditions may include, but are not limited to, one or more of the following: merchant platform, product category, product price range, and product sales method (e.g., offline sales, online sales, or a combination of online and offline sales). The first server can combine products that meet some or all of the product fusion conditions with the products provided by the merchant platform to obtain one or more product combinations.

[0101] For example, if the first server combines products that meet all product fusion conditions with products from merchant platform 1. The product fusion conditions for merchant platform 1 include merchant platform 1 or merchant platform 2, product category 1, product price range 1, and product sales method 1. The first server can combine products from merchant platform 1 or merchant platform 2 that are of product category 1, have a price range of 1, and are sold using sales method 1 with products from merchant platform 1 (e.g., random combination, sequential combination, etc.) to obtain multiple product combinations.

[0102] In this way, merchants no longer need to manually create product combinations. When there are a large number of products on the merchant platform, product combinations can be automatically generated, resulting in higher combination efficiency.

[0103] Understandably, merchant platforms can also set default display styles for product combinations. This allows the primary server to display multiple product combinations, including those from the merchant platform, based on the product merging conditions and default display styles set by the merchant platform, providing customers with a wider variety of product options.

[0104] In some examples, merchant platforms can divide uploaded products into multiple sections and set one or more of the following for each section: product merging conditions, permission information, etc. For instance, the platform can divide products into sections based on one or more of the following: product category, sales method, price, etc. This allows for matching different products with more suitable combinations, making it easier for customers to purchase the items they need in one go and increasing the probability of each product being sold.

[0105] It should be noted that, in addition to the above-mentioned methods of manually setting product combinations or setting product combinations based on product fusion conditions, product combinations can also be set in other ways. For example, the first server can also set multiple product combinations based on the historical purchase records of multiple customers through an artificial intelligence model, etc. This application embodiment does not limit this.

[0106] For example, electronic device 300 can receive a response to... Figure 2A After input is received into the setting control 204 shown in (a), in response to the input, the following is displayed: Figure 2D The settings interface shown is 251. (As shown) Figure 2D As shown, the settings interface 251 can be used to set the product fusion conditions for merchant platform 1. The settings interface 251 may include, but is not limited to, one or more of the following: one or more merchant platform options, one or more product category options, etc. For example, one or more merchant platform options may include, but is not limited to, options 252A, 252B, and 252C. Option 252A indicates merchant platform 2, option 252B indicates merchant platform 1, and option 252C indicates merchant platform 3. Similarly, one or more product category options may include, but is not limited to, one or more of the following: options 253A, 253B, and 253C. Option 253A indicates the food category, option 253B indicates the general merchandise category, and option 253C indicates the pharmaceutical category.

[0107] If electronic device 300 receives user input and selects options 252A, 252B, and 253C, the products on merchant platform 1 can be combined with food products from either merchant platform 1 or merchant platform 2 to create a product combination. This is understandable. Figure 2D The options shown are for illustrative purposes only and should not be construed as specific limitations.

[0108] Optionally, the electronic device 300 can determine one or more merchant platform options to display to merchant platform 1 based on the product's permission information. For example, if the product permission information in merchant platform 1 indicates that the allowed combination of products includes products from merchant platform 2, and the product permission information in merchant platform 2 indicates that the allowed combination of products includes products from merchant platform 1, the electronic device 300 can display the merchant platform option corresponding to merchant platform 2 to merchant platform 1. If the product permission information in merchant platform 1 indicates that the allowed combination of products does not include products from merchant platform 2, or the product permission information in merchant platform 2 indicates that the allowed combination of products does not include products from merchant platform 1, the electronic device 300 will not display the merchant platform option corresponding to merchant platform 2 to merchant platform 1.

[0109] In some examples, after receiving input from a user triggering the display of a product combination, the electronic device 100 can, in response to this input, retrieve configuration data for one or more product combinations from the business platform server. The configuration data for the first product combination includes one or more of the following: a first display style for the first product combination, and content data for all products in the first product combination. The content data includes one or more of the following: product name, product category, product description, product price, product inventory, and product image. Based on the retrieved configuration data for one or more product combinations, the electronic device 100 can display a fusion card corresponding to the product combination. The fusion card includes fusion card 1, which includes product combination 1. After receiving input from the user for fusion card 1, the electronic device 100 can pay for and purchase product combination 1. In this way, the electronic device 100 can display a fusion card for purchasing product combinations.

[0110] For example, such as Figure 3A As shown in (a), the electronic device 100 displays a desktop 301. The desktop 301 may include multiple application icons. Upon receiving user input on the desktop 301 (e.g., a rightward swipe), the electronic device 100, in response to that input, displays... Figure 3A The negative screen 311 shown in (b). Figure 3A As shown in (b), the negative one screen 311 can display icons for multiple meta-services. The electronic device 100 can display icons such as... after receiving user input on the negative one screen 311 (e.g., swiping up). Figure 3B The negative screen 311 shown in (a)

[0111] like Figure 3BAs shown in (a), the negative one screen 311 can display multiple cards. These multiple cards include a merge card 312. The merge card 312 can be used to purchase product combination 1. The merge card 312 may include, but is not limited to, one or more of the following: name 312A, content 312B of product 1, content 312C of product 2, and purchase control 312D. A description of the merge card 312 can be found in [reference needed]. Figure 2C The description of preview area 232 shown in (a) will not be repeated here. Optionally, the electronic device 100 can, upon receiving user input... Figure 3A Upon input (e.g., swiping right) to desktop 301 as shown in (a), in response to that input, the following is displayed: Figure 3B The fusion card 312 shown in (a) is shown.

[0112] Optional, such as Figure 3B The negative one screen 311 shown in (a) may also include a card 313. The card 313 can be used to trigger the electronic device 100 to display multiple cards for purchasing individual items, and the items on these cards can be combined into a product bundle. In this way, users can create product bundles themselves and purchase multiple items at once, reducing the number of payment steps for multiple items and increasing purchasing efficiency.

[0113] Electronic device 100 can receive user input Figure 3B After inputting the purchase control 312D shown in (a), in response to the input, the following is displayed: Figure 3B The payment interface 321 shown in (b) is as follows. Figure 3B As shown in (b), the payment interface 321 is used to purchase product combination 1, which includes product 1 and product 2. The payment interface 321 may include an entry 322 for product 1 and an entry 323 for product 2. Entry 322 displays a description of product 1, and entry 323 displays a description of product 2. The payment interface 321 may also include a total amount 324 for product combination 1 and a payment control 325. Upon receiving user input to the payment control 325, the electronic device 100 can, in response to this input, trigger a settlement process for product combination 1.

[0114] Understandably, if product combination 1 includes offline products, payment interface 321 may also include the pickup address for the offline products. If product combination 1 includes online products, payment interface 321 may also include the delivery address for the online products. For example, electronic device 100 may receive user input to determine the delivery address.

[0115] Electronic device 100 can display the following after the checkout process for product combination 1 is successful: Figure 3C The payment interface 331 shown in (a) is as follows. Figure 3CAs shown in (a), the payment interface 331 may include a prompt message 332. The prompt message 332 can be used to notify the user of the result of purchasing product combination 1. For example, the prompt message 332 may include a text-based prompt message: "Purchase successful". Optionally, the payment interface 331 may also include, but is not limited to, one or more of the following: a view order icon, a "buy again" icon, one or more cards, etc. The view order icon can be used to trigger the electronic device 100 to display an order details page. For example, if the product is an online product, the order details page may include, but is not limited to, delivery progress, delivery address, product description, etc. If the product is an offline product, the order details page may include, but is not limited to, pickup address, pickup time, product description, etc. The "buy again" icon can be used to trigger the electronic device 100 to display, such as... Figure 3B The payment interface 321 shown in (b) allows one or more cards to be used to purchase the corresponding goods.

[0116] In this way, the electronic device 100 can display multiple integrated cards, enabling users to efficiently purchase multiple items, making payment operations more convenient and providing a better user experience.

[0117] In some examples, electronic device 100 can obtain the image and identifier of product combination 1 from business platform server 21. For example, the configuration data of product combination 1 may include, but is not limited to, the image and identifier of product combination 1. Electronic device 100 can display, based on the image of product combination 1, such as... Figure 3C As shown in (b), the fusion card 315 includes an image of product combination 1. Upon receiving user input on the fusion card 315, the electronic device 100 can retrieve content data of the products in product combination 1 from the business platform server 21 based on the product combination identifier of product combination 1. For example, the content data may include, but is not limited to, one or more of the following: product name, product description, product price, product stock, quantity of sold products, product image, etc. The electronic device 100 can display, based on the retrieved content data, such as... Figure 3B The payment interface 321 shown in (b) allows the electronic device 100 to display images of the product combination 1, providing a more vivid and engaging presentation of the products in the product combination 1, resulting in a better display effect.

[0118] In some examples, the first electronic device can display multiple candidate cards, including a first candidate card and a second candidate card. The first candidate card is used to purchase a third item, and the second candidate card is used to purchase a fourth item. The first electronic device receives a third input indicating that the first and second candidate cards have been selected. In response to the third input, the first electronic device displays a second combined card, which includes a second product combination that includes the third and fourth items. The first electronic device receives a fourth input regarding the second combined card. Upon receiving the fourth input, the first electronic device generates a second payment request, triggering settlement processing for the second product combination based on the second payment request. In this way, users can combine items from multiple merchant platforms into a product combination for quick and efficient purchase.

[0119] In some examples, the first electronic device can obtain configuration data for multiple candidate products from a first server, including a third product and a fourth product. Based on the configuration data of the multiple candidate products, the first electronic device displays multiple candidate cards. In this way, the first electronic device can display a card for purchasing a single product through the first server.

[0120] For example, such as Figure 4A As shown in (a), the electronic device 100 can obtain configuration data for multiple candidate products from the business platform server 21. These candidate products can be combined to form product combinations. For example, product permission information can be used to determine whether products can be combined. After obtaining the configuration data for multiple candidate products, the electronic device 100 can display a settings interface 401. The settings interface 401 may include multiple cards and a generation control 406. For example, the multiple cards may include, but are not limited to, cards 402, 403, 404, and 405. Card 402 can be used to purchase product 4, card 405 can be used to purchase product 5, card 403 can be used to purchase product 6, and card 404 can be used to purchase product 7. Optionally, the electronic device 100 can receive user input... Figure 3B After input of card 313 as shown in (a), in response to the input, the following is displayed: Figure 4A The settings interface 401 shown in (a) is shown.

[0121] After receiving input from the user selecting cards 402 and 405, the electronic device 100 can display the following: Figure 4A The settings interface 401 is shown in (b). Figure 4A As shown in (b), cards 402 and 405 are selected, while cards 403 and 404 are unselected. Electronic device 100 can receive user input... Figure 4AUpon input to the generation control 406 shown in (b), in response to that input, a fusion card 411 for purchasing product combination 2 is generated based on cards 402 and 405. Product combination 2 includes product 4 and product 5. The electronic device 100 can display as shown... Figure 4B The fusion card 411 shown in (a)

[0122] like Figure 4B As shown in (a), the merge card 411 can be used to purchase product bundle 2. The merge card 411 may include the contents 412 of product 4 and the contents 413 of product 5. The contents 412 may include, but are not limited to, the name of product 4: "coffee" and the price: "12". The contents 413 may include, but are not limited to, the name of product 5: "water bill" and the price: "53.2". The merge card 411 may also include a payment control 416, which can be used to trigger the electronic device 100 to display an interface for paying for product bundle 2.

[0123] Optionally, the fusion card 411 may also include a modification control 415. Upon receiving user input to the modification control 415, the electronic device 100 may, in response to that input, display, as shown below. Figure 4A The settings interface 401 is shown in (b). This allows users to adjust the product combinations, making it easier for them to purchase the items they need.

[0124] In some examples of this application, product 4 is also referred to as the third product, product 5 as the fourth product, card 402 as the first candidate card, card 405 as the second candidate card, fusion card 411 as the second fusion card, and product combination 2 as the second product combination.

[0125] Electronic device 100 can receive user input Figure 4B Upon input to the payment control 416 shown in (a), in response to the input, the following is displayed: Figure 4B The payment interface 421 shown in (b) is shown.

[0126] like Figure 4B As shown in (b), the payment interface 421 is used to purchase product combination 2, which includes product 4 and product 5. The payment interface 421 may include an entry 422 for product 4 and an entry 423 for product 5. Entry 422 displays a description of product 4, and entry 423 displays a description of product 5. The payment interface 421 may also include a payment control 424. Upon receiving user input to the payment control 424, the electronic device 100 can, in response to the input, trigger a settlement process for product combination 2.

[0127] Electronic device 100 can display the following after the checkout process for product combination 2: Figure 4CThe payment interface shown is 431. (As shown) Figure 4C As shown, the payment interface 431 may include a prompt message 432. The prompt message 432 can be used to notify the user of a successful purchase of product combination 2. A description of the payment interface 431 can be found here. Figure 3C The description of the payment interface 331 shown in (a) will not be repeated here. The payment interface 431 may also include an order viewing control, which can be used to trigger the electronic device 100 to display an order details page. A description of the order details page can be found in the above embodiments.

[0128] In this way, the electronic device 100 can display multiple candidate cards, enabling users to efficiently purchase multiple items, making payment operations more convenient and providing a better user experience.

[0129] The following is a flowchart illustrating a processing method provided in an embodiment of this application.

[0130] For example, such as Figure 5 As shown, the processing method provided in this application embodiment can be applied to electronic device 100 and business platform server 21. The processing method may include the following steps: S501. The business platform server 21 sends configuration data of product combination 1 to the electronic device 100. Product combination 1 includes multiple products, which belong to different merchant platforms.

[0131] The business platform server 21 can send configuration data for one or more product combinations to the electronic device 100. For example, the business platform server 21 can filter one or more product combinations from stored product combinations based on user data. The filtered product combinations may include one or more of the following: products purchased by the electronic device 100, products near the location of the electronic device 100, etc. In some examples, a description of determining one or more product combinations based on user data can be found in [reference needed]. Figure 1 The illustrated embodiment.

[0132] For example, the configuration data may include a display style. The display style instructs the electronic device 100 how to display the product combination. For instance, the display style may indicate whether to display the package contents, coupons, or product names when displaying the product combination. Optionally, the display style may also indicate the arrangement of products in the product combination, whether to display images of products in the product combination, and the font and size of the text when displaying the product combination; this embodiment does not limit these aspects.

[0133] Configuration data can also include product combination identifiers. These identifiers can be used to uniquely and accurately locate corresponding product combinations. This allows for the differentiation of different product combinations.

[0134] Optionally, the configuration data may also include an account binding identifier. This identifier can be used to indicate the payment account of the merchant platform to which the products in the product bundle belong. In this way, the electronic device 100 can execute the payment process for the product bundle based on the account binding identifier.

[0135] In some examples, the configuration data may also include, but is not limited to, the content data of all products in the product bundle. For example, content data may include, but is not limited to, one or more of the following: product name, product category, product description, product price, product inventory, quantity sold, and product image. Optionally, the bundled card may include content data. This allows users to understand the details of the product bundle through the content data displayed in the bundled card, making it easier for them to select the product bundle they need.

[0136] Optionally, the business platform server 21 can receive product detail data uploaded by the merchant platform, including content data. Based on the product detail data, the business platform server 21 can determine the product content data. Thus, the business platform server 21 can determine the content data that the electronic device 100 can display based on the detail data uploaded by the merchant platform.

[0137] In other examples, the business platform server 21 can determine the product identifiers of all products in a product combination based on the product combination identifier. The business platform server 21 can then retrieve product content data from the merchant platform based on these product identifiers. In this way, the business platform server 21 can obtain the latest product data from the merchant platform, providing users with more accurate card content.

[0138] Optionally, the business platform server 21 can obtain the merchant platform identifier based on the product combination identifier. The business platform server 21 can then obtain the product content data indicated by the product identifier from the corresponding merchant platform based on the merchant platform identifier. This facilitates the business platform server 21 in obtaining content data from the merchant platform.

[0139] Optionally, the configuration data may include product identifiers for all products in the product portfolio, and / or merchant platform identifiers. This allows the business platform server 21 to directly retrieve content data from the merchant platform based on the configuration data.

[0140] S502. Electronic device 100 displays fusion card 1, fusion card 1 including product combination 1.

[0141] After receiving configuration data for one or more product combinations, the electronic device 100 can display one or more integrated cards based on the received configuration data. The one or more integrated cards include integrated card 1, which includes product combination 1.

[0142] S503. Electronic device 100 receives input to fusion card 1.

[0143] After displaying one or more converged cards, the electronic device 100 receives input from the user for converged card 1. Upon receiving input for converged card 1, the electronic device 100 can then pay for and purchase the product bundle 1. Specifically, upon receiving input for converged card 1, the electronic device 100 can execute step S504.

[0144] For example, if Fusion Card 1 is Figure 3B As shown in (a) of the fusion card 312, the input to the fusion card 1 can be a... Figure 3B The input of the purchase control 312D shown in (a).

[0145] S504. Electronic device 100 can send payment request 1 to business platform server 21.

[0146] After receiving input for the converged card 1, the electronic device 100 can send a payment request 1 to the business platform server 21.

[0147] S505. After receiving payment request 1, business platform server 21 obtains the payment for the goods package 1 purchased by the electronic device, and uses the obtained payment to settle accounts with different merchant platforms for the goods in the goods package 1.

[0148] In this context, payment request 1 indicates that electronic device 100 is purchasing product combination 1. Upon receiving payment request 1, business platform server 21 can transfer the payment for product combination 1 from the payment account of electronic device 100 to the receiving account of business platform server 21. After successfully receiving the payment, business platform server 21 can process the settlement for the products in product combination 1 on the merchant platform. It is understood that if the products in product combination 1 belong to multiple merchant platforms, business platform server 21 can process the settlement for the products in product combination 1 on each of those merchant platforms, thus enabling the purchase of product combination 1 for the user logged into electronic device 100. If the products in product combination 1 belong to only one merchant platform, business platform server 21 can process the settlement for all products in product combination 1 on that single merchant platform, thus enabling the purchase of product combination 1 for the user logged into electronic device 100.

[0149] In some examples, product portfolio 1 includes product 1 from merchant platform 1. Business platform server 21 can transfer payment for product portfolio 1 from its payment account to its receiving account. Business platform server 21 can also transfer payment for product 1 from its receiving account to the receiving account of merchant platform 1.

[0150] In some examples, payment request 1 may carry a product combination identifier for product combination 1 and a user identifier (UID) for electronic device 100. The user identifier of electronic device 100 can be used to indicate the payment account of electronic device 100. The product combination identifier can be used to indicate product combination 1. The business platform server 21 can also determine the merchant platform identifier of the products in product combination 1, the product identifier of the products in product combination 1, and the receiving account of the merchant platform to which the products in product combination 1 belong, based on the product combination identifier of product combination 1. In this way, the business platform server 21 can complete the purchase process for product combination 1 based on payment request 1.

[0151] In some examples, the business platform server 21 can store the payment binding relationships of goods. These payment binding relationships indicate the receiving account associated with the business platform server 21 and the receiving account of the merchant platform, and instruct the business platform server 21 to transfer the payment for goods in the merchant platform from the payment account associated with the business platform server 21 to the receiving account of the merchant platform through the receiving account associated with the business platform server 21. The business platform server 21 can determine the receiving account of the merchant platform through the payment binding relationships of goods. This allows for the rapid determination of the receiving account of the merchant platform to which a product in a product combination belongs.

[0152] In some examples, the payment binding relationship includes a receiving account associated with the payment platform and a receiving account with merchant platform 1. The payment binding relationship can be used to instruct the payment platform to transfer payment for a product combination from the customer's payment account (e.g., the payment account associated with a user logging into electronic device 100) to the receiving account associated with the payment platform. The payment platform then transfers payment for the products in merchant platform 1 from the payment account associated with the payment platform to the receiving account of merchant platform 1.

[0153] Optionally, payment request 1 can also include the total amount of product combination 1. This allows the business platform server 21 to verify the payment amount for product combination 1, ensuring payment security.

[0154] The following is a flowchart illustrating a processing method provided in an embodiment of this application.

[0155] For example, such as Figure 6As shown, this processing method can be applied to a communication system including an electronic device 100, an application market connection platform, and a distribution server 22. The AGC platform can include an AGC client and an AGC server 23. The processing method includes the following steps: S601. Distribution server 22 stores detailed data of multiple products, which is used by the merchant platform to determine product combinations.

[0156] The distribution server 22 can receive and store product detail data uploaded by the merchant platform. This detail data may include, but is not limited to, one or more of the following: product identifier, merchant platform identifier, and product content data.

[0157] S602. The application market connection platform can obtain detailed data of multiple products from the distribution server 22.

[0158] S603. The application market connection platform determines a product combination from multiple products 1.

[0159] S604. Application Market Connection Platform: Set the display style of Product Combination 1.

[0160] S605. The application market connection platform displays product combination 1 based on the set display style.

[0161] In some examples, the AGC platform can receive input from staff on Merchant Platform 1 to obtain detailed data for multiple products. The AGC platform can also receive input from staff on Merchant Platform 1 to determine multiple product combinations, including Product Combination 1. This allows staff on the merchant platform to set up the product combinations themselves.

[0162] Optionally, after receiving input from the staff of Merchant Platform 1, the AGC platform can obtain detailed data on multiple products that Merchant Platform 1 is allowed to use, based on Merchant Platform 1's merchant platform identifier and product permission information. The product permission information is set by the respective merchant platform. This allows the staff of the merchant platform to independently set which merchant platforms' products can be combined with, thus controlling the scope of cooperation.

[0163] In some examples, after the AGC platform identifies multiple product combinations, it can receive input from the staff of Merchant Platform 1 to set the display style of these combinations. This allows the Merchant Platform staff to customize how the product combinations are displayed. For example, the AGC platform can provide multiple style options (e.g., ...). Figure 2B (as shown in (b)) The AGC platform can receive input from the staff of the merchant platform 1 on the style options and set the display style of the product combination.

[0164] Optionally, the AGC platform can also display product combinations according to a set display style. This allows merchant platform staff to preview the display style of product combinations, making it easier for them to adjust the display style to achieve the most satisfactory effect.

[0165] In other examples, the AGC platform can determine one or more product combinations from multiple products, including product combination 1. For instance, the AGC platform can determine multiple product combinations based on preset product fusion conditions. These preset conditions can be default settings for the AGC platform. Alternatively, the AGC platform can determine multiple product combinations using artificial intelligence algorithms. In this way, the AGC platform can automatically determine multiple product combinations based on products uploaded from multiple merchant platforms, eliminating the need for manual confirmation and thus increasing the efficiency of product combination creation.

[0166] Optionally, the AGC platform can also determine product combinations based on the product permission information set by the merchant platform. This allows the AGC platform to avoid combining products from merchant platforms that have not given their consent, providing merchants with a safer and more reliable product combination service.

[0167] Optionally, when determining product combinations, the AGC platform can also set display styles for multiple product combinations. The AGC platform can set the display styles for multiple product combinations according to a default style. This allows the AGC platform to determine the display style of product combinations when making those combinations. Since the process of setting product combinations on the AGC platform does not require the involvement of merchant platform staff, the AGC platform may choose not to display product combination 1.

[0168] Optionally, the AGC platform can also receive display styles set by the merchant platform's staff, and set the display styles for products belonging to that merchant platform within the product mix, thereby determining the overall display style of the product mix. Optionally, the AGC platform can also display examples of the display styles set by the merchant platform. In this way, the AGC platform can determine the display style of the merchant platform's products within the product mix according to the display styles set by the merchant platform.

[0169] S606. The application market connection platform sends relevant data of product combination 1, including display style, to the distribution server 22.

[0170] After successfully setting up one or more product combinations, the AGC platform can send the relevant data of the product combinations to the distribution server 22. The relevant data includes the product combination identifier, the display style of the product combination, the detailed data of the products in the product combination, and the account binding identifier of the products in the product combination. The display style is used to instruct electronic devices such as 100 how to display the product combination.

[0171] Optionally, the AGC platform may omit the step of setting the display style of the product bundle. Instead, the AGC platform can send the content data of all products in the product bundle to the electronic device 100. The electronic device 100 can then generate and display a merged card for purchasing the product bundle based on the content data of all products in the bundle. For example, the electronic device 100 can generate the merged card based on the content data using an artificial intelligence model.

[0172] S607. Distribution server 22 stores relevant data for product combination 1.

[0173] After receiving data related to one or more product combinations sent by the AGC platform, the distribution server 22 can store the data related to the one or more product combinations.

[0174] S608. The distribution server 22 sends configuration data for one or more product combinations to the electronic device 100, the one or more product combinations including product combination 1.

[0175] The distribution server 22 can determine the configuration data of the product combinations from the relevant data of the product combinations, and the distribution server 22 can send the configuration data of one or more product combinations to the electronic device 100. The relevant data of the product combinations includes the configuration data of the product combinations. A description of the configuration data can be found in the above embodiments.

[0176] S609. Electronic device 100 displays a corresponding fusion card based on configuration data of one or more product combinations, the displayed fusion card including fusion card 1, fusion card 1 including product combination 1.

[0177] The distribution server 22 can send configuration data for one or more product combinations to the electronic device 100. After receiving the configuration data for the one or more product combinations, the electronic device 100 can display the corresponding fusion card based on the received configuration data.

[0178] In some examples, electronic device 100 can send a request message to distribution server 22 after receiving user input indicating that it wants to display a product combination. Distribution server 22 can then send configuration data for one or more product combinations to electronic device 100 based on the request message. Specifically, distribution server 22 can determine one or more product combinations based on user data before sending the configuration data for those combinations to electronic device 100. In this way, distribution server 22 can determine a suitable product combination for display by electronic device 100.

[0179] It should be noted that the distribution server 22 is not limited to sending configuration data for product combinations after receiving a request message from the electronic device 100. The distribution server 22 may also send configuration data for one or more product combinations to the electronic device 100 at preset push intervals, or it may send configuration data for product combinations of merchants near the location of the electronic device 100 after detecting a change in the electronic device 100's location, etc. This embodiment does not limit these possibilities. After receiving configuration data for one or more product combinations, the electronic device 100 can display the corresponding integrated card based on the configuration data when it receives user input to display an integrated card. In this way, the distribution server 22 can push the latest product combinations to the electronic device 100, or push nearby product combinations to the electronic device 100 based on its location.

[0180] In some examples, the input for displaying the product combination can also be the input that triggers the electronic device 100 to display the negative one screen. This allows the electronic device 100 to display the product combination on the negative one screen, making it easy for the user to quickly trigger the display of the product combination.

[0181] S610. Electronic device 100 receives input indicating that it has purchased product combination 1.

[0182] S611. Electronic device 100 triggers settlement processing for product combination 1.

[0183] After displaying multiple product combinations, the electronic device 100 can trigger the settlement process for product combination 1 upon receiving input indicating that it wants to purchase product combination 1. In this way, the AGC platform can set up multiple product combinations, and the distribution server 22 can provide these pre-set combinations to the electronic device 100. The electronic device 100 can then implement a process of paying for and purchasing multiple products in one transaction, making the purchasing process more convenient and efficient.

[0184] The following is a flowchart illustrating a process for setting up a product combination, provided by an embodiment of this application.

[0185] For example, such as Figure 7As shown, the payment platform may include a payment server 24, and the application market connection platform may include an AGC server 23. The process for setting up a product combination on the merchant platform 1 includes the following steps: S701. Merchant Platform 1: Developers register and log in to the application market connection platform.

[0186] The developer side of Merchant Platform 1 can register and log in to the AGC platform. The AGC platform can create an AGC platform account for each merchant platform and set a corresponding merchant platform identifier. This merchant platform identifier is used to distinguish different merchant platforms. In some examples, the merchant platform identifier can include both the developer identifier and the application identifier mentioned above. In other examples, the merchant platform identifier can be the AGC platform account, and so on.

[0187] In some examples, the developer's client for merchant platform 1 can be an electronic device 300. The developer's client for merchant platform 1 can receive operations from the staff of merchant platform 1 and execute them. Figure 7 The steps are shown.

[0188] In some examples, the developer side of Merchant Platform 1 can be staff members of Merchant Platform 1. The AGC platform can receive and execute operations from the staff members of Merchant Platform 1. Figure 7 The steps are shown.

[0189] S702. The developer side of Merchant Platform 1 obtains the permission to publish product combinations on Merchant Platform 1.

[0190] After registering and logging into the AGC platform, the developer client of Merchant Platform 1 can obtain the permission to publish product combinations on the AGC platform. For example, the developer client of Merchant Platform 1 can send a publishing request to the AGC platform. This publishing request instructs Merchant Platform 1 to apply for the permission to publish product combinations. AGC platform staff can review Merchant Platform 1 (e.g., to determine its compliance) and, upon approval, grant it the permission to publish product combinations. In this way, the AGC platform can grant the permission to publish product combinations to legitimate merchant platforms and refuse to grant this permission to illegitimate merchant platforms, thus enhancing security.

[0191] It should be noted that step S702 is an optional step. In some other examples, the developer side of merchant platform 1 may not execute step S702, and all merchant platforms registered on the AGC platform can publish product combinations.

[0192] S703. The developer of Merchant Platform 1 connects to the platform through the application market and sets up the payment platform to distribute the payment to Merchant Platform 1.

[0193] Merchant Platform 1's developers can sign a payment agreement with the payment platform through the AGC platform. After signing the agreement, when a customer purchases a product bundle, the payment platform can collect payment for the bundle from the customer's payment account. The payment platform then transfers payment for the individual items in the bundle to the corresponding merchant platform's receiving account and purchases the bundle on that merchant platform. This allows for unified payment collection across multiple merchant platforms, simplifying the process for merchants to collect payments and reducing the steps required for users to purchase bundles, thus saving shopping time.

[0194] For example, the AGC platform or payment platform can set up a payment binding relationship for the goods on merchant platform 1. This payment binding relationship is used to instruct the payment platform's associated receiving account to transfer the payment for the goods on merchant platform 1 from the payment platform's associated payment account to the merchant platform 1's receiving account through the payment platform's associated receiving account.

[0195] For example, a payment binding relationship includes the receiving account associated with the payment platform and the receiving account of merchant platform 1. The payment binding relationship can be used to instruct the payment platform to transfer the payment for a product combination from the customer's payment account (e.g., the payment account associated with the user logging into electronic device 100) to the receiving account associated with the payment platform. The payment platform then transfers the payment for the products in merchant platform 1 from the payment account associated with the payment platform to the receiving account of merchant platform 1.

[0196] S704. The developer of Merchant Platform 1 can send the detailed data of the products of Merchant Platform 1 to the distribution server 22 through the application market connection platform. The detailed data includes product identifier and merchant platform identifier.

[0197] Optionally, the product details may include, but are not limited to, one or more of the following: product identifier, product description, product price, product inventory, merchant platform identifier 1, and merchant platform 1's payment account.

[0198] In some examples, the AGC platform can provide a product upload function, allowing the developer of merchant platform 1 to upload products from merchant platform 1 to the AGC platform. After obtaining the products uploaded by merchant platform 1, the AGC platform can store the product details data on the distribution server 22.

[0199] Optionally, the developer side of merchant platform 1 can configure distribution server 22 to obtain product detail data from the server of merchant platform 1 through the AGC platform. In this way, the developer side of merchant platform 1 does not need to manually upload products. Distribution server 22 can obtain product detail data from the server of merchant platform 1, which not only saves the time of manual input, but also avoids the situation of manual input errors. Distribution server 22 can update data in real time, which is more timely.

[0200] S705. The developer of Merchant Platform 1 can send the permission information of the products of Merchant Platform 1 to the distribution server 22 through the application market connection platform, which is used to indicate the merchant platform that allows the products to be added to the product portfolio.

[0201] The AGC platform provides permission information settings, allowing the developer of Merchant Platform 1 to configure permission information for its products. After obtaining the permission information uploaded by Merchant Platform 1, the AGC platform stores it on the distribution server 22. This permission information can be used to indicate which merchant platforms are allowed to add Merchant Platform 1's products to a product portfolio. This allows the merchant platform to manage which merchant platforms are permitted to use its products, ensuring product security.

[0202] Step S705 is optional. The AGC platform may also choose not to provide the function of setting permission information.

[0203] S706. Merchant Platform 1's developer-side query allows Merchant Platform 1 to add products to a product portfolio.

[0204] S707. The application market connection platform sends a product query request to the distribution server 22 to query products that the merchant platform 1 is allowed to add to the product portfolio.

[0205] S708. The application market connection platform receives a product list 1 sent by the distribution server 22, including products that the merchant platform 1 is allowed to add to the product portfolio.

[0206] The AGC platform provides functionality for querying products used to compose product combinations, as well as for setting up product combinations. The developer side of Merchant Platform 1 can query the distribution server 22 for products allowed to be added to product combinations through the AGC platform. For example, the AGC platform can receive input from the developer side of Merchant Platform 1 requesting products allowed to be added to product combinations (e.g., for...). Figure 2A After inputting the search control 214 shown in (b), a product query request is sent to the distribution server 22.

[0207] After receiving a product query request, distribution server 22 can provide product list 1 to the developer's client on merchant platform 1 through the AGC platform. Product list 1 includes products that merchant platform 1 can add to product combinations. The developer's client on merchant platform 1 can select multiple products from product list 1 to form product combinations. After receiving the product combinations determined by merchant platform 1, the AGC platform can store the relevant data of the product combinations on distribution server 22.

[0208] For example, after receiving a product query request, the distribution server 22 can send product list 1 to the AGC platform. Upon receiving product list 1, the AGC platform can output product list 1. For instance, the AGC platform can display product list 1; a description of how the AGC platform displays product list 1 can be found in [link to relevant documentation]. Figure 2B The embodiment shown in (a) is as follows.

[0209] S709. The developer side of Merchant Platform 1 determines Product Combination 1 in the application market connection platform, which includes multiple products selected in Product List 1.

[0210] Among them, the developer side of merchant platform 1 can select multiple products from the product list 1 provided by AGC platform to form product combination 1.

[0211] In other examples, the AGC platform can provide product fusion condition setting functionality. The developer side of merchant platform 1 can set product fusion conditions for products on merchant platform 1 within the AGC platform. The AGC platform or distribution server 22 can then set product combinations based on these fusion conditions. For details, please refer to... Figure 2D The illustrated embodiment.

[0212] The developer side of S710 Merchant Platform 1 determines the display style of Product Combination 1 by connecting to the platform through the application market.

[0213] After determining the products included in product bundle 1, the developer side of Merchant Platform 1 can also determine the display style of product bundle 1 through the AGC platform. A description of how the developer side of Merchant Platform 1 sets the display style of product bundle 1 can be found here. Figure 2B (b) and Figure 2C The embodiment shown in (a) is as follows.

[0214] S711. The application market connection platform sends relevant data of product combination 1 to the distribution server 22, including the display style of product combination 1 and the product identifiers of all products in product combination 1.

[0215] After the AGC platform confirms the product combination 1 and its display style on the merchant platform 1, it can store the relevant data of product combination 1 on the distribution server 22. This data may include, but is not limited to, the product combination identifier of product combination 1, the display style of product combination 1, the detailed data of all products in product combination 1, the account binding identifiers of all products in product combination 1, etc.

[0216] In this way, the developer side of merchant platform 1 can publish products on the AGC platform, set up product combinations, and store the products and product combinations on the distribution server 22. The developer side of merchant platform 1 can also set up to collect payments for the products through a payment platform.

[0217] The following is a schematic diagram of a process for purchasing a combination of goods provided in an embodiment of this application.

[0218] For example, such as Figure 8 As shown, the process of purchasing a product bundle using electronic device 100 includes the following steps: S801. Electronic device 100 receives input to display a combination of goods.

[0219] The electronic device 100 can obtain configuration data for one or more product combinations after receiving input to display the product combination.

[0220] In some examples, the input for displaying the product combination can be the input for toggling the display of the negative one screen. For example, the input for displaying the product combination can be... Figure 3A The input is a rightward swipe on desktop 301 as shown in (a).

[0221] In some examples, the input for displaying the product combination can be an input that triggers the electronic device 100 to display metadata service content. For example, the input for displaying the product combination can be... Figure 3A The input is shown in (b) on the negative screen 311.

[0222] S802. Electronic device 100 obtains configuration data for one or more product combinations from distribution server 22, the one or more product combinations including product combination 1.

[0223] After receiving input to display a product combination, electronic device 100 can obtain configuration data for one or more product combinations from distribution server 22. For example, after receiving input to display a product combination, electronic device 100 sends a combination request to distribution server 22. Distribution server 22, upon receiving the combination request, can send configuration data for one or more product combinations to electronic device 100. For details, please refer to... Figure 6 The embodiments shown are not described in detail here.

[0224] In other examples, after receiving input to display a product combination, electronic device 100 can retrieve historical merged orders from the payment platform. These historical merged orders can indicate which product combinations have been purchased by electronic device 100. Based on these historical merged orders, electronic device 100 can obtain configuration data for the corresponding product combinations from distribution server 22. Based on this configuration data, electronic device 100 can display the corresponding merged card. This allows for matching the user's past consumption preferences, providing a more accurate and personalized push notification experience.

[0225] S803. Electronic device 100 displays one or more merge cards based on configuration data of one or more product combinations, the one or more merge cards including merge card 1, merge card 1 including product combination 1.

[0226] After receiving configuration data for one or more product combinations, the electronic device 100 can determine how to display the product combinations based on the display style in the configuration data. The electronic device 100 can display the product combinations in the form of cards according to the display style. These product combinations displayed in card form are also called integrated cards.

[0227] S804. Electronic device 100 receives input to fusion card 1.

[0228] When displaying one or more converged cards, electronic device 100 receives input to converged card 1. After receiving input to converged card 1, electronic device 100 can perform the step of purchasing product bundle 1.

[0229] S805. Electronic device 100 sends a payment request to the payment platform 1.

[0230] After receiving input for the converged card 1, the electronic device 100 can send a payment request 1 to the payment platform. The payment request 1 can be used to instruct the electronic device 100 to purchase the product combination 1.

[0231] S806. The payment platform obtains the payment for product combination 1 and settles the payment for product combination 1 using the obtained payment.

[0232] After receiving payment request 1, the payment platform can obtain the payment for product combination 1 from the payment account associated with the user who logged into electronic device 100, and use the obtained payment to settle accounts with multiple merchant platforms for the products in product combination 1.

[0233] For example, payment request 1 carries the product combination identifier of product combination 1 and the payment account of electronic device 100. The payment platform can obtain from the distribution server 22 the merchant platforms to which all products in product combination 1 belong, and the unique identifier of each product on its respective merchant platform, based on the product combination identifier of product combination 1. For example, the distribution server 22 can determine the unique identifier of each product on its respective merchant platform based on the product identifier. The payment platform can then search for and purchase the product on its respective merchant platform based on its unique identifier, until all products in product combination 1 have been purchased.

[0234] Optionally, the configuration data for product combination 1 may include the account binding identifiers of all merchant platforms corresponding to all products in product combination 1. The payment platform can determine the payment binding relationship based on the account binding identifiers, thereby obtaining the receiving account corresponding to the merchant platform from the distribution server 22.

[0235] In this way, electronic devices can provide users with the service of purchasing goods from multiple merchant platforms in one transaction, eliminating the need for users to place repeated orders and allowing them to quickly purchase the required goods from multiple merchant platforms. It is understood that the processing method provided in this application embodiment can also be used to purchase multiple goods from a single merchant platform in one transaction, and this application embodiment does not limit this approach.

[0236] The following is a schematic diagram of a process for establishing a payment binding relationship provided by an embodiment of this application.

[0237] For example, such as Figure 9A As shown, the process of establishing a payment binding relationship includes the following steps: S901. Merchant Platform 1: Developers register and log in to the application market connection platform.

[0238] S902. The application market connection platform sets the merchant platform identifier of merchant platform 1 to merchant platform identifier 1.

[0239] S903. The developer side of Merchant Platform 1 obtains the permission to publish integrated cards on Merchant Platform 1 through the application market connection platform.

[0240] The descriptions of steps S901-S903 can be found in [reference needed]. Figure 7 The illustrated embodiment.

[0241] S904. The developer side of Merchant Platform 1 initiates a payment agreement signing process with the application market connection platform.

[0242] In this process, after obtaining the merchant platform identifier 1, the developer of merchant platform 1 can initiate a payment agreement signing process with the AGC platform. For example, the AGC platform can provide a control for signing the payment agreement. After receiving input from the developer of merchant platform 1 regarding the control for signing the payment agreement, the AGC platform can execute step S905.

[0243] S905. The application market connection platform sends a payment agreement signing request to the payment platform, carrying the merchant platform identifier 1.

[0244] The AGC platform can detect when the developer of Merchant Platform 1 initiates a payment agreement signing process and can then send a payment agreement signing request to the payment platform. The payment platform can include Merchant Platform Identifier 1 in the payment agreement signing request.

[0245] Optionally, the payment agreement signing request may also include the agreement initiation time. This allows us to determine when the payment platform signed the payment agreement.

[0246] S906. Based on the payment agreement signing request, the payment platform sets up the distribution of payment to merchant platform 1.

[0247] After receiving a payment agreement signing request, the payment platform can configure itself to distribute the payment for goods from Merchant Platform 1 within the product bundle to Merchant Platform 1. The customer's electronic device can then transfer the payment for the product bundle to the payment platform's receiving account. The payment platform then distributes the payment for goods from each merchant platform within the product bundle to the respective merchant platform's receiving account.

[0248] S907. The payment platform establishes a payment binding relationship 1, which is used to indicate the correspondence between the merchant platform 1's receiving account and the payment platform's receiving account.

[0249] After receiving a payment agreement signing request, the payment platform can also establish a payment binding relationship 1. This payment binding relationship 1 indicates the correspondence between the merchant platform 1's receiving account and the payment platform's receiving account. Specifically, payment binding relationship 1 can be used by the payment platform to transfer payments for goods from the merchant platform 1's receiving account to the merchant platform 1's receiving account. In this way, the payment platform can act as an intermediary between customers and merchant platforms, collecting payments for multiple goods from the customer's account at once, and then transferring the payments for each item to the corresponding merchant platform's account.

[0250] For example, payment binding relationship 1 includes a receiving account associated with merchant platform 1 and a receiving account associated with payment platform. Payment binding relationship 1 can be used to instruct the payment platform to transfer the payment for a combination of goods from the customer's payment account (e.g., the payment account associated with the user logging into electronic device 100) to the receiving account associated with payment platform. The payment platform then transfers the payment for the goods in merchant platform 1 from the payment account associated with payment platform to the receiving account of merchant platform 1.

[0251] In some examples, payment binding relationship 1 includes a payment binding identifier. Thus, the corresponding payment binding relationship can be identified through the payment binding identifier.

[0252] Optionally, the payment request can include the payment binding identifier of each item in the product bundle. For example, the payment binding identifier can be included in the configuration data, making it easier for the customer's electronic device to access it. Alternatively, the payment platform can store the mapping between product bundle identifiers and payment binding identifiers. The payment request can then include the product bundle identifier. In both cases, the payment binding relationship can be determined through the payment binding identifier.

[0253] In some examples, since the distribution of payments needs to be handled through a payment platform, the payment platform can charge a transaction fee based on the revenue sharing ratio when transferring payments. Payment binding relationship 1 is also used to indicate the revenue sharing ratio between merchant platform 1 and the payment platform when a shopping transaction is completed through the payment platform. It is understood that when a product combination includes multiple products from a single merchant platform, the revenue sharing ratio is charged only once to that merchant platform.

[0254] In some examples, payment binding relationship 1 includes an account binding identifier (merchant_binding_ID), the merchant platform 1's receiving account (L2_merchantID), the payment platform's receiving account (L1_merchantID), and a split ratio. The account binding identifier indicates payment binding relationship 1, and can be used to find the merchant platform 1's receiving account, the payment platform's receiving account, and the split ratio. Thus, the configuration data for the product combination sent by the distribution server 22 to the electronic device can include the account binding identifier, facilitating the payment platform's confirmation of the merchant platform's receiving account when a customer purchases the product combination.

[0255] S908. The payment platform sends a payment agreement signing response to the application market connection platform.

[0256] After setting up the payment platform to distribute payments to merchant platform 1, it can send a payment agreement signing response to the AGC platform. This response indicates that the payment platform has successfully set up the payment platform to distribute payments to merchant platform 1.

[0257] S909. The application market connection platform returns a successful payment agreement signing message to the developer side of merchant platform 1.

[0258] After receiving the payment agreement signing response, the AGC platform can return a message indicating successful payment agreement signing to the developer's client on merchant platform 1. For example, the AGC platform can output a notification message to the developer's client on merchant platform 1 indicating that the payment agreement has been successfully signed.

[0259] In this way, merchant platform 1 can... Figure 9A The steps shown are configured so that the payment platform distributes the payment to merchant platform 1, thereby enabling the collection of payment for the goods on merchant platform 1 in the product combination.

[0260] The following is a schematic diagram of a process for uploading products provided in an embodiment of this application.

[0261] For example, such as Figure 9B As shown, the process of uploading products includes the following steps: S911. The developer of Merchant Platform 1 uploads detailed data of one or more products in Merchant Platform 1 to the distribution server 22 through the application market connection platform, including one or more of the following: product identifier, product description, product price, product inventory, and Merchant Platform Identifier 1.

[0262] Developers on Merchant Platform 1 can upload products from Merchant Platform 1 to the AGC platform. For details, please refer to... Figure 7 The description of step S704 is shown.

[0263] S912. The distribution server 22 stores the detailed data of the one or more products.

[0264] Distribution server 22 can store the details of the products received from merchant platform 1. Similarly, distribution server 22 can store the details of multiple products from multiple merchant platforms.

[0265] In some examples, the distribution server 22 can also store the account binding identifier in the product details data when storing the product details data, based on the aforementioned payment binding relationship 1. This facilitates the subsequent determination of the merchant platform's receiving account.

[0266] S913. The distribution server 22 sends a product entry notification to the application market connection platform to indicate that the distribution server has successfully saved the product details data of the merchant platform 1.

[0267] After storing the product details data of merchant platform 1, distribution server 22 can send a product receipt notification to the AGC platform. This product receipt notification can be used to indicate to the distribution server that it has successfully saved the product details data of merchant platform 1.

[0268] S914. The application market connection platform returns a message to the developer side of merchant platform 1 indicating that the product has been successfully published.

[0269] Upon receiving a notification that a product has been successfully published, the AGC platform can send a success message to the developer side of merchant platform 1. For example, the AGC platform can notify the developer side of merchant platform 1 that the product has been successfully published by outputting a notification message indicating successful publication.

[0270] S915. The developer side of Merchant Platform 1 sets the permission information of the products of Merchant Platform 1 on the application market connection platform.

[0271] The developer side of Merchant Platform 1 can set the permission information for products on Merchant Platform 1 within the AGC platform. For details, please refer to... Figure 7 The description of step S705 is shown below. The product permission information is used to indicate which merchant platforms are permitted to add the product to the product portfolio.

[0272] In some examples, the developer side of merchant platform 1 can set whether a product is allowed to be added to a product portfolio by other merchant platforms on the AGC platform, and when a product is set to be allowed to be added to a product portfolio by other merchant platforms, the merchant platform identifier of the merchant platform that is allowed to add the product to the product portfolio is set.

[0273] In some examples, the developer side of merchant platform 1 can batch set permission information for multiple products on the AGC platform. This allows for quick setting of permission information for multiple products, saving setup time.

[0274] In some examples, the AGC platform can use the "access_policy" parameter to indicate the product's access permissions. For instance, when the "access_policy" parameter is set to "open," it means all merchant platforms are allowed to add the product to their product portfolio. When the "access_policy" parameter is set to "whitelist," it means specified merchant platforms are allowed to add the product to their product portfolio. When the "access_policy" parameter is set to "private," it means no merchant platform is allowed to add the product to their product portfolio.

[0275] S916. The application market connection platform sends the product permission information of merchant platform 1 to the distribution server 22, which is used to indicate which merchant platforms are allowed to add products to the product portfolio.

[0276] After receiving the permission information of the products of merchant platform 1 set by the developer of merchant platform 1, the AGC platform can send the permission information of the products of merchant platform 1 to the distribution server 22.

[0277] S917. Distribution server 22 stores the permission information of the goods of merchant platform 1.

[0278] After receiving the product permission information from merchant platform 1, distribution server 22 can store the product permission information from merchant platform 1. Similarly, distribution server 22 can store product permission information from multiple merchant platforms.

[0279] S918. The distribution server 22 sends a permission activation notification to the application market connection platform, which is used to indicate that the distribution server 22 has successfully stored the permission information of the merchant platform 1's products.

[0280] After storing the permission information of the products on merchant platform 1, distribution server 22 can send a permission activation notification to the AGC platform. This permission activation notification indicates that distribution server 22 has successfully stored the permission information of the products on merchant platform 1.

[0281] S919. The application market connection platform returns permission information to the developer side of merchant platform 1, indicating successful configuration.

[0282] After receiving the notification that the permissions have taken effect, the AGC platform can return a message to the developer's side of merchant platform 1 indicating that the permission configuration was successful. For example, the AGC platform can output a message to indicate that merchant platform 1 has successfully set up product permissions.

[0283] In this way, various merchant platforms can... Figure 9B The steps shown indicate how to upload products from the platform to facilitate the subsequent creation of product combinations.

[0284] The following is a flowchart illustrating a product selection process according to an embodiment of this application.

[0285] For example, such as Figure 9C As shown, the process for selecting items in a product bundle includes the following steps: S921. The developer side of Merchant Platform 1 connects to the platform through the application market to query products to be added to the product portfolio.

[0286] Specifically, the developer side of Merchant Platform 1 can query products for adding to product portfolios on the AGC platform. The AGC platform can query products that Merchant Platform 1 is allowed to add to product portfolios based on Merchant Platform 1's Merchant Platform Identifier 1.

[0287] For example, the AGC platform can provide a product query control. After receiving input from the developer on the merchant platform 1, the AGC platform can query the products to be added to the product portfolio.

[0288] S922. The application market connection platform sends a product query request to the distribution server 22, carrying the merchant platform identifier 1.

[0289] After receiving input from the developer side of merchant platform 1 requesting products to be added to the product portfolio, the AGC platform can send a product query request to the distribution server 22. The product query request can carry the merchant platform identifier 1.

[0290] Optionally, the product query request may carry the "filter_pocliy" parameter, which instructs the distribution server 22 to determine the list of products to be returned based on the permission information.

[0291] S923. The distribution server 22 determines a product list 1 from products provided by multiple merchant platforms based on the merchant platform identifier 1. The product list 1 includes products that the merchant platform 1 is allowed to add to the product portfolio.

[0292] The distribution server 22 can determine a product list 1 from multiple stored products based on the product's permission information and the merchant platform identifier 1. The product list 1 includes products whose permission information indicates that the merchant platform 1 is permitted to add them to the product portfolio.

[0293] For example, the distribution server 22 can add the product with the merchant platform identifier 1, including the product's permission information, to the product list 1.

[0294] S924. Distribution server 22 sends product list 1 to application market connection platform.

[0295] After determining the product list 1, the distribution server 22 can send the product list 1 to the AGC platform.

[0296] S925. The application market connection platform returns product list 1 to the developer side of merchant platform 1.

[0297] After receiving the product list 1 sent by the distribution server 22, the AGC platform can return the product list 1 to the developer side of the merchant platform 1. For example, the AGC platform can output the product list 1.

[0298] S926. The developer side of Merchant Platform 1 confirms Product Combination 1 through the application market connection platform, which includes multiple products in Product List 1.

[0299] The developer side of merchant platform 1 can select multiple products from product list 1 to create product combination 1. For example, when the AGC platform outputs product list 1, it can receive input from the developer side of merchant platform 1 to select multiple products and obtain product combination 1.

[0300] In some examples, the product list 1 may include detailed product data. This allows the developer side of the merchant platform 1 to select product combinations based on the detailed data.

[0301] In some examples, product portfolio 1 includes a linked sku list. The linked sku list includes multiple products selected by the developer on merchant platform 1 from product list 1.

[0302] S927. The developer side of Merchant Platform 1 submits the sales method of Product Combination 1 to the application market connection platform to indicate the sales method of the products in Product Combination 1. The sales method includes online sales method and offline sales method.

[0303] In this system, the developer side of merchant platform 1 can submit the sales methods for products in a product combination on the AGC platform. Optionally, the AGC platform can store the sales methods of products in product combination 1 on the distribution server 22. This allows the platform to recommend suitable product combinations to customers based on the sales methods and also makes it easier for customers to confirm how to receive the products. For example, the AGC platform can use the "rule_type" parameter to indicate the sales method of products in a product combination.

[0304] It should be noted that step S927 is an optional step. The AGC platform can skip step S927 and proceed to step S928 after executing step S926.

[0305] S928. The application market connection platform sends a verification request 1 to the distribution server 22, which instructs the distribution server 22 to verify whether the product combination 1 conforms to the preset combination rules.

[0306] After the AGC platform confirms product combination 1 on the merchant platform 1, it can send verification request 1 to the distribution server 22. Verification request 1 can be used to instruct the distribution server 22 to verify whether product combination 1 conforms to the preset combination rules.

[0307] The distribution server 22 can confirm compliance with preset combination rules when it detects one or more of the following: the products in product combination 1 belong to different merchant platforms; the merchant platforms to which the products in product combination 1 belong have signed payment agreements; and the permission information of the products in the product combination matches the merchant platforms of the products in the product combination. Specifically, if the merchant platforms indicated by the permission information of any product in product combination 1 include the merchant platforms of all products in product combination 1, then the permission information of the products in the product combination matches the merchant platforms of the products in the product combination.

[0308] S929. When the distribution server 22 determines that the product combination 1 conforms to the preset combination rules, it notifies the application market connection platform that the product combination verification has passed.

[0309] When the distribution server 22 determines that product combination 1 conforms to the preset combination rules, it notifies the AGC platform that the product combination verification has passed. After confirming that the product combination verification has passed, the AGC platform can execute step S930.

[0310] It should be noted that steps S928 and S929 are optional steps. The AGC platform may choose not to execute step S928 and step S929.

[0311] S930. The application market connection platform instructs the distribution server 22 to set the product combination identifier of product combination 1.

[0312] The AGC platform can instruct the distribution server 22 to assign a product combination identifier to product combination 1. Upon receiving this instruction, the distribution server 22 can set the product combination identifier of product combination 1 to product combination identifier 1. In this way, the product combination identifier can be used as an index to find the corresponding product combination.

[0313] After determining the product combination identifier of the product combination, the distribution server 22 can also store the correspondence between the payment binding identifier, the product combination identifier, and the detailed data of each product in the product combination. This makes it easier for the distribution server 22 to find relevant information about the product combination.

[0314] S931. Distribution server 22 returns a successful message to the application market connection platform: "Set up product combination 1".

[0315] After determining the product combination identifier of product combination 1, the distribution server 22 can return a successful setting of product combination 1 to the AGC platform.

[0316] S932. The application market connection platform returns a successful product combination 1 setting to the developer side of merchant platform 1.

[0317] After receiving the message from the distribution server 22 that the product combination 1 has been successfully set, the AGC platform can send a message to the developer side of the merchant platform 1 that the product combination 1 has been successfully set.

[0318] Optionally, the AGC platform can output a notification message to the user indicating that product combination 1 has been successfully set up.

[0319] In this way, merchants can set up product combinations on the AGC platform.

[0320] The following is a schematic diagram of a process for determining a product combination provided by an embodiment of this application.

[0321] For example, such as Figure 9D As shown, the process for merchant platform 1 to determine product combinations includes the following steps: S941. The developer side of Merchant Platform 1 instructs the application market to connect to the platform to generate the display style of Product Combination 1.

[0322] After determining the products in product combination 1, the developer side of merchant platform 1 can also set the display style of product combination 1 through the AGC platform. For example, after receiving a request from the developer side of merchant platform 1 to set the display style, the AGC platform can execute step S942.

[0323] S942. The application market connection platform determines the display style of product combination 1 based on the preset style generation rules.

[0324] The AGC platform can determine the display style of product combination 1 based on preset style generation rules. For example, the preset style generation rules can be rules indicated by the Ark UI framework. For instance, preset style generation rules can be used to indicate one or more of the layout, spacing, saturation, font, etc., used when generating the product combination. In some examples, the AGC platform can set the display style through domain-specific language (DSL) information.

[0325] S943. The application market connection platform returns the display style of product combination 1.

[0326] After determining the display style of product combination 1, the AGC platform can return the display style of product combination 1 to the developer side of merchant platform 1. For example, the AGC platform can display product combination 1 based on the determined display style.

[0327] S944. The developer side of Merchant Platform 1 adjusts the display style of Product Combination 1 by connecting to the platform through the application market.

[0328] After returning the display style of product combination 1, the AGC platform can also receive settings from the developer side of merchant platform 1 and adjust the display style of product combination 1.

[0329] In some examples of this application, the display style of product bundle 1 can be used to indicate one or more of the following: whether the package contents of the products are displayed when product bundle 1 is displayed, whether the coupons of the products are displayed when product bundle 1 is displayed, whether the name of the products is displayed when product bundle 1 is displayed, the arrangement of the products in product bundle 1, whether the image of the products is displayed when product bundle 1 is displayed, and the text style of the text when product bundle 1 is displayed.

[0330] It is understandable that the developer side of merchant platform 1 may also use the display style of product combination 1 generated by AGC platform without adjusting the display style of product combination 1. This application embodiment does not limit this.

[0331] S945. The developer side of Merchant Platform 1 confirms the relevant data of Product Combination 1 through the application market connection platform.

[0332] After setting the display style of product combination 1, the AGC platform can receive operations from the developer side of merchant platform 1 (e.g., for...). Figure 2C (Input to the confirmation control 237 shown in (a)) confirms the relevant data for product combination 1. The relevant data for product combination 1 may include, but is not limited to, display style, payment binding identifier, product combination identifier, and bound product list. The bound product list includes detailed data for each product in the product combination.

[0333] In this way, the distribution server 22 can determine the correspondence between the display style, payment binding identifier, product combination identifier and the bound product list in the product combination, which makes it easier for the distribution server 22 to determine the configuration data of the product combination.

[0334] After the AGC platform confirms the relevant data of product combination 1 on the developer's side of merchant platform 1, it can store the display style of product combination 1 to distribution server 22. Distribution server 22 can determine the relevant data of product combination 1 after receiving the display style of product combination 1.

[0335] S946. The application market connection platform sends an information verification request to the distribution server 22 to instruct the distribution server 22 to verify whether the relevant data of product combination 1 is complete.

[0336] After the AGC platform confirms the relevant data of product combination 1 on the developer's side of merchant platform 1, it can send an information verification request to distribution server 22. This information verification request instructs distribution server 22 to verify the completeness of the relevant data for product combination 1.

[0337] Distribution server 22 can notify the AGC platform that information verification failed when it determines that the relevant data for product combination 1 is incomplete. The AGC platform can then return a failure to upload product combination 1. Optionally, the AGC platform can also instruct the developer of merchant platform 1 to supplement the missing relevant data for product combination 1.

[0338] The distribution server 22 can execute step S947 when it determines that the relevant data of product combination 1 is complete.

[0339] S947. When the distribution server 22 determines that the relevant data of product combination 1 is complete, it notifies the application market connection platform that the information verification has passed.

[0340] S948. The application market connection platform returns relevant data on the successful upload of product combination 1 to the developer side of merchant platform 1.

[0341] When the AGC platform receives a notification from the distribution server 22 and the verification is successful, it can return relevant data about the successful upload of product combination 1 to the developer side of the merchant platform 1.

[0342] In this way, the merchant platform can set up product combinations, and the distribution server 22 can store relevant data about the product combinations.

[0343] In some examples, distribution server 22 can synchronize product combinations to the payment platform. The payment platform can then generate corresponding product combination orders based on these combinations. These product combination orders are used to purchase the corresponding product combinations. The payment platform can also send one or more product combination orders to electronic device 100 based on completed shopping orders already placed on the electronic device 100.

[0344] After receiving one or more product combination orders from the payment platform, electronic device 100 can obtain configuration data of the product combination corresponding to the product combination order from distribution server 22. Based on the obtained configuration data, electronic device 100 can display a fusion card used to purchase the product combination.

[0345] In this way, since the payment platform stores the completed shopping orders of electronic device 100, it can analyze users' shopping habits and recommend product combination orders that are more likely to be purchased by users of electronic device 100. Furthermore, the payment platform can generate product combination orders in advance, and electronic device 100 can send the corresponding product combination order to the payment platform after receiving input from the user for a fusion card to purchase a certain product combination, thus quickly purchasing the product combination.

[0346] In some examples, the payment platform can determine one or more product combination orders sent to electronic device 100 based on user data. In this way, the payment platform can recommend product combination orders that are more likely to be purchased by the user of electronic device 100 based on their shopping habits and other factors.

[0347] The following is a schematic diagram of a process for purchasing a combination of goods provided in an embodiment of this application.

[0348] For example, such as Figure 10 As shown, the process of purchasing a product bundle using electronic device 100 includes the following steps: S1001. Distribution server 22 sends multiple product combinations to the payment platform, including product combination 1.

[0349] The distribution server 22 can send stored product combinations to the payment platform. The product combinations stored by the distribution server 22 may include product combinations set by the merchant platform, and / or product combinations set based on product fusion conditions, etc. For example, the distribution server 22 can send relevant data about product combinations to the payment platform, enabling the payment platform to obtain multiple product combinations.

[0350] S1002. The payment platform generates a product combination order corresponding to the product combination, and the product combination order is used to purchase the product combination.

[0351] After receiving multiple product combinations from the distribution server 22, the payment platform can generate multiple product combination orders corresponding to each product combination. For example, a product combination order may include, but is not limited to, a product combination identifier, an account binding identifier, and product prices. Thus, the product combination identifier indicates the product combination, the merchant binding identifier identifies the payment platform's receiving account and the merchant platform's receiving account, and the total price of the product combination is determined.

[0352] Optionally, a product bundle order may also include product identifiers and merchant platform identifiers for all products in the bundle. This allows for identification of the products in the bundle order and the merchant platform to which they belong, facilitating the payment platform's purchase of the corresponding products from the merchant platform.

[0353] Optionally, a product combination order may also include an order identifier. This allows the order to be clearly identified, making it easier for the payment platform to manage such orders.

[0354] S1003. Electronic device 100 receives input to display a combination of goods.

[0355] Electronic device 100 receives input to display a product combination. In some examples, the input to display a product combination may be input to display a fusion card.

[0356] S1004. Electronic device 100 sends a product combination order request to the payment platform, carrying the user identifier of electronic device 100.

[0357] After receiving input indicating a product combination, electronic device 100 can send a product combination order request to the payment platform. This order request may include the user identifier of electronic device 100.

[0358] S1005. The payment platform determines order combination 1 based on user data. Order combination 1 includes one or more product combination orders, and one or more product combination orders include product combination order 1 corresponding to product combination 1.

[0359] After receiving a request for a combined product order, the payment platform can determine order combination 1 based on the user data of electronic device 100. For details, please refer to [link / reference]. Figure 1 The illustrated embodiment. Order combination 1 includes product combination order 1, which is used to purchase product combination 1.

[0360] S1006. The payment platform sends order combination 1 to electronic device 100.

[0361] After confirming order combination 1, the payment platform can send order combination 1 to electronic device 100.

[0362] S1007. Electronic device 100 obtains the configuration data of the corresponding product combination from the distribution server 22 based on the product combination order of order combination 1.

[0363] After receiving order combination 1, electronic device 100 can obtain the configuration data of the corresponding product combination from distribution server 22 based on the product combination order of order combination 1. The configuration data may include, but is not limited to, display styles. Electronic device 100 can then display a fusion card including the product combination based on the display style.

[0364] S1008. Electronic device 100 displays multiple merge cards based on the configuration data of the acquired product combination, the multiple merge cards including merge card 1, and merge card 1 including product combination 1.

[0365] S1009. Electronic device 100 receives input indicating that it has purchased product combination 1.

[0366] After receiving input indicating that the purchase of product combination 1 is being made, electronic device 100 may execute step S1010. For example, the input to purchase product combination 1 may be an input to fusion card 1.

[0367] S1010. Electronic device 100 sends a payment request to the payment platform.

[0368] After receiving input indicating the purchase of product combination 1, electronic device 100 can send a payment request to the payment platform. For example, the payment request may carry the user identifier of electronic device 100 and the product combination identifier of product combination 1. Optionally, the payment request may also carry the price of product combination 1.

[0369] In some examples, electronic device 100 can transmit parameters to the payment platform and trigger the payment platform to perform the operation of payment and purchase of goods combination 1 by calling the payment interface provided by the payment platform.

[0370] S1011. The payment platform deducts the payment for the goods combination 1 from the payment account associated with the electronic device 100 and transfers the payment to the receiving account of the payment platform.

[0371] Upon receiving a payment request, the payment platform can deduct the payment for goods combination 1 from the payment account associated with electronic device 100 and transfer the payment to the payment platform's receiving account. For example, the payment account associated with electronic device 100 is the payment account associated with the user who logged into electronic device 100.

[0372] S1012. The payment platform performs settlement processing for the goods in product combination 1 on the merchant platform.

[0373] After receiving payment for Combination 1, the payment platform can process settlements for the goods in Combination 1 on one or more merchant platforms that provide the goods. Specifically, the payment platform can transfer payment from its own account to the respective merchant platform's account, enabling users logged into electronic device 100 to purchase Combination 1.

[0374] S1013. The payment platform returns the payment result to the electronic device 100.

[0375] After processing the settlement of product combination 1, the payment platform can return a payment result to the electronic device 100. It is understood that if the payment platform successfully processes the settlement of product combination 1, it can return a payment result indicating successful payment. If the payment platform fails to process the settlement of product combination 1, it can return a payment result indicating payment failure.

[0376] S1014. Electronic device 100 outputs payment result.

[0377] After receiving the payment result from the payment platform, the electronic device 100 can output the payment result. For example, the electronic device 100 can output a prompt message to inform the user of the payment result.

[0378] In this way, electronic device 100 can use the processing method provided in the embodiments of this application to purchase multiple goods provided by one or more merchant platforms through a single payment operation.

[0379] In some application scenarios, such as Figure 11 As shown, the distribution server 22 may include, but is not limited to, a product information query module 1101, a card style generation module 1102, and a storage module 1103. The product information query module 1101 can be used to determine the product list based on the merchant platform identifier. The card style generation module 1102 can be used to generate the display style of the product combination. The storage module 1103 can be used to store the product details data and related data of the product combination. The staff of the merchant platform 1 can connect to the AGC platform through the application market to set up the integrated card, including the following steps: (1) The application market connection platform receives the input of the developer end of the merchant platform to set up the product combination.

[0380] For example, the input can be a pair Figure 2A The input of setting control 204 shown in (a).

[0381] (2) The application market connection platform sends the developer identifier and application identifier of the merchant platform to the product information query module 1101.

[0382] After receiving the input of the merchant platform setting the product combination, the AGC platform can send the merchant platform's developer identifier and application identifier to the product information query module 1101 of the distribution server 22.

[0383] (3) The product information query module 1101 sends the product list to the application market connection platform.

[0384] After receiving the developer identifier and application identifier from the merchant platform, the product information query module 1101 can determine the product list based on these identifiers. The description of how the product information query module 1101 determines the product list can be found in the description of determining the product list based on permission information described above. After determining the product list, the product information query module 1101 can send the product list to the AGC platform.

[0385] Upon receiving a product list, the AGC platform can display it. For example, a description of how the AGC platform displays a product list can be found here. Figure 2B The embodiment shown in (a) is as follows.

[0386] (4) The developer side of the merchant platform sets the product combination and its display style.

[0387] After the AGC platform outputs the product list, the merchant platform's developer side can configure product combinations and their display styles on the AGC platform. For example, see [link to relevant documentation]. Figure 2B (a) to Figure 2B The embodiment shown in (b) is as follows.

[0388] (5) The application market connection platform sends the developer identifier, application identifier, and product identifier to the distribution server 22.

[0389] After receiving the product combination selected by the developer on the merchant platform, the AGC platform can send the developer identifier, application identifier, and product identifier of the selected product to the distribution server 22.

[0390] (6) The distribution server 22 sends the product combination identifier and display style of the product combination to the application market connection platform.

[0391] After receiving the developer identifier, application identifier, and product identifier, the distribution server 22 can set a product combination identifier for the product combination and generate the display style of the product combination through the card style generation module 1102. After determining the product combination identifier and display style of the product combination, the distribution server 22 can send the product combination identifier and display style of the product combination to the AGC platform.

[0392] Optionally, and not limited to, the product combination identifier and display style determined by the distribution server 22 can also be determined by the AGC platform, and / or the display style. This application embodiment does not limit this.

[0393] (7) The developer side of the merchant platform confirms the product combination.

[0394] The AGC platform can display product combinations according to a defined display style. Merchant platform developers can confirm product combinations on the AGC platform.

[0395] (8) The application market connection platform sends the developer identifier, application identifier, product combination identifier, and display style to the storage module 1103.

[0396] After receiving the product combination input from the developer on the merchant platform, the AGC platform can send the developer identifier, application identifier, product combination identifier, and display style to the storage module 1103.

[0397] In some examples, since the distribution server 22 generates the display style of the product combination, the AGC platform, after receiving the confirmation of the product combination input from the developer on the merchant platform, does not need to send the display style to the distribution server 22; it can only send the product combination identifier. In this way, the distribution server 22 can confirm that the merchant platform has published the product combination based on the product combination identifier, and can also store relevant data of the product combination through the storage module 1103. This relevant data may include, but is not limited to, developer identifier, application identifier, product combination identifier, and display style.

[0398] (9) The storage module 1103 sends status information to the application market connection platform. The status information is used to indicate the result of setting the product combination.

[0399] The storage module 1103 can send status information to the AGC platform after storing the relevant data for the product combination. This status information indicates the result of setting the product combination. If the storage module 1103 successfully stores the relevant data for the product combination, it can send status information to the AGC platform indicating successful product combination publication. If the storage module 1103 fails to store the relevant data for the product combination, it can send status information to the AGC platform indicating failed product combination publication.

[0400] Optionally, after receiving the status information, the AGC platform can return the status information to the developer's side of the merchant platform. For example, the input for confirming the product combination can be a pair of... Figure 2C The input of the confirmation control 237 shown in (a), and the description of the status information returned by the AGC platform, can be found in [reference needed]. Figure 2C The embodiment shown in (b) is as follows.

[0401] In some application scenarios, such as Figure 12 As shown, the distribution server 22 may include, but is not limited to, a product information query module 1101 and an order query module 1201. The product information query module 1101 can be used to query product details, product configuration data, and product combination configuration data. The order query module 1201 can be used to query candidate products. The merchant platform may include, but is not limited to, an order query module 1211, a product information query module 1212, and a payment module 1213. The order query module 1211 can be used to query overview data of candidate products. The product information query module 1212 can be used to query product details. Setting up and purchasing product combinations on the electronic device 100 includes the following steps: (1) Electronic device 100 receives input to display candidate cards.

[0402] For example, the input for displaying candidate cards can be a pair of... Figure 3B The input of card 313 shown in (a).

[0403] (2) Electronic device 100 sends user data to the order query module 1201 of distribution server 22.

[0404] After receiving input to display candidate cards, the electronic device 100 can send its user data to the order query module 1201 of the distribution server 22. The user data may include, but is not limited to, one or more of the following: user identifier, location of the electronic device 100, etc.

[0405] (3) The order query module 1201 of the distribution server 22 sends the product identifiers of multiple candidate products to the order query module 1211 of the merchant platform.

[0406] (4) The order query module 1211 of the merchant platform sends an overview of multiple candidate products to the order query module 1201 of the distribution server 22.

[0407] After receiving user data from electronic device 100, order query module 1201 can identify multiple candidate products. These candidate products can be combined arbitrarily to form product combinations. For example, order query module 1201 can determine multiple specified products based on user data from electronic device 100. Order query module 1201 can then use specified products that support mutual combinations as candidate products.

[0408] After the order query module 1201 identifies multiple candidate products, it can obtain overview data of these candidate products through the order query module 1211. This overview data may include, but is not limited to, product inventory, product price, and product details. The order query module 1201 can send product identifiers of the multiple candidate products to the order query module 1211. Upon receiving the product identifiers of the multiple candidate products, the order query module 1211 can send probability data of those candidate products to the order query module 1201.

[0409] In some examples, the product identifiers in the order query module 1201 and the order query module 1211 may be different. The order query module 1201 may store the mapping relationship between the product identifiers in the distribution server 22 and the product identifiers in the merchant platform, so that the distribution server 22 can determine the corresponding product in the merchant platform.

[0410] Optionally, the order query module 1201 can be used to query product combination orders purchased by the electronic device 100. The order query module 1211 can send relevant information about product combination orders to the order query module 1201. In this way, the distribution server 22 can recommend products from the purchased product combinations to the user of the electronic device 100.

[0411] (5) The order query module 1201 of the distribution server 22 sends configuration data of multiple candidate products to the electronic device 100.

[0412] The order query module 1201 of the distribution server 22 can send configuration data of multiple candidate products to the electronic device 100 after obtaining overview data of multiple candidate products.

[0413] It should be noted that the step of order query module 1201 obtaining probability data through order query module 1211 is optional. When the merchant platform uploads products, distribution server 22 can store relevant product data. Based on the stored relevant data of candidate products, distribution server 22 can determine the configuration data of candidate products and then send the configuration data to electronic device 100. For a description of how distribution server 22 obtains the configuration data of products, please refer to the description of distribution server 22 obtaining the configuration data of product combinations; it will not be repeated here.

[0414] (6) Electronic device 100 receives input to select multiple candidate products.

[0415] After receiving configuration data for multiple candidate products, electronic device 100 can display those candidate products. For example, a description of electronic device 100 displaying multiple candidate products can be found here. Figure 4A The embodiment shown in (a) shows that the input for selecting multiple candidate items can be a selection of... Figure 4A The input of multiple cards is shown in (b).

[0416] (7) Electronic device 100 sends user identifier and product identifier of multiple candidate products to product information query module 1101 of distribution server 22.

[0417] After receiving input to select multiple candidate products, the electronic device 100 can send the user identifier and the product identifiers of the multiple candidate products selected by the user to the product information query module 1101 of the distribution server 22.

[0418] (8) The product information query module 1101 of the distribution server 22 obtains the details of multiple candidate products from the product information query module 1212 of the merchant platform.

[0419] The product information query module 1101 of the distribution server 22 can obtain detailed data of multiple candidate products from the product information query module 1212 of the merchant platform after receiving the product identifiers of multiple candidate products.

[0420] (9) The product information query module 1101 of the distribution server 22 sends the configuration data of the product combination to the electronic device 100. The product combination includes multiple candidate products selected by the user.

[0421] The product information query module 1101 of the distribution server 22 can send configuration data of a product combination to the electronic device 100 after obtaining detailed data of multiple candidate products. The product combination includes multiple candidate products selected by the user. In this way, the product information query module 1101 can obtain the latest product data from the merchant platform.

[0422] It should be noted that the product information query module 1101 of the distribution server 22 can also obtain the configuration data of the product combination from the storage module 1103 of the distribution server 22. In this way, since the storage module 1103 has pre-stored the configuration data, the distribution server 22 can update the configuration data in the storage module 1103 when the merchant platform updates the product details data. This eliminates the need to retrieve the details data only when the user selects a product, saving display time.

[0423] (10) Electronic device 100 receives input of purchased product combination.

[0424] After receiving the configuration data for the product combination, the electronic device 100 can display the corresponding product combination. For example, see [link to example]. Figure 4B The embodiment shown in (a) is as follows.

[0425] (11) Electronic device 100 sends a user identifier, a product combination identifier, and a product price to the payment platform. The user identifier is used to indicate the payment account of electronic device 100.

[0426] After receiving input indicating the purchase of a product combination, electronic device 100 can send a user identifier, a product combination identifier, and the product price to the payment platform. The user identifier indicates the payment account of electronic device 100.

[0427] After receiving the user identifier, product combination identifier, and product price, the payment platform can generate a product combination order for purchasing the product combination. The payment platform can also set an order identifier for the product combination order.

[0428] After a product combination order is generated, the payment platform can transfer the payment for the product combination from the payment account of the electronic device 100 to the receiving account of the payment platform.

[0429] Optionally, the payment platform can determine the payment binding relationship of all products in the product combination based on the product combination identifier, thereby determining the receiving account of the merchant platform to which all products in the product combination belong.

[0430] Optionally, the configuration data for the product combination may include a payment binding relationship or an account binding identifier. When the electronic device 100 sends the user identifier, product combination identifier, and product price to the payment platform, it may also send a payment binding relationship or an account binding identifier to the payment platform.

[0431] (12) The payment platform sends the user identifier and product identifier to the payment module 1213 of the merchant platform.

[0432] After receiving payment for the product bundle, the payment platform can purchase the bundled products on the merchant platform. Specifically, the payment platform sends a user identifier and a product identifier to the merchant platform's payment module 1213. The user identifier indicates the account using the product, and the product identifier indicates the purchased product. The payment module 1213 can then be used to facilitate the sale of these products.

[0433] The payment platform can transfer the payment for goods from the payment platform's receiving account to the merchant platform's receiving account, enabling the purchase of goods in a product bundle.

[0434] (13) The merchant platform's payment module 1213 sends the payment result to the payment platform. The payment result is used to indicate whether the corresponding goods have been successfully purchased.

[0435] The merchant platform's payment module 1213 can send a payment result to the payment platform after the payment operation is executed. The payment result indicates whether the purchase of the corresponding goods was successful. Specifically, if the payment platform successfully pays the money, the payment result indicates that the purchase of the corresponding goods was successful. If the payment platform fails to pay the money, the payment result indicates that the purchase of the corresponding goods failed.

[0436] (14) The payment platform sends the user identifier, order identifier, product combination identifier and payment result to the electronic device 100.

[0437] After receiving the payment result returned by the payment module 1213, the payment platform can send the user identifier, order identifier, product combination identifier, and payment result to the electronic device 100. The electronic device 100 can then display the payment result. For example, see [link to relevant documentation]. Figure 4C The illustrated embodiment.

[0438] In this way, by following the steps above, multiple products can be combined into one product bundle, achieving the effect of purchasing multiple products at once.

[0439] Figure 13 A schematic diagram of the structure of the electronic device 100 is shown.

[0440] The following description uses electronic device 100 as an example to illustrate the embodiment. It should be understood that... Figure 13 The electronic device 100 shown is merely an example, and the electronic device 100 may have more than Figure 13 The more or fewer components shown can be combined into two or more components, or they can have different component configurations. Figure 13The various components shown can be implemented in hardware, software, or a combination of hardware and software, including one or more signal processing and / or application-specific integrated circuits.

[0441] Electronic device 100 may include processor 110, external memory interface 120, internal memory 121, universal serial bus (USB) interface 130, charging management module 140, power management module 141, battery 142, antenna 1, antenna 2, mobile communication module 150, wireless communication module 160, audio module 170, speaker 170A, receiver 170B, microphone 170C, headphone jack 170D, sensor module 180, button 190, motor 191, indicator 192, camera 193, display screen 194, and subscriber identification module (SIM) card interface 195, etc. The sensor module 180 may include a pressure sensor 180A, a gyroscope sensor 180B, a barometric pressure sensor 180C, a magnetic sensor 180D, an accelerometer sensor 180E, a distance sensor 180F, a proximity sensor 180G, a fingerprint sensor 180H, a temperature sensor 180J, a touch sensor 180K, an ambient light sensor 180L, a bone conduction sensor 180M, etc.

[0442] It is understood that the structures illustrated in the embodiments of this application do not constitute a specific limitation on the electronic device 100. In other embodiments of this application, the electronic device 100 may include more than Figure 13 This may involve more or fewer components, or combining certain components, or splitting certain components, or different component arrangements. Figure 13 The components shown can be implemented in hardware, software, or a combination of both.

[0443] Processor 110 may include one or more processing units, such as application processors (APs), modem processors, graphics processing units (GPUs), image signal processors (ISPs), controllers, video codecs, digital signal processors (DSPs), baseband processors, and / or neural network processing units (NPUs). These different processing units may be independent devices or integrated into one or more processors.

[0444] The controller can generate operation control signals based on the instruction opcode and timing signals to complete the control of instruction fetching and execution.

[0445] The processor 110 may also include a memory for storing instructions and data. In some embodiments, the memory in the processor 110 is a cache memory. This memory can store instructions or data that the processor 110 has just used or that are used repeatedly. If the processor 110 needs to use the instruction or data again, it can retrieve it directly from the memory. This avoids repeated accesses, reduces the waiting time of the processor 110, and thus improves the efficiency of the system.

[0446] In some embodiments, the processor 110 may include one or more interfaces. Interfaces may include an inter-integrated circuit (I2C) interface, an inter-integrated circuit sound (I2S) interface, a pulse code modulation (PCM) interface, a universal asynchronous receiver / transmitter (UART) interface, a mobile industry processor interface (MIPI), a general-purpose input / output (GPIO) interface, a subscriber identity module (SIM) interface, and / or a universal serial bus (USB) interface, etc.

[0447] It is understood that the interface connection relationships between the modules illustrated in the embodiments of this application are merely illustrative and do not constitute a structural limitation on the electronic device 100. In other embodiments of this application, the electronic device 100 may also employ different interface connection methods or combinations of multiple interface connection methods as described in the above embodiments.

[0448] The charging management module 140 receives charging input from a charger. The charger can be a wireless charger or a wired charger. In some wired charging embodiments, the charging management module 140 receives charging input from the wired charger via the USB interface 130. In some wireless charging embodiments, the charging management module 140 receives wireless charging input via the wireless charging coil of the electronic device 100. While charging the battery 142, the charging management module 140 can also supply power to the electronic device via the power management module 141.

[0449] The power management module 141 connects the battery 142, the charging management module 140, and the processor 110. The power management module 141 receives input from the battery 142 and / or the charging management module 140, providing power to the processor 110, internal memory 121, display screen 194, camera 193, and wireless communication module 160, etc. The power management module 141 can also monitor parameters such as battery capacity, battery cycle count, and battery health status (leakage current, impedance). In some other embodiments, the power management module 141 may also be located within the processor 110. In other embodiments, the power management module 141 and the charging management module 140 may be located in the same device.

[0450] The wireless communication function of electronic device 100 can be realized through antenna 1, antenna 2, mobile communication module 150, wireless communication module 160, modem processor and baseband processor, etc.

[0451] Antenna 1 and antenna 2 are used to transmit and receive electromagnetic wave signals. Each antenna in electronic device 100 can be used to cover one or more communication frequency bands. Different antennas can also be multiplexed to improve antenna utilization. For example, antenna 1 can be multiplexed as a diversity antenna for a wireless local area network. In some other embodiments, the antennas can be used in conjunction with tuning switches.

[0452] The mobile communication module 150 can provide solutions for wireless communication, including 2G / 3G / 4G / 5G, applied to the electronic device 100. The mobile communication module 150 may include at least one filter, switch, power amplifier, low noise amplifier (LNA), etc. The mobile communication module 150 can receive electromagnetic waves via antenna 1, and perform filtering, amplification, and other processing on the received electromagnetic waves before transmitting them to a modem processor for demodulation. The mobile communication module 150 can also amplify the signal modulated by the modem processor and convert it into electromagnetic waves for radiation via antenna 1. In some embodiments, at least some functional modules of the mobile communication module 150 may be housed in the processor 110. In some embodiments, at least some functional modules of the mobile communication module 150 and at least some modules of the processor 110 may be housed in the same device.

[0453] The modem processor may include a modulator and a demodulator. The modulator modulates the low-frequency baseband signal to be transmitted into a mid-to-high frequency signal. The demodulator demodulates the received electromagnetic wave signal into a low-frequency baseband signal. The demodulator then transmits the demodulated low-frequency baseband signal to the baseband processor for processing. After processing by the baseband processor, the low-frequency baseband signal is transmitted to the application processor. The application processor outputs sound signals through an audio device (not limited to speaker 170A, receiver 170B, etc.) or displays images or videos through the display screen 194. In some embodiments, the modem processor may be a separate device. In other embodiments, the modem processor may be independent of the processor 110 and may be housed in the same device as the mobile communication module 150 or other functional modules.

[0454] The wireless communication module 160 can provide solutions for wireless communication applications on the electronic device 100, including wireless local area networks (WLANs) (such as wireless fidelity (Wi-Fi) networks), Bluetooth (BT), global navigation satellite system (GNSS), frequency modulation (FM), near field communication (NFC), and infrared (IR) technologies. The wireless communication module 160 can be one or more devices integrating at least one communication processing module. The wireless communication module 160 receives electromagnetic waves via antenna 2, performs frequency modulation and filtering of the electromagnetic wave signals, and sends the processed signal to processor 110. The wireless communication module 160 can also receive signals to be transmitted from processor 110, perform frequency modulation and amplification, and convert them into electromagnetic waves for radiation via antenna 2.

[0455] In some embodiments, antenna 1 of electronic device 100 is coupled to mobile communication module 150, and antenna 2 is coupled to wireless communication module 160, enabling electronic device 100 to communicate with networks and other devices via wireless communication technology. Wireless communication technology may include Global System for Mobile Communications (GSM), General Packet Radio Service (GPRS), Code Division Multiple Access (CDMA), Wideband Code Division Multiple Access (WCDMA), Time-Division Code Division Multiple Access (TD-SCDMA), Long Term Evolution (LTE), BT, GNSS, WLAN, NFC, FM, and / or IR technologies, etc. GNSS can include the Global Positioning System (GPS), the Global Navigation Satellite System (GLONASS), the BeiDou Navigation Satellite System (BDS), the Quasi-Zenith Satellite System (QZSS), and / or satellite-based augmentation systems (SBAS).

[0456] Electronic device 100 implements display functions through a GPU, a display screen 194, and an application processor. The GPU is a microprocessor for image processing, connected to the display screen 194 and the application processor. The GPU is used to perform mathematical and geometric calculations and for graphics rendering. Processor 110 may include one or more GPUs, which execute program instructions to generate or modify display information.

[0457] Display screen 194 is used to display images, videos, etc. Display screen 194 includes a display panel. The display panel may be a liquid crystal display (LCD), an organic light-emitting diode (OLED), an active-matrix organic light-emitting diode (AMOLED), a flexible light-emitting diode (FLED), a miniature LED, a microLED, a quantum dot light-emitting diode (QLED), etc. In some embodiments, electronic device 100 may include one or N displays 194, where N is a positive integer greater than 1.

[0458] Electronic device 100 can perform shooting functions through ISP, camera 193, video codec, GPU, display 194 and application processor.

[0459] The ISP (Image Signal Processor) is used to process data fed back from the camera 193. For example, when taking a picture, the shutter is opened, and light is transmitted through the lens to the camera's photosensitive element. The light signal is converted into an electrical signal, and the camera's photosensitive element transmits the electrical signal to the ISP for processing, transforming it into an image visible to the naked eye. The ISP can also perform algorithmic optimization on image noise and brightness. The ISP can also optimize parameters such as exposure and color temperature of the shooting scene. In some embodiments, the ISP can be set in the camera 193.

[0460] Camera 193 is used to capture still images or videos. An object passes through the lens to generate an optical image that is projected onto a photosensitive element. The photosensitive element converts the light signal into an electrical signal, which is then passed to an ISP (Internet Service Provider) for conversion into a digital image signal. The ISP outputs the digital image signal to a DSP (Digital Signal Processor) for processing. The DSP converts the digital image signal into image signals in standard formats such as RGB and YUV. In some embodiments, the electronic device 100 may include one or N cameras 193, where N is a positive integer greater than 1.

[0461] Digital signal processors (DSPs) are used to process digital signals. Besides digital image signals, they can also process other digital signals. For example, when electronic device 100 selects a frequency, the DSP can perform Fourier transforms on the frequency energy.

[0462] Video codecs are used to compress or decompress digital video. Electronic device 100 may support one or more video codecs. Thus, electronic device 100 can play or record videos in various encoding formats, such as Moving Picture Experts Group (MPEG) 1, MPEG2, MPEG3, MPEG4, etc.

[0463] An NPU (Neural Processing Unit) is a computational processor for neural networks (NNs). By borrowing the structure of biological neural networks, such as the transmission patterns between neurons in the human brain, it can rapidly process input information and continuously learn on its own. NPUs can enable intelligent cognitive applications in electronic devices, such as image recognition, facial recognition, speech recognition, and text understanding.

[0464] Internal memory 121 can be used to store computer executable program code, which includes instructions. Processor 110 executes various functional applications and data processing of electronic device 100 by running the instructions stored in internal memory 121. Internal memory 121 may include a program storage area and a data storage area. The program storage area may store the operating system, at least one application program required for a function (such as sound playback, image playback, etc.), etc. The data storage area may store data created during the use of electronic device 100 (such as audio data, phonebook, etc.). Furthermore, internal memory 121 may include high-speed random access memory and may also include non-volatile memory, such as at least one disk storage device, flash memory device, universal flash storage (UFS), etc.

[0465] Electronic device 100 can implement audio functions, such as music playback and recording, through audio module 170, speaker 170A, receiver 170B, microphone 170C, headphone jack 170D, and application processor.

[0466] Audio module 170 is used to convert digital audio information into analog audio signal output, and also to convert analog audio input into digital audio signal. Speaker 170A, also called a "loudspeaker," is used to convert audio electrical signals into sound signals. Receiver 170B, also called a "handpiece," is used to convert audio electrical signals into sound signals. Microphone 170C, also called a "microphone" or "voice transducer," is used to convert sound signals into electrical signals. Headphone jack 170D is used to connect wired headphones.

[0467] When pressure sensor 180A is used to sense pressure signals, it can convert the pressure signals into electrical signals. In some embodiments, pressure sensor 180A can be disposed on display screen 194. Gyroscope sensor 180B can be used to determine the motion posture of electronic device 100. Barometric pressure sensor 180C is used to measure barometric pressure. Magnetic sensor 180D includes a Hall sensor and can be used to detect the opening and closing of the flip cover. Accelerometer 180E can detect the magnitude of acceleration of electronic device 100 in various directions (generally three axes). Distance sensor 180F is used to measure distance. Proximity sensor 180G can also be used for automatic unlocking and locking in flip cover mode and pocket mode. Ambient light sensor 180L is used to sense ambient light brightness. Fingerprint sensor 180H is used to collect fingerprints. Temperature sensor 180J is used to detect temperature. Touch sensor 180K, also called "touch panel". Touch sensor 180K can be disposed on display screen 194, and touch sensor 180K and display screen 194 constitute a touch screen, also called "touch screen". A touch sensor 180K is used to detect touch operations applied to or near it. The touch sensor can transmit the detected touch operation to the application processor to determine the type of touch event. Visual output related to the touch operation can be provided via the display screen 194. In some embodiments, the touch sensor 180K may also be located on the surface of the electronic device 100, in a different position than the display screen 194. A bone conduction sensor 180M can acquire vibration signals. Buttons 190 include a power button, volume buttons, etc. A motor 191 can generate vibration cues. An indicator 192 may be an indicator light, used to indicate charging status, battery level changes, or messages, missed calls, notifications, etc. A SIM card interface 195 is used to connect a SIM card.

[0468] In this application embodiment, the operation (input) may include operations (inputs) generated by simulated humans, such as intelligent agents, robots, artificial intelligence, and automated machines. This application embodiment does not limit this.

[0469] This application also provides a computer-readable storage medium storing a computer program, which, when executed by a processor, can implement the steps in the above-described method embodiments.

[0470] This application also provides a computer program product, including a computing program, which, when run on a processor, can implement the steps in the above-described method embodiments.

[0471] This application also provides a chip system, which includes a processing circuit interface circuit. The interface circuit receives code instructions and transmits them to the processing circuit. The processing circuit executes the code instructions to enable the chip system to implement the steps of any method embodiment of this application. The chip system can be a single chip or a chip module composed of multiple chips.

[0472] The above embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit it. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of this application.

Claims

1. A processing method applied to a first electronic device, characterized in that, The method includes: Receive user input to trigger the first electronic device to display the first interface; In response to the user input, configuration data for multiple product combinations is obtained from the first server. Each product combination includes multiple products, and the multiple product combinations are set by one or more merchant platforms on the first server. Based on the configuration data of the multiple product combinations, the first interface is displayed; wherein, the first interface includes multiple fusion cards, one fusion card corresponds to one product combination, the multiple fusion cards include a first fusion card, the first fusion card includes a first product combination, and the multiple products included in the first product combination belong to different merchant platforms. Receive the first input to the first fusion card; Upon receiving the first input, a first payment request is generated, and settlement processing for the first product combination is triggered based on the first payment request.

2. The method according to claim 1, characterized in that, Upon receiving the first input, generating a first payment request and triggering settlement processing for the first product combination based on the first payment request includes: In response to the first input, a payment interface is displayed, the payment interface including the first product combination and payment controls; Receive a second input to the payment control; In response to the second input, the first payment request is generated, and settlement processing for the first product combination is triggered based on the first payment request.

3. The method according to claim 1, characterized in that, The configuration data for the first product combination includes one or more of the following: a first display style for the first product combination and content data for all products in the first product combination. The content data includes one or more of the following: product name, product category, product description, product price, product inventory, and product image. Displaying the first interface includes: Based on the configuration data of the first product combination, the first fusion card is displayed.

4. The method according to claim 1, characterized in that, The step of generating the first payment request and triggering settlement processing for the first product combination based on the first payment request includes: A first payment request is sent to a first server, the first payment request indicating that the first electronic device is purchasing the first product combination, and instructing the first server to transfer the payment for the first product combination from the first payment account associated with the user who logged into the first electronic device to the first receiving account indicated by the first server.

5. The method according to any one of claims 1-4, characterized in that, The method further includes: Display multiple candidate cards, including a first candidate card and a second candidate card, wherein the first candidate card is used to purchase a third item and the second candidate card is used to purchase a fourth item; Receive a third input that selects the first candidate card and the second candidate card; In response to the third input, a second fusion card is displayed, the second fusion card including a second product combination, the second product combination including the third product and the fourth product; A fourth input to the second fusion card was received; Upon receiving the fourth input, a second payment request is generated, and settlement processing for the second product combination is triggered based on the second payment request.

6. The method according to claim 5, characterized in that, The display of multiple candidate cards includes: The configuration data of multiple candidate products are obtained from the first server, wherein the multiple candidate products include the third product and the fourth product; Based on the configuration data of the multiple candidate products, the multiple candidate cards are displayed.

7. A processing method applied to a first server, characterized in that, The method includes: Receive multiple product combinations set by one or more merchant platforms, each product combination including multiple products; The configuration data of multiple product combinations is sent to the first electronic device. The multiple product combinations sent to the first electronic device include the first product combination. The multiple products included in the first product combination belong to different merchant platforms. The configuration data of the first product combination is used by the first electronic device to display the first fusion card. The first fusion card is used to trigger the first electronic device to send the first payment request to the first server. Receive the first payment request sent by the first electronic device, wherein the first payment request is used to indicate that the first electronic device is purchasing the first product combination; Upon receiving the first payment request, the payment for the first product combination is obtained from the first payment account associated with the user who logged into the first electronic device, and the payment is used to settle the payment for the products in the first product combination with the different merchant platforms.

8. The method according to claim 7, characterized in that, The different merchant platforms include a first merchant platform; prior to sending configuration data for multiple product combinations to the first electronic device, the method further includes: Receive the first query request sent by the first merchant platform; Send a first product list to the first merchant platform, the first product list including products in the first product combination; Receive the first product combination sent by the first merchant platform.

9. The method according to claim 8, characterized in that, After receiving the first product combination sent by the first merchant platform, the method further includes: The system receives a first display style for the first merchant combination sent by the first merchant platform. The first display style is used to indicate whether to display the package contents of the product, the coupon of the product, and the name of the product when displaying the first product combination. The configuration data of the first product combination includes the first display style.

10. The method according to claim 8, characterized in that, Before sending configuration data for multiple product combinations to the first electronic device, the method further includes: The system receives detailed data of one or more products uploaded by the first merchant platform. The one or more products include at least one product from the first product combination. The detailed data includes a product identifier and a merchant platform identifier, which indicates the merchant platform to which the product belongs.

11. The method according to claim 10, characterized in that, After receiving the details data of one or more products uploaded by the first merchant platform, the method further includes: Receive first permission information sent by the first merchant platform, the first permission information being used to indicate that the merchant platform is allowed to add the products of the first merchant platform to the product portfolio; Sending the first product list to the first merchant platform includes: Based on the merchant platform identifier of the first merchant platform and the product permission information stored on the first server, the first product list is determined. The first product list includes products that are allowed to be added to the product portfolio by the first merchant platform.

12. The method according to claim 8, characterized in that, Before receiving the first product combination sent by the first merchant platform, the method further includes: The system receives a first payment agreement signing request from the first merchant platform. The first payment agreement signing request is used to set the first server to distribute the payment for the goods belonging to the first merchant platform in the product combination to the first merchant platform. The system stores a first payment binding relationship, which is used to indicate the first receiving account associated with the first server and the second receiving account of the first merchant platform, and to instruct the first server to transfer the payment for goods in the first merchant platform from the first payment account to the second receiving account through the first receiving account.

13. The method according to claim 7, characterized in that, Sending configuration data for multiple product combinations to the first electronic device includes: Based on the user data of the first electronic device, the plurality of product combinations are selected from the stored product combinations; wherein, the user data includes one or more of the following: user identifier and the location of the first electronic device; The configuration data of the multiple product combinations is sent to the first electronic device.

14. The method according to claim 13, characterized in that, The multiple product combinations include one or more of the products purchased by the first electronic device and products near the location of the first electronic device.

15. The method according to claim 7, characterized in that, The first product combination includes a first product from a first merchant platform; the step of obtaining payment for the first product combination from a first payment account associated with a user logged into the first electronic device, and using the payment to settle accounts with the multiple merchant platforms for the products in the first product combination, includes: The payment for the first combination of goods is transferred from the first payment account to the first receiving account indicated by the first server; The payment for the first product is transferred from the first receiving account to the second receiving account indicated by the first merchant platform.

16. The method according to claim 15, characterized in that, The first payment request carries the first payment account and the identifier of the first product combination; the step of transferring the payment for the first product combination from the first payment account to the first receiving account indicated by the first server includes: Based on the first product combination identifier, the payment binding relationship of all products in the first product combination is determined. The payment binding relationship is used to indicate the first receiving account associated with the first server and the receiving account of the merchant platform to which the product belongs, and is used to instruct the first server to transfer the payment of the product from the payment account to the receiving account of the merchant platform through the first receiving account; the payment binding relationship of the first product is used to indicate the second receiving account of the first merchant platform. After determining the payment binding relationship of all products in the first product combination, the payment for the first product combination is transferred from the first payment account to the first receiving account. The step of transferring the payment for the first product from the first receiving account to the second receiving account indicated by the first merchant platform includes: After transferring the payment for the first combination of goods from the first payment account to the first receiving account, the payment for the first goods is transferred from the first receiving account to the second receiving account.

17. The method according to claim 7, characterized in that, The method further includes: The configuration data of multiple candidate products are sent to the first electronic device, the multiple candidate products including a third product and a fourth product; The first electronic device receives a first fusion request, the first fusion request carrying the product identifier of the third product and the product identifier of the fourth product; The configuration data of the second product combination, which includes the third product and the fourth product, is sent to the first electronic device. The configuration data of the second product combination is used by the first electronic device to display a second fusion card, which is used to purchase the second product combination.

18. The method according to claim 17, characterized in that, After sending the configuration data of the second product combination to the first electronic device, the method further includes: Receive a second payment request sent by the first electronic device, the second payment request being used to identify that the first electronic device has purchased the second product combination; Upon receiving the second payment request, the payment for the second product combination is obtained from the first payment account, and the payment for the second product combination is used to settle accounts with multiple merchant platforms for the products in the second product combination.

19. The method according to claim 7, characterized in that, The configuration data of the first product combination includes one or more of the display style of the first product combination and the content data of all products in the first product combination. The content data includes one or more of the following: product name, product category, product description, product price, product inventory, and product image.

20. A communication system, characterized in that, Includes a first electronic device and a first server; wherein, The first electronic device is configured to perform the processing method as described in any one of claims 1-6; The first server is configured to perform the processing method as described in any one of claims 7-19.

21. An electronic device, characterized in that, include: One or more processors and one or more memories, wherein the one or more memories are coupled to the one or more processors, and the one or more memories are used to store a computer program, which, when the one or more processors execute the computer program, performs the processing method as described in any one of claims 1-6.

22. A computer-readable storage medium, characterized in that, The device contains a computer program that, when executed by a processor, implements the processing method as described in any one of claims 1-6.

23. A computer program product, characterized in that, Includes a computer program that, when executed by a processor, implements the processing method as described in any one of claims 1-6.

24. A chip system, characterized in that, It includes a processing circuit and an interface circuit, wherein the interface circuit is used to receive code instructions and transmit them to the processing circuit, and the processing circuit is used to execute the code instructions to perform the processing method as described in any one of claims 1-6.

Images