Right and interest issuing method and device, equipment, storage medium and product

Abstract

The invention relates to the technical field of rights and interests management, and discloses a rights and interests issuing method and device, equipment, a storage medium and a product, and the method comprises the steps: determining a rights and interests type identifier corresponding to each currently put rights and interests product; determining a target distribution user range of the right and interest product from an associated subject of the target distribution object based on the right and interest type identifier; determining right and interest information of the enterprise user, and obtaining a distribution rule determined based on the right and interest type identifier and the right and interest information; and distributing the right and interest product to the target distribution object based on the distribution rule. According to the method, the target distribution user range is defined through the right type identification, and the right information is combined to obtain the adaptive distribution rule to complete distribution, so that the right distribution is accurately matched with the right type, the enterprise user authority and the actual demand, the same right product can be circulated among different roles in the enterprise according to the demand, and the user experience is improved. The right utilization rate is remarkably improved, and the right receiving requirements of various enterprise customers and associated subjects are met.

Description

Technical Field

[0001] This application relates to the field of rights management technology, and in particular to a method, apparatus, device, storage medium and product for rights issuance. Background Technology

[0002] When conducting benefit marketing to corporate clients and users, it is necessary to not only obtain effective responses from target corporate clients and users to marketing activities, but also to accurately deliver pre-prepared benefit content to them. In the traditional benefit distribution process, the actual usage scenarios and business entities corresponding to the benefits are not distinguished. Benefits directly related to the company's daily banking business are blindly distributed to corporate legal persons or owners who are not involved in specific business transactions. This leads to a disconnect between the benefit recipients and the actual users, resulting in low actual utilization rates of the benefits by enterprises, wasting the bank's benefit marketing resources, and failing to achieve the expected marketing results. Summary of the Invention

[0003] The main purpose of this application is to provide a method, apparatus, equipment, storage medium and product for distributing rights, which aims to solve the technical problem that in the traditional rights distribution process, rights related to the daily business of enterprises are distributed to corporate legal persons or enterprise owners who do not directly handle banking-related business, resulting in low actual utilization rate of rights by enterprises after distribution.

[0004] To achieve the above objectives, this application proposes a method for granting rights, the method comprising: Determine the corresponding rights type identifier for each rights product currently being offered; Based on the rights type identifier, the target user range for the rights product is determined from the associated entities of the target distribution object. The target user range is used to determine the enterprise users who distribute the rights product. Determine the rights and interests information of the enterprise users, and obtain the distribution rules based on the rights and interests type identifier and the rights and interests information; The rights and benefits products are distributed to the target recipients based on the distribution rules.

[0005] Optionally, the rights type identifier is a first identifier, and the rights product corresponding to the first identifier is initially deployed to the enterprise; The step of distributing the rights and benefits products to the target recipients based on the distribution rules includes: Generate a rights instance corresponding to the rights product, and write the rights instance into the enterprise rights library; Based on the distribution rules, determine the query interface for each enterprise user in the enterprise rights pool; The system receives a processing request submitted by the enterprise user through the query interface, and transfers the rights instance from the enterprise rights pool to the enterprise user, so that the enterprise user can distribute the rights product to the target distribution object.

[0006] Optionally, the step of receiving the processing request submitted by the enterprise user through the query interface and transferring the rights instance from the enterprise rights pool to the enterprise user, so that the enterprise user can distribute the rights product to the target distribution object, includes: Receive the processing request submitted by the enterprise user through the query interface, and determine the type of the benefit product based on the processing request; In response to the fact that the type of the benefit product is a corporate service benefit, the benefit instance is bound to the corporate account of the target recipient and synchronized to the business operation interface of the corporate user, so that the corporate user can handle the corresponding corporate business; In response to the fact that the type of the benefit product is a personal service benefit, the benefit instance is transferred from the enterprise benefit pool to the personal benefit account according to the benefit allocation instruction in the processing request. The user corresponding to the personal benefit account is the associated entity of the target distribution object.

[0007] Optionally, the rights type identifier is a second identifier, and the rights product corresponding to the second identifier is initially deployed to enterprise users. The type of the rights product corresponding to the second identifier is personal service rights. The step of distributing the rights and benefits products to the target recipients based on the distribution rules includes: Write the rights instances of the rights products into the personal rights database of the enterprise user, and open the forwarding interface to the enterprise user; Based on the distribution rules, the system receives forwarding requests submitted by the enterprise user through the forwarding interface. Based on the forwarding request, the rights and benefits products are distributed to the target distribution recipient.

[0008] Optionally, the step of distributing the rights and benefits product to the target distribution recipient according to the forwarding request includes: In response to the fact that the target distribution object is an enterprise user, based on the target enterprise user identifier carried in the forwarding request, the rights instance is transferred from the enterprise user's personal rights pool to the target enterprise user's personal rights pool; In response to the fact that the target distribution object is a non-enterprise user, a one-time credential is generated based on the external contact identifier carried in the forwarding request and sent to the terminal corresponding to the external contact identifier.

[0009] Optionally, after determining the rights and interests information of the enterprise user and obtaining the distribution rules determined based on the rights and interests type identifier and the rights and interests information, the method further includes: Receive reservation requests submitted by target users among the enterprise users, wherein the reservation requests include product information of the benefit products to be reserved; Based on the product information, the rights instances of the rights products are distributed to the target user's personal rights pool according to the distribution rules.

[0010] Furthermore, to achieve the above objectives, this application also proposes an rights distribution device, which includes: The identifier determination module is used to determine the corresponding rights type identifier for each rights product currently being offered; The scope determination module is used to determine the target user scope of the rights product from the associated entities of the target distribution object based on the rights type identifier. The target user scope is used to determine the enterprise users who distribute the rights product. The rule determination module is used to determine the rights and interests information of the enterprise user and obtain the distribution rules determined based on the rights and interests type identifier and the rights and interests information; The product distribution module is used to distribute the rights and benefits products to the target distribution objects based on the distribution rules.

