Resource management product processing method and device, electronic equipment, computer readable storage medium and computer program product

Abstract

The invention provides a resource management product processing method and device, electronic equipment, a computer readable storage medium and a computer program product. The method comprises the steps that a first income list of a resource management product is displayed, and the first income list comprises a plurality of first incomes corresponding to the resource management product in a plurality of historical cycles; in response to a selection operation for a target historical period, displaying an income detail interface of the resource management product in the target historical period, the target historical period comprising a plurality of historical natural days; and displaying a plurality of second earnings respectively corresponding to the resource management product in the plurality of historical natural days in the earning detail interface. Through the application, the sensitivity of short-term fluctuation of the market can be reduced, the user can pay attention to long-term return of investment, meanwhile, the investment emotion of the user can be stabilized, and a trust relationship with a financial management platform can be established.

Description

Technical Field

[0001] This application relates to the field of Internet technology, and in particular to a method, apparatus, electronic device, computer-readable storage medium, and computer program product for processing resource management products. Background Technology

[0002] With the rapid development of internet technology, various financial institutions have launched their own internet applications and corresponding financial products within these applications, which has greatly improved the efficiency of people's financial product processing.

[0003] Fund products are a type of financial product. Funds are initiated by fund management companies or other institutions, raising capital from the public and then investing in various assets such as stocks, bonds, and money market instruments to achieve the goals of diversification, risk reduction, and increased returns. Bond funds, in particular, are funds that specialize in investing in bonds. They pool funds from numerous investors to create a diversified portfolio of bonds, seeking relatively stable returns. However, while bond funds are generally low-risk, market fluctuations can lead to negative returns on certain trading days. Since some users are highly sensitive to returns, emotional fluctuations can cause them to redeem their funds, resulting in losses for both the users and the investment platform. Summary of the Invention

[0004] This application provides a method, apparatus, electronic device, computer-readable storage medium, and computer program product for processing resource management products. These methods can reduce the sensitivity to short-term market fluctuations, allow users to focus on long-term investment returns, stabilize users' investment sentiment, and establish a trust relationship with the financial management platform.

[0005] The technical solution of this application embodiment is implemented as follows:

[0006] This application provides a method for processing a resource management product, including:

[0007] Display the first revenue list of the resource management product, wherein the first revenue list includes multiple first revenues corresponding to the resource management product in multiple historical periods;

[0008] In response to the selection operation for a target historical period, the revenue details interface of the resource management product within the target historical period is displayed, wherein the target historical period includes multiple historical calendar days;

[0009] The revenue details interface displays multiple secondary revenues corresponding to the resource management product within the multiple historical natural days.

[0010] This application provides a processing apparatus for a resource management product, including:

[0011] The display module is used to display a first revenue list of the resource management product, wherein the first revenue list includes multiple first revenues corresponding to the resource management product in multiple historical periods.

[0012] The display module is also configured to, in response to a selection operation for a target historical period, display a revenue details interface of the resource management product within the target historical period, wherein the target historical period includes multiple historical natural days;

[0013] The display module is also used to display, in the revenue details interface, multiple second revenues corresponding to the resource management product within the multiple historical natural days.

[0014] This application provides an electronic device, including:

[0015] Memory is used to store executable instructions for a computer;

[0016] The processor, when executing computer-executable instructions stored in the memory, implements the processing method of the resource management product provided in the embodiments of this application.

[0017] This application provides a computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, implement the processing method of the resource management product provided in this application.

[0018] This application provides a computer program product, including a computer program or computer executable instructions, which, when executed by a processor, implements the processing method of the resource management product provided in this application.

[0019] The embodiments of this application have the following beneficial effects:

[0020] By aggregating multiple secondary returns corresponding to resource management products over multiple historical days, a primary return list for resource management products is obtained. This primary return list includes multiple primary returns corresponding to resource management products over multiple historical periods. This can smooth out small fluctuations in daily returns, reduce sensitivity to short-term market fluctuations, and allow users to focus on long-term investment returns. At the same time, it retains the function of allowing users to view the returns of resource management products for each historical day within a certain historical period, thereby stabilizing users' investment sentiment and building trust between them and the financial management platform. Attached Figure Description

[0021] Figure 1 This is a schematic diagram of the architecture of the processing system 100 of the resource management product provided in this application embodiment;

[0022] Figure 2 This is a schematic diagram of the structure of the electronic device 500 provided in the embodiments of this application;

[0023] Figure 3 This is a first flowchart illustrating the processing method of the resource management product provided in this application embodiment;

[0024] Figure 4 This is a second flowchart illustrating the processing method of the resource management product provided in this application embodiment;

[0025] Figure 5 This is a schematic diagram of the third process of the resource management product processing method provided in the embodiments of this application;

[0026] Figure 6 This is a schematic diagram illustrating an application scenario of the processing method for the resource management product provided in this application embodiment;

[0027] Figure 7 This is a schematic diagram illustrating the principle of the processing method of the resource management product provided in the embodiments of this application;

[0028] Figure 8 This is a schematic diagram of the fourth process of the resource management product processing method provided in the embodiments of this application;

[0029] Figure 9 This is a schematic diagram of the fifth process of the resource management product processing method provided in the embodiments of this application;

[0030] Figure 10 This is a schematic diagram of the sixth process of the resource management product processing method provided in the embodiments of this application;

[0031] Figure 11 This is a schematic diagram of the seventh process of the resource management product processing method provided in the embodiments of this application;

[0032] Figure 12 This is the eighth flowchart of the processing method for the resource management product provided in the embodiments of this application. Detailed Implementation

[0033] To make the objectives, technical solutions, and advantages of this application clearer, the application will be further described in detail below with reference to the accompanying drawings. The described embodiments should not be regarded as limitations on this application. All other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0034] In the following description, references are made to “some embodiments,” which describe a subset of all possible embodiments. However, it is understood that “some embodiments” may be the same subset or different subsets of all possible embodiments and may be combined with each other without conflict.

[0035] It is understood that in the embodiments of this application, data such as user information are involved. When the embodiments of this application are applied to specific products or technologies, user permission or consent is required, and the collection, use and processing of related data must comply with relevant laws, regulations and standards.

[0036] In the following description, the terms “first, second, ...” are used merely to distinguish similar objects and do not represent a specific ordering of objects. It is understood that “first, second, ...” may be interchanged in a specific order or sequence where permitted, so that the embodiments of this application described herein can be implemented in an order other than that illustrated or described herein.

[0037] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this application belongs. The terminology used herein is for the purpose of describing embodiments of this application only and is not intended to limit this application.

[0038] Before providing a further detailed description of the embodiments of this application, the nouns and terms involved in the embodiments of this application will be explained, and the nouns and terms involved in the embodiments of this application shall be interpreted as follows.

[0039] 1) Responding to: used to indicate the conditions or states on which the operation is performed depends. When the conditions or states on which it depends are met, one or more operations can be performed in real time or with a set delay. Unless otherwise specified, there is no restriction on the order in which the multiple operations are performed.

[0040] 2) Resource management products: These include financial products and products with financial transaction attributes. Financial products may include funds, stocks, and bonds, while products with financial transaction attributes may include digital resources, precious metals, and collectibles.

[0041] 3) Transaction date: refers to the date on which a transaction occurs for a resource management product. Transaction dates generally cover weekdays from Monday to Friday, but exclude weekends and statutory holidays.

[0042] This application provides a method, apparatus, electronic device, computer-readable storage medium, and computer program product for processing resource management products. These technologies can reduce sensitivity to short-term market fluctuations, allowing users to focus on long-term investment returns, while also stabilizing user investment sentiment and establishing trust between the user and the financial management platform. The electronic device provided in this application is described below. The electronic device provided in this application can be implemented as various types of terminal devices such as smartphones, tablets, laptops, desktop computers, smart speakers, smartwatches, and in-vehicle terminals.

[0043] For example, see Figure 1 , Figure 1 This is a schematic diagram of the architecture of the processing system 100 of the resource management product provided in this application embodiment, as shown below. Figure 1 As shown in the embodiment of this application, the processing system 100 for the resource management product includes: a server 200, a network 300, and a terminal device 400. The server 200 can be an independent physical server, a server cluster or distributed system composed of multiple physical servers, or a cloud server providing basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, content delivery networks (CDNs), and big data and artificial intelligence platforms. The network 300 can be a local area network (LAN), a wide area network (WAN), or a combination of both. The terminal device 400 is a user-associated terminal device, on which a client 410 runs. The client 410 can be various types of financial management clients.

[0044] In some embodiments, when client 410 receives a user-triggered return viewing operation, it can send a return query request to server 200 via network 300. The return query request may carry the product identifier of the resource management product to be queried (e.g., a bond fund). After receiving the return query request from client 410, server 200 can first parse the product identifier from the request, and then return a first return list of the resource management product corresponding to the product identifier to client 410 via network 300 for display. This first return list may include multiple first returns corresponding to the resource management product in multiple historical periods. Next, in response to the user's selection of a target historical period, client 410 can display a return details interface for the resource management product within that target historical period, which may include multiple historical calendar days. Subsequently, client 410 can display multiple second returns corresponding to the resource management product within the multiple historical calendar days in the return details interface.

[0045] In other embodiments, the terminal device can also implement the processing method of the resource management product provided in this application embodiment by running various computer-executable instructions or computer programs. For example, computer-executable instructions can be microprogram-level commands, machine instructions, or software instructions. Computer programs can be native programs or software modules in an operating system; they can be native applications (APPs), i.e., programs that need to be installed in the operating system to run, such as financial management APPs; or they can be applets that can be embedded in any APP, i.e., programs that only need to be downloaded to a browser environment to run. In summary, the above-mentioned computer-executable instructions can be any form of instruction, and the above-mentioned computer programs can be any form of application, module, or plugin.

[0046] The structure of the electronic device provided in the embodiments of this application will be further described below. Taking the electronic device as a terminal device as an example, see... Figure 2 , Figure 2 This is a schematic diagram of the structure of the electronic device 500 provided in the embodiments of this application. Figure 2 The illustrated electronic device 500 includes at least one processor 510, a memory 550, at least one network interface 520, and a user interface 530. The various components in the electronic device 500 are coupled together via a bus system 540. It is understood that the bus system 540 is used to implement communication between these components. In addition to a data bus, the bus system 540 also includes a power bus, a control bus, and a status signal bus. However, for clarity, ... Figure 2 The general labeled all buses as Bus System 540.

[0047] The processor 510 can be an integrated circuit chip with signal processing capabilities, such as a general-purpose processor, a digital signal processor (DSP), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor can be a microprocessor or any conventional processor.

