Electronic payment method, electronic device, storage medium, and computer program product

Abstract

The application relates to the technical field of intelligent terminals, in particular to an electronic payment method, an electronic device, a storage medium and a computer program product, a plurality of payment applications and a payment management application are installed on the electronic device, the method comprises the following steps: the payment management application detects a first payment operation of a user in the payment management application, wherein the first payment operation indicates that a payment function is completed by using a first payment application in the plurality of payment applications; the payment management application calls the payment function of the first payment application to complete the payment function corresponding to the first payment operation. According to the application, the payment management application is arranged to manage the plurality of payment applications installed on the electronic device, a payment capability module for providing a payment function in each payment application exists in the form of an independent atomic capability module in a distributed operating system carried by the electronic device, the payment management application completes payment by calling the payment capability module, and the payment behavior of the user can be uniformly managed.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of intelligent terminals, and in particular to an electronic payment method, an electronic device, a storage medium and a computer program product. BACKGROUND

[0002] With the development of intelligent terminals and Internet technology, mobile payment has gradually become the mainstream payment method of people. At present, in many payment scenarios, users can not only use various terminal devices to perform payment behavior, such as mobile phones, watches, bracelets, etc., but also can arbitrarily select payment channels, such as completing payment behavior through payment channels such as Alipay TM , WeChat TM , UnionPay Cloud Flash Payment TM , and bank client, etc. The above payment channels are provided by payment applications with payment functions such as Alipay TM , WeChat TM , UnionPay Cloud Flash Payment TM , and bank client, etc.

[0003] It can be understood that in offline scenarios, when a user performs a payment operation, the user generally opens a payment application on a terminal device to show a payment code to a merchant to perform payment, or opens a payment application on a terminal device to scan a payment code provided by a merchant to perform payment. In online scenarios, when a user needs to perform a payment operation, for example, in an online shopping scenario, after a user selects a product, if the shopping application used by the user to perform the payment operation itself has payment function, such as Meituan TM , the user can complete payment after clicking the payment option and inputting a payment password or fingerprint verification. If the shopping application used by the user to perform the payment operation itself does not have payment function, the user will be redirected to a third-party payment application to complete payment after clicking the payment option, for example, the user can select to be redirected to Alipay TM to perform payment after clicking the payment option in Taobao TM .

[0004] In the above payment operation process, no matter which payment application is used by the user to complete payment, each payment application can only record and count payment data generated by the payment application itself, such as bills. However, the bills counted in each payment application cannot completely cover all payment behaviors of the user. In other words, the existing payment application cannot obtain payment and receipt data on other payment applications, and it is difficult to comprehensively count all payment and receipt behaviors of the user, so the user cannot comprehensively, accurately and intuitively understand the income and expenditure situation of the user. Based on this, the user cannot obtain comprehensive and accurate payment and receipt statistical analysis or financial advice services based on any payment application. SUMMARY

[0005] The electronic payment method, the electronic device, the storage medium and the computer program product provided in the embodiments of the present application can manage a plurality of payment applications installed on an electronic device by setting a payment management application, each function module of each payment application exists in the form of an independent atomic capability module in a distributed operating system carried by the electronic device, and the payment management application can complete a payment operation by calling a payment capability module of an authorized payment application, thereby facilitating unified management of payment behaviors of a user; the payment management application can also obtain historical payment data on each payment application through the payment capability module, thereby summarizing payment records and comprehensively counting payment behaviors of the user, so that the payment behaviors of the user can be comprehensively analyzed, and a comprehensive financial analysis report or financial suggestion is provided for the user, thereby improving user experience.

[0006] In a first aspect, the embodiments of the present application provide an electronic payment method applied to an electronic device, the electronic device being installed with a plurality of payment applications and a payment management application, and the method comprising: detecting, by the payment management application, a first payment operation of a user in the payment management application, wherein the first payment operation indicates that a payment function is completed by using a first payment application in the plurality of payment applications; and calling, by the payment management application, the payment function of the first payment application to complete the payment function corresponding to the first payment operation.

[0007] That is, the payment management application installed on the electronic device has a function of managing a plurality of payment applications installed on the electronic device, mainly managing payment functions of the payment applications, and when the user performs a payment operation by opening the payment management application, the payment management application can call the payment function of the managed payment application to complete the payment. The payment management application can be a payment management platform installed on a mobile phone described in the embodiments below, for example, the payment management platform can call the payment function of the managed Alipay application to complete the payment. TM TM TM That is, the payment management platform can independently complete the payment function of the Alipay application by calling the payment capability module of the Alipay application. TM TM

[0008] In a possible implementation of the first aspect, the payment management application calling the payment function of the first payment application comprises: the payment management application calling the payment function of the first payment application to generate a payment code and display the payment code in a display interface of the payment management application; or the payment management application calling the payment function of the first payment application to display a scan code window in the display interface of the payment management application.

[0009] ​​​​That is, the user opens the payment management application on the electronic device, for example, the payment management platform installed on the mobile phone described in the embodiments below, the user can click the payment code / sweep code payment button in the interface of the payment management platform to open the payment code and show it to the merchant for payment, or click the payment code / sweep code payment button in the interface of the payment management platform to open the sweep code window and scan the payment code displayed by the merchant for payment.

[0010] In a possible implementation of the first aspect, the payment management application displays prompt information indicating that the payment corresponding to the first payment operation has been completed.

[0011] That is, after completing the payment, the payment management application interface can display a payment success prompt message or a notification window to inform the user that the payment operation has been completed.

[0012] In a possible implementation of the first aspect, the payment management application invokes the payment function of the first payment application, and after completing the payment function corresponding to the first payment operation, the method further includes: the payment management application records first payment data generated by completing the first payment operation.

[0013] That is, the payment management application generates corresponding payment data for recording when the user performs a payment operation through the payment management application. For example, the payment management platform described in the embodiments below records the payment record of the user completing the payment through the payment management platform, including recording the payment time and the payment amount, and the data content contained in the payment data will be described in detail below, which will not be described here.

[0014] In a possible implementation of the first aspect, before the payment management application detects the first payment operation of the user in the payment management application, the method further includes: displaying authorization prompt information to the user in the display interface of the payment management application or the display interface of the first application, wherein the authorization prompt information is used to prompt the user whether to authorize the management right of the payment function of the first payment application to the payment management application; in the case of detecting the authorization operation of the user, the management right of the payment function of the first payment application is authorized to the payment management application, and prompt information indicating that the authorization is successful is displayed.

[0015] The process of the payment management application obtaining the permission to manage the payment application needs to be authorized by the user. When the user operates to open the payment management application, the electronic device displays the interface of the payment management application and simultaneously displays authorization prompt information on the interface, prompting the user to select the payment application that can be added to the payment management application for management, and completes the authorization; or when the user operates to open a certain payment application, the electronic device displays the interface of the payment application and simultaneously displays the authorization prompt information, prompting the user to authorize the payment function of the payment application to the payment management application. After the user completes the authorization operation according to the prompt information, the electronic device displays the prompt information of successful authorization. For example, the mobile phone described with reference to FIG. 11 in the following embodiment when running the payment management platform for the first time can display a list of payment applications that can be added to the payment management platform for management, including Alipay TM , WeChat TM , and Yunshenfu TM , and the user can complete the authorization operation by checking the payment application in the list and clicking the confirmation button. After the authorization is successful, the interface of the payment management platform displays the prompt information of successful authorization. For another example, the mobile phone described with reference to Figure 8 in the following embodiment when running the Alipay TM application for the first time can display a notification of adding the running Alipay TM application to the payment management platform for management. The user can complete the authorization operation by clicking the add button on the notification. After the authorization is successful, the interface of the Alipay TM application displays the prompt information of successful authorization. It can be understood that the authorization prompt information displayed by the mobile phone when running the payment management platform or the Alipay TM application can include a check box that allows the user to select not to display the prompt information next time the mobile phone is running. Refer to the check box 804 shown in the following embodiment Figure 8 to avoid the prompt information from being displayed frequently, which can disturb the user and affect the user experience.

[0016] In a possible implementation of the first aspect, the management permission includes that the payment management application can complete payment by calling the payment function of the first payment application, and the payment management application can obtain the first historical payment data from the first payment application.

[0017] That is, after the payment management permission obtains the payment function management permission of the payment application, the payment management permission not only can call the payment function of the payment application to perform the payment operation, but also can obtain the historical payment data (i.e., the first historical payment data) recorded on the payment application. For example, the payment management platform described in the following embodiment not only can call Alipay TM to perform payment, but also can obtain the historical payment data on Alipay TM , including the historical payment data before the Alipay TMThe payment record data generated by the completed payment operation also includes the payment data of the user operating the Alipay through the mobile phone after the payment management platform is authorized to manage TM The payment record data generated by the completed payment operation also includes the payment data of the user operating the Alipay through the mobile phone after the payment management platform is authorized to manage

[0018] In a possible implementation of the first aspect, the method further includes: generating, by the payment management application, a payment record of at least one user of the electronic device based on the first historical payment data and the second historical payment data, wherein the second historical payment data is record data of a payment operation completed by the payment management application calling the first payment application.

[0019] That is, the payment data generated by the payment management application calling the payment function of the payment application to perform the payment operation (i.e., the second historical payment data described above), and the historical payment data recorded on the payment application and obtained by the payment management application (i.e., the first historical payment data described above), the payment management application can summarize the two types of historical payment data to generate a payment record, i.e., the accounting classification data counted by the accounting classification module described in the embodiments below. It can be understood that the payment management application can obtain the management authority of the payment function of one or more payment applications, and the accounts logged in each payment application can be the same user's account or different user's accounts; in another embodiment, the payment management application or the same payment application can log in two or more user accounts during different periods, and the payment management application can perform account-by-account statistics on the historical payment data of different users after summarizing the two types of historical payment data to generate payment record data corresponding to each user.