[0011] In addition, to achieve the above objectives, this application also proposes an rights distribution device, the device comprising: a memory, a processor, and a computer program stored in the memory and executable on the processor, the computer program being configured to implement the steps of the rights distribution method as described above.

[0012] In addition, to achieve the above objectives, this application also proposes a storage medium, which is a computer-readable storage medium, on which a computer program is stored, and which, when executed by a processor, implements the steps of the rights distribution method described above.

[0013] In addition, to achieve the above objectives, this application also provides a computer program product, which includes a computer program that, when executed by a processor, implements the steps of the rights distribution method described above.

[0014] This application discloses a method for determining the rights type identifier corresponding to each currently deployed rights product; based on the rights type identifier, determining the target user range for the rights product from the associated entities of the target distribution object, wherein the target user range is used to determine the enterprise users to whom the rights product is distributed; determining the rights information of the enterprise users, and obtaining distribution rules based on the rights type identifier and the rights information; and distributing the rights product to the target distribution object based on the distribution rules. By accurately defining the target user range through the determined rights type identifier and obtaining appropriate distribution rules based on the rights information to complete the distribution, the method achieves precise matching between rights distribution and rights type, enterprise user permissions, and actual needs. This allows the same rights product to circulate on demand among different roles within the enterprise, significantly improving the rights utilization rate and adapting to the rights receiving needs of various enterprise customers and associated entities. Attached Figure Description

[0015] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application.

[0016] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, for those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0017] Figure 1 This is a flowchart illustrating the first embodiment of the method for granting rights under this application; Figure 2 This is a flowchart illustrating the second embodiment of the method for granting rights under this application; Figure 3 This is a schematic diagram illustrating the distribution of the rights and benefits products corresponding to the first identifier. Figure 4 This is a flowchart illustrating the third embodiment of the method for granting rights under this application; Figure 5 This is a schematic diagram of the interface defined for the rights and interests product corresponding to the second identifier in this application; Figure 6 This is a schematic diagram of the module structure of the rights distribution device according to an embodiment of this application; Figure 7 This is a schematic diagram of the device structure of the hardware operating environment involved in the rights granting method in this application embodiment.

[0018] The purpose, features, and advantages of this application will be further explained in conjunction with the embodiments and with reference to the accompanying drawings. Detailed Implementation

[0019] It should be understood that the specific embodiments described herein are merely illustrative of the technical solutions of this application and are not intended to limit this application.

[0020] To better understand the technical solution of this application, a detailed description will be provided below in conjunction with the accompanying drawings and specific implementation methods.

[0021] In the banking industry, various types of benefits are commonly used as leverage and tools in marketing campaigns targeting corporate clients. When marketing benefits to corporate clients and users, it's crucial to both elicit an effective response from them and accurately deliver the pre-designed benefits. Traditionally, various benefits are distributed to corporate users, legal representatives, and owners who trigger the event. However, in practice, corporate users, often their accounting staff, may hesitate to claim benefits in their personal capacity for fear of causing disputes or negative impacts. Furthermore, benefits relevant to daily business operations may be distributed to legal representatives or owners who don't directly handle banking matters, leading to low actual usage rates. Moreover, once distributed to companies and users, benefits cannot be redistributed, preventing them from reaching those who truly need them, resulting in low utilization and poor marketing effectiveness.

[0022] This application provides a method for distributing benefits to enterprise customers. By identifying the benefit type, the target user scope is accurately defined, and the distribution is completed by combining benefit information with appropriate distribution rules. This achieves precise matching between benefit distribution and benefit type, enterprise user permissions, and actual needs, enabling the same benefit product to circulate as needed among different roles within the enterprise. This significantly improves the utilization rate of benefits and adapts to the benefit receiving needs of various enterprise customers and related entities.

[0023] It should be noted that the executing entity in this embodiment can be a computing service device with data processing, network communication, and program execution functions, such as a tablet computer, personal computer, or mobile phone, or an electronic device capable of performing the above functions. The following uses the method system as an example to describe this embodiment and the subsequent embodiments.

[0024] Based on this, the embodiments of this application provide a method for granting rights, referring to... Figure 1 , Figure 1 This is a flowchart illustrating the first embodiment of the method for granting rights under this application.

[0025] In this embodiment, the method for distributing rights includes: Step S10: Determine the rights type identifier corresponding to each rights product currently being offered.

[0026] It should be noted that "rights products" refer to various rights vehicles offered to corporate clients, including but not limited to corporate financial service-related rights and retail rights for individual use, which can be used for marketing incentives or service value-added services. The rights type identifier is a unique classification identifier set to distinguish rights products with different attributes, used to clarify the target audience, usage scenarios, and circulation rules of the rights product.

[0027] Understandably, determining the corresponding rights type identifier for each currently deployed rights product can involve extracting the core attribute information of the rights product to be deployed. This core attribute information may include service attributes (such as corporate service attributes and personal service attributes), user entity attributes (such as applicable to corporate entities and applicable to individual entities), and business scenario attributes (such as corporate business processing scenarios and personal daily consumption scenarios). Then, a preset rights type identifier library is invoked. This identifier library pre-stores multiple sets of standard identifiers and corresponding attribute matching rules, with each set of standard identifiers associated with a unique combination of rights classification attributes. The extracted core attribute information of the rights product is compared one by one with the attribute matching rules in the identifier library to determine the standard identifier with the highest matching degree.

[0028] Step S20: Based on the rights type identifier, determine the target user range for the rights product from the associated entities of the target distribution object. The target user range is used to determine the enterprise users who distribute the rights product.