[0048] User interface 530 includes one or more output devices 531 that enable the presentation of media content, including one or more speakers and / or one or more visual displays. User interface 530 also includes one or more input devices 532, including user interface components that facilitate user input, such as a keyboard, mouse, microphone, touch screen display, camera, other input buttons and controls.

[0049] The memory 550 may be removable, non-removable, or a combination thereof. Exemplary hardware devices include solid-state storage, hard disk drives, optical disk drives, etc. The memory 550 may optionally include one or more storage devices physically located away from the processor 510.

[0050] The memory 550 may include volatile memory or non-volatile memory, or both. The non-volatile memory may be read-only memory (ROM), and the volatile memory may be random access memory (RAM). The memory 550 described in this application embodiment is intended to include any suitable type of memory.

[0051] In some embodiments, memory 550 is capable of storing data to support various operations, examples of which include programs, modules, and data structures or subsets or supersets thereof, as illustrated below.

[0052] Operating system 551 includes system programs for handling various basic system services and performing hardware-related tasks, such as the framework layer, core library layer, driver layer, etc., for implementing various basic business functions and handling hardware-based tasks;

[0053] The network communication module 552 is used to reach other computing devices via one or more (wired or wireless) network interfaces 520, exemplary network interfaces 520 including: Bluetooth, WiFi, and Universal Serial Bus (USB), etc.

[0054] Presentation module 553 is configured to enable the presentation of information (e.g., a user interface for operating peripheral devices and displaying content and information) via one or more output devices 531 (e.g., a display screen, a speaker, etc.) associated with user interface 530;

[0055] The input processing module 554 is used to detect and translate one or more user inputs or interactions from one or more input devices 532.

[0056] In some embodiments, the apparatus provided in this application can be implemented in software. Figure 2 A processing device 555 for a resource management product stored in memory 550 is shown. This device can be software in the form of programs and plug-ins, including the following software modules: a display module 5551, an acquisition module 5552, and a determination module 5553. These modules are logically linked and can therefore be arbitrarily combined or further separated according to the functions implemented. It should be noted that... Figure 2For ease of explanation, all the above modules are shown at once, but this should not be considered as excluding the implementation of the resource management product processing device 555 which may only include the display module 5551. The functions of each module will be described below.

[0057] The following will describe in detail the processing method of the resource management product provided in the embodiments of this application, taking into account the exemplary application and implementation of the terminal device provided in the embodiments of this application.

[0058] For example, see Figure 3 , Figure 3 This is a first flowchart illustrating the processing method of the resource management product provided in this application embodiment, which will be combined with... Figure 3 The steps shown are explained.

[0059] It should be noted that, Figure 3 The method illustrated can be executed by various forms of computer programs running on the terminal device, and is not limited to a client. For example, it can also be the operating system, software module, script, and applet mentioned above. Therefore, the client-side examples used below should not be considered as limiting the embodiments of this application. Furthermore, for ease of description, no specific distinction will be made between the terminal device and the client running on the terminal device below.

[0060] In step 101, the first revenue list of the resource management product is displayed.

[0061] Here, the first revenue list can include multiple first revenues for the resource management product across multiple historical periods. For example, when the historical period corresponds to a weekly time dimension, the first revenue list is the weekly revenue list for the resource management product, with the corresponding first revenue being weekly revenue. In other words, the weekly revenue list can display multiple weekly revenues for the resource management product over the past several weeks, allowing users to view the revenue of the resource management product in a particular week. Similarly, when the historical period corresponds to a monthly time dimension, the first revenue list is the monthly revenue list for the resource management product, with the corresponding first revenue being monthly revenue. This means that the monthly revenue list can display multiple monthly revenues for the resource management product over the past several months, allowing users to view the revenue of the resource management product in a particular month.

[0062] It should be noted that the first earnings list, in addition to including multiple historical periods and multiple first earnings corresponding to the resource management product within each historical period, may also include the current period (e.g., the current week or the current month) and the first notification information corresponding to the current period. The first notification information can be used to indicate that the resource management product's first earnings for the current period will be updated after the current period ends. Alternatively, the first earnings list may also include the current period, the earnings already credited to the resource management product within the current period, and a second notification information. The second notification information can be used to indicate that the resource management product's first earnings for the current period are being updated (e.g., the weekly earnings for the current week are being updated). For example, taking the current period as the current week, since the current week has not ended and the weekly earnings for the resource management product in the current week cannot be obtained, the weekly earnings for the resource management product in the current week may not be displayed in the first earnings list (i.e., the weekly earnings list), but the user may be prompted that the weekly earnings for the resource management product in the current week will be updated after 0:00 on Monday of the following week. Alternatively, the weekly earnings list may also display the earnings already credited to the resource management product in the current week and prompt the user that the weekly earnings for the current week are being updated.

[0063] For example, taking a resource management product as a bond fund, in addition to providing a daily return query option (such as a "Daily Return" tab control), the bond fund's return interface can also provide at least one of a weekly return query option (such as a "Weekly Return" tab control) and a monthly return query option (such as a "Monthly Return" tab control). When a user selects the weekly return query option in the returns interface, for example, if the user clicks the "Weekly Returns" tab control displayed in the returns interface, a list of weekly returns for bond funds can be displayed in the returns interface. The weekly return list can include multiple weekly returns for the bond fund over the past several weeks (e.g., the past 15 weeks). The weekly returns can be obtained by aggregating the daily returns of the bond fund over multiple historical natural days according to the week. For example, for week 11, assuming that week 11 corresponds to March 10 to March 16, the returns of the bond fund for the 7 natural days from March 10 to March 16 can be aggregated to obtain the weekly return of the bond fund in week 11. Furthermore, the weekly return list can also include the current week (e.g., week 16). Since the current week has not yet ended, this application embodiment can provide the following two solutions for the current week: First, do not display the weekly return of the bond fund in the current week in the weekly return list, but only prompt the user that the weekly return of the bond fund in the current week will be updated after 0:00 on the following Monday; second, display the income already credited to the account for the bond fund in the current week in the weekly return list, and prompt the user that the weekly return for the current week is being updated. In other words, this application embodiment can provide users with a new return dimension (i.e., the weekly dimension). The weekly dimension return has better return stability than the trading day dimension return, which can smooth out the small fluctuations in trading day returns. The probability of a negative weekly return is also lower, thus providing a better profit experience for users.

[0064] It should be noted that if the user selects the monthly return query option in the aforementioned returns interface, for example, if the user clicks on the "Monthly Returns" tab control displayed in the returns interface, the returns interface can also display multiple monthly returns for the bond fund over the past several months (e.g., the past 10 months). The monthly return can be obtained by aggregating the daily returns of the bond fund over multiple historical natural days according to the month dimension. For example, for the first month, assuming the dates of the first month are January 1st to January 31st, the daily returns of the bond fund for these 31 natural days from January 1st to January 31st can be aggregated to obtain the monthly return of the bond fund in the first month. In addition, the monthly return list may also include the current month (for example, the 11th month). Since the current month has not ended, the embodiments of this application can provide the following two solutions for the current month: First, do not display the monthly return of the bond fund in the current month in the monthly return list, but only prompt the user that the monthly return of the bond fund in the current month will be updated on the 1st of the next month; Second, display the returns of the bond fund that have been credited in the current month in the monthly return list, and prompt the user that the monthly return of the current month is being updated.

[0065] In some embodiments, step 101 above can also be implemented in the following ways: displaying the timeline of the resource management product; in response to the time period selection operation based on the timeline, obtaining multiple historical periods located within the selected timeline; displaying a first revenue list of the resource management product, wherein the first revenue list includes multiple first revenues corresponding to the resource management product in the multiple historical periods respectively.

[0066] For example, taking a resource management product as a bond fund, when a user opens a wealth management app, the homepage of the app can display at least one bond fund held by the user. When the user selects a bond fund from the at least one bond fund, the timeline of the selected bond fund can be displayed. The starting point of the timeline can be the date the user bought the bond fund, and the ending point of the timeline can be the current date. Users can select time periods based on this timeline. For example, two points in time triggered by the user on the timeline can be used as the start and end points of the selected time period. In addition, users can choose to view the weekly or monthly returns of the selected bond funds. If a user chooses to view the weekly returns of the selected bond funds, for example, if the system receives a click on the "Weekly Returns" tab, it can retrieve multiple historical weeks within the selected time period (e.g., week 6 to week 11) and display a list of weekly returns for the selected bond funds. This list can include multiple weekly returns for the selected bond funds within weeks 6 to 11. In other words, users can select time periods based on the timeline of the selected bond funds, thereby accurately viewing the weekly returns of the selected bond funds within a specific time period, further enhancing the user's query experience. Of course, if a user chooses to view the monthly returns of a selected bond fund, for example, by receiving a click on the "Monthly Returns" tab control, multiple historical months within the selected time period (e.g., from February to April) can be retrieved, and a list of monthly returns for the selected bond fund can be displayed. This list can include the returns for each of the three months from February to April. In other words, users can select a time period based on the timeline of the selected bond fund, thus accurately viewing the monthly returns of the selected bond fund within a specific time period, thereby improving the user's query experience.

[0067] It should be noted that in practical applications, in addition to selecting time periods based on the timeline of the resource management product, time periods can also be selected in other ways. For example, time periods can also be selected based on the time period setting control. For instance, two dates entered by the user in the time period setting control can be used as the start date and end date of the selected time period, respectively. This application embodiment does not specifically limit this.

[0068] In other embodiments, see Figure 4 , Figure 4 This is a schematic diagram of the second process of the resource management product processing method provided in the embodiments of this application, such as... Figure 4 As shown, Figure 3 Step 101 shown can be achieved through Figure 4 The implementation of steps 1011 and 1012 shown will be combined with Figure 4 The steps shown are explained.

[0069] In step 1011, in response to the operation of viewing the revenue of the resource management product, the revenue interface of the resource management product is displayed.

[0070] Here, the earnings interface can include multiple tab controls, each corresponding to a different time dimension. For example, the multiple tab controls can include a "Monthly Earnings" tab control, a "Weekly Earnings" tab control, and a "Daily Earnings" tab control. The "Monthly Earnings" tab control corresponds to a monthly time dimension and is used to display the monthly earnings of the resource management product over the past several months. The "Weekly Earnings" tab control corresponds to a weekly time dimension and is used to display the weekly earnings of the resource management product over the past several weeks. The "Daily Earnings" tab control corresponds to a daily time dimension and is used to display the daily earnings of the resource management product over the past several calendar days.

[0071] In some embodiments, step 1011 can be implemented as follows: displaying at least one resource management product held by the target object (i.e., the user); in response to a selection operation for at least one resource management product, displaying a details interface for the selected resource management product, wherein the details interface may include a revenue viewing control for the selected resource management product; and in response to a trigger operation for the revenue viewing control, displaying a revenue interface for the selected resource management product.