[0020] For example, the payment management platform described in the embodiments below can obtain the historical payment data of one or more users logged in during the running of the Alipay TM , WeChat TM , and Cloud Flash Payment TM , and combine the historical payment data corresponding to the payment performed by the user through the payment management platform to generate a payment record corresponding to the account of one or more users.

[0021] In a possible implementation of the first aspect, the first historical payment data or the second historical payment data includes one or more of the following: time of occurrence of the payment operation, transaction nature, merchant name, payee account, merchant single number, payment method, payer account, and serial number.

[0022] In a possible implementation of the first aspect, the method further includes: generating a financial analysis report or a financial suggestion corresponding to the user based on the payment record of the user.

[0023] That is, the payment management application can generate a financial analysis report or a financial suggestion suitable for the user according to the statistical payment record corresponding to each user. It can be understood that the payment management application can be pre-installed with a generation rule of the financial analysis report or a generation rule of the financial suggestion, for example, the generation rule can be realized by a professional big data financial algorithm. For example, the big data financial analysis function of the big data financial suggestion module of the payment management platform described in the following embodiment.

[0024] In a possible implementation of the first aspect, the display interface of the payment management application includes an authorization management control.

[0025] In a possible implementation of the first aspect, the method further includes: after detecting the operation of the user on the authorization management control, the payment management application displays the authorized payment application and the unauthorized payment application to the user; and after detecting that the user confirms to authorize at least one unauthorized payment application, the payment management application acquires the management permission of the payment function of the payment application authorized by the user, and displays prompt information indicating that the authorization is successful. After detecting the operation of the user on the authorization management control, the payment management application deletes the payment application selected by the user to terminate the authorization.

[0026] That is, the authorization management control capable of managing the authorization or the cancellation of authorization of each payment application can be set on the interface of the payment management application, for example, the application setting button on the payment management platform described in the following embodiment. The user can click the application setting button on the interface of the payment management platform to perform the authorization operation on the payment application that has not been authorized, or cancel the authorization of the payment application that has been authorized by the payment management platform, and stop the management of the payment function of the payment application.

[0027] In a possible implementation of the first aspect, the operating system of the electronic device includes a Harmony operating system.

[0028] That is, the electronic device running the payment management application can adopt a Harmony operating system (HarmonyOS), for example, as described in the following embodiment, in the HarmonyOS carried by the electronic device, the payment function of each payment application can be an independent payment capability module (for example, a payment FA), and after the payment management application acquires the management permission of the payment function of each payment application, the payment management application can call the payment capability module (payment FA) of each payment application through the application portal module of the payment management application to complete the payment, which will not be described here.

[0029] In a second aspect, the embodiments of the present application provide an electronic device, which includes: one or more processors; one or more memories; and one or more programs stored in the one or more memories and configured to, working with the one or more processors, cause the electronic device to perform the above-mentioned electronic payment method.

[0030] In a third aspect, the embodiments of the present application provide a computer readable storage medium, which stores instructions. The instructions, when executed on a computer, cause the computer to perform the electronic payment method.

[0031] In a fourth aspect, the embodiments of the present application provide a computer program product, which comprises computer programs / instructions. The computer programs / instructions, when executed by a processor, implement the electronic payment method.

[0032] For example, the computer program product is a payment management application, such as a payment management platform or a wallet application, which is not limited herein. BRIEF DESCRIPTION OF DRAWINGS

[0033] Figure 1 An application scenario of an electronic payment method provided by the embodiments of the present application is shown.

[0034] Figure 2 An exemplary system architecture block diagram of a Harmony operating system 200 provided by the embodiments of the present application is shown.

[0035] Figures 3A-3B An operation interface schematic diagram of a payment management application provided by the embodiments of the present application is shown.

[0036] Figure 4 A composition schematic diagram of a Harmony operating system APP provided by the embodiments of the present application is shown.

[0037] Figure 5 An architecture schematic diagram of a payment system provided by the embodiments of the present application is shown.

[0038] Figure 6A An exemplary structure schematic block diagram of a payment management platform 300 provided by the embodiments of the present application is shown.

[0039] Figure 6B A function interface schematic diagram of a payment management platform 300 provided by the embodiments of the present application is shown.

[0040] Figure 7 An implementation flowchart of a method for identifying a payment application and adding the payment application to unified management of a payment management platform 300 provided by the embodiments of the present application is shown.

[0041] Figure 8 An interface schematic diagram displayed by a mobile phone 100 provided by the embodiments of the present application is shown.

[0042] Figure 9 An interface schematic diagram displayed by a mobile phone 100 provided by the embodiments of the present application is shown.

[0043] Figure 10 Fig. 19 shows an implementation flowchart of a method for identifying a payment application and adding the payment application to the unified management of the payment management platform 300 according to an embodiment of the present application.

[0044] Figures 11A-11C Fig. 20 shows an interface displayed by the mobile phone 100 according to an embodiment of the present application.

[0045] Figure 12 Fig. 21 shows an operation flowchart of payment through the payment management platform 300 according to an embodiment of the present application.

[0046] Figure 13 Fig. 22 shows a structural schematic block diagram of a mobile phone 100 according to an embodiment of the present application.

[0047] Figure 14 Fig. 23 shows another structural schematic block diagram of a mobile phone 100 according to an embodiment of the present application. DETAILED DESCRIPTION

[0048] Various aspects of illustrative embodiments will now be described using terminology commonly employed by those skilled in the art to convey the substance of their work to others skilled in the art. However, it will be apparent to those skilled in the art that alternative embodiments can be practiced with some alternative features to those described herein. For purposes of explanation and ease of understanding, specific details are set forth to provide a more thorough understanding of illustrative embodiments. However, it will be apparent to those skilled in the art that alternative embodiments can be practiced without specific details. In some instances, some well-known features are omitted or simplified in order not to obscure illustrative embodiments of the present application.

[0049] For the purpose of making the objects, technical solutions and advantages of the present application clearer, the technical solutions of the embodiments of the present application will be described in further detail below in combination with the drawings and embodiments.

[0050] The illustrative embodiments of the present application include, but are not limited to, electronic payment methods, electronic devices, storage media and computer program products, etc.

[0051] Figure 1 Fig. 18 shows an application scenario of an electronic payment method according to an embodiment of the present application.

[0052] The scenario includes a mobile phone 100, which is installed with multiple payment applications, such as Alipay TM 101, WeChat TM 102, Cloud Flash Payment TM 103 and bank client 104, etc., and is also installed with a payment management application 105.

[0053] When users need to make payments for goods or services purchased online or offline, they can use the payment application installed on their mobile phone to scan the QR code provided by the merchant's terminal, or they can use the payment application installed on their mobile phone to show their payment code. For example, users can use WeChat on their mobile phone. TM 102 or Alipay TM 101. Scan the merchant's QR code or show your payment code to complete the payment. Secondly, when users want to send red envelopes to relatives and friends, for example, they can do so via WeChat. TM 102. Click the "Send Red Envelope" button, enter the red envelope amount and number of red envelopes to send a red envelope. Alternatively, when a user needs to transfer money to someone else, they can also open the bank's mobile app 100, click the "Transfer" button, and enter the transfer amount to transfer money. This bank app could be, for example, the China Construction Bank app, the China Merchants Bank app, etc., and is not limited here. As described in the background technology above, Alipay... TM 101. WeChat TM 102. UnionPay QuickPass TM Payment applications such as 103 and bank client 104 only record payment data generated by payment operations within their respective applications, and cannot comprehensively record users' payment behavior.

[0054] As mentioned earlier, in various current payment scenarios, existing payment applications cannot provide payment management services that comprehensively record user payment behavior. Therefore, it is also difficult to conduct statistical analysis of user payment behavior and provide users with scientific and reasonable financial advice.

[0055] To address the aforementioned issues, this application provides an electronic payment method. The electronic device used in this method has multiple payment applications installed, along with a payment management application capable of managing these applications. Each functional module of the payment applications exists as an independent atomic capability module within the distributed operating system of the electronic device. The module that enables the payment application to perform payment functions is called a payment capability module. This payment capability module can be called not only by the corresponding payment application itself but also by the payment management application. Based on these independently callable payment capability modules, on the one hand, payment data recorded by the user through the payment application can be sent to the payment management application for aggregated payment and receipt management; on the other hand, the user can directly call the corresponding payment capability module of the payment application through the payment management application to complete the payment.

[0056] For example, refer to Figure 1 As shown, the operating system on the mobile phone 100 is a distributed operating system, such as HarmonyOS. The Alipay app installed on the mobile phone 100 is mentioned above. TM 101. WeChat TM 102. UnionPay QuickPassTM 103 and bank client 104, etc. have corresponding payment capability modules that can be independently invoked. The payment management application 105 installed on the mobile phone 100 can obtain the management authority of the payment functions of each payment application through user authorization. On the one hand, the user can perform payment operations through the Alipay TM 101, WeChat TM 102, Cloud Flash Pay TM 103 and bank client 104, etc. have corresponding payment capability modules that can be independently invoked. The payment management application 105 installed on the mobile phone 100 can obtain the management authority of the payment functions of each payment application through user authorization. On the one hand, the user can perform payment operations through the Alipay TM 101, WeChat TM 102, Cloud Flash Pay TM 103 or bank client 104 corresponding to the payment capability module directly.

[0057] It can be understood that the payment management method provided by the present application can uniformly manage multiple payment applications installed on the mobile phone 100, and the user can also uniformly perform payment or collection operations through the payment management application 105, which is convenient for management and also convenient for security. The file encryption capability of the operating system of the electronic device such as the mobile phone 100 can ensure the security of the payment management application management payment process.

