Project processing method and apparatus

Abstract

This specification provides a project processing method and apparatus. One project processing method includes: obtaining a target associated user selected by a target object from a list of associated users for project access; creating a reservation task for the target object to participate in the project and sending a task access link corresponding to the reservation task to the target associated user; determining the amount of participation resources for the project by the target associated user based on the user's identity information and the authorization instruction submitted after triggering the task access link; performing project participation processing based on the reservation task and the amount of participation resources to obtain project participation details corresponding to the reservation task; and constructing a project sharing relationship between the target object and the target associated user based on the project participation details.

Description

[0001] This application is a divisional application of Chinese invention patent application filed on November 23, 2020, with application number CN112308261A and title “Project Processing Method and Apparatus”. Technical Field

[0002] This document relates to the field of data processing technology, and in particular to a project processing method and apparatus. Background Technology

[0003] With the rapid development of internet technology, routine business such as sales, after-sales service, and claims processing of insurance products can be conveniently handled online. At the same time, as users pay more and more attention to their own health, critical illness insurance and health accident insurance are becoming increasingly popular. When purchasing critical illness insurance and health accident insurance online, applicants are more cautious in their selection of insurance products and are paying more and more attention to whether the insurance products can be claimed. Summary of the Invention

[0004] This specification provides one or more embodiments of a project processing method. The project processing method includes: obtaining a target associated user selected by a target object from a list of associated users for project access assurance; creating a reservation task for the target object to participate in the project assurance; sending a task access link corresponding to the reservation task to the target associated user; determining the amount of participation resources for the project assurance for the target associated user based on the target associated user's identity information, according to the authorization instruction submitted by the target associated user after triggering the task access link; performing project participation processing based on the reservation task and the amount of participation resources to obtain project participation details corresponding to the reservation task; and constructing a project sharing relationship between the target object and the target associated user based on the project participation details.

[0005] This specification provides one or more embodiments of a project processing apparatus, including: an associated user selection module configured to obtain a target associated user selected by a target object from a list of associated users for project access; a reservation task creation module configured to create a reservation task for the target object to participate in the project and send a task access link corresponding to the reservation task to the target associated user; a participation resource amount determination module configured to determine the participation resource amount for the project by the target associated user based on the authorization instruction submitted by the target associated user after triggering the task access link, and based on the identity information of the target associated user; a project participation processing module configured to perform project participation processing based on the reservation task and the participation resource amount to obtain project participation details corresponding to the reservation task; and a sharing relationship construction module configured to construct a project sharing relationship between the target object and the target associated user based on the project participation details.

[0006] This specification provides one or more embodiments of a project processing device, including: a processor; and a memory configured to store computer-executable instructions, which, when executed, cause the processor to: obtain a target associated user selected by a target object from a list of associated users for project access; create a reservation task for the target object to participate in the project and send a task access link corresponding to the reservation task to the target associated user; determine the amount of participation resources for the project for the target associated user based on the target associated user's identity information, according to the authorization instruction submitted by the target associated user after triggering the task access link; perform project participation processing based on the reservation task and the amount of participation resources to obtain project participation details corresponding to the reservation task; and construct a project sharing relationship between the target object and the target associated user based on the project participation details.

[0007] This specification provides one or more embodiments of a storage medium for storing computer-executable instructions, which, when executed, perform the following process: Obtaining a target associated user selected by a target object from a list of associated users connected to a security project. Creating a reservation task for the target object to participate in the security project and sending a task access link corresponding to the reservation task to the target associated user. Based on the authorization instruction submitted by the target associated user after triggering the task access link, determining the amount of participation resources for the security project for the target associated user based on the user's identity information. Performing project participation processing based on the reservation task and the amount of participation resources to obtain project participation details corresponding to the reservation task. Constructing a project sharing relationship between the target object and the target associated user based on the project participation details. Attached Figure Description

[0008] To more clearly illustrate the technical solutions in one or more embodiments of this specification or in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments recorded in this specification. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0009] Figure 1 A flowchart illustrating a project processing method provided in one or more embodiments of this specification;

[0010] Figure 2 A flowchart for generating a reservation task is provided for one or more embodiments of this specification;

[0011] Figure 3 A flowchart for authorizing a scheduled task is provided for one or more embodiments of this specification;

[0012] Figure 4 A flowchart for generating project participation details is provided for one or more embodiments of this specification;

[0013] Figure 5 A flowchart illustrating a project processing method for a multi-user assurance project, provided for one or more embodiments of this specification;

[0014] Figure 6 A schematic diagram of a project processing device provided for one or more embodiments of this specification;

[0015] Figure 7 This is a schematic diagram of the structure of a project processing device provided for one or more embodiments of this specification. Detailed Implementation

[0016] To enable those skilled in the art to better understand the technical solutions in one or more embodiments of this specification, the technical solutions in one or more embodiments of this specification will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of this specification, and not all of the embodiments. Based on one or more embodiments of this specification, all other embodiments obtained by those skilled in the art without creative effort should fall within the protection scope of this document.

[0017] This specification provides an example of a project processing method:

[0018] Reference Figure 1 It shows a flowchart of a project processing method provided in this embodiment, referring to... Figure 2 It shows a flowchart of a reservation task generation method provided for this embodiment, with reference to... Figure 3 It shows a flowchart of a reservation task authorization process provided for this embodiment, with reference to... Figure 4 It illustrates a flowchart for generating project participation details provided for this embodiment; see reference. Figure 5 It shows a flowchart of a project processing method for a multi-user assurance project provided for this embodiment;

[0019] Reference Figure 1 The project processing method provided in this embodiment specifically includes the following steps S102 to S110.

[0020] Step S102: Obtain the target associated user selected by the target object from the list of associated users for ensuring project access.

[0021] In practical applications, during multi-user insurance program participation, applicants need to provide accurate identity information of the participants so that the insurance agency can generate a policy. However, applicants often find it difficult to remember the identity information of other insured participants, requiring offline communication. Obtaining and recording identity information before filling out forms is costly, leading to significant conversion rate drops in insurance programs.

[0022] The project processing method provided in this embodiment generates a reservation task when an applicant invites multiple participants to a multi-user protection project. After all invited participants authorize, formal project participation details are generated, and a sharing relationship is established between the applicant and the multiple participants for the multi-user protection project. Specifically, the target user first selects a target associated user from the list of associated users accessing the protection project. If both the target user and the target associated user pass access checks, a reservation task for participating in the protection project is created, and a corresponding task access link is sent to the target associated user. Then, based on the authorization instruction submitted by the target associated user, the target user's identity information is obtained, and the amount of resources the target associated user contributes to the protection project is determined based on this information. After deducting resources from the target user according to the contribution amount, project participation processing is performed, and the project participation details corresponding to the reservation task are obtained. Finally, a project sharing relationship is established between the target user and the target associated user, and permissions are shared with the target associated user based on this relationship. This improves the conversion rate and user experience of protection projects while fully protecting user privacy.

[0023] The protection program described in this embodiment includes a multi-user protection program based on a family unit. Participation in this program involves one family member initiating an invitation to other family members to participate. Additionally, the protection program can also be a multi-user protection program involving a group of friends, colleagues, classmates, or other similar groups. It should be noted that in this embodiment, after the protection applicant sends a participation invitation to one or more participants, all invited participants must confirm their authorization before further participation in the protection program can proceed.

[0024] The target object refers to the applicant who invites others to participate in the protection project; the associated users in the associated user list refer to users who have a data relationship with the target object, such as users with a spouse, children, parents, friends, etc. These users can determine their data relationship with the target object through interaction within the application; the target associated user is one or more associated users selected by the target object from the associated user list. Here, the target associated user selected by the target object is the protection participant invited by the target object as the protection applicant to participate in the protection project; it should be noted that the target object can also select itself as the protection participant when selecting protection participants.