[0029] It should be noted that the target beneficiaries are the core entities ultimately distributing the rights and benefits products, typically the corporate clients themselves, and are the ultimate beneficiaries of the rights and benefits distribution. Related entities are various entities that have a direct business relationship or management affiliation with the target beneficiaries, including but not limited to the target beneficiaries' corporate management personnel, legal representatives, and managers. The target beneficiary user scope is a group of personnel selected from the related entities who possess the operational authority to distribute the current rights and benefits products. Corporate users refer to the personnel specifically selected from the target beneficiary user scope who will execute the rights and benefits distribution operations. They must possess operational qualifications matching the rights and benefits type and are responsible for distributing the rights and benefits products to the target beneficiaries according to the rules.

[0030] Understandably, when conducting benefit marketing to corporate clients, it is necessary to first clarify that the benefit products offered to corporate clients and corporate users mainly include corporate financial service benefits and retail benefits (benefits for personal use, including but not limited to points, audio-visual benefits, catering benefits, vouchers, recharge cards, physical goods, value-added services, etc.); the target corporate members mainly include corporate administrators (1 or more people), corporate legal representatives (1 person), corporate financial operators (multiple people), etc.

[0031] It should be understood that when distributing benefits to enterprise clients, the basic functionalities of the distribution scheme can be built in conjunction with the relevant scenarios of benefit distribution.

[0032] Specifically, based on the rights type identifier, determining the target user range for the rights product from the associated entities of the target distribution object can involve constructing an information database of associated entities of the target distribution object, collecting and storing the identity attribute information, functional authority information, and relationship information with the target distribution object of the associated entities, forming a structured associated entity graph; extracting the rights distribution qualification requirements corresponding to the rights type identifier; setting multi-dimensional screening conditions based on the qualification requirements corresponding to the rights type identifier, and calling a screening algorithm to verify the entity information in the associated entity information database against the set screening conditions one by one, and selecting associated entities that meet all qualification requirements as candidate distribution users.

[0033] Step S30: Determine the rights and interests information of the enterprise user and obtain the distribution rules determined based on the rights and interests type identifier and the rights and interests information.

[0034] It should be noted that enterprise user rights information is a complete set of data related to enterprise users that affects the distribution and use of rights, including but not limited to the enterprise user's historical rights distribution records, rights usage status (unused / used / expired), rights operation permission level, rights compliance usage records, and related business interaction data. Distribution rules refer to a set of pre-defined rules based on the attribute characteristics of rights type identifiers and enterprise user rights information, used to regulate the entire rights distribution process, including core content such as rights distribution path, storage method, operation permission, flow constraints, usage scenarios, and time limit restrictions.

[0035] It is understood that determining the rights and interests information of the enterprise user can be done by calling the rights and interests data collection interface, retrieving the full amount of original data corresponding to the target enterprise user from the preset multi-source data storage nodes (including rights and interests history database, user permission database, and business interaction database), and integrating it according to preset data dimensions to form a standardized enterprise user rights and interests information dataset.

[0036] It should be understood that obtaining the distribution rules determined based on the right type identifier and the right information can be done by inputting the right type identifier and the enterprise user right information dataset into a rule matching engine, performing multi-dimensional matching analysis on the two through a feature association algorithm, and selecting the basic rule template with the highest suitability from the rule library. The rule library pre-stores multiple sets of basic rule templates, each set of templates corresponding to a specific right type identifier and user right information feature combination, including right storage configuration, distribution permission allocation, and circulation mechanism.

[0037] Furthermore, in order to allow enterprise users to submit reservation applications in advance to lock in target benefits through the benefit reservation mechanism, this satisfies the needs of enterprise users for scarce or popular benefits and avoids competition or omissions when benefits are distributed. Following step S30, the following is also included: The system receives reservation requests submitted by target users among the enterprise users, the reservation requests including product information of the reserved benefit products; based on the product information, the system distributes benefit instances of the benefit products to the target user's personal benefit pool according to the distribution rules.

[0038] Understandably, target users are enterprise users with the corresponding permissions, such as account managers. Product information refers to the core attribute data of the benefit product marked in the reservation application. A benefit instance is an executable benefit carrier with a unique identifier, generated based on the benefit product template. It is the concrete presentation of the benefit product, containing personalized information such as a unique usage code, effective date, and expiration date, and can be directly claimed and used by the user. The personal benefit library refers to the exclusive benefit storage unit allocated to each target user by the benefit distribution management system. It is used to centrally store various benefit instances already acquired under the user's name, supporting operations such as benefit query, use, and transfer.

[0039] It should be understood that in designated channel systems (such as mobile sales), benefits can be assigned to account managers, who can then give the benefits (physical benefits) to key stakeholders of the enterprise, such as the actual controller or relevant business managers of the enterprise, through online or offline visits.

[0040] Specifically, the use of benefits by account managers can be managed through a benefits platform, supporting their flexible allocation of benefits. On the platform, account managers submit appointment requests, and based on these requests, pre-prepared benefits information and related inventory are allocated to them. Account managers can view the benefits information they have received (including inventory quantities, etc.). They can then contact clients online or visit them offline to bestow the relevant benefits. For example, if an account manager visits a business owner or business manager, the benefits are distributed to the relevant person through online contact or in-person visits. If it's a financial service benefit, it's recorded under the corporate client's name; if it's a retail benefit, it's given to the visited individual. Simultaneously, corporate financial operators can view and use the financial service benefits bestowed by account managers when handling related business.

[0041] Step S40: Distribute the rights and benefits products to the target distribution recipients based on the distribution rules.

[0042] It is understood that distributing the rights product to the target recipient based on the distribution rules can be done according to the preset distribution path configuration in the distribution rules, determining the specific distribution method of the rights product, including direct distribution to the target recipient, distribution through an enterprise user intermediary, and indirect distribution through a dedicated rights storage unit. If the distribution rules specify direct distribution, the system generates a rights instance corresponding to the rights product, associates it with the unique identifier of the target recipient, and directly pushes it to its dedicated rights account or storage unit, triggering a rights arrival record; if distribution through an intermediary is specified, the system first distributes the rights instance to the enterprise user's operation account, and the enterprise user completes the secondary transfer to the target recipient according to the rules. After the rights product is successfully distributed to the target recipient, the system automatically updates the distribution status of the rights product.