[0058] It can be understood that in some other embodiments, Figure 1 The mobile phone 100 in the scenario shown can also be other electronic devices that can install payment applications, including but not limited to mobile phones, smart screens, desktop computers, tablet computers, laptop computers, wearable devices, head-mounted displays, mobile email devices, portable game consoles, portable music players, reader devices, personal digital assistants, virtual reality or augmented reality devices, electronic devices such as televisions embedded or coupled with one or more processors, etc. without limitation.

[0059] As an example, the following takes the application of the electronic payment method of the present application to the mobile phone 100 as an example to introduce the specific process of implementing the scheme of the present application.

[0060] As described above, the distributed operating system carried by the mobile phone 100 can be, for example, the HarmonyOS described above. In order to facilitate understanding, the following first takes the HarmonyOS as an example to describe the distributed operating system and how to manage the payment application based on the HarmonyOS.

[0061] Figure 2 An exemplary system architecture block diagram of the HarmonyOS 200 is shown.

[0062] As Figure 2As shown, HarmonyOS 200 employs a layered architecture as an example. The layered architecture divides HarmonyOS 200 into several layers, each of which has a clear role and division of labor. Layers communicate with each other through software interfaces. In some embodiments, HarmonyOS 200 is divided into four layers, from top to bottom, an application layer 210, an application framework layer 220, a system service layer 230, and a kernel layer 240. In other embodiments, HarmonyOS 200 can also be divided into other number of hierarchical structures, which are not limited here.

[0063] The application layer 210 can include a series of applications (Application, APP), such as system applications 211, extension applications 212 (or third-party applications), etc. In some embodiments of the present application, the extension applications 212 include, but are not limited to, the above-mentioned Alipay TM 101, WeChat TM 102, UnionPay Cloud Flash Payment TM 103, bank client 104, etc. payment applications, and payment management applications 105, etc., which are not limited here.

[0064] The application framework layer 220 provides Java / C / C++ / JS, etc. multi-language framework for the application layer 210, including User Interface (UI) framework 221, user program framework 222 and capability framework 223, as well as multi-language framework application programming interface (API) and framework API of multiple programming languages. Among them, the application framework layer 220 includes some pre-defined functions. Among them, the UI framework 221 includes window manager, content provider, view system, phone manager, resource manager, notification manager, etc., which are not described here. The user program framework 222 and the capability framework 223 are multi-language frameworks provided by the application framework layer for application programs, including providing various types of characteristic capabilities required by application programs, such as payment capabilities provided for payment applications.

[0065] It can be understood that the application in HarmonyOS 200 is composed of one or more feature capabilities (Feature Ability, FA) or particle capabilities (Particle Ability, PA). Among them, the FA has a user interface (User Interface, UI), which provides the ability to interact with the user, also known as atomic capability or meta capability, for example, the payment capability module providing the payment capability interacting with the user described above; and the PA has no UI, which provides the capability of running tasks in the background and unified data access abstraction. The application developed based on the FA / PA can realize specific business functions, support cross-device scheduling and distribution, and provide consistent and efficient application experience for users. In some embodiments of the present application, the payment application on the mobile phone 100 is an application program developed based on the payment feature capability (i.e. the payment capability module described above, hereinafter referred to as payment FA).

[0066] The user can click the application icon of each application program in the desktop program of the mobile phone 100 to start the running of the application program. It can be understood that the application icon of each application program is provided by the application entrance module, and the application entrance module will be described in detail below, and will not be described here. In the embodiments of the present application, as shown in Figure 1 , the user can click the application icon of the payment management application 105 in the desktop application program of the mobile phone 100 to start the payment management application 105. When the user performs a payment operation through the payment management application 105, if the first order payment application set in the payment management application 105 is Alipay TM 101, the application entrance module of the payment management application 105 directly calls the payment FA of Alipay TM 101 to complete the payment, wherein the payment FA of Alipay TM 101 can independently run to provide the payment function of Alipay TM 101, and then deduct the corresponding amount from the user's Alipay account.

[0067] As an example, the main interface of the payment management application 105 can refer to the interface of the payment management platform 300 as shown in Figure 3A , for example, referring to operation ① as shown in Figure 3A , the user can click the payment code / sweep code payment button 301 to enter the interface as shown in Figure 3B , the user can click the payment code option 302 to present the payment code for payment, Figure 3B , the user can also click the sweep option 303 to open the code scanning window to scan the payment code for payment.

[0068] The system service layer 230 is the core of the HarmonyOS 200, and provides services for the application programs in the application layer 210 through the application framework layer 220. The system service layer 230 includes:

[0069] The system basic capability subsystem set 231: provides basic capabilities for the running, scheduling, migration, and the like of distributed applications on multiple devices, and is composed of a distributed software bus, a distributed data management, a distributed task scheduling, a ark multi-language runtime subsystem, a public basic library subsystem, a multi-mode input subsystem, a graphics subsystem, a security subsystem, an AI subsystem, and the like. The ark multi-language runtime subsystem provides a C / C++ / JS multi-language runtime and a basic system class library, and also provides a runtime for a Java program (i.e., an application program or a part developed using the Java language in the framework layer) that is statically compiled using the ark compiler.

[0070] The basic software service subsystem set 232: provides common and universal software services for the HarmonyOS 200, and is composed of an event notification subsystem, a phone subsystem, a multimedia subsystem, a DFX subsystem, an MSDP&DV subsystem, and the like.

[0071] The enhanced software service subsystem set 233: provides differentiated capability-enhanced software services for different devices for the HarmonyOS 200, and is composed of a smart screen exclusive business subsystem, a wearable exclusive business subsystem, an IoT exclusive business subsystem, and the like.

[0072] The hardware service subsystem set 234: provides hardware services for the distributed operating system, and is composed of a location service subsystem, a biometric identification subsystem, a wearable exclusive hardware service subsystem, an IoT exclusive hardware service subsystem, and the like.

[0073] According to the deployment environment of different device forms, the basic software service subsystem set, the enhanced software service subsystem set, and the hardware service subsystem set can be tailored at the subsystem granularity, and each subsystem can be tailored at the function granularity.

[0074] The kernel layer 240 is a layer between hardware and software. The kernel layer of the HarmonyOS 200 includes a kernel subsystem 241 and a driver subsystem 242.

[0075] Among them, the kernel subsystem 241 is interposed between HarmonyOS 200 can adopt a multi-kernel design, so the kernel subsystem 241 supports selecting a suitable OS kernel for different resource-constrained devices. The kernel abstraction layer (KAL) on the kernel subsystem 241 provides basic kernel capabilities to the upper layer by shielding the multi-kernel differences, including process / thread management, memory management, file system, network management, and peripheral management, etc.

[0076] The driver subsystem 242 is the driver framework (HDF) of HarmonyOS 200, and is also the basis for opening the hardware ecosystem of the distributed system, providing unified peripheral access capabilities and driver development and management framework. The kernel layer 240 at least includes display drivers, camera drivers, audio drivers, and sensor drivers.

[0077] It can be understood that the system architecture shown in the above Figure 2 does not constitute a limitation on the system architecture of HarmonyOS 200. In some other embodiments, HarmonyOS 200 can have more or fewer system architecture structures than the structure shown in the above Figure 2 , or can have other forms of system architecture, which are not limited herein.

[0078] It can be understood that the application publishing form on HarmonyOS 200 is APP Pack (Application Package, APP for short), that is, the HarmonyOS APP described above. In order to facilitate understanding, Figure 4 a composition diagram of a HarmonyOS APP is shown.

[0079] As Figure 4 shown, a HarmonyOS APP is composed of one or more HAP (HarmonyOS Ability Package) packages and a pack.info file describing the APP Pack attributes. Among them, HAP is a deployment package of meta-ability (Ability), and the HarmonyOS application code is developed around the Ability component, which is composed of one or more Abilities. Abilities are divided into two types: FA and PA. As described above, FA / PA is the basic component unit of the application, which can implement specific business functions, and will not be described here.

[0080] It can be understood that a HAP is a module package composed of codes, resources, third-party libraries and an application manifest file, including two types of Entry and Feature, wherein the Entry is an entry module of an application, an APP can only have one Entry module, the Entry module can be installed independently, and a desktop application icon is provided for a user to click to start the corresponding application program, for example, the above-mentioned Alipay TM 101 has a unique Entry module, and the payment management application 105 also has a unique Entry module; the Feature is a dynamic feature module of an application, and an APP can contain one or more Feature modules. As shown in Figure 4 The Entry.hap can include the above-mentioned Ability component, database (libs), resource file (resources) and configuration file (config.json) describing resolution, security parameter and the like.

[0081] It can be understood that the application name, function option and interface display of the payment management application 105 are not limited to the above-mentioned Figure 3A The payment management platform 300, and in other embodiments, the payment management application 105 can be presented in other application names, and the function modules of the payment management application 105 can also be displayed in other forms of interfaces, which are not limited herein.

[0082] For ease of description, the following will take the payment management application 105 as Figure 3A The payment management platform 300 as shown in the above-mentioned

[0083] It can be understood that the above-mentioned Alipay TM 101, WeChat TM 102, and cloud flash payment TM 103 and the bank client 104 and the like form a payment system with the payment management platform 300 provided by the present application in the HarmonyOS 200, as an example, Figure 5 An architecture schematic diagram of a payment management system is shown.

