Account information processing method and device, electronic equipment and readable storage medium

Abstract

The invention provides an account information processing method and device, electronic equipment and a readable storage medium, and the method comprises the steps: obtaining and displaying the selectable data of a user based on the authority of the user, responding to the selection creation operation of the user for a target combination and / or a target entity unit in a plan, generating a virtual plan, and displaying the virtual plan. And determining and displaying the valuation information of the virtual plan according to the valuation information of each entity unit in the virtual plan. According to the method, the account data is extracted and analyzed accurately at one time by responding to the selection of the user on any selected entity unit or combination within the permission range and analyzing the data, so that the user requirement is met, the system loading frequency is reduced, and the response speed and the use experience are improved.

Description

Technical Field

[0001] The present application relates to the technical field of account information processing. Specifically, it relates to a method, device, electronic device, and readable storage medium for processing account information. Background Art

[0002] With the continuous development of computer technology, it is possible to intelligently manage and analyze investment-related data with the help of investment analysis-related systems. The analysis dimensions of data are no longer limited to the time-series analysis of a single plan or portfolio, or the horizontal comparison of a combination of a set of fixed conditions. There is a great demand for flexibly analyzing accounts across hierarchies, plans, types, and custom account sets.

[0003] Currently, investment analysis-related systems mainly provide two account selection modes. One is a single account, that is, one investment account is selected at a time for display, which is mostly used for the time-series analysis of indicators. The other is multiple accounts with specified conditions, that is, it supports displaying all investment accounts that meet a certain same attribute at one time for analysis, such as all investment portfolios under the same plan, all products included under the same product type, etc.

[0004] However, this relatively fixed selection condition cannot quickly meet the diverse analysis query and data extraction needs of business users. When complex selection dimensions appear, it will cause serious waste of system resources and processing time. Such a system does not support creating personalized account dimensions and real-time analysis. For example, for custom development corresponding to query dimensions, not only a large amount of man-hours of technical personnel such as requirements, design, front-end, back-end, and testing are required, but also a long time period from development to online is needed, and the actual needs of users cannot be met in a timely manner. Summary of the Invention

[0005] The purpose of the present application is to provide a method, device, electronic device, and readable storage medium for processing account information to solve the problems in the prior art that the diverse analysis query needs of business users cannot be met and the development time period is long.

[0006] To achieve the above purpose, the technical solution adopted in the present application is as follows:

[0007] In a first aspect, the present application provides a method for processing account information, and the method includes:

[0008] Based on the user's permissions, obtain and display the selectable data of the user. The selectable data includes at least one combination in a plan, each combination includes at least one entity unit, and each entity unit has corresponding attribute information, and the attribute information is used to indicate the category to which the entity unit belongs;

[0009] Generate a virtual plan in response to an operation created by the user's selection of a target portfolio and / or a target entity unit in the plan. The account includes at least one virtual portfolio and / or at least one entity portfolio and / or at least one entity unit;

[0010] Determine and display the valuation information of the virtual plan according to the valuation information of each entity unit in the virtual plan.

[0011] Optionally, based on the user's permissions, obtain and display the selectable data of the user, including:

[0012] Obtain all initial selection data;

[0013] Filter the initial selection data based on the user's permissions to determine the selectable data of the user.

[0014] Optionally, the filtering of the initial selection data based on the user's permissions to determine the selectable data of the user includes:

[0015] Traverse each initial selection data. For the currently traversed initial selection data, determine whether the user has the permission for the current initial selection data. If so, use the current initial selection data as the selectable data of the user.

[0016] Optionally, the generating of a virtual plan in response to an operation created by the user's selection of a target portfolio and / or a target entity unit in the plan includes:

[0017] Combine each target entity unit selected by the user into a virtual portfolio;

[0018] Respectively use each target portfolio selected by the user as a virtual portfolio;

[0019] Generate the virtual plan according to each virtual portfolio. Optionally, the virtual plan is presented in the form of a hierarchical data table. The hierarchical data table includes multiple layers of data corresponding one by one to the levels of the virtual plan. Each layer of data includes an account opening date, an account closing date, and detailed data;

[0020] The determining and displaying of the valuation information of the virtual plan according to the valuation information of each entity unit in the virtual plan includes:

[0021] Filter at least one target detailed data from the hierarchical data table according to the date range selected by the user and the account opening date and the account closing date of each layer of data in the hierarchical data table;

[0022] Determine and display the valuation information of the virtual plan according to the valuation information corresponding to the at least one target detailed data.

[0023] Optionally, determining and displaying the valuation information of the virtual plan according to the valuation information corresponding to the at least one target detail data includes:

[0024] Combining the valuation information of each target detail data to obtain and display the valuation information of the virtual plan.

[0025] Optionally, before obtaining and displaying the entity plan selected by the user based on the user's permissions, it further includes:

[0026] Responding to the user's login operation, and obtaining the user's permissions according to the user's account information.

[0027] In a second aspect, the present application provides an account information processing device, and the device includes:

[0028] An acquisition module, configured to acquire and display selectable data of the user based on the user's permissions, where the selectable data includes at least one combination in the plan, each combination includes at least one entity unit, and each entity unit has corresponding attribute information, and the attribute information is used to indicate the category to which the entity unit belongs;