[0072] For example, taking bond funds as a resource management product, a financial management app can run on a user's device. When the user opens the app, at least one bond fund held by the user can be displayed on the app's homepage. For instance, suppose there are three different bond funds: Bond Fund 1, Bond Fund 2, and Bond Fund 3. These three bond funds can be issued by the same fund company or by different fund companies. For example, Bond Fund 1 could be issued by Fund Company A, Bond Fund 2 by Fund Company B, and Bond Fund 3 by Fund Company 3. The user can select the bond fund of interest from these three funds. Suppose the user selects Bond Fund 2. If the app receives a click on the identifier (e.g., name or icon) of Bond Fund 2, the details page for Bond Fund 2 can be displayed, showing a button to view the returns of Bond Fund 2. When a user clicks the "View Returns" button, the system will redirect from the details page of Bond Fund 2 to the returns page of Bond Fund 2, allowing users to view the returns of Bond Fund 2, such as weekly or monthly returns.

[0073] In other embodiments, after displaying the revenue interface of the resource management product, at least one of the following can also be displayed on the revenue interface: the cumulative revenue of the resource management product, the first revenue of the resource management product in the previous historical period (e.g., the weekly revenue of last week), wherein the cumulative revenue is obtained by adding up the multiple third revenues corresponding to the resource management product in multiple historical trading days.

[0074] For example, taking a bond fund as an example of a resource management product, the return interface of a bond fund can provide at least one of the following options: daily return (e.g., a "Daily Return" tab control), weekly return (e.g., a "Weekly Return" tab control), and monthly return (e.g., a "Monthly Return" tab control). If the user selects the weekly return option, for example, by clicking the "Weekly Return" tab control, the return interface can display not only the weekly return list of the bond fund, but also the cumulative return and the return of the previous week. For example, the cumulative return of the bond fund can be displayed in the upper left corner of the return interface. The cumulative return can be the return of the bond fund over multiple trading days (e.g., ...). For example, the daily returns could be accumulated from all trading days since the user purchased the bond fund. Additionally, the weekly returns for the previous week could be displayed in the upper right corner of the returns interface, allowing users to easily and intuitively understand the overall and current returns of the bond fund. If the user selects the monthly returns option on the returns interface, for example, by clicking the "Monthly Returns" tab, in addition to displaying the monthly returns list, the cumulative returns and the previous month's returns could also be shown. For instance, the cumulative returns could be displayed in the upper left corner of the returns interface, and the monthly returns for the previous month could be displayed in the upper right corner.

[0075] It should be noted that if a user selects the daily return query option on the aforementioned returns interface, for example, by clicking the "Daily Returns" tab, the returns interface will display not only the daily return list for that bond fund, but also its cumulative return and the previous day's return. For instance, the cumulative return could be displayed in the upper left corner of the returns interface, and the previous day's daily return in the upper right corner. In other words, the content displayed on the returns interface will change according to the user's selections.

[0076] In step 1012, in response to the first tab control among multiple tab controls being selected, the first revenue list of the resource management product is displayed in the revenue interface.

[0077] Here, the first revenue list includes multiple second revenues for the resource management product across multiple historical calendar days, aggregated according to the time dimension corresponding to the first tab control. For example, when the time dimension corresponding to the first tab control is weekly, the daily revenue of the resource management product can be aggregated according to the weekly dimension to obtain the weekly revenue; when the time dimension corresponding to the first tab control is monthly, the daily revenue of the resource management product can be aggregated according to the monthly dimension to obtain the monthly revenue; and when the time dimension corresponding to the first tab control is quarterly, the daily revenue of the resource management product can be aggregated according to the quarterly dimension to obtain the quarterly revenue.

[0078] In some embodiments, taking a bond fund as an example of a resource management product, the return interface of a bond fund can display multiple tab controls, such as tab controls for "Quarterly Returns," "Monthly Returns," "Weekly Returns," and "Daily Returns." When a user clicks on the "Quarterly Returns" tab control displayed on the return interface, a list of quarterly returns for the bond fund can be displayed on the return interface. This list can include the quarterly returns of the bond fund over the past few quarters (e.g., the first and second quarters). When a user clicks on the "Monthly Returns" tab control displayed on the return interface... When the user clicks the button, the monthly return list of the bond fund can be displayed on the return interface. This monthly return list can include multiple monthly returns for the bond fund over the past few months (e.g., from month 1 to month 6). When the user clicks the "Weekly Returns" tab control displayed on the return interface, the weekly return list of the bond fund can be displayed on the return interface. This weekly return list can include multiple weekly returns for the bond fund over the past several weeks (e.g., from week 1 to week 20). In other words, this embodiment of the application can provide returns from different perspectives for the user to view, further improving the user's viewing experience.

[0079] In other embodiments, during execution Figure 3 Before step 101 shown, the following processing may also be performed: For each historical period included in the first revenue list, the following processing is performed, wherein the historical period includes multiple historical natural days: obtain multiple second revenues corresponding to the resource management product in the multiple historical natural days respectively; add the multiple second revenues together, and take the sum as the first revenue of the resource management product in the historical period.

[0080] For example, taking a bond fund as a resource management product, when the first return list is the weekly return list of that bond fund, for example, if the user selects the weekly return query option in the return interface, the following processing can be performed before displaying the weekly return list in the return interface of that bond fund: Aggregate the daily returns of the bond fund in the historical natural days according to the weekly dimension to obtain the corresponding weekly returns. For example, taking the first week as an example, assuming that the multiple historical natural days included in the first week are January 1 to January 7, the daily returns of the bond fund in these 7 days from January 1 to January 7 can be aggregated to obtain the weekly return of the bond fund in the first week. Similarly, multiple weekly returns corresponding to the bond fund in the past multiple weeks can be obtained. Then, the weekly return list of the bond fund can be displayed in the return interface. The weekly return list can include multiple weekly returns corresponding to the bond fund in the past multiple weeks (for example, assuming the first week to the 15th week). When the first return list is the monthly return list of the bond fund, for example, if the user selects the monthly return query option in the return interface, the following processing can be performed before the monthly return list is displayed in the return interface of the bond fund: Aggregate the multiple daily returns of the bond fund in multiple historical natural days according to the monthly dimension to obtain the corresponding monthly return. For example, taking the first month as an example, the 31 daily returns of the bond fund in the 31 days from January 1 to January 31 can be aggregated to obtain the monthly return of the bond fund in the first month. Using the same method, the multiple monthly returns of the bond fund in the past few months (for example, assuming 4 months, namely the first month to the fourth month) can be obtained. Then, the monthly return list of the bond fund can be displayed in the return interface. The monthly return list can include the multiple monthly returns of the bond fund in the past few months.

[0081] In other embodiments, following the above examples, the acquisition of multiple second returns corresponding to the resource management product over multiple historical natural days can be achieved in the following manner: For each historical natural day among the multiple historical natural days, the following processing is performed: When the historical natural day is a historical rest day, the second return of the resource management product on that historical rest day is determined based on the daily rate of return of that historical rest day; when the historical natural day is a historical trading day and the day before that historical trading day is a historical rest day, the second return of the resource management product on that historical trading day is determined based on the return of the resource management product on that historical trading day and the cumulative return of the resource management product over multiple historical rest days; when the historical natural day is a historical trading day and the day before that historical trading day is also a historical trading day, the difference between the unit net value of the resource management product on that historical trading day and the unit net value of the previous historical trading day is determined, and the result of multiplying the difference by the holding shares of the resource management product is used as the second return of the resource management product on that historical trading day.

[0082] For example, the above-mentioned daily rate of return based on the historical rest day can be achieved by determining the second return of the resource management product on the historical rest day in the following way: Add the daily rate of return of the historical rest day to a preset value (e.g., 1) to obtain a fourth sum; use the fourth sum as the base and a third quantity as the exponent to perform a power operation to obtain a third power operation result, where the third quantity is the number of days between the historical rest day and the second historical trading day, and the second historical trading day is the historical trading day that is before the historical rest day and closest to the historical rest day; multiply the third power operation result by the total amount of the resource management product on the second historical trading day to obtain a second multiplication result; use the difference between the second multiplication result and the total amount as the second return of the resource management product on the historical rest day.

[0083] For example, the second revenue of the resource management product on the historical trading day can be determined by the following method: The revenue of the resource management product on the historical trading day is summed up to obtain the cumulative revenue of the resource management product on the historical trading day, where the historical trading day falls between the current historical trading day and the previous historical trading day; the revenue of the resource management product on the historical trading day is subtracted from the cumulative revenue, and the result of the subtraction is taken as the second revenue of the resource management product on the historical trading day.

