Interface display method and apparatus

Abstract

The present application relates to the technical field of terminal devices, and provides an interface display method and apparatus. The method comprises: when a user requests to purchase digital goods on a first interface, displaying, on the basis of a goods identifier and a first calling interface that are associated with the first interface, a second interface comprising payment description information of the digital goods. The payment and transaction of the digital goods are implemented outside an application to which the digital goods belong, the process of responding to the purchase request for the digital goods is also simplified, and the complexity of the purchase process of the digital goods is reduced, and thus, user experience is good.

Description

Interface display method and device

[0001] This application claims priority to Chinese Patent Application No. 202510245908.7, filed on February 28, 2025, entitled "Interface Display Method and Apparatus", the entire contents of which are incorporated herein by reference. Technical Field

[0002] This application relates to the field of terminal device technology, and in particular to an interface display method and apparatus. Background Technology

[0003] With the advancement of computer and network communication technologies, information is increasingly being digitized and rapidly disseminated, leading to the growing popularity of digital goods transactions via the internet. Digital goods refer to goods that exist in electronic form and are distributed and consumed through the internet. Digital goods do not require physical carriers and can be verified electronically and delivered instantly.

[0004] Typically, the process of purchasing digital goods offered by an app requires switching from the app or interface that recommends the digital goods to the app that offers them. After switching to the app that offers the digital goods, the user needs to log in to the app before the transaction interface (such as the payment interface) for the digital goods can be loaded within that app.

[0005] However, switching between different applications or interfaces takes a long time, as does logging into the application and loading the transaction interface. This can easily lead to an overly cumbersome and complex response process for digital goods transaction requests, resulting in long response times. Summary of the Invention

[0006] To address the aforementioned technical problems, this application provides a method and apparatus for displaying an interface. In this method, a first interface is associated with a product identifier for a digital product and a first interface indicating the invocation of a system service. When a user requests to purchase the digital product on the first interface, a second interface containing payment description information for the digital product can be displayed based on the product identifier associated with the first interface and the first interface. This eliminates the need to prompt the user to log in to a first application and switch the application interface to the first application for transaction and payment. It avoids the loading process of the second interface within the first application. Thus, not only is payment and transaction of the digital product realized outside the application to which the digital product belongs, but the response process to purchase requests for digital products is also simplified, and the complexity of the purchase process is reduced, resulting in a better user experience.

[0007] In a first aspect, this application provides a method for displaying an interface. The method includes: displaying a first interface, the first interface including product description information of a digital product, the first interface being associated with a product identifier of the digital product and a first interface indicating the invocation of a system service, the first interface being different from the application interface of a first application providing the digital product; responding to received first user input on the first interface, displaying a second interface based on the product identifier and the first interface, the first user input indicating a request to purchase the digital product, the system service indicating the acquisition of payment description information of the digital product based on the product identifier, the second interface including the payment description information.

[0008] In one possible implementation, a product identifier can serve as a unique identifier for digital goods, distinguishing them from different digital products. As an example, the product identifier for a digital product could consist of a combination of numbers and / or letters.

[0009] In one possible implementation, the product description information may be information that describes some attributes of the digital product. For example, the product description information may include, but is not limited to: product name, application, pricing, currency, discounted price (e.g., the price after discount), discount information (e.g., discount rate or coupon information).

[0010] In one possible implementation, the payment description information can provide details about the transaction of the digital goods. For example, the payment description information may include, but is not limited to, information about the digital goods to be paid, such as the amount due, payment method (e.g., third-party payment or bank card), product name, and quantity.

[0011] For example, the first interface can be bound to the product identifier of the digital product and the first interface, so that the first interface is associated with the product identifier and the first interface.

[0012] For example, the system service could be an out-of-application payment service, and the first interface could be associated with a first interface that indicates how to call the out-of-application payment service.

[0013] For example, the second interface could be the checkout interface for digital goods.

[0014] Unlike related technologies where the initial interface recommending a digital product is not the application interface of the app that owns the product (i.e., when the digital product is recommended from outside the app), the display needs to be switched from the initial interface to the application interface of the app that provides the digital product (also known as the app that owns the digital product) to enable payment and transaction within the app. This means users need to log in to the first app when switching apps, and the client needs to wait for the first app to load the application interface that provides the digital product before they can conduct the transaction, making the process cumbersome.

[0015] In this implementation, although the first interface recommending the digital product is not the application interface of the application to which the digital product belongs (the first application), the first interface may be associated with the product identifier of the digital product and a first interface indicating the invocation of an external payment service (a system service). Therefore, when a user requests to purchase the digital product on the first interface, the method of this embodiment can display a second interface containing payment description information of the digital product based on the product identifier associated with the first interface and the aforementioned first interface. This second interface could, for example, be the cashier interface for the digital product.

[0016] Thus, when a user purchases the digital goods, the method of this embodiment does not require prompting the user to log in to the first application and switching the application interface to the first application's interface for the transaction and payment of the digital goods. For example, it eliminates the need to display the second interface within the first application and avoids the loading process of the second interface within the first application. This not only enables payment and transaction of the digital goods outside the application to which the digital goods belong, but also simplifies the response process to purchase requests for digital goods, reduces the cumbersomeness of the purchase process, and provides a better user experience.

[0017] Furthermore, when a user requests to purchase a product outside the first application, this invention does not redirect the user to the first application. Instead, it allows the user to directly access the system service outside the application by utilizing the product ID and interface associated with the first interface. This system service then launches the payment interface for the product (example of the second interface). This enables product transactions to be completed outside the application, eliminating the need to switch the foreground application to the first application. It avoids processes such as application login and loading the digital product interface, simplifying the process and shortening the transaction time for digital products.

[0018] In one possible implementation, displaying a second interface based on a product identifier and a first interface includes: passing the product identifier to the first interface and calling the system service through the first interface to display the second interface.

[0019] In this implementation, after the product identifier is passed to the first interface, the system service can be called through the first interface to determine the payment description information of the digital product based on the product identifier. Then, a second interface containing the payment description information of the digital product can be displayed through the first interface. There is no need to prompt the user to log in to the first application and switch the application interface to the first application for the transaction and payment of the digital product, thus avoiding the loading process of the second interface within the first application. In this way, not only is the payment and transaction of the digital product realized outside the application to which the digital product belongs, but the response process to the purchase request of the digital product is also simplified, and the cumbersomeness of the purchase process is reduced, resulting in a better user experience.

[0020] In one possible implementation, the first interface is the application interface of the second application, and the first application is different from the second application.

[0021] For example, the second application may recommend multiple digital products, and the products recommended by the second application may include the aforementioned digital products.

[0022] For example, the first application is for suppliers of the aforementioned digital goods.

[0023] As an example, a digital product could be a song, the first application could be a music application, the second application could be a reading application, and the first interface could be the interface of the reading application.

[0024] In this implementation, the first interface recommends the digital product corresponding to its associated product identifier. The second application can recommend products that include the aforementioned digital product, and the supplier of the digital product is the first application. This allows the recommendation and transaction of the digital product to be implemented within the application interface of an application other than the one providing the digital product, enabling transactions of digital products provided by the first application to be conducted outside of the first application, thus avoiding switching between applications. Furthermore, it avoids the issues of logging into the first application and loading the application interface for the digital product, reducing the complexity of the response process for purchasing digital products and shortening the response time, resulting in a better user experience.

[0025] In one possible implementation, displaying a second interface based on a product identifier and a first interface includes: displaying the second interface within the application interface of a second application based on the product identifier and the first interface.

[0026] For example, the second interface, also known as the checkout interface, can provide payment functionality for digital goods. This second interface can be the application interface of the second application, or a sub-interface such as a window within the application interface of the second application; there are no restrictions.

[0027] This approach avoids switching from the second application to the first, as well as the need to log in to the first application and load the second interface within it, when recommending digital goods provided by the first application within the second application. This not only enables payment and transaction of digital goods outside of their original application but also simplifies the response process to purchase requests and reduces the complexity of the purchase process, resulting in a better user experience.

[0028] In one possible implementation, the first interface is a notification message interface.

[0029] For example, the notification message can be a pop-up message (i.e., a notification message displayed on the lock screen), then the first screen can be the lock screen; or, the notification message can be a notification message in the pull-down notification bar, then the first screen can be the pull-down notification bar screen; or, the notification message can be an SMS message, then the first screen can be the display screen of the SMS application.

[0030] In this implementation, the first interface recommends the digital product corresponding to its associated product identifier. When purchasing a digital product offered by an application via a notification message, switching from the notification message interface to the first application offering the digital product is avoided. Furthermore, the payment interface is not displayed until after logging into the first application and the application loading the interface offering the digital product. This reduces the complexity of the response process for digital product purchase requests and the response time, resulting in a better user experience.

[0031] In one possible implementation, the method further includes: displaying a third interface based on payment description information, the third interface including information indicating the completion of a digital goods transaction provided by the first application, the third interface being different from the application interface of the first application.

[0032] For example, the information provided by the first application regarding the completion of digital goods transactions includes, but is not limited to: product name, payment amount, and product quantity.

[0033] In this implementation, a third interface containing information indicating the completion of a digital goods transaction provided by the first application can be displayed outside the first application based on payment description information. This third interface could be, for example, a payment success interface. This eliminates the need to switch the foreground application to the first application, simplifying the process and shortening the time required to use digital goods.

[0034] In one possible implementation, the third interface further includes a second interface that indicates the output of resource information for a digital product. The method further includes: in response to a received second user input to the third interface, calling the second interface to output the resource information of the digital product of the first application, wherein the second user input indicates the use of the digital product.

[0035] For example, resource information for digital goods can be a QR code. Users can scan the QR code to use the digital goods.

[0036] In this implementation, instead of redirecting to the first application, the system operates directly outside the first application. It can respond to input from a second user instructing them to use the digital product and output the digital product's resource information based on a second interface. This allows users to use the digital product outside the first application without switching the foreground application to the first application, avoiding processes such as application login and loading the digital product's interface, simplifying the process and shortening the time spent using the digital product.

[0037] In one possible implementation, outputting the resource information of the digital goods of the first application includes: outputting the resources of the digital goods of the first application on a third interface; or, switching the display interface to a fourth interface of the first application to output the resources of the digital goods on the fourth interface.

[0038] In this implementation, the resources for digital goods can be output on a third interface or a fourth interface of the first application. The third interface differs from the interface of the first application. This allows users to use digital goods both outside and within the first application, expanding the usage scenarios for digital goods.

[0039] Furthermore, using digital goods outside the primary application eliminates the need to switch the foreground application to the primary application, avoiding processes such as application login and loading the digital goods interface, thus simplifying the process and shortening the time required to use digital goods.

[0040] In one possible implementation, the method further includes: based on payment description information, invoking a system service to notify the server of the first application to send resource information of digital goods to the first application.

[0041] As an example, the server of the system service can send a notification message to the server of the first application to notify the server of the first application to send resource information of digital goods to the first application.

[0042] For example, notification messages may include product identifiers, order numbers, user identifiers, etc.

[0043] In this implementation, after a user purchases the digital product on the second interface, they are not redirected to the first application. Instead, they can directly access the system service outside the first application through payment information. The system service then notifies the server of the first application, sending the resource information of the digital product to the first application. This allows the user to use the digital product through the first application. Thus, the transaction can be completed outside the application, eliminating the need to switch the foreground application to the first application, avoiding application login and loading the digital product interface, simplifying the process, and shortening the transaction time.