[0029] A generation module, configured to generate a virtual plan in response to a user's selection and creation operation for a target combination and / or a target entity unit in the plan, where the account includes at least one virtual combination and / or at least one entity combination and / or at least one entity unit;

[0030] A determination module, configured to determine and display the valuation information of the virtual plan according to the valuation information of each entity unit in the virtual plan.

[0031] Optionally, the acquisition module is specifically configured to:

[0032] Acquire all initial selection data;

[0033] Filter the initial selection data based on the user's permissions to determine the selectable data of the user.

[0034] Optionally, the acquisition module is specifically configured to:

[0035] Traverse each initial selection data, and for the currently traversed initial selection data, determine whether the user has the permission for the current initial selection data. If so, use the current initial selection data as the selectable data of the user.

[0036] Optionally, the generation module is specifically configured to:

[0037] Combine each target entity unit selected by the user into a virtual combination;

[0038] Respectively take each selected target combination by the user as a virtual combination;

[0039] Generate the virtual plan according to each virtual combination.

[0040] Optionally, the virtual plan is presented in the form of a hierarchical data table, and the hierarchical data table includes multiple layers of data corresponding one by one to the levels of the virtual plan. Each layer of data respectively includes an account opening date, an account closing date, and detailed data;

[0041] Optionally, the determining module is specifically configured to:

[0042] According to the selected date range by the user, the account opening date, and the account closing date of each layer of data in the hierarchical data table, screen at least one target detailed data from the hierarchical data table;

[0043] Determine and display the valuation information of the virtual plan according to the valuation information corresponding to the at least one target detailed data.

[0044] Optionally, the determining module is specifically configured to:

[0045] Combine the valuation information of each target detailed data to obtain and display the valuation information of the virtual plan.

[0046] Optionally, the obtaining module is further configured to:

[0047] In response to the user's login operation, obtain the user's permissions according to the user's account information.

[0048] In a third aspect, the present application provides an electronic device, including: a processor, a memory, and a bus. The memory stores machine-readable instructions executable by the processor. When the electronic device runs, the processor communicates with the memory through the bus. The processor executes the machine-readable instructions to perform the steps of the account information processing method as described above.

[0049] In a fourth aspect, the present application provides a computer-readable storage medium, on which a computer program is stored. When the computer program is run by a processor, it performs the steps of the account information processing method as described above.

[0050] The beneficial effects of this application are as follows: First, based on the user's permissions, the selected data chosen by the user is obtained and displayed. Then, in response to the user's selection operation on at least one target combination and / or at least one target entity unit in the plan, a virtual plan is generated. Thus, in addition to entity plans and combinations, virtual combinations and virtual plans are also supported, and the user is provided with cross-level selection of plans and combinations, breaking the rigid analysis framework. Then, according to the valuation information of each entity unit in the virtual plan, the valuation information of the virtual plan is determined and displayed, thereby giving the virtual plan the same status as the entity plan and realizing the same analysis function as the entity plan. And it can accurately analyze and extract data such as the valuation information of each entity unit and combination at one time, avoiding resource waste caused by multiple operations and redundant data queries, reducing the number of system loads, loading time consumption, and resource occupancy, thereby effectively improving the response speed and user experience. In this embodiment, by applying the account information processing method in the server, the valuation data can be obtained in real time according to the status of the entity unit and the user's needs, reducing labor costs and time costs, having high scalability, improving the timeliness and consistency of business analysis, and reducing the functional defect rate and operation and maintenance difficulty. BRIEF DESCRIPTION OF THE DRAWINGS

[0051] To more clearly illustrate the technical solutions of the embodiments of this application, the following will briefly introduce the drawings required in the embodiments. It should be understood that the following drawings only show some embodiments of this application, and therefore should not be regarded as limiting the scope. For those of ordinary skill in the art, other related drawings can be obtained based on these drawings without creative efforts.

[0052] Figure 1 FIG. is a schematic diagram of an application scenario of an account information processing method provided by an embodiment of this application;

[0053] Figure 2 FIG. is a schematic diagram of a user account creation interface provided by an embodiment of this application;

[0054] Figure 3 FIG. is a schematic diagram of a user account combination interface provided by an embodiment of this application;

[0055] Figure 4 FIG. is a schematic diagram of a process flow of an account information processing method provided by an embodiment of this application;

[0056] Figure 5 FIG. is a schematic diagram of a process flow of a method for generating a virtual plan provided by an embodiment of this application;

[0057] Figure 6 FIG. is a schematic diagram of the structure of an account information processing device provided by an embodiment of this application;

[0058] Figure 7It is a schematic structural diagram of an electronic device provided by an embodiment of the present application. Detailed implementation manners

[0059] To make the objectives, technical solutions and advantages of the embodiments of the present application clearer, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present application. It should be understood that the accompanying drawings in the present application are only for the purposes of illustration and description, and are not used to limit the protection scope of the present application. In addition, it should be understood that the schematic drawings are not drawn to scale. The flowcharts used in the present application illustrate operations implemented according to some embodiments of the present application. It should be understood that the operations in the flowchart may not be implemented in sequence, and steps without logical context may be reversed or implemented simultaneously. In addition, those skilled in the art may add one or more other operations to the flowchart or remove one or more operations from the flowchart under the guidance of the content of the present application.

