Benefit information display method and electronic device

Abstract

Disclosed in embodiments of the present application are a benefit information display method and an electronic device. The method comprises: acquiring a benefit data definition template, wherein the benefit data definition template comprises a plurality of data fields; acquiring data display rule information respectively corresponding to a plurality of benefit items; on the basis of the benefit data definition template, storing data of a user respectively on the plurality of data fields of the plurality of benefit items; and in response to a benefit information viewing request initiated by a target user, reading, from the stored information, data of the target user on the plurality of data fields of the plurality of benefit items, and assembling the data into display content respectively corresponding to the plurality of benefit items, so as to display, in a target page, the display content respectively corresponding to the plurality of benefit items. By means of the embodiments of the present application, information of a plurality of different benefit items can be displayed in an aggregated manner by means of a same page, and low development cost and high expandability are achieved.

Description

Method and electronic device for displaying equity information

[0001] This application claims priority to the Chinese patent application filed with the China Patent Office on August 14, 2023, with application number 202311015911.7 and application name “Method and electronic device for displaying rights and interests information”, the entire contents of which are incorporated by reference into this application. Technical Field

[0002] The present application relates to the field of information technology, and in particular to a method and electronic device for displaying rights and interests information. Background Art

[0003] Many application systems have membership systems where users can obtain more membership benefits by becoming members of higher levels. For example, in a product information service system, merchants can be offered a variety of membership types. At higher membership levels, merchants can receive a variety of membership benefits, such as industry management guidance, priority access to high-quality logistics services, and so on.

[0004] In the existing technology, customer service personnel usually introduce users to information such as the benefits and rights enjoyed by various membership levels. However, after users become members of the corresponding level, information about the available benefits is usually revealed in multiple different scenarios. For example, when a merchant ships to an overseas user, the user may be reminded that the merchant enjoys "sea shipping priority", etc. It can be seen that under this method, the user's perception and use of various benefits are relatively passive. Therefore, many benefits may be difficult for users to use, or the frequency of use is very low, making it difficult to reflect the actual value that the corresponding membership level can bring to users.

[0005] Summary of the Invention

[0006] This application provides a method and electronic device for displaying rights and interests information, which can aggregate and display information of multiple different rights and interests items on the same page, with low development cost and high scalability.

[0007] This application provides the following solutions:

[0008] A method for displaying equity information, comprising:

[0009] Obtaining a rights and interests data definition template, wherein the rights and interests data definition template includes multiple data fields, wherein the multiple data fields include data fields related to basic information and data fields related to user usage;

[0010] Obtain data display rule information on data fields related to user usage corresponding to multiple benefit items in different user usage situations;

[0011] According to the rights and interests data definition template, the user's data in multiple data fields of multiple rights and interests items are saved, wherein the data in the data fields related to the user's usage is determined based on the user's rights and interests item usage information and the data display rule information;

[0012] In response to a request initiated by a target user to view rights information, the data of the target user on multiple data fields of the multiple rights items are read from the saved information and assembled into display contents corresponding to the multiple rights items, so as to display the display contents corresponding to the multiple rights items on the target page.

[0013] Among them, for fields related to user usage, different benefit items correspond to different candidate values ​​for the same field;

[0014] The data display rule information specifically includes: the correspondence between the candidate values ​​of the same benefit item in the same field and the user's usage, so as to determine the data to be displayed for the corresponding benefit item in the corresponding field from the candidate values ​​of the corresponding benefit item in the corresponding field based on the usage information of the specific user.

[0015] The fields related to user usage include: description text and / or action items required to be displayed when displaying benefit items;

[0016] The method of obtaining data display rule information on data fields related to user usage corresponding to the plurality of benefit items under different user usage situations includes:

[0017] Obtaining information on displaying rules for descriptions and / or actions corresponding to multiple benefit items under different user usage scenarios; wherein each benefit item corresponds to a different candidate description and / or candidate action item, and the data display rule information includes: a correspondence between each candidate description and / or candidate action item for the same benefit item and the user usage scenario;

[0018] The step of saving data of multiple users in multiple data fields of multiple rights items according to the rights data definition template includes:

[0019] Obtain usage information of the multiple rights items by multiple users respectively, and determine the corresponding description text and / or action items to be displayed when displaying the rights items to each user based on the usage information and the data display rules, and save them as data in the corresponding data fields.

[0020] The action item information includes the name of the action item and a jump address, so as to jump to the corresponding page according to the jump address to obtain detailed information related to the benefit item, or perform processing related to the benefit item.

[0021] If the target user has used the benefit item, the description text includes: the number of times the target user has used the benefit item, the remaining number of times and / or the usage effect information obtained.

[0022] If the target user has not used the benefit item, the description text includes: functional description summary information about the benefit item.

[0023] Among them, by executing scheduled tasks, the usage information of multiple users on the multiple rights items is obtained, and based on the usage information and the data display rules, the data corresponding to the data field related to the user's usage is determined when the rights items are displayed to each user.

[0024] The rights and interests data definition template includes: a first template and a second template, wherein the first template is used to define data fields related to the rights and interests items and basic information, and the second template is used to define data fields related to multiple rights and interests items and user usage;

[0025] The step of saving data of multiple users in multiple data fields of multiple rights items according to the rights data definition template includes:

[0026] According to the first template, data on data fields related to the plurality of equity items and the basic information are saved as equity configuration information;

[0027] According to the second template, data on the data fields related to the plurality of benefit items and user usage are saved as benefit usage related data information;

[0028] When responding to the target user's request to view the rights and interests information, it includes:

[0029] Acquire data of the plurality of equity items in data fields related to basic information from the equity configuration information;

[0030] Acquire data of the target user on data fields related to user usage of the plurality of benefit items from the benefit usage related data;

[0031] The data of the multiple rights items in the data fields related to the basic information and the data in the data fields related to the user usage are assembled to generate display content corresponding to the multiple rights items respectively.

[0032] The step of obtaining data of the plurality of equity items in data fields related to basic information from the equity configuration information includes:

[0033] Determine the membership type information corresponding to the target user;

[0034] The data of the multiple benefit items corresponding to the member type in the data fields related to the basic information are obtained from the benefit configuration information.

[0035] Among them, different membership types correspond to different processor modules;