[0084] For example, taking the time dimension corresponding to the historical cycle as the week dimension, each historical cycle includes 7 historical natural days. For example, taking the first historical cycle (e.g., week 15) of multiple historical cycles as an example, assuming that the 7 historical natural days included in week 15 are April 7th to April 13th, and assuming that April 7th is a Saturday, April 8th is a Sunday, April 9th ​​is a Monday, April 10th is a Tuesday, April 11th is a Wednesday, April 12th is a Thursday, and April 13th is a Friday, that is, April 7th and April 8th are historical rest days, and April 9th ​​to April 13th are historical trading days, then the daily returns of resource management products (e.g., bond funds) within these 7 historical natural days can be calculated in the following way: First, obtain the daily yield of the bond fund on April 7th and April 8th. These two daily yields can be determined based on the yield of the bond fund on April 9th, which will be explained in detail below. After obtaining the daily returns of the bond fund on April 7th and April 8th, the daily return for April 7th can be calculated as follows: Add the daily return of the bond fund on April 7th (e.g., 0.0015) to 1, multiply the result (1.0015) by the total amount of the bond fund at the end of trading on April 6th (e.g., 100 yuan), and subtract the result from the total amount. The difference between the two (i.e., 0.15 yuan) is taken as the daily return of the bond fund on April 7th. For April 8th, the daily return of the bond fund on April 8th can be calculated as follows: Add the daily return of the bond fund on April 8th (for example, assuming it's 0.0015) to 1, and use the sum (i.e., 1.0015) as the base, and raise it to the power of 2 (since April 8th is the second rest day, the exponent is 2) to obtain the power result (i.e., 1.0015). 2=1.003), and then the result of the exponentiation can be multiplied by the total amount of the bond fund at the end of the trading day on April 6 (for example, assuming it is 100 yuan), and the result of the multiplication can be subtracted from the total amount. The result of the subtraction (i.e., 0.3 yuan) can be used as the daily return of the bond fund on April 8. After obtaining the daily returns of the bond fund on April 7th and 8th, the daily returns on April 7th and 8th can be added together to obtain the cumulative return of the bond fund over these two historical rest days (i.e., 0.45 yuan). Then, the daily return of the bond fund on April 9th ​​(e.g., 0.3 yuan) can be subtracted from the cumulative return over these two historical rest days, and the result of the subtraction (i.e., -0.15 yuan) can be taken as the final daily return of the bond fund on April 9th. In this way, the daily return of the bond fund on Monday can be split over Saturday and Sunday, and the 7-day annualized yield of the bond fund can be calculated. Furthermore, for the period from April 10th to April 13th, the daily return can be calculated as follows: Daily Return = Number of Units Held × (Latest Net Asset Value per Unit - Net Asset Value per Unit of the Previous Trading Day). For example, taking April 10th as an example, assuming that the net asset value per unit of the bond fund was 1.0012 yuan / unit at the end of the trading day on April 10th, and assuming that the net asset value per unit of the bond fund was 1.0001 yuan / unit on the previous trading day (i.e., April 9th), and the user held 1000 units of the bond fund, then the daily return of the bond fund on April 10th would be 1000 units × (1.0012 yuan / unit - 1.0001 yuan / unit) = 1.1 yuan. Using the same method, the daily return of the bond fund from April 11th to April 13th can be calculated.

[0085] In other embodiments, after execution Figure 4 Following step 1011, the following processing may also be performed: In response to the selection of a second tab control (e.g., the "Daily Revenue" tab control) among multiple tab controls, a second revenue list (e.g., a daily revenue list) of the resource management product is displayed in the revenue interface, wherein the second revenue list includes multiple second revenues (e.g., daily revenues) corresponding to the resource management product in multiple historical natural days.

[0086] For example, taking a bond fund as a resource management product, the fund's return interface can provide at least one of the following: daily return query option (e.g., a "Daily Return" tab control), weekly return query option (e.g., a "Weekly Return" tab control), and monthly return query option (e.g., a "Monthly Return" tab control). If a user selects the daily return query option on the return interface, for example, when the user clicks on the "Daily Return" tab control displayed on the return interface, a list of daily returns for the bond fund can be displayed. This list can include multiple daily returns for the bond fund over the past several days (e.g., all calendar days since the user purchased the bond fund). In other words, users can view not only the weekly or monthly returns of the bond fund, but also its daily returns, thus meeting users' viewing needs at different granularities.

[0087] In some embodiments, the aforementioned multiple historical periods are arranged sequentially in the first revenue list from latest to earliest by default. The first revenue list may also include a toggle control; see [link to relevant documentation]. Figure 5 , Figure 5 This is a schematic diagram of the third process of the resource management product processing method provided in the embodiments of this application, as shown below. Figure 5 As shown, after execution Figure 3 After step 101 shown, you can also execute... Figure 5 Step 104 shown will combine Figure 5 The steps shown are explained.

[0088] In step 104, in response to the trigger operation of the switching control, the resource management product is displayed in the first revenue list in the order after the switch, showing the first revenue corresponding to the resource management product in multiple historical periods.

[0089] Here, the order after switching can include one of the following: order from high to low returns, or order from low to high returns.

[0090] In some embodiments, taking a bond fund as an example of a resource management product, the bond fund's return interface may provide at least one of the following: daily return query options (e.g., a "Daily Return" tab control), weekly return query options (e.g., a "Weekly Return" tab control), and monthly return query options (e.g., a "Monthly Return" tab control). When a user selects the weekly return query option in the return interface, for example, if the interface receives a click on the "Weekly Return" tab control, a list of weekly returns for the bond fund can be displayed. By default, the weekly return list displays the bond fund's weekly returns over the past few weeks (e.g., from week 1 to week 15) in ascending order of time. That is, the weekly return for week 15 is at the top of the weekly return list, and the weekly return for week 1 is at the bottom. In addition, a toggle button can be displayed in the weekly return list. When a user clicks the toggle button, the weekly returns of the bond fund over the past 15 weeks can be rearranged in descending order of weekly returns; alternatively, they can be rearranged in ascending order of weekly returns. This allows users to clearly see which week's weekly return was the highest and which week's weekly return was the lowest, thus facilitating their subsequent decision-making.

[0091] It should be noted that if a user selects the monthly return query option on the aforementioned returns interface, for example, if the system receives a click on the "Monthly Returns" tab control from the user, the monthly return list for that bond fund will be displayed on the returns interface. By default, the monthly return list displays the monthly returns for that bond fund in ascending order of time over the past few months (for example, assuming 4 months, which are months 1 to 4). That is, the monthly return for month 4 is displayed at the top of the monthly return list, while the monthly return for month 1 is displayed at the bottom of the monthly return list. In addition, a toggle button can be displayed in the monthly return list. When a user clicks the toggle button, the monthly return list can be rearranged in descending order of monthly return, or in ascending order of monthly return. This allows users to clearly and quickly see which month's return was the highest and which month's return was the lowest, thus facilitating their subsequent decision-making.

[0092] In step 102, in response to the selection operation for the target historical period, the revenue details interface of the resource management product within the target historical period is displayed.

[0093] Here, the target historical period can include multiple historical natural days. For example, when the time dimension corresponding to the target historical period is the week dimension, the target historical period can include 7 historical natural days; when the time dimension corresponding to the target historical period is the month dimension, the target historical period can include 28, 30 or 31 historical natural days (depending on the specific month, the number of days included in different months is different).

[0094] In some embodiments, the first revenue list may further include multiple detail viewing controls corresponding to multiple historical periods. Step 102 can be implemented as follows: in response to the triggering operation of the detail viewing control corresponding to the target historical period, the revenue details interface of the resource management product in the target historical period is displayed, wherein the target historical period is the selected historical period among multiple historical periods.

[0095] For example, taking a bond fund as a resource management product, the fund's return interface can provide at least one of the following: daily return query options (e.g., a "Daily Return" tab control), weekly return query options (e.g., a "Weekly Return" tab control), and monthly return query options (e.g., a "Monthly Return" tab control). If a user selects the weekly return query option on the return interface, for example, by clicking the "Weekly Return" tab control, the weekly return list for the bond fund can be displayed. This list shows the weekly returns for the past several weeks (e.g., weeks 1 to 15) and also includes detailed view buttons for each past week. If a user is interested in the weekly return for a specific week in the list, for example, if they want to view the details for that week (e.g., week 15), they can click the detailed view button for that week. When a user clicks the "View Details" button for week 15 in the weekly returns list, the user is redirected to the returns details page for that bond fund within week 15. This page displays the daily returns for the seven historical calendar days included in week 15 (e.g., April 7th to April 13th). In other words, this embodiment of the application provides both weekly and daily returns, further enhancing the user experience.

[0096] It should be noted that if a user selects the monthly return query option on the aforementioned returns interface, for example, by clicking the "Monthly Returns" tab, the monthly return list for that bond fund will be displayed on the returns interface. This list will show not only the monthly returns for the bond fund over the past several months, but also detailed return buttons for each past month. If a user is interested in a specific month, they can click the detailed return button for that month (e.g., the 3rd month). When the user clicks the detailed return button for the 3rd month, the user will be redirected to the returns details interface for that bond fund within the 3rd month. This interface will display the daily returns for the 31 historical calendar days within the 31 days of the 3rd month (March 1st to March 31st).

[0097] In other embodiments, after displaying the revenue details interface of the resource management product within the target historical period, the following processing may also be performed: the revenue details interface displays the annualized rate of return (e.g., 7-day annualized rate of return) of the resource management product within the target historical period, wherein the annualized rate of return is determined based on the cumulative rate of return of the resource management product within the target historical period.

[0098] For example, taking a bond fund as a resource management product, after displaying the fund's return details for a target historical period (e.g., week 15), the return details page can also display the fund's 7-day annualized yield for week 15. This annualized yield can be determined based on the fund's cumulative yield over week 15; the specific calculation process for the 7-day annualized yield will be explained below. Thus, by displaying the bond fund's 7-day annualized yield on the return details page, users can compare its returns with those of money market funds, thereby guiding them from low-risk money market funds to medium-risk bond funds.

[0099] In some embodiments, following the above example, before displaying the annualized rate of return of the resource management product within the target historical period in the return details interface, the following processing may also be performed: obtaining multiple daily rates of return corresponding to multiple historical natural days included in the target historical period for the resource management product; determining the cumulative rate of return of the resource management product within the target historical period based on the multiple daily rates of return; and determining the annualized rate of return of the resource management product within the target historical period based on the cumulative rate of return.

[0100] For example, taking a resource management product as a bond fund, before displaying the annualized return of the bond fund in the return details interface for the target historical period (e.g., the 15th week), the annualized return of the bond fund in the 15th week can also be calculated in the following way: obtain the 7 daily returns corresponding to the 7 historical calendar days included in the 15th week (e.g., April 7th to April 13th), then calculate the cumulative return of the bond fund in these 7 days based on these 7 daily returns, and finally calculate the 7-day annualized return of the bond fund in the 15th week based on the cumulative return. The specific calculation process will be explained below.

[0101] In other embodiments, following the above, the acquisition of multiple daily yields of the resource management product within multiple historical natural days of the target historical period can be achieved in the following manner: For each historical natural day in the multiple historical natural days of the target historical period, the following processing is performed: When the historical natural day is a historical rest day (i.e., a non-trading day), the daily yield of the historical rest day is determined based on the daily yield of the historical trading day that is after the historical rest day and closest to the historical rest day; when the historical natural day is a historical trading day and the day before the historical trading day is a historical rest day, the result of splitting the daily yield of the historical trading day is used as the daily yield of the historical trading day; when the historical natural day is a historical trading day and the day before the historical trading day is also a historical trading day, the daily yield of the resource management product on that historical trading day is obtained, and the result of dividing the daily yield by the total amount of the resource management product on the previous historical trading day is used as the daily yield of that historical trading day.

[0102] For example, the above-mentioned method of determining the daily return of a historical rest day based on the daily return of the historical trading day that is after and closest to the historical rest day can be achieved as follows: Obtain the daily return of the historical trading day that is after and closest to the historical rest day; add the daily return to a preset value (e.g., 1) to obtain a third sum; use the third sum as the base and the result of dividing the preset value (e.g., 1) by a second quantity as the exponent to perform a power operation to obtain a second power operation result, where the second quantity is the number of days between the first and second historical trading days, the first historical trading day is the historical trading day that is after and closest to the historical rest day, and the second historical trading day is the historical trading day that is before and closest to the historical rest day; take the difference between the second power operation result and the preset value (e.g., 1) as the daily return of the historical rest day.

[0103] For example, taking the 15th week as the target historical period, assuming that the 7 historical calendar days included in the 15th week are April 7th to April 13th, and assuming that April 7th is a Saturday, April 8th is a Sunday, April 9th ​​is a Monday, April 10th is a Tuesday, April 11th is a Wednesday, April 12th is a Thursday, and April 13th is a Friday, that is, April 7th and April 8th are historical rest days, and April 9th ​​to April 13th are historical trading days, then the daily yield of resource management products (such as bond funds) within the above 7 historical calendar days can be calculated as follows: First, obtain the daily yield of the bond fund on April 9th ​​(for example, assuming it is 0.3 yuan) and the principal that generated the daily yield (i.e., the total amount of the bond fund after the close of trading on April 6th, for example, assuming it is 100 yuan). Then, obtain the daily yield of the bond fund on April 9th ​​(for example, assuming it is 0.3 yuan). The daily return on April 9th ​​is divided by the principal that generated that return (0.003), which is the total return rate. Then, the number of days between April 9th ​​(the date of this historical trading day) and the previous historical trading day (April 6th) is calculated (2). The total return rate is then added to 1 (1 + 0.003 = 1.003). Using the sum (1.003) as the base, the result of dividing 1 by the number of days (2) is used as the exponent to perform a power operation, resulting in 1.0015. Finally, the difference between the power operation result and 1 (1.0015 - 1 = 0.0015) is used as the daily return rate for April 7th, April 8th, and April 9th. In other words, the daily return rate for April 7th, April 8th, and April 9th ​​is 0.0015. Furthermore, the daily return rate from April 10th to April 13th can be calculated using the following formula: daily return rate divided by the principal amount that generated that daily return. For example, taking April 10th as an example, assuming the daily return rate of this bond fund on April 10th is 0.1 yuan, and the principal amount that generated that daily return (i.e., the total amount of the bond fund at the end of trading on April 9th) is 100.3 yuan, then the daily return rate of this bond fund on April 10th is 0.000997. Similarly, the daily return rate of this bond fund from April 11th to April 13th can be obtained. For example, assuming the return rate of this bond fund on April 11th is 0.00087, on April 12th is 0.00063, and on April 13th is -0.00076.

[0104] In some embodiments, following the above, the determination of the cumulative rate of return of a resource management product within a target historical period based on multiple daily rates of return can be achieved in the following way: adding the multiple daily rates of return to a preset value (e.g., 1) to obtain multiple first summation results; multiplying the multiple first summation results to obtain a first multiplication result; and taking the difference between the first multiplication result and the preset value (e.g., 1) as the cumulative rate of return of the resource management product within the target historical period.

[0105] For example, continuing from the previous example, let's take the 15th week as the target historical period. Assume the 15th week includes 7 historical days from April 7th to April 13th. Also, assume the resource management product (e.g., bond funds) has the following 7 daily returns during these 7 days: 0.0015, 0.0015, 0.0015, 0.000997, 0.00087, 0.00063, and -0.00076. Then, we can first add each of these 7 daily returns to 1 to obtain the following 7 sums: 1.0015, ... The sums are 1.0015, 1.0015, 1.000997, 1.00087, 1.00063, and 0.99924. These seven sums are then multiplied together to obtain the first product (1.0015 × 1.0015 × 1.0015 × 1.000997 × 1.00087 × 1.00063 × 0.99924 = 1.0141). Finally, the first product is subtracted from 1, and the result (1.0141 - 1 = 0.0141) is taken as the cumulative return of the bond fund over the 15th week.

[0106] In other embodiments, following the above, the determination of the annualized rate of return of the resource management product within the target historical period based on the cumulative rate of return can be achieved in the following way: the cumulative rate of return is added to a preset value (e.g., 1) to obtain a second addition result; using the second addition result as the base and the division result between the first quantity and the quantity of multiple historical natural days as the exponent, a power operation is performed to obtain a first power operation result, wherein the first quantity is the number of natural days included in a natural year (e.g., 365); the difference between the first power operation result and the preset value (e.g., 1) is taken as the annualized rate of return of the resource management product within the target historical period.

[0107] For example, continuing from the previous example, let's take the 15th week as the target historical period. Assume the cumulative return of a resource management product (e.g., a bond fund) in the 15th week is 0.0141. First, add the cumulative return of this bond fund in the 15th week to 1 to get the second sum (0.0141 + 1 = 1.0141). Then, using the second sum (1.0141) as the base and the result of dividing 365 by 7 (365 / 7 = 52.14) as the exponent, perform a power operation to obtain the first power operation result (1.0141). 52.14=2.075), and subtract 1 from the result of the first power operation, and take the result of the subtraction (i.e. 1.075) as the annualized yield of the bond fund over 15 weeks. In this way, the daily income of the trading day is split into the daily income of the natural day through the compound interest algorithm, and the 7-day annualized yield of the bond fund is calculated accordingly. Users can use this indicator (i.e., the 7-day annualized yield) to compare the income with that of money market funds, so as to facilitate users to choose different types of funds.

[0108] In step 103, the revenue details interface displays multiple secondary revenues corresponding to the resource management product over multiple historical natural days.

[0109] In some embodiments, the above-mentioned display of multiple second benefits corresponding to the resource management product in multiple historical natural days can be implemented in the following way: For each of the multiple historical natural days, the following processing is performed: when the second benefit of the resource management product in that historical natural day is positive, the second benefit of the resource management product in that historical natural day is displayed using a first display style; when the second benefit of the resource management product in that historical natural day is negative, the second benefit of the resource management product in that historical natural day is displayed using a second display style; wherein, the first display style is different from the second display style.

[0110] For example, taking a bond fund as a resource management product, when the target historical period corresponds to a weekly time dimension, that is, when a user selects to view the weekly return details from the weekly return list of the bond fund, for example, when the user clicks the button to view the details for a certain week (e.g., week 15), the return details interface for the bond fund in week 15 can be displayed. The return details interface can display the returns for the seven natural days included in week 15 (e.g., from April 7th to April 13th). For positive natural day returns, the return amount can be displayed in red; and for negative natural day returns, the return amount can be displayed in green. In this way, users can quickly and intuitively understand which natural days have positive returns and which natural days have negative returns.

[0111] It should be noted that when the target historical period mentioned above corresponds to a monthly time dimension, that is, when a user selects to view the monthly return details from the monthly return list of the bond fund, for example, when the user clicks the button to view the details for a certain month (e.g., the second month), the return details interface for the bond fund in the second month can be displayed. The return details interface can display the daily returns of the bond fund within the 28 calendar days of the second month (i.e., February 1st to February 28th). For positive daily returns, the daily return amount can be displayed in red; and for negative daily returns, the daily return amount can be displayed in green. In this way, users can quickly and intuitively understand which daily returns are positive and which are negative.

[0112] The following example, using a resource management product as a bond fund, illustrates an exemplary application of the embodiments of this application in a real-world application scenario.

[0113] Many users with low risk tolerance purchase bond funds. These users often have limited risk appetite and financial literacy. Therefore, investment platforms tend to provide more detailed explanations regarding returns. For example, a user might ask: "Are there returns on weekends and holidays?" The platform would explain: "Returns are generated on weekends and holidays, but they are not updated in the display. They will be shown together with the returns on the first day after the holiday." Furthermore, while bond funds are generally low-risk, market fluctuations can lead to negative returns on certain trading days. Because these users are sensitive to returns, emotional reactions can cause them to redeem their funds, resulting in losses for both the user and the investment platform.

[0114] In view of this, this application provides a method for processing resource management products. After obtaining the trading day income generated by the net asset value issued on the trading day by the institution, the wealth management platform uses a compound interest algorithm to split it into natural daily income, and then aggregates the natural daily income into weekly income, while calculating its 7-day annualized yield. That is, this application provides the 7-day annualized yield of bond funds, so the yield can be compared with that of money market funds. This can guide users from low-risk money market funds to medium-risk bond funds. At the same time, the weekly yield method reduces the sensitivity to short-term market fluctuations, allowing users to focus on long-term investment returns. It is a useful tool for wealth management platforms to guide users' investment growth, stabilize users' investment sentiment, and build trust between users and the wealth management platform.

[0115] In other words, the processing method of the resource management product provided in this application first generates daily returns from the net asset value issued by the fund company, then distributes the daily returns to each natural day through a compound interest algorithm, and finally aggregates the natural day returns into weekly returns. Therefore, the financial platform provides users with a new return dimension (i.e., weekly dimension). Weekly dimension returns have better return stability than daily dimension returns and can smooth out small fluctuations in daily returns. The probability of weekly returns being negative is also lower, thus providing users with a better profit experience.

[0116] The processing method of the resource management product provided in the embodiments of this application will be described in detail below.

[0117] In some embodiments, in addition to providing a daily return query option, the wealth management platform may also provide a weekly return query option. When a user selects the weekly return query option, a weekly return list can be displayed on the bond fund's return interface. This weekly return list may include multiple weekly returns for the bond fund over the past several weeks. Furthermore, for the current week in the weekly return list, this application embodiment provides the following two solutions:

[0118] Option 1): Do not display the current earnings, but only prompt the user that the earnings will be updated at 0:00 next Monday.