[0025] In practical applications, the amount of resources required for participation in a protection project often needs to be determined based on the age of the participants. This amount includes the fees or resources (such as funds, points, etc.) required to participate in the protection project. Specifically, before obtaining the target users selected by the target from the list of associated users connected to the protection project, the list of associated users is displayed on a list page. For each associated user in the list, the relationship tags and predicted amount of participation resources for each user are displayed on the list page.

[0026] Furthermore, to ensure that the relationship tags displayed to the target object are more accurate and conform to the actual association, thereby making the predicted participation resource amount based on this actual association more precise and providing more effective reference value to the target object, in an optional implementation of this embodiment, after accessing the associated user list to the target object, the predicted participation resource amount is also displayed to the target object in the following manner:

[0027] Based on the association between the target object and the target associated user, the predicted age field of the target associated user is determined;

[0028] Based on the predicted age field, determine the predicted amount of resources the target associated user will participate in the protection project and display it to the target object;

[0029] Based on the display of the predicted amount of participating resources, obtain the target object's signing instruction for the deduction agreement;

[0030] The deduction agreement includes the deduction cycle, deduction frequency, specified deduction time period and / or deduction payment channel.

[0031] In addition, the process of displaying the predicted amount of participation resources to the target audience can also be carried out after the target audience selects a target associated user. Specifically, after the target audience selects a target associated user, the predicted age field of the target associated user is determined based on the relationship between the target associated user and the target audience and the target audience's age field. Based on the predicted age field, the predicted amount of participation resources for the target associated user to participate in the guarantee project is determined and displayed to the target audience. Similarly, in the process of determining the amount of participation resources, it can also be confirmed based on other characteristic data related to identity features, such as occupation and gender.

[0032] In practical applications, when a target person chooses to invite family members to participate in the protection project, the associated user list will automatically include the configured associated users who have family relationships with the target person, such as spouse, children, and parents, and the relationship between the associated users and the target person will be included. The target person can then select the target associated user from the associated users. However, due to missing data or incorrect data configuration, the relationship tags may not display the correct relationship, which may affect the determination of the predicted amount of resources to be participated in.

[0033] To address this, and to further refine the actual relationship, thereby making the predicted resource allocation based on this relationship more accurate and enhancing its reference value for the target audience, if the target audience observes an incorrect relationship in the relationship label, they can modify their relationship with the associated user by triggering a configured modification control. The target audience can also fill in the age information of the associated user.

[0034] In addition, in practical applications, in order to avoid the waste of resources caused by repeated participation in protection projects, an admission verification is automatically performed on each associated user in the associated user list. If an associated user already has project participation details or appointment tasks for the protection project, the associated user is marked as already participating, and the area where the candidate protection participant is located in the associated user list is marked as unselectable. Alternatively, if the protection applicant selects the associated user, a reminder is sent to the protection applicant that the associated user is already in the participation status of the protection project.

[0035] In specific implementation, to avoid unnecessary expenses and resource waste caused by repeated applications, in an optional implementation of this embodiment, during the process of the target object selecting the target associated object, it is detected whether the target associated user has project participation details or appointment tasks of the guaranteed project; if so, a failure reminder is sent to the target object and / or the invitation permission of the target associated user is frozen; otherwise, no action is taken.

[0036] Specifically, during the process of accessing the associated user list to the target object, it checks whether the associated users in the associated user list have project participation details or reservation tasks for the guaranteed project. If so, when displaying the associated user list to the target object, the invitation permissions of the associated users who have already participated in the guaranteed project or have reservation tasks are frozen. In addition, the above-mentioned detection of whether associated users have project participation details or task details can also be performed after the target object selects the target associated user, and then check whether the invited target associated user has project participation details or reservation tasks for the guaranteed project. If so, a reminder is sent to the target object that the target associated user cannot be invited.

[0037] For example, if applicant X invites multiple family members to participate in a family protection program, a list of associated users who are related to applicant X as children, spouses, or parents is displayed to applicant X. This list includes child A, spouse C, father D, and mother E. During the display of this list, the ages of the associated users are predicted based on their relationship to applicant X (e.g., if applicant X is 35 years old, according to the legal marriage age, the ages of children A and B are predicted to be between 1 and 10 years old). Based on the predicted ages, the participation fee for each associated user in the protection program is predicted and displayed when showing the list. Simultaneously, it checks whether the associated users have already participated in the protection program or have any reservation tasks for the program. If so, the invitation permissions for the associated users who have already participated or have reservation tasks are frozen in the associated user list area.

[0038] Step S104: Create a reservation task for the target object to participate in the guarantee project, and send the task access link corresponding to the reservation task to the target associated user.

[0039] In this embodiment, when an applicant applies for multiple family members to participate in the protection project, a formal project participation detail is not generated immediately. Instead, a reservation form is created first. After all protection participants authorize and confirm, the participation process for the protection project is initiated uniformly, and a formal project participation detail is generated. The reservation task refers to the reservation form, which includes the reservation form number, project product code, target object ID, target associated user ID, reservation time, task deadline, reservation form status, and / or task processing status. The task access link refers to a message jump link dynamically generated by concatenating the link of the authorization pending confirmation page and the reservation form number.

[0040] In specific implementation, a reservation task is created for the target object to participate in the guarantee project, and a task access link corresponding to the reservation task is sent to the target associated user. Optionally, after creating the reservation task, the task processing status recorded in the reservation task is marked as a first processing status; if the processing instruction submitted by the target associated user is an authorization instruction, the task processing status is updated to a second processing status; or, if the processing instruction submitted by the target associated user is a rejection instruction, the task processing status is updated to a third processing status. The first processing status refers to the initialization status, the second processing status refers to the authorized status, and the third processing status refers to the rejected status. Furthermore, after creating the reservation task, the task status recorded in the reservation task is marked as the initialization status; when all guarantee participants submit confirmation authorization instructions, the task status is updated to the fully authorized status; if the reservation task times out or a guarantee participant submits a rejection instruction, the task status is updated to the canceled status.

[0041] For example, Table 1 below shows the record of scheduled tasks:

[0042]

[0043]

[0044] Table 1

[0045] Among them, the target object with target object ID 208001 invites the target associated user with target associated user ID 208002 and the target associated user with target associated user ID 208003 to participate in the multi-user guarantee project with project product code sp001. The created reservation order number is order001. In the task status, 'I' indicates that the reservation task is in the initialization state, and in the task processing status, '1' indicates the initialization state and '2' indicates the authorized state.

[0046] In specific implementation, when a reservation task is created, the task status is marked as initialization and the processing status is marked as first processing status. When a target associated user submits an authorization instruction, the processing status corresponding to that target associated user is updated to second processing status. When a target associated user submits a rejection instruction, the task status is updated to canceled status, and the processing status corresponding to that target associated user is updated to third processing status. Within the task period, if all target associated users who sent the task access link corresponding to the reservation task have submitted authorization instructions, the task status is updated to full authorization status. If, after the task period expires, a target associated user who sent the task access link corresponding to the reservation task has not submitted a processing instruction, the task status is updated to canceled status. If a target object submits a rejection instruction, the task status is updated to canceled status. Optionally, the task status of the reservation task is updated to canceled status if the task period contained in the reservation task has expired, the target object submits a rejection instruction, and / or at least one target associated user who sent the task access link submits a rejection instruction.

[0047] In addition, in the event of a cancelled appointment task, to more clearly display the reason for cancellation, the task status recorded in the appointment task can also be configured as: initialization status, full authorization status, active cancellation status, and timeout cancellation status; among which, the active cancellation status and the supermarket cancellation status are both marked as cancelled status.

[0048] In practical applications, there are situations where the target entity invites related entities to participate in the protection project multiple times, but the related users do not have the intention to participate. For example, if the protection applicant has been denied authorization multiple times within the month, it indicates that the protection participants have no intention to participate in the protection project together. Therefore, in order to avoid giving protection participants frequent invitations, the protection applicant will be prevented from making any more appointments.

[0049] In practical implementation, to avoid frequent message disturbances to the invited target users caused by multiple appointments by the target object, this embodiment provides an optional implementation method in which the number of times the target object invites the target users is controlled before creating the appointment task by the following method:

[0050] Detect the number of appointment invitations made by the target object to the target associated user within a preset time range;

[0051] If the number of appointment invitations exceeds the invitation limit, the appointment invitation privileges of the target object will be frozen.

[0052] In practice, a reservation task is created after confirming that the target user can make reservations for the target candidate. Simultaneously, the target user signs a deduction agreement. Resource deductions are made after all associated users have authorized the process, and participation in the protection project is initiated. This eliminates the need for the target user to prepay resources during the reservation process, reducing resource risk and management costs. The signed deduction agreement includes stipulations on the deduction cycle, frequency, specified time period, and / or payment channel. The target user is informed that the actual amount of resources involved will be determined based on their identity information after authorization from associated users.

[0053] Specifically, such as Figure 2 As shown, the creation of the reservation task is completed by executing steps S202 to S210.

[0054] Step S202: Obtain the target associated user selected by the target object from the list of associated users for ensuring project access.

[0055] Step S204: Detect the number of times the target object invites the target associated user within a preset time range.

[0056] Step S206: If the number of invitations does not exceed the invitation threshold, determine the predicted participation resource amount of the target associated user and display it to the target object.

[0057] Step S208: Obtain the target object's signing instruction for the withholding agreement.

[0058] Step S210: Create a reservation task and send the task access link corresponding to the reservation task to the target associated user.

[0059] In practical applications, after sending a task access link to the target associated user, in order to improve the authorization efficiency of the scheduled task, the target object can send the task access link to the target associated user multiple times before the task deadline by triggering the configured secondary sending instruction. However, in order to avoid the target associated user receiving authorization invitation messages frequently and causing resentment and reducing user experience, in an optional implementation of this embodiment, when the secondary sending instruction submitted by the target object is detected, it is determined whether the time interval between the target object triggering the sending instruction meets the preset conditions.

[0060] If so, send the task access link to the target associated user according to the secondary sending instruction and display a notification of successful sending to the target object;

[0061] If not, a notification is sent to the target object indicating that the operation is too frequent.

[0062] For example, if applicant X invites multiple family members to participate in a family protection program, and after applicant X selects child A, spouse C, father D, and mother E as participants, the system checks whether applicant X has invited child A, spouse C, father D, and mother E to make appointments more than three times within a month. If so, an alert is sent to applicant X indicating that they do not have appointment privileges. If not, an invitation to sign a deduction agreement is sent to applicant X, and an appointment form for applicant X to participate in the protection program is created. After applicant X signs the deduction agreement, a message link dynamically generated by combining a link to the authorization confirmation page and the appointment number is generated and sent to child A, spouse C, father D, and mother E via SMS, in-app message, etc. If the participants do not confirm authorization for a long time, applicant X can send message links to the participants multiple times by triggering a secondary sending command. Specifically, if the applicant's child is too young to confirm authorization, the system automatically confirms authorization for the target associated user who does not have authorization capabilities after the applicant's selection.

[0063] In addition, if a target user associated with a task access link is detected to be close to the task deadline but has not submitted an authorization instruction, a reminder will be sent to the target user in order to improve the participation in the project and encourage the target user to trigger a second instruction.

[0064] In specific implementation, based on the above-mentioned generation of the reservation task, in order to effectively and promptly respond to the processing operation of the target associated user on the task access link, and at the same time to monitor the reservation task more timely, this embodiment provides an optional implementation, such as... Figure 3 As shown, the monitoring of the scheduled task is specifically implemented using the following steps S302 to S310:

[0065] In specific implementation, to ensure the validity of the reservation task, the reservation task authorization process in this embodiment includes steps S302 to S310:

[0066] Step S302: If the task access link is detected to be triggered, determine whether the task status of the scheduled task is canceled.

[0067] If so, no action needs to be taken;

[0068] If not, proceed to step S304.

[0069] Step S304: Determine whether the target associated user corresponding to the task access link has submitted the authorization instruction;

[0070] If so, proceed to step S308;

[0071] If not, proceed to step S306.

[0072] Step S306: Mark the task status of the scheduled task as cancelled.

[0073] Step S308: Determine whether all target associated users who sent the task access link have submitted the authorization instruction;

[0074] If so, then proceed to step S106, based on the authorization instruction submitted by the target associated user after triggering the task access link, and based on the identity information of the target associated user, determine the amount of resources the target associated user participates in for the guarantee project;

[0075] If not, proceed to step S310.

[0076] Step S310: Enter the task waiting period for the scheduled task.

[0077] It should be noted that the reservation task is in the task waiting period after it is created and within the task period. The "entering the task waiting period" mentioned in step S310 above means continuing to be in the task waiting period.

[0078] For example, applicant X invites multiple family members to participate in a family protection program. After the applicant selects child A, spouse C, father D, and mother E as participants, an appointment is created and a message link is sent to the participants. If spouse C accesses this message link, it is determined whether the appointment is cancelled. If cancelled, a cancellation notification is sent to spouse C. If not cancelled, the processing instruction submitted by spouse C is retrieved. If the submitted processing instruction is an authorization instruction, it is then determined whether child A, father D, and mother E have all submitted authorization instructions. If not, the appointment remains in the waiting period until all participants submit authorization instructions. If spouse C submits a rejection instruction, the authorization status of the participant corresponding to spouse C in the appointment is updated to the rejection status, and the appointment status is updated to the cancellation status.

[0079] In addition, in an optional implementation of this embodiment, the reservation task is monitored in the following manner:

[0080] If the task access link is detected to be triggered, determine whether the task deadline of the scheduled task has been exceeded;

[0081] If so, the task status of the scheduled task will be marked as cancelled;

[0082] If not, determine whether there is a rejection instruction in the processing instructions submitted by the target associated user who sent the task access link;

[0083] If so, the task status of the scheduled task will be marked as cancelled;

[0084] If not, determine whether the target associated user corresponding to the task access link has submitted the authorization instruction;

[0085] If the authorization instruction is submitted, determine whether all target associated users who sent the task access link have submitted the authorization instruction;

[0086] If not, then the task will enter the waiting period for the scheduled task.

[0087] It should be noted that, in the specific implementation process, the two methods for monitoring appointment tasks provided above can be combined to monitor appointment tasks more effectively and in a timely manner.

[0088] In addition, one or more of the two monitoring implementation methods can be used to monitor the reservation task. For example, if the task access link is detected to be triggered, it can be determined whether the task period of the reservation task has been exceeded.

[0089] If so, the task status of the scheduled task will be marked as cancelled;

[0090] If not, determine whether there is a rejection instruction in the processing instructions submitted by the target associated user who sent the task access link;

[0091] If so, the task status of the scheduled task will be marked as cancelled;

[0092] If not, proceed to step S106 or subsequent judgment processing.

[0093] For example, if the task access link is detected to be triggered, determine whether the target associated user corresponding to the triggering task access link has submitted the authorization instruction;

[0094] If so, proceed with step S106 or subsequent judgment processing.

[0095] If not, the task status of the scheduled task will be marked as cancelled.

[0096] Step S106: Based on the authorization instruction submitted by the target associated user after triggering the task access link, and based on the identity information of the target associated user, determine the amount of participation resources of the target associated user for the guarantee project.

[0097] In practical applications, target users can trigger a task access link, select whether to agree to the protection applicant's access and use their stored real-name information to participate in the protection project according to the pop-up instructions, and submit the corresponding submission authorization instruction or rejection instruction.

[0098] In practice, since the predicted age field of the target associated users may be biased, the predicted amount of participating resources may also be biased. In order to determine the actual amount of participating resources, if all the operation instructions submitted by the target associated users are authorization instructions, the identity information (age, ID number, etc.) of the target associated users is obtained.

[0099] Specifically, in order to determine the actual amount of resources involved in the project by the target associated users, this embodiment provides an optional implementation method, which specifically adopts the following operation:

[0100] Extract the feature fields contained in the identity information of the target associated user;