[0043] In this embodiment, by identifying the rights type, the target user range is accurately defined, and the distribution is completed by combining rights information to obtain and adapt the distribution rules. This achieves a precise match between rights distribution and rights type, enterprise user permissions, and actual needs, enabling the same rights product to circulate as needed among different roles within the enterprise. This significantly improves the utilization rate of rights and adapts to the rights receiving needs of various enterprise customers and related entities.

[0044] Reference Figure 2 , Figure 2 This is a flowchart illustrating a second embodiment of the method for granting rights under this application. Based on the first embodiment described above, a second embodiment of the method for granting rights under this application is proposed. In the second embodiment, the rights type identifier is a first identifier, and the rights product corresponding to the first identifier is initially deployed to the enterprise. Step S40 includes: Step S401: Generate an equity instance corresponding to the equity product and write the equity instance into the enterprise equity library.

[0045] It should be noted that the first identifier refers to a pre-defined identifier for a specific type of benefit, corresponding to benefit products initially targeted at enterprises, such as corporate financial service benefits and some retail benefits for individual use. The enterprise benefit library refers to a dedicated benefit storage and management unit allocated by the benefit management system to the target enterprise. It is used to centrally store benefit instances initially deployed to the enterprise, supports classification and management by benefit type, usage status, and other dimensions, and access and operation permissions are only available to authorized users of the enterprise.

[0046] It should be understood that, regardless of the marketing method, any corporate financial service benefits will be directly issued to the company. Financial operators can then directly view and use these benefits on the relevant business processing page when logging into the company's online banking or mobile banking. Benefits related to financial services, such as interest rate coupons, handling fee coupons, and corporate annual fee and handling fee coupons, will be issued to the company and can only be used by the company through its financial operators when processing related business. For retail benefits intended for individual use, the benefits will first be issued to the company, creating a corporate benefits pool. The company's legal representative, administrator, and financial operators can then retrieve and use these benefits from the corporate benefits pool.

[0047] Specifically, the rights management system receives rights product deployment instructions, extracts the core information of the rights products from the instructions, and verifies whether the rights type identifier corresponding to the rights product is the first identifier. If it is the first identifier, it confirms that the initial deployment target is the target enterprise, and simultaneously retrieves the preset enterprise rights library association information. By calling the rights instance generation interface, based on the template parameters of the rights product, a unique rights instance is generated, and a unique instance code, effective time, and expiration time are assigned to it. The first identifier, rights product code, and target enterprise unique identifier are then associated and bound to the rights instance. After verifying that the target enterprise's enterprise rights library is in a normal and usable state, the generated rights instance is written into the target enterprise's enterprise rights library according to preset storage rules (such as storage by rights type partition), updating the ownership status of the rights instance.

[0048] Step S402: Determine the query interface for each enterprise user in the enterprise rights pool according to the distribution rules.

[0049] It should be noted that the query interface is a standardized data access interface configured by the rights management system for the enterprise rights database, used to receive rights query requests from enterprise users and provide corresponding rights data.

[0050] It is understood that, according to the distribution rules, the query interface for each enterprise user in the enterprise rights pool can be determined based on the enterprise user's role identifier and the permission configuration in the distribution rules. A corresponding configuration scheme is matched for each enterprise user, and a unique query interface for each enterprise user is generated according to the configuration scheme. A unique access identifier (such as interface ID or exclusive key) is assigned to the interface, and the interface access identifier is associated and bound with the enterprise user's identity information and the permission parameters of the distribution rules.

[0051] Step S403: Receive the processing request submitted by the enterprise user through the query interface, and transfer the rights instance from the enterprise rights pool to the enterprise user so that the enterprise user can distribute the rights product to the target distribution object.

[0052] It should be understood that a processing request refers to an operation request submitted by an enterprise user to the rights and interests management system through a dedicated query interface, targeting a specific rights and interests instance in the enterprise rights and interests repository. The core purpose is to transfer the rights and interests instance from the enterprise rights and interests repository to the user's own name. Rights and interests instance transfer refers to the process, provided that the system verification is successful, changing the ownership of a rights and interests instance in the enterprise rights and interests repository from the enterprise's public storage dimension to the enterprise user's personal ownership dimension. After the transfer, the ownership of the rights and interests instance is updated to the corresponding enterprise user, while retaining the core attributes and usage rules of the rights and interests product.

[0053] It should be understood that by first issuing rights to the enterprise and forming an enterprise rights pool under the enterprise's name, and then allowing users such as the enterprise's legal representative, enterprise administrator, and enterprise financial operators to claim and use the relevant rights from the enterprise's rights pool, the adverse effects on the enterprise's products caused by enterprise operators directly claiming rights issued by the bank can be reduced to some extent.

[0054] In one example, reference Figure 3 , Figure 3 This is a schematic diagram illustrating the distribution of the rights and benefits products corresponding to the first identifier. When distributing rights and benefits to corporate clients, a corporate rights and benefits pool is created under the company's name. This pool allows various roles, including corporate legal representatives, corporate administrators, and corporate financial operators, to claim retail rights and benefits from the company's name and transfer them to their personal accounts for use. It enables the direct distribution of rights and benefits (excluding corporate financial service rights) to companies, and allows corporate legal representatives, corporate administrators, and corporate financial operators to claim retail rights and benefits from the company's name and transfer them to their personal accounts. This also supports their use of these rights and benefits. For example, banks may distribute rights and benefits to corporate clients through marketing activities or direct distribution. A rights and benefits pool is created under the corporate client's name, where users can view the company's currently unused, used, and expired rights and benefits. Corporate legal representatives, corporate administrators, and corporate financial operators can claim unused rights and benefits (excluding financial service rights) from the corporate rights and benefits pool and use them.