[0119] Option 2): Display the credited earnings and prompt the user that earnings are being updated. For example, if the credited earnings are 0.20 yuan, the following content can be displayed: 0.20, earnings are being updated.

[0120] For example, see Figure 6 , Figure 6 This is a schematic diagram illustrating an application scenario of the processing method of the resource management product provided in this application embodiment, such as... Figure 6As shown, in the bond fund's return interface 601, in addition to the tab control 602 displaying "Daily Returns" (i.e., providing a query option for daily returns), a tab control 603 displaying "Weekly Returns" (i.e., providing a query option for weekly returns) can also be displayed. When the "Weekly Returns" tab control 603 is selected, a list of weekly returns can be displayed in the return interface 601. This list can include multiple weekly returns corresponding to past weeks. Furthermore, for the current week in the weekly return list (e.g., week 16), the current return can be hidden, and the user can be prompted that the return will be updated after 00:00 next Monday. Additionally, if the user is interested in the weekly return of a particular week, they can further view the return details for that week. For example, assuming the user is interested in the weekly return of week 15 in the weekly return list, they can click the "View Details" button 604 corresponding to week 15. When a user clicks the "View Details" button 604 for week 15, the bond fund's return details interface 605 for week 15 is displayed. This interface shows the bond fund's 7-day annualized yield 606 for week 15, as well as the daily returns for each of the seven calendar days within week 15. In other words, users can view both the weekly return list to see the weekly return for a specific week and the daily return details for each calendar day within that week.

[0121] It should be noted that the above-mentioned income interface 601 can also display the cumulative income and weekly income of the bond fund. For example, the cumulative income of the bond fund can be displayed in the upper left corner of the income interface 601, and the weekly income of the bond fund can be displayed in the upper right corner of the income interface 601.