[0044] Secondly, this application provides an interface display device. The device includes: a display module for displaying a first interface, the first interface including product description information of a digital product, the first interface being associated with a product identifier of the digital product and a first interface indicating the invocation of a system service, the first interface being different from the application interface of a first application providing the digital product; the display module is further configured to respond to received first user input to the first interface, the first interface displaying a second interface based on the product identifier and the first interface, the first user input indicating a request to purchase the digital product, the system service indicating the acquisition of payment description information of the digital product based on the product identifier, and the second interface including the payment description information.

[0045] In one possible implementation, the display module is specifically used to: pass the product identifier to the first interface, and call the system service through the first interface to display the second interface.

[0046] In one possible implementation, the first interface is the application interface of the second application, and the first application is different from the second application.

[0047] In one possible implementation, the display module is specifically used to: display the second interface within the application interface of the second application based on the product identifier and the first interface.

[0048] In one possible implementation, the first interface is a notification message interface.

[0049] In one possible implementation, the display module is also used to display a third interface based on payment description information. The third interface includes information indicating that the digital goods transaction provided by the first application has been completed. The third interface is different from the application interface of the first application.

[0050] In one possible implementation, the third interface further includes a second interface indicating the output of resource information for a digital product. The device also includes an output module for invoking the second interface to output the resource information of the digital product for the first application in response to a received second user input to the third interface, wherein the second user input indicates the use of the digital product.

[0051] In one possible implementation, the output module is specifically used to: output the resources of digital goods of the first application on the third interface; or, switch the display interface to the fourth interface of the first application to output the resources of digital goods on the fourth interface.

[0052] In one possible implementation, the device further includes a notification module, which, based on payment description information, invokes a system service to notify the server of the first application to send resource information of digital goods to the first application.

[0053] The effects of the interface display devices implemented in the above-mentioned ways are similar to the effects of the interface display methods in the first aspect or any of the implementations of the first aspect, and will not be repeated here.

[0054] Thirdly, this application provides an interface display device. The navigation device includes a processor configured to execute instructions, wherein when the instructions are executed by the processor, the processor is configured to perform the method in any of the above implementations.

[0055] In some implementations, the interface display device includes a memory that can store instructions, which, when executed by the processor, are used to perform the method in any of the above implementations.

[0056] In other implementations, the interface display device includes one or more interface circuits; the interface circuits are used to receive signals from a memory and send the signals to the processor, the signals including instructions stored in the memory; when the processor executes the instructions, the processor is used to perform the method in any of the above implementations.

[0057] The effect of the interface display device in this implementation is similar to that of the navigation method in the first aspect or any of the implementations of the first aspect, and will not be described again here.

[0058] Fourthly, this application provides a computer-readable storage medium. The computer-readable storage medium stores a computer program that, when executed on a computer or processor, causes the computer or processor to perform the methods described in any of the above implementations.

[0059] The effect of the computer-readable storage medium of this implementation is similar to that of the interface display method of the first aspect or any implementation of the first aspect, and will not be described again here.

[0060] Fifthly, this application provides a computer program product. The computer program product includes a software program that, when executed by a computer or processor, causes the methods in any of the above implementations to be performed.

[0061] The effect of the computer program product of this implementation is similar to that of the interface display method of the first aspect or any of the implementations of the first aspect, and will not be described again here.

[0062] Sixthly, this application provides a chip. The chip includes a processor and a communication interface, wherein the processor is configured to call and execute instructions from the communication interface, and when the processor executes the instructions, it implements the method in any of the above implementations.

[0063] The effect of the chip in this implementation is similar to that of the interface display method in the first aspect or any of the implementations of the first aspect, and will not be described again here. Attached Figure Description

[0064] Figure 1 is a schematic diagram of the structure of a client provided in an embodiment of this application;

[0065] Figure 2 is a schematic diagram of the software structure of a client provided in an embodiment of this application;

[0066] Figure 3 is a schematic diagram of an interaction between a client and a server provided in an embodiment of this application;

[0067] Figure 4 is a flowchart illustrating an interface display method provided in an embodiment of this application;

[0068] Figure 5a is a schematic diagram of an application scenario provided by an embodiment of this application;

[0069] Figure 5b is a schematic diagram of another application scenario provided by the embodiments of this application;

[0070] Figure 6 is a schematic diagram of another application scenario provided by the embodiments of this application;

[0071] Figure 7 is a schematic diagram of another application scenario provided by the embodiments of this application;

[0072] Figure 8 is a schematic diagram of another application scenario provided by the embodiments of this application;

[0073] Figure 9 is a flowchart illustrating another interface display method provided in an embodiment of this application;

[0074] Figure 10 is a schematic diagram of the structure of an interface display device provided in an embodiment of this application;

[0075] Figure 11 is a schematic diagram of another interface display device provided in an embodiment of this application. Detailed Implementation

[0076] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0077] In this article, the term "and / or" is merely a description of the relationship between related objects, indicating that there can be three relationships. For example, A and / or B can represent three situations: A exists alone, A and B exist simultaneously, and B exists alone.

[0078] The terms "first" and "second," etc., used in the specification and claims of this application are used to distinguish different objects, not to describe a specific order of objects. For example, "first target object" and "second target object," etc., are used to distinguish different target objects, not to describe a specific order of target objects.

[0079] In the embodiments of this application, the terms "exemplary" or "for example" are used to indicate that something is an example, illustration, or description. Any embodiment or design that is described as "exemplary" or "for example" in the embodiments of this application should not be construed as being more preferred or advantageous than other embodiments or design. Specifically, the use of the terms "exemplary" or "for example" is intended to present the relevant concepts in a specific manner.

[0080] In the description of the embodiments in this application, unless otherwise stated, "multiple" means two or more. For example, multiple processing units means two or more processing units; multiple systems means two or more systems.

[0081] Before describing the technical solutions of the embodiments of this application, a brief introduction to the technical background involved in the embodiments of this application will be given first.

[0082] With the advancement of computer and network communication technologies, information is increasingly being digitized and rapidly disseminated, leading to the growing popularity of digital goods transactions via the internet. Digital goods refer to goods that exist in electronic form and are distributed and consumed through the internet. Digital goods do not require physical carriers and can be verified electronically and delivered instantly.

[0083] Typically, digital goods need to be purchased within a specific application. For example, after a user logs into a specific application, they view and select the digital goods they want to buy. After the user selects the digital goods, the application loads a payment page, and the user completes the payment through the payment page within the application.

[0084] In some scenarios, the technology can recommend digital goods via push notifications. After receiving the notification, a user can request to purchase the digital product. In response to this purchase request, the technology will redirect the user from the notification interface to the application interface that provides the digital product. Furthermore, the user must log in to the application before they can purchase the digital product within that application, thus completing the transaction.

[0085] For example, in a scenario where game items are being promoted, after a user receives a promotional notification or coupon notification from the system, the relevant technology will redirect the user from the system notification interface to the game application and prompt the user to log in to the game application. Only then can the user purchase the game item from the game item interface displayed in the game application.

[0086] When purchasing digital goods offered by an app via system notification, the technology requires switching from the system notification interface to the app itself. Furthermore, the payment interface can only be displayed after logging into the app and the app loading the interface offering the digital goods. This significantly increases the cumbersomeness and time required to respond to purchase requests, resulting in a poor user experience.

[0087] In addition, in other scenarios, application 1 recommends digital goods that application 2 can provide. When a user requests to purchase the digital goods within application 1, the relevant technology will redirect from application 1 to the application interface of application 2 that provides the digital goods, and prompt the user to log in to application 2. Only after application 2 loads and displays the interface of the digital goods can the user purchase the digital goods within application 2, thus realizing the response to the digital goods purchase request. After the digital goods transaction is completed, the relevant technology will also switch back from application 2 to application 1 to display the application interface of application 1, so that the user can continue to use application 1.

[0088] For example, while a user is reading an ebook within a reading app, the app's interface may suggest songs related to the ebook (such as theme songs from movies or TV series adapted from the ebook). When the user interacts with this suggestion within the reading app to purchase or play the song, the technology will redirect the user from the reading app's interface to the music app that provides the song, prompting the user to log in to the music app. The music app can then load and display the song's interface, allowing the user to purchase the song within the music app. After purchasing the song, the technology also needs to switch the foreground application back from the music app to the reading app so that the purchased song can be played within the reading app's interface.

[0089] In scenarios where a single application recommends digital goods offered by other applications, users need to switch between applications that offer those digital goods. This involves switching between different applications, logging into the application offering the digital goods, and loading the application interface for those digital goods. This increases the complexity of the response process for purchasing digital goods and the response time, resulting in a poor user experience.

[0090] In some scenarios, when a user requests to purchase digital goods, if the application providing the digital goods or the application server corresponding to the application is undergoing an update or experiencing a malfunction, it may lead to problems such as unsuccessful application login or the application failing to load the application interface used for trading digital goods. In this case, responding to the user's transaction request for digital goods according to the above process in the relevant technology will result in an excessively long response time for the digital goods transaction request, which may further lead to the failure of the response to the purchase request for digital goods.

[0091] In summary, the process of purchasing digital goods offered by an application in related technologies requires switching from the application or interface recommending the digital goods to the application offering them. Furthermore, after switching to the application offering the digital goods, the user needs to log in to that application before the transaction interface (e.g., payment interface) can be loaded. Switching between different applications or interfaces, as well as logging in and loading the transaction interface, takes considerable time, easily leading to an overly cumbersome and complex transaction request response process, long response times, and a poor user experience. Moreover, if the application or application server offering the digital goods experiences updates or malfunctions, it can easily result in a response failure after a long response time.

[0092] To address the above issues, this application provides a method for displaying an interface, as well as a client and a server, wherein the server interacts with the client to resolve the aforementioned technical problems.

[0093] The client 100 of this application embodiment will now be described with reference to the accompanying drawings. Figure 1 shows a schematic diagram of the structure of the client 100. It should be understood that the client 100 shown in Figure 1 is only an example of a client. Optionally, the client 100 can be a terminal, also known as a terminal device. The terminal can be a smartphone, tablet computer, laptop computer, desktop computer, smart speaker, smartwatch, in-vehicle terminal, smart TV, wearable device, smart car, etc., and this application does not limit it. In addition, the client 100 can also be software on a terminal device, such as a system service on a mobile phone, or a vehicle system in a smart car. It should be further noted that the client 100 may have more or fewer components than shown in the figure, may combine two or more components, or may have different component configurations. The various components shown in Figure 1 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.

[0094] As shown in Figure 1, taking client 100 as an example of a terminal device, client 100 may include: processor 610, external memory interface 620, internal memory 621, universal serial bus (USB) interface 630, charging management module 640, power management module 641, battery 642, antenna 1, antenna 2, mobile communication module 650, wireless communication module 660, audio module 670, speaker 670A, receiver 670B, microphone 670C, headphone jack 670D, sensor module 680, button 690, motor 691, indicator 692, camera 693, display screen 694, and subscriber identification module (SIM) card interface 695, etc. The sensor module 680 may include a pressure sensor 680A, a gyroscope sensor 680B, a barometric pressure sensor 680C, a magnetic sensor 680D, an accelerometer sensor 680E, a distance sensor 680F, a proximity light sensor 680G, a fingerprint sensor 680H, a temperature sensor 680J, a touch sensor 680K, an ambient light sensor 680L, a bone conduction sensor 680M, etc.