[0055] Furthermore, to effectively address the issues of mixed use of public and individual benefits and mismatched usage scenarios in traditional benefit distribution, and to further improve the efficiency and user experience of different types of benefits, step S403 may include: The system receives a processing request submitted by the enterprise user through the query interface and determines the type of the benefit product based on the processing request. If the benefit product is a corporate service benefit, the system binds the benefit instance to the enterprise account of the target recipient and synchronizes it to the enterprise user's business operation interface, enabling the enterprise user to handle corresponding corporate business. If the benefit product is a personal service benefit, the system transfers the benefit instance from the enterprise benefit pool to a personal benefit account according to the benefit allocation instruction in the processing request. The user corresponding to the personal benefit account is the associated entity of the target recipient.

[0056] It should be noted that corporate service benefits refer to financial service benefits specifically designed for corporate entities and used only for corporate business scenarios. These correspond to the first identifier in the benefit type identifier and must be linked to a corporate account before use. Examples include preferential loan interest rates and fee waivers for corporate transactions. Personal service benefits refer to benefit types designed for individuals associated with a corporate entity and used for personal purposes. These can be transferred to a personal benefit account, such as restaurant vouchers, audio-visual memberships, and physical goods redemption benefits. A corporate account refers to the dedicated corporate account linked to the benefit management system by the target recipient, used to bind instances of corporate service benefits.

[0057] Understandably, the business operation interface is the system interaction interface used by corporate users (such as financial operators) when handling corporate business. The synchronized rights instance information can be directly used for rights deduction during the business process. The rights allocation instruction is an allocation instruction for personal service rights instances included in the processing request submitted by the corporate user, explicitly specifying the recipient of the rights instance as the associated entity of the target distribution object. A personal rights account refers to a dedicated rights storage account allocated by the rights management system to the associated entity of the target distribution object (such as corporate employees or partners), used to receive and manage personal service rights instances. Associated entities refer to individuals with business connections or affiliations with the target distribution object (corporation), including internal employees and personnel from partner organizations, who are qualified to receive personal service rights.

[0058] Specifically, in response to the fact that the type of rights product is corporate service rights, the rights management system first extracts the unique code corresponding to the rights instance and the corporate account identifier of the target recipient, and completes the binding operation between the rights instance and the corporate account according to the distribution rules, establishing a unique association between the two; at the same time, the system automatically synchronizes the core information of the rights instance (including rights type, validity period, usage conditions, etc.) to the corresponding corporate user's business operation interface, ensuring that when corporate users log in to the business operation interface to handle corresponding corporate business, they can directly view and call the rights instance to complete the verification and use, realizing seamless connection between rights and business processing procedures.

[0059] In response to the fact that the type of rights product is personal service rights, the rights management system parses the rights allocation instructions in the enterprise user's processing request, extracts the associated entity information and corresponding personal rights account identifier of the target distribution object specified in the instructions, verifies that the receiving qualification of the associated entity meets the distribution rules, and initiates the rights instance transfer process. The corresponding rights instance in the enterprise rights library is moved out of the enterprise public storage area and transferred to the personal rights account of the associated entity. After the transfer is completed, the ownership status of the rights instance is updated to personal holding, and the transfer trajectory is recorded to the system log simultaneously. At the same time, a rights arrival notification is pushed to the associated entity.

[0060] In this embodiment, by first issuing the rights to the enterprise and forming an enterprise rights pool under the enterprise, users such as the enterprise's legal representative, enterprise administrator, and enterprise financial operator can then retrieve and use the relevant rights from the enterprise's rights pool. This solves the chaotic problem of decentralized management of rights under the enterprise's name and provides enterprise users with a convenient channel for querying and retrieving rights, avoiding the problem of untimely retrieval caused by information asymmetry.

[0061] Reference Figure 4 , Figure 4 This is a flowchart illustrating the third embodiment of the rights granting method of this application. Based on the second embodiment described above, a third embodiment of the rights granting method of this application is proposed. In the third embodiment, the rights type identifier is a second identifier, and the rights product corresponding to the second identifier is initially deployed to enterprise users. The type of the rights product corresponding to the second identifier is a personal service rights. Step S40 includes: Step S404: Write the rights instance of the rights product into the personal rights database of the enterprise user, and open the forwarding interface to the enterprise user.

[0062] It should be noted that the exclusive rights type identifier of the second identifier corresponds to rights products whose initial target audience is enterprise users and whose type is personal service.

[0063] Understandably, after receiving a rights product delivery instruction, the rights management system first parses the type of rights product and the corresponding rights type identifier in the instruction, verifying that the identifier is the second identifier, the product type is personal service rights, and the initial delivery target is enterprise users. Subsequently, the system generates a unique rights instance based on the template parameters of the rights product, assigns a unique identity code and effective and expiration times, and associates the second identifier with the identity information of the target enterprise user. After verifying that the target enterprise user's personal rights library is in a normal and usable state, the system writes the generated rights instance into its personal rights library, updates the ownership status of the rights instance to be held by the enterprise user personally, and records the operation log. At the same time, according to the circulation constraints of the second identifier rights in the distribution rules, a dedicated forwarding interface is opened for the enterprise user, configuring parameters such as interface access permissions, forwarding limit, and recipient scope. After the interface is activated, a usage guide is pushed to ensure that the enterprise user can perform rights usage or forwarding operations in compliance with regulations.

[0064] It should be understood that for retail-related benefits, both direct distribution to enterprise stakeholders (or key personnel) and distribution to those stakeholders are supported, as well as the initial distribution of benefits to the enterprise, with users such as the enterprise's legal representative, administrator, and financial operators then claiming the relevant benefits from the enterprise's benefit pool. When developing marketing activities for enterprises, benefits are returned to enterprise customers and users, and enterprise users are clearly notified in writing that they can confidently claim and use the benefits available in marketing activities.