[0101] The amount of participation resources for the target associated user in the protection project is determined based on the age field included in the feature fields.

[0102] Using the previous example, after spouse c submits the authorization instruction, it is detected that child a, father d, and mother e have all submitted authorization instructions. Then, the identity information of child a, father d, mother e, and spouse c is obtained, and based on the age field in the identity information, the actual amount of resources that child a, father d, mother e, and spouse c participate in the protection project is determined respectively.

[0103] Step S108: Perform project participation processing based on the reservation task and the amount of participation resources to obtain the project participation details corresponding to the reservation task.

[0104] The project participation details include the insurance contract or insurance order generated after the insurance project takes effect; the project participation details record the details of the insurance project, as well as the details of the insurance applicant and insurance participants participating in the insurance project. The project participation details record resource deduction information generated during the participation in the insurance project, such as, in a multi-user insurance project, the deduction information includes the deduction time, deduction amount, and deducted resources, etc.

[0105] In specific implementation, after obtaining the authorization instructions submitted by all target associated users and determining the actual participation resource amount for each target associated user in the project guarantee based on the age field in the identity information, in order to improve the participation efficiency of the project guarantee, this embodiment provides an optional implementation method to generate project participation details in the following way:

[0106] Based on the reservation task and the participation amount, resources will be deducted from the target object's resource account.

[0107] Based on the resource deduction, project participation is processed, and project participation details corresponding to the reservation task are generated.

[0108] Specifically, the process of generating formal project participation details after the appointment task is authorized by the target associated user includes steps S402 to S408.

[0109] Step S402: If all the target associated users have submitted the authorization instructions, extract the feature fields from the identity information of the target associated users.

[0110] Step S404: Based on the age field in the feature fields, determine the amount of resources the target associated user will participate in for the protection project.

[0111] Step S406: Deduct resources from the target object's resource account based on the amount of participating resources.

[0112] Step S408: Process project participation based on the resource deduction and generate project participation details corresponding to the reservation task.

[0113] It should be noted that generating project participation details can be achieved by submitting all information related to the participation resource amount and the scheduled task to the support organization to which the project belongs, and obtaining project participation details generated by the support organization; or it can be achieved by directly generating project participation details based on authorization confirmed with the support organization to which the project belongs.

[0114] For example, if applicant X invites multiple family members to participate in a family protection program, selecting child A, spouse C, father D, and mother E as participants, and based on all participants submitting authorization instructions, the system obtains the pre-registered identity information of each participant and extracts the characteristic fields from that information. Based on the age field within these characteristic fields, the system determines the actual resource amount for each participant's participation in the program. Furthermore, according to applicant X's signed withholding agreement when creating the appointment form, the system deducts the required resource amount from applicant X's resource account. Finally, based on the deduction process and the program's participation details, a formal program participation record is generated.

[0115] Step S110: Based on the project participation details, construct the project sharing relationship between the target object and the target associated user.

[0116] The project sharing relationship refers to the data relationship used to share the project permissions of the target object for the insured project with the target associated user. Through this project sharing relationship, the target associated user enjoys the same permissions as the target object for the insured project to a certain extent, such as access permissions and claims permissions.

[0117] For example, Table 2 below shows the project sharing relationship data:

[0118] Project Number Project Product Code Target object ID Target associated user ID Expiry date bx001 sp001 208001 208001 xxxx-xx-xx bx001 sp001 208001 208002 xxxx-xx-xx bx001 sp001 208001 208003 xxxx-xx-xx

[0119] Table 2

[0120] Among them, the target object with target object ID 208001 invited the target associated user with target associated user ID 208002 and the target associated user with target associated user ID 208003 to participate in the multi-user protection project as protection participants. At the same time, the target object with target object ID 208001 also selected itself as a protection participant. The target associated user with target associated user ID 208001, the target associated user with target associated user ID 208002, and the target associated user with target associated user ID 208003 jointly participated in the multi-user protection project with project product code sp001, project order number bx001, and protection period ending xxxx-xx-xx.

[0121] In practical applications, only the target audience can view the project participation details; related users cannot initiate subsequent operations such as policy maintenance or claims. Specifically, to enhance the awareness of the project among the target audience and related users, and to enable related users to initiate subsequent operations such as policy maintenance or claims without contacting the target audience, this embodiment provides an optional implementation where, after generating the project participation details, the following steps are taken:

[0122] Share permissions for the target associated user regarding the project participation details of the target object;

[0123] Based on the shared permissions, the project participation details are sent to the target associated user.

[0124] In specific implementation, after establishing the project sharing relationship, in order to further enhance the awareness of the target associated users, this embodiment provides an optional implementation method in which project participation details are sent to the target associated users in the following way:

[0125] If an access request from the target associated user to the protected project is obtained, query whether there is a project sharing relationship that records the user identifier carried in the access request;

[0126] If so, query the project participation details corresponding to the project sharing relationship and send them to the target associated user;

[0127] The sharing period of the project sharing relationship is the same as the participation period of the project participation details.

[0128] Specifically, as shown in Table 2 above, during the query process, the target object ID that has a project sharing relationship with the target associated user ID is first queried, and then the project product code, project order number, and expiration time containing the project participation details of the target associated user ID and the target object ID are queried.

[0129] In addition, in an optional implementation of this embodiment, the target associated user can also query project participation details in the following way: first, open the access interface of the project sharing relationship to the target associated user; when the access interface is detected to be triggered, query the project participation details corresponding to the project sharing relationship and send them to the target associated user; wherein, the sharing period of the project sharing relationship is the participation period of the project participation details.

[0130] It should be noted that, regarding the two implementation methods for querying project participation details provided above, in specific implementation processes, the two query methods can be combined to perform more accurate queries on project participation details; in addition, one or more processing flows from the two query implementation methods can be used to query the project participation details. For example, firstly, the access interface for the project sharing relationship can be opened to the target associated user. When the access interface is detected to be triggered, it is checked whether there is a project sharing relationship that records the user identifier carried in the access request; if so, the project participation details corresponding to the project sharing relationship are queried and sent to the target associated user.

[0131] Based on this, after establishing a project sharing relationship, the target associated user can spontaneously perform subsequent operations related to the protection project without having to contact the target object when needed. This avoids affecting the experience of the target associated user due to the inability to contact the target object in a timely manner. In one optional implementation method provided in this embodiment, the project participation details corresponding to the project sharing relationship are first determined and sent to the target associated user; then, upon obtaining the protection instruction or claim instruction submitted by the target associated user for the protection project, the protection processing or claim processing for the target associated user is carried out according to the project participation details.

[0132] For example, applicant x invites multiple family members to participate in the family protection program. After selecting children a, spouse c, father d, and mother e as participants, and all of them confirm authorization to generate official program participation details, the program shares the applicant x's access to these details with children a, spouse c, father d, and mother e. Based on this sharing relationship, the program participation details are then distributed to children a, spouse c, father d, and mother e. Specifically, when an access request for the family protection program is detected, it checks if a sharing relationship exists that records the user identifier of the applicant carried in the access request. If it exists, the program participation details corresponding to this sharing relationship are found and distributed to the applicant who submitted the access request. It should be noted that the sharing period for the established sharing relationship between applicant x and children a, spouse c, father d, and mother e is the expiration date marked on the program participation details.

[0133] In addition, the target object in this embodiment can be a family project execution robot. The participation resource amount is the accumulated feature identifier in the family project. When the family project execution robot detects that the accumulated feature identifier has reached a value that meets the participation conditions and that the family member participating in the family project has not participated in the protection project, it can proactively generate a message link and send it to the family member. If all family members authorize it, the participation resource amount is determined according to the family member's identity information, the number of feature identifiers corresponding to the participation resource amount is deducted, and project participation details are generated. Finally, the sharing relationship of the family member with the project participation details is established. Reminders can also be sent to the family member to encourage them to accumulate the feature identifier to participate in the protection project.