[0095] Processor 610 may include one or more processing units, such as: application processor (AP), modem processor, graphics processing unit (GPU), image signal processor (ISP), controller, memory, video codec, digital signal processor (DSP), baseband processor, and / or neural network processing unit (NPU), etc. The different processing units may be independent devices or integrated into one or more processors.

[0096] The controller can serve as the central nervous system and command center of the client 100. The controller can generate operation control signals based on the instruction opcode and timing signals to control the fetching and execution of instructions.

[0097] The processor 610 may also include a memory for storing instructions and data. In some embodiments, the memory in the processor 610 is a cache memory. This memory can store instructions or data that the processor 610 has just used or that are used repeatedly. If the processor 610 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 610, and thus improves the efficiency of the system.

[0098] In some embodiments, the processor 610 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.

[0099] The USB port 630 is a USB standard compliant interface, which can be a Mini USB port, Micro USB port, USB Type-C port, etc. The USB port 630 can be used to connect a charger to charge client 100, and can also be used for data transfer between client 100 and peripheral devices. It can also be used to connect headphones for audio playback. This interface can also be used to connect other clients, such as AR devices.

[0100] 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 client 100. In other embodiments of this application, the client 100 may also adopt different interface connection methods or a combination of multiple interface connection methods as described in the above embodiments.

[0101] The charging management module 640 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 640 receives charging input from the wired charger via a USB interface 630. In some wireless charging embodiments, the charging management module 640 receives wireless charging input via the wireless charging coil of the client 100. While charging the battery 642, the charging management module 640 can also supply power to the client via the power management module 641.

[0102] The power management module 641 connects the battery 642, the charging management module 640, and the processor 610. The power management module 641 receives input from the battery 642 and / or the charging management module 640, providing power to the processor 610, internal memory 621, external memory, display screen 694, camera 693, and wireless communication module 660. The power management module 641 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 641 may also be located within the processor 610. In other embodiments, the power management module 641 and the charging management module 640 may be located in the same device.

[0103] The wireless communication function of client 100 can be implemented through antenna 1, antenna 2, mobile communication module 650, wireless communication module 660, modem processor and baseband processor.

[0104] Antennas 1 and 2 are used to transmit and receive electromagnetic wave signals. Each antenna in client 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 a tuning switch.

[0105] The mobile communication module 650 can provide solutions for wireless communication applications including 2G / 3G / 4G / 5G on the client 100. The mobile communication module 650 may include at least one filter, switch, power amplifier, low noise amplifier (LNA), etc. The mobile communication module 650 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 650 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 650 may be housed in the processor 610. In some embodiments, at least some functional modules of the mobile communication module 650 and at least some modules of the processor 610 may be housed in the same device.

[0106] 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 670A, receiver 670B, etc.) or displays images or videos through a display screen 694. In some embodiments, the modem processor may be a separate device. In other embodiments, the modem processor may be independent of the processor 610 and may be housed in the same device as the mobile communication module 650 or other functional modules.

