Method and system for issuing rights and interests
By introducing business modules and equity platforms into the equity management system, and obtaining and recording equity sending parameters based on user orders, the problem that the existing system cannot manage complex equity structures is solved, and the efficiency of equity distribution and user experience are improved.
Patent Information
- Application Number
- CN202411783477.1
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-12-05
- Publication Date
- 2025-04-15
AI Technical Summary
The existing equity management system cannot effectively support multi-level and complex equity structures, especially when sharing equity among family members, it cannot flexibly allocate and manage, and at the same time it cannot be compatible with different types of equity, which reduces the operational efficiency of equity.
Provide a method and system for issuing rights and interests. Through business modules and rights and interests platforms, the rights and interests are obtained according to the orders for users to purchase rights and interests, the rights and interests data of the target rights and interests are determined, and recorded in the corresponding rights and interests data table, so as to realize unified management of user rights and interests of multiple attributable parties.
It improves the efficiency of equity distribution and operation, realizes flexible management of multi-level and complex equity structures, and improves user experience.
Smart Images
Figure CN119831650A_ABST
Abstract
Description
Technical Field
[0001] The present disclosure relates to the field of computer software technology, and in particular to a method and system for issuing rights and interests. Background Art
[0002] Rights refer to the rights and interests that consumers enjoy after purchasing goods or services. Existing rights and interests management systems are often limited to a single type of rights and interests management, such as personal rights and interests or device rights and interests, and fail to effectively support multi-level and complex rights and interests structures. For example, family members may need to share certain rights and interests, such as family packages, shared device usage rights, etc., but these rights and interests are often not flexibly configured and managed in existing systems.
[0003] At the same time, with the development of technology, user needs are becoming increasingly diversified, and more and more consumers hope to manage the rights and interests of individuals, family members and devices on one platform. The existing rights and interests system cannot flexibly accommodate different types of rights and interests, which reduces the operational efficiency of rights and interests. Summary of the invention
[0004] In view of this, the present disclosure provides a method and system for equity issuance, which can effectively improve the efficiency of equity issuance and operation.
[0005] According to a first aspect of an embodiment of the present disclosure, a method for issuing rights and interests is provided, the method being executed by a rights and interests sending system, the rights and interests sending system comprising: a business module and a rights and interests platform; the method comprising:
[0006] The business module obtains the rights and interests sending parameters corresponding to the target rights and interests purchased by the user based on the rights and interests order of the user, and the rights and interests sending parameters include: the rights and interests identifier of the target rights and interests, and the identifier of the party to which the target rights and interests belong; the identifier of the party to which the target rights and interests belong is used to indicate that the party to which the target rights and interests belong is an individual, a family or a device;
[0007] The equity platform determines the equity data of the target equity according to the equity identifier of the target equity;
[0008] The rights and interests platform records the rights and interests data in a rights and interests data table corresponding to the ownership identifier.
[0009] In one embodiment, the equity platform determines the equity data of the target equity according to the equity identifier of the target equity, including:
[0010] The equity platform acquires a preset configuration data table corresponding to the equity identifier according to the equity identifier, wherein the preset configuration data table at least includes: the equity name of the target equity corresponding to the equity identifier, and the equity duration;
[0011] The equity platform determines the start time and end time of the target equity according to the equity duration;
[0012] The equity platform determines the equity data of the target equity, and the equity data includes: equity name, start time and end time.
[0013] In one embodiment, the equity sending parameter includes: an identifier of a party to which the target equity belongs;
[0014] The business module obtains the equity sending parameters corresponding to the target equity purchased by the user based on the equity order of the user purchasing the equity, including:
[0015] The business module queries a preset equity category table based on the equity name of the target equity to determine the category of the party to which the target equity belongs, wherein the equity category table at least includes the equity name and the equity category corresponding to the equity name;
[0016] When the attribution party category is an individual, the service module determines the user ID as the attribution party identifier according to the login information of the user;
[0017] When the category of the attributable party is a device, the business module determines a device code as the attributable party identifier according to the device of the user purchasing the target benefit;
[0018] When the belonging party category is family, the service module determines the family ID as the belonging party identifier according to the family information of the user.
[0019] In one embodiment, the preset configuration data table further includes: equity priority;
[0020] The equity platform records the equity data in the equity data table corresponding to the ownership identifier, including:
[0021] The equity platform determines the processing order of the target equity based on the equity priority;
[0022] The equity platform records the equity data of the target equity into the target equity data table through a message queue according to the processing order and the ownership identifier.
[0023] In one embodiment, the method further comprises:
[0024] If the equity platform fails to record the equity data of the target equity into the target equity data table, obtaining the number of issuances of the target equity;
[0025] If the number of issuances of the target rights is less than the first preset threshold, the rights sending parameters corresponding to the target rights purchased by the user are re-acquired, and the rights data of the target rights are recorded in the rights data table corresponding to the ownership identifier through the rights platform.
[0026] In one embodiment, the rights and interests data table includes: an individual data table and an overall data table, wherein the individual data table is used to record the rights and interests data corresponding to each attribution party identification, and the overall data table is used to record the rights and interests data corresponding to each attribution party category.
[0027] In one embodiment, the equity sending parameter further includes: an equity sender identifier; the equity sender identifier is used to identify the business module;
[0028] After the equity platform records the equity data in the equity data table corresponding to the ownership identifier, the method further includes:
[0029] The rights and interests platform obtains the rights and interests sender identifier;
[0030] If the rights sender identifier belongs to the preset business party code, the rights platform sends a callback notification to the business module;
[0031] The business module updates the equity order status according to the callback notification and pushes the equity notification to the user.
[0032] In one embodiment, if the equity sender identifier belongs to a preset business party code, the equity platform sends a callback notification to the business module, including:
[0033] The rights and interests platform generates a notification issuance request according to the issuer identifier;
[0034] The rights and interests platform pushes the notification issuance request to a message queue, and calls an interface of the rights and interests platform through the message queue;
[0035] The rights and interests platform sends a callback notification to the business module according to the interface of the rights and interests platform.
[0036] In one embodiment, the method further comprises:
[0037] If the rights platform fails to send a callback notification to the business module, the number of times the rights notification is issued is obtained;
[0038] If the number of issuances of the rights and interests notification is less than a second preset threshold, the rights and interests platform resends a callback notification to the business module.
[0039] According to a second aspect of the embodiments of the present disclosure, a rights issuance system, a business module and a rights platform are provided;
[0040] The business module is used to obtain the rights and interests sending parameters corresponding to the target rights and interests purchased by the user according to the rights and interests order of the user; the rights and interests sending parameters include: the rights and interests identifier of the target rights and interests, and the identifier of the party to which the target rights and interests belong; the identifier of the party to which the target rights and interests belong is used to indicate that the party to which the target rights and interests belong is an individual, a family or a device;
[0041] The equity platform is used to record the equity data of the target equity into the equity data table corresponding to the ownership identifier according to the equity sending parameter.
[0042] The technical solution provided by the embodiments of the present disclosure may have the following beneficial effects:
[0043] Based on the rights and interests order of the user's rights and interests purchase, the business module determines the rights and interests sending parameters corresponding to the target rights and interests, and determines the rights and interests data according to the identification of the target rights and interests through the rights and interests platform, and finally records the rights and interests data table corresponding to the rights and interests issuance parameters, realizing the unified management of user rights and interests of multiple parties. After the user purchases the rights and interests, the rights and interests can be automatically issued according to the rights and interests issuance parameters, which improves the efficiency of the rights and interests method and enhances the user experience. BRIEF DESCRIPTION OF THE DRAWINGS
[0044] Figure 1 is a flow chart of a method for issuing rights and interests shown in an exemplary embodiment of the present disclosure;
[0045] Figure 2 is a flow chart of a method for obtaining a home party identifier shown in an exemplary embodiment of the present disclosure;
[0046] Figure 3 is a flow chart of a method for determining equity data shown in an exemplary embodiment of the present disclosure;
[0047] Figure 4 is a flow chart of a method for recording equity data shown in an exemplary embodiment of the present disclosure;
[0048] Figure 5 is a flow chart of another method for recording equity data shown in an exemplary embodiment of the present disclosure;
[0049] Figure 6 is a flow chart of a method for retrying to record equity data shown in an exemplary embodiment of the present disclosure;
[0050] Figure 7 is a flowchart of a method for performing callback notification shown in an exemplary embodiment of the present disclosure;
[0051] Figure 8 is a flow chart of a method for sending a callback notification shown in an exemplary embodiment of the present disclosure;
[0052] Fig. 9 The figure is a flow chart of a method for retrying to send a callback notification, shown as an exemplary embodiment of the present disclosure. DETAILED DESCRIPTION
[0053] Exemplary embodiments will be described in detail herein, examples of which are shown in the accompanying drawings. When the following description refers to the drawings, the same numbers in different drawings represent the same or similar elements unless otherwise indicated. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present disclosure. Instead, they are merely examples of devices and methods consistent with some aspects of the present disclosure as detailed in the appended claims.
[0054] The terms used in this disclosure are for the purpose of describing specific embodiments only and are not intended to limit the disclosure. The singular forms of "a", "said" and "the" used in this disclosure and the appended claims are also intended to include plural forms unless the context clearly indicates otherwise. It should also be understood that the term "and / or" used herein refers to and includes any or all possible combinations of one or more associated listed items.
[0055] It should be understood that although the terms first, second, third, etc. may be used in the present disclosure to describe various information, such information should not be limited to these terms. These terms are only used to distinguish the same type of information from each other. For example, without departing from the scope of the present disclosure, the first information may also be referred to as the second information, and similarly, the second information may also be referred to as the first information. Depending on the context, the word "if" as used herein may be interpreted as "at the time of" or "when" or "in response to determining".
[0056] Current rights issuance systems usually only support a single type of rights (such as personal or device rights), and cannot effectively manage rights at multiple levels of family, personal, and device at the same time. In addition, in the rights method system, the rights issuance is tightly coupled with the user notification logic, resulting in any notification failure during the issuance process that may affect the timely issuance of rights, increasing the instability of rights issuance. This coupling design easily leads to system delays and difficulty in error handling.
[0057] Based on this, the present disclosure provides a method for issuing rights, which is executed by a rights sending system, and the rights sending system includes: a business module and a rights platform. The rights platform is a platform for managing user rights in a backend server. The business module can interact with the user through a client and provide the user with rights order information for the user to purchase rights. The rights issuing system can be applied to learning devices (such as learning machine tablets) in the field of education and related systems.
[0058] Figure 1 A flowchart of a method for issuing rights is shown, the flowchart comprising the following steps:
[0059] S101, the business module obtains the rights and interests sending parameters corresponding to the target rights and interests purchased by the user based on the rights and interests order of the user to purchase the rights and interests.
[0060] The rights sending parameters include: the rights identification of the target rights, and the owner identification of the target rights; the owner identification is used to indicate that the rights holder to whom the target rights belong is an individual, a family or a device. For example, in the rights issuance system, a number can be pre-assigned to each user or each family to determine the user identity or family information, and each device can determine the device information based on the SN (Serial Number) code carried by the device itself.
[0061] The user can purchase the rights and interests through the client and generate a rights and interests order. After the user purchases the rights and interests order, the business module will purchase the rights and interests order of the target rights and interests according to the rights and interests order, and generate the rights and interests identification of the target rights and interests according to the rights and interests order. At the same time, the category of the target rights and interests is determined, for example, the category of the belonging party is a family. Then, the identification of the belonging party of the target rights and interests is automatically extracted, and the identity of the rights and interests holder is accurately determined according to the identification of the belonging party, so as to flexibly distribute the rights and interests.
[0062] For example, a user purchases screen-breaking insurance benefits in the client application interface and generates a screen-breaking insurance order. The business module can determine that the category of the party to which the benefits belong is the device based on the screen-breaking insurance order. Then, the SN code of the device for which the user purchased the screen-breaking insurance benefits is extracted. This determines which specific device has the screen-breaking insurance benefits, and then issues the screen-breaking insurance benefits to the device.
[0063] In some embodiments, reference may be made to Figure 2 The method of the flowchart shown in the figure obtains the attribution identifier of the target equity, and the flowchart may include the following steps:
[0064] S201, the business module searches a preset equity category table based on the equity name of the target equity to determine the category of the party to which the target equity belongs.
[0065] S202: When the category of the attribution party is an individual, the service module determines a user ID as the attribution party identifier according to the login information of the user.
[0066] S203: When the category of the attributable party is a device, the business module determines a device code as the attributable party identifier according to the device used by the user to purchase the target benefit.
[0067] S204: When the category of the belonging party is family, the service module determines a family ID as the belonging party identifier according to the family information of the user.
[0068] The equity category table at least includes the equity name and the equity category corresponding to the equity name. The business module can query the preset equity category table according to the equity name of the target equity purchased by the user. In the equity category table, the equity name corresponds to the equity attribution party category one by one, so the attribution party category of the target equity can be determined according to the equity name. After the equity attribution party category is determined, the attribution party identifier can be extracted according to the order information of the user purchasing the target equity.
[0069] If the target benefit is classified as an individual, then the user ID can be extracted as the identifier of the owner based on the user information of the currently logged-in user in the business module when the user purchases the target benefit. If the target benefit is classified as a device, then the business module can extract the SN code of the device as the identifier of the owner based on the device information selected by the user when purchasing the target benefit. If the target benefit is classified as a family, then the business module can obtain the family ID as the identifier of the owner based on the family information of the family of the currently logged-in user. The family information refers to the member information of each family, such as parent information, number of children, and age information and grade information of each child. A family can configure a corresponding family ID in the business module. Family members of the same family have the same family ID, and the information of family members in each family can be determined based on the family ID.
[0070] In this way, the identification of different categories of owners can be extracted to determine the recipients of the target rights. By classifying and managing the rights owners in multiple dimensions such as individuals, devices, and families, the flexibility of the rights distribution system in managing user rights can be improved.
[0071] S102: The equity platform determines the equity data of the target equity according to the equity identifier of the target equity.
[0072] After the business module obtains the equity issuance parameters, the equity method parameters can be pushed to the Kafka message queue. Kafka is a distributed, high-throughput, and highly scalable message queue system. The issuance operation of the target equity is processed through the message queue, and the parallel mechanism of the message queue can quickly process the issuance task of the target equity. After the equity issuance parameters are pushed into the message queue, the message queue calls the interface of the equity platform and performs the equity issuance logic through the equity platform. The equity platform supports flexible configuration of interface calls under different business scenarios. The platform stores pre-configured equity basic data of multiple categories, which at least include information such as equity name, validity period, equity duration, and equity priority. After the configuration of the equity platform is completed, the equity basic data can be written to the database and updated to the cache middleware at the same time, and the validity of the cache can be ensured through the real-time update mechanism. By querying the equity basic data, the configuration data table of each equity can be obtained.
[0073] When the equity platform performs the equity issuance logic, first query the cache middleware according to the equity identifier of the target equity to determine the equity data of the target equity. If the equity data of the target equity is not stored in the cache middleware, the database can be queried to obtain the equity data of the target equity, and the result of the database query can be synchronously updated to the cache middleware. The specific information of the target equity can be determined based on the queried equity data, so that the equity data of the target equity can be recorded in the equity data table later to realize the issuance of the target equity.
[0074] Figure 3 A flowchart for determining equity data of a target equity is schematically shown, and the flowchart includes the following steps:
[0075] S301, the rights and interests platform obtains a preset configuration data table corresponding to the rights and interests identifier according to the rights and interests identifier.
[0076] S302, the equity platform determines the start time and end time of the target equity according to the equity duration.
[0077] S303: The equity platform determines the equity data of the target equity.
[0078] The preset configuration data table at least includes: the rights and interests name of the target rights and interests corresponding to the rights and interests identifier, and the rights and interests duration. The rights and interests data includes: the rights and interests name, the start time and the end time.
[0079] The equity platform can determine the configuration data table corresponding to the equity identifier in the pre-configured equity basic data according to the equity identifier in the equity issuance parameters. Further, according to the equity duration in the equity data table, the start time and end time of the target equity are determined. For example, the target equity purchased by the user is the membership equity. According to the membership equity identifier purchased by the user, the equity basic data is queried to determine that the duration of the membership equity is one month. Based on the date when the user purchases the membership equity, the start time and end time of the membership equity can be determined, thereby determining the equity data of the target equity.
[0080] S103, the rights and interests platform records the rights and interests data into the rights and interests data table corresponding to the ownership identifier.
[0081] After the rights and interests platform determines the rights and interests data of the target rights and interests, the rights and interests data can be processed according to the rights and interests data, that is, the rights and interests data can be recorded in the rights and interests data table. Specifically, the rights and interests data table corresponding to the target rights and interests purchased by the user can be determined according to the owner identifier of the target rights and interests. The rights and interests data table includes: an individual data table and an overall data table, wherein the individual data table is used to record the rights and interests data corresponding to each owner identifier, and the overall data table is used to record the rights and interests data corresponding to each owner category. For example, the overall data table may include a personal rights and interests data table, a device rights and interests data table, and a family rights and interests data table. The personal rights and interests data table records all personal rights and interests in the rights and interests issuance system, such as membership; the device rights and interests data table records all device rights and interests in the rights and interests issuance system, such as broken screen insurance rights; the family rights and interests data table records all family rights and interests in the rights and interests issuance system, such as reading unlock rights and interests. After a user purchases the reading unlock function, all his family members can enjoy the reading unlock rights and interests in their own accounts. The individual data table may include a personal rights and interests cache table, a device rights and interests cache table, and a family rights and interests cache table. The personal rights cache table records all the rights of a user, such as the membership rights and course rights owned by a user; the device rights cache table records all the rights of a device, such as the screen breakage insurance rights and warranty rights of a device; the family rights cache table records all the rights of a family, such as the reading unlocking rights and article translation rights of a family.
[0082] The rights and interests platform can then record the rights and interests data such as the rights and interests name, start time and end time of the target rights and interests purchased by the user into the rights and interests data table corresponding to the ownership identifier, so as to realize the issuance of the target rights and interests.
[0083] When the equity platform records the equity data to the corresponding equity data table, it is implemented through a message queue. When the message opposition processes the equity data, the equity data can be processed according to the priority order of the pre-set target equity, which can ensure the efficiency of processing equity data in high-concurrency scenarios. The priority information can be determined when obtaining the configuration data table from the pre-configured equity basic data. Because there is an equity priority in the equity basic data pre-configured in the equity platform, when the configuration data table is obtained according to the equity identifier, there will be equity priority information in the configuration data table.
[0084] In one embodiment, the process of recording equity data can be found in Figure 4 The flowchart shown includes the following steps:
[0085] S401, the equity platform determines the processing order of the target equity based on the equity priority.
[0086] S402: The equity platform records the equity data of the target equity into the equity data table through a message queue according to the processing order and the ownership identifier.
[0087] The equity platform determines the processing order and processing channel of the target equity based on the equity priority in the configuration data table. Then, the equity data can be recorded in the equity data table corresponding to the owner identifier in the corresponding processing channel according to the processing order of the target equity according to the message queue.
[0088] It should be noted that since there are overall data tables and individual data tables in the equity data table, the equity data of the target equity must be recorded in the overall data table first to achieve the issuance of the target equity. After the overall data table is recorded, the equity change log is updated. The data in the equity change log can help developers and operation and maintenance personnel monitor the health of the equity issuance system and discover problems and anomalies in a timely manner. After the equity change log is recorded, the individual data table can be updated to complete the issuance process of the target equity.
[0089] Based on the rights and interests order of the user's rights and interests purchase, the business module determines the rights and interests sending parameters corresponding to the target rights and interests, and determines the rights and interests data according to the identification of the target rights and interests through the rights and interests platform, and finally records the rights and interests data table corresponding to the rights and interests issuance parameters, realizing the unified management of user rights and interests of multiple parties. After the user purchases the rights and interests, the rights and interests can be automatically issued according to the rights and interests issuance parameters, which improves the efficiency of the rights and interests method and enhances the user experience.
[0090] In one embodiment, the process of the equity platform writing the equity data into the equity data table is as follows: Figure 5 As shown:
[0091] S501, the rights and interests platform receives the rights and interests issuance parameters of the target rights and interests sent by the business module, including the owner identifier, the rights and interests identifier and the rights and interests issuing party code.
[0092] S502, according to the rights issuance parameters, query the pre-configured rights basic data in the cache middleware, wherein the rights basic data contains a plurality of configuration data tables of rights.
[0093] S503, determining whether there is a configuration data table of the target equity in the cache, and if so, returning the configuration data table of the target equity to the equity platform to determine the equity name, equity duration, and equity priority of the target equity.
[0094] S504: If the configuration data table of the target equity does not exist in the cache middleware, the equity data of the target equity is obtained from the database, and the data in the configuration data table is recorded in the cache middleware.
[0095] S505, the equity platform calculates the duration of the target equity according to the configuration data table of the target equity and determines the equity data.
[0096] S506, after determining the issuance duration of the target rights and interests, the rights and interests issuance process can be executed, that is, firstly determining the ownership category of the target rights and interests according to the rights and interests owner identifier.
[0097] S507, after determining the attribution category of the target right, the right data can be written into the corresponding overall data table in the database according to the right category, and the data of the target right can be added to the corresponding right change log. The right attribution categories can include individuals, equipment, and families. Correspondingly, the overall data table is used to record the right data corresponding to each attribution category. The overall data table may include an individual right data table, an equipment right data table, and a family right data table. For example, when it is determined that the attribution category of the target right is an individual, the right data of the target right can be written into the individual right data table.
[0098] S508, determine the individual data table corresponding to the rights and interests owner identifier in the cache middleware, and record the rights and interests data of the target rights and interests into the corresponding individual data table. The individual data table is used to record the rights and interests data corresponding to each owner identifier, and the individual data table may include a personal rights and interests cache table, a device rights and interests cache table, and a family rights and interests cache table. The personal rights and interests cache table records all the rights and interests of a user, such as the personal rights and interests cache table records the membership rights and course rights owned by a user; the device rights and interests cache table records all the rights and interests of a device, such as the device rights and interests cache table records the broken screen insurance rights and warranty rights of a device; the family rights and interests cache table records all the rights and interests of a family, such as the family rights and interests cache table records the reading unlocking rights and article translation rights of a family.
[0099] When writing the equity data of the target equity into the database, the equity data of the target equity may fail to be stored due to abnormal conditions such as network delays or system errors, resulting in the failure of equity issuance, affecting user experience. Therefore, the equity issuance system needs to implement a retry mechanism after the equity issuance fails, and re-issue the equity to the user to improve the accuracy of equity issuance.
[0100] See also Figure 6 The flowchart shown includes the following steps:
[0101] S601: If the equity platform fails to record the equity data of the target equity into the equity data table corresponding to the ownership identifier, the number of issuances of the target equity is obtained.
[0102] 602. If the number of issuances of the target rights is less than the first preset threshold, the rights sending parameters corresponding to the target rights purchased by the user are re-acquired, and the rights data of the target rights are recorded in the rights data table corresponding to the ownership identifier through the rights platform.
[0103] If the equity platform fails to successfully record the equity data of the target equity into the equity data table corresponding to the attribution party identifier, then it is necessary to obtain the number of issuances of the current target equity. If the number of issuances of the current equity is less than the preset first threshold, the equity platform can repeatedly execute the steps of obtaining the equity data according to the equity issuance parameters and recording the equity data into the equity data table corresponding to the attribution party identifier until the equity data is successfully recorded into the equity data table, or the number of equity issuances reaches the first preset threshold.
[0104] Through the retry mechanism, the rights issuance steps can be retried when the rights issuance fails to ensure that users can obtain the purchased rights in time, improve the user experience, and reduce the workload of system administrators.
[0105] After the issuance of rights is completed, it can be determined whether a callback notification is needed for the target rights based on the rights sender identifier when the user purchases the target rights. The rights sender identifier is determined according to the business module. Different business modules correspond to different rights sender identifiers. Exemplarily, the rights sender identifier can be allocated to different business modules in advance by the rights platform. When the user purchases the target rights, the business module can determine the rights sender identifier based on the target rights, assemble it into the rights issuance parameters, and send it to the rights platform.
[0106] Figure 7 A flowchart of a rights and interests platform executing a callback notification is shown, and the flowchart includes the following steps:
[0107] S701, the rights and interests platform obtains the rights and interests sender identifier.
[0108] S702: If the rights sender identifier belongs to a preset business party code, the rights platform sends a callback notification to the business module.
[0109] S703: The business module updates the equity order status according to the callback notification and pushes the equity notification to the user.
[0110] After recording the equity data to the equity data table corresponding to the owner identifier, the equity issuance process is completed. At this time, the business module can push the equity notification to the user by executing the equity callback notification event. When executing the equity callback notification event, the equity platform first obtains the equity sender identifier sent by the business module, and then determines whether a callback notification is required for the target equity based on the equity sender identifier. Specifically, it can be determined whether the equity sender identifier belongs to the preset business party code. If the equity sender identifier is in the preset business party code, it means that the target equity needs a callback notification.
[0111] If the target rights require a callback notification, a callback notification request is generated and sent to the corresponding business module, so that the business module can process subsequent logic, such as updating the status of the rights order and pushing message notifications to the client to inform the user that the rights have been successfully issued.
[0112] It should be noted that because users may purchase rights in business modules such as web pages, and the web browser will directly initiate a request to the rights platform to confirm the rights issuance results without the need for additional callback notifications, some business modules may not require callback notifications.
[0113] Figure 8 A flowchart of sending a callback notification from a rights platform to a business module is schematically shown, and the flowchart includes the following steps:
[0114] S801, the rights and interests platform generates a notification issuance request according to the rights and interests sender identifier.
[0115] S802, the rights and interests platform pushes the notification issuance request to a message queue, and calls an interface of the rights and interests platform through the message queue.
[0116] S803: The rights and interests platform sends a callback notification to the business module according to the interface of the rights and interests platform.
[0117] After determining that a callback notification is required for the target equity, the equity platform generates a notification request based on the equity sender ID and pushes the notification request into the message queue. The business module interface corresponding to the equity sender ID is called through the message queue to enable the business module to receive the notification request, and after receiving the notification request, the status of the equity order is updated according to the notification request.
[0118] If the equity platform fails to send a callback notification to the business module, that is, the business module fails to successfully receive the callback notification, then the callback notification event needs to be retried. Fig. 9 The flowchart shown shows a flowchart of a retry mechanism, the flowchart comprising:
[0119] S901: If the rights platform fails to send a callback notification to the business module, the number of times the callback notification is issued is obtained.
[0120] S902: If the number of times the callback notification is issued is less than a second preset threshold, the rights and interests platform resends the callback notification to the business module.
[0121] If the rights platform fails to send a callback notification to the business module, that is, the business module fails to receive the callback notification, the number of times the rights platform sends the current callback notification to the business module can be obtained. If the number of callback notification issuance is less than the preset second threshold, the rights platform can regenerate the notification issuance request based on the rights issuance result, that is, the information recorded in the rights data table, and push the request back to the message queue, so that the message queue re-calls the interface of the business module and sends a callback notification to the business module.
[0122] After the callback notification fails to be sent, retrying to send the callback notification request to the business module can improve the accuracy of the callback notification issuance. In the existing rights issuance system, the rights issuance is tightly coupled with the user notification logic, resulting in any notification failure in the issuance process that may affect the timely issuance of rights, increasing the instability of rights issuance, and easily causing system delays and error handling difficulties. Compared with the existing system, the rights issuance system in the present disclosure decouples the rights issuance event from the callback notification event. After the rights issuance is completed, the notification callback event is further executed according to the rights sender identifier, which improves the stability and efficiency of rights issuance.
[0123] In another aspect of the present disclosure, there is also provided a rights and interests sending system, the system comprising: a business module and a rights and interests platform;
[0124] The business module is used to obtain the rights and interests sending parameters corresponding to the target rights and interests purchased by the user according to the rights and interests order of the user; the rights and interests sending parameters include: the rights and interests identifier of the target rights and interests, and the identifier of the party to which the target rights and interests belong; the identifier of the party to which the target rights and interests belong is used to indicate that the party to which the target rights and interests belong is an individual, a family or a device;
[0125] The equity platform is used to record the equity data of the target equity into the equity data table corresponding to the ownership identifier according to the equity sending parameter.
[0126] Based on the same inventive concept, the present disclosure also provides a device for issuing rights, the device comprising:
[0127] An acquisition unit is used for the business module to acquire, based on the equity order of the user purchasing the equity, the equity sending parameters corresponding to the target equity purchased by the user, wherein the equity sending parameters include: an equity identifier of the target equity and an identifier of the party to which the target equity belongs; the identifier of the party to which the target equity belongs is used to indicate that the party to which the target equity belongs is an individual, a family or a device;
[0128] A determination unit, configured to determine the equity data of the target equity according to the equity identifier of the target equity through the equity platform;
[0129] The recording unit is used to record the equity data into the equity data table corresponding to the ownership identifier through the equity platform.
[0130] Based on the same inventive concept, the present disclosure also provides a computer-readable storage medium on which a computer program is stored, and when the program is executed by a processor, the method steps for issuing the rights and interests are implemented.
[0131] Based on the same inventive concept, the present disclosure also provides a computer device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the method steps for issuing rights and interests are implemented when the processor executes the program.
[0132] The embodiments of the subject matter and functional operations described in this specification may be implemented in the following: digital electronic circuits, tangibly embodied computer software or firmware, computer hardware including the structures disclosed in this specification and their structural equivalents, or a combination of one or more of them. The embodiments of the subject matter described in this specification may be implemented as one or more computer programs, i.e., one or more modules in computer program instructions encoded on a tangible non-temporary program carrier to be executed by a data processing device or to control the operation of the data processing device. Alternatively or additionally, the program instructions may be encoded on an artificially generated propagation signal, such as a machine-generated electrical, optical or electromagnetic signal, which is generated to encode information and transmit it to a suitable receiver device for execution by a data processing device. The computer storage medium may be a machine-readable storage device, a machine-readable storage substrate, a random or serial access memory device, or a combination of one or more of them.
[0133] Although this specification includes many specific implementation details, these should not be interpreted as limiting the scope of any invention or the scope of protection claimed, but are mainly used to describe the features of the specific embodiments of specific inventions. Certain features described in multiple embodiments in this specification may also be implemented in combination in a single embodiment. On the other hand, the various features described in a single embodiment may also be implemented separately in multiple embodiments or in any suitable sub-combination. In addition, although features may work in certain combinations as described above and even initially claim protection, one or more features from the claimed combination may be removed from the combination in some cases, and the claimed combination may point to a sub-combination or a variation of a sub-combination.
[0134] Similarly, although operations are depicted in a particular order in the accompanying drawings, this should not be understood as requiring that these operations be performed in the particular order shown or performed sequentially, or requiring that all illustrated operations be performed to achieve the desired results. In some cases, multitasking and parallel processing may be advantageous. In addition, the separation of various system modules and components in the above-described embodiments should not be understood as requiring such separation in all embodiments, and it should be understood that the described program components and systems can generally be integrated together in a single software product, or packaged into multiple software products.
[0135] Thus, specific embodiments of the subject matter have been described. Other embodiments are within the scope of the appended claims. In some cases, the actions recited in the claims can be performed in a different order and still achieve the desired results. In addition, the processes depicted in the drawings do not necessarily require the particular order or sequential order shown to achieve the desired results. In some implementations, multitasking and parallel processing may be advantageous.
[0136] The above description is only a preferred embodiment of the present disclosure and is not intended to limit the present disclosure. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the present disclosure shall be included in the scope of protection of the present disclosure.
Claims
1. A method for issuing rights, characterized in that: The method is executed by a rights and interests sending system, and the rights and interests sending system includes: a business module and a rights and interests platform; the method includes: The business module obtains the rights and interests sending parameters corresponding to the target rights and interests purchased by the user based on the rights and interests order of the user, and the rights and interests sending parameters include: the rights and interests identifier of the target rights and interests, and the identifier of the party to which the target rights and interests belong; the identifier of the party to which the target rights and interests belong is used to indicate that the party to which the target rights and interests belong is an individual, a family or a device; The equity platform determines the equity data of the target equity according to the equity identifier of the target equity; The rights and interests platform records the rights and interests data in a rights and interests data table corresponding to the ownership identifier.
2. The method according to claim 1, characterized in that The equity platform determines the equity data of the target equity according to the equity identifier of the target equity, including: The equity platform acquires a preset configuration data table corresponding to the equity identifier according to the equity identifier, wherein the preset configuration data table at least includes: the equity name of the target equity corresponding to the equity identifier, and the equity duration; The equity platform determines the start time and end time of the target equity according to the equity duration; The equity platform determines the equity data of the target equity, and the equity data includes: equity name, start time and end time.
3. The method according to claim 1, characterized in that The equity sending parameters include: the owner identifier of the target equity; The business module obtains the equity sending parameters corresponding to the target equity purchased by the user based on the equity order of the user purchasing the equity, including: The business module queries a preset equity category table based on the equity name of the target equity to determine the category of the party to which the target equity belongs, wherein the equity category table at least includes the equity name and the equity category corresponding to the equity name; When the attribution party category is an individual, the service module determines the user ID as the attribution party identifier according to the login information of the user; When the category of the attributable party is a device, the business module determines a device code as the attributable party identifier according to the device of the user purchasing the target benefit; When the belonging party category is family, the service module determines the family ID as the belonging party identifier according to the family information of the user.
4. The method according to claim 2, characterized in that: The preset configuration data table also includes: equity priority; The equity platform records the equity data in the equity data table corresponding to the ownership identifier, including: The equity platform determines the processing order of the target equity based on the equity priority; The equity platform records the equity data of the target equity into the equity data table corresponding to the ownership identifier through a message queue according to the processing order and the ownership identifier.
5. The method according to claim 1, characterized in that The method further comprises: If the equity platform fails to record the equity data of the target equity into the equity data table, obtaining the number of issuances of the target equity; If the number of issuances of the target rights is less than the first preset threshold, the rights sending parameters corresponding to the target rights purchased by the user are re-acquired, and the rights data of the target rights are recorded in the rights data table corresponding to the ownership identifier through the rights platform.
6. The method according to claim 1, characterized in that The rights and interests data table includes: an individual data table and an overall data table, wherein the individual data table is used to record the rights and interests data corresponding to each belonging party identification, and the overall data table is used to record the rights and interests data corresponding to each belonging party category.
7. The method according to claim 1, characterized in that The equity sending parameter also includes: an equity sender identifier; the equity sender identifier is used to identify the business module; After the equity platform records the equity data in the equity data table corresponding to the ownership identifier, the method further includes: The rights and interests platform obtains the rights and interests sender identifier; If the rights sender identifier belongs to the preset business party code, the rights platform sends a callback notification to the business module; The business module updates the equity order status according to the callback notification and pushes the equity notification to the user.
8. The method according to claim 7, characterized in that If the rights sender identifier belongs to the preset business party code, the rights platform sends a callback notification to the business module, including: The rights and interests platform generates a notification issuance request according to the rights and interests sender identifier; The rights and interests platform pushes the notification issuance request to a message queue, and calls an interface of the rights and interests platform through the message queue; The rights and interests platform sends a callback notification to the business module according to the interface of the rights and interests platform.
9. The method according to claim 8, characterized in that The method further comprises: If the rights platform fails to send a callback notification to the business module, obtaining the number of times the callback notification is issued; If the number of times the callback notification is issued is less than a second preset threshold, the equity platform resends the callback notification to the business module.
10. A rights and interests sending system, characterized in that: The system includes: a business module and a rights and interests platform; The business module is used to obtain the rights and interests sending parameters corresponding to the target rights and interests purchased by the user according to the rights and interests order of the user; the rights and interests sending parameters include: the rights and interests identifier of the target rights and interests, and the identifier of the party to which the target rights and interests belong; the identifier of the party to which the target rights and interests belong is used to indicate that the party to which the target rights and interests belong is an individual, a family or a device; The equity platform is used to record the equity data of the target equity into the equity data table corresponding to the ownership identifier according to the equity sending parameter.