[0084] As shown in Figure 5 The payment system includes Alipay TM 101, WeChat TM 102, cloud flash payment TM 103 and the payment management platform 300. Among them, Alipay TM 101 has an application entry module 311, a payment class FA 312, WeChat TM 102 has an application entry module 321, a payment class FA 322, cloud flash paymentTM 103 has application entry module 331, payment class FA 332. Among them, the payment class FA 332 of Alipay TM 101, WeChat TM 102, Yunshenfu TM 103, when installed on the mobile phone 100 equipped with HarmonyOS 200, complete the registration and authorization of the payment class FA 332 of Alipay TM 101, the payment class FA 312 of WeChat TM 102, the payment class FA 322 of Yunshenfu TM 103, the payment class FA 332 can be understood as the registration and authorization on the FA management module 201 in HarmonyOS 200. It can be understood that the FA management module 201 is used to manage various FAs possessed by any application installed on HarmonyOS 200, which is not limited here.

[0085] It can be understood that the payment application installed on the mobile phone 100 equipped with HarmonyOS 200 not only includes the application entry module, but also includes the payment class FA. As described above, each payment application completes the registration and authorization of the corresponding payment class FA on the FA management module 201 in HarmonyOS 200. The payment management platform 300 obtains the management permission of the payment class FA of each payment application based on the authorization behavior of the user, that is, it obtains the management permission of the payment function of each payment application. The payment management platform 300 can further directly call the payment class FA of each payment application for payment operation through the unified application entry module. The payment management platform 300 can also obtain all the payment data on the corresponding payment application based on each payment class FA, including historical payment data, and perform summary management. For example, after HarmonyOS 200 scans the payment class FA 322 of WeChat TM 102, and the payment class FA 332 of Yunshenfu TM 103, it requests the user to authorize the management of the above-mentioned payment class FAs 322 and 332. After the user authorizes, HarmonyOS 200 can suggest the user to authorize the above-mentioned payment class FAs 322 and 332 to the payment management platform 300 for management. After the user agrees to authorize, the payment management platform 300 can directly call the above-mentioned payment class FAs 322 or 332 through the unified Entry.hap when performing payment operation, or can obtain the payment data on WeChat TM 102 based on the above-mentioned payment class FA 322, and the payment data on Yunshenfu TM 103 based on the payment class FA 332.

[0086] Specifically, the payment management platform 300 provides a unified application entry module (i.e. Entry.hap) that can call the payment class FA of the payment application added to the payment management platform 300 for unified management to provide a unified payment entry or payment channel to complete the payment operation, including generating a unified payment code and providing a unified code scanning entry, etc., when performing the payment operation, for example Figure 5 The payment management platform 300 shown in the figure generates a payment code through the Entry.hap of the platform to complete the payment operation. TM 101, the payment management platform 300 directly calls the payment class FA 312 of the Alipay TM 101 to generate a payment code for payment.

[0087] It can be understood that if there are many payment applications added to the payment management platform 300 for payment management, the user can set the payment order of each payment application, and the payment channel such as bank card and credit card managed by each payment application can still be set with a payment order, and when the payment management platform 300 calls the payment class FA of the payment application to perform the payment operation, it will be paid by default through the first-order payment channel set in the payment application. For example, in the above example, when the payment management platform 300 calls the payment class FA 312 of the Alipay TM 101 to perform the payment operation, if the first-order payment channel set in the Alipay TM 101 is a credit card of a certain bank, the payment process of the payment management platform 300 will be to deduct the payment from the credit card of the bank bound on the Alipay TM 101 to complete the payment. In addition, it can be understood that even if the payment management platform 300 can call each payment class FA to perform the payment operation after being authorized by the user, if the user still opens the payment application, such as the Alipay TM 101, to perform the payment operation, at this time the entry module 311 of the Alipay TM 101 calls the payment class FA 312 of the Alipay TM 101 to perform the payment operation, and the payment management platform 300 can obtain the payment data related to the payment operation based on the management permission of the payment class FA 312.

[0088] It can be understood that if the FA management module 201 of the HarmonyOS 200 scans the payment type FA and notifies the user to authorize the addition to the unified management of the payment management platform 300, the payment management platform 300 cannot perform unified payment management on the payment application corresponding to the payment type FA, and cannot obtain the payment and receipt data on the payment application. At this time, if the user operates the mobile phone 100 to run the payment application for payment operation, the application entry module of the payment application will call the payment type FA of the payment application to complete the payment operation. For example, if the user operates the mobile phone 100 to run the Alipay TM 101 to perform payment operation, the application entry module 311 of the Alipay TM 101 calls the payment type FA 312 to complete the payment operation.

[0089] It can be understood that the payment management platform 300 based on Entry.hap provides a unified payment channel to collect payment and receipt data when performing payment operation, and the payment and receipt data obtained by the payment management platform 300 through the payment type FA of each payment application are summarized and counted, so that the consumption information statistics can be completed, and then the classified accounting function and consumption financial advice can be provided to the user based on the statistical payment and receipt data.

[0090] It can be understood that the payment management platform 300 provided by the present application can also have the function of managing savings cards, credit cards and other fund accounts as most of the current payment applications, which will not be repeated here.

[0091] It can be understood that the above-mentioned payment management platform 300 can be a HarmonyOS APP, or a payment application on HarmonyOS 200, such as the wallet application of Huawei TM . In other embodiments, the above-mentioned payment management platform 300 can also be other services or applications with payment and / or payment management functions, which are not limited here. It can be understood that the payment management platform 300 installed on the mobile phone 100 can also authorize other electronic devices connected with the mobile phone 100 to provide payment codes for payment operation, that is, the payment management platform 300 can support multiple devices to cooperate for payment. The function of the payment management platform 300 supporting multiple devices to cooperate will be described in detail below, which will not be repeated here.

[0092] As an example, Figure 6A a structure schematic block diagram of a payment management platform 300 is shown.

[0093] As Figure 6A shown, the payment management platform 300 includes a payment type FA management module 310, an accounting classification module 320, a multi-device cooperative communication module 330, and a financial advice big data module 340. The functions of each module include but are not limited to the following description:

[0094] The payment FA management module 310 can manage the payment FAs added to the payment management platform 300 by user authorization, including managing the authorized addition, canceling authorization, and the like of the payment FAs, and can also call the payment FAs managed by the payment FA management module 310 by the unified application portal of the payment management platform 300 to complete payment operations through corresponding payment applications, for example, calling the payment FAs of the payment applications added to the unified management of the payment management platform 300 by the unified Entry.hap to generate a payment code for payment. This function can be referred to the description of the above-mentioned Figure 5 application portal. It can be understood that the payment FA management module 310 can manage the payment order of each payment application before calling the payment FAs of each payment application to perform payment operations through the unified Entry.hap, for example, the payment FA management module 310 can adjust the payment order of each payment application in response to the user's setting operation, and call the payment FAs of each payment application to perform payment operations according to the payment order. In some embodiments, the payment FA management module 310 can also set a default payment order for each payment application added to the payment management platform 300 for payment, which is not limited here.

[0095] It can be understood that the payment FA management module 310 can send the payment and receipt data on each payment application obtained through the payment FAs to the accounting classification module 320, the financial advice big data module 340, and the basic function library 350.

[0096] The accounting classification module 320 can classify and count the payment and receipt data generated when performing payment operations through the payment management platform 300 and the payment and receipt data on each payment application obtained from each payment FA by the payment FA management module 310 to obtain accounting classification data, for example, classifying the above-mentioned payment and receipt data according to the payment and receipt types, which can include consumption types such as food, clothing, and daily necessities, and can also include money flow types such as transfer, red envelope, and income, which are not limited here. In some embodiments, the accounting classification module 320 can add and subtract the payment and receipt data within a certain time period to calculate the total expenditure and total income, for example, to calculate the monthly total expenditure and monthly total income, and the like. The accounting classification module 320 can also calculate the proportion of each type of expenditure according to the above-mentioned classified types within a certain time period, for example, to calculate the proportion of monthly daily necessities consumption expenditure in the total monthly expenditure, and the like. It can be understood that the classification and counting results of the accounting classification module 320 on the payment and receipt data can be provided to the financial advice big data module 340 to determine the financial advice suitable for the user's income and expenditure.

[0097] It can be understood that the payment management platform 300 can obtain the management right of the payment function of one or more payment applications, for example, obtain the payment function management right of the payment applications such as Alipay TM , WeChat TM , and Cloud Flash TM , and the accounts logged in on each payment application can be the same user's account or different user's accounts; in another embodiment, the payment management platform 300 or the same payment application can also log in two or more user accounts in different periods, and the accounting classification module 320 of the payment management platform 300 can perform account statistics on the historical payment and receipt data of different users after summarizing the above two types of historical payment and receipt data, to generate accounting classification data corresponding to each user.

[0098] The multi-device cooperative communication module 330 is configured to manage the communication interconnection between other electronic devices and the mobile phone 100, to authorize other electronic devices to provide the payment and receipt function and the accounting function of the payment management platform 300, for example, the smart watch or smart bracelet worn by the user can be interconnected with the mobile phone 100 through the multi-device cooperative communication module 330 and obtain the user authorization, and the user can display the payment code through the smart watch or smart bracelet to perform the payment operation, and in some other embodiments, the user can also view the payment and receipt bill or financial advice through the smart watch or smart bracelet, which is not limited herein. In some embodiments, the function of the multi-device cooperative communication module 330 can be realized by the distributed software bus in the HarmonyOS 200, which is not limited herein.

[0099] The financial advice big data module 340 is configured to perform big data analysis on the payment and receipt data generated when performing the payment operation through the payment management platform 300 and the payment and receipt data on each payment application obtained by the payment type FA management module 310 from each payment type FA, and generate the financial advice based on the preset financial algorithm and provide the financial advice for the user's reference. In some other embodiments, the financial advice big data module 340 can also perform financial analysis based on the classification and statistical results obtained by the accounting classification module 320 processing the above payment and receipt data, and generate the financial advice for the user's reference, which is not limited herein.