[0065] Step S405: Receive the forwarding request submitted by the enterprise user through the forwarding interface based on the dispatching rules.

[0066] It should be noted that a forwarding request refers to a formal request submitted by an enterprise user holding the rights instance corresponding to the second identifier through the forwarding interface opened by the system, for the purpose of transferring the personal service rights instance to the designated recipient.

[0067] It should be understood that when distributing benefits (excluding financial service benefits) to enterprise administrators, the system supports the use and secondary forwarding of these benefits by the enterprise administrators. When distributing benefits to enterprise administrators, their use and secondary forwarding of these benefits are supported. For example, a bank may distribute benefits to an enterprise administrator through marketing activities or direct distribution. The enterprise administrator can normally view the benefits under their name and perform the following operations: 1. Use and cancel the benefits; 2. Forward the benefits under their name to other users (such as the corporate legal representative, corporate financial operator, etc.), and then the recipient of the benefits can use them.

[0068] In one example, reference Figure 5 , Figure 5This is a schematic diagram illustrating the interface definition for the rights and benefits products corresponding to the second identifier in this application. First, a rights and benefits query (list) / view (details) service interface is defined. Based on this, a rights and benefits redemption service interface is defined, and finally, a rights and benefits usage service interface is defined. By defining the interface functions in stages, a full-process service capability is built to enable rights and benefits from query to redemption to usage, allowing enterprise users (mainly financial operators) to view, redeem, and use rights and benefits. For example, it enables enterprise users to view the rights and benefits list information and display rights and benefits details on the channel system page; enables enterprise users to redeem rights and benefits (including electronic coupons and physical rights and benefits); and enables enterprise users to use rights and benefits (including electronic coupons and physical rights and benefits), etc.

[0069] Specifically, banks distribute rights to corporate stakeholders (or key corporate personnel; if the company does not maintain its stakeholder / key personnel information, the rights will be distributed to the corporate legal person by default) through marketing activities or direct distribution; corporate stakeholders / key personnel then receive and use the rights.

[0070] Step S406: Distribute the rights and benefits product to the target distribution object according to the forwarding request.

[0071] Furthermore, to enable non-enterprise users to claim benefits using a one-time voucher, the threshold for external users to claim benefits is lowered while ensuring the secure distribution of benefits, thus resolving the incompatibility issue of benefit receiving methods for different user groups. Step S406 may include: In response to the target distribution object being an enterprise user, the rights instance is transferred from the enterprise user's personal rights database to the target enterprise user's personal rights database based on the target enterprise user identifier carried in the forwarding request; in response to the target distribution object being a non-enterprise user, a one-time credential is generated and sent to the terminal corresponding to the external contact identifier based on the external contact identifier carried in the forwarding request.

[0072] It should be noted that the target enterprise user identifier is a system code carried in the forwarding request, used to uniquely identify the target distribution recipient (enterprise user), and is associated with the target enterprise user's identity information. Non-enterprise users refer to external related entities among the target distribution recipients who are not authorized to operate within the enterprise, such as personnel from enterprise partners, individual customers, and family members of enterprise users. They do not have a system-allocated personal rights database and must obtain rights through a one-time credential. A one-time credential is a temporary rights carrier generated specifically for non-enterprise users, possessing a unique verification code and validity period. It contains core information about the rights instance (such as rights type and scope of use) and a usage and verification entry point. Non-enterprise users can activate and use rights through the credential; it cannot be forwarded a second time.

[0073] Understandably, based on the different sources of corporate stakeholders, corporate stakeholders can be divided into corporate operators (corporate employees) and custom stakeholders (non-corporate employees) to achieve the definition and management of corporate stakeholders (or key corporate personnel).

[0074] Specifically, after parsing the target distribution object type in the forwarding request, the rights management system executes the processing flow according to different scenarios. If the target distribution object is an enterprise user, the system first extracts the target enterprise user identifier from the request, verifies whether the user corresponding to the identifier is an authorized entity within the enterprise, whether the personal rights pool is in an available state, and verifies that the current status of the rights instance meets the transfer conditions (not expired, not occupied). After the verification is passed, the rights instance is moved out of the personal rights pool of the enterprise user who initiated the forwarding and transferred to the personal rights pool of the target enterprise user. The ownership identifier and transfer trajectory of the rights instance are updated, a transfer success notification is generated and pushed to both enterprise users, and the operation log is recorded. If the target distribution object is a non-enterprise user, the system extracts the external contact identifier from the request, verifies the legality of the identifier format (such as whether the mobile phone number conforms to the standard and whether the email is valid), and generates a one-time certificate containing a unique verification code, validity period and usage instructions in combination with the rights instance information. The certificate is issued through the terminal channel corresponding to the identifier (such as SMS, email), and the certificate generation time, associated rights instance code and receiving terminal information are recorded. An automatic expiration mechanism is set after the certificate is used to ensure that non-enterprise users can securely activate rights through the certificate and to avoid certificate abuse.

[0075] It should be understood that if the target recipients are non-enterprise users, before distributing the benefits to them, it is necessary to establish a corresponding enterprise beneficiary for each non-enterprise user through the terminal. By maintaining these enterprise beneficiaries / key individuals, benefits are distributed to them, enabling small and medium-sized enterprise customers or micro-enterprise customers to express their intention to receive and use the benefits.

[0076] In this embodiment, the secondary transfer of rights is supported by an open forwarding interface, which enables enterprise users to forward rights to the target distribution object according to actual needs, thereby improving the utilization rate of personal service rights.

[0077] It should be noted that the above examples are only for understanding this application and do not constitute a limitation on the method of granting the rights of this application. Any simple modifications based on this technical concept are within the scope of protection of this application.