[0122] The following will continue to combine Figure 7 The processing method of the resource management product provided in the embodiments of this application will be described.

[0123] For example, see Figure 7 , Figure 7 This is a schematic diagram illustrating the principle of the processing method of the resource management product provided in the embodiments of this application, such as... Figure 7 As shown, each resource management product (such as a bond fund) held by a user can have a corresponding accumulated return record. This accumulated return record can include several key fields such as user identifier (ID, IDentity document), product ID, and accumulated return. Furthermore, each accumulated return record can be associated with multiple (e.g., N, where N is a positive integer greater than 1) daily return records. This means that the return amount from each daily return record is added to the accumulated return record. Each daily return record can include several key fields such as user ID, product ID, return date, and return amount. See also... Figure 7 In the technical solution provided in this application embodiment, the wealth management platform can also use a compound interest algorithm to split the product's daily transaction return into the product's daily return. For example, the wealth management platform can use a compound interest algorithm to split the return of a bond fund on Monday into Saturday and Sunday. The daily return can include multiple key fields such as user ID, product ID, return date, return amount, and daily yield. Finally, the wealth management platform can aggregate the daily returns of the product by week to obtain the weekly return. For example, the wealth management platform can aggregate the daily returns of 7 products into a weekly return. The weekly return can include multiple key fields such as user ID, product ID, return period, return amount, and 7-day annualized yield.

[0124] The following will continue to combine Figure 8 Explain the process of recording revenue on product transaction days.

[0125] For example, see Figure 8 , Figure 8 This is a schematic diagram of the fourth process of the resource management product processing method provided in the embodiments of this application, which will be combined with Figure 8 The steps shown are explained.

[0126] In step 201, the wealth management platform's scheduled task retrieves the product's net asset value on a daily basis.

[0127] In some embodiments, the scheduled tasks of the wealth management platform can obtain the latest net asset value per unit of resource management products (such as bond funds) from external sources (e.g., fund companies, data platforms, etc.).

[0128] In step 202, the wealth management platform's scheduled task sends a request to the platform's backend to update the product's net asset value.

[0129] In some embodiments, after obtaining the latest net asset value per unit of the bond fund, the scheduled task of the wealth management platform can send a request to the backend of the wealth management platform to update the product's net asset value. The request may include the latest net asset value per unit of the bond fund.

[0130] In step 203, the financial management platform updates the product's net asset value in its backend.

[0131] In some embodiments, after receiving a request from a scheduled task to update the net asset value (NAV) of a product, the backend of the wealth management platform can update the NAV of the product. For example, the backend of the wealth management platform can update the NAV of a bond fund to the latest NAV carried in the request.

[0132] In step 204, the financial management platform's backend calculates the daily transaction income.

[0133] In some embodiments, after receiving the latest unit net asset value sent by a scheduled task, the backend of the wealth management platform can update the product's net asset value and calculate the bond fund's return for the current trading day. The trading day return can be calculated using the following formula:

[0134] Daily profit = Number of shares held * (Latest net asset value per unit - Net asset value per unit of the previous trading day)

[0135] In step 205, the backend of the wealth management platform returns the daily earnings to the platform's scheduled task.

[0136] In some embodiments, the backend of the wealth management platform can write the calculated daily transaction income into the product's daily transaction income table, and can also add the product's daily transaction income to the product's cumulative income.

[0137] The following will continue to combine Figure 9 Explain the process of recording daily revenue for the product.

[0138] For example, see Figure 9 , Figure 9 This is a schematic diagram of the fifth process of the resource management product processing method provided in this application embodiment, which will be combined with... Figure 9 The steps shown are explained.

[0139] In step 301, the scheduled task of the wealth management platform sends a daily earnings query request to the backend of the wealth management platform.

[0140] In some embodiments, the scheduled tasks of the wealth management platform can query the daily returns to be split in the backend of the wealth management platform, such as the returns of a bond fund on Monday.

[0141] In step 302, the wealth management platform's scheduled task breaks down the daily transaction income into daily income.

[0142] In some embodiments, the scheduled tasks of a wealth management platform can use a compound interest algorithm to split the daily return of a transaction into daily returns. The specific process is as follows: Assuming the daily return is P and the principal generating the return is M, then the total rate of return (let's call it R) = P / M. Next, we can obtain the number of days between the current transaction day (i.e., the transaction day to be split) and the previous transaction day (let's call it n). Then, the daily rate of return (let's call it r) = (1 + R). 1 / n -1, the daily profit on the m-th day (let's call it p) = M*(1+r) m-M, where m is an integer variable satisfying 1≤m≤N, and N is the total number of rest days. Furthermore, to ensure that the cumulative daily returns equal the trading day returns, the calculation of the last day's returns can use subtraction, i.e., the trading day returns minus the cumulative returns of the preceding daily days to obtain the last day's returns. For example, taking Monday as the trading day to be split, this embodiment of the application can use the above-mentioned compound interest algorithm to split the bond fund's returns on Monday into Saturday, Sunday, and Monday. For example, assuming the bond fund's returns on Monday are 5 yuan, and assuming that after calculation using the above compound interest algorithm, the bond fund's returns on Saturday are 1 yuan and on Sunday are 2 yuan, then the final returns of the bond fund on Monday are 5 - (1 + 2) = 2 yuan. In this way, the trading day returns can be split into multiple daily days.

[0143] In step 303, the scheduled task of the wealth management platform sends a request to the backend of the wealth management platform to insert daily income.

[0144] In some embodiments, after the scheduled task of the wealth management platform splits the transaction day income to be split into natural day income, it can send a request to the backend of the wealth management platform to insert natural day income. The request may carry the natural day income obtained by the scheduled task for splitting the transaction day income to be split.

[0145] In step 304, the daily earnings are inserted into the backend of the wealth management platform.

[0146] In some embodiments, after receiving a request from a scheduled task to insert daily earnings, the backend of the wealth management platform can write the daily earnings into the product's daily earnings table.

[0147] In step 305, the backend of the wealth management platform returns the insertion result to the scheduled task of the wealth management platform.

[0148] In some embodiments, after the backend of the wealth management platform writes the daily returns into the product's daily returns table, it can return the insertion result to the scheduled task of the wealth management platform to inform the scheduled task that the daily returns have been written into the product's daily returns table.

[0149] The following will continue to combine Figure 10 Explain the process of recording weekly product revenue.

[0150] For example, see Figure 10 , Figure 10 This is a schematic diagram of the sixth process of the resource management product processing method provided in the embodiments of this application, which will be combined with Figure 10 The steps shown are explained.

[0151] In step 401, the scheduled task of the wealth management platform sends a daily return query request to the backend of the wealth management platform.

[0152] In some embodiments, the scheduled tasks of the wealth management platform can query the pending daily earnings in the backend of the wealth management platform. For example, the scheduled task can send a daily earnings query request to the backend of the wealth management platform, and the request can carry the date of the daily earnings corresponding to the pending daily earnings.

[0153] In step 402, the financial management platform's scheduled task determines the week to which the natural day belongs.

[0154] In some embodiments, after the scheduled task of the wealth management platform finds the daily income to be processed in the background of the wealth management platform, it can determine the week to which the daily income belongs. For example, for the 15th week of XXXX, the corresponding dates are April 7, XXXX to April 13, XXXX.

[0155] In step 403, the wealth management platform's scheduled task sends a request to the platform's backend to add daily earnings.

[0156] In some embodiments, after determining the week to which a natural day belongs, the scheduled task of the wealth management platform can send a request to the backend of the wealth management platform to add the natural day's earnings. The request may include the week to which the natural day belongs.

[0157] In step 404, the backend of the wealth management platform adds the daily earnings to the weekly earnings of the corresponding week.

[0158] In some embodiments, after receiving a request from the wealth management platform's scheduled task, the platform's backend can add the daily earnings to the weekly earnings of the corresponding week.

[0159] In step 405, the backend of the wealth management platform determines whether the weekly earnings have been earned for all days of the week. If yes, proceed to step 406; otherwise, proceed to step 407.

[0160] In step 406, the backend of the wealth management platform sets the status of the weekly earnings to "accounted for" and calculates the 7-day annualized yield of the product, and records the 7-day annualized yield in the product's weekly earnings table.

[0161] In step 407, the backend of the wealth management platform sets the status of the weekly earnings to "in progress".

[0162] In some embodiments, the backend of the wealth management platform can determine the status of weekly earnings. If the weekly earnings have been earned for all days of the week, the status is set to "accounted for"; otherwise, the status is set to "accounting for". Furthermore, if the status is "Accounts credited," the financial platform's backend can also calculate the 7-day annualized yield of the bond fund for this week. The specific process is as follows: First, look up the daily yields for each day of the week from the calendar, denoted as r1, r2, r3, r4, r5, r6, and r7, where r1 is the daily yield for Monday, r2 is for Tuesday, r3 is for Wednesday, r4 is for Thursday, r5 is for Friday, r6 is for Saturday, and r7 is for Sunday. Next, calculate the cumulative yield for 7 days (denoted as T) = (1+r1)×(1+r2)×(1+r3)×(1+r4)×(1+r5)×(1+r6)×(1+r7)-1. Finally, calculate the 7-day annualized yield of the bond fund (denoted as S) = (1+T). 365 / 7 -1. After calculating the 7-day annualized yield of the bond fund, the wealth management platform's backend can record the 7-day annualized yield in the product's weekly yield table.

[0163] The following will continue to combine Figure 11 The process of users querying product weekly earnings is explained.

[0164] For example, see Figure 11 , Figure 11 This is a schematic diagram of the seventh process of the resource management product processing method provided in the embodiments of this application, which will be combined with Figure 11 The steps shown are explained.

[0165] In step 501, the front end sends a weekly earnings list query request to the wealth management platform.

[0166] In some embodiments, the human-computer interaction interface provided by the front end (e.g., a financial management APP) may display a query option for the weekly returns of bond funds. When the front end receives the user's selection of the query option for weekly returns, it may send a weekly return list query request to the financial management platform. The request may include the product identifier of the bond fund, such as the bond fund's number.

[0167] In step 502, the wealth management platform queries the list of weekly product returns.

[0168] In some embodiments, after receiving a weekly return list query request from the front end, the wealth management platform can first parse the bond fund number carried in the request, and then query the weekly return list of the bond fund based on the number.

[0169] In step 503, the wealth management platform returns a list of weekly returns to the front end.

[0170] In some embodiments, after the financial management platform retrieves the weekly return list of the corresponding bond fund based on the number carried in the request, it can return the retrieved weekly return list to the front end for display.