[0134] The following is in conjunction with the appendix Figure 5 Taking the application of the project processing method provided in this embodiment in a multi-user assurance project as an example, the project processing method provided in this embodiment will be further explained. (Refer to...) Figure 2 The specific processing method for the family protection program includes steps S502 to S524.

[0135] Step S502: Obtain the insurance participants selected by the applicant from the list of associated users in the multi-user insurance project access.

[0136] Among them, multi-user protection programs include multi-user insurance programs, such as insurance programs outside the family.

[0137] Step S504: Create an appointment form for the applicant to participate in the multi-user protection program; and send the access link corresponding to the appointment form to the participants.

[0138] Step S506: If it is detected that the participant has accessed the access link, determine whether the status of the reservation order is cancelled.

[0139] If so, send a notification to the participants that the reservation has been cancelled;

[0140] If not, proceed to step S508.

[0141] Step S508: Determine whether the instruction submitted by the participant is an authorization instruction;

[0142] If so, proceed to step S510;

[0143] If not, mark the reservation status as cancelled.

[0144] Step S510: Determine whether all participants have submitted authorization instructions;

[0145] If so, proceed to step S512;

[0146] If not, proceed to the reservation waiting status.

[0147] Step S512: Extract the age field from the identity information of the participants.

[0148] Step S514: Determine the amount of resources for each participant in the multi-user protection program based on the age field.

[0149] Step S516: Deduct resources from the applicant's resource account according to the amount of resources involved.

[0150] Step S518: Process the participation of multiple users in the project protection project based on resource deduction and generate the project participation details corresponding to the reservation order.

[0151] Step S520: Based on the project participation details, establish a project sharing relationship between the applicant and the participants.

[0152] Step S522: Based on the project sharing relationship, the rights of the insurance applicants for the multi-user insurance project are shared among the insurance participants.

[0153] Step S524: Based on permission sharing, send project participation details to the participants.

[0154] In summary, the project processing method provided in this embodiment first obtains the target associated user selected from the list of associated users for project access guarantee. Then, it creates a reservation task for the target object to participate in the guarantee project and sends a task access link corresponding to the reservation task to the target associated user. Based on the authorization instruction submitted by the target associated user after triggering the task access link, and based on the target associated user's identity information, it determines the amount of resources the target associated user will participate in the guarantee project. Then, it processes project participation based on the reservation task and the amount of resources, obtaining the project participation details corresponding to the reservation task. Finally, based on the project participation details, it establishes a project sharing relationship between the target object and the target associated user. This saves resources and improves user experience through group buying.

[0155] The following is an embodiment of a project processing device provided in this specification:

[0156] In the above embodiments, a project processing method is provided, and correspondingly, a project processing device is also provided, which will be described below with reference to the accompanying drawings.

[0157] Reference Figure 6 The diagram shows a schematic of a project processing device provided in this embodiment.

[0158] Since the apparatus embodiments correspond to the method embodiments, the descriptions are relatively simple. For relevant parts, please refer to the corresponding descriptions of the method embodiments provided above. The apparatus embodiments described below are merely illustrative.

[0159] This embodiment provides a project processing device, including:

[0160] The associated user selection module 602 is configured to obtain the target associated user selected by the target object from the associated user list for ensuring project access;

[0161] The appointment task creation module 604 is configured to create an appointment task for the target object to apply to participate in the guarantee project, and send the task access link corresponding to the appointment task to the target associated user.

[0162] The participation resource amount determination module 606 is configured to determine the participation resource amount of the target associated user for the guarantee project based on the authorization instruction submitted by the target associated user after triggering the task access link and the identity information of the target associated user.

[0163] The project participation processing module 608 is configured to perform project participation processing based on the reservation task and the amount of participation resources, and obtain the project participation details corresponding to the reservation task.

[0164] The sharing relationship building module 610 is configured to build a project sharing relationship between the target object and the target associated user based on the project participation details.

[0165] Optionally, the project processing device further includes:

[0166] The task status determination module is configured to determine whether the task status of the scheduled task is canceled when the task access link is detected to be triggered.

[0167] If not, the processing instruction judgment module is run. The processing instruction judgment module is configured to determine whether the target associated user corresponding to the task access link has submitted the authorization instruction.

[0168] If the authorization instruction is submitted, the associated user judgment module is run. The associated user judgment module is configured to determine whether all target associated users who sent the task access link have submitted the authorization instruction; if not, the task waiting period for the scheduled task begins.

[0169] Optionally, the project processing device further includes:

[0170] The predicted age determination module is configured to determine the predicted age field of the target associated user based on the association relationship between the target object and the target associated user;

[0171] The predicted amount determination module is configured to determine the predicted amount of resources the target associated user will participate in for the protection project based on the predicted age field and display it to the target object;

[0172] The signing instruction determination module is configured to obtain the target object's signing instruction for the deduction agreement based on the display of the predicted amount of participating resources;

[0173] The deduction agreement includes the deduction cycle, deduction frequency, specified deduction time period and / or deduction payment channel.

[0174] Optionally, the project processing device further includes:

[0175] The task deadline determination module is configured to determine whether the task deadline of the scheduled task has been exceeded when the task access link is detected to be triggered.

[0176] If so, the task status update module is run, which is configured to mark the task status of the scheduled task as canceled.

[0177] If not, the rejection instruction judgment module is run. The rejection instruction judgment module is configured to determine whether there is a rejection instruction in the processing instruction submitted by the target associated user who sent the task access link.

[0178] Optionally, the project processing device further includes:

[0179] The permission sharing module is configured to share permissions for the target associated user regarding the project participation details of the target object;

[0180] The distribution module is configured to distribute the project participation details to the target associated user based on the permission sharing.

[0181] Optionally, the project processing device further includes:

[0182] The shared relationship query module is configured to, upon receiving an access request from the target associated user to the protected project, query whether there is a project shared relationship that records the user identifier carried in the access request.

[0183] If so, run the participation details query module, which is configured to query the project participation details corresponding to the project sharing relationship and send them to the target associated user;

[0184] The sharing period of the project sharing relationship is the same as the participation period of the project participation details.

[0185] Optionally, the project processing device further includes:

[0186] The access interface opening module is configured to open the access interface of the project sharing relationship to the target associated user;

[0187] The participation details distribution module is configured to, upon detecting that the access interface has been triggered, query the project participation details corresponding to the project sharing relationship and distribute them to the target associated user.

[0188] The sharing period of the project sharing relationship is the same as the participation period of the project participation details.

[0189] Optionally, the project processing device further includes:

[0190] The sharing relationship determination module is configured to determine the project participation details corresponding to the project sharing relationship and send them to the target associated user;

[0191] The processing module is configured to, upon receiving a preservation instruction or claim instruction submitted by the target associated user for the protection project, perform preservation processing or claim processing on the target associated user according to the project participation details.

[0192] Optionally, the task processing status recorded in the scheduled task is marked as the first processing status after the scheduled task is created;

[0193] If the processing instruction submitted by the target associated user is an authorization instruction, the task processing status is updated to the second processing status; or, if the processing instruction submitted by the target associated user is a rejection instruction, the task processing status is updated to the third processing status.

[0194] Optionally, if the task status of the scheduled task exceeds the task period contained in the scheduled task, the target object submits a rejection instruction, and / or at least one of the target associated users who sent the task access link submits a rejection instruction, the task status of the scheduled task will be updated to a cancelled status.

[0195] Optionally, the project processing device further includes:

[0196] The invitation count detection module is configured to detect the number of times the target object invites the target associated user within a preset time range;

[0197] The invitation permission freeze module is configured to freeze the reservation invitation permission of the target object when the number of reservation invitations exceeds the invitation number threshold.

[0198] Optionally, the project processing device further includes:

[0199] The detection module is configured to detect whether the target associated user has project participation details or appointment tasks for the guaranteed project;

[0200] If so, the invited permission freezing module is run. The invited permission freezing module is configured to send a failure reminder to the target object and / or freeze the invited permissions of the target associated user.

[0201] Optionally, the module for determining the amount of participating resources is specifically configured as follows:

[0202] Extract the feature fields contained in the identity information of the target associated user;

[0203] The amount of resources the target associated user participates in the protection project is determined based on the age field included in the feature fields.

[0204] Optionally, the project participation processing module is specifically configured as follows:

[0205] Based on the reservation task and the participation amount, resources will be deducted from the target object's resource account.

[0206] Based on the resource deduction, project participation is processed, and project participation details corresponding to the reservation task are generated.

[0207] Optionally, the project processing device further includes:

[0208] The secondary instruction monitoring module is configured to determine whether the time interval between the target object triggering the sending instruction meets a preset condition when a secondary sending instruction is detected submitted by the target object.

[0209] If so, the secondary sending module is run. The secondary sending module is configured to send the task access link to the target associated user according to the secondary sending instruction and display a notification of successful sending to the target object.

[0210] The following is an example of a project processing device provided in this specification:

[0211] Corresponding to the project processing method described above, based on the same technical concept, one or more embodiments of this specification also provide a project processing device for executing the project processing method described above. Figure 7 This is a schematic diagram of the structure of a project processing device provided for one or more embodiments of this specification.

[0212] like Figure 7 As shown, the project processing device can vary significantly due to differences in configuration or performance. It may include one or more processors 701 and memory 702, and the memory 702 may store one or more application programs or data. The memory 702 may be temporary or persistent storage. The application programs stored in the memory 702 may include one or more modules (not shown), each module may include a series of computer-executable instructions from the project processing device. Furthermore, the processor 701 may be configured to communicate with the memory 702 and execute the series of computer-executable instructions in the memory 702 on the project processing device. The project processing device may also include one or more power supplies 703, one or more wired or wireless network interfaces 704, one or more input / output interfaces 705, one or more keyboards 706, etc.

[0213] In one specific embodiment, the project processing device includes a memory and one or more programs, wherein the one or more programs are stored in the memory, and the one or more programs may include one or more modules, and each module may include a series of computer-executable instructions for use in the project processing device, and is configured to be executed by one or more processors. The one or more programs include computer-executable instructions for performing the following:

[0214] Retrieve the target associated user selected from the list of associated users for the project access guarantee;

[0215] Create a reservation task for the target object to participate in the guarantee project, and send the task access link corresponding to the reservation task to the target associated user;

[0216] Based on the authorization instruction submitted by the target associated user after triggering the task access link, and based on the identity information of the target associated user, the amount of resources the target associated user participates in for the protection project is determined;

[0217] Based on the reservation task and the amount of participation resources, the project participation process is performed to obtain the project participation details corresponding to the reservation task;

[0218] Based on the project participation details, a project sharing relationship is constructed between the target object and the target associated user.

[0219] Optionally, the computer-executable instructions, when executed, may also include:

[0220] If the task access link is detected to be triggered, determine whether the task status of the scheduled task is canceled.

[0221] If not, determine whether the target associated user corresponding to the task access link has submitted the authorization instruction;

[0222] If the authorization instruction is submitted, determine whether all target associated users who sent the task access link have submitted the authorization instruction;

[0223] If not, then the task will enter the waiting period for the scheduled task.

[0224] Optionally, the computer-executable instructions, when executed, may also include:

[0225] Based on the association between the target object and the target associated user, the predicted age field of the target associated user is determined;

[0226] Based on the predicted age field, determine the predicted amount of resources the target associated user will participate in the protection project and display it to the target object;

[0227] Based on the display of the predicted amount of participating resources, obtain the target object's signing instruction for the deduction agreement;

[0228] The deduction agreement includes the deduction cycle, deduction frequency, specified deduction time period and / or deduction payment channel.

[0229] Optionally, after the steps of creating the reservation task for the target object to participate in the guarantee project and sending the task access link corresponding to the reservation task to the target associated user are executed, and before the steps of determining the participation resource amount of the target associated user for the guarantee project based on the identity information of the target associated user according to the authorization instruction submitted by the target associated user after triggering the task access link are executed, the method further includes:

[0230] If the task access link is detected to be triggered, determine whether the task deadline of the scheduled task has been exceeded;

[0231] If so, the task status of the scheduled task will be marked as cancelled;

[0232] If not, determine whether there is a rejection instruction in the processing instructions submitted by the target associated user who sent the task access link;

[0233] If so, the task status of the scheduled task will be marked as cancelled;

[0234] If not, determine whether the target associated user corresponding to the task access link has submitted the authorization instruction;

[0235] If the authorization instruction is submitted, determine whether all target associated users who sent the task access link have submitted the authorization instruction;

[0236] If not, then the task will enter the waiting period for the scheduled task.

[0237] Optionally, after the step of constructing the project sharing relationship between the target object and the target associated user based on the project participation details is executed, the method further includes:

[0238] Share permissions for the target associated user regarding the project participation details of the target object;

[0239] Based on the shared permissions, the project participation details are sent to the target associated user.

[0240] Optionally, after the step of constructing the project sharing relationship between the target object and the target associated user based on the project participation details is executed, the method further includes:

[0241] If an access request from the target associated user to the protected project is obtained, query whether there is a project sharing relationship that records the user identifier carried in the access request;

[0242] If so, query the project participation details corresponding to the project sharing relationship and send them to the target associated user;

[0243] The sharing period of the project sharing relationship is the same as the participation period of the project participation details.

[0244] Optionally, after the step of constructing the project sharing relationship between the target object and the target associated user based on the project participation details is executed, the method further includes:

[0245] Open the access interface for the project sharing relationship to the target associated user;

[0246] Upon detecting that the access interface has been triggered, query the project participation details corresponding to the project sharing relationship and send them to the target associated user;

[0247] The sharing period of the project sharing relationship is the same as the participation period of the project participation details.

[0248] Optionally, after the step of constructing the project sharing relationship between the target object and the target associated user based on the project participation details is executed, the method further includes:

[0249] Determine the project participation details corresponding to the project sharing relationship and send them to the target associated user;

[0250] Upon receiving a preservation instruction or claim instruction submitted by the target associated user for the protection project, the preservation or claim processing shall be carried out on the target associated user in accordance with the project participation details.

[0251] This specification provides an example of a storage medium as follows:

[0252] Corresponding to the project processing method described above, and based on the same technical concept, one or more embodiments of this specification also provide a storage medium.

[0253] The storage medium provided in this embodiment is used to store computer-executable instructions, which, when executed, implement the following process:

[0254] Retrieve the target associated user selected from the list of associated users for the project access guarantee;

[0255] Create a reservation task for the target object to participate in the guarantee project, and send the task access link corresponding to the reservation task to the target associated user;

[0256] Based on the authorization instruction submitted by the target associated user after triggering the task access link, and based on the identity information of the target associated user, the amount of resources the target associated user participates in for the protection project is determined;

[0257] Based on the reservation task and the amount of participation resources, the project participation process is performed to obtain the project participation details corresponding to the reservation task;

[0258] Based on the project participation details, a project sharing relationship is constructed between the target object and the target associated user.

[0259] Optionally, the computer-executable instructions, when executed, also implement the following processes:

[0260] If the task access link is detected to be triggered, determine whether the task status of the scheduled task is canceled.

[0261] If not, determine whether the target associated user corresponding to the task access link has submitted the authorization instruction;

[0262] If the authorization instruction is submitted, determine whether all target associated users who sent the task access link have submitted the authorization instruction;

[0263] If not, then the task will enter the waiting period for the scheduled task.

[0264] Optionally, the computer-executable instructions, when executed, also implement the following processes:

[0265] Based on the association between the target object and the target associated user, the predicted age field of the target associated user is determined;

[0266] Based on the predicted age field, determine the predicted amount of resources the target associated user will participate in the protection project and display it to the target object;

[0267] Based on the display of the predicted amount of participating resources, obtain the target object's signing instruction for the deduction agreement;

[0268] The deduction agreement includes the deduction cycle, deduction frequency, specified deduction time period and / or deduction payment channel.