[0060] In addition, the described embodiments are only some embodiments of the present application, rather than all embodiments. The components of the embodiments of the present application described and illustrated in the drawings here may be arranged and designed in various different configurations. Therefore, the following detailed description of the embodiments of the present application provided in the drawings is not intended to limit the scope of the claimed present application, but merely represents selected embodiments of the present application. All other embodiments obtained by those skilled in the art based on the embodiments of the present application without creative efforts belong to the protection scope of the present application.

[0061] It should be noted that the term "including" will be used in the embodiments of the present application to indicate the existence of the subsequently stated features, but does not exclude adding other features.

[0062] Currently, related systems for investment analysis mainly provide two account selection modes. One is a single account, and the other is multiple accounts with specified conditions. However, the selection conditions of the above two account selection modes are relatively fixed, and cannot quickly meet the diverse analysis query and data extraction needs of business users. When other specific selection dimensions appear, or when it is necessary to query and analyze after selecting accounts one by one, or when it is necessary to manually filter some unnecessary data after all are loaded, it will cause serious waste of system resources and processing time. Therefore, it does not support creating personalized account dimensions and real-time analysis. If customized development is required for each query dimension, not only a large amount of working hours of technical personnel such as requirements, design, front-end, back-end, and testing are required, but also a long time period from development to online is needed, and the actual needs of users cannot be met in time.

[0063] In the above account selection mode, the main reasons why the traditional account information processing system cannot meet the multi-dimensional account selection may include: the query conditions and account sets customized by users based on business needs are highly personalized and diverse. Among them, the user's selection may be a non-entity plan at the planning level, or it may be a grouping of combinations according to different classification criteria under entity and / or non-entity plans, or even a non-entity combination formed by fitting multiple assets or individual bonds. The traditional system accesses the basic information of entity plans and entity combinations from the custodian bank, and calculates and analyzes indicators such as positions and returns based on the valuation information such as the cost, market value, and valuation increment of entity combinations and entity units in the valuation table obtained daily. However, for non-entity account sets, account classification methods, hierarchical settings, etc. that exist irregularly and are customized, the basic elements for calculation cannot be obtained by accessing the valuation information sent by the custodian. Especially for the summary accounts in the valuation table, the system needs to be able to create processing logic to automatically generate virtual valuation data to achieve the same standard of data analysis basis as entity plans and / or entity combinations. Therefore, the traditional account information processing system cannot provide support for the analysis requirements of the above non-entity accounts, and its query and analysis scope are limited to the scope of entity plans and entity combinations, and it cannot support real-time analysis of account dimensions outside the created entities.

[0064] Based on the above problems, the present application proposes an account information processing method. Based on the user's permissions, this method obtains and displays the selectable data of the user, so as to provide the user with multiple combinations in multiple plans and the entity units included in the combinations. Then, in response to the user's selection and creation operation for the target combination and / or target entity unit in the plan, a virtual plan is generated to meet the user's flexible and diverse analysis query and data extraction needs. Then, according to the valuation information of each entity unit in the virtual plan, the valuation information of the virtual plan is determined and displayed to achieve customized analysis for the user's query dimension. And, by presetting the calculation logic for determining the valuation information of the virtual plan based on the valuation information of the entity unit and solidifying it in the system applied by the account information processing method, the development cycle is shortened, so as to meet the actual needs of users in a timely manner.

[0065] Next, refer to Figure 1 to introduce the application scenario of the account information processing method. As Figure 1As shown in the figure, the account information processing method can be applied to a server. The server can obtain the valuation information of each entity unit sent by the custodian bank, and display selectable data to the user through the user account information interface, including the planned combinations and entity units, and respond to the user's selection and creation operation, thereby creating a combination and an entity combination including the selected entity units that the user needs to analyze. Combine the selected entity units and combinations into virtual combinations and virtual plans according to the hierarchical relationship, and based on the date range selected by the user, process the valuation information in each entity unit according to the relationship between the virtual combinations and virtual plans and the entity units and entity combinations, determine the valuation information of the virtual plan, and display the valuation information to the user, so that the user can analyze and compare according to the valuation information.

[0066] Figure 2 It is a schematic diagram of the user account creation interface. Figure 3 It is a schematic diagram of the user account combination interface.

[0067] As Figure 2 shown, the schematic diagram of the user account creation interface includes a basic information filling column, an account selection column, and a category selection column. Among them, in the basic information filling column, the user can first select the entity plan to which the combination to be created belongs in the basic information, and then set the code, name, and expiration date for the combination to be created. Then select the entity unit in the account selection column. The account selection column is used to display each account included in the plan selected by the user, and the user can select the account to be viewed in the account selection column. Optionally, each account in the account selection column includes information such as plan number, plan name, account code, account name, and operation. Among them, the plan number and plan name can be the number and name of the plan to which the account belongs, the account code and account name are the code and name of the current account, and the operation can be selected and unselected. The category selection column is used to represent the entity units included in at least one account selected by the user in the account selection column, and the entity units can be sorted according to the category rules. Optionally, each entity unit in the category selection column can include information such as account number, account name, category classification name, category grouping name, category detailed name, and operation. Among them, the account number and account name are the number and name of the account to which the current entity unit belongs, the category classification name, category grouping name, and category detailed name are the attribute information of the entity unit, and the operation can be selected and unselected. The user can select the account to be analyzed in the account selection column, or directly select the entity unit to be analyzed in the category selection column. After the selection is completed, click the OK button to complete the construction of the virtual account.