[0078] This application also provides a rights distribution device, please refer to... Figure 6 The rights distribution device includes: The identifier determination module 10 is used to determine the corresponding rights type identifier for each rights product currently being offered; The scope determination module 20 is used to determine the target user scope of the rights product from the associated entities of the target distribution object based on the rights type identifier. The target user scope is used to determine the enterprise users who distribute the rights product. The rule determination module 30 is used to determine the rights and interests information of the enterprise user and obtain the distribution rules determined based on the rights and interests type identifier and the rights and interests information; Product distribution module 40 is used to distribute the rights and benefits products to the target distribution objects based on the distribution rules.

[0079] The rights distribution device provided in this application, employing the rights distribution method described in the above embodiments, can solve the technical problem of low actual utilization rate of rights by enterprises after distribution, where rights related to daily business are distributed to corporate entities or owners who do not directly handle banking-related business in the traditional rights distribution process. Compared with the prior art, the beneficial effects of the rights distribution device provided in this application are the same as those of the rights distribution method provided in the above embodiments, and other technical features in the rights distribution device are the same as those disclosed in the methods of the above embodiments, and will not be repeated here.

[0080] This application provides an rights distribution device, which includes: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, the instructions being executed by the at least one processor to enable the at least one processor to perform the rights distribution method in Embodiment 1 above.

[0081] The following is for reference. Figure 7 The diagram illustrates a structural schematic of a rights-granting device suitable for implementing embodiments of this application. The rights-granting device in embodiments of this application may include, but is not limited to, mobile terminals such as mobile phones, laptops, digital broadcast receivers, PDAs (Personal Digital Assistants), PADs (Portable Application Description), PMPs (Portable Media Players), in-vehicle terminals (e.g., in-vehicle navigation terminals), and fixed terminals such as digital TVs and desktop computers. Figure 7 The rights distribution device shown is merely an example and should not impose any limitation on the functionality and scope of use of the embodiments of this application.

[0082] like Figure 7As shown, the rights-issuing device may include a processing unit 1001 (e.g., a central processing unit, a graphics processing unit, etc.), which can perform various appropriate actions and processes according to a program stored in a read-only memory 1002 or a program loaded from a storage device 1003 into a random access memory 1004. The random access memory 1004 also stores various programs and data required for the operation of the rights-issuing device. The processing unit 1001, the read-only memory 1002, and the random access memory 1004 are interconnected via a bus 1005. An input / output interface 1006 is also connected to the bus. Typically, the following systems can be connected to the input / output interface 1006: input devices 1007 including, for example, a touchscreen, touchpad, keyboard, mouse, image sensor, microphone, accelerometer, gyroscope, etc.; output devices 1008 including, for example, a liquid crystal display (LCD), speaker, vibrator, etc.; storage devices 1003 including, for example, magnetic tape, hard disk, etc.; and communication devices 1009. Communication device 1009 allows the rights-granting device to communicate wirelessly or wiredly with other devices to exchange data. Although rights-granting devices with various systems are shown in the figures, it should be understood that implementation or possession of all the systems shown is not required. More or fewer systems may be implemented alternatively.

[0083] Specifically, according to the embodiments disclosed in this application, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, embodiments disclosed in this application include a computer program product comprising a computer program carried on a computer-readable medium, the computer program containing program code for performing the methods shown in the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network via a communication device, or installed from storage device 1003, or installed from read-only memory 1002. When the computer program is executed by processing device 1001, it performs the functions defined in the methods of the embodiments disclosed in this application.

[0084] The rights distribution device provided in this application, employing the rights distribution method described in the above embodiments, can solve the technical problem of low actual utilization rate of rights after distribution, where rights related to the company's daily business are distributed to corporate entities or owners who do not directly handle banking-related business during the traditional rights distribution process. Compared with the prior art, the beneficial effects of the rights distribution device provided in this application are the same as those of the rights distribution method provided in the above embodiments, and other technical features of the rights distribution device are the same as those disclosed in the previous embodiment method, and will not be repeated here.

[0085] It should be understood that the various parts disclosed in this application can be implemented using hardware, software, firmware, or a combination thereof. In the description of the above embodiments, specific features, structures, materials, or characteristics can be combined in any suitable manner in one or more embodiments or examples.

[0086] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

[0087] This application provides a computer-readable storage medium having computer-readable program instructions (i.e., a computer program) stored thereon, the computer-readable program instructions being used to execute the benefit granting method in the above embodiments.

[0088] The computer-readable storage medium provided in this application may be, for example, a USB flash drive, but is not limited to, electrical, magnetic, optical, electromagnetic, infrared, or semiconductor systems, devices, or any combination thereof. More specific examples of computer-readable storage media may include, but are not limited to: electrical connections having one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fibers, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof. In this embodiment, the computer-readable storage medium may be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system, system, or device. The program code contained on the computer-readable storage medium may be transmitted using any suitable medium, including but not limited to: wires, optical cables, RF (Radio Frequency), etc., or any suitable combination thereof.

[0089] The aforementioned computer-readable storage medium may be included in the rights-issuing device; or it may exist independently and not assembled into the rights-issuing device.

[0090] The aforementioned computer-readable storage medium carries one or more programs, which, when executed by the rights-issuing device, cause the rights-issuing device to perform the rights-issuing method described above.

[0091] Computer program code for performing the operations of this application can be written in one or more programming languages ​​or a combination thereof, including object-oriented programming languages ​​such as Java, Smalltalk, and C++, and conventional procedural programming languages ​​such as the "C" language or similar programming languages. The program code can be executed entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving remote computers, the remote computer can be connected to the user's computer via any type of network—including a Local Area Network (LAN) or a Wide Area Network (WAN)—or can be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0092] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of this application. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, may be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.

[0093] The modules described in the embodiments of this application can be implemented in software or hardware. The names of the modules do not necessarily limit the functionality of the unit itself.