[0036] After determining the membership type information corresponding to the target user, the method further includes:

[0037] The corresponding processor module is determined according to the member type information, so that the processor module can read and assemble the data.

[0038] Wherein, the equity configuration information includes a sorting index field corresponding to the equity item;

[0039] The method further comprises:

[0040] According to the data on the sorting index field, the display contents corresponding to the multiple rights and interests items are sorted so as to be displayed in the corresponding order on the target page.

[0041] When a benefit item is added, deleted, or information is updated, the benefit configuration information and / or benefit usage-related data information are updated to update the displayed benefit item and / or corresponding display content.

[0042] A method for displaying equity information, comprising:

[0043] Receive a request from a target user to view rights information;

[0044] Displaying a target page, the target page including display content corresponding to the plurality of benefit items, the display content being generated by a same processor module reading and assembling data of the target user in the plurality of data fields of the plurality of benefit items;

[0045] Among them, the data of the target user in multiple data fields of the multiple rights and interests items are determined according to the rights and interests data definition template, including data fields related to basic information and data fields related to user usage. The data in the data fields related to user usage is determined based on the user's rights and interests item usage information and the data display rules.

[0046] The display contents corresponding to the multiple rights and interests items include:

[0047] Action item information corresponding to the benefit item, including the name of the action item and a jump address, so as to jump to the corresponding page according to the jump address to obtain detailed information related to the benefit item, or perform processing related to the benefit item;

[0048] Among them, different benefit items correspond to different action items under the same user usage situation.

[0049] A device for displaying equity information, comprising:

[0050] a template acquisition unit, configured to acquire a rights and interests data definition template, wherein the rights and interests data definition template includes a plurality of data fields, wherein the plurality of data fields include a data field related to basic information and a data field related to user usage;

[0051] A data display rule acquisition unit is used to acquire data display rule information on data fields related to user usage conditions corresponding to multiple benefit items under different user usage conditions;

[0052] a data acquisition unit, configured to save the user's data in multiple data fields of multiple benefit items according to the benefit data definition template, wherein the data in the data fields related to the user's usage is determined based on the user's benefit item usage information and the data display rules;

[0053] The display content construction unit is used to respond to a request for viewing rights information initiated by a target user, read the data of the target user on multiple data fields of the multiple rights items from the saved information, and assemble them into display content corresponding to the multiple rights items, so as to display the display content corresponding to the multiple rights items on the target page.

[0054] A device for displaying equity information, comprising:

[0055] A request receiving unit, configured to receive a request from a target user to view rights information;

[0056] A page display unit, configured to display a target page, wherein the target page includes display content corresponding to a plurality of benefit items, wherein the display content is generated by assembling and reading data of the target user in a plurality of data fields of the plurality of benefit items by a same processor module;

[0057] Among them, the data of the target user in multiple data fields of the multiple rights and interests items are determined according to the rights and interests data definition template, including data fields related to basic information and data fields related to user usage. The data in the data fields related to user usage is determined based on the user's rights and interests item usage information and the data display rules.

[0058] A computer-readable storage medium stores a computer program, which, when executed by a processor, implements the steps of any of the aforementioned methods.

[0059] An electronic device, comprising:

[0060] one or more processors; and

[0061] A memory associated with the one or more processors, the memory being used to store program instructions, wherein the program instructions, when read and executed by the one or more processors, execute the steps of any of the aforementioned methods.

[0062] According to the specific embodiments provided in this application, this application discloses the following technical effects:

[0063] Through the embodiments of the present application, the display information of multiple different rights and interests items can be standardized and decomposed and extracted into a standardized template. In the template, the data that needs to be displayed for the rights and interests items can be split into data fields related to basic information and data fields related to user usage. At the same time, data display rules for the fields related to user usage corresponding to multiple rights and interests items under different user usage conditions can also be configured. Afterwards, the user's data on multiple data fields of multiple rights and interests items can be saved according to the rights and interests data definition template. Among them, the data on the fields related to user usage can be determined based on the user's usage information of the multiple rights and interests items and the aforementioned data display rules. In this way, after the target user initiates a request to view the rights and interests information, the data of the target user on multiple data fields of the multiple rights and interests items can be read from the saved information and assembled into the display content corresponding to the multiple rights and interests items for display on the target page. In this way, information of multiple different rights and interests items can be aggregated and displayed on the same page, and information related to user usage can be displayed. During the implementation process, although the information that needs to be conveyed in the same field for each benefit item may be different and related to the specific user's usage of the corresponding benefit item, since the data fields corresponding to each benefit item are uniformly defined and the data to be displayed for different users in multiple fields of each benefit item can be obtained in advance, when it needs to be displayed to the user, the same processing logic can be used to process and complete the data assembly. Accordingly, only the same set of processing logic needs to be developed to complete the display of multiple different benefit items, thereby achieving the purpose of reducing development costs.

[0064] In addition, when equity items are added, deleted, or information is updated, only the specific configuration information needs to be updated. For example, for newly added equity items, it is only necessary to configure the data on each field according to the aforementioned template, without the need to develop new processing logic separately. Therefore, this solution has stronger scalability.

[0065] In a preferred embodiment, the data related to the rights and interests items can be split into two parts: data in fields related to basic information and data in fields related to user usage, with corresponding first and second templates provided. This way, only the data in fields related to user usage needs to be saved at the user dimension and dynamically updated. For data in fields related to basic information, only one copy needs to be saved for each rights and interests item, eliminating the need to save a copy for each user, thus saving storage space.

[0066] Of course, any product implementing the present application does not necessarily need to achieve all of the advantages described above at the same time. BRIEF DESCRIPTION OF THE DRAWINGS

[0067] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the following briefly introduces the drawings required for use in the embodiments. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work.

[0068] FIG1 is a schematic diagram of a system architecture provided in an embodiment of the present application;

[0069] FIG2 is a flow chart of a first method provided in an embodiment of the present application;

[0070] FIG3 is a schematic diagram of a first interface provided in an embodiment of the present application;

[0071] FIG4 is a schematic diagram of a second interface provided in an embodiment of the present application;

[0072] FIG5 is a schematic diagram of a third interface provided in an embodiment of the present application;

[0073] FIG6 is a flow chart of a second method provided in an embodiment of the present application;