[0107] The wireless communication module 660 can provide solutions for wireless communication applications on the client 100, including wireless local area networks (WLAN) (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 660 can be one or more devices integrating at least one communication processing module. The wireless communication module 660 receives electromagnetic waves via antenna 2, performs frequency modulation and filtering of the electromagnetic wave signals, and sends the processed signal to processor 610. The wireless communication module 660 can also receive signals to be transmitted from processor 610, perform frequency modulation and amplification, and convert them into electromagnetic waves for radiation via antenna 2.

[0108] In some embodiments, antenna 1 of client 100 is coupled to mobile communication module 650, and antenna 2 is coupled to wireless communication module 660, enabling client 100 to communicate with networks and other devices via wireless communication technology.

[0109] Client 100 implements display functions through a GPU, display screen 694, and application processor. The GPU is a microprocessor for image processing, connecting the display screen 694 and the application processor. The GPU is used to perform mathematical and geometric calculations for graphics rendering. Processor 610 may include one or more GPUs, which execute program instructions to generate or modify display information.

[0110] Display screen 694 is used to display images, videos, etc. Display screen 694 includes a display panel. The display panel can 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 Mini LED, a MicroLED, a Micro-OLED, a quantum dot light-emitting diode (QLED), etc. In some embodiments, client 100 may include one or N displays 694, where N is a positive integer greater than 1.

[0111] Client 100 can perform shooting functions through ISP, camera 693, video codec, GPU, display 694 and application processor.

[0112] Camera 693 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.

[0113] The external storage interface 620 can be used to connect an external storage card, such as a Micro SD card, to expand the storage capacity of the client 100. The external storage card communicates with the processor 610 through the external storage interface 620 to perform data storage functions. For example, music, video, and other files can be saved on the external storage card.

[0114] Internal memory 621 can be used to store computer executable program code, which includes instructions. Processor 610 causes client 100 to execute the methods described in this embodiment by running the instructions stored in internal memory 621. Internal memory 621 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 by client 100 during use (such as audio data, phonebook, etc.). Furthermore, internal memory 621 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.

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

[0116] The audio module 670 is used to convert digital audio information into analog audio signals for output, and also to convert analog audio input into digital audio signals. The audio module 670 can also be used for encoding and decoding audio signals. In some embodiments, the audio module 670 may be located in the processor 610, or some functional modules of the audio module 670 may be located in the processor 610.

[0117] Buttons 690 include a power button, volume buttons, etc. Buttons 690 can be mechanical buttons or touch-sensitive buttons. Client 100 can receive button input and generate key signal inputs related to user settings and function control of client 100.

[0118] Motor 691 can generate vibration alerts. Motor 691 can be used for incoming call vibration alerts or for touch vibration feedback. For example, different vibration feedback effects can be corresponding to touch operations applied to different applications (such as taking photos, playing audio, etc.). Motor 691 can also correspond to different vibration feedback effects for touch operations applied to different areas of the display screen 694. Different application scenarios (such as time reminders, receiving messages, alarm clocks, games, etc.) can also correspond to different vibration feedback effects. The touch vibration feedback effect can also be customized.

[0119] Indicator 692 can be an indicator light, used to indicate charging status, power changes, or messages, missed calls, notifications, etc.

[0120] The SIM card interface 695 is used to connect a SIM card. The SIM card can be inserted into or removed from the SIM card interface 695 to establish contact with and disconnect from the client 100. The client 100 can support one or N SIM card interfaces, where N is a positive integer greater than 1. The SIM card interface 695 can support Nano SIM cards, Micro SIM cards, SIM cards, etc. Multiple cards can be inserted into the same SIM card interface 695 simultaneously. The multiple cards can be of the same or different types. The SIM card interface 695 is also compatible with different types of SIM cards. The SIM card interface 695 is also compatible with external storage cards. The client 100 interacts with the network through the SIM card to achieve functions such as calls and data communication. In some embodiments, the client 100 uses an eSIM, i.e., an embedded SIM card. The eSIM card can be embedded in the client 100 and cannot be separated from the client 100.

[0121] The software system of client 100 can adopt a layered architecture, event-driven architecture, microkernel architecture, microservice architecture, or cloud architecture. This application embodiment uses a layered Android system as an example to illustrate the software structure of client 100.

[0122] Figure 2 is a software structure block diagram of the client 100 according to an embodiment of this application.

[0123] The layered architecture of client 100 divides the software into several layers, each with a clear role and function. Layers communicate with each other through software interfaces. In some embodiments, the Android system is divided into four layers, from top to bottom: the application layer, the application framework layer, the Android runtime and system libraries, and the kernel layer.

[0124] The application layer can include a series of application packages.

[0125] As shown in Figure 2, the application package may include applications such as gallery, SMS, navigation, music, video, reading, and ticketing.

[0126] The application framework layer provides application programming interfaces (APIs) and a programming framework for applications in the application layer. The application framework layer includes some predefined functions.

[0127] As shown in Figure 2, the application framework layer may include a window manager, content provider, view system, phone manager, resource manager, notification manager, out-of-application payment service, push service, etc.

[0128] The window manager is used to manage windowed applications. It can retrieve screen size, determine the presence of a status bar, lock the screen, and capture screenshots, among other things.

[0129] Content providers store and retrieve data, making that data accessible to applications. This data may include videos, images, audio, made and received phone calls, browsing history and bookmarks, phone books, etc.

[0130] A view system includes visual controls, such as controls for displaying text and controls for displaying images. View systems can be used to build applications. A display interface can consist of one or more views. For example, a display interface including a text notification icon could include views for displaying text and views for displaying images.

[0131] The phone manager is used to provide communication functions for client 100. For example, it manages call status (including connection, hang-up, etc.).

[0132] The file explorer provides applications with various resources, such as localized strings, icons, images, layout files, video files, and more.

[0133] The notification manager allows applications to display notifications in the status bar. These can be used to convey informational messages and can disappear automatically after a short pause, requiring no user interaction. For example, the notification manager can be used to notify of download completion or message alerts. The notification manager can also display notifications as icons or scrolling text in the top status bar, such as notifications from background applications, or as dialog boxes on the screen. Examples include displaying text messages in the status bar, emitting sound alerts, vibrating the client, or flashing indicator lights.

[0134] Out-of-application payment services can be used to display payment description information for digital goods and to realize the transaction of digital goods outside of the application. The specific implementation process of out-of-application payment services will be described in detail in the following method embodiments.

[0135] Push services can be used to push various notifications (such as SMS messages, system messages, etc.), and the specific push process will be described in detail in the following examples.

[0136] The system library and runtime layer include the system libraries and the Android Runtime. The system libraries can include multiple functional modules, such as the surface manager, media libraries, 3D graphics processing libraries (e.g., OpenGL ES), and 2D graphics engines (e.g., SGL). The 3D graphics library is used to implement 3D graphics drawing, image rendering, compositing, and layer processing. The Android Runtime includes the core libraries and the virtual machine. The Android Runtime is responsible for the scheduling and management of the Android system. The core libraries consist of two parts: one part contains the functionalities that the Java language needs to call, and the other part contains the core Android libraries. The application layer and application framework layer run in the virtual machine. The virtual machine executes the Java files of the application layer and application framework layer as binary files. The virtual machine is used to perform functions such as object lifecycle management, stack management, thread management, security and exception management, and garbage collection.

[0137] The Surface Manager is used to manage the display subsystem and provides the blending of 2D and 3D layers for multiple applications.

[0138] The media library supports playback and recording of various common audio and video formats, as well as still image files. It supports multiple audio and video encoding formats, such as MPEG4, H.264, MP3, AAC, AMR, JPG, and PNG.

[0139] The 3D graphics processing library is used to implement 3D graphics drawing, image rendering, compositing, and layer processing.

[0140] A 2D graphics engine is a graphics engine for 2D drawing.

[0141] The kernel layer is the layer between hardware and software. The kernel layer contains at least the display driver, camera driver, audio driver, and sensor driver.

[0142] It is understood that the components included in the system framework layer, system library, and runtime layer shown in Figure 2 do not constitute a specific limitation on the client 100. In other embodiments of this application, the client 100 may include more or fewer components than shown in the figure, or combine some components, or split some components, or have different component arrangements.

[0143] Please refer to Figure 3, which exemplarily illustrates a schematic diagram of a digital goods transaction between a server and a client.

[0144] As shown in Figure 3, client 100 may include, but is not limited to, a push service, a first application, and a system service (also referred to as an out-of-application payment service). The first application is an application that provides digital goods. Server 11 is the service side of the first application (e.g., a server). Server 11 can provide resource information for digital goods (e.g., if the digital goods are music, then the resource information is specific audio resources). The system service shown in Figure 3 can also be referred to as the client of the out-of-application payment service. Server 10 may deploy the server of this out-of-application payment service. The server of this out-of-application payment service can interact with the client of the out-of-application payment service, enabling client 100 to transact the digital goods provided by the first application outside the application interface of the first application, without needing to transact the digital goods within the first application.

[0145] Server 10 can provide cloud services (such as services that provide out-of-application payment functionality). By purchasing this cloud service, the supplier of the first application can enable its server 11 to list the digital goods it provides to server 10, so that server 10 can provide out-of-application payment services for the digital goods.

[0146] After a digital product is listed on server 10, server 11 can also push the digital product to client 100, allowing client 100 to receive the product via system notification messages, SMS messages, or application notification messages from the first application. For example, server 11 can push a purchase notification message for the digital product to the client's push service.

[0147] The purchase notification message or the first interface where the purchase notification message is located not only includes descriptive information about the digital product, but also associates the product identifier of the digital product and indicates the first interface for calling the system service shown in Figure 3. Therefore, when the user requests to purchase the digital product by operating the purchase notification message or the first interface, the client 100 can call the first interface associated with the first interface without switching to the first application, and pass the product identifier to the first interface to call the system service.

[0148] Subsequently, as shown in Figure 3, client 100 can purchase the digital product from server 10 by calling the system service outside the first application, thus displaying a second interface (e.g., a cashier interface) outside the first application. After payment for the digital product is made through the cashier interface, server 10 can notify server 11 to ship the digital product, so that server 11 sends the resource information of the digital product to the first application. In this way, the transaction of digital products outside the first application that provides the digital product can be realized through client 100, server 10, and server 11.

[0149] The server-side, also known as the cloud side, can implement its functions through software or hardware.

[0150] In the first example, when the functionality of the server is implemented through software, the server can be, for example, an application running on a computing instance, such as a virtual machine, container, or host.

[0151] In the second example, when the functionality of the server is implemented through hardware, the server can be implemented through at least one physical device including a processor, such as a server.

[0152] The processor can be a central processing unit (CPU) or a graphics processing unit (GPU), or it can be any type of processor or any combination thereof, such as an application-specific integrated circuit (ASIC), a programmable logic device (PLD), a complex programmable logical device (CPLD), a field-programmable gate array (FPGA), a generic array logic (GAL), a system-on-chip (SoC), a software-defined infrastructure (SDI) chip, an AI chip, or a data processing unit (DPU).

[0153] Furthermore, the number of processors included in the server can be arbitrary, and the types of processors included can be one or more. The specific number and types of processors can be set according to the actual business needs of the application, and this application does not limit this.

[0154] The physical device can be a server (such as a central server or an edge server), a base station, a relay device, a satellite device, etc., and there are no restrictions here.

[0155] In the third example, when the server-side functionality is implemented through hardware, the server can also be a computing cluster comprising multiple computing nodes. Furthermore, these multiple computing nodes can communicate through the at least one switching node. Exemplarily, a computing node can be a computing server including an accelerator card. This accelerator card can be, for example, a deep-learning processing unit (DPU), a GPU, a neural-network processing unit (NPU), or a tensor processing unit (TPU), or other types of accelerator cards. Alternatively, a computing node can be a computing server including a general-purpose processor (such as a CPU).

[0156] Figure 4 illustrates a flowchart of an interface display method according to an embodiment of this application. This method flowchart can be combined with, but is not limited to, the embodiments shown in Figures 1, 2, and 3.

[0157] As shown in Figure 4, the method flow may include, but is not limited to, the following steps:

[0158] Optionally, S101. Server 11 sends the attribute information of the digital goods to Server 10.

[0159] In some embodiments, digital goods refer to goods that exist in electronic form, are distributed and consumed via the Internet, and do not require a physical carrier, allowing for electronic verification and immediate delivery. This application does not limit the specific form of digital goods.

[0160] As an example, digital goods can be electronically verifiable ticket-type goods such as concert tickets and train tickets, and the application to which such digital goods belong can be described as a ticketing application as shown in Figure 9 below; as another example, digital goods can be electronically verifiable virtual goods such as game items (e.g., game skins and game equipment), and the application to which such digital goods belong can be described as a game application as shown in Figure 9 below; as yet another example, digital goods can be electronically verifiable audio-visual goods such as music and videos, and the application to which such digital goods belong can be described as a content application as shown in Figure 9 below.

[0161] Thus, the first application providing this digital product can be a ticketing application, a game application, or a content application, etc., without any restrictions.

[0162] In optional embodiments, the attribute information of digital goods may include, but is not limited to, product identification and product description information.

[0163] A product identifier can serve as a unique identifier for digital goods, distinguishing them from different digital products. As an example, a product identifier for a digital product can consist of a combination of numbers and / or letters; there are no restrictions on the specific implementation of this product identifier.

[0164] For example, the product identifier 1 of digital product 1 can be "0001", the product identifier 2 of digital product 2 can be "name-sp2", and the product identifier 3 of digital product 3 can be "sp0003".

[0165] Product description information can be information that describes some attributes of digital products. For example, product description information may include, but is not limited to: product name, application, pricing, currency, discounted price (e.g., the price after discount), discount information (e.g., discount rate or coupon information).

[0166] In an optional embodiment, pricing is used to indicate the selling price of the digital goods. For example, the selling price can be the price of the digital goods before various discounts are applied.

[0167] In an optional embodiment, the currency is used to indicate the type of currency used to pay for digital goods. For example, the currency can be RMB, USD, EUR, etc. Alternatively, the currency can be a virtual currency adapted to the first application and usable for payment within the first application. The virtual currency can be purchased using RMB, thereby purchasing digital goods.

[0168] As an example, product descriptions may also include detailed information about product features, functions, and usage methods, designed to help users understand digital products. For instance, if the digital product is a concert ticket, the product description might include the concert location, time, and performers.

[0169] Optionally, S102. Server 11 pushes digital goods to client 100.

[0170] In some embodiments, server 11 may send attribute information of digital goods to client 100. For example, server 11 may send the product name, product identifier, application to which it belongs, pricing, currency, etc. of digital goods to client 100.

[0171] In an optional embodiment, as shown in Figures 2 and 9, the client 100 may include a push service, which may receive attribute information of the digital product sent by the server 11 (e.g., a server providing a first application for digital products) to push a notification message. In this way, the client 100 can display a first interface based on the push notification message.

[0172] This application does not impose any restrictions on the execution order of S101 and S102.

[0173] S201. Client 100 displays the first interface.

[0174] In an optional embodiment, after receiving the digital goods pushed to the client 100 by the server 11, the client 100 can display the first interface through the push service. For example, the first interface can be a notification message interface, such as a pop-up message (i.e., a notification message displayed on the lock screen interface), then the first interface can be the lock screen interface; or, the notification message can be a notification message in the pull-down notification bar (such as notification controls 421 and 422 shown in Figure 5a(2), then the first interface can be a pull-down notification bar interface (such as notification bar interface 420 shown in Figure 5a(2); or, the notification message can be an SMS message (such as SMS control 6481 shown in Figure 6), then the first interface can be the display interface of the SMS application (such as SMS interface 480 shown in Figure 6).

[0175] For example, the first interface could be the window containing the marketing notification controls (such as the notification message), or the notification interface containing the marketing notification controls. Alternatively, the first interface could be the SMS interface, or the session interface of a single SMS message; there are no restrictions here.

[0176] In some embodiments, the first interface is different from the application interface of the first application that provides digital goods.

[0177] In some embodiments, the first interface is the application interface of the second application, and the first application is different from the second application.

[0178] In some embodiments, the first interface indicates the recommendation of the digital product corresponding to its associated product identifier. The products recommended by the second application may include the aforementioned digital product, and the supplier of the digital product is the first application. This allows the recommendation and transaction of the digital product to be implemented within the application interface of an application other than the one providing the digital product, enabling transactions of digital products provided by the first application to be conducted outside of the first application, thus avoiding switching between applications. Furthermore, it avoids the issues of logging into the first application and loading the application interface of the digital product within the first application, reducing the complexity of the response process for purchasing digital products and shortening the response time, resulting in a better user experience.

[0179] The aforementioned first interface may include product description information of digital goods. The first interface may be associated with product identifiers of digital goods and a first interface for invoking system services (such as the out-of-application payment service shown in Figures 2 and 9, hereinafter referred to as out-of-application payment service).

[0180] In an optional embodiment, the first interface is the interface of the second application, which is different from the first application.

[0181] The second application can recommend multiple digital products, including the digital products mentioned in S101 and S102 above, and the provider of these digital products is the first application. That is, the client 100 can display the first interface of the second application to recommend digital products provided by the first application.

[0182] In some embodiments, the first interface may carry the product identifier of the digital goods provided by the first application and carry the first interface.

[0183] The digital product is one that can be paid for on the first interface without being redirected to the first application that provides the digital product.

[0184] In some embodiments, the first interface may be bound to the product identifier of the digital product and the first interface, so that the first interface is associated with the product identifier and the first interface.

[0185] This application embodiment does not limit the association form between the first interface and the product identifier of the digital product and the first interface.

[0186] In some embodiments, the number of product identifiers for digital goods carried on a first interface can be one or more. That is, the client of this application can provide payment functionality for one or more digital goods outside the first application based on user operations on the first interface (e.g., the first user input described below). This application does not limit this. The following embodiments use one product identifier for digital goods carried on a first interface as an example, but are not intended to limit this application.

[0187] Optionally, S202. Client 100 receives the first user input.

[0188] The first user inputs an instruction requesting to purchase the digital product associated with the first interface.

[0189] In an optional embodiment, the first interface of the client 100 may display product description information of the digital goods. In some embodiments, the product identifier is not used to display on the first interface.

[0190] In an optional embodiment, the user performs an operation on the first interface, and the client 100 receives the first user input performed by the user on the first interface.

[0191] For example, the first user input could be for purchasing concert tickets. Or, the first user input could be for purchasing game skins. Or, the first user input could be for purchasing a theme song.

[0192] S204. Client 100 responds to the first user input above and displays the second interface.

[0193] In some embodiments, in response to a received first user input to a first interface, client 100 displays a second interface based on the product identifier associated with the first interface and a first interface. The first user input indicates a request to purchase digital goods, and the first interface is associated with a first interface that indicates an invocation of a system service (specifically, an out-of-application payment service). This system service may instruct the user to obtain payment description information for the digital goods based on the product identifier, and the second interface includes the payment description information.

[0194] The first interface can be, for example, a deep link, or other interfaces; there are no restrictions here.

[0195] In an optional embodiment, the payment description information can provide details about the transaction information of the digital goods. For example, the payment description information may include, but is not limited to, information about the digital goods to be paid, such as the amount to be paid, the payment method (e.g., a third party or bank card), the name of the goods, and the quantity of the goods.

[0196] In some embodiments, the client 100 may use the product identifier to invoke the first interface, thereby displaying the second interface.

[0197] In some embodiments, the client 100 may pass the product identifier to the first interface and call the off-application payment service through the first interface to display the second interface.

[0198] In an optional embodiment, the client 100 may display a second interface within the application interface of a second application that recommends the digital product, based on the product identifier and the first interface.

[0199] This second interface, also known as the checkout interface, provides payment functionality for digital goods. This second interface can be the application interface of the second application, or a sub-interface such as a window within the application interface of the second application; there are no restrictions.

[0200] This approach avoids switching from the second application to the first, as well as the need to log in to the first application and load the second interface within it, when recommending digital goods provided by the first application within the second application. This not only enables payment and transaction of digital goods outside of their original application but also simplifies the response process to purchase requests and reduces the complexity of the purchase process, resulting in a better user experience.

[0201] In some embodiments, after a user triggers an action to purchase digital goods (an example of first user input), the client 100 may respond to the user action by invoking the aforementioned out-of-application payment service through a first interface. Furthermore, the client 100 may send the product identifier of the digital goods associated with the first interface to the out-of-application payment service to conduct the transaction of the digital goods provided by the first application through the out-of-application payment service, without needing to jump from the first interface to the application interface of the first application to conduct the transaction. This reduces the complexity of the response process for purchasing digital goods and shortens the response time, resulting in a better user experience.

[0202] In related technologies, when the first interface recommending a digital product is not the application interface of the app that provides the digital product (i.e., when the digital product is recommended from outside the app), and the transaction or payment for the digital product is to be made, the display interface needs to be switched from the first interface to the application interface of the app that provides the digital product (also known as the app that provides the digital product) to enable payment and transaction within the app. This requires the user to log in to the first app when switching apps, and the client needs to wait for the first app to load the application interface providing the digital product before the transaction can proceed, making the process cumbersome. When purchasing digital products provided by an app through a system notification, the technology requires switching from the system notification interface to that app, logging into the app, and waiting for the app to load the application interface providing the digital product before the payment interface can be displayed. When recommending digital products that app 2 can provide within app 1, the technology requires redirecting from app 1 to the application interface of app 2 providing the digital product, prompting the user to log in to app 2, and then app 2 loading and displaying the interface for the digital product before the user can purchase the digital product within app 2, thus fulfilling the digital product purchase request. This will significantly increase the complexity of the response process for purchasing digital goods and the response time, resulting in a poor user experience.

[0203] However, in this embodiment, although the first interface recommending the digital product is not the application interface of the application to which the digital product belongs (the first application), the first interface may be associated with the product identifier of the digital product and a first interface indicating the invocation of an external payment service (a system service). Therefore, when a user requests to purchase the digital product on the first interface, the method of this embodiment can display a second interface containing payment description information of the digital product based on the product identifier associated with the first interface and the aforementioned first interface. This second interface could be, for example, the cashier interface of the digital product. Thus, when a user purchases the digital product, the method of this embodiment does not require prompting the user to log in to the first application and switch the application interface to the first application's application interface for the transaction and payment of the digital product. For example, it does not require displaying the second interface within the first application and avoids the loading process of the second interface within the first application. This not only realizes the payment and transaction of the digital product outside of its owning application but also simplifies the response process to purchase requests for digital products and reduces the cumbersomeness of the purchase process, resulting in a better user experience. Furthermore, when a user requests to purchase a product outside the first application, this invention does not redirect the user to the first application. Instead, it allows the user to directly access the system service outside the application by utilizing the product ID and interface associated with the first interface. This system service then launches the payment interface for the product (example of the second interface). This enables product transactions to be completed outside the application, eliminating the need to switch the foreground application to the first application. It avoids processes such as application login and loading the digital product interface, simplifying the process and shortening the transaction time for digital products.

[0204] In some embodiments, as shown in FIG4, after S202 and before S204, there may be S203, S301, and S302, among others.

[0205] Optionally, S203. Client 100 sends an order request to server 10.

[0206] In an optional embodiment, client 100 may send an order request for the digital product to server 10 in response to a first user input.

[0207] In a specific embodiment, the first interface may be associated with a product identifier for a digital product, and the order request may include the product identifier of the digital product. The client 100 may, in response to a user's first input on the first interface, send the order request to the server 10 to place an order for the digital product outside the first application.

[0208] In an optional embodiment, the order request may also include user information. For example, the user information may be the user's login account.

[0209] Optionally, in S301, server 10 obtains the payment description information of the digital product requested for this order based on the order request and the attribute information of the digital product received from the digital product server (e.g., server 11) through the above S101.

[0210] Optionally, S302. Server 10 sends payment description information of digital goods to client 100.

[0211] In a specific embodiment, as shown in Figure 9, during the process of the client 100 calling the out-of-application payment service through the first interface, the out-of-application payment service can send the product identifier of the aforementioned digital product to the server 10, so that the server 10 can determine the payment description information of the digital product based on the product identifier. In response to the order request, the server 10 can send the payment description information of the digital product to the out-of-application payment service, which can then obtain the payment description information sent by the server 10 to display a second interface (e.g., a cashier interface).

[0212] In an optional embodiment, the payment description information sent by the server 10 to the client 100 may include, but is not limited to, the amount to be paid for the digital goods, the name of the goods, and the quantity of the goods.

[0213] In an optional embodiment, the second interface differs from the application interface of the first application that provides digital goods.

[0214] In an optional embodiment, the second interface is a payment description information interface. Responding to the user's first input on the first interface, the client 100 invokes an external payment service based on the first interface associated with it. The external payment service obtains payment description information for the digital goods based on the product identifier transmitted within the first interface. Subsequently, the client 100 can display the second interface including the payment description information via the above-described S204 as shown in FIG4.

[0215] In an optional embodiment, the order request includes the product identifier of the digital product associated with the first interface. The attribute information of the digital product includes, but is not limited to, the product identifier and product description information (e.g., application, pricing, currency). The server 10 can determine the attribute information of the digital product to be ordered based on the product identifier of the digital product in this order. Then, the server 10 can determine the payment description information of the digital product based on its attribute information. For example, the server 10 can determine the name, application, pricing, currency, and product description information of the digital product based on its product identifier.

[0216] In a specific embodiment, server 10 stores attribute information for multiple digital products, and server 10 retrieves the attribute information for these multiple digital products. Based on the product identifier of the digital product, server 10 determines the attribute information of the digital product corresponding to that product identifier from the multiple attribute information.

[0217] For example, server 10 can store attribute information of various digital goods. These various digital goods are not limited to those provided by server 11 of the first application, but may also include digital goods provided by servers of other applications. Server 10 may, optionally, look up the attribute information of the digital goods corresponding to the product identifier in the attribute information table based on the product identifier of the digital goods ordered this time, in conjunction with the application to which it belongs (e.g., the first application).

[0218] In a specific embodiment, the server 10 searches the attribute information table for the name, application, and pricing corresponding to the digital product identifier.

[0219] In some embodiments, server 10 may determine the outstanding payment amount of digital goods based on the pricing of the digital goods. For example, server 10 determines the pricing of the digital goods as the outstanding payment amount of the digital goods.

[0220] In other embodiments, server 10 may determine the outstanding payment amount of the digital goods based on the pricing of the digital goods and the application to which the digital goods belong. For example, if the application to which the digital goods belong offers a promotion of 50 off for purchases over 300, and the pricing of the digital goods is greater than or equal to 300, server 10 determines the outstanding payment amount of the digital goods as the pricing amount minus 50; if the pricing of the digital goods is less than 50, server 10 determines the pricing amount of the digital goods as the outstanding payment amount.

[0221] In some other embodiments, server 10 may determine the outstanding payment amount for digital goods based on the pricing and order information of the digital goods. For example, server 10 obtains the order creation time through order information, and determines the outstanding payment amount for digital goods based on the order creation time and the pricing of the digital goods.

[0222] As an example, orders created before time A are eligible for a 10% discount. Server 10 determines the outstanding amount of digital goods as the price multiplied by 0.9.

[0223] As another example, orders created between time A and time B are eligible for a 5 yuan discount. Server 10 determines the outstanding payment amount for digital goods as the price minus 5 yuan.

[0224] In some other embodiments, server 10 may determine the outstanding payment amount for digital goods based on the pricing of the digital goods and user information. For example, server 10 obtains user coupon information through user information, and server 10 determines the outstanding payment amount for digital goods based on the user coupon information and the pricing of the digital goods.

[0225] As an example, a user has a coupon for 1 yuan, and the server determines that the amount to be paid for the digital product is equal to the price minus 1.

[0226] As another example, if a user has a 9.5% discount, the server determines that the amount due for the digital goods is equal to the price multiplied by 0.95.

[0227] In one example, the attribute information table is shown in Table 1 below.

[0228] Table 1

[0229] As an example, the product identifier for a concert ticket is "ych-1128". Server 10 uses the product identifier "ych-1128" to look up the attribute information table shown in Table 1, and determines that the name of the digital product is "concert ticket", the application it belongs to is "ticketing application", the price is "price 1", the currency is "RMB", and the product description information is "product description information 1".

[0230] As another example, the product identifier for the game skin is "pf-0020". Server 10 uses the product identifier "pf-0020" to look up the attribute information table shown in Table 1 to determine that the name of the digital product is "game skin", the application it belongs to is "game application", the price is "price 2", the currency is "RMB", and the product description information is "product description information 2".

[0231] As another example, the product identifier for the theme song is "yy-0320". The server 10 uses the product identifier "yy-0320" to look up the attribute information table shown in Table 1 to determine that the name of the digital product is "theme song", the application it belongs to is "music application", the price is "price 3", the currency is "RMB", and the product description information is "product description information 3".

[0232] The implementation process of S204 and the steps preceding it shown in Figure 4 will be described below in conjunction with a specific application scenario.

[0233] In an optional embodiment, the first interface is a notification message interface.

[0234] In specific embodiments, the notification message can be a pop-up message, a notification bar message, an SMS message, etc., and correspondingly, the first interface can be a pop-up interface, a notification bar interface, an SMS interface, etc.

[0235] To illustrate with a specific example 1, Figure 5a is a schematic diagram of an application scenario provided by an embodiment of this application.

[0236] As shown in Figure 5a(1), taking the client 100 as a mobile phone as an example, the mobile phone's display interface 410 is the main interface. The main interface may include one or more application icons, including but not limited to: game application 411, ticketing application 412, reading application 413, music application 414, and information application 415. Optionally, the main interface may also include clock application, calendar application, gallery application, memo application, file management application, video application, settings, weather application, camera application, and phone application, etc.

[0237] As an example, a user can pull down from the top of the display interface 410 in the direction of the arrow. The phone can respond to the pull-down operation and switch the phone's display interface from the display interface 410 shown in Figure 5a(1) to the notification bar interface 420 shown in Figure 5a(2).

[0238] As another example, a user can pull down from the top of the phone's lock screen, and the phone can respond to the pull-down operation by switching the phone's display interface from the lock screen to the notification bar interface 420 shown in Figure 5a(2). This application does not limit the user operation method for displaying the notification bar interface 420.

[0239] In this example, the first interface mentioned above can be the notification bar interface 420, which can display notification messages pushed by the push service (such as notification controls 421 and 422). This first interface is the interface displayed based on the push service, rather than the interface of a specific application.

[0240] As shown in Figure 5a(2), the notification bar interface 420 may include one or more controls, including but not limited to notification control 421 and notification control 422. Notification control 421 may display a ticket-grabbing message for concert tickets provided by ticketing application 412, and notification control 422 may display a purchase notification message for game skins provided by game application 411. Notification control 421 includes a "grab ticket" button, which users can click to purchase concert tickets pushed by notification control 421. For example, after a user clicks the "grab ticket" button, the mobile phone may respond to the user's operation by switching the mobile phone's display interface from Figure 5a(2) to the payment interface 430 shown in Figure 5a(3) to purchase concert tickets. Among them, ticketing application 412 is an example of a first application that provides the concert tickets (an example of a digital product), and game application 411 is an example of a first application that provides game skins (a type of digital product).

[0241] In this example, the second interface can be the payment interface 430, and the first interface can be the interface corresponding to the "ticket grabbing" button included in the notification control 421.

[0242] Optionally, the controls displayed on the payment interface 430 shown in FIG5a(3) are not limited to the controls shown in FIG5a(3). The payment interface 430 may also include various payment-related controls in the payment interface 520 shown in FIG7(2) for payment of digital goods outside the first application.

[0243] In this embodiment, the first interface recommends the digital product corresponding to its associated product identifier. When purchasing a digital product offered by an application via a notification message, switching from the notification message interface to the first application offering the digital product is avoided. Furthermore, the payment interface is not displayed until after logging into the first application and the application loading the interface offering the digital product. This reduces the complexity of the response process for digital product purchase requests and the response time, resulting in a better user experience.

[0244] Optionally, after S204, in S207, the client 100 displays a third interface based on the payment description information included in the second interface.

[0245] In an optional embodiment, the client 100 displays a third interface based on payment description information. The third interface may include information indicating that the digital goods transaction provided by the first application has been completed. The third interface is different from the application interface of the first application.

[0246] Optionally, as shown in Figure 4, after S204 and before S207, the method may further include S205, S206, and S303. Optionally, after S303, S304 and S103 may also be included. This application does not restrict the execution order of S304, S103, and S207.

[0247] Optionally, in S205, client 100 receives third user input to the second interface in S204.

[0248] In an optional embodiment, the user performs an operation on the second interface (an example of third user input), and the client 100 receives the third user input performed by the user on the second interface.

[0249] The third user input indicates the submission of payment information for the digital goods. For example, the third user input could be clicking the payment button.

[0250] Optionally, in response to the third user input, client 100 sends the user's payment account information to server 10.

[0251] In an optional embodiment, after receiving the user's third user operation on the second interface, the client 100 sends the user's payment account information to the server 10.

[0252] In a specific embodiment, the third interface (e.g., the payment interface 520 shown in Figure 7(2)) may include the user's payment account. The payment account information may include the user's payment account and the payment tool bound to the user's payment account. The client 100 determines the payment tool bound to the payment account based on the payment account, and the client 100 sends the user's payment account, the payment tool bound to the user's payment account, etc., to the server 10.

[0253] Optionally, S303. The server 10 determines, based on the payment account information, a notification message indicating that the digital goods transaction provided by the first application has been completed and sends the notification message to the client 100.

[0254] In an optional embodiment, the notification information may include the product identifier of the digital product, the order number of the digital product order, the user identifier, etc.

[0255] In a specific embodiment, the payment account information includes the user's payment account, and the server 10 can identify the user's payment account as the user identifier.

[0256] In a specific embodiment, the server 10 generates an order for the digital product and obtains the order number of the order.

[0257] Thus, as shown in S207 of Figure 4, the client 100 can display a third interface based on the notification information.

[0258] Based on the specific example 1 above, the implementation process of S207 and the steps preceding it shown in Figure 4 will be described further.

[0259] As shown in Figure 5a(3), the payment interface 430 (an example of the second interface mentioned above) may include one or more controls, including but not limited to a quantity control 431 and a payment control 432. The quantity control 431 can display the number of concert tickets purchased, and the quantity control 431 includes a "-" button and a "+" button.

[0260] Users can click the "-" button to decrease the number of concert tickets purchased, and click the "+" button to increase the number of concert tickets purchased. For example, after a user clicks the "-" button, the phone can respond by decreasing the number of concert tickets purchased displayed in the quantity control 431 by one. Similarly, after a user clicks the "+" button, the phone can respond by increasing the number of concert tickets purchased displayed in the quantity control 431 by one.

[0261] In an optional embodiment, the quantity control 431 displays the number of concert tickets purchased as 1 by default, and the quantity control 431 can also display the number of concert tickets purchased as a positive integer greater than 0.

[0262] Users can click on payment control 432 to pay for concert tickets. For example, after a user clicks the "Pay" button, the mobile phone can respond to the user's click on payment control 432 and switch the mobile phone's display interface from the payment interface 430 shown in Figure 5a(3) to the cashier interface (for example, the payment interface 520 shown in Figure 7(2)) to pay for the concert tickets.

[0263] In an optional embodiment, the checkout interface may include payment description information for digital goods. For example, the payment description information may include the amount due, the user's payment account, and the payment method. The user's payment account may be their mobile phone number. Payment methods may include, but are not limited to, bank cards, friend-paid payments, and account balances.

[0264] In an optional embodiment, the cashier interface may also include a "Confirm" button, which the user can click to pay for the concert tickets. For example, after the user clicks the "Pay" button, the mobile phone can respond to the user's click on the "Pay" button by switching the mobile phone's display interface from the cashier interface to the order interface 440 shown in Figure 5a(4) (an example of the third interface in S207 above). The order interface 440 is different from the application interface of the ticketing application that provides the concert ticket resources; in other words, the order interface 440 is not the application interface of the ticketing application. For example, the order interface 440 may be a system interface provided by the system of the client 100, and there are no specific limitations.

[0265] In an optional embodiment, the payment interface 430 may also display product description information for concert tickets, concert show times, and concert ticket tiers. For example, as shown in Figure 5a(3), the product description information for concert tickets includes the concert performer and concert address. Concert show times include Saturdays and Sundays, and concert ticket tiers include grandstand and inner field. Grandstand tiers may include NT$380, NT$580, and NT$780 ticket tiers; inner field tiers may include NT$1080, NT$1280, and NT$1580 ticket tiers.

[0266] Please refer to Figure 5a(3). Users can select Saturday and NT$780 for the stands on the payment interface 430 to choose a concert ticket with the performance date on Saturday and the ticket price of NT$780 for the stands.

[0267] In this example, the payment interface 430 is an example of the second interface mentioned above, and the order interface 440 is an example of the third interface mentioned above. Both the second and third interfaces are different from the application interface of the second application (here, the ticketing application).

[0268] In this example, the interface corresponding to payment control 432 is an example of the first interface mentioned above.

[0269] Based on the application scenario shown in Figure 7, describe the implementation process of S207 and the steps preceding it shown in Figure 4.

[0270] To illustrate with a specific example 2, Figure 7 is a schematic diagram of an application scenario provided by an embodiment of this application.

[0271] Taking a mobile phone as an example, as shown in Figure 7(1), the reading interface 510 of the reading application 413 shown in Figure 5a(1) includes a recommendation control 511. For example, the recommendation control 511 is used to display the product description information and "confirm" link of the digital products recommended by the reading application 413 (an example of a second application).

[0272] In this example, the first interface can be the reading interface 510 of the reading application, and the reading application 413 can display the recommendation control 511 by recommending music resources provided by the music application 414 as shown in Figure 5a(1) within the application.

[0273] In a specific embodiment, the reading interface 510 is the reading interface of the novel "XXX". The digital product recommended by the reading application 413 is the theme song of the TV series "AAA" adapted from the novel "XXX". The novel "XXX" is provided by the reading application 413, and the theme song is provided by the aforementioned music application 414.

[0274] As an example, as shown in Figure 7(1), the reading interface 510 displays the content of the novel "XXX", and the recommendation control 511 displays the description information of digital products (e.g., "The theme song of the TV series "AAA" adapted from the novel "XXX" is available for 3 yuan") and the purchase link (e.g., "Confirm" link).

[0275] As another example, the first interface could also be the homepage of the novel "XXX," displaying descriptive information about the novel. For instance, the first interface could display the author, genre, synopsis, and reviews of the novel "XXX."

[0276] Users can click the "Confirm" link displayed on the recommendation control 511 in the display interface 510. In response to the click of the "Confirm" button, the phone's display interface will switch from the reading interface 510 shown in Figure 7(1) to the payment interface 520 (an example of the second interface) shown in Figure 7(2) to purchase the theme song. In this way, the music application 414 is an example of the first application that provides the theme song.

[0277] In this example, the second interface can be the payment interface 520. In some embodiments, this second interface (also called the cashier interface) is a system interface displayed based on the first user input, rather than an application-specific interface.

[0278] As shown in Figure 7(2), the payment interface 520 may include one or more controls, including but not limited to cashier control 521, payment tool control 522, and payment control 523.

[0279] The cashier control 521 displays the outstanding amount for the theme song, the user's payment account, and the user's payment method. For example, as shown in Figure 7(2), the outstanding amount for the theme song is 3 yuan. The user's payment account can be the user's mobile phone number. The user's payment method can be bank card, payment by a friend, account balance, etc.

[0280] The payment tool control 522 displays at least one payment tool. For example, payment tools may include, but are not limited to, bank cards, friend-paid payments, and account balances. Users can select a payment tool in the payment control 522, and the mobile phone, in response to the user's action, displays the selected payment tool in the payment method section of the cashier control 521. For example, if a user selects Bank Card 1 in the payment control, the mobile phone, in response to the user's action, displays Bank Card 1 in the payment method section of the cashier control 521.

[0281] In an optional embodiment, the user can click "View All" displayed on the payment tool control 522, and the mobile phone will respond to the user's operation by displaying all payment tools in the cashier control 521.

[0282] For example, the payment interface 520 may also include product description information for the theme song. This product description information may include information such as the singer of the theme song, the novel and film / television series corresponding to the theme song, etc. This embodiment of the application does not limit the specific content of the product description information for the theme song displayed on the payment interface 520.

[0283] Users can click on the payment control 523 on the payment interface 520. In response to the user's click on the payment control 523, the mobile phone switches the display interface of the mobile phone from the payment interface 520 shown in Figure 7(2) to the display interface 530 shown in Figure 7(3) (an example of the third interface mentioned above).

[0284] In this example, display interface 510 is an example of the first interface mentioned above, payment interface 520 is an example of the second interface mentioned above, and display interface 530 is an example of the third interface mentioned above. Here, the first application is a music application, the second application is a reading application, and the first, second, and third interfaces are all application interfaces of the second application (here, the reading application).

[0285] In this example, the payment control 523 shown in Figure 7(2) is an example of the first interface mentioned above.

[0286] In some other embodiments, the client 100 may display the first interface and the second interface described above simultaneously.

[0287] In an optional embodiment, the first interface can be the display interface 510 shown in Figure 7(1), and the second interface can be a payment window. The client 100 displays the payment window on top of the display interface 510.

[0288] In this embodiment, based on payment description information, a third interface containing information indicating the completion of a digital goods transaction provided by the first application can be displayed outside the first application. This third interface could be, for example, a payment success interface. This eliminates the need to switch the foreground application to the first application, simplifying the process and shortening the time required to use digital goods.

[0289] Optionally, as shown in Figure 4, after S303 above, the method may further include S304.

[0290] S304. Server 10 sends a notification message to Server 11.

[0291] In a specific embodiment, server 10 sends the product identifier of the digital product, the order number of the order corresponding to the traded digital product, and the user identifier of the user to server 11.

[0292] Optionally, after S304, the method may also include S103.

[0293] S103. Server 11 sends resource information of digital goods to client 100.

[0294] In an optional embodiment, the client 100 may invoke the aforementioned out-of-application payment service based on the payment description information to notify the server 11 to send resource information of digital goods to the first application.

[0295] In a specific embodiment, server 11 receives notification information sent by server 10, and then server 11 sends resource information of digital goods to client 100.

[0296] As an example, after receiving a notification from server 10, server 11 can determine the application to which the digital goods belong as the first application based on the notification. Then, server 11 sends the resource information of the digital goods to the first application.

[0297] For example, the resource information for digital goods could be a QR code for a concert ticket. Or, the resource information for digital goods could be game skins. Or, the resource information for digital goods could be a theme song.

[0298] In this embodiment, after a user purchases the digital product on the second interface, they are not redirected to the first application. Instead, they can directly access the system service outside the first application through payment information. The system service then notifies the server of the first application, sending the resource information of the digital product to the first application. This allows the user to use the digital product through the first application. Thus, the transaction can be completed outside the application, eliminating the need to switch the foreground application to the first application, avoiding application login and loading the digital product interface, simplifying the process, and shortening the transaction time.

[0299] Optionally, S208 may also be included after S207 and S103.

[0300] Optionally, in S208, client 100 may, in response to a received second user input to the third interface, invoke the second interface to output resource information of digital goods in the first application, whereby the second user input indicates the use of digital goods. For example, client 100 may invoke the second interface to play a theme song, display concert tickets, or use game skins, etc. The third interface further includes a second interface indicating the output of resource information for digital goods.

[0301] In some embodiments, when outputting the resource information of the digital goods of the first application, the resources of the digital goods of the first application may be output on a third interface.

[0302] In some embodiments, when outputting the resource information of the digital goods of the first application, the display interface may be switched to the fourth interface of the first application so as to output the resources of the digital goods on the fourth interface.

[0303] Based on the specific example 1 above, the implementation process of S207 and the steps preceding it shown in Figure 4 will be described further.

[0304] As shown in Figure 5b(1), the order interface 440 (which can be an example of the order interface 440 shown in Figure 5a(4)) displays the product description information of digital goods, the information of the moviegoers, and the contact information reserved by the users.

[0305] In an optional embodiment, the order interface 440 may include a control 441. A user can click the control 441, and in response, the phone switches its display from the order interface 440 (an example of a third interface) shown in Figure 5b(1) to the interface 470 (an example of a fourth interface) shown in Figure 5b(2), so that the concert ticket resources (an example of digital goods resources) are output on interface 470. The interface corresponding to the control 441 may be an example of the second interface that indicates the output of digital goods resource information. The interface 470 may be the application interface of a ticketing application that provides the concert ticket resources.

[0306] As shown in Figure 5b(2), interface 470 displays a QR code for digital goods (an example of concert ticket resources), which users can use to access the digital goods.

[0307] In this embodiment, digital goods resources can be output on interface 470, allowing users to access the goods within a first application. This ensures that users can access digital goods through the application providing them.

[0308] In an optional embodiment, the interface 470 may also display product description information of concert tickets, the concert show selected by the user, the ticket price of the concert selected by the user, the number of concert tickets selected by the user, information of the audience, and the contact information reserved by the user.

[0309] In this example, the order interface 440 is an example of the third interface mentioned above. Control 441 is an example of the second interface mentioned above.

[0310] In an optional embodiment, the mobile phone may also respond to the user's click on the operation of the control 441 (an example of the second user input) to display the QR code shown in FIG5b(2) on the order interface 440 (an example of the third interface), thereby outputting the digital goods resources of the first application (ticketing application) on the third interface.

[0311] In an optional embodiment, for example, after the mobile phone obtains the QR code of the concert ticket from the first application (ticketing application), the QR code of the concert ticket is displayed on the interface 470.

[0312] In this embodiment, digital product resources can be displayed on the order interface 440, allowing users to access the products outside the first application. This eliminates the need to switch the foreground application to the first application, avoiding processes such as application login and loading the digital product interface, thus simplifying the process and shortening the time required to use the digital products.

[0313] Based on the specific example 2 above, the implementation process of S207 and the steps preceding it shown in Figure 4 will be described further.

[0314] The user can click the playback control 531 in the display interface 530 (an example of the third interface) shown in Figure 7(3) to allow the mobile phone to receive a second user input to the third interface. In response to the user input, the mobile phone switches the display interface 530 shown in Figure 7(3) to the display interface 510 shown in Figure 7(4) and displays the playback control 531 on the display interface 510 (an example of the fourth interface of the first application (reading application)). The playback control 531 displays the song name and a status switch button. The user can click the status switch button to play or pause the theme song.

[0315] In an optional embodiment, the display interface 510 may not include the playback control 531, and the mobile phone can play the theme song in the background.

[0316] In this example, the display interface 510 is an example of the fourth interface mentioned above. The interface corresponding to the playback control 531 is an example of the second interface mentioned above.

[0317] In this embodiment, instead of redirecting to the first application, the system operates directly outside the first application. Responding to input from a second user instructing them to use the digital product, the system outputs the digital product's resource information via a second interface. This allows users to use the digital product outside the first application without switching the foreground application to the first application, avoiding processes such as application login and loading the digital product's interface. This simplifies the process and shortens the time required to use the digital product.

[0318] In this embodiment, the resources for digital goods can be output on a third interface or a fourth interface of the first application. The third interface differs from the interface of the first application. This allows users to use digital goods both outside and within the first application, expanding the usage scenarios for digital goods.

[0319] Furthermore, using digital goods outside the primary application eliminates the need to switch the foreground application to the primary application, avoiding processes such as application login and loading the digital goods interface, thus simplifying the process and shortening the time required to use digital goods.

[0320] The following describes the implementation process of S204 and the steps preceding it shown in Figure 4, using the application scenario shown in Figure 6 as an example.

[0321] In the application scenario shown in Figure 6, the first interface is the application interface of the second application, not the notification message interface.

[0322] Figure 6 is a schematic diagram of another application scenario provided by an embodiment of this application.

[0323] As an example, in conjunction with Figure 5a(1), a user can click on the Messages application 415 on the display interface 410 shown in Figure 5a(1), and the mobile phone can respond to the user's operation by switching the mobile phone's display interface from the display interface 410 shown in Figure 5a(1) to the SMS interface 480 shown in Figure 6.

[0324] As another example, the phone can respond to user input by switching its display interface from Figure 5a(1) to a text message list interface (not shown in the figure). When the user clicks on a corresponding text message in the text message list interface, the phone responds to the user input by switching its display interface from Figure 5a(1) to the text message interface 480 shown in Figure 6. In this example, the text message interface 480 is an example of the first interface mentioned above. Here, the first application is a game application, and the first interface is the application interface of the second application (here, the text message application). That is to say, the phone can recommend digital goods (such as game skins) provided by the game application via text message within the text message application.

[0325] The SMS interface 480 shown in Figure 6 includes an SMS control 481. The SMS control 481 can display product description information of digital goods (e.g., "[Skin XX] is a quality skin for the game application, available in limited quantities, only 2 yuan for the first release!") and a purchase link for digital goods (e.g., "www.xxx.com"). The product description information may specifically include Skin XX and the price of Skin XX. As shown in Figure 6, the user can click the purchase link (the corresponding interface can be the first interface mentioned above). The user's click on the link is an example of the first user input. The mobile phone can respond to the first user input and switch the mobile phone's display interface from the SMS interface 480 shown in Figure 6 to the cashier interface (e.g., the payment interface 520 shown in Figure 7(2)) where the game skin can be purchased. Thus, the game skin can be purchased without logging in and switching to the application interface of the game application. Other processes related to the resource output and use of the game skin can be referred to the relevant principles of the embodiment in Figure 7, which will not be repeated here.

[0326] The following describes the implementation process of S204 and the steps preceding it shown in Figure 4, using the application scenario shown in Figure 8 as an example.

[0327] Figure 8 is a schematic diagram of another application scenario provided by an embodiment of this application.

[0328] In the application scenario shown in Figure 8, the purchase of recommended music resources (provided by the music application) can be realized within the notification message of the reading application.

[0329] As shown in Figure 8(1), the display interface 410 shown in Figure 8(1) is the same as the display interface 410 shown in Figure 5a(1) above, and will not be described again here.

[0330] The user can click on the reading application 413 on the display interface 410 shown in Figure 8(1). The mobile phone can respond to the user's operation and switch the display interface of the mobile phone from the display interface 410 shown in Figure 8(1) to the display interface 550 shown in Figure 8(2). The display interface 550 is the main interface of the reading application 413 (an example of a second application). The main interface may include one or more controls, including but not limited to the message control 551.

[0331] The user can click on message control 551, and the mobile phone can respond to the user's operation by switching the mobile phone's display interface from display interface 550 shown in Figure 8(2) to display interface 560 shown in Figure 8(3). Display interface 560 (an example of the first interface) is the message display interface of reading application 413. The message display interface may include one or more controls, including but not limited to notification control 561. Notification control 561 is used to display product description information and "buy" links of digital products recommended by reading application 413 (the corresponding interface is an example of the first interface).

[0332] For example, the digital product is the theme song for the TV series "AAA," adapted from the novel "XXX." The novel "XXX" is provided by the reading application 413, and the theme song is provided by the aforementioned music application 414. The notification control 561 displays a description of the theme song and a purchase link (e.g., a "Buy" link).

[0333] In optional embodiments, the main interface may also include a "Bookstore" control and a "My" control. Users can click the "Bookstore" control to view other books provided by the reading application 413, and users can click the "My" control to view their own information. This application embodiment does not impose any limitations on this.

[0334] In optional embodiments, the message display interface may also include other controls. For example, the message display interface may also include notification controls for novel updates and notification controls for new novels, and this application embodiment does not impose any limitations on this.

[0335] As shown in Figure 8(3), when the user clicks the “Purchase” link in the notification control 561, the phone receives the first user input and displays the first interface. The specific process is similar to the description of other scenarios above, and will not be repeated here. In this way, the user can purchase music resources outside the second application (such as a music application) by entering the first user input in the notification message list of the reading application.

[0336] In conjunction with any of the above embodiments, FIG9 exemplarily illustrates a flowchart of another interface display method of this application.

[0337] As shown in Figure 9, client 100 includes an application layer and a system service layer. The application layer includes game applications, content applications, and electronic ticketing applications, etc. The system service layer includes out-of-application payment services, push services, etc.

[0338] Server 10 includes a payment center, an order center, and a product center.

[0339] Referring to Figure 9, in step 1, server 11 lists digital products in the product center and pushes the digital products to the push service via step 2. The push service can send push notifications. For example, the push service can display a product push interface (an example of the first interface) via step 3. The product push interface may include description information of the digital products and a "Buy" button (an example of the first interface).

[0340] Step 4: The user clicks the "Buy" button to invoke the out-of-app payment service. Optionally, during the invocation of the out-of-app payment service, the product identifier of the digital goods is sent to the out-of-app payment service.

[0341] The out-of-app payment service places an order for digital goods based on their product identifiers. Specifically, the out-of-app payment service sends the digital goods' product identifiers to the product center in step 5.

[0342] Based on the product identifier, the product center determines the payment description information for the digital product and sends this information to the external payment service via step 6. In step 7, the external payment service displays the checkout interface (an example of the second interface) based on the payment description information. This checkout interface includes the payment description information for the digital product and a "Pay" button (an example of the second interface).

[0343] Step 8: The user clicks the "Pay" button to invoke the external payment service to complete the digital goods transaction. The application payment service then sends the user's payment account information to the payment center in Step 9 to process the payment. After successful payment, the payment center sends a payment success request to the order center in Step 10.

[0344] Step 11: Based on the successful payment request, the order center notifies the server 11 to ship the digital goods. For example, the order center sends the product identifier, order number, and user identifier to the server 11.

[0345] Server 11 sends the resource information of the digital product to the application to which the digital product belongs via step 12. For example, as shown in Figure 9, the digital product is an electronic ticket, and the application to which the digital product belongs is an electronic ticket application. Server 11 sends the QR code of the electronic ticket to the electronic ticket application.

[0346] Corresponding to the above-described interface display method, this application also provides an interface display device. Figure 10 is a schematic diagram of the structure of an exemplary interface display device 700. Referring to Figure 10, the interface display device 700 includes:

[0347] Display module 701 is used to display a first interface, which includes product description information of the digital product. The first interface is associated with a product identifier of the digital product and a first interface that indicates the invocation of system services. The first interface is different from the application interface of the first application that provides the digital product. Display module 701 is also used to respond to a first user input received on the first interface and display a second interface based on the product identifier and the first interface. The first user input indicates a request to purchase the digital product, and the system service indicates that payment description information of the digital product is obtained based on the product identifier. The second interface includes the payment description information.

[0348] In one possible implementation, the display module 701 is specifically used to: pass the product identifier to the first interface, and call the system service through the first interface to display the second interface.

[0349] In one possible implementation, the first interface is the application interface of the second application, and the first application is different from the second application.

[0350] In one possible implementation, the display module 701 is specifically used to: display the second interface within the application interface of the second application based on the product identifier and the first interface.

[0351] In one possible implementation, the first interface is a notification message interface.

[0352] In one possible implementation, the display module 701 is further configured to display a third interface based on payment description information. The third interface includes information indicating that the digital goods transaction provided by the first application has been completed. The third interface is different from the application interface of the first application.

[0353] In one possible implementation, the third interface further includes a second interface that indicates the output of resource information of the digital goods, and the interface display device 700 further includes an output module 702, which, in response to a received second user input to the third interface, calls the second interface to output the resource information of the digital goods of the first application, wherein the second user input indicates the use of the digital goods.

[0354] In one possible implementation, the output module 702 is specifically used to: output the resources of digital goods of the first application on the third interface; or, switch the display interface to the fourth interface of the first application to output the resources of digital goods on the fourth interface.

[0355] In one possible implementation, the interface display device 700 further includes a notification module 703, which, based on payment description information, calls a system service to notify the server of the first application to send resource information of digital goods to the first application.

[0356] The effect of the above-described interface display device is similar to that of the interface display method executed by the client 100 in the above embodiments, and will not be described again here.

[0357] It is understood that, in order to implement the above functions, the client 800 includes hardware and / or software modules corresponding to the execution of each function. Based on the algorithm steps of the examples described in the embodiments disclosed herein, this application can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed in hardware or by computer software driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application in conjunction with the embodiments, but such implementation should not be considered beyond the scope of this application.

[0358] In one example, Figure 11 shows a schematic block diagram of a client 800 according to an embodiment of the present application. The client 800 may include: a processor 801, optionally a transceiver / transceiver pin 802, and optionally a memory 803.

[0359] The various components of client 800 are coupled together via bus 804, which includes a data bus, a power bus, a control bus, and a status signal bus. However, for clarity, all buses are referred to as bus 804 in the diagram.

[0360] Optionally, the memory 803 can be used for the instructions in the foregoing method embodiments. The processor 801 can be used to execute the instructions in the memory 803 to implement the foregoing method. Furthermore, the processor 801 can be used to control the receive pin to receive signals and to control the transmit pin to transmit signals.

[0361] Optionally, the processor 801 is used to run computer programs or software code or instructions 508 therein to implement the interface display methods provided in the embodiments of this application.

[0362] For example, the structure of the client in this application is not limited to that shown in Figure 11. The client 800 can be a standalone device or part of a larger device. For instance, the implementation of the client 800 could be:

[0363] (1) A standalone integrated circuit IC, or chip, or chip system or subsystem; (2) A collection of one or more ICs, optionally including storage components for storing data or instructions; (3) A module that can be embedded in other devices; (4) Vehicle equipment, etc.; (5) Others, etc.

[0364] When the client 800 is implemented as a chip or chip system, the chip or chip system may include a processor and an interface. The number of processors may be one or more, and the number of interfaces may be multiple. Optionally, the chip or chip system may include a memory 803. The processor is used to call and execute instructions from the interface, and when the processor executes the instructions, it can implement the steps of the above method embodiments.

[0365] Client 800 can be an electronic device or a chip of an electronic device in the above method embodiments.

[0366] All relevant content of each step involved in the above method embodiments can be referenced from the functional description of the corresponding functional module, and will not be repeated here.

[0367] This embodiment also provides a computer storage medium storing computer instructions. When the computer instructions are executed on an electronic device, the electronic device performs the aforementioned method steps to implement the interface display method in the above embodiment.

[0368] This embodiment also provides a computer program product that, when run on a computer, causes the computer to perform the aforementioned steps to implement the interface display method in the above embodiment.

[0369] In addition, embodiments of this application also provide an apparatus, which may specifically be a chip, component or module. The apparatus may include a connected processor and a memory; wherein the memory is used to store computer execution instructions, and when the apparatus is running, the processor may execute the computer execution instructions stored in the memory to cause the chip to execute the interface display method in the above method embodiments.

[0370] In this embodiment, the client, computer storage medium, computer program product or chip are all used to execute the corresponding methods provided above. Therefore, the beneficial effects they can achieve can be referred to the beneficial effects in the corresponding methods provided above, and will not be repeated here.

[0371] Through the above description of the embodiments, those skilled in the art will understand that, for the sake of convenience and brevity, only the division of the above functional modules is used as an example. In actual applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above.

[0372] In the several embodiments provided in this application, it should be understood that the disclosed apparatus and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of modules or units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another apparatus, or some features may be ignored or not executed. Furthermore, the mutual coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

[0373] The units described as separate components may or may not be physically separate. A component shown as a unit can be one or more physical units; that is, it can be located in one place or distributed in multiple different locations. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0374] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0375] Any content in the various embodiments of this application, as well as any content in the same embodiment, can be freely combined. Any combination of the above content is within the scope of this application.

[0376] The steps of the methods or algorithms described in conjunction with the embodiments of this application can be implemented in hardware or by a processor executing software instructions. The software instructions can consist of corresponding software modules, which can be stored in random access memory (RAM), flash memory, read-only memory (ROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), registers, hard disks, portable hard disks, CD-ROMs, or any other form of storage medium well known in the art. An exemplary storage medium is coupled to a processor, enabling the processor to read information from and write information to the storage medium. Of course, the storage medium can also be a component of the processor. The processor and the storage medium can reside in an ASIC.

[0377] Those skilled in the art will recognize that the functions described in the embodiments of this application in one or more of the above examples can be implemented using hardware, software, firmware, or any combination thereof. When implemented using software, these functions can be stored in a computer-readable medium or transmitted as one or more instructions or code on a computer-readable medium. Computer-readable media include computer storage media and communication media, wherein communication media include any medium that facilitates the transfer of a computer program from one place to another. Storage media can be any available medium that can be accessed by a general-purpose or special-purpose computer.

[0378] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit them. 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 protection scope of the technical solutions of the embodiments of this application.

Claims

1. A method for displaying an interface, characterized in that, The method includes: The first interface is displayed, which includes product description information of digital goods. The first interface is associated with the product identifier of the digital goods and a first interface for invoking system services. The first interface is different from the application interface of the first application that provides the digital goods. In response to a first user input received on the first interface, a second interface is displayed based on the product identifier and the first interface. The first user input indicates a request to purchase the digital product, and the system service indicates that payment description information of the digital product is obtained based on the product identifier. The second interface includes the payment description information.

2. The method according to claim 1, characterized in that, The step of displaying a second interface based on the product identifier and the first interface includes: The product identifier is passed to the first interface, and the system service is called through the first interface to display the second interface.

3. The method according to claim 1, characterized in that, The first interface is the application interface of the second application, and the first application is different from the second application.

4. The method according to claim 3, characterized in that, The step of displaying the second interface based on the product identifier and the first interface includes: Based on the product identifier and the first interface, the second interface is displayed within the application interface of the second application.

5. The method according to any one of claims 1 to 4, characterized in that, The first interface is the notification message interface.

6. The method according to any one of claims 1 to 5, characterized in that, The method further includes: A third interface is displayed based on the payment description information. The third interface includes information indicating that the digital goods transaction provided by the first application has been completed. The third interface is different from the application interface of the first application.

7. The method according to claim 6, characterized in that, The third interface further includes a second interface that indicates the output of resource information for the digital goods, and the method further includes: In response to a second user input received on the third interface, the second interface is invoked to output resource information of the digital goods of the first application, wherein the second user input indicates the use of the digital goods.

8. The method according to claim 7, characterized in that, The step of outputting the resource information of the digital goods of the first application includes: The third interface outputs the resources of the digital goods of the first application; or, The display interface will be switched to the fourth interface of the first application to output the resources of the digital goods on the fourth interface.

9. The method according to any one of claims 1 to 8, characterized in that, The method further includes: Based on the payment description information, the system service is invoked to notify the server of the first application to send the resource information of the digital goods to the first application.

10. An interface display device, characterized in that, The device includes: The display module is used to display a first interface, which includes product description information of digital goods. The first interface is associated with the product identifier of the digital goods and a first interface that indicates the invocation of system services. The first interface is different from the application interface of the first application that provides the digital goods. The display module is further configured to respond to a first user input received on the first interface, and display a second interface based on the product identifier and the first interface, wherein the first user input indicates a request to purchase the digital product, and the system service indicates obtaining payment description information of the digital product based on the product identifier, and the second interface includes the payment description information.

11. The apparatus according to claim 10, characterized in that, The display module is specifically used for: The product identifier is passed to the first interface, and the system service is called through the first interface to display the second interface.

12. The apparatus according to claim 10, characterized in that, The first interface is the application interface of the second application, and the first application is different from the second application.

13. The apparatus according to claim 12, characterized in that, The display module is specifically used for: Based on the product identifier and the first interface, the second interface is displayed within the application interface of the second application.

14. The apparatus according to any one of claims 10 to 13, characterized in that, The first interface is the notification message interface.

15. The apparatus according to any one of claims 10 to 14, characterized in that, The display module is further configured to display a third interface based on the payment description information. The third interface includes information indicating that the digital goods transaction provided by the first application has been completed. The third interface is different from the application interface of the first application.

16. The apparatus according to claim 15, characterized in that, The third interface further includes a second interface that indicates the output of resource information for the digital goods, and the device further includes: An output module is configured to, in response to a received second user input to the third interface, invoke the second interface to output resource information of the digital goods of the first application, wherein the second user input indicates the use of the digital goods.

17. The apparatus according to claim 16, characterized in that, The output module is specifically used for: The third interface outputs the resources of the digital goods of the first application; or, The display interface will be switched to the fourth interface of the first application to output the resources of the digital goods on the fourth interface.

18. The apparatus according to any one of claims 10 to 17, characterized in that, The device further includes: The notification module is used to invoke the system service based on the payment description information to notify the server of the first application to send the resource information of the digital goods to the first application.

19. An interface display device, characterized in that, The interface display device includes a processor, which is configured to execute instructions. When the instructions are executed by the processor, the processor is configured to perform the method as described in any one of claims 1 to 9.

20. A computer-readable storage medium, characterized in that, Includes a computer program that, when running on a computer or processor, causes the computer or processor to perform the method as described in any one of claims 1 to 9.

21. A computer program product, characterized in that, The computer program product includes a software program that, when executed by a computer or processor, causes the steps of the method described in any one of claims 1 to 9 to be performed.

22. A chip, characterized in that, The chip includes a processor and a communication interface, wherein the processor is configured to call and execute instructions from the communication interface, and when the processor executes the instructions, it implements the method as described in any one of claims 1 to 9.

Images