[0068] As Figure 3As shown, in the user account combination interface, there are an account selection column and a selected column. The account selection column may include a plan column, a grouping column, and an account column. The plan column can display multiple entity plans that match the user's permissions, and can also include multiple pre-set virtual plans. The grouping column can display the groups included in the entity plans or virtual plans selected by the user. The account column can display the accounts included in the groups selected by the user, that is, the entity combinations, and the virtual combinations created through the user account creation interface as shown in Figure 2 The plans, groups, and accounts selected by the user in the plan column, grouping column, and account column can be displayed in the selected column. It should be noted that the plan column, grouping column, and account column can each include a select-all option for the convenience of the user's efficient selection. Optionally, there are delete buttons for the options of the plans, groups, and accounts in the selected column to facilitate the user to delete misselected items. At the same time, there is a one-click clear button in the selected column to delete all the content in the selected column at once. When the user selects at least one plan, group, or account that needs to be analyzed and then clicks the OK button, the server can generate a virtual plan based on the plan, group, or account selected by the user.

[0069] It should be noted that a group can include multiple accounts, and an account can include an entity combination and a virtual combination, where the virtual combination can be pre-set.

[0070] Next, with reference to Figure 4 A method for processing account information in this application will be explained in detail. The account information processing method is applied in the above server.

[0071] S401. Based on the user's permissions, obtain and display the user's selectable data. The selectable data includes at least one combination in the plan. Each combination includes at least one entity unit, and each entity unit has corresponding attribute information, and the attribute information is used to indicate the category to which the entity unit belongs.

[0072] Optionally, the user's permissions can be pre-set according to the user's account information. The permissions of different users can be different, and the plans and combinations that users with different permissions can select may be different.

[0073] Optionally, the plan can be an entity plan or a virtual plan. Among them, the entity plan can be a real investment plan that has already been invested, and the virtual plan can be a plan that has not been invested and is composed of invested entity combinations or invested entity units and does not actually exist. For example, an entity plan can be a plan formed by an investor investing an annuity fund.

[0074] The combinations can include physical combinations and virtual combinations. Among them, a physical combination is an asset allocation made by an investor with part of the funds for a physical plan. For example, the investor hands over the annuity fund to multiple investment management units for management, and each investment management unit conducts asset allocation on the allocated part of the annuity fund, thus forming multiple physical combinations. A virtual combination is preset and composed of at least one physical unit. Optionally, both the physical plan and the virtual plan can include multiple combinations, and each combination can have a focused classification. Exemplarily, the combinations can include equity-biased combinations, fixed-income-biased combinations, and money-market-biased combinations.

[0075] A physical unit can be multiple holding asset units that make up physical combinations and virtual combinations. For example, it can be an individual bond. According to the dimension of the holding assets, it can be the attribute information corresponding to the physical unit. According to the attribute information, individual bonds can be divided into multiple categories, including subject codes, asset groupings, primary asset classifications or secondary asset classifications, asset sub-categories, and summary subjects, etc. Exemplarily, a physical combination can include three physical units: time deposits, national debts, and interest rate bonds. Among them, national debts can be divided into national debts with a maturity of more than one year and national debts with a maturity of less than one year according to the asset sub-category, and interest rate bonds can be classified as financial bonds, etc.

[0076] After obtaining the user's permission, the data that the user can select can be obtained and displayed. As Figure 2 shown, after the user selects a physical plan, the account selection bar displays all the combinations that can be viewed under the user's permissions included in the plan, and all the physical units under the user's permissions within the combinations. As an optional implementation method, a virtual plan can also be preset, and the virtual plan can be composed of virtual combinations composed of multiple physical units.

[0077] S402. In response to the user's selection and creation operation for the target combination and / or target physical unit in the plan, generate a virtual plan, and the account includes at least one virtual combination and / or at least one physical combination and / or at least one physical unit.

[0078] Optionally, after the user selects the target combination and / or target physical unit in the interface as Figure 2 and Figure 3 shown, a virtual combination can be generated according to the target physical unit, and then a virtual plan can be generated according to the target combination and the virtual combination.

[0079] Optionally, in Figure 3 it can be set that after the user performs a selection operation on the grouping and the combinations and physical units in the account, the selected content is not displayed in the account selection bar, so as to match the query requirements and save loading time and system resources.

[0080] Optionally, the entity units in the combination can be sorted according to type rules. Among them, the category rules can be rules that give priority to a certain category for display. Among them, the category can be the account attributes, asset attributes, subject attributes, etc. of the entity unit or combination. Exemplarily, the user can select the option of giving priority to national debts, and then the server can preferentially display the entity combinations, virtual combinations, and entity units in the combinations related to national debts to the user. It should be noted that if the category rule selected by the user is the priority of Class A, but the selected plan by the user does not include combinations and entity units related to Class A, the combinations and entity units are displayed to the user in the default sorting order. Among them, the default sorting order can be sorted according to the combination code and the entity unit code.