[0094] The readable storage medium provided in this application is a computer-readable storage medium that stores computer-readable program instructions (i.e., a computer program) for executing the above-described rights distribution method. This solves the technical problem in traditional rights distribution processes where rights related to a company's daily business are distributed to corporate entities or owners who do not directly handle banking-related business, resulting in low actual utilization of the rights by the company after distribution. Compared with the prior art, the beneficial effects of the computer-readable storage medium provided in this application are the same as those of the rights distribution method provided in the above embodiments, and will not be repeated here.

[0095] This application also provides a computer program product, including a computer program that, when executed by a processor, implements the steps of the rights granting method described above.

[0096] The computer program product provided in this application can solve the technical problem that in the traditional rights distribution process, rights related to the company's daily business are distributed to corporate entities or owners who do not directly handle banking-related business, resulting in low actual utilization of the rights by the company after distribution. Compared with the prior art, the beneficial effects of the computer program product provided in this application are the same as those of the rights distribution method provided in the above embodiments, and will not be repeated here.

[0097] The above description is only a part of the embodiments of this application and does not limit the scope of this application. All equivalent structural transformations made under the technical concept of this application and using the content of this application specification and drawings, or direct / indirect applications in other related technical fields, are included within the protection scope of this application.

Claims

1. A method for distributing rights, characterized in that, The methods for distributing the rights include: Determine the corresponding rights type identifier for each rights product currently being offered; Based on the rights type identifier, the target user range for the rights product is determined from the associated entities of the target distribution object. The target user range is used to determine the enterprise users who distribute the rights product. Determine the rights and interests information of the enterprise users, and obtain the distribution rules based on the rights and interests type identifier and the rights and interests information; The rights and benefits products are distributed to the target recipients based on the distribution rules.

2. The method for distributing rights as described in claim 1, characterized in that, The rights type identifier is a first identifier, and the rights product corresponding to the first identifier is initially deployed to the enterprise; The step of distributing the rights and benefits products to the target recipients based on the distribution rules includes: Generate a rights instance corresponding to the rights product, and write the rights instance into the enterprise rights library; Based on the distribution rules, determine the query interface for each enterprise user in the enterprise rights pool; The system receives a processing request submitted by the enterprise user through the query interface, and transfers the rights instance from the enterprise rights pool to the enterprise user, so that the enterprise user can distribute the rights product to the target distribution object.

3. The method for distributing rights as described in claim 2, characterized in that, The step of receiving the processing request submitted by the enterprise user through the query interface, transferring the rights instance from the enterprise rights pool to the enterprise user, so that the enterprise user can distribute the rights product to the target distribution object, includes: Receive the processing request submitted by the enterprise user through the query interface, and determine the type of the benefit product based on the processing request; In response to the fact that the type of the benefit product is a corporate service benefit, the benefit instance is bound to the corporate account of the target recipient and synchronized to the business operation interface of the corporate user, so that the corporate user can handle the corresponding corporate business; In response to the fact that the type of the benefit product is a personal service benefit, the benefit instance is transferred from the enterprise benefit pool to the personal benefit account according to the benefit allocation instruction in the processing request. The user corresponding to the personal benefit account is the associated entity of the target distribution object.

4. The method for distributing rights as described in claim 1, characterized in that, The rights and benefits type identifier is the second identifier. The rights and benefits products corresponding to the second identifier are initially deployed to enterprise users. The type of the rights and benefits products corresponding to the second identifier is personal service rights. The step of distributing the rights and benefits products to the target recipients based on the distribution rules includes: Write the rights instances of the rights products into the personal rights database of the enterprise user, and open the forwarding interface to the enterprise user; Based on the distribution rules, the system receives forwarding requests submitted by the enterprise user through the forwarding interface. Based on the forwarding request, the rights and benefits products are distributed to the target distribution recipient.

5. The method for distributing rights as described in claim 4, characterized in that, The step of distributing the rights and benefits product to the target recipient according to the forwarding request includes: In response to the fact that the target distribution object is an enterprise user, based on the target enterprise user identifier carried in the forwarding request, the rights instance is transferred from the enterprise user's personal rights pool to the target enterprise user's personal rights pool; In response to the fact that the target distribution object is a non-enterprise user, a one-time credential is generated based on the external contact identifier carried in the forwarding request and sent to the terminal corresponding to the external contact identifier.

6. The method for granting rights as described in any one of claims 1 to 5, characterized in that, After the steps of determining the rights and interests information of the enterprise user and obtaining the distribution rules determined based on the rights and interests type identifier and the rights and interests information, the method further includes: Receive reservation requests submitted by target users among the enterprise users, wherein the reservation requests include product information of the benefit products to be reserved; Based on the product information, the rights instances of the rights products are distributed to the target user's personal rights pool according to the distribution rules.

7. A rights distribution device, characterized in that, The device includes: The identifier determination module is used to determine the corresponding rights type identifier for each rights product currently being offered; The scope determination module is used to determine the target user scope of the rights product from the associated entities of the target distribution object based on the rights type identifier. The target user scope is used to determine the enterprise users who distribute the rights product. The rule determination module is used to determine the rights and interests information of the enterprise user and obtain the distribution rules determined based on the rights and interests type identifier and the rights and interests information; The product distribution module is used to distribute the rights and benefits products to the target distribution objects based on the distribution rules.

8. A rights distribution device, characterized in that, The device includes: a memory, a processor, and a computer program stored in the memory and executable on the processor, the computer program being configured to implement the steps of the benefit distribution method as described in any one of claims 1 to 6.

9. A storage medium, characterized in that, The storage medium is a computer-readable storage medium, and a computer program is stored on the storage medium. When the computer program is executed by a processor, it implements the steps of the benefit distribution method as described in any one of claims 1 to 6.

10. A computer program product, characterized in that, The computer program product includes a computer program that, when executed by a processor, implements the steps of the benefit distribution method as described in any one of claims 1 to 6.

Images