[0269] Optionally, after the steps of creating the reservation task for the target object to participate in the guarantee project and sending the task access link corresponding to the reservation task to the target associated user are executed, and before the steps of determining the participation resource amount of the target associated user for the guarantee project based on the identity information of the target associated user according to the authorization instruction submitted by the target associated user after triggering the task access link are executed, the method further includes:

[0270] If the task access link is detected to be triggered, determine whether the task deadline of the scheduled task has been exceeded;

[0271] If so, the task status of the scheduled task will be marked as cancelled;

[0272] If not, determine whether there is a rejection instruction in the processing instructions submitted by the target associated user who sent the task access link;

[0273] If so, the task status of the scheduled task will be marked as cancelled;

[0274] If not, determine whether the target associated user corresponding to the task access link has submitted the authorization instruction;

[0275] If the authorization instruction is submitted, determine whether all target associated users who sent the task access link have submitted the authorization instruction;

[0276] If not, then the task will enter the waiting period for the scheduled task.

[0277] Optionally, after the step of constructing the project sharing relationship between the target object and the target associated user based on the project participation details is executed, the method further includes:

[0278] Share permissions for the target associated user regarding the project participation details of the target object;

[0279] Based on the shared permissions, the project participation details are sent to the target associated user.

[0280] Optionally, after the step of constructing the project sharing relationship between the target object and the target associated user based on the project participation details is executed, the method further includes:

[0281] If an access request from the target associated user to the protected project is obtained, query whether there is a project sharing relationship that records the user identifier carried in the access request;

[0282] If so, query the project participation details corresponding to the project sharing relationship and send them to the target associated user;

[0283] The sharing period of the project sharing relationship is the same as the participation period of the project participation details.

[0284] Optionally, after the step of constructing the project sharing relationship between the target object and the target associated user based on the project participation details is executed, the method further includes:

[0285] Open the access interface for the project sharing relationship to the target associated user;

[0286] Upon detecting that the access interface has been triggered, query the project participation details corresponding to the project sharing relationship and send them to the target associated user;

[0287] The sharing period of the project sharing relationship is the same as the participation period of the project participation details.

[0288] Optionally, after the step of constructing the project sharing relationship between the target object and the target associated user based on the project participation details is executed, the method further includes:

[0289] Determine the project participation details corresponding to the project sharing relationship and send them to the target associated user;

[0290] Upon receiving a preservation instruction or claim instruction submitted by the target associated user for the protection project, the preservation or claim processing shall be carried out on the target associated user in accordance with the project participation details.

[0291] It should be noted that the embodiments concerning storage media and the embodiments concerning user resource processing methods in this specification are based on the same inventive concept. Therefore, the specific implementation of this embodiment can be referred to the implementation of the corresponding methods described above, and the repeated parts will not be described again.

[0292] The foregoing has described the characteristic embodiments of this specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recited in the claims may be performed in a different order than that shown in the embodiments and may still achieve the desired result. Furthermore, the processes depicted in the drawings do not necessarily require the shown sequence or sequential order of features to achieve the desired result. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.

[0293] In the 1930s, improvements to a technology could be clearly distinguished as either hardware improvements (e.g., improvements to the circuit structure of diodes, transistors, switches, etc.) or software improvements (improvements to the methodology). However, with technological advancements, many improvements to the methodology today can be considered direct improvements to the hardware circuit structure. Designers almost always obtain the corresponding hardware circuit structure by programming the improved methodology into the hardware circuit. Therefore, it cannot be said that an improvement to the methodology cannot be implemented using a hardware physical module. For example, a Programmable Logic Device (PLD) (e.g., a Field Programmable Gate Array (FPGA)) is such an integrated circuit whose logic function is determined by the user programming the device. Designers can program a digital system themselves to "integrate" it onto a PLD, without needing chip manufacturers to design and manufacture dedicated integrated circuit chips. Furthermore, nowadays, instead of manually manufacturing integrated circuit chips, this programming is mostly implemented using "logic compiler" software. Similar to the software compiler used in program development, the original code before compilation must also be written in a specific programming language, called a Hardware Description Language (HDL). There are many HDLs, such as ABEL (Advanced Boolean Expression Language), AHDL (Altera Hardware Description Language), Confluence, CUPL (Cornell University Programming Language), HDCal, JHDL (Java Hardware Description Language), Lava, Lola, MyHDL, PALASM, and RHDL (Ruby Hardware Description Language). Currently, the most commonly used are VHDL (Very-High-Speed ​​Integrated Circuit Hardware Description Language) and Verilog. Those skilled in the art should also understand that by simply performing some logic programming on the method flow using one of these hardware description languages ​​and programming it into an integrated circuit, the hardware circuit implementing the logical method flow can be easily obtained.

[0294] The controller can be implemented in any suitable manner. For example, it can take the form of a microprocessor or processor and a computer-readable medium storing computer-readable program code (e.g., software or firmware) executable by the (micro)processor, logic gates, switches, application-specific integrated circuits (ASICs), programmable logic controllers, and embedded microcontrollers. Examples of controllers include, but are not limited to, the following microcontrollers: ARC 625D, Atmel AT91SAM, Microchip PIC18F26K20, and Silicon Labs C8051F320. A memory controller can also be implemented as part of the control logic of the memory. Those skilled in the art will also recognize that, in addition to implementing the controller in purely computer-readable program code form, the same functionality can be achieved by logically programming the method steps to make the controller take the form of logic gates, switches, application-specific integrated circuits, programmable logic controllers, and embedded microcontrollers. Therefore, such a controller can be considered a hardware component, and the means included therein for implementing various functions can also be considered as structures within the hardware component. Alternatively, the means for implementing various functions can be considered as both software modules implementing the method and structures within the hardware component.

[0295] The systems, devices, modules, or units described in the above embodiments can be implemented by computer chips or entities, or by products with certain functions. A typical implementation device is a computer. Specifically, a computer can be, for example, a personal computer, laptop computer, cellular phone, camera phone, smartphone, personal digital assistant, media player, navigation device, email device, game console, tablet computer, wearable device, or any combination of these devices.

[0296] For ease of description, the above apparatus is described by dividing it into various functional units. Of course, when implementing the embodiments of this specification, the functions of each unit can be implemented in one or more software and / or hardware.

[0297] Those skilled in the art will understand that one or more embodiments of this specification can be provided as a method, system, or computer program product. Therefore, one or more embodiments of this specification may take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this specification may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0298] This specification is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this specification. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create a machine for implementing the flowchart illustrations and / or block diagrams. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0299] These computer program instructions may also be stored in a computer-readable storage medium capable of directing a computer or other programmable data processing device to operate in a characteristic manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0300] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0301] In a typical configuration, a computing device includes one or more processors (CPU), input / output interfaces, network interfaces, and memory.

[0302] Memory may include non-persistent storage in computer-readable media, such as random access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash RAM. Memory is an example of computer-readable media.

[0303] Computer-readable media includes both permanent and non-permanent, removable and non-removable media that can store information using any method or technology. Information can be computer-readable instructions, data structures, modules of programs, or other data. Examples of computer storage media include, but are not limited to, phase-change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, CD-ROM, digital versatile optical disc (DVD) or other optical storage, magnetic tape, magnetic magnetic disk storage or other magnetic storage devices, or any other non-transferable medium that can be used to store information accessible by a computing device. As defined herein, computer-readable media does not include transient computer-readable media, such as modulated data signals and carrier waves.

[0304] It should also be noted that the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0305] One or more embodiments of this specification can be described in the general context of computer-executable instructions, such as program modules, that are executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc., that perform a characteristic task or implement a characteristic abstract data type. One or more embodiments of this specification can also be practiced in distributed computing environments where tasks are performed by remote processing devices connected via a communication network. In a distributed computing environment, program modules can reside in local and remote computer storage media, including storage devices.

[0306] The various embodiments in this specification are described in a progressive manner. Similar or identical parts between embodiments can be referred to interchangeably. Each embodiment focuses on describing the differences from other embodiments. In particular, the system embodiments are basically similar to the method embodiments, so the description is relatively simple; relevant parts can be referred to the descriptions in the method embodiments.