[0081] As an optional implementation manner, if the user does not select a target combination, a virtual combination is generated according to at least one target entity unit, and then a virtual plan is generated from the virtual combination.

[0082] S403. Determine and display the valuation information of the virtual plan according to the valuation information of each entity unit in the virtual plan.

[0083] Optionally, the valuation information of each entity unit may include a valuation table of the entity unit, and the valuation table includes information such as the cost, market value, and valuation increment of the entity unit. Information such as the position and income of the entity unit can be calculated through the information in the valuation table.

[0084] It should be noted that the valuation information of the virtual plan is generated by statistically calculating the valuation information of the real-time units and real-time combinations within the period according to a preset period. Therefore, the valuation information of the virtual plan is displayed according to the preset period, so that the user can view the valuation information of the virtual plan for the preset period and make an analysis based on the valuation information.

[0085] In this embodiment, first, based on the user's permissions, the selectable data of the user is obtained and displayed. Then, in response to the user's selection and creation operations for the target combination and / or target entity unit in the plan, a virtual plan is generated. Thus, in addition to the entity plan and combination, virtual combinations and virtual plans are also supported, and the user is provided with cross-level selection of plans and combinations, breaking the rigid analysis framework. Then, according to the valuation information of each entity unit in the virtual plan, the valuation information of the virtual plan is determined and displayed, so as to give the virtual plan the same status as the entity plan and achieve the same analysis function as the entity plan. And it can accurately analyze and extract data such as the valuation information of each entity unit and combination at one time, avoiding resource waste caused by multiple operations and redundant data queries, reducing the system loading times, loading time consumption and resource occupancy, and thus effectively improving the response speed and user experience. In this embodiment, by applying the account information processing method in the server, the valuation data can be obtained in real time according to the status of the entity unit and the user's needs, reducing the labor cost and time cost, having high scalability, improving the timeliness and consistency of business analysis, and reducing the functional defect rate and operation and maintenance difficulty.

[0086] Next, in the above steps, how to obtain and display the selectable data of the user based on the user's permissions will be introduced:

[0087] Optionally, obtain all initial selection data.

[0088] Optionally, obtain all plans stored in the memory and the combinations included in the plans, as well as the entity units included in the combinations.

[0089] Optionally, filter the initial selection data based on the user's permissions to determine the selectable data of the user.

[0090] Optionally, display the data that the user has the right to view and use the above data as the selectable data.

[0091] In this embodiment, all initial selection data is obtained, and then the initial selection data is filtered based on the user's permissions to determine the selectable data of the user, so as to ensure the security of the data and prevent users without permissions from viewing the combinations and the entity units in the combinations.

[0092] Furthermore, in the above steps, how to filter the initial selection data based on the user's permissions to determine the selectable data of the user will be introduced:

[0093] Optionally, traverse each initial selection data. For the currently traversed initial selection data, determine whether the user has the permission for the current initial selection data. If so, use the current initial selection data as the selectable data of the user.

[0094] Optionally, it can be characterized by tags whether the user has the permission to view the initial selected data. Exemplarily, if user A has the permission to view Plan A, then there is a tag of user A in Plan A.

[0095] It should be noted that if the current user has the permission for combination Z but does not have the permission for each entity unit in combination Z, then combination Z is not displayed on the user account creation interface.

[0096] In this embodiment, each initial selected data is traversed. For the currently traversed initial selected data, it is judged whether the user has the permission for the current initial selected data. If so, the current initial selected data is used as the selectable data of the user, so as to ensure data security and prevent users without permission from viewing the combination and the entity units in the combination.

[0097] Next, with reference to Figure 5 the generation of a virtual plan in response to the user's selection and creation operation for the target combination and / or target entity unit in the plan in step S402 above will be introduced:

[0098] S501. Combine the target entity units selected by the user into a virtual combination.

[0099] Optionally, after the user selects the target combination and entity units to be analyzed in the user account information combination interface as shown in Figure 3 and clicks Confirm. The server first generates a virtual combination according to the target entity units selected by the user. It should be noted that the user can select the rules and quantity for generating the virtual combination. Exemplarily, if the user selects entity unit a, entity unit b, entity unit c, and entity unit d and confirms to generate two virtual combinations: virtual combination A and virtual combination B, then the user can use the drag function to drag entity unit a, entity unit b, and entity unit c into virtual combination A and drag entity unit b into virtual combination B.

[0100] S502. Respectively use each target combination selected by the user as a virtual combination.

[0101] Optionally, the target combination can include an entity combination and a virtual combination. Keep the virtual combination unchanged and use the entity combination as the virtual combination, then multiple virtual combinations can be output.

[0102] Optionally, the number and name of the virtual combination can be set by the user. It is worth mentioning that the numbers of each virtual combination are different.

[0103] S503. Generate a virtual plan according to each virtual combination.

[0104] Optionally, combining the virtual combinations that can be obtained in steps S501 - S502 can generate at least one virtual plan. The user can set the numbers and names of multiple virtual plans to be generated. The numbers of each virtual plan are all different.