[0171] The following will continue to combine Figure 12 The process of users querying product weekly revenue details is explained.

[0172] For example, see Figure 12 , Figure 12 This is the eighth flowchart of the processing method of the resource management product provided in the embodiments of this application, which will be combined with Figure 12 The steps shown are explained.

[0173] In step 601, the front end sends a request to the wealth management platform to query weekly earnings details.

[0174] In some embodiments, when a user selects the option to query weekly returns, a list of weekly returns for bond funds can be displayed on the front-end interface. This list can include multiple weekly returns for each bond fund over the past few weeks. When a user is interested in the weekly return of a particular week, they can further view the details of that week's returns. For example, upon receiving a click from a user on the "View Details" button for that week (e.g., week 15), the front-end can send a weekly return details query request to the financial platform. This request may include the week number corresponding to the clicked "View Details" button.

[0175] In step 602, the wealth management platform queries the product's weekly return table.

[0176] In some embodiments, after receiving a weekly return details query request sent by the front end, the wealth management platform can first parse the week number carried in the request, and then query the product's weekly return table based on the number to obtain the 7-day annualized yield of the bond fund in the week corresponding to that number (e.g., week 15).

[0177] In step 603, the wealth management platform queries the product's daily return table.

[0178] In some embodiments, after receiving a weekly return details query request sent by the front end, the wealth management platform can also query the product's daily return table based on the week number carried in the request, and obtain the 7 daily returns of the bond fund within the 7 natural days of the week corresponding to that number (i.e., week 15).

[0179] In step 604, the wealth management platform returns weekly earnings details to the front end.

[0180] In some embodiments, after querying the product's weekly return table and daily return table to obtain the weekly return details, the wealth management platform can return the retrieved weekly return details to the front end so that the front end can display the weekly return details returned by the wealth management platform. The weekly return details include the 7-day annualized yield of the bond fund in that week, as well as the 7 daily returns corresponding to the 7 natural days included in that week.

[0181] In summary, the processing method of the resource management product provided in this application has the following beneficial effects:

[0182] 1) Reduce risk perception: This application embodiment uses a weekly return method, which allows users to reduce their sensitivity to short-term market fluctuations and see long-term investment returns;

[0183] 2) Reasonable return comparison: By allocating the transaction day's returns to the weekly returns of each natural day, the embodiments of this application can better compare the returns of different resource management products (such as bond funds and money market funds);

[0184] 3) Enhance the attractiveness of the wealth management platform: In addition to daily returns, the wealth management platform has added a weekly return function, which can guide users to view investment returns from a long-term perspective, thus enhancing the platform's attractiveness to users.

[0185] The following description continues to illustrate the exemplary structure of the processing device 555 for the resource management product provided in this application embodiment as a software module. In some embodiments, such as... Figure 2 As shown, the software module in the processing device 555 of the resource management product stored in the memory 550 may include: a display module 5551.

[0186] Display module 5551 is used to display a first revenue list of the resource management product, wherein the first revenue list includes multiple first revenues corresponding to the resource management product in multiple historical periods; display module 5551 is also used to display a revenue details interface of the resource management product in the target historical period in response to a selection operation for a target historical period, wherein the target historical period includes multiple historical natural days; display module 5551 is also used to display multiple second revenues corresponding to the resource management product in the multiple historical natural days in the revenue details interface.

[0187] In some embodiments, the display module 5551 is further configured to display a revenue interface for the resource management product in response to a revenue viewing operation for the resource management product, wherein the revenue interface includes multiple tab controls, and different tab controls correspond to different time dimensions; in response to the selection of the first tab control among the multiple tab controls, a first revenue list for the resource management product is displayed in the revenue interface, wherein the first revenue list includes the first revenue obtained by aggregating multiple second revenues corresponding to the resource management product in multiple historical natural days based on the time dimension corresponding to the first tab control.

[0188] In some embodiments, after displaying the revenue interface of the resource management product, the display module 5551 is further configured to perform the following processing: in response to the selection of a second tab control among a plurality of tab controls, displaying a second revenue list of the resource management product in the revenue interface, wherein the second revenue list includes a plurality of second revenues corresponding to the resource management product in a plurality of historical natural days.

[0189] In some embodiments, the display module 5551 is further configured to display at least one resource management product held by the target object; in response to a selection operation for at least one resource management product, display a details interface of the selected resource management product, wherein the details interface includes a revenue viewing control; and in response to a trigger operation for the revenue viewing control, display a revenue interface of the selected resource management product.

[0190] In some embodiments, after displaying the revenue interface of the resource management product, the display module 5551 is further configured to display at least one of the following in the revenue interface: the cumulative revenue of the resource management product, and the first revenue of the resource management product in the previous historical period, wherein the cumulative revenue is obtained by summing up the multiple third revenues corresponding to the resource management product in multiple historical trading days.

[0191] In some embodiments, the first revenue list may further include the current period and a first notification message corresponding to the current period, wherein the first notification message is used to indicate that the first revenue of the resource management product in the current period will be updated after the current period ends; or, the first revenue list may further include the current period, the revenue already credited to the resource management product in the current period, and a second notification message, wherein the second notification message is used to indicate that the first revenue of the resource management product in the current period is being updated.

[0192] In some embodiments, after displaying the revenue details interface of the resource management product within the target historical period, the display module 5551 is further configured to display the annualized rate of return of the resource management product within the target historical period in the revenue details interface, wherein the annualized rate of return is determined based on the cumulative rate of return of the resource management product within the target historical period.

[0193] In some embodiments, the processing device 555 for the resource management product further includes an acquisition module 5552 and a determination module 5553. Before the display module 5551 displays the annualized rate of return of the resource management product within the target historical period in the return details interface, the acquisition module 5552 is used to acquire multiple daily rates of return corresponding to multiple historical natural days for the resource management product; the determination module 5553 is used to determine the cumulative rate of return of the resource management product within the target historical period based on the multiple daily rates of return; and to determine the annualized rate of return of the resource management product within the target historical period based on the cumulative rate of return.

[0194] In some embodiments, the determining module 5553 is further configured to add multiple daily rates of return to preset values ​​respectively to obtain multiple first summation results; multiply the multiple first summation results to obtain a first multiplication result; and use the difference between the first multiplication result and the preset value as the cumulative rate of return of the resource management product in the target historical period.

[0195] In some embodiments, the determining module 5553 is further configured to add the cumulative rate of return to a preset value to obtain a second addition result; use the second addition result as the base and the result of dividing the first quantity by the quantity of multiple historical natural days as the exponent to perform a power operation to obtain a first power operation result, wherein the first quantity is the quantity of natural days included in a natural year; and use the difference between the first power operation result and the preset value as the annualized rate of return of the resource management product in the target historical period.

[0196] In some embodiments, the determining module 5553 is further configured to perform the following processing for each of the plurality of historical natural days: when the historical natural day is a historical rest day, determine the daily yield of the historical rest day based on the daily yield of the historical trading day that is after the historical rest day and closest to the historical rest day; when the historical natural day is a historical trading day and the day before the historical trading day is a historical rest day, use the split result of the daily yield of the historical trading day as the daily yield of the historical trading day; when the historical natural day is a historical trading day and the day before the historical trading day is also a historical trading day, obtain the daily yield of the resource management product on the historical trading day, and use the result of dividing the daily yield by the total amount of the resource management product on the previous historical trading day as the daily yield of the historical trading day.

[0197] In some embodiments, the acquisition module 5552 is further configured to acquire the daily return rate of the historical trading day that is after the historical rest day and closest to the historical rest day; the determination module 5553 is further configured to add the daily return rate to a preset value to obtain a third summing result; using the third summing result as the base and the result of dividing the preset value by a second quantity as the exponent, a power operation is performed to obtain a second power operation result, wherein the second quantity is the number of days between the first historical trading day and the second historical trading day, the first historical trading day is the historical trading day that is after the historical rest day and closest to the historical rest day, and the second historical trading day is the historical trading day that is before the historical rest day and closest to the historical rest day; the difference between the second power operation result and the preset value is used as the daily return rate of the historical rest day.

[0198] In some embodiments, before displaying the first revenue list of the resource management product, the determination module 5553 is further configured to perform the following processing for each historical period included in the first revenue list, wherein the historical period includes multiple historical natural days: obtaining multiple second revenues corresponding to the resource management product in the multiple historical natural days; adding the multiple second revenues together, and using the sum as the first revenue of the resource management product in the historical period.

[0199] In some embodiments, the determining module 5553 is further configured to perform the following processing for each of a plurality of historical natural days: when the historical natural day is a historical rest day, determine the second return of the resource management product on the historical rest day based on the daily return rate of the historical rest day; when the historical natural day is a historical trading day and the day before the historical trading day is a historical rest day, determine the second return of the resource management product on the historical trading day based on the return of the resource management product on the historical trading day and the cumulative return of the resource management product over a plurality of historical rest days; when the historical natural day is a historical trading day and the day before the historical trading day is also a historical trading day, determine the difference between the unit net value of the resource management product on the historical trading day and the unit net value of the previous historical trading day, and multiply the difference by the holding shares of the resource management product as the second return of the resource management product on the historical trading day.

[0200] In some embodiments, the determining module 5553 is further configured to add the daily rate of return of historical rest days to a preset value to obtain a fourth summing result; use the fourth summing result as the base and a third quantity as the exponent to perform a power operation to obtain a third power operation result, wherein the third quantity is the number of days between the historical rest day and the second historical trading day, and the second historical trading day is the historical trading day that is before the historical rest day and closest to the historical rest day; multiply the third power operation result by the total amount of the resource management product on the second historical trading day to obtain a second multiplication result; and use the difference between the second multiplication result and the total amount as the second return of the resource management product on the historical rest day.

[0201] In some embodiments, the determining module 5553 is further configured to sum up the multiple revenues of the resource management product corresponding to multiple historical rest days to obtain the cumulative revenue of the resource management product on multiple historical rest days, wherein the multiple historical rest days are located between the historical trading day and the previous historical trading day; subtract the revenue of the resource management product on the historical trading day from the cumulative revenue, and use the result of the subtraction as the second revenue of the resource management product on the historical trading day.

[0202] In some embodiments, the display module 5551 is further configured to perform the following processing for each of a plurality of historical natural days: when the second revenue of the resource management product within the historical natural day is positive, display the second revenue of the resource management product within the historical natural day using a first display style; when the second revenue of the resource management product within the historical natural day is negative, display the second revenue of the resource management product within the historical natural day using a second display style; wherein the first display style is different from the second display style.

[0203] In some embodiments, the first revenue list further includes multiple detail viewing controls corresponding to multiple historical periods; the display module 5551 is also used to display the revenue details interface of the resource management product within the target historical period in response to the trigger operation of the detail viewing control corresponding to the target historical period, wherein the target historical period is the selected historical period among multiple historical periods.