[0100] The basic function library 350 is configured to provide the application program interface (API) for the interaction between the payment management platform 300 and the HarmonyOS 200, to support the calling of the system function by each function module of the payment management platform 300 to complete the interaction with the user. For example, the function button provided by the payment management platform 300 based on each function module for the user needs to call the image drawing function on the system to display the chart of the function button.

[0101] It can be understood that the application installed in HarmonyOS 200 will be uniformly scanned by the system, and if it is a payment application with a payment FA, the system can remind the user to add the payment application to the payment management platform 300 for unified management.

[0102] Based on Figure 6A the structure of the payment management platform 300 shown in the figure, Figure 6B a functional interface schematic diagram of a payment management platform 300 is shown.

[0103] As Figure 6B shown, the functional interface of the payment management platform 300 includes a payment code / scanning payment button 601 (i.e. the payment code / scanning payment button 301 described above Figure 3A shown), an accounting editing button 602, a financial management button 603, an application setting button 604, and a device management button 605.

[0104] Based on the functional support provided by each functional module shown above Figure 6A , the user can trigger the input event of the corresponding function by clicking each functional button shown above Figure 6B .

[0105] The user can present a payment code or open a scanning window to scan a payment code to perform a payment operation by clicking the payment code / scanning payment button 601.

[0106] The user can view the details of the collection and payment by clicking the accounting editing button 602. The interface displaying the details of the collection and payment can be displayed in order of the collection and payment time, or can be displayed according to the type of the collection and payment corresponding to the collection and payment. The user can also set the display form on the interface displaying the details of the collection and payment, which is not limited here.

[0107] The user can view the financial analysis report and financial advice by clicking the financial management button 603, for example, the interface opened by the financial management button 603 can display a financial analysis report, and the financial advice summary is displayed below the report, which is not limited here.

[0108] The user can manage the payment application added to the platform 300 for unified management by clicking the application setting button 604. The user can set the payment order of the payment application managed by the platform 300 on the interface opened by the application setting button 604, or can select to add a payment application to trigger the acquisition of a payment FA that has not been added to the platform 300 for unified management, and authorize the addition.

[0109] The user can click the device management button 605 to manage other electronic devices, such as smart watches or smart bands, that have obtained the unified application entry calling permission for unified payment management on the payment management platform 300. The user can add device authorization, or cancel authorization for an added device, delete the device, and the like on the interface opened by clicking the device management button 605.

[0110] In some embodiments, the payment management platform 300 can be configured to Figure 6B The function interface of the platform 300 shown in the figure can also display the consumption data of the user through a statistical chart, for example Figure 6B The function interface of the platform 300 can also display financial advice based on the analysis of the payment and receipt data in the past month or half year for the user to refer, which is not limited herein.

[0111] Based on the above Figure 6A The structure of the payment management platform 300 shown in the figure and Figure 6B The interface of the payment management platform 300 shown in the figure, the specific implementation process of the electronic payment method through the payment management platform 300 of the present application will be described in detail below through specific embodiments.

[0112] Embodiment one

[0113] The present embodiment continues to take the mobile phone 100 configured with HarmonyOS 200 as an example, and based on the structure features of HarmonyOS 200 described above, the process of the mobile phone 100 managing payment applications through the payment management platform 300 is described in detail in combination with the flowchart. The present embodiment mainly introduces a method of adding payment applications to the payment management platform 300 for unified management.

[0114] Figure 7 An implementation flowchart of a method of identifying payment applications and adding them to the payment management platform 300 for unified management is shown. It can be understood that Figure 7 The execution subject of each step shown in the figure is the mobile phone 100.

[0115] As Figure 7 shown, the method comprises the following steps:

[0116] 701: Install an application program on the mobile phone 100.

[0117] Specifically, when using the mobile phone 100, the user can install some application programs according to his own use needs, for example, the user wants to install Alipay TM on the mobile phone 100, search for Alipay TM in the application store and click to install. After the installation program is run, the installation of Alipay TM is completed.

[0118] 702: The mobile phone 100 determines whether the installed application is a payment application. If yes, step 703 is performed, and if no, no processing is performed.

[0119] Specifically, the HarmonyOS 200 carried by the mobile phone 100 can identify whether there is a payment FA in the installed application, for example, by scanning the FA characteristic parameters of the installed application, to identify whether there is a payment FA in the application. That is, when the application is installed, the operating system of the mobile phone 100 can trigger the acquisition of the FA possessed by the application, and identify whether there is a payment FA. If the installed application has a payment FA, the application is a payment application; if the installed application does not have a payment FA, the application is other application, which is not a payment application.

[0120] 703: The mobile phone 100 adds the installed application to the list of payment applications to be managed.

[0121] Specifically, as described above Figure 2 As shown in the figure, the HarmonyOS 200 carried by the mobile phone 100 can manage and call various FAs in various applications, and add the identifiable payment FAs to the payment application list in the system. It can be understood that the list records the payment FAs of various payment applications installed on the mobile phone 100.

[0122] 704: When the mobile phone 100 runs the payment application, the user is prompted whether to add the application to the payment management platform 300 for management.

[0123] Specifically, when the mobile phone 100 runs the installed payment application, the user can be notified on the interface of the application whether to add the application to the payment management platform 300 for management. It can be understood that in order not to disturb the user too much, the mobile phone 100 usually sends a confirmation notification to the user when the payment application is run for the first time, and the notification can include a check box, and the user can select the check box to not pop up the confirmation notification next time the payment application is run.

[0124] As an example, the interface shown in the figure can be referred to Figure 8 The Alipay TM installed on the mobile phone 100 TM When the user completes the initial application setting and enters the Alipay Figure 8The system detects that the application can be added to the payment management platform for unified management. Please confirm whether to add it. The user can click the add button 802 to confirm the addition of the payment application to the payment management platform 300 for management. The user can also click the cancel button 803 to refuse to add the payment application to the payment management platform 300 for management. It can be understood that in Figure 8 In the confirmation notification 801, a check box 804 can also be displayed below the add button 802 and the cancel button 803. After the user checks the check box 804 and closes the confirmation notification 801, the confirmation notification will not pop up when the mobile phone 100 runs the payment application next time. In other embodiments, the content and display form of the above-mentioned confirmation notification can also be other, which is not limited here.

[0125] 705: The mobile phone 100 uses the application portal of the platform to call the payment class FA corresponding to each payment application for payment operation.

[0126] Specifically, after the payment application is added to the payment management platform 300, the user can use the payment management platform 300 to display the payment code for payment by the application when making payment. As an example, refer to Figure 6B As shown, the user can click the payment code / code scanning payment button 601 on the payment management platform 300 to display the payment code. It can be understood that when the user clicks the button 601, the "payment code" tab card and the "code scanning" tab card can pop up on the interface of the payment management platform 300. Refer to Figure 9 As shown, the user can click the "payment code" tab card 901 to display the payment code, and click the "code scanning" tab card 902 to open the code scanning portal to display the code scanning interface. In other embodiments, a quick code scanning button 606 can be added to the search box on the interface to facilitate the user to perform quick operation to open the code scanning portal. Figure 6B

[0127] It can be understood that the method of adding a payment application to the payment management platform 300 for unified management is not limited to the method described in steps 701 to 705. Another method of adding a payment application to the payment management platform 300 for unified management is described below through another embodiment.

[0128] Embodiment Two

[0129] Based on the structure and characteristics of the HarmonyOS 200 described above, the process of managing payment applications by the mobile phone 100 through the payment management platform 300 is described in detail from another angle below. The present application mainly introduces another method of adding a payment application to the payment management platform 300 for unified management. ​

[0130] Figure 10 This diagram illustrates the implementation process of a method for identifying payment applications and adding them to a unified payment management platform 300. It can be understood that... Figure 10 The execution entity for each step shown is mobile phone 100.

[0131] like Figure 10 As shown, the method includes the following steps:

[0132] 1001: Running the payment management platform 300.

[0133] Specifically, the user clicks on the payment management platform 300 installed on mobile phone 100, and mobile phone 100 runs the payment management platform 300. Upon first launch of the payment management platform 300, mobile phone 100 can display a pop-up window on its main interface showing a list of payment applications already entered into the system, allowing the user to select and add them to the payment management platform. (See reference...) Figure 11A As shown in pop-up window 1101, the user can select or uncheck the checkboxes 1102 next to each payment application displayed in this pop-up window 1101, and then click the confirmation button 1103 to complete the addition. After the addition is completed, the mobile phone 100 can display a prompt message indicating successful authorization, which will not be described in detail here.

[0134] In another embodiment, the user can also click the application settings button 604 on the main function interface of the payment management platform 300 displayed on the mobile phone 100, refer to Figure 11B As shown in operation ②, phone 100 responds to the user's operation by opening the settings interface 1104. (See reference) Figure 11C As shown, users can click the "Add" button (1105) on this settings interface to open the list of payment applications already entered into the system and select the application to add, as described above. Figure 11A On the screen shown, click the "Confirm" button (1103) to complete the addition. After completion, the phone (100) will display a message indicating successful authorization; further details will not be provided here.

[0135] It's understandable that the payment applications already on the system's list are those whose payment features are identified by the HarmonyOS 200 scanning feature list on the phone and added to the system's list of payment features. The corresponding payment applications for those payment features are the ones already on the system's list. Users can... Figure 11C As shown in the interface, clicking the order setting button 1106 for each payment application allows you to adjust the setting order. It can be understood that the order setting button 1106 for the first-priority payment application can display a word such as "Default," while the order setting buttons 1106 for non-first-priority payment applications can display an icon containing an upward arrow; there are no restrictions here. Accordingly, refer to... Figure 11CThe user can also click the delete button 1107 corresponding to each payment application under the delete application option on the interface shown in Figure 11C The corresponding payment application is deleted from the payment management platform 300, i.e., it is no longer uniformly managed for payment operation.