[0307] The above description is merely an embodiment of this document and is not intended to limit the scope of this document. Various modifications and variations can be made to this document by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this document should be included within the scope of the claims of this document.

Claims

1. A project processing method, comprising: Retrieve the target associated users selected by the target object from the associated user list who are participating in the multi-user protection project; Create a reservation task for the target object to participate in the multi-user protection project, and send the task access link corresponding to the reservation task to the target associated user; If the task access link is detected to be triggered, determine whether all the target associated users who triggered the task access link have submitted authorization instructions; If so, extract the feature fields from the identity information of the target associated user, and determine the amount of resources the target associated user participates in the multi-user protection project based on the age field in the feature fields; Based on the amount of participating resources, resource deductions are made from the resource account of the target object, and project participation is processed based on the resource deductions, generating project participation details corresponding to the scheduled task.

2. The project processing method according to claim 1, after the step of performing project participation processing based on the resource deduction and generating the project participation details corresponding to the reservation task, further includes: Based on the project participation details, a project sharing relationship is constructed between the target object and the selected target associated user.

3. The project processing method according to claim 1 further includes: Based on the association between the target object and the selected target associated users, the predicted age field of the selected target associated users is determined; Based on the predicted age field, determine the predicted amount of resources the selected target associated user will participate in the protection project and display it to the target object; Based on the display of the predicted amount of participating resources, obtain the target object's signing instruction for the deduction agreement; The deduction agreement includes the deduction cycle, deduction frequency, specified deduction time period and / or deduction payment channel.

4. The project processing method according to claim 1 further includes: If the task access link is detected to be triggered, determine whether the task deadline of the scheduled task has been exceeded; If so, the task status of the scheduled task will be marked as cancelled; If not, determine whether there is a rejection instruction in the processing instructions submitted by the target associated user who sent the task access link; If so, the task status of the scheduled task will be marked as cancelled.

5. The project processing method according to claim 2, after the step of constructing the project sharing relationship between the target object and the selected target associated user based on the project participation details is executed, it further includes: Share permissions for the selected target users regarding the project participation details; Based on the shared permissions, the project participation details are sent to the selected target associated users.

6. The project processing method according to claim 2, after the step of constructing the project sharing relationship between the target object and the selected target associated user based on the project participation details is executed, it further includes: If the selected target associated user obtains an access request to the protected project, query whether there is a project sharing relationship that records the user identifier carried in the access request; If so, query the project participation details corresponding to the project sharing relationship and send them to the selected target associated user; The sharing period of the project sharing relationship is the same as the participation period of the project participation details.

7. The project processing method according to claim 2, after the step of constructing the project sharing relationship between the target object and the selected target associated user based on the project participation details is executed, it further includes: Open the access interface for the project sharing relationship to the selected target associated users; Upon detecting that the access interface has been triggered, query the project participation details corresponding to the project sharing relationship and send them to the selected target associated user; The sharing period of the project sharing relationship is the same as the participation period of the project participation details.

8. The project processing method according to claim 2, after the step of constructing the project sharing relationship between the target object and the selected target associated user based on the project participation details is executed, it further includes: Determine the project participation details corresponding to the project sharing relationship and send them to the selected target associated users; Upon receiving a preservation instruction or claim instruction submitted by the selected target associated user for the protection project, the preservation or claim processing shall be carried out on the selected target associated user in accordance with the project participation details.

9. The project processing method according to claim 1, wherein the task processing status recorded in the appointment task is marked as the first processing status after the appointment task is created; If the processing instruction submitted by the selected target associated user is an authorization instruction, the task processing status is updated to the second processing status; or, if the processing instruction submitted by the selected target associated user is a rejection instruction, the task processing status is updated to the third processing status.

10. The project processing method according to claim 1, wherein if the task status of the scheduled task exceeds the task period contained in the scheduled task, the target object submits a rejection instruction, and / or at least one of the target associated users who sent the task access link submits a rejection instruction, the task status of the scheduled task is updated to a cancelled status.

11. The project processing method according to claim 1, after the step of obtaining the target associated user selected by the target object in the list of associated users for project access is executed, and before the step of creating the reservation task for the target object to participate in the project and sending the task access link corresponding to the reservation task to the target associated user is executed, it further includes: Detect the number of appointment invitations made by the target object to the selected target associated user within a preset time range; If the number of appointment invitations exceeds the invitation limit, the appointment invitation privileges of the target object will be frozen.

12. The project processing method according to claim 1, further comprising: Detect whether the selected target associated user has project participation details or appointment tasks for the guaranteed project; If so, send a failure notification to the target object and / or freeze the invitation permissions of the selected target associated user.

13. The project processing method according to claim 1, after the steps of creating the reservation task for the target object to participate in the guarantee project and sending the task access link corresponding to the reservation task to the target associated user are executed, it further includes: If the target object is detected to have submitted a second sending instruction, determine whether the time interval between the target object triggering the sending instruction meets a preset condition; If so, the task access link is sent to the selected target associated user according to the secondary sending instruction, and a notification of successful sending is displayed to the target object.

14. A project processing method, comprising: The target object generates a message chain for the multi-user protection project and sends it to family members; The message jump chain is generated after the accumulated feature identifiers in the family project reach a value that meets the participation conditions and the family members participating in the family project have not participated in the multi-user protection project. If all family members have authorized the project, extract the feature fields from the identity information of the family members, and determine the amount of resources the family members participate in the multi-user protection project based on the age field in the feature fields. The number of feature identifiers corresponding to the amount of participating resources is deducted, and project participation details are generated.

15. The project processing method according to claim 14, wherein the target object includes: Family Project Execution Robot.

16. A project processing apparatus, comprising: The associated user selection module is configured to retrieve the target associated users selected by the target object from the associated user list who are participating in the multi-user protection project. The appointment task creation module is configured to create an appointment task for the target object to apply to participate in the multi-user protection project, and send the task access link corresponding to the appointment task to the target associated user. The task status judgment module is configured to determine whether all target associated users who triggered the task access link have submitted authorization instructions when the task access link is detected to be triggered. If so, the associated user judgment module is run. The associated user judgment module is configured to extract feature fields from the identity information of the target associated user and determine the amount of resources the target associated user participates in the multi-user protection project based on the age field in the feature fields. Based on the amount of participating resources, resource deductions are made from the resource account of the target object, and project participation is processed based on the resource deductions, generating project participation details corresponding to the scheduled task.

17. A project processing device, comprising: processor; as well as, A memory configured to store computer-executable instructions, which, when executed, cause the processor to: Retrieve the target associated users selected by the target object from the associated user list who are participating in the multi-user protection project; Create a reservation task for the target object to participate in the multi-user protection project, and send the task access link corresponding to the reservation task to the target associated user; If the task access link is detected to be triggered, determine whether all the target associated users who triggered the task access link have submitted authorization instructions; If so, extract the feature fields from the identity information of the target associated user, and determine the amount of resources the target associated user participates in the multi-user protection project based on the age field in the feature fields; Based on the amount of participating resources, resource deductions are made from the resource account of the target object, and project participation is processed based on the resource deductions, generating project participation details corresponding to the scheduled task.

18. A storage medium for storing computer-executable instructions, which, when executed, perform the following process: Retrieve the target associated users selected by the target object from the associated user list who are participating in the multi-user protection project; Create a reservation task for the target object to participate in the multi-user protection project, and send the task access link corresponding to the reservation task to the target associated user; If the task access link is detected to be triggered, determine whether all the target associated users who triggered the task access link have submitted authorization instructions; If so, extract the feature fields from the identity information of the target associated user, and determine the amount of resources the target associated user participates in the multi-user protection project based on the age field in the feature fields; Based on the amount of participating resources, resource deductions are made from the resource account of the target object, and project participation is processed based on the resource deductions, generating project participation details corresponding to the scheduled task.

Images