[0105] It should be noted that a virtual plan includes at least one virtual combination, and a virtual combination includes at least one entity unit. Therefore, the generated virtual plan contains information about the virtual plan, including type, code, name, opening date, and deactivation date, etc., and also includes information about the virtual combination, including type, code, name, opening date, and deactivation date, etc., and also includes information about the entity unit, including type, code, name, opening date, and deactivation date, etc. That is to say, the generated virtual plan can be a virtual asset tree, with the virtual plan at the top level, the virtual plan including at least one virtual combination, and the virtual combination including at least one entity unit.

[0106] In this embodiment, first, the selected target entity units of the user are combined into virtual combinations, and then each selected target combination of the user is taken as a virtual combination. According to the virtual combinations, virtual plans are generated, so as to combine the entity units and combinations belonging to at least one combination selected by the user to generate virtual plans, thereby constructing a multi - level account analysis system to meet the actual analysis needs of the user.

[0107] As an optional implementation manner, the virtual plan is presented in the form of a hierarchical data table. The hierarchical data table includes multiple layers of data corresponding one - to - one to the levels of the virtual plan, and each layer of data includes an opening date, a closing date, and detailed data respectively.

[0108] Optionally, the hierarchical data table can represent the data of each level in the virtual plan. Specifically, the data in each level can include a serial number, a category, a code, a name, an opening date, and a deactivation date. Among them, the serial number represents the sorting position in the current level, the category can include national debt categories, etc., and the code represents the code of the current plan, combination, or entity unit. The opening date and deactivation date represent the opening date and deactivation date of the current plan, combination, or entity unit. It should be noted that in the virtual plan and virtual combination, the opening date and deactivation date can synthesize the opening date and deactivation date of the entity units it contains. As an optional implementation manner, the union of the dates composed of the opening dates and deactivation dates of each entity unit can be used as the interval composed of the opening date and deactivation date of the combination, and then the union of the dates composed of the opening dates and deactivation dates of each combination can be used as the interval composed of the opening date and deactivation date of the plan.

[0109] As an alternative implementation, the hierarchical data table can be represented as: {sequence number, type, code, name, account opening date, deactivation date, detailed data {sequence number, type, code, name, account opening date, deactivation date, detailed data {sequence number, type, code, name, account opening date, deactivation date}}}.

[0110] Next, an introduction is given to determining and displaying the valuation information of the virtual plan according to the valuation information of each entity unit in the virtual plan in step S403 above.

[0111] Optionally, at least one target detailed data is filtered from the hierarchical data table according to the date range selected by the user and the account opening date and account closing date of each layer of data in the hierarchical data table.

[0112] First, respond to the date range selected by the user, and then filter at least one target detailed data from the hierarchical data table according to the account opening date and account closing date of each layer of data in the hierarchical data table, including the account opening date and account closing date of the plan, portfolio, and entity unit. Among them, the target detailed data includes the relationship between each portfolio included in the plan and the relationship between each entity unit included in the portfolio, and includes the plan code, portfolio code, dimension classification code, grouping code, and dimension code included in each portfolio, and includes the plan code included in each plan and the portfolio code included.

[0113] For example, taking a certain entity unit in the hierarchical relationship table as an example, if the account opening date and account closing date of the entity unit are from January 1st to April 1st, and the date range selected by the user is from May 30th to December 30th, then this entity unit is filtered out, and other entity units that meet the date range are selected as part of the target detailed data. The filtering process of the portfolio and the plan is the same as above.

[0114] It should be noted that before responding to the date range selected by the user, the maximum business date of the valuation information of each plan, portfolio, and entity unit in the hierarchical data table can also be obtained, which is used to limit the end time option of the date range selected by the user. Exemplarily, if the maximum business date is December 30th, then when the user selects the date range, only the date on December 30th and before can be selected, so as to generate the date range.

[0115] Optionally, the valuation information of the virtual plan is determined and displayed according to the valuation information corresponding to at least one target detailed data.

[0116] The valuation information of the virtual plan can be determined according to the valuation information of each plan, entity unit, and portfolio included in the target detailed data. It should be noted that the valuation data of the portfolio at least includes: quantity, cost, market value, and valuation increment.

[0117] In this embodiment, at least one target detailed data is filtered from the hierarchical data table according to the date range selected by the user and the account opening date and account closing date of each layer of data in the hierarchical data table. Then, according to the valuation information corresponding to at least one target detailed data, the valuation information of the virtual plan is determined and displayed, so as to solidify the valuation information calculation process and meet the analysis requirements of various investment indicators and application scenarios.

[0118] Further, the determination and display of the valuation information of the virtual plan according to the valuation information corresponding to at least one target detailed data will be specifically introduced as follows:

[0119] Optionally, the valuation information of each target detailed data is combined to obtain and display the valuation information of the virtual plan.

[0120] It should be noted that the business time for accessing and calculating the valuation information can be in days.

[0121] In the target detailed data, if a virtual portfolio is included, obtain the plan code, portfolio code, dimension classification code, grouping code, and dimension code of the virtual portfolio, and then group the virtual portfolio and its corresponding virtual portfolio according to the coding polarity to obtain each virtual portfolio information set.