[0136] In some other embodiments, the payment management platform 300 can also be a wallet application or other payment application installed on the mobile phone 100 and having the payment management capability described in the embodiments of the present application, which is not limited herein.

[0137] 1002: Display the payment application list that has been entered for the user to select and add to the payment management platform 300.

[0138] Specifically, reference can be made to Figure 11A On the interface shown in the pop-up window 1101, the list of payment applications installed on the mobile phone 100 is displayed. It can be understood that the system of the mobile phone 100 enters each payment application by identifying the payment class FA on each payment application. The user's selection of adding to the payment management platform 300 on the pop-up window 1101 has been described in step 1001 above, which will not be repeated here.

[0139] 1003: Set the payment order in response to the user's operation.

[0140] Specifically, the payment management platform 300 of the mobile phone 100 can preset rules to determine the default payment order by itself, for example, the payment order is set by default according to the time of adding each payment application. It can be understood that after the payment application is added to the payment management platform 300, the user can set the payment order under the set payment order option on the interface shown in Figure 11C Figure 11C The specific operation is described in the related description of step 1101 above, which will not be repeated here.

[0141] It can be understood that each payment application added to the payment management platform 300 for unified management can perform payment operation on the payment class FA corresponding to each payment application through the unified Entry.hap call provided by the payment management platform 300, for example, by clicking the payment code / sweep code payment button 601 on the interface of the payment management platform 300. As described above, the payment application that is not added to the payment management platform 300 for unified management can be authorized by the user to enable the payment management platform 300 to obtain the payment data generated by the independent payment operation on each payment application and the income data.

[0142] The execution process of the unified payment operation through the payment management platform 300 is described in detail in another embodiment below.

[0143] Embodiment Three ​

[0144] After the payment management platform 300 completes the payment application related settings based on the method introduced in the above embodiment one or embodiment two, the present application will introduce the specific operation process of the payment management platform 300 provided by the present application when performing payment in combination with a specific flowchart.

[0145] Figure 12 An operation process schematic diagram of payment through the payment management platform 300 is shown. It can be understood that, Figure 12 The execution subject of each step shown is the mobile phone 100.

[0146] As Figure 12 shown, the process includes the following steps:

[0147] 1201: In response to a user operation, open the interface of the payment management platform 300.

[0148] Specifically, the user can find the application icon of the payment management platform 300 in the desktop application program of the mobile phone 100, click the icon, and the mobile phone 100 runs the payment management platform 300, which will not be repeated here. Among them, the interface of the opened payment management platform 300 can refer to Figure 6B shown, which will not be repeated here.

[0149] 1202: In response to the payment method selected by the user according to the payment scenario, determine whether to display the payment code. If yes, execute step 1203; if no, execute step 1204.

[0150] Specifically, referring to various payment scenarios shown in the above Figure 2 shown, for example, the user is in the scenario of purchasing goods or services offline Figure 2 shown, the user can select the payment method according to whether the payment method supported by the merchant is to be scanned by the merchant himself. If yes, the user needs to present the payment code, that is, execute step 1203; if no, the user needs to scan the payment code of the merchant using the mobile phone 100, that is, needs to execute step 1204.

[0151] 1203: In response to a user operation, display the payment code.

[0152] Specifically, the user operates the mobile phone 100, and the operation of opening the payment code on the main function interface of the payment management platform 300 can refer to the related description of step 705 in the above embodiment one, that is, click the payment code / code scanning payment button 601 shown in Figure 6B shown, click the "payment code" tab 901 on the opened Figure 9 shown interface to display the payment code, which will not be repeated here.

[0153] 1204: In response to a user operation, open the code scanning function.

[0154] Specifically, the user operates the mobile phone 100, and the operation of opening the code scanning function on the main function interface of the payment management platform 300 can refer to the related description of step 705 in Embodiment I above, that is, clicking Figure 6B the payment code / scanning code payment button 601 shown in the figure, and then opening the Figure 9 interface shown in the figure, and clicking the “scan” tab 902 to open the scanning code interface. Details are not repeated here.

[0155] 1205: Complete payment based on the payment order set on the payment management platform 300, and record the consumption amount, type, and other information.

[0156] Specifically, the payment management platform 300 completes payment based on the set payment order, for example, referring to the interface shown above Figure 11C , the Alipay TM application is the default payment method, so after the above step 1203 shows the payment code or the above step 1204 scans the merchant payment code, the user can input the set payment password or fingerprint authentication payment to complete the payment verification, and the payment management platform 300 pays the corresponding amount through the default Alipay TM application. The payment management platform 300 records the data related to the payment order generated during the payment process, such as consumption amount, consumption type, consumption time, consumption location, payment serial number, etc., without limitation.

[0157] It can be understood that the Alipay TM application can complete the deduction based on the deduction order set in the application, without limitation.

[0158] As an example, Figure 13 a structural schematic diagram of a mobile phone 100 is shown.

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

[0160] The processor 110 can include one or more processing units, for example: the processor 110 can include an application processor (AP), a modem processor, a graphics processing unit (GPU), an image signal processor (ISP), a controller, a video codec, a digital signal processor (DSP), a baseband processor, and / or a neural-network processing unit (NPU), etc. Different processing units can be independent devices, or can be integrated in one or more processors.

[0161] The controller can generate operation control signals according to instruction operation codes and timing signals, and complete the control of fetching and executing instructions. In the embodiments of the present application, the processor 110 can execute the electronic payment method provided in the present application through the controller.

[0162] The memory in the processor 110 can also be provided for storing instructions and data. In some embodiments, the memory in the processor 110 is a cache memory. The memory can save instructions or data that have just been used or are repeatedly used by the processor 110. If the processor 110 needs to use the instructions or data again, it can directly call from the memory. This avoids repeated access and reduces the waiting time of the processor 110, thus improving the efficiency of the system.

[0163] In some embodiments, the processor 110 can include one or more interfaces. The interfaces can 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.

[0164] The USB interface 130 is an interface conforming to the USB standard specification, and can be a Mini USB interface, a Micro USB interface, a USB Type C interface, etc. The USB interface 130 can be used to connect a charger to charge the mobile phone 100, and can also be used to transmit data between the mobile phone 100 and peripheral devices. It can also be used to connect earphones to play audio through the earphones. The interface can also be used to connect other electronic devices, such as AR devices, etc.

[0165] It can be understood that the interface connection relationship between the modules shown in the embodiments of the present application is only illustrative and does not constitute a structural limitation of the mobile phone 100. In some other embodiments of the present application, the mobile phone 100 can also use different interface connection methods or combinations of multiple interface connection methods in the above embodiments.

[0166] The charging management module 140 is configured to receive charging input from a charger. The charger can be a wireless charger or a wired charger. In some wired charging embodiments, the charging management module 140 can receive charging input from a wired charger through the USB interface 130. In some wireless charging embodiments, the charging management module 140 can receive wireless charging input through the wireless charging coil of the mobile phone 100. The charging management module 140 can charge the battery 142 while also supplying power to electronic devices through the power management module 141.

[0167] The wireless communication function of the mobile phone 100 can be implemented by the antenna 1, the antenna 2, the mobile communication module 150, the wireless communication module 160, the modem processor, the baseband processor, and the like.

[0168] The antenna 1 and the antenna 2 are used for transmitting and receiving electromagnetic wave signals. Each antenna in the mobile phone 100 can be used to cover a single or multiple communication frequency bands. Different antennas can also be multiplexed to improve the utilization of the antennas. For example, the antenna 1 can be multiplexed as a diversity antenna of a wireless local area network. In some other embodiments, the antennas can be used in combination with a tuning switch.

[0169] The mobile communication module 150 can provide a solution for wireless communication including 2G / 3G / 4G / 5G and the like applied to the mobile phone 100. The mobile communication module 150 can include at least one filter, a switch, a power amplifier, a low noise amplifier (LNA), and the like. The mobile communication module 150 can receive electromagnetic waves from the antenna 1, and perform filtering, amplification, and the like on the received electromagnetic waves, and transmit the processed signals to the modem processor for demodulation. The mobile communication module 150 can also amplify signals modulated by the modem processor, and convert the signals into electromagnetic waves radiated through the antenna 1. In some embodiments, at least part of the functional modules of the mobile communication module 150 can be arranged in the processor 110. In some embodiments, at least part of the functional modules of the mobile communication module 150 and at least part of the modules of the processor 110 can be arranged in the same device.

[0170] The wireless communication module 160 can provide a solution for wireless communication including wireless local area networks (WLAN) (such as wireless fidelity (Wi-Fi) network), Bluetooth (BT), global navigation satellite system (GNSS), frequency modulation (FM), near field communication (NFC), infrared technology (IR), and the like applied to the mobile phone 100. The wireless communication module 160 can be one or more devices integrated with at least one communication processing module. The wireless communication module 160 receives electromagnetic waves via the antenna 2, performs frequency modulation and filtering processing on the electromagnetic wave signals, and transmits the processed signals to the processor 110. The wireless communication module 160 can also receive signals to be transmitted from the processor 110, perform frequency modulation and amplification on the signals, and convert the signals into electromagnetic waves radiated through the antenna 2.

[0171] In some embodiments, the antennas 1 and the mobile communication module 150 are coupled, and the antennas 2 and the wireless communication module 160 are coupled, so that the mobile phone 100 can communicate with a network and other devices through wireless communication technologies. The wireless communication technologies can include global system for mobile communications (GSM), general packet radio service (GPRS), code division multiple access (CDMA), wideband code division multiple access (WCDMA), time-division code division multiple access (TD-SCDMA), long term evolution (LTE), BT, GNSS, WLAN, NFC, FM, and / or IR technologies, etc. The GNSS can include global positioning system (GPS), global navigation satellite system (GLONASS), beidou navigation satellite system (BDS), quasi-zenith satellite system (QZSS), and / or satellite based augmentation systems (SBAS).