[0074] FIG7 is a schematic diagram of a first device provided in an embodiment of the present application;

[0075] FIG8 is a schematic diagram of a second device provided in an embodiment of the present application;

[0076] FIG9 is a schematic diagram of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0077] The following will be combined with the accompanying drawings in the embodiments of this application to clearly and completely describe the technical solutions in the embodiments of this application. Obviously, the embodiments described are only part of the embodiments of this application, not all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field are within the scope of protection of this application.

[0078] First of all, it should be noted that the inventors of this application discovered in the process of implementing the embodiments of this application that, in the prior art, a dedicated page is usually not provided to display the rights and interests that can be enjoyed under a specific membership type, but are scattered on different pages. If a user (specifically a merchant user) needs to use or enable (including activation, configuration, authentication, etc.) a certain right, it is necessary to find the entry for the use or activation of the corresponding right through a multi-level directory before performing the corresponding operation.

[0079] In view of the above situation, in order to better provide users with information about rights and interests and facilitate users to use specific rights and interests, in an embodiment of the present application, a specific page can be provided for users, on which information on various rights and interests that can be enjoyed under a specific membership type can be aggregated and displayed. In addition, not only can basic information such as the name and introduction of each right and interest be displayed, but also corresponding descriptive text (for example, whether it has been used, if used, what is the effect of use, etc.), relevant action item information and other information related to user usage can be provided based on the specific user's use of each right and interest. In this way, users can understand which rights and interests they have, whether they have used them, if used, the corresponding use effects, etc. through the same page. In addition, they can also take specific actions directly through the page, for example, including using, activating, and registering for a certain right and interest item, etc., without having to go to different pages to find the corresponding action entry.

[0080] However, in the process of implementing the above solution, the inventors of the present application discovered that for different users, due to the different usage of each benefit item, the corresponding copy, action items, etc. that need to be displayed will also be different. For example, if a user has already used a certain benefit item, it means that the previous activation, authentication and other processes have been completed and it can be used directly. Therefore, action items such as "de-use" can be directly provided; and if the user has not used a certain benefit item, it may be necessary to activate, authenticate and other processes first. Therefore, options such as "de-activate" and "de-authenticate" can be displayed. On the other hand, for different benefit items, even if the user usage status is the same, the specific copy and action items that need to be displayed to the user may be different. For example, for benefit items A and B, a user has already used both benefits. However, for benefit item A, the copy that needs to be displayed may be "X targets to be completed", and for benefit item B, the copy that needs to be displayed may be "X have been reported this month", and so on, where "X" needs to be determined based on the specific user's usage; or, for benefit items C and benefit item D, a user has not used either of these two benefits, but the action item that needs to be displayed to the user for benefit item C may be "Go to sign up", and the action item that needs to be displayed to the user for benefit item D may be "Go to verify", and so on.

[0081] In other words, if you need to display multiple different rights and interests items and the corresponding data / action items related to user usage through a unified page, then since each right and interest item needs to convey different information / action points to the user, the specific descriptions and action items may also be different. Therefore, the situation is more complicated and you need to consider how to implement it specifically.

[0082] For example, a specific implementation method may be to define a processing class (also called a processor module) for each equity item separately to undertake the processing logic of each equity, including the acquisition and processing of data for each equity item. However, since processors for multiple different equity items need to be defined separately, each processor needs to output descriptions such as the equity item name, icon, whether it meets the standards, equity description text, and the number of remaining equity items. In addition, different action items need to be output. Therefore, when the number of equity items is relatively large, the development cost will be relatively high. In addition, each new equity item requires a new equity processing class, so the scalability of the solution will be relatively poor.

[0083] In order to reduce development costs and improve the scalability of the solution, a specific solution is also provided in an embodiment of the present application. In this solution, a unified processing class can be developed for multiple different rights and interests items, and the differentiated needs of different rights and interests items in terms of display copy and action items can be met through the same processing logic. In order to achieve this goal, the embodiment of the present application can first provide a standardized rights and interests data definition template, in which multiple specific data fields can be defined. Different rights and interests items can share this unified template when being displayed. That is, the specific display content of each rights and interests item can be assembled from the data on each field in the specific template.

[0084] After configuring the data definition template, you can configure the data of each benefit item in each field on the user dimension according to the template for assembling specific display content. Among them, as mentioned above, since different benefit items may have different requirements when displaying descriptive text, action items and other information related to user usage even under the same user usage status, it is also possible to configure separate display rules for each benefit item. The display rules mainly refer to the data display rule information on the data fields related to user usage corresponding to multiple benefit items under different user usage conditions. For example, since different benefit items correspond to different candidate values ​​on the same field for fields related to user usage, the specific data display rule information can be the correspondence between the candidate values ​​of the same benefit item on the same field and the user usage. In this way, the data to be displayed for the corresponding benefit item on the corresponding field can be determined from the candidate values ​​of the corresponding benefit item on the corresponding field based on the usage information of the specific user, and so on.

[0085] After configuring the specific rights data definition template and the aforementioned data display rule information, since it includes data fields related to the user's use of rights items, and these data may change continuously, therefore, under the preferred embodiment, it is possible to obtain data related to the user's use of rights items from the corresponding data source (for example, a data base table that maintains user-dimensional feature data, such as the number of times a certain rights item is used, etc.) by executing a scheduled task. This includes whether a certain user has used a certain rights item, the specific effect of use, etc. After obtaining this data, it is possible to determine what specific text to display when displaying a specific rights item to the user, as well as which specific action item, etc., based on the display rule information corresponding to the specific rights item. These data can be saved in the form of a vertical table, etc., and updated regularly by the aforementioned scheduled task.

[0086] Because data for each benefit item across multiple fields is maintained at the user level, when a specific target user needs to access a specific benefit center page, the basic information for that benefit item and the data in fields related to the user's usage can be read from the pre-stored data and assembled into specific display content for display on the page. Since each data field in the above template is uniformly defined, although the specific content displayed in each field for each benefit item may be different, the same processing logic can be used to assemble the data when it is displayed to the user. Therefore, only a unified processor module needs to be developed to display each different benefit item, thereby reducing development costs. Furthermore, when adding new benefit items, only the configuration or retrieval of data for each field needs to be performed according to the above template, without the need to develop new processing logic. Therefore, this solution has greater scalability. Of course, in actual applications, different processor modules can also be developed based on different membership types, so that the same processor module can process and assemble the relevant data for multiple different benefit items corresponding to the same membership type.