[0204] In some embodiments, multiple historical periods are arranged in the first revenue list by default in the order of late to early time, and the first revenue list also includes a switching control; after displaying the first revenue list of the resource management product, the display module 5551 is further configured to respond to the trigger operation of the switching control, and sequentially display multiple first revenues corresponding to the resource management product in multiple historical periods in the first revenue list in the order after switching, wherein the order after switching includes one of the following: revenue from high to low, revenue from low to high.

[0205] In some embodiments, the display module 5551 is further configured to display the timeline of the resource management product; the acquisition module 5552 is further configured to acquire multiple historical periods within the selected historical time period in response to a time period selection operation based on the timeline; the display module 5551 is further configured to display a first revenue list of the resource management product, wherein the first revenue list includes multiple first revenues corresponding to the resource management product in the multiple historical periods.

[0206] It should be noted that the description of the apparatus in this application embodiment is similar to the description of the method embodiment above, and has similar beneficial effects as the method embodiment, therefore it will not be repeated. For any technical details not covered in the processing apparatus of the resource management product provided in this application embodiment, please refer to... Figure 3 , Figure 4 ,or Figure 5 The meaning is understood in accordance with the description of any of the accompanying drawings.

[0207] This application provides a computer program product comprising a computer program or computer-executable instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer-executable instructions from the computer-readable storage medium and executes the computer-executable instructions, causing the computer device to perform the processing method of the resource management product described above in this application.

[0208] This application provides a computer-readable storage medium storing computer-executable instructions. When these computer-executable instructions are executed by a processor, they cause the processor to perform a processing method of the resource management product provided in this application. For example, ... Figure 3 , Figure 4 ,or Figure 5 The processing method of the resource management product is shown.

[0209] In some embodiments, the computer-readable storage medium may be a memory such as FRAM, ROM, PROM, EPROM, EEPROM, flash memory, magnetic surface memory, optical disk, or CD-ROM; or it may be a variety of devices including one or any combination of the above-mentioned memories.

[0210] In some embodiments, executable instructions may take the form of a program, software, software module, script, or code, written in any form of programming language (including compiled or interpreted languages, or declarative or procedural languages), and may be deployed in any form, including as a standalone program or as a module, component, subroutine, or other unit suitable for use in a computing environment.

[0211] As an example, executable instructions can be deployed to execute on a single electronic device, or on multiple electronic devices located in one location, or on multiple electronic devices distributed across multiple locations and interconnected via a communication network.

[0212] The above description is merely an embodiment of this application and is not intended to limit the scope of protection of this application. Any modifications, equivalent substitutions, and improvements made within the spirit and scope of this application are included within the scope of protection of this application.

Claims

1. A method for processing resource management products, characterized in that, The method includes: Display the first revenue list of the resource management product, wherein the first revenue list includes multiple first revenues corresponding to the resource management product in multiple historical periods; In response to the selection operation for a target historical period, the revenue details interface of the resource management product within the target historical period is displayed, wherein the target historical period includes multiple historical calendar days; The revenue details interface displays multiple secondary revenues corresponding to the resource management product within the multiple historical natural days.

2. The method according to claim 1, characterized in that, The first revenue list of the display resource management product includes: In response to an operation to view the revenue of a resource management product, the revenue interface of the resource management product is displayed. The revenue interface includes multiple tab controls, and different tab controls correspond to different time dimensions. In response to the selection of the first tab control among the plurality of tab controls, a first revenue list of the resource management product is displayed in the revenue interface. The first revenue list includes a first revenue that is obtained by aggregating multiple second revenues corresponding to the resource management product in multiple historical natural days based on the time dimension corresponding to the first tab control.

3. The method according to claim 2, characterized in that, After displaying the revenue interface of the resource management product, the method further includes: In response to the selection of the second tab control among the plurality of tab controls, a second revenue list of the resource management product is displayed in the revenue interface, wherein the second revenue list includes a plurality of second revenues corresponding to the resource management product in a plurality of historical natural days.

4. The method according to claim 2, characterized in that, The response to the operation of viewing the revenue of the resource management product, displaying the revenue interface of the resource management product, includes: Display at least one resource management product held by the target entity; In response to a selection operation for the at least one resource management product, a details interface for the selected resource management product is displayed, wherein the details interface includes a revenue viewing control; In response to a triggered operation on the revenue viewing control, the revenue interface of the selected resource management product is displayed.

5. The method according to claim 2, characterized in that, After displaying the revenue interface of the resource management product, the method further includes: The earnings interface displays at least one of the following: the cumulative earnings of the resource management product, and the first earnings of the resource management product in the previous historical period. The cumulative earnings are obtained by summing up the third earnings of the resource management product in multiple historical trading days.

6. The method according to claim 1, characterized in that, The first revenue list also includes the current period and a first notification message corresponding to the current period, wherein the first notification message is used to indicate that the first revenue of the resource management product in the current period will be updated after the current period ends; or, the first revenue list also includes the current period, the revenue already credited to the resource management product in the current period, and a second notification message, wherein the second notification message is used to indicate that the first revenue of the resource management product in the current period is being updated.

7. The method according to claim 1, characterized in that, After displaying the revenue details of the resource management product within the target historical period on the interface, the method further includes: The revenue details interface displays the annualized rate of return of the resource management product within the target historical period, wherein the annualized rate of return is determined based on the cumulative rate of return of the resource management product within the target historical period.

8. The method according to claim 7, characterized in that, In the revenue details interface, before displaying the annualized rate of return of the resource management product within the target historical period, the method further includes: The resource management product is obtained as a plurality of daily yields within the plurality of historical natural days, wherein the plurality of historical natural days include historical rest days and historical trading days, and the daily yield of the historical rest days is obtained by splitting the daily yield of the first historical trading day, wherein the first historical trading day is the historical trading day that is after the historical rest day and closest to the historical rest day among the plurality of historical trading days; The cumulative return rate is calculated based on the multiple daily returns to obtain the cumulative return rate of the resource management product within the target historical period; The annualized rate of return is calculated based on the cumulative rate of return, the number of the plurality of historical natural days, and the first quantity to obtain the annualized rate of return of the resource management product within the target historical period, wherein the first quantity is the number of natural days included in a natural year.

9. The method according to claim 1, characterized in that, Before displaying the first revenue list of the resource management product, the method further includes: For each historical period included in the first revenue list, the following processing is performed, wherein the historical period includes multiple historical calendar days: Obtain multiple second benefits corresponding to the resource management product within the multiple historical natural days; The multiple second benefits are summed together, and the sum is taken as the first benefit of the resource management product in the historical period.

10. The method according to claim 9, characterized in that, The acquisition of multiple second benefits corresponding to the resource management product within the multiple historical natural days includes: For each of the plurality of historical natural days, perform the following processing: When the historical natural day is a historical rest day, the daily return is calculated based on the daily rate of return of the historical rest day, the third quantity, and the total amount of the resource management product on the second historical trading day to obtain the second return of the resource management product on the historical rest day. The third quantity is the number of days between the historical rest day and the second historical trading day, and the second historical trading day is the historical trading day that is before the historical rest day and is closest to the historical rest day. When the historical calendar day is a historical transaction day and the day before the historical transaction day is a historical rest day, the multiple revenues of the resource management product corresponding to the multiple historical rest days are accumulated to obtain the cumulative revenue of the resource management product on the multiple historical rest days, wherein the multiple historical rest days are located between the historical transaction day and the previous historical transaction day; the revenue of the resource management product on the historical transaction day is subtracted from the cumulative revenue, and the result of the subtraction is taken as the second revenue of the resource management product on the historical transaction day; When the historical calendar day is a historical trading day and the day before the historical trading day is also a historical trading day, the difference between the unit net value of the resource management product on the historical trading day and the unit net value on the previous historical trading day is determined, and the result of multiplying the difference by the holding shares of the resource management product is taken as the second income of the resource management product on the historical trading day.

11. The method according to any one of claims 1 to 10, characterized in that, The display shows the multiple second benefits corresponding to the resource management product within the multiple historical natural days, including: For each of the plurality of historical natural days, perform the following processing: When the second revenue of the resource management product is positive within the historical natural day, the second revenue of the resource management product within the historical natural day is displayed using the first display style. When the second revenue of the resource management product within the historical natural day is negative, the second revenue of the resource management product within the historical natural day is displayed using the second display style. The first display style is different from the second display style.

12. The method according to any one of claims 1 to 10, characterized in that, The first revenue list also includes multiple detail viewing controls corresponding to the multiple historical periods; In response to a selection operation for a target historical period, the resource management product's revenue details interface for that target historical period is displayed, including: In response to the triggering operation of the details viewing control corresponding to the target historical period, the revenue details interface of the resource management product within the target historical period is displayed, wherein the target historical period is the selected historical period among the plurality of historical periods.

13. The method according to any one of claims 1 to 10, characterized in that, The multiple historical periods are arranged in the first revenue list in ascending order of time by default, and the first revenue list also includes a switching control; Following the first revenue list of the displayed resource management product, the method further includes: In response to the trigger operation of the switching control, the resource management product is displayed in the first revenue list in the order after the switch, and the order after the switch includes one of the following: revenue from high to low, revenue from low to high.

14. The method according to any one of claims 1 to 10, characterized in that, The first revenue list of the display resource management product includes: Displays the timeline of resource management products; In response to a time period selection operation based on the time axis, multiple historical periods located within the selected historical time period are obtained; Display the first revenue list of the resource management product, wherein the first revenue list includes multiple first revenues corresponding to the resource management product in the multiple historical periods.

15. A processing device for a resource management product, characterized in that, The device includes: The display module is used to display a first revenue list of the resource management product, wherein the first revenue list includes multiple first revenues corresponding to the resource management product in multiple historical periods. The display module is also configured to, in response to a selection operation for a target historical period, display a revenue details interface of the resource management product within the target historical period, wherein the target historical period includes multiple historical natural days; The display module is also used to display, in the revenue details interface, multiple second revenues corresponding to the resource management product within the multiple historical natural days.

16. An electronic device, characterized in that, include: Memory is used to store executable instructions for a computer; A processor, when executing computer-executable instructions stored in the memory, implements the processing method of the resource management product according to any one of claims 1 to 14.

17. A computer-readable storage medium storing computer-executable instructions, characterized in that, When the computer-executable instructions are executed by the processor, they implement the processing method of the resource management product according to any one of claims 1 to 14.

18. A computer program product comprising a computer program or computer-executable instructions, characterized in that, When the computer program or computer-executable instructions are executed by the processor, they implement the processing method of the resource management product according to any one of claims 1 to 14.

Images