[0172] The mobile phone 100 implements a display function through a GPU, a display screen 194, and an application processor, etc. The GPU is a microprocessor for image processing, connected to the display screen 194 and the application processor. The GPU is used to perform mathematical and geometric calculations for graphics rendering. The processor 110 can include one or more GPUs that execute program instructions to generate or change display information. In the embodiments of the present application, the operation interface of the payment management platform 300 and the two-dimensional code displayed when the user makes a payment are all displayed by the display screen 194 of the mobile phone 100 after the GPU processes and renders the corresponding graphics data.

[0173] The display screen 194 is configured to display images, videos, and the like. The display screen 194 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 flex light-emitting diode (FLED), a Mini-LED, a Micro-LED, a Micro-OLED, a quantum dot light emitting diode (QLED), or the like. In some embodiments, the mobile phone 100 can include one or N display screens 194, where N is a positive integer greater than 1.

[0174] The mobile phone 100 can implement the photographing function through the ISP, the camera 193, the video codec, the GPU, the display screen 194, and the application processor.

[0175] The ISP is configured to process the data fed back by the camera 193. For example, when taking a photo, the shutter is opened, the light is transmitted to the camera photosensitive element through the lens, the light signal is converted into an electrical signal, and the camera photosensitive element transmits the electrical signal to the ISP for processing to convert it into an image visible to the naked eye. The ISP can also optimize the noise, brightness, and skin color of the image. The ISP can also optimize the exposure, color temperature, and other parameters of the shooting scene. In some embodiments, the ISP can be disposed in the camera 193.

[0176] The camera 193 is configured to capture still images or videos. An object generates an optical image through a lens and projects it onto a photosensitive element. The photosensitive element can be a charge coupled device (CCD) or a complementary metal-oxide-semiconductor (CMOS) phototransistor. The photosensitive element converts the light signal into an electrical signal, which is then transmitted to the ISP to convert it into a digital image signal. The ISP outputs the digital image signal to the DSP for processing. The DSP converts the digital image signal into an image signal in a standard RGB, YUV, or the like format. In some embodiments, the mobile phone 100 can include one or N cameras 193, where N is a positive integer greater than 1.

[0177] The digital signal processor is used to process digital signals, in addition to being able to process digital image signals, it can also process other digital signals. For example, when the mobile phone 100 is in frequency point selection, the digital signal processor is used to perform Fourier transform on the frequency point energy, etc.

[0178] The video codec is used to compress or decompress digital video. The mobile phone 100 can support one or more video codecs. In this way, the mobile phone 100 can play or record videos in multiple encoding formats, such as: moving picture experts group (MPEG) 1, MPEG 2, MPEG 3, MPEG 4, etc.

[0179] The NPU is a neural-network (NN) calculation processor, which can quickly process input information by drawing on the structure of biological neural networks, such as drawing on the transmission mode between human brain neurons, and can also continuously self-learn. Through the NPU, the mobile phone 100 can realize intelligent cognition applications such as image recognition, face recognition, voice recognition, text understanding, etc.

[0180] The external memory interface 120 can be used to connect an external memory card, such as a Micro SD card, to expand the storage capacity of the mobile phone 100. The external memory card communicates with the processor 110 through the external memory interface 120 to realize data storage functions. For example, music, video, etc. Files are saved in the external memory card.

[0181] The internal memory 121 can be used to store computer executable program codes, which include instructions. The internal memory 121 can include a program storage area and a data storage area. The program storage area can store an operating system, at least one application program required by a function (such as a sound playing function, an image playing function, etc.), etc. The data storage area can store data created during the use of the mobile phone 100 (such as audio data, a phonebook, etc.), etc. In addition, the internal memory 121 can include a high-speed random access memory, and can also include a non-volatile memory, such as at least one magnetic disk storage device, a flash memory device, a universal flash storage (UFS), etc. The processor 110 executes various function applications and data processing of the mobile phone 100 by running instructions stored in the internal memory 121 and / or instructions stored in the memory provided in the processor.

[0182] The mobile phone 100 can realize audio functions through the audio module 170, the speaker 170A, the receiver 170B, the microphone 170C, the earphone interface 170D, and the application processor, etc. For example, music playing, recording, etc.

[0183] The audio module 170 is configured to convert digital audio information into an analog audio signal output, and to convert an analog audio input into a digital audio signal. The audio module 170 can also be configured to encode and decode audio signals. In some embodiments, the audio module 170 can be disposed in the processor 110, or some functional modules of the audio module 170 can be disposed in the processor 110.

[0184] The speaker 170A, also referred to as a "loudspeaker", is configured to convert an audio electrical signal into a sound signal. The mobile phone 100 can listen to music or listen to a hands-free call through the speaker 170A.

[0185] The receiver 170B, also referred to as an "earpiece", is configured to convert an audio electrical signal into a sound signal. When the mobile phone 100 answers a call or a voice message, the receiver 170B can be held close to a human ear to listen to the voice.

[0186] The microphone 170C, also referred to as a "microphone", "sound collector", is configured to convert a sound signal into an electrical signal. When making a call or sending a voice message, a user can speak into the microphone 170C to input a sound signal into the microphone 170C. The mobile phone 100 can be provided with at least one microphone 170C. In other embodiments, the mobile phone 100 can be provided with two microphones 170C, which can be configured to not only collect sound signals, but also to achieve noise reduction. In other embodiments, the mobile phone 100 can be provided with three, four or more microphones 170C, which can be configured to not only collect sound signals and achieve noise reduction, but also to identify the source of the sound and achieve directional recording.

[0187] The earphone interface 170D is configured to connect a wired earphone. The earphone interface 170D can be a USB interface 130, or a 3.5mm open mobile terminal platform (OMTP) standard interface, or a cellular telecommunications industry association of the USA (CTIA) standard interface.

[0188] The pressure sensor 180A is used to sense a pressure signal and convert the pressure signal into an electrical signal. In some embodiments, the pressure sensor 180A can be disposed on the display 194. There are many types of pressure sensors 180A, such as a resistive pressure sensor, an inductive pressure sensor, a capacitive pressure sensor, etc. A capacitive pressure sensor can include at least two parallel plates with a conductive material. When a force is applied to the pressure sensor 180A, the capacitance between the electrodes changes. The phone 100 determines the intensity of the force based on the change in capacitance. When a touch operation is applied to the display 194, the phone 100 detects the intensity of the touch operation based on the pressure sensor 180A. The phone 100 can also calculate the location of the touch based on the detection signal of the pressure sensor 180A. In some embodiments, touch operations applied to the same touch location but with different touch operation intensities can correspond to different operation instructions. For example, when a touch operation with a touch operation intensity less than a first pressure threshold is applied to a short message application icon, an instruction to view a short message is executed. When a touch operation with a touch operation intensity greater than or equal to the first pressure threshold is applied to the short message application icon, an instruction to create a new short message is executed.

[0189] The gyroscope sensor 180B can be used to determine the motion attitude of the phone 100.

[0190] The barometric pressure sensor 180C is used to measure air pressure. In some embodiments, the phone 100 calculates altitude, assists in positioning and navigation based on the air pressure value measured by the barometric pressure sensor 180C.

[0191] The magnetic sensor 180D includes a Hall sensor. The phone 100 can use the magnetic sensor 180D to detect the opening and closing of a flip cover. In some embodiments, when the phone 100 is a flip phone, the phone 100 can detect the opening and closing of the flip cover based on the magnetic sensor 180D. Further, based on the detected opening and closing state of the cover or the opening and closing state of the flip cover, the phone 100 can set a feature such as automatic unlocking of the flip cover.

[0192] The acceleration sensor 180E can detect the magnitude of acceleration of the phone 100 in various directions (typically three axes). When the phone 100 is stationary, the acceleration sensor 180E can detect the magnitude and direction of gravity. The acceleration sensor 180E can also be used to identify the attitude of the electronic device and applied to applications such as landscape / portrait screen switching and pedometers.

[0193] The distance sensor 180F is used to measure distance. The phone 100 can measure distance using infrared or laser. In some embodiments, when a scene is photographed, the phone 100 can use the distance sensor 180F to measure distance to achieve fast focusing.

[0194] The proximity light sensor 180G can include, for example, a light emitting diode (LED) and a light detector, such as a photodiode. The mobile phone 100 can use the proximity light sensor 180G to detect that a user is holding the mobile phone 100 close to his ear for a phone call, so as to automatically turn off the screen to save power. The proximity light sensor 180G can also be used for automatic unlocking and locking in a holster mode or a pocket mode.

[0195] The ambient light sensor 180L is used to sense ambient light brightness. The mobile phone 100 can adaptively adjust the brightness of the display screen 194 according to the sensed ambient light brightness. The ambient light sensor 180L can also be used to automatically adjust the white balance when taking a photo. The ambient light sensor 180L can also work with the proximity light sensor 180G to detect whether the mobile phone 100 is in a pocket to prevent accidental touch.

[0196] The fingerprint sensor 180H is used to collect a fingerprint. The mobile phone 100 can use the collected fingerprint characteristics to implement fingerprint unlocking, access application lock, fingerprint photo, fingerprint call answering, and the like.

[0197] The temperature sensor 180J is used to detect temperature. In some embodiments, the mobile phone 100 uses the temperature detected by the temperature sensor 180J to implement a temperature handling strategy. For example, when the temperature reported by the temperature sensor 180J exceeds a threshold value, the mobile phone 100 implements a performance reduction of a processor located near the temperature sensor 180J, so as to reduce power consumption and implement thermal protection.