[0122] When calculating the valuation information of the virtual portfolio, first extract the valuation information of the previous day of the business date according to the business date, then obtain the valuation information of each entity unit included in the portfolio on the business date, and separately summarize the position quantity, position cost, position market value, and valuation increment. Then, according to the changes in the number of entity units and the cost of entity units in the valuation information of the business date and the previous day of the business date, determine whether a transaction has occurred. If a transaction has occurred, calculate the buy and sell amounts of the virtual portfolio and entity units on the business date. On the business date, in the valuation information of the virtual portfolio, the portfolio cost is the total cost of the summarized entity units. The portfolio quantity is the quantity of the previous day of the business date plus the ratio of the total turnover on the business date to the market value of the previous day of the business date. The portfolio market value is the summarized market value of the entity units. The valuation increment is the summarized valuation increment of the entity units. The unit cost is the ratio of the cost of the entity unit to the number of entity units. The unit net value is the ratio of the market value of the entity unit to the number of entity units.

[0123] When calculating the valuation information of the virtual plan, first obtain the cash flows of the virtual portfolio and entity portfolio included therein, then calculate the entrusted amount and the balance of entrusted assets according to the cash flows, and summarize the valuation information of the above virtual portfolio, including quantity, cost, market value, and valuation increment. The above entrusted amount, balance of entrusted assets, quantity, cost, market value, and valuation increment are used as the valuation information of the virtual plan.

[0124] In this embodiment, by combining the valuation information of each target detail data, the valuation information of the virtual plan is obtained and displayed, so as to realize the account selection and analysis that are not only configurable but also more analyzable and have no limit on the virtual and real.

[0125] As an alternative implementation, before step S401, based on the user's permissions, obtaining and displaying the entity plan selected by the user, the user's permissions can also be obtained according to the user's account information in response to the user's login operation.

[0126] Optionally, the user's login account and password can be stored in advance. When the user logs in, it is compared whether the account and password entered by the user are consistent with the stored account and password. If they are consistent, the user's permissions can be obtained according to the user's account information.

[0127] In this embodiment, by responding to the user's login operation and obtaining the user's permissions according to the user's account information, the plans, combinations, and entity units that the user can operate and view are displayed for the user, ensuring system and information security.

[0128] Based on the same inventive concept, an account information processing device corresponding to the account information processing method is also provided in the embodiment of the present application. Since the principle of solving problems by the device in the embodiment of the present application is similar to the above-mentioned account information processing method in the embodiment of the present application, the implementation of the device can refer to the implementation of the method, and the repeated parts will not be described again.

[0129] Refer to Figure 6 As shown in the figure, it is a schematic diagram of an account information processing device provided by an embodiment of the present application. The device includes: an acquisition module 601, a generation module 602, and a determination module 603; where:

[0130] The acquisition module 601 is configured to obtain and display the selectable data of the user based on the user's permissions. The selectable data includes at least one combination in the plan, each combination includes at least one entity unit, and each entity unit has corresponding attribute information, and the attribute information is used to indicate the category to which the entity unit belongs.

[0131] The generation module 602 is configured to generate a virtual plan in response to the user's selection and creation operation for the target combination and / or target entity unit in the plan. The account includes at least one virtual combination and / or at least one entity combination and / or at least one entity unit.

[0132] The determination module 603 is configured to determine and display the valuation information of the virtual plan according to the valuation information of each entity unit in the virtual plan.

[0133] Optionally, the acquisition module 601 is specifically configured to:

[0134] Obtain all initial selected data;

[0135] Filter the initial selected data based on the user's permissions to determine the selectable data for the user.

[0136] Optionally, the obtaining module 601 is specifically configured to:

[0137] Traverse the initial selected data. For the currently traversed initial selected data, determine whether the user has the permission for the current initial selected data. If so, use the current initial selected data as the selectable data for the user.

[0138] Optionally, the generating module 602 is specifically configured to:

[0139] Combine the target entity units selected by the user into a virtual combination;

[0140] Respectively use each target combination selected by the user as a virtual combination;

[0141] Generate the virtual plan according to the virtual combinations.

[0142] Optionally, the virtual plan is presented in the form of a hierarchical data table. The hierarchical data table includes multiple layers of data corresponding one by one to the levels of the virtual plan. Each layer of data includes an account opening date, an account closing date, and detailed data;

[0143] Optionally, the determining module 603 is specifically configured to:

[0144] Filter at least one target detailed data from the hierarchical data table according to the date range selected by the user and the account opening date and account closing date of each layer of data in the hierarchical data table;

[0145] Determine and display the valuation information of the virtual plan according to the valuation information corresponding to the at least one target detailed data.

[0146] Optionally, the determining module 603 is specifically configured to:

[0147] Combine the valuation information of the target detailed data to obtain and display the valuation information of the virtual plan.

[0148] Optionally, the obtaining module 601 is further configured to:

[0149] In response to the user's login operation, obtain the user's permissions according to the user's account information.

[0150] For the processing flow of each module in the device and the interaction flow between modules, reference can be made to the relevant descriptions in the method embodiments above, which will not be elaborated here.