[0087] Among them, under the preferred implementation method, since the specific rights and interests data may include some fields with relatively fixed specific data that will not change due to different users or different user usage, such as the name, icon and other basic information of the rights and interests item, the specific rights and interests data definition template can also be split into two parts, which are used to standardize the fields related to the basic information of the rights and interests items and the fields related to the user's usage. In this way, multiple users can share the same basic information about each rights and interests item, and only the data related to the user's usage needs to be dynamically constructed and saved separately by user. In this way, the basic information of each right and interests can be avoided from being stored separately for each user, thereby saving storage space.

[0088] From the perspective of system architecture, referring to FIG1 , the embodiment of the present application may involve the client and server of a specific application system, wherein, on the server side, it is mainly possible to save specific rights and interests data definition templates (specifically, it may include a first template corresponding to the basic information field and a second template corresponding to the field related to user usage). In addition, it is also possible to save data display rule information on fields related to user usage for multiple rights and interests items under different user usage conditions. Afterwards, the data on the basic information fields of each rights and interests item can be obtained and saved, and the data on the fields related to user usage of the user-dimensional rights and interests item can be constructed by executing timed tasks, etc., and can be updated regularly. After a specific user initiates a request to view the rights and interests information through the client, the server side can also read the data corresponding to each rights and interests item of the target user and assemble it into specific display content to provide to the client for display.

[0089] The specific implementation scheme provided in the embodiments of this application is introduced in detail below.

[0090] Example 1

[0091] First, from the perspective of the server, this embodiment provides a method for displaying rights information. Referring to FIG2 , the method may specifically include:

[0092] S201: Acquire a rights and interests data definition template, wherein the rights and interests data definition template includes multiple data fields, and the multiple data fields include data fields related to basic information and data fields related to user usage.

[0093] The specific rights and interests data definition template can be used to define multiple data fields. The data on these data fields can be the relevant data used to construct the display content of the specific rights and interests item. For example, the specific data fields can include the name, icon, text, action item information, etc. of the rights and interests item.

[0094] Among them, as mentioned above, regarding the multiple data fields in the specific template, some may include fields with relatively fixed specific data, which usually do not change due to different users or different user usage. These fields are usually used to define some basic information of specific rights and interests items, such as the name and icon of the rights and interests item; in addition, some fields are also included, which are related to user usage, that is, what kind of data needs to be displayed in the corresponding fields, which changes dynamically according to the user's usage of the specific rights and interests item, such as the copy to be displayed, the name of the action item, etc.

[0095] Therefore, in order to save storage space during specific implementation, the specific rights and interests data definition template can also be standardized and decomposed into a first template and a second template, wherein the first template is mainly used to define some relatively fixed basic information-related fields, and the second template is mainly used to define some fields related to user usage. In this way, the first template can be universal for different users, that is, for each rights and interests item, it is only necessary to maintain a unified configuration data according to the first template, including the name and icon of the rights and interests item (since the data on these fields will not change due to different users or different user usage, there is no need to configure a separate copy for each user). As for the fields related to user usage, that is, the fields whose specific data may change due to different user usage, a separate copy of rights and interests data can be maintained for each user and saved by constructing a vertical table or other methods.

[0096] For example, in a specific implementation, the first template may specifically include the fields shown in Table 1 below:

[0097] Table 1

[0098] Regarding the second template, the specific defined data fields may be as shown in Table 2:

[0099] Table 2

[0100] It should be noted that in cross-border applications, users may come from multiple countries / regions. Therefore, obtaining information such as the name, grouping, and description of each benefit item may require multilingual display. Specifically, for this basic information, the data for each benefit item in each field can be saved in multiple languages. When displaying this information to a specific user, the benefit item name can be displayed in the corresponding language based on the user's country / region.

[0101] S202: Obtain data display rule information on data fields related to user usage conditions corresponding to multiple benefit items in different user usage conditions.

[0102] Since different rights items may correspond to different candidate values ​​on the same field related to user usage, even in the same user usage situation, the specific data that needs to be revealed for different rights items may be different. For example, when different rights items are used for the same user usage status, the specific data that needs to be revealed, such as the text or action items, on the fields related to user usage may also be different. Therefore, specific data display rule information can also be configured for each rights item separately. For example, such data display rules can be used to describe which candidate values ​​each rights item has on the fields specifically related to user usage, and what data needs to be revealed on the specific fields in various different user usage situations, for example, including what kind of descriptive text and / or what kind of action items are revealed, etc. Among them, the specific candidate texts, action items, and corresponding disclosure rules for each rights item can be different.

[0103] For example, the candidate actions for a benefit item A include "deactivate" and "deactivate", while the candidate actions for another benefit item B include "deactivate" and "deauthenticate". Accordingly, the corresponding rules can be set as follows:

[0104] Equity Item A:

[0105] If the user has used benefit item A, the action item displayed is "Deactivate". If the user has not used benefit item A, since benefit item A requires activation before use, the action item displayed may be "Deactivate".

[0106] Equity Item B:

[0107] If the user has used benefit item B, the action item displayed is "de-use"; if the user has not used benefit item B, since benefit item B requires user authentication before use, the action item displayed may be "de-authentication".

[0108] It should be noted that in the specific display rules, regarding action items, in addition to configuring the name of the action item, you can also configure information such as the jump address corresponding to the specific action item. In this way, after the specific action item is displayed, if the user clicks on the specific action item, the jump address can be used to jump to the corresponding page for display, so that the user can complete the corresponding "action".

[0109] Regarding specific descriptions, they can also be configured differently based on different user usage scenarios. For example, if the target user has used the benefit item, the description includes: the number of times the target user has used the benefit item, the remaining number of times, and / or the usage effect information obtained, etc. If the target user has not used the benefit item, the description includes: summary information about the function description of the benefit item, etc. In addition, under the same user usage scenario, the descriptions that need to be displayed for different benefit items may be different. For example, if a user has used two benefit items, the description that needs to be displayed for one of the benefit items may be "X targets to be completed", and the description that needs to be displayed for the other benefit item may be "X reported this month", etc. These can all be configured in a rule-based manner, where the specific quantity information can be dynamically determined based on the actual usage of the specific user.