[0198] The touch sensor 180K, also referred to as a "touch device". The touch sensor 180K can be disposed on the display screen 194, and the touch sensor 180K and the display screen 194 form a touch screen, also referred to as a "touch screen". The touch sensor 180K is used to detect a touch operation acting on or near it. The touch sensor can transmit the detected touch operation to the application processor to determine the touch event type. Visual output related to the touch operation can be provided through the display screen 194. In other embodiments, the touch sensor 180K can also be disposed on the surface of the mobile phone 100, which is different from the position where the display screen 194 is located.

[0199] The bone conduction sensor 180M can obtain a vibration signal.

[0200] The keys 190 include a power-on key, a volume key, and the like. The keys 190 can be mechanical keys. They can also be touch keys. The mobile phone 100 can receive key inputs and generate key signal inputs related to user settings and function control of the mobile phone 100.

[0201] The motor 191 can generate a vibration prompt. The motor 191 can be used for incoming call vibration prompt, and can also be used for touch vibration feedback. For example, touch operations acting on different applications (such as taking pictures, playing audio, etc.) can correspond to different vibration feedback effects. Touch operations acting on different regions of the display screen 194 can also correspond to different vibration feedback effects of the motor 191. Different application scenarios (such as time reminders, received messages, alarms, games, etc.) can also correspond to different vibration feedback effects. The touch vibration feedback effect can also be customized.

[0202] The indicator 192 can be an indicator light, which can be used to indicate the charging state, the power change, and can also be used to indicate messages, missed calls, notifications, etc.

[0203] The SIM card interface 195 is used to connect the SIM card. The SIM card can be inserted into or pulled out of the SIM card interface 195 to realize contact and separation with the mobile phone 100.

[0204] It can be understood that the structure shown in the above Figure 13 does not constitute a specific limitation on the mobile phone 100. In other embodiments of the present application, the mobile phone 100 can include more or fewer components than those shown, or combine certain components, or split certain components, or different component arrangements. The components shown can be implemented in hardware, software, or a combination of software and hardware.

[0205] In other embodiments, the structure of the mobile phone 100 can also refer to the structure shown in Figure 14 .

[0206] As shown in Figure 14 , the mobile phone 100 includes a processor 1410, a communication module 1420, a memory 1430, a display device 1440, and an input device 1450. The operating system 1400 configured by the mobile phone 100 is installed with a plurality of application programs 1401. It can be understood that the plurality of application programs 1401 include a payment application and other applications without payment functions.

[0207] The processor 1410 can control the reception and manipulation of input and output data between the components of the computer system. In the embodiments of the present application, the processor 1410 can be used to calculate the fund flow data involved in the payment details.

[0208] The communication module 1420 is used to connect the terminal device to the Internet and enable data communication with the server deployed on the Internet. The data interaction between the application program and the server is through the communication module. In the embodiments of the present application, the communication module 1420 can be used to interact with the server, obtain the UTC time on the server, and transmit data such as consumption records.

[0209] The memory 1430, which can be connected to the processor 1410, is used to store the operating system, application program information, and the like for the terminal. The memory can include read-only memory (ROM), random access memory (RAM), and the like, and information can also reside on removable storage media and be loaded or installed on the computer system as needed, including SD memory cards. In the embodiments of the present application, the memory is used to store consumption information and the like.

[0210] The display device 1440, which can be connected to the processor 1410, is used to receive and display the processing results returned by the processor 1410. A graphical user interface (GUI) is usually configured thereon, which provides an easy-to-use user interface between the user of the computer system and the operating system or application running thereon. In the embodiments of the present application, the display device 1440 can be used to display payment codes, consumption records, and the like.

[0211] The input device 1450, which can be connected to the processor 1410, is used to receive the input operation of the user and can send the user input content to the server. The input device can be a touchpad or touch screen placed on or in front of the display device, which can be based on various sensing technologies, including but not limited to capacitive sensing, resistive sensing, surface acoustic wave sensing, pressure sensing, optical sensing, and the like. The touchpad or touch screen can be integrated with the display device or can be a separate component. The above input device 1450 can be a single-point or multi-point input device, which is not limited herein.

[0212] It can be understood that Figure 14 The functions of the structures involved can also be referred to the corresponding structures and related descriptions shown in the above Figure 13 and will not be described in detail here.

[0213] The reference in the specification to "one embodiment" or "an embodiment" means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one of the example embodiments or techniques disclosed in accordance with the present application. The appearance of the phrase "in one embodiment" in various places in the specification is not necessarily all referring to the same embodiment.

[0214] The present application discloses also an apparatus for performing the operations in the text. This apparatus can be specially constructed for the required purposes or it can comprise a general purpose computer selectively activated or reconfigured by a computer program stored in the computer. Such a computer program can be stored in a computer readable medium, such as, but not limited to any type of disk including floppy disks, optical disks, CD-ROMs, magnetic-optical disks, read-only memories (ROMs), random access memories (RAMs), EPROMs, EEPROMs, magnetic or optical cards, application specific integrated circuits (ASICs), or any type of media suitable for storing electronic instructions, and each coupled to a computer system bus. Furthermore, the computers described in the specification can include a single processor or can be architectures employing multiple processor designs for increased computing capability.

[0215] The processes and displays presented herein are not inherently related to any particular computer or other apparatus. Various general purpose systems can be used with programs in accordance with the teachings herein, or it can prove convenient to construct more specialized apparatus to perform one or more method steps. The structure for a variety of these systems is discussed in the description below. In addition, any particular programming language can be used to implement the teachings of the present disclosure as discussed herein. Various programming languages can be used to implement the present disclosure as discussed herein.

[0216] Also, the language used in the specification has been principally selected for readability and instructional purposes and can not have been selected to delineate or circumscribe the disclosed subject matter. Accordingly, the present application discloses are intended to be illustrative, not limiting, of the scope of the concepts discussed herein.

Claims

1. An electronic payment method applied to an electronic device, wherein a plurality of payment applications and a payment management application are installed on the electronic device, and the method comprises the steps of: The electronic device is equipped with a distributed operating system, the plurality of payment applications have payment capability modules that can be independently invoked, and when the plurality of payment applications are installed on the electronic device, the registration and authorization of the payment capability modules of each payment application are completed on a characteristic capability management module in the distributed operating system, and the method comprises: ​ In the case where the authorization operation of the user is detected, the payment management application acquires the management right of the payment capability module of the first payment application through the characteristic capability management module, and the plurality of payment applications include the first payment application; The payment management application detects a first payment operation of the user in the payment management application, wherein the first payment operation indicates that the payment function is completed by using the first payment application; The payment management application invokes the payment capability module of the first payment application to complete the payment function corresponding to the first payment operation.

2. The method of claim 1, wherein, The payment management application invoking the payment function of the first payment application comprises: The payment management application invokes the payment capability module of the first payment application to generate a payment code and displays the payment code in the display interface of the payment management application; or The payment management application invokes the payment capability module of the first payment application to display a code scanning window in the display interface of the payment management application.

3. The method of claim 1, wherein, The payment management application displays prompt information that the payment corresponding to the first payment operation has been completed.

4. The method of claim 1, wherein, After the payment management application invokes the payment capability module of the first payment application to complete the payment function corresponding to the first payment operation, the method further comprises: The payment management application records first payment data generated by completing the first payment operation.

5. The method of claim 1, wherein, Before the payment management application detects the first payment operation of the user in the payment management application, the method further comprises: In the display interface of the payment management application or the display interface of the first payment application, the authorization prompt information is displayed to the user, wherein The authorization prompt information is used to prompt the user whether to authorize the management right of the payment capability module of the first payment application to the payment management application; In the case where the authorization operation of the user is detected, the management right of the payment capability module of the first payment application is authorized to the payment management application, and prompt information that the authorization is successful is displayed.

6. The method of claim 5, wherein, The management right comprises that the payment management application can complete payment by invoking the payment capability module of the first payment application, and The payment management application can obtain first historical payment data from the first payment application.

7. The method of claim 6, wherein, The method further comprises: The payment management application generates a payment record of at least one user of the electronic device based on the first historical payment data and second historical payment data, wherein The second historical payment data is the record data of the payment operation completed by the payment management application invoking the first payment application.

8. The method of claim 7, wherein, The first historical payment data or the second historical payment data comprises: One or more of the occurrence time of the payment operation, the transaction nature, the merchant name, the payee account, the merchant serial number, the payment method, the payment account, and the serial number.

9. The method of claim 8, wherein, The method further comprises: Based on the payment record of the user, a financial analysis report or a financial suggestion corresponding to the user is generated.

10. The method of claim 5, wherein, The display interface of the payment management application includes an authorization management control.

11. The method of claim 10, wherein, The method further includes: After detecting the operation of the user on the authorization management control, the payment management application displays the authorized payment application and the unauthorized payment application to the user. After detecting that the user confirms the authorization of at least one of the unauthorized payment applications, the payment management application acquires the management right of the payment capability module of the payment application authorized by the user, and displays a prompt information of successful authorization.

12. The method of claim 10, wherein, The method further includes: After detecting the operation of the user on the authorization management control, the payment management application deletes the payment application selected by the user to terminate the authorization.

13. The method according to any one of claims 1 to 12, characterized in that, The distributed operating system of the electronic device includes a Hongmeng operating system.

14. An electronic device, comprising: Comprise: One or more processors; One or more memories; the one or more memories store one or more programs, when the one or more programs are executed by the one or more processors, the electronic device executes the electronic payment method in any one of claims 1-13.

15. A computer-readable storage medium, characterized in that, The storage medium stores instructions, which, when executed on a computer, cause the computer to execute the electronic payment method in any one of claims 1-13.

16. A computer program product, characterised in that, Include computer programs / instructions, which, when executed by a processor, implement the electronic payment method in any one of claims 1-13.

Images