[0151] An embodiment of the present application also provides an electronic device, such as Figure 7 shown in the structural schematic diagram of the electronic device provided by the embodiment of the present application, including: a processor 701, a memory 702, and a bus. The memory 702 stores machine-readable instructions executable by the processor 701 (for example, Figure 6 the execution instructions corresponding to the acquisition module 601, the generation module 602, and the determination module 603 in the device in

[0152] ), etc.). When the computer device runs, the processor 701 communicates with the memory 702 through the bus, and when the machine-readable instructions are executed by the processor 701, the above-mentioned account information processing method is executed.

[0153] Those skilled in the art can clearly understand that for the convenience and simplicity of description, the specific working processes of the above-described systems and devices can refer to the corresponding processes in the method embodiments, which will not be elaborated in this application. In the several embodiments provided in this application, it should be understood that the disclosed systems, devices, and methods can be implemented in other ways. The device embodiments described above are only illustrative. For example, the division of the modules is only a logical function division, and there can be other division methods in actual implementation. For another example, multiple modules or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the displayed or discussed couplings or direct couplings or communication connections to each other can be through some communication interfaces, and the indirect couplings or communication connections of the devices or modules can be electrical, mechanical, or other forms.

[0154] In addition, each functional unit in various embodiments of the present application may be integrated into one processing unit, may exist physically alone for each unit, or two or more units may be integrated into one unit. If the function is implemented in the form of a software functional unit and sold or used as an independent product, it may be stored in a computer-readable storage medium. Based on such an understanding, the technical solution of the present invention, in essence, or the part that contributes to the prior art, or a part of the technical solution, may be embodied in the form of a software product. The computer software product is stored in a storage medium and includes several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in various embodiments of the present invention. The foregoing storage medium includes: various media such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disc that can store program codes.

[0155] The above are only specific embodiments of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art within the technical scope disclosed by the present application can easily think of changes or substitutions, which should all be covered by the protection scope of the present application.

Claims

1. A method for processing account information, characterized in that, The method includes: Based on the user's permissions, obtain and display the user's selectable data. The selectable data includes at least one combination in the plan. Each combination includes at least one entity unit, and each entity unit has corresponding attribute information, where the attribute information is used to indicate the category to which the entity unit belongs; In response to the user's selection creation operation for the target combination and / or target entity unit in the plan, generate a virtual plan. The account includes at least one virtual combination and / or at least one entity combination and / or at least one entity unit; Based on the valuation information of each entity unit in the virtual plan, determine and display the valuation information of the virtual plan.

2. The method according to claim 1, characterized in that, The obtaining and displaying the user's selectable data based on the user's permissions includes: Obtain all initial selection data; Filter the initial selection data based on the user's permissions to determine the user's selectable data.

3. The method according to claim 2, wherein The filtering the initial selection data based on the user's permissions to determine the user's selectable data includes: Traverse each initial selection data. For the currently traversed initial selection data, determine whether the user has the permission for the current initial selection data. If so, use the current initial selection data as the user's selectable data.

4. The method according to claim 1, characterized in that, The generating a virtual plan in response to the user's selection creation operation for the target combination and / or target entity unit in the plan includes: Combine the selected target entity units by the user into a virtual combination; Respectively use each selected target combination by the user as a virtual combination; Generate the virtual plan according to each virtual combination.

5. The method according to claim 1, characterized in that, The virtual plan is presented in the form of a hierarchical data table. The hierarchical data table includes multiple layers of data corresponding one by one to the levels of the virtual plan. Each layer of data includes an account opening date, an account closing date, and detailed data; The determining and displaying the valuation information of the virtual plan based on the valuation information of each entity unit in the virtual plan includes: According to the date range selected by the user and the account opening date and account closing date of each layer of data in the hierarchical data table, filter at least one target detailed data from the hierarchical data table; Based on the valuation information corresponding to the at least one target detailed data, determine and display the valuation information of the virtual plan.

6. The method according to claim 5, characterized in that The determining and displaying the valuation information of the virtual plan based on the valuation information corresponding to the at least one target detailed data includes: Combine the valuation information of each target detailed data to obtain and display the valuation information of the virtual plan.

7. The method according to claim 1, wherein Before the obtaining and displaying the entity plan selected by the user based on the user's permissions, it further includes: In response to the user's login operation, obtain the user's permissions according to the user's account information.

8. An account information processing device, characterized in that, The device includes: An obtaining module, configured to obtain and display the user's selectable data based on the user's permissions. The selectable data includes at least one combination in the plan. Each combination includes at least one entity unit, and each entity unit has corresponding attribute information, where the attribute information is used to indicate the category to which the entity unit belongs; A generation module, configured to generate a virtual plan in response to an operation created by a user's selection of a target combination and / or a target entity unit in the plan, where the account includes at least one virtual combination and / or at least one entity combination and / or at least one entity unit; A determination module, configured to determine and display the valuation information of the virtual plan according to the valuation information of each entity unit in the virtual plan.

9. An electronic device, characterized in that, Comprising: A processor, a memory, and a bus. The memory stores program instructions executable by the processor. When the electronic device runs, the processor communicates with the memory through the bus. The processor executes the program instructions to perform the steps of the account information processing method according to any one of claims 1 to 7 when executed.

10. A computer-readable storage medium, characterized in that, A computer program is stored on the computer-readable storage medium. When the computer program is run by the processor, it performs the steps of the account information processing method according to any one of claims 1 to 7.

Images