[0110] S203: According to the rights and interests data definition template, the user's data on multiple data fields of multiple rights and interests items are saved, wherein the data on the data fields related to the user's usage is determined based on the user's rights and interests item usage information and the data display rules.

[0111] Since the rights data definition template and data display rules are configured, the data of multiple users on multiple data fields of multiple rights items can be saved according to the template and data display rules. Among them, if it is split into the first template and the second template, then for the first template part, the data on each data field can be configured for each rights item respectively. These data usually do not need to be updated unless the name, icon, etc. of a certain rights item changes. In other words, the data on the fields related to the basic information of the rights items can be constructed through manual configuration and other methods. For example, the specific rights configuration item definition can be configured and designed in formats such as JSON (JavaScript Object Notation). After completing the data configuration on the basic information related fields of each rights item, it can be saved on the server side. For example, it can be saved through the configuration center server of the server side, and so on.

[0112] The data on the fields related to user usage can be specifically determined based on the user's rights and interests usage information and the data display rules. In a specific implementation, since each user's usage of rights and interests items may change dynamically, the data on the fields related to user usage may also change dynamically. To this end, under a preferred embodiment, the data on the fields related to user usage can be obtained and updated regularly by executing scheduled tasks. In a specific implementation, the user's usage data for each right and interest can be obtained from a data source such as a data base table that maintains user-dimensional feature data. The above-mentioned data base table can be maintained by a log system, etc.

[0113] Among them, the obtained data on the use of various rights and interests by users may specifically include whether the user has used a certain right item, the specific number of times a certain right item has been used, etc. These data can be directly obtained from the aforementioned data base table, or they can be obtained by processing the data in the data base table, and so on. In other words, if there are processed data indicators in the data base table, they can be used directly. If not, the aforementioned scheduled task can also process the data in the base table to obtain the user usage data indicators of the right items. For example, for a certain right item, it is necessary to obtain whether the user has participated in a certain activity. However, the data does not directly exist in the data base table. In this case, the scheduled task can use the data already in the data base table to count whether the user has participated in the activity, and so on. Among them, the specific scheduled task can implement the logic of processing the data in the base table through SQL (Structured Query Language) statements and the like.

[0114] After determining the user's usage data for the benefit items, it is possible to determine what information needs to be displayed in the fields related to the user's usage when displaying the specific benefit item to the user based on the aforementioned display rule information corresponding to the specific benefit item, such as specific descriptive text, action items, etc. For example, assuming that a user has used benefit item A, and benefit item A is related to quotation and has a limit on the number of uses, the text displayed can be "Quoted X times this month", and the action item can be "Go to quote", etc. Among them, the specific number of times "X" that has been quoted can also be obtained by the aforementioned scheduled task from the specific data base table (directly or after processing).

[0115] After obtaining data related to a user's usage of specific benefit items and determining the information that needs to be displayed in specific fields related to user usage based on the data display rules corresponding to each benefit item, a user-dimensional benefit item data table can be constructed (for example, this can be saved in the form of a vertical table). This data table can include benefit item data constructed for each user, such as descriptive text determined based on each user's usage of each benefit item (whether it has been used, the effectiveness of use, etc.), and action item information that needs to be displayed based on each user's usage of each benefit item, etc.

[0116] S204: In response to a request for viewing rights information initiated by a target user, the data of the target user on multiple data fields of the multiple rights items are read from the saved information, and assembled into display contents corresponding to the multiple rights items, so as to display the display contents corresponding to the multiple rights in the target page.

[0117] Since the data required to be displayed on each field of the user-dimensional rights and interests items have been obtained in advance, when it is necessary to display rights and interests information to a specific target user, the data of the target user on multiple data fields of the multiple rights and interests items can be read from the saved data and assembled into display content corresponding to the multiple rights and interests items.

[0118] Among them, if it is disassembled into two parts according to the aforementioned first template and second template, the data of multiple rights items in the data fields related to the basic information can be first obtained from the rights configuration information, and the data of the target user on the multiple rights items in the data fields related to the user usage can be obtained from the rights usage related data; then, the data of the multiple rights items in the data fields related to the basic information and the data in the data fields related to the user usage are assembled to generate the display content corresponding to the multiple rights items.

[0119] It should be noted that the specific equity configuration information may also include a sorting index field corresponding to the equity items. The data in this field may include the sorting order number of the specific equity item. In this case, the display content corresponding to the multiple equity items may also be sorted according to the data in the sorting index field so that they are displayed in the corresponding order on the target page.

[0120] For example, when displaying, as shown in Figure 3, the information of various rights and interests items corresponding to the current target user can be displayed. Among them, the rights and interests item shown at 31 is named "Industry Business Guidance". Since the current target user has already used this rights and interests item, the displayed text is "2 goals to be completed" (wherein, the number "2" can change dynamically to prompt the user's use of the rights and interests item), and the action item is "Go to check"; the rights and interests item shown at 32 is named "Management Certificate". Since the current target user has not used this rights and interests item, the displayed text is "Management System Certificate", and the action item can be "Go to verify", and so on.

[0121] Among them, the icons of specific rights items can also be interactive. When performing interactive operations such as clicking, some detailed description information of the rights items can be displayed through pop-up windows / floating layers. For example, when clicking the icon of the "L2+ Self-Marketing" rights item, a pop-up window as shown in Figure 4 can be displayed, which can display more detailed information about the rights item; when clicking the "RFQ" rights item, a pop-up window as shown in Figure 5 can be displayed, which can display detailed information about the rights item, etc.

[0122] Furthermore, when new equity items are added, deleted, or their data is updated, only the configuration information needs to be updated. For example, in the case of a new equity item, the data for each field of the new equity item can be configured according to the aforementioned template, without the need to develop new processing logic. Therefore, this solution has greater scalability.

[0123] It should also be noted that in the embodiments of this application, multiple benefit items can share the same processing logic for display. However, in a specific application system, there may be multiple different membership types, and different membership types may correspond to different benefit items. In addition, some benefit items may have special requirements when displaying, etc. Therefore, in a specific implementation, different processing logic can be implemented for different membership types. In this way, when displaying benefit items for a target user, it is possible to first determine which membership type the current target user belongs to, and then call the processing logic corresponding to that type for processing.

[0124] In summary, through the embodiments of the present application, the display information of multiple different rights and interests items can be standardized and decomposed and extracted into a standardized template. In the template, the data that needs to be displayed for the rights and interests items can be split into data fields related to basic information and data fields related to user usage. At the same time, data display rules for the fields related to user usage corresponding to multiple rights and interests items under different user usage conditions can also be configured. Afterwards, the user's data on multiple data fields of multiple rights and interests items can be saved according to the rights and interests data definition template. Among them, the data on the fields related to user usage can be determined based on the user's usage information of the multiple rights and interests items and the aforementioned data display rules. In this way, after the target user initiates a request to view the rights and interests information, the data of the target user on multiple data fields of the multiple rights and interests items can be read from the saved information and assembled into the display content corresponding to the multiple rights and interests items for display on the target page. In this way, information of multiple different rights and interests items can be aggregated and displayed on the same page, and information related to user usage can be displayed. During the implementation process, although the information that needs to be conveyed in the same field for each benefit item may be different and related to the specific user's usage of the corresponding benefit item, since the data fields corresponding to each benefit item are uniformly defined and the data to be displayed for different users in multiple fields of each benefit item can be obtained in advance, when it needs to be displayed to the user, the same processing logic can be used to process and complete the data assembly. Accordingly, only the same set of processing logic needs to be developed to complete the display of multiple different benefit items, thereby achieving the purpose of reducing development costs.

[0125] In addition, when equity items are added, deleted, or information is updated, only the specific configuration information needs to be updated. For example, for newly added equity items, it is only necessary to configure the data on each field according to the aforementioned template, without the need to develop new processing logic separately. Therefore, this solution has stronger scalability.

[0126] In a preferred embodiment, not only can the data related to the rights and interests items be split into two parts, namely the data in the fields related to basic information and the data in the fields related to user usage, but a first template and a second template can also be provided for each of these two parts. In this way, only the data in the fields related to user usage needs to be saved in the user dimension and dynamically updated, while the data in the fields related to basic information only needs to be saved for each rights and interests item, rather than for each user, thereby saving storage space.

[0127] Example 2

[0128] The second embodiment corresponds to the first embodiment and provides a method for displaying rights information from the perspective of the client. Referring to FIG6 , the method may include:

[0129] S601: Receive a request from a target user to view rights information;

[0130] S602: Display a target page, wherein the target page includes display content corresponding to a plurality of benefit items, wherein the display content is generated by a same processor module reading and assembling data of the target user in a plurality of data fields of the plurality of benefit items;

[0131] Among them, the data of the target user in multiple data fields of the multiple rights and interests items are determined according to the rights and interests data definition template, including data fields related to basic information and data fields related to user usage. The data in the data fields related to user usage is determined based on the user's rights and interests item usage information and the data display rules.

[0132] Specifically, the display content corresponding to the multiple rights and interests items includes: action item information corresponding to the rights and interests items, and the action item information includes the name of the action item and the jump address, so as to jump to the corresponding page according to the jump address to obtain detailed information related to the rights and interests item, or perform processing related to the rights and interests item; wherein, different rights and interests items correspond to different action items under the same user usage situation.

[0133] For details not described in the second embodiment, please refer to the first embodiment and other parts of this specification, which will not be repeated here.

[0134] It should be noted that the embodiments of the present application may involve the use of user data. In actual applications, user-specific personal data can be used in the scheme described herein within the scope permitted by applicable laws and regulations, subject to the requirements of applicable laws and regulations of the country where the user is located (for example, with the user's explicit consent, effective notification to the user, etc.).

[0135] Corresponding to the first embodiment, the embodiment of the present application further provides a device for displaying rights and interests information. Referring to FIG7 , the device may include:

[0136] The template acquisition unit 701 is configured to acquire a rights and interests data definition template, wherein the rights and interests data definition template includes a plurality of data fields, including data fields related to basic information and data fields related to user usage;

[0137] The data display rule acquisition unit 702 is used to acquire data display rule information on data fields related to user usage conditions corresponding to multiple benefit items under different user usage conditions;

[0138] The data acquisition unit 703 is configured to save the user's data in multiple data fields of multiple benefit items according to the benefit data definition template, wherein the data in the data fields related to the user's usage is determined based on the user's benefit item usage information and the data display rules;

[0139] The display content construction unit 704 is used to respond to a request for viewing rights information initiated by a target user, read the data of the target user on multiple data fields of the multiple rights items from the saved information, and assemble them into display contents corresponding to the multiple rights items, so as to display the display contents corresponding to the multiple rights items on the target page.

[0140] The fields related to user usage include: description text and / or action items required to be displayed when displaying benefit items;

[0141] At this time, the data display rule acquisition unit can be specifically used to: obtain description copy and / or action item display rule information corresponding to multiple benefit items under different user usage situations; wherein each benefit item corresponds to a different candidate copy and / or candidate action item, and the data display rule information includes: the correspondence between each candidate copy and / or candidate action item of the same benefit item and the user usage situation;

[0142] The data acquisition unit can be specifically used to: obtain usage information of the multiple rights items by multiple users respectively, and determine the corresponding description text and / or action items to be displayed when the rights items are displayed to each user based on the usage information and the data display rules, and save them as data in the corresponding data fields.

[0143] The action item information includes the name of the action item and a jump address, so as to jump to the corresponding page according to the jump address to obtain detailed information related to the benefit item, or perform processing related to the benefit item.

[0144] If the target user has used the benefit item, the description text includes: the number of times the target user has used the benefit item, the remaining number of times and / or information on the use effect obtained.

[0145] If the target user has not used the benefit item, the description text includes: functional description summary information about the benefit item.

[0146] Among them, the data acquisition unit can specifically obtain the usage information of the multiple rights items by multiple users by executing a scheduled task, and determine the data on the data field related to the user's usage when displaying the rights items to each user based on the usage information and the data display rules.

[0147] The rights and interests data definition template includes: a first template and a second template, wherein the first template is used to define data fields related to the rights and interests items and basic information, and the second template is used to define data fields related to multiple rights and interests items and user usage;

[0148] At this time, the data acquisition unit can be specifically used to:

[0149] According to the first template, data on data fields related to the plurality of equity items and the basic information are saved as equity configuration information;

[0150] According to the second template, data on the data fields related to the plurality of benefit items and user usage are saved as benefit usage related data information;

[0151] The display content assembly unit can be specifically used for:

[0152] In response to a request for viewing rights information initiated by the target user, obtaining data on data fields related to basic information of the plurality of rights items from the rights configuration information;

[0153] Acquire data of the target user on data fields related to user usage of the plurality of benefit items from the benefit usage related data;

[0154] The data of the multiple rights items in the data fields related to the basic information and the data in the data fields related to the user usage are assembled to generate display content corresponding to the multiple rights items respectively.

[0155] Specifically, if there are multiple different membership types, the display content assembly unit can be specifically used to: determine the membership type information corresponding to the target user; obtain data on multiple rights and interests items corresponding to the membership type in data fields related to basic information from the rights and interests configuration information.

[0156] In addition, different membership types can also correspond to different processor modules. At this time, the display content assembly unit can also be specifically used to: after determining the membership type information corresponding to the target user, determine the corresponding processor module according to the membership type information, so that the processor module can read and assemble the data.

[0157] The equity configuration information may further include a sorting index field corresponding to the equity item;

[0158] At this time, the device may further include:

[0159] The sorting unit is used to sort the display contents corresponding to the multiple rights and interests items according to the data on the sorting index field, so as to display them in the corresponding order on the target page.

[0160] When a benefit item is added, deleted, or information is updated, the benefit configuration information and / or benefit usage-related data information are updated to update the displayed benefit item and / or corresponding display content.

[0161] Corresponding to the second embodiment, the embodiment of the present application further provides a device for displaying rights and interests information. Referring to FIG8 , the device may include:

[0162] The request receiving unit 801 is used to receive a request from a target user to view rights information;

[0163] A page display unit 802 is configured to display a target page, wherein the target page includes display content corresponding to a plurality of benefit items, wherein the display content is generated by assembling and reading data of the target user in a plurality of data fields of the plurality of benefit items by a same processor module;

[0164] Among them, the data of the target user in multiple data fields of the multiple rights and interests items are determined according to the rights and interests data definition template, including data fields related to basic information and data fields related to user usage. The data in the data fields related to user usage is determined based on the user's rights and interests item usage information and the data display rules.

[0165] The display contents corresponding to the multiple rights and interests items include:

[0166] The action item information corresponding to the benefit item includes the name of the action item and the jump address, so as to jump to the corresponding page according to the jump address to obtain detailed information related to the benefit item, or perform processing related to the benefit item; wherein different benefit items correspond to different action items under the same user usage situation.

[0167] In addition, an embodiment of the present application further provides a computer-readable storage medium on which a computer program is stored. When the program is executed by a processor, the steps of any one of the methods in the aforementioned method embodiments are implemented.

[0168] And an electronic device comprising:

[0169] one or more processors; and

[0170] A memory associated with the one or more processors, the memory being used to store program instructions, wherein the program instructions, when read and executed by the one or more processors, execute the steps of the method described in any one of the aforementioned method embodiments.

[0171] 9 exemplarily illustrates the architecture of an electronic device, which may include a processor 910, a video display adapter 911, a disk drive 912, an input / output interface 913, a network interface 914, and a memory 920. The processor 910, the video display adapter 911, the disk drive 912, the input / output interface 913, the network interface 914, and the memory 920 may be communicatively connected via a communication bus 930.

[0172] Among them, the processor 910 can be implemented by a general-purpose CPU (Central Processing Unit, processor), a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits, and is used to execute relevant programs to implement the technical solutions provided in this application.

[0173] The memory 920 can be implemented in the form of ROM (Read Only Memory), RAM (Random Access Memory), static storage devices, dynamic storage devices, etc. The memory 920 can store an operating system 921 for controlling the operation of the electronic device 900 and a basic input and output system (BIOS) for controlling the low-level operations of the electronic device 900. In addition, a web browser 923, a data storage management system 924, and a rights and interests information display processing system 925, etc. can also be stored. The above-mentioned rights and interests information display processing system 925 can be an application program that specifically implements the operations of the aforementioned steps in the embodiment of the present application. In short, when the technical solution provided by the present application is implemented by software or firmware, the relevant program code is stored in the memory 920 and is called and executed by the processor 910.

[0174] The input / output interface 913 is used to connect input / output modules to implement information input and output. The input / output modules can be configured as components in the device (not shown in the figure) or can be externally connected to the device to provide corresponding functions. Input devices may include a keyboard, mouse, touch screen, microphone, various sensors, etc., and output devices may include a display, speaker, vibrator, indicator light, etc.

[0175] The network interface 914 is used to connect to a communication module (not shown) to enable communication between the device and other devices. The communication module can communicate via a wired method (such as USB, network cable, etc.) or a wireless method (such as mobile network, WiFi, Bluetooth, etc.).

[0176] The bus 930 comprises a pathway for transmitting information between the various components of the device (eg, the processor 910 , the video display adapter 911 , the disk drive 912 , the input / output interface 913 , the network interface 914 , and the memory 920 ).

[0177] It should be noted that although the above device only shows the processor 910, video display adapter 911, disk drive 912, input / output interface 913, network interface 914, memory 920, bus 930, etc., in the specific implementation process, the device may also include other components necessary for normal operation. In addition, it will be understood by those skilled in the art that the above device may also include only the components necessary to implement the solution of the present application, and does not necessarily include all the components shown in the figure.

[0178] Through the description of the above embodiments, it can be seen that those skilled in the art can clearly understand that the present application can be implemented by means of software plus a necessary general hardware platform. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art, can be embodied in the form of a software product, which can be stored in a storage medium such as ROM / RAM, a magnetic disk, an optical disk, etc., and includes a number of instructions for enabling a computer device (which can be a personal computer, a server, or a network device, etc.) to execute the methods described in various embodiments of the present application or certain parts of the embodiments.

[0179] Each embodiment in this specification is described in a progressive manner. The same or similar parts between the embodiments can be referred to each other. Each embodiment focuses on the differences from other embodiments. In particular, for system or system embodiments, since they are basically similar to method embodiments, the description is relatively simple. For relevant parts, refer to the partial description of the method embodiment. The system and system embodiments described above are merely schematic, wherein the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the modules can be selected according to actual needs to achieve the purpose of the solution of this embodiment. A person of ordinary skill in the art can understand and implement it without expending creative work.

[0180] The above describes in detail the method and electronic device for displaying rights information provided by this application. Specific examples are used herein to illustrate the principles and implementation methods of this application. The description of the above embodiments is intended only to help understand the method and core concept of this application. At the same time, those skilled in the art will appreciate that the specific implementation methods and scope of application may vary based on the concept of this application. In summary, the contents of this specification should not be construed as limiting this application.

Claims

1. A method for displaying equity information, characterized in that: include: Acquire a rights and interests data definition template, wherein the rights and interests data definition template includes a plurality of data fields, wherein the plurality of data fields include a data field related to basic information and a data field related to user usage; Obtain data display rule information on data fields related to user usage corresponding to multiple benefit items under different user usage conditions; According to the rights and interests data definition template, the data of the user in multiple data fields of multiple rights and interests items are saved, wherein the data in the data fields related to the user's usage is determined according to the user's rights and interests item usage information and the data display rule information; In response to a request initiated by a target user to view rights and interests information, the data of the target user on multiple data fields of the multiple rights and interests items are read from the saved information and assembled into display contents corresponding to the multiple rights and interests items respectively, so as to display the display contents corresponding to the multiple rights and interests items respectively in the target page.

2. The method according to claim 1, characterized in that For fields related to user usage, different benefit items correspond to different candidate values ​​for the same field; The data display rule information specifically includes: the correspondence between the candidate values ​​of the same benefit item in the same field and the user's usage, so as to determine the data to be displayed for the corresponding benefit item in the corresponding field from the candidate values ​​of the corresponding benefit item in the corresponding field according to the usage information of the specific user.

3. The method according to claim 2, characterized in that The fields related to user usage include: description text and / or action items to be displayed when displaying benefit items; The obtaining of data display rule information on data fields related to user usage corresponding to the plurality of rights and interests items under different user usage situations includes: Obtaining description texts and / or action item display rule information corresponding to a plurality of benefit items under different user usage situations; wherein each benefit item corresponds to a different candidate text and / or candidate action item, and the data display rule information includes: a correspondence between each candidate text and / or candidate action item of the same benefit item and the user usage situation; The step of saving data of multiple users in multiple data fields of multiple rights and interests items according to the rights and interests data definition template includes: Obtain usage information of the multiple benefit items by multiple users respectively, and determine the corresponding description text and / or action items to be displayed when displaying the benefit items to each user based on the usage information and the data display rules, and save them as data in the corresponding data fields.

4. The method according to claim 3, characterized in that The action item information includes the name of the action item and a jump address, so as to jump to a corresponding page according to the jump address to obtain detailed information related to the benefit item, or perform processing related to the benefit item.

5. The method according to claim 3, characterized in that: If the target user has used the benefit item, the description text includes: the number of times the target user has used the benefit item, the remaining number of times and / or information on the use effect obtained.

6. The method according to claim 3, characterized in that If the target user has not used the benefit item, the description text includes: functional description summary information about the benefit item.

7. The method according to claim 1, characterized in that By executing scheduled tasks, the usage information of the multiple benefit items by multiple users is obtained, and based on the usage information and the data display rules, the data corresponding to the data field related to the user's usage is determined when the benefit items are displayed to each user.

8. The method according to any one of claims 1 to 7, characterized in that: The rights and interests data definition template includes: a first template and a second template, wherein the first template is used to define data fields related to the rights and interests items and basic information, and the second template is used to define data fields related to multiple rights and interests items and user usage conditions; The step of saving data of multiple users in multiple data fields of multiple rights and interests items according to the rights and interests data definition template includes: According to the first template, data on the data fields of the plurality of equity items and the basic information are saved as equity configuration information; According to the second template, data on the data fields related to the plurality of benefit items and user usage are saved as benefit usage related data information; When responding to the request for viewing the rights and interests information initiated by the target user, it includes: Acquire data of the plurality of equity items in data fields related to the basic information from the equity configuration information; Acquire data of the target user on data fields related to user usage of the plurality of benefit items from the benefit usage related data; The data of the multiple rights and interests items in the data fields related to the basic information and the data of the data fields related to the user usage are assembled to generate display contents corresponding to the multiple rights and interests items respectively.

9. The method according to claim 8, characterized in that The acquiring data of the plurality of equity items in data fields related to basic information from the equity configuration information includes: Determine the membership type information corresponding to the target user; The data of the multiple rights and interests items corresponding to the member type in the data fields related to the basic information are obtained from the rights and interests configuration information.

10. The method according to claim 9, characterized in that Different membership types correspond to different processor modules; After determining the membership type information corresponding to the target user, the following further includes: The corresponding processor module is determined according to the member type information, so that the processor module can read and assemble the data.

11. The method according to claim 8, characterized in that The equity configuration information includes a sorting index field corresponding to the equity item; The method further comprises: According to the data on the sorting index field, the display contents corresponding to the multiple rights and interests items are sorted so as to be displayed in the target page in a corresponding order.

12. A method for displaying equity information, characterized in that: include: Receive a request from a target user to view rights information; Displaying a target page, wherein the target page includes display contents corresponding to a plurality of rights and interests items, respectively, and the display contents are generated by reading and assembling the data of the target user on a plurality of data fields of the plurality of rights and interests items by the same processor module; Among them, the data of the target user in multiple data fields of the multiple rights and interests items are determined according to the rights and interests data definition template, including data fields related to basic information and data fields related to user usage. The data in the data fields related to user usage is determined based on the user's rights and interests item usage information and the data display rules.

13. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the program is executed by a processor, the steps of the method described in any one of claims 1 to 12 are implemented.

14. An electronic device, characterized in that: include: one or more processors; as well as A memory associated with the one or more processors, the memory being used to store program instructions, wherein the program instructions, when read and executed by the one or more processors, execute the steps of the method described in any one of claims 1 to 12.

Images