Association relationship determination method and apparatus, device, storage medium, and program product

Abstract

The present disclosure relates to an association relationship determination method and apparatus, a device, a storage medium, and a program product. The association relationship determination method comprises: acquiring an association state between a first object and a second object; when the association state indicates that a first association relationship exists between the first object and the second object, displaying an object addition control for the second object; in response to a trigger operation on the object addition control by the first object, generating and sending a verification request to the second object; and on the basis of a verification result generated by the second object for the verification request, determining a second association relationship between the first object and the second object, the second association relationship indicating that the first object has a permission associated with the second object.

Description

Method, device, and apparatus for determining association relationship, storage medium, and program product

[0001] Cross-reference to Related Applications

[0002] This application claims priority to Chinese Patent Application No. 202411337097.5, filed September 24, 2024, the disclosure of which is incorporated herein in its entirety as part of the present application. TECHNICAL FIELD

[0003] The present disclosure relates to a method, device, apparatus, storage medium, and program product for determining an association relationship. BACKGROUND

[0004] With the development of Internet technology, application programs of mobile terminals are increasingly favored. For example, an application program can support a user to publish content, and friends in the application program can access the content. However, the experience of interaction between users through the application program needs to be improved. SUMMARY

[0005] Therefore, the present disclosure provides a method, device, apparatus, storage medium, and program product for determining an association relationship.

[0006] In a first aspect, the present disclosure provides a method for determining an association relationship, comprising: obtaining an association state between a first object and a second object; if the association state indicates that the first object and the second object have a first association relationship, displaying an object adding control for the second object; in response to a triggering operation of the first object on the object adding control, generating a verification request and sending it to the second object; based on a verification result generated by the second object for the verification request, determining a second association relationship between the first object and the second object, the second association relationship indicating that the first object has a permission associated with the second object.

[0007] In a second aspect, the present disclosure provides a method for determining an association relationship, comprising: receiving a verification request initiated by a first object, and displaying the verification request on an object application interface, the first object and a second object having a first association relationship; in response to a feedback operation of the second object on the verification request, generating a verification result corresponding to the verification request; based on the verification result, constructing a second association relationship between the first object and the second object, and sending the verification result to the first object, so that the first object determines the second association relationship between the first object and the second object based on the verification result.

[0008] In a third aspect, the present disclosure provides a second association relationship determination apparatus, comprising: an acquisition module configured to acquire an association state between a first object and a second object; a control display module configured to display an object adding control for the second object if the association state indicates that the first object and the second object have a first association relationship; a verification request sending module configured to generate a verification request and send the verification request to the second object in response to a triggering operation of the first object on the object adding control; and a second association relationship determination module configured to determine a second association relationship between the first object and the second object based on a verification result generated by the second object for the verification request, the second association relationship indicating that the first object has a permission associated with the second object.

[0009] In a fourth aspect, the present disclosure provides a second association relationship determination apparatus, comprising: a verification request receiving module configured to receive a verification request initiated by a first object and display the verification request on an object application interface, the first object and a second object having a first association relationship; a verification result generating module configured to generate a verification result corresponding to the verification request in response to a feedback operation of the second object on the verification request; and a second association relationship constructing module configured to construct a second association relationship between the first object and the second object based on the verification result and send the verification result to the first object, so that the first object determines the second association relationship between the first object and the second object based on the verification result.

[0010] In a fifth aspect, the present disclosure provides an electronic device, comprising a memory and a processor, the memory and the processor being communicatively connected with each other, the memory storing computer instructions, and the processor executing the computer instructions to perform the association relationship determination method of the first aspect or any one of the corresponding embodiments thereof, or perform the association relationship determination method of the second aspect or any one of the corresponding embodiments thereof.

[0011] In a sixth aspect, the present disclosure provides a computer readable storage medium, the computer readable storage medium storing computer instructions, the computer instructions being used to make a computer execute the association relationship determination method of the first aspect or any one of the corresponding embodiments thereof, or execute the association relationship determination method of the second aspect or any one of the corresponding embodiments thereof.

[0012] In a seventh aspect, the present disclosure provides a computer program product, comprising computer instructions, the computer instructions being used to make a computer execute the association relationship determination method of the first aspect or any one of the corresponding embodiments thereof, or execute the association relationship determination method of the second aspect or any one of the corresponding embodiments thereof. BRIEF DESCRIPTION OF DRAWINGS

[0013] In order to more clearly illustrate the technical solutions in the specific embodiments of the present disclosure, the drawings needed to be used in the specific embodiments will be briefly introduced as follows. Obviously, the drawings in the following description are some embodiments of the present disclosure, and other drawings can also be obtained by those skilled in the art without creative effort on the basis of these drawings.

[0014] FIG. 1 is a flowchart of a method for determining an association relationship according to an embodiment of the present disclosure;

[0015] FIG. 2 is a schematic diagram of adding a control of a homepage display object according to an embodiment of the present disclosure;

[0016] FIG. 3 is a flowchart of another method for determining an association relationship according to an embodiment of the present disclosure;

[0017] FIG. 4 is a schematic diagram of pushing a second object in an information flow according to an embodiment of the present disclosure;

[0018] FIG. 5 is a schematic diagram of pushing a second object in a waterfall content according to an embodiment of the present disclosure;

[0019] FIG. 6 is a schematic diagram of pushing a second object in a social display interface according to an embodiment of the present disclosure;

[0020] FIG. 7 is a schematic diagram of pushing a second object in an association relationship application interface according to an embodiment of the present disclosure;

[0021] FIG. 8 is a schematic diagram of pushing a second object in an association relationship recommendation interface according to an embodiment of the present disclosure;

[0022] FIG. 9 is a schematic diagram of a verification interface according to an embodiment of the present disclosure;

[0023] FIG. 10 is a schematic diagram of displaying prompt information according to an embodiment of the present disclosure;

[0024] FIG. 11 is a schematic diagram of displaying an object adding control in an information interface according to an embodiment of the present disclosure;

[0025] FIG. 12 is a schematic diagram of triggering a second setting control according to an embodiment of the present disclosure;

[0026] FIG. 13 is a schematic diagram of triggering other controls according to an embodiment of the present disclosure;

[0027] FIG. 14 is a schematic diagram of an object adding control in a disabled state according to an embodiment of the present disclosure;

[0028] FIG. 15 is a flowchart of yet another method for determining an association relationship according to an embodiment of the present disclosure;

[0029] FIG. 16 is a schematic diagram of a target association object application interface according to an embodiment of the present disclosure;

[0030] FIG. 17 is a schematic diagram of a user content display interface according to an embodiment of the present disclosure;

[0031] FIG. 18 is a display schematic diagram of an excess prompt information according to an embodiment of the present disclosure;

[0032] FIG. 19 is a schematic diagram of a message type according to an embodiment of the present disclosure;

[0033] FIG. 20 is a schematic diagram of an application according to an embodiment of the present disclosure;

[0034] FIG. 21 is a schematic diagram of setting a note according to an embodiment of the present disclosure;

[0035] FIG. 22 is a schematic diagram of note information customization according to an embodiment of the present disclosure;

[0036] FIG. 23 is a structural block diagram of a determination device of an association relationship according to an embodiment of the present disclosure;

[0037] FIG. 24 is a structural block diagram of another determination device of an association relationship according to an embodiment of the present disclosure; and

[0038] FIG. 25 is a hardware structure schematic diagram of an electronic device according to an embodiment of the present disclosure. DETAILED DESCRIPTION

[0039] In order to make the purpose, technical scheme and advantages of the embodiments of the present disclosure clearer, the technical scheme in the embodiments of the present disclosure will be described clearly and completely below with reference to the drawings in the embodiments of the present disclosure. Obviously, the described embodiments are part of the embodiments of the present disclosure, rather than all the embodiments. Based on the embodiments in the present disclosure, all other embodiments obtained by those skilled in the art without creative labor are within the scope of protection of the present disclosure.

[0040] It can be understood that, before using the technical scheme disclosed in the embodiments of the present disclosure, the type, use range, use scenario, etc. of the personal information involved in the present disclosure should be informed to the user and the authorization of the user should be obtained through appropriate means according to relevant laws and regulations.

[0041] For example, when responding to the active request of the user, the prompt information is sent to the user to explicitly prompt the user that the operation requested to be executed will need to obtain and use the personal information of the user. Thus, the user can voluntarily choose whether to provide the personal information to the software or hardware such as electronic device, application program, server or storage medium, etc. which executes the operation of the technical scheme of the present disclosure according to the prompt information.

[0042] As an optional but non-limiting implementation, in response to receiving the active request of the user, the manner of sending the prompt information to the user may be, for example, a pop-up window manner, in which the prompt information may be presented in the form of text. In addition, the pop-up window may also carry a selection control for the user to select "agree" or "disagree" to provide personal information to the electronic device.

[0043] It can be understood that the above notification and user authorization process is only illustrative and does not limit the implementation of the present disclosure, and other manners meeting the relevant laws and regulations can also be applied to the implementation of the present disclosure.

[0044] It can be understood that the data involved in the technical solution (including but not limited to the data itself, the acquisition or use of the data) should comply with the requirements of the relevant laws and regulations and the relevant provisions.

[0045] The technical solution of the present disclosure determines the association relationship with the access permission of the published content of the other party, and needs to pass the verification of both parties on the basis of mutual attention or interaction, etc. to build the association relationship with the access permission of the published content of the other party. Therefore, the use experience of the user for the application program is further improved.

[0046] According to the embodiment of the present disclosure, a method for determining an association relationship is provided. It should be noted that the steps shown in the flowchart of the accompanying drawings can be executed in a computer system such as a group of computer executable instructions, and although the logical order is shown in the flowchart, in some cases, the steps shown or described can be executed in an order different from that shown here.

[0047] In the present embodiment, a method for determining an association relationship is provided, which can be used in electronic devices such as mobile phones, tablet computers, computers, etc. The electronic device used by the first object is taken as the execution subject in the present embodiment, and FIG. 1 is a flowchart of a method for determining an association relationship according to an embodiment of the present disclosure, as shown in FIG. 1, the flow includes the following steps:

[0048] In step S101, the association state between the first object and the second object is obtained.

[0049] The association state is used to represent whether the first object and the second object have a first association relationship of mutual association, such as mutual attention, mutual fans, etc. For example, mutual attention, mutual fans, and one-way attention represent that the first object and the second object have a first association relationship; and the absence of the above relationships represents that the first object and the second object do not have a first association relationship.

[0050] The electronic device is installed with an application program, and the first object realizes interaction with the second object by registering a corresponding account on the application program. The association state between the first object and the second object can be obtained by reading the account information of the first object.

[0051] Specifically, if the first object only has a temporary interaction with the second object, the first object can not establish a first association relationship with the second object, and accordingly, there is no first association relationship between the first object and the second object. If the first object hopes to have multiple interactions with the second object, before the first object interacts with the second object, the first object can apply to establish a first association relationship with the second object, and accordingly, the electronic device can interact the account of the first object with the account of the second object, and record the association information in the account information. Thus, by reading the association information corresponding to the account information, the association state between the first object and the second object can be determined.

[0052] In step S102, if the association state indicates that the first object and the second object have a first association relationship, an object adding control for the second object is displayed.

[0053] The object adding control is a control for triggering the first object to add the second object as a target association object. The association state is used to indicate different identifiers of the existence of the first association relationship and the non-existence of the first association relationship, for example, the identifier of the existence of the first association relationship is 1, and the identifier of the non-existence of the first association relationship is 0. By determining the identifier corresponding to the association state, whether the first object and the second object have the first association relationship can be determined.

[0054] If the association state indicates that the first object and the second object have a first association relationship, it means that the first object and the second object are associated with each other, and when the first object enters the home page of the second object, the object adding control will be displayed on the home page of the second object, as shown in FIG. 2.

[0055] In step S103, in response to the triggering operation of the first object on the object adding control, a verification request is generated and sent to the second object.

[0056] The verification request is a request generated when the first object applies to add the second object as a target association object. The verification request is used for the second object to verify the first object to determine whether to accept the application of the first object. Specifically, the first object clicks the object adding control, and accordingly, the application program in the electronic device can respond to the click operation of the first object to trigger a verification request for adding the second object as a target association object, and send the verification request to the second object, and the second object can receive and view the verification request through the application program.

[0057] In step S104, based on a verification result generated by the second object for the verification request, a second association relationship between the first object and the second object is determined, and the second association relationship indicates that the first object has an association permission with the second object.

[0058] After the second object views the verification request sent by the first object, the second object can view the homepage of the first object to learn the information of the first object, so as to determine whether to pass the verification request of the first object. If the second object passes the verification request initiated by the first object, a second association relationship is established between the first object and the second object, the first object and the second object are target association objects of each other, and each has a permission associated with the other. Specifically, the associated permission includes a permission to access the published content of the other party. It should be noted that the published content herein refers to public published content. For private published content, the access permission does not exist.

[0059] At the same time when the second object passes the verification request initiated by the first object, the second object generates a verification result for the verification request and sends the verification result to the first object through an application, so that the first object can know that the second object has passed the verification request and has the second association relationship with the second object.

[0060] The association relationship determination method provided in the embodiment can be used to determine whether to add the first object as a target association object through verification, thereby improving the user experience of the application.

[0061] In the embodiment, an association relationship determination method is provided, which can be used for electronic devices such as mobile phones, tablet computers, computers, and the like. The electronic device used by the first object is taken as an execution subject in the embodiment. FIG. 3 is a flowchart of the association relationship determination method according to the embodiment of the disclosure. As shown in FIG. 3, the flowchart includes the following steps:

[0062] In step S201, the association state between the first object and the second object is obtained. For details, please refer to the related description of the corresponding step in the above embodiment, which will not be repeated here.

[0063] In step S202, if the association state indicates that the first object and the second object have a first association relationship, an object adding control for the second object is displayed.

[0064] Specifically, step S202 can include the following steps:

[0065] In step S2021, in response to a trigger operation of the first object on the object identifier of the second object, an information interface of the second object is displayed, and an object adding control is displayed on the information interface.

[0066] The information interface is used to display attribute information of the second object. The information interface includes a nickname, an avatar, a published work, associated object data (such as a number of likes, a number of followings, and a number of fans) of the second object, and the like.

[0067] In a specific embodiment, the first object can click a position where the second object is located in the non-reply area to enter a homepage of the second object, so as to display the information interface on the homepage. The information interface displays the nickname, the avatar, the number of likes, the number of followings, the number of fans, the first association relationship between the first object and the second object, signature information, and the published work of the second object. Meanwhile, the object adding control is displayed on the information interface. The object adding control can be arranged above the published work. In addition, a private message control can be arranged to support the first object to send a private message to the second object, as shown in FIG. 2.

[0068] By triggering the second object to enter the information interface of the second object and displaying the object adding control on the information interface, the adding experience of the first object for the second object is improved.

[0069] Specifically, the above step S202 can include:

[0070] In step S2022, an information push interface associated with the second object is displayed, and the object adding control is displayed on the information push interface corresponding to the second object.

[0071] The information push interface is an interface for displaying the second object. The object adding control is displayed on the information push interface, so that the first object can select the second object of interest from the object adding control for adding. The application program in the electronic device can display the information push interface associated with the second object to the first object according to the social data of the first object, so as to realize the push for the second object.

[0072] By displaying the object adding control on the information push interface corresponding to the second object, the scene of adding the second object by the first object is enriched, which is conducive to improving the adding willingness of the first object.

[0073] In some optional embodiments, the information push interface pushes the second object in the form of a card.

[0074] The appearance and layout of the push card are designed in advance, including the position and style of elements such as a title, a picture, a description, and a button. Attribute information of the second object associated with the first object is obtained from a database of the application program, and the obtained attribute information is filled into a corresponding position of the card to ensure the accuracy and integrity of the information. Meanwhile, interactive elements such as an object adding button can be added to the card, so that the first object can perform an object adding operation. After the card is assembled, the card is pushed to the first object in the application program, so that the attribute information of the second object is presented to the first object in a simple and intuitive manner through the card.

[0075] In some optional embodiments, the displaying of the information push interface associated with the second object in step S2022 comprises:

[0076] Step a1, displaying the information push interface associated with the second object in the media content stream display interface.

[0077] Step a2, displaying the information push interface associated with the second object in the preset interface associated with the first object.

[0078] The media content stream is a continuous transmission of multimedia data, such as audio, video, image, text, etc., by an application through a network. The media content stream allows the first object to play the content corresponding to the multimedia data in real time while receiving the multimedia data. The preset interface is a browsing interface preset for the first object to display the information push interface. When the first object browses the media content through the preset interface, the information push interface can be displayed in the media content stream display interface of the preset interface.

[0079] In some specific embodiments, according to the social network relationship of the first object, the information push interface is displayed in the information stream to recommend the second object associated with the first object to the first object. The second object can be one or multiple, as shown in FIG. 4.

[0080] In some specific embodiments, when the user performs a browsing operation on the media stream content, the information push interface can be displayed in the displayed media stream content to recommend the second object related to the interest of the first object, i.e., the information push interface associated with the second object is embedded in the display of the media stream content, as shown in FIG. 5. The information push interface can also be displayed when it is detected that the media stream content browsing is ended to push the second object to the first object, i.e., the push display of the information push interface associated with the second object is at the bottom of the media stream content, as shown in FIG. 5.

[0081] In some specific embodiments, the preset interface can be a user content display interface for displaying social sharing content published by other objects. The first object can switch from other interfaces to the user content display interface to browse the social sharing content. If it is detected that the social sharing content displayed in the user content display interface is empty, the information push interface can be displayed in the user content display interface to push the second object, so that the first object can add the second object, as shown in FIG. 6.

[0082] In some embodiments, the preset interface can be a second association relationship application interface, which is used to display the verification request sent by the other object to the first object. The first object can switch from other interfaces to the second association relationship application interface to view the verification request received by the first object. As shown in FIG. 7, after the first object enters the second association relationship application interface, the information recommendation interface can be displayed below the verification request display area to push the second object.

[0083] In some embodiments, the preset interface can be a second association relationship recommendation interface, which is used to display a plurality of second objects having a first association relationship with the first object. The first object can switch from other interfaces to the second association relationship recommendation interface to view the second objects associated with the first object, so as to select the second object interested by the first object for object addition. As shown in FIG. 8, after the first object enters the second association relationship recommendation interface, the second object is pushed and displayed in the second association relationship recommendation interface.

[0084] The embodiments support pushing the second object in various application scenarios, enrich the pushing mode of the second object, make the pushing mode more diversified, and thus enable the first object to understand the second object associated with the first object in various scenarios.

[0085] In step S203, in response to the triggering operation of the first object on the object addition control, a verification request is generated and sent to the second object.

[0086] Specifically, the above step S203 includes:

[0087] In step S2031, in response to the triggering operation of the first object on the object addition control, a verification interface is displayed, and the verification interface includes a verification request sending control.

[0088] The verification interface is an interface for displaying verification information, and the verification request sending control is provided on the verification interface, which can be in the form of a button. As shown in FIG. 9, when the first object triggers the object addition control, the verification interface is pulled up from the current interface, and the verification request sending button is displayed on the verification interface.

[0089] In step S2032, in response to the triggering operation on the verification request sending control, a verification request is generated and sent to the second object.

[0090] When the first object triggers the verification request sending control, the application responds to the triggering operation of the first object, generates a verification request according to the verification information displayed on the verification interface, and sends the verification request to the second object, so that the second object can check the verification request and confirm whether to build a second association relationship with the first object.

[0091] The method for determining the association relationship provided in this embodiment can pop up a verification interface when the object adding component is triggered, so as to send a verification request to the second object in the verification interface, thereby realizing the construction of the second association relationship in a verification manner, and improving the construction experience of the second association relationship.

[0092] In some optional embodiments, the verification interface includes a verification information input area for inputting verification information. Accordingly, the step S2032 includes:

[0093] In step b1, the verification information is obtained in response to an information input operation in the verification information input area.

[0094] In step b2, a verification request is generated according to the verification information and sent to the second object in response to a triggering operation on the verification request sending control.

[0095] As shown in FIG. 9, the verification information input area is included in the verification interface, and the verification information input area supports the first object to input verification information. Specifically, the first object can click the verification information input area to pull up an input component (for example, a keyboard component), and input verification information into the verification information input area through the input component. After the input of the verification information is completed, the first object can trigger the verification request sending control to send the verification information.

[0096] The method for determining the association relationship provided in this embodiment supports editing verification information in the verification interface, so as to send the verification information together with the verification request, which facilitates the second object to confirm the identity information of the first object according to the verification information, and is beneficial to improving the pass rate of the verification request.

[0097] In some optional embodiments, the method further includes saving the verification information, and displaying the saved verification information in the verification information input area when the first object triggers the object adding control again.

[0098] After the first object sends the verification request, the electronic device saves the verification information corresponding to the verification request. When the first object triggers the object adding control again to request to add other objects, the verification information saved last time is displayed in the verification interface that is popped up.

[0099] It should be noted that if the first object clears the verification information and sends the verification request, the verification information in the verification interface pulled up next time is also empty, that is, consistent with the verification information when the verification request is triggered last time.

[0100] The method for determining the association relationship provided in this embodiment supports saving the verification information, so as to be used directly next time when the verification request is sent, thereby avoiding repeated input of the same verification information, and improving the verification request sending experience of the first object.

[0101] In some optional embodiments, the method further includes: if the sending of the verification request is successful, displaying first prompt information indicating that the sending of the verification request is successful.

[0102] After triggering the sending of the verification request, the electronic device can monitor the sending state of the verification request to determine whether the sending of the verification request is successful. When it is determined that the sending of the verification request is successful, the first prompt information is displayed in the interface for adding the second object, and the first prompt information indicates that the sending of the verification request is successful. For example, the first prompt information can be "application for adding an object has been sent", as shown in FIG. 10.

[0103] The method for determining the association relationship provided in this embodiment supports the display of prompt information when the sending of the verification request is successful, so that the first object can determine the sending state of the verification request.

[0104] In some optional embodiments, the method further includes: if the number of times of sending the verification request reaches a preset value, displaying second prompt information indicating that the verification is being waited for.

[0105] The preset value is a maximum number of times of sending the verification request by the first object to the same second object that is allowed in advance. If the first object does not receive the verification result fed back by the second object, the first object can repeatedly send the verification request to the second object, and the number of times of sending the verification request by the first object is accumulated. When the number of times of sending the verification request reaches the preset value, the sending of the verification request is refused again, and the second prompt information is displayed in the interface for adding the second object, and the second prompt information indicates that the number of times of sending the verification request is over the limit. For example, the second prompt information can be "you have added the other party for many times, please wait for the application patiently", as shown in FIG. 10.

[0106] In a specific example, the first object A can add the second object B for many times, and the upper limit of adding the second object B is 5 times (i.e., sending the verification request 5 times) every six natural months (6 natural months are counted from the date of adding the second object for the first time), and more than the number of times is regarded as over the limit of the number of times of sending. When the object adding control is triggered again, the second prompt information "you have added the other party for many times, please wait for the application patiently" is displayed.

[0107] The method for determining the association relationship provided in this embodiment supports the display of prompt information when the number of times of sending the verification request is too large, so as to remind the first object that the number of times of sending the verification request is too large, and avoid repeated sending by the user.

[0108] In some optional embodiments, the method further includes: if the sending of the verification request fails, displaying third prompt information indicating that the verification request is modified.

[0109] In one specific example, if the verification information is unavailable, the verification request cannot be successfully sent. For example, the number of words of the verification information exceeds the limit, which causes the verification request to be unable to be sent. At this time, a third prompt information can be displayed on the interface for adding the second object to inform the first object to modify the verification information in the verification request through the third information. For example, the third information can be "the verification information is unavailable, please modify and retry", as shown in FIG. 10.

[0110] In one specific example, if the verification request fails to be sent due to network problems, a third prompt information can also be displayed on the interface for adding the second object to inform the first object that the verification request fails to be sent through the third information. For example, the third information can be "your network is unstable, please retry", as shown in FIG. 10.

[0111] The method for determining the association relationship provided in the embodiment supports the display of the prompt information when the verification request fails to be sent, so that the first object can resend the verification request in time.

[0112] In some optional embodiments, the verification interface further includes a remark information input area, and the remark information input area is used for inputting a remark for the second object. Correspondingly, the method further includes:

[0113] Step c1, in response to an information input operation in the remark information input area, the remark information for the second object is acquired.

[0114] Step b2, in response to the establishment of the second association relationship between the first object and the second object, the second object is displayed based on the remark information.

[0115] As shown in FIG. 9, the verification interface includes a remark information input area, which supports the first object to input the remark information for the second object. Specifically, the first object can click the remark information input area to pull an input component (for example, a keyboard component), and input the remark information into the remark information input area through the input component. After the input of the verification information and / or the remark information is completed, the first object can trigger the verification request sending control to send the verification information.

[0116] When the second object passes the verification request sent by the first object, the construction of the second association relationship between the first object and the second object is completed. At this time, the second object is displayed in the target association object list of the first object according to the remark information, so that the first object can quickly retrieve the second object having the target association relationship with the first object according to the remark information.

[0117] The method for determining the association relationship provided in the embodiment supports editing the remark information when sending the verification request, and displaying the second object according to the remark information after the construction of the second association relationship is completed, so that the first object can quickly retrieve the second object according to the remark information.

[0118] In some optional embodiments, the method further includes: if the remark information is unavailable, displaying fourth prompt information for modifying the remark information.

[0119] The input of the remark information is subject to a character limit, and if the number of characters of the remark information exceeds the limit, the remark information will be unavailable. If the remark information is unavailable, the verification request cannot be successfully sent. At this time, fourth prompt information can be displayed on the interface for adding the second object to inform the first object to modify the remark information in the verification request. For example, the fourth information can be "remark information is unavailable, please modify and try again", as shown in FIG. 10.

[0120] The method for determining the association relationship provided in the embodiment supports displaying prompt information when the remark information is unavailable, so that the first object can modify the remark information in time.

[0121] In some optional embodiments, the method further includes:

[0122] Step d1, determining whether the interactive association between the first object and the second object meets a preset condition, and obtaining a determination result.

[0123] Step d2, based on the determination result, determining to display an object adding control or a target control for the second object on an information interface of the second object, the target control including a first association control indicating to establish an association relationship with the second object or a second association control indicating that the first object and the second object have established an association relationship.

[0124] The preset condition is a condition for determining that the first object and the second object have an interactive association, for example, the first object and the second object follow each other, the first object and the second object are fans of each other, the first object follows the second object unilaterally, the second object follows the first object unilaterally, or the first object and the second object have interactive information. The preset condition is not limited here, and can be determined by a person skilled in the art according to actual needs.

[0125] The first association control is used to indicate the association relationship between the first object and the second object, and the second association control is used to indicate that the first object and the second object have the association relationship. The association state between the first object and the second object is detected, and it is determined whether the interactive association between the first object and the second object meets the preset condition. If it is determined that the interactive association between the first object and the second object meets the preset condition, the object adding control or the target control for the second object is displayed on the information interface of the second object. The target control includes the first association control indicating the establishment of the association relationship with the second object or the second association control indicating that the first object and the second object have established the association relationship.

[0126] In some optional embodiments, the step d2 comprises:

[0127] The step d21 displays the object adding control for the second object on the information interface of the second object in response to the determination that the interactive association between the first object and the second object meets the preset condition.

[0128] The step d22 displays the target control on the information interface of the second object in response to the determination that the interactive association between the first object and the second object meets the preset condition.

[0129] If it is determined that the interactive association between the first object and the second object meets the preset condition of the mutual association, the object adding control for the second object is displayed on the information interface of the second object when the first object enters the information interface of the second object.

[0130] If it is determined that the interactive association between the first object and the second object meets the preset condition of the one-sided association, the target control for the second object is displayed on the information interface of the second object when the first object enters the information interface of the second object.

[0131] In some optional embodiments, the step d22 of displaying the target control on the information interface of the second object can comprise:

[0132] The step e1 determines whether the first association relationship exists between the first object and the second object.

[0133] The step e2 displays the second association control on the information interface of the second object if the first association relationship exists between the first object and the second object.

[0134] The step e3 displays the first association control on the information interface of the second object if the first association relationship does not exist between the first object and the second object.

[0135] The first association relationship is used to represent whether the first object and the second object are associated with each other, for example, mutual attention, mutual fans, and the like. If the first object and the second object have the first association relationship, it indicates that the first object and the second object are associated with each other, and the second association control (for example, “followed”) is displayed on the information interface of the second object. If the first object and the second object do not have the first association relationship, it indicates that the first object and the second object are not associated with each other, and the first association control (for example, “follow”) is displayed on the information interface of the second object.

[0136] Specifically, if the first object and the second object do not have the first association relationship, it can be detected whether the first object and the second object have an interactive association. Specifically, the interactive association can include work interaction, one-way association, and address book friends in the case that the user fully authorizes the address book, and the like. Here, the content of the interactive association is not limited.

[0137] If the first object and the second object have the interactive association, the first association control for the second object is displayed on the information interface of the second object.

[0138] If the first association relationship between the first object and the second object is determined by determining the identifier corresponding to the association state, it is determined that the first object and the second object do not have the first association relationship, and the social relationship data of the first object is further acquired. By analyzing the social relationship data of the first object, it is determined whether the first object and the second object have an interactive association. If the first object and the second object have the interactive association, and the second object is the first interactive association object of the first object, when the first object enters the information interface of the second object, the object adding control is displayed on the information interface of the second object.

[0139] If the first object and the second object have the interactive association, and the second object is the second interactive association object of the first object, when the first object enters the information interface of the second object, the second association control (for example, “followed”) and the setting control are displayed on the information interface of the second object. When the first object triggers the setting control of the information interface, the object adding control is displayed on the setting interface corresponding to the setting control, as shown in FIG. 12.

[0140] If the first object and the second object have the interactive association, and the second object is the third interactive association object of the first object, when the first object enters the information interface of the second object, the first association control (for example, “follow”) is displayed on the information interface of the second object. When the first object triggers the association control, the object adding control is displayed on the information interface of the second object.

[0141] The first object can click the object adding control to trigger an adding process for the second object. Specifically, the application program responds to the operation of the first object clicking the object adding control, triggers a verification request for adding the second object as a target associated object, and sends the verification request to the second object, which can then receive and view the verification request through the application program.

[0142] In some optional embodiments, as shown in FIG. 11, the above method further includes:

[0143] Step f1, displaying a second association control and a first setting control in the information interface of the second object.

[0144] Step f2, in response to the triggering operation of the first object on the first setting control, displaying a first setting interface, the first setting interface including a preset adding control.

[0145] Step f3, in response to the triggering operation of the first object on the preset adding control, generating a verification request and sending it to the second object.

[0146] The first object clicks the first setting control. Accordingly, the application program can respond to the clicking operation of the first object on the first setting control, pop up the first setting interface from the information interface, and display the preset adding control in the first setting interface.

[0147] Then, the first object can click the preset adding control. Accordingly, the application program can respond to the clicking operation of the first object on the preset adding control, pop up a verification interface from the first device interface to send a verification request to the second object through the verification interface.

[0148] By integrating the adding control in the first setting control, the first object is provided with multiple ways to add the second object, which facilitates the first object to select the desired adding method according to actual needs.

[0149] In some optional embodiments, the above method further includes:

[0150] Step e1, if there is no interactive association between the first object and the second object, displaying a first association control for the second object.

[0151] Step e2, in response to the triggering operation of the first object on the first association control, constructing a first association relationship between the first object and the second object.

[0152] Step e3, if the first association relationship is successfully constructed, displaying a second association control and a second setting control.

[0153] Step e4, in response to the triggering operation of the first object on the second setting control, displaying a second setting interface, the second setting interface including a preset adding control.

[0154] Step e5, in response to the first object triggering the preset adding control, generating a verification request and sending it to the second object.

[0155] Step e6, if the first association relationship fails to be built, generating a fifth prompt information indicating the association failure, and rejecting the verification request sent by the object adding.

[0156] If there is no interactive association between the first object and the second object, it means that the second object is a stranger compared with the first object. At this time, when the first object enters the information interface of the second object, the first association control (for example, "follow") is displayed in the information interface of the second object, as shown in FIG. 13. By clicking the first association control, the first association relationship between the first object and the second object is built, that is, the first object unilaterally associates the second object. By clicking other controls (for example, "…" shown in FIG. 13), the related attribute information can be set in the pop-up interface, for example, canceling the association, setting the note information, etc.

[0157] When it is determined that the first association relationship between the first object and the second object is successfully built, the second association control and the second setting control are displayed in the information interface of the second object, as shown in FIG. 12.

[0158] The first object clicks the second setting control. Correspondingly, the application can pop up a second setting interface from the information interface in response to the click operation of the first object on the second setting control, and the preset adding control is displayed in the second setting interface.

[0159] Then, the first object can click the preset adding control. Correspondingly, the application can pop up a verification interface from the second device interface in response to the click operation of the first object on the preset adding control, so as to send a verification request to the second object through the verification interface.

[0160] When it is determined that the first association relationship between the first object and the second object fails to be built, the application rejects to send the verification request sent by the object adding to the second object, and triggers the display of the fifth prompt information, which represents the association failure between the first object and the second object. At this time, the first object can trigger the second association control again to request the first association relationship with the second object.

[0161] The association relationship determination method provided in the embodiment supports building the first association relationship first and then triggering the adding of the second object when there is no interactive association between the first object and the second object, which ensures the construction of the second association relationship to be more secure and improves the construction experience of the user for the second association relationship.

[0162] In some optional embodiments, the above method further comprises:

[0163] Step g1, determining whether the second object is a private object based on the account attribute information of the second object.

[0164] Step g2, if the second object is a private object and there is no first association relationship between the first object and the second object, the object adding control is in a disabled state.

[0165] The account attribute information is used to represent the attributes of the object, and a private account flag is set in the account attribute information. By analyzing the account attribute information of the second object, it can be determined whether the second object is a private object. If the second object is a private object and there is no first association relationship between the first object and the second object, the first object cannot add the second object as a target associated object.

[0166] If the first object wants to build a second association relationship with the second object, the first object needs to apply to build a first association relationship with the second object, and when the second object passes the association request, the first association relationship between the first object and the second object is built. At this time, if the first object only associates the second object unilaterally, the object adding control will still be in a disabled state, as shown in FIG. 14. Only when the first object and the second object have a mutual association relationship, the first object can trigger the object adding control to send a verification request for object addition to the second object.

[0167] When other objects add objects to private objects, their object adding controls are in a disabled state, ensuring the privacy of private objects.

[0168] Step S204, determining a second association relationship between the first object and the second object based on a verification result generated by the second object for the verification request, the second association relationship indicating that the first object has an association permission with the second object.

[0169] Specifically, the above step S204 includes:

[0170] Step S2041, if the verification result represents that the second object passes the verification request, it is determined that a target second association relationship is generated between the first object and the second object, and the target second association relationship is used to represent that the first object has a permission to access the content published by the second object.

[0171] If the second object passes the verification request sent by the first object, that is, a target second association relationship is generated between the first object and the second object, so that the first object has a permission to access the content published by the second object, at the same time, the second object also has a permission to access the content published by the first object.

[0172] Accordingly, when the second object passes the verification request, the application program can feed back the verification result generated by the second object for the verification request to the first object, and the first object can determine that the target second association relationship has been generated between the first object and the second object.

[0173] In step S2042, if the verification result indicates that the second object fails to pass the verification request, it is determined that the original first association relationship between the first object and the second object is maintained, and the original first association relationship is used to indicate that the first object does not have the permission to access the content published by the second object.

[0174] If the second object fails to pass the verification request sent by the first object, that is, the original first association relationship between the first object and the second object is maintained, the first object does not have the permission to access the content published by the second object, and the second object also does not have the permission to access the content published by the first object.

[0175] Accordingly, when the second object fails to pass the verification request, the application program can feed back the verification result generated by the second object for the verification request to the first object, and the first object can determine that the target second association relationship has not been generated between the first object and the second object. If the first object still wants to access the content published by the second object, it can send a verification request to the second object again.

[0176] The association relationship determination method provided in the embodiment can determine whether the verification request passes in combination with the verification result, thereby being able to determine the second association relationship between the first object and the second object according to whether the verification request passes or not, and thereby determining the permission of the first object to the content published by the second object, and avoiding that the content published by the second object is accessed randomly.

[0177] In the embodiment, an association relationship determination method is provided, which can be used in electronic devices such as mobile phones, tablet computers, computers and the like. In the embodiment, the electronic device used by the second object is taken as an execution subject. FIG. 15 is a flowchart of a second association relationship determination method according to the embodiment of the disclosure, as shown in FIG. 15, the flowchart includes the following steps:

[0178] In step S301, a verification request initiated by a first object is received, and the verification request is displayed on an association object application interface, and the first object and a second object have a first association relationship.

[0179] As described above, when the first object has the first association relationship with the second object, the first object generates a corresponding verification request when triggering the object adding control for adding the second object as a target association object, and sends the verification request to the second object. Specifically, the electronic device used by the second object also has an application installed thereon, and the application receives the verification request initiated by the first object. The second object can check the verification request initiated by the first object in an association object application interface, as shown in FIG. 16.

[0180] In step S302, a verification result corresponding to the verification request is generated in response to a feedback operation of the second object on the verification request.

[0181] The feedback operation is a verification operation performed by the second object on the verification request initiated by the first object, and the feedback operation can be performed by clicking a verification label corresponding to the verification request. As shown in FIG. 16, the second object can click the "go to verification" label corresponding to the verification request to verify the first object, so as to generate a verification result for the first object.

[0182] In step S303, a second association relationship between the first object and the second object is constructed based on the verification result, and the verification result is sent to the first object, so that the first object determines the second association relationship between the first object and the second object based on the verification result.

[0183] After the second object completes the verification on the first object, a corresponding second association relationship between the first object and the second object is constructed according to the verification result. Specifically, if the second object passes the verification request initiated by the first object, a second association relationship between the first object and the second object is constructed; if the second object does not pass the verification request initiated by the first object, the original first association relationship between the first object and the second object is maintained. Meanwhile, the second object sends the verification result to the first object through the application, so that the first object can determine the second association relationship between the first object and the second object according to the verification result.

[0184] The determination method of the association relationship provided in the embodiment can receive the verification request initiated by the first object, and feed back the verification request, so as to construct a second association relationship between the first object and the second object in combination with the verification result fed back by the second object, further strengthening the determination method of the second association relationship, and improving the user experience of the application.

[0185] In some optional embodiments, the above method further includes: displaying the number of association object applications in the user content display interface, wherein the number of association object applications is the sum of the number of new verification requests and the number of new application messages.

[0186] The user content display interface is used to display dynamic information published by a target associated object, the target associated object being an object having a second association relationship with the second object and having the permission to access the content published by the second object. The associated object application number is the number of new information initiated by the application to the second object.

[0187] Specifically, the associated object application number is displayed in the user content display interface, so that the second object can intuitively know the number of application messages currently received. The associated object application number is the sum of the number of new verification requests and the number of new application messages, wherein the number of new verification requests is the number of new verification requests received by the second object, and the number of new application messages is the number of messages sent by new application friends.

[0188] In some optional embodiments, the associated object application number is displayed in the form of a bubble at the top of the user content display interface. As shown in FIG. 17, the associated object application number is displayed at the top of the user content display interface and in the form of a bubble, so as to avoid affecting the display of dynamic information in the user content display interface.

[0189] In some optional embodiments, the above method further comprises:

[0190] Step A1, obtaining the message type corresponding to the second object.

[0191] Step A2, updating the associated object application number based on the message type.

[0192] The message type represents the message style of the message received by the second object and the message style of the message sent by the second object. Specifically, as shown in FIG. 19, the message type can include: (1) the second object receives a verification request of the first object, and the verification request carries verification information; (2) the second object receives a verification request of the first object, and the verification request does not carry verification information; (3) the second object receives a verification request of the first object, and the second object has clicked to pass; (4) the second object sends a verification request to another object; (5) the second object sends a verification request to another object, and the verification request carries verification information, and the other object replies to the verification information; (6) the second object sends a verification request to another object, and the other object has clicked to pass; (7) the second object receives a verification request of the first object, and the verification request has expired; (8) the second object sends a verification request to another object, and the verification request has expired.

[0193] If the message type of the message received by the second object is (1), (2), (5), or (6), the associated object application number will be updated.

[0194] The associated relationship determination method provided in this embodiment supports multiple message types, enriches the message style, and thus enables the verification request to meet various user needs.

[0195] In some optional embodiments, the method further includes: in response to a click operation of the second object on the association object application number, displaying an association object application interface, and the association object application number disappearing from the user content display interface; wherein the association object application interface includes an application information display list, and the application information display list includes at least one application information.

[0196] The second object can click the association object application number in the user content display interface, and accordingly, the application program can switch from the user content display interface to the association object application interface in response to the click operation of the second object on the association object application number in the user content display interface. As shown in FIG. 16, the application information display list is displayed in the association object application interface, and at least one application information is displayed in the application information display list. When switching back from the association object application interface to the user content display interface, the association object application number will disappear from the user content display interface.

[0197] The method for determining the association relationship provided in the embodiment supports hiding of the association object application number, thereby ensuring the content display effect of the user content display interface.

[0198] In some optional embodiments, the method further includes: if the verification request is a new verification request, displaying a new sign at a list position of the new verification request; wherein the new sign disappears when entering the association object application interface next time.

[0199] The new sign is displayed on the new verification request, and the new sign represents that the verification request is newly received by the second object. As shown in FIG. 16, the new sign can be a small dot and is displayed in front of the new verification request. When the second object exits from the association object application interface and enters the association object application interface again, the new sign displayed last time will disappear.

[0200] The method for determining the association relationship provided in the embodiment supports adding the new sign before the new verification request, highlights the display of the user identifier of the new verification request, so that the second object can filter the new verification request according to the new sign.

[0201] In some optional embodiments, each verification request is displayed in the application information display list in chronological order. Specifically, each verification request can be sorted in chronological order from recent to remote, for example, the verification request of the first object A is arranged at the xth position, when the reply information of the first object A is added or a new verification request is received again, the application information display list will update the time stamp of each application information and re-sort according to the updated time stamp.

[0202] The application provides a method for determining an association relationship, which can sequentially display application information of each verification request by time sorting, so that the display of the verification request can be sequenced.

[0203] In some optional embodiments, the application information display list comprises at least one page, and the page is used to display the verification request received in different time intervals.

[0204] The different time intervals are used to represent different time ranges, such as the last three days, three days ago, half a year ago, and the like, as shown in FIG. 16. The application information display list can be divided according to different time intervals to obtain a page corresponding to each time interval, and the verification request received in the corresponding time interval is displayed in each page.

[0205] The application provides a method for determining an association relationship, which supports paging of the verification request according to different time intervals, facilitates the second object to view and manage the verification request in different time intervals, and improves the efficiency and readability of information display.

[0206] In some optional embodiments, the method further comprises: when the number of newly received verification requests exceeds a preset number, displaying an excess prompt information on the association object application interface.

[0207] The preset number is a preset verification request quantity used to represent excess. The number of newly received verification requests of the second object is counted, and the number of newly received verification requests is compared with the preset number to determine whether the number of newly received verification requests exceeds the preset number. If the number of newly received verification requests exceeds the preset number, the excess prompt information is displayed on the association object application interface.

[0208] As shown in FIG. 18, the excess prompt information can be displayed in the form of a prompt bar. When the number of newly received verification requests exceeds the preset number, the prompt information “received too many strange messages, please set the target association object” is displayed in the prompt bar. If the second object clicks the excess prompt information, the second object can enter the addition setting interface, and set an addition condition in the addition setting interface. The addition condition can be used to filter subsequent verification requests, and the verification request that does not meet the addition condition is rejected.

[0209] The application provides a method for determining an association relationship. When the number of newly received verification requests exceeds the preset number, the second object can see the excess prompt information on the association object application interface, so that the second object can timely understand the current received verification request and take corresponding processing measures.

[0210] In some optional embodiments, the method further comprises:

[0211] Step B1, in response to the closing operation for the excess prompt information, the excess prompt information is closed.

[0212] Step B2, when the number of times of triggering the closing operation reaches a preset number of times, the excess prompt information is no longer displayed.

[0213] As shown in FIG. 18, the excess prompt information has a corresponding closing label, i.e., the excess prompt information allows closing. When the second object clicks the closing label corresponding to the excess prompt information, the application can respond to the closing operation of the second object and close the excess prompt information.

[0214] The preset number of times is a preset number of times of closing the excess prompt display, for example, 3 times. When the second object clicks the closing label, the application can count the number of times of triggering the closing operation of the second object, and compare the number of times with the preset number of times to determine whether the number of times of triggering the closing operation reaches the preset number of times. If the number of times of triggering the closing operation reaches the preset number of times, the excess prompt information is no longer displayed. When the newly received verification request reaches the preset number of times, the excess prompt information is triggered to be displayed again.

[0215] The determination method of the association relationship provided in the embodiment supports closing of the excess prompt information, and the excess prompt information is no longer displayed when the number of closing times reaches a preset number of times, thereby realizing flexible closing of the excess prompt information.

[0216] In some optional embodiments, the above method further includes:

[0217] Step C1, in response to a deletion operation for the application information of the first object, the application information is removed from the application information display list.

[0218] Step C2, if the first object initiates a verification request again, the application information corresponding to the verification request will be displayed in the application information display list again.

[0219] The deletion operation is an operation of deleting the verification request initiated by the first object by the second object. The deletion operation can be triggered by long pressing the verification request. As shown in FIG. 19, the second object can long press the verification request to trigger the display of the “delete notification” button, and click the “delete notification” to remove the verification request from the application information display list.

[0220] After deleting the verification request initiated by the first object, if the first object repeatedly sends a verification request to the second object, the deleted verification request of the first object will be displayed in the application information display list again.

[0221] In some optional embodiments, if the second object replies to the verification information carried in the verification request initiated by the first object and deletes the verification request after the reply, the verification information corresponding to the deleted verification request of the first object is displayed in the application information display list again when the first object replies to the reply message of the second object.

[0222] The method for determining the association relationship provided in the embodiment supports deletion of the verification request, so that the second object can delete the verification request that is not interested in according to actual needs, and provides the second object with the selectivity of the verification request.

[0223] In some optional embodiments, the method further includes: if the second association relationship between the first object and the second object is released, the verification request corresponding to the first object is removed from the application information display list.

[0224] When the second object releases the second association relationship between the first object and the second object, the first object can no longer send a message to the second object, and the verification request sent by the first object to the second object is also removed from the application information display list.

[0225] The method for determining the association relationship provided in the embodiment releases the second association relationship, and the corresponding application information is deleted, so that it is ensured that the verification request displayed in the application information display list is meaningful, and the display of meaningless verification request is avoided.

[0226] In some optional embodiments, the method further includes:

[0227] Step D1, if the verification request carries the verification information, a reply control is displayed in the area where the verification request is located.

[0228] Step D2, in response to a trigger operation on the reply control, an information reply area is displayed.

[0229] Step D3, in response to an information editing operation in the information reply area, reply information corresponding to the verification information is generated.

[0230] When the verification request received by the second object is the verification request carrying the verification information, the second object can reply to the verification information. As shown in FIG. 16, if the verification request carries the verification information, a reply control is displayed in the area where the verification request is located.

[0231] The second object can click the reply control to reply to the verification information. When it is detected that the second object clicks the reply control, the information reply area is popped up, and the second object can input reply information in the information reply area. Specifically, the second object clicks the information reply area, and the information input component (such as a keyboard input component) is popped up. The second object can edit in the information reply area through the information input component, generate corresponding reply information, and send the reply information to the first object. If the sending of the reply information fails, a sending failure prompt information can be generated, for example, “sending failure, please retry”. At this time, the second object can resend the reply information to the first object.

[0232] Specifically, the reply scenario between the first object and the second object includes: (1) the verification information is carried in the verification request when the first object adds the second object, and the second object can reply to the verification information; (2) the verification information is carried in the verification request when the first object adds the second object, and the second object has replied to the verification information, and the first object can reply to the reply of the second object.

[0233] It should be noted that continuous reply is supported between the first object and the second object, and when the number of continuous replies reaches a preset reply number (for example, 20), the reply control will no longer be displayed.

[0234] The determination method of the association relationship provided in the embodiment supports replying to the verification information, facilitates the first object and the second object to communicate through the reply information, thereby strengthening the interaction between the first object and the second object, and is beneficial to improving the pass rate of the verification request through the reply information.

[0235] In some optional embodiments, the above method further includes: if the first object is in the blacklist, the reply information sent by the first object is rejected.

[0236] If the second object refuses to build the second association relationship with the first object and replies to the verification information to inform the first object of the refusal to add, the second object will pull the first object into the blacklist. Therefore, when the first object sends reply information to the second object, the reply information cannot be sent.

[0237] If the second object pulls the first object into the blacklist without reading the reply information of the first object after receiving the reply information of the first object, the reply information will be deleted.

[0238] If the second object pulls the first object into the blacklist after viewing the reply message of the first object, the second object will no longer receive any information sent by the first object, and the historical messages received will be displayed in an expired manner.

[0239] The method for determining the association relationship provided in the embodiment can reject the message of the first object if the first object is in the blacklist, thereby avoiding the second object from being disturbed by the first object and protecting the rights and interests and information security of the second object.

[0240] In some optional embodiments, the method further includes:

[0241] Step E1, displaying a remark editing area in response to a remark triggering operation for the first object.

[0242] Step E2, generating the remark information corresponding to the first object in response to an input operation for the remark editing area.

[0243] When the second object requests the authentication of the first object, the second association relationship is established between the first object and the second object, as shown in FIG. 20. At this time, the second object can make a remark for the first object for subsequent searching. As shown in FIGS. 21 and 22, the second object displays a remark editing area when triggering a remark operation for the first object, and the second object can input the remark information in the remark editing area.

[0244] The method for determining the association relationship provided in the embodiment supports the editing of the remark information, and realizes the customization of the alternative information.

[0245] In some optional embodiments, the method further includes: if there is remark information for the first object, displaying the remark information in the remark editing area when triggering the remark operation for the first object.

[0246] If the first object exists in the address book of the second object, it indicates that the first object has remark information, and the name of the first object in the address book can be displayed in the remark editing area when triggering the remark operation for the first object, and the name is used as the remark information of the first object.

[0247] If the first object does not exist in the address book of the second object, but the remark information of the first object exists in the authentication information, the remark information in the authentication information can be displayed in the remark editing area when triggering the remark operation for the first object.

[0248] If there is historical remark information for the first object, the historical remark information can be displayed in the remark editing area when triggering the remark operation for the first object.

[0249] It should be noted that the remark information supports the index authentication information and the address book name, and the index priority of the address book name is higher than that of the authentication information.

[0250] In some optional embodiments, if the note editing area is empty, or if the complete button or the close button of the note editing area is clicked, the note operation is skipped.

[0251] The method for determining an association relationship provided in this embodiment supports displaying note information according to an index, thereby realizing intelligent display of note information.

[0252] In some optional embodiments, the method further includes: if the generation of the verification result fails, displaying retry prompt information.

[0253] If the second object fails to pass the verification request due to a network problem or the like, the corresponding retry prompt information (for example, "failed to pass, please retry") can be generated and displayed, so as to remind the second object to pass the verification request again.

[0254] The method for determining an association relationship provided in this embodiment supports displaying retry prompt information when the generation of the verification result fails, so that the second object can learn about the verification result of the verification request in a timely manner.

[0255] In this embodiment, a device for determining an association relationship is also provided, which is used to implement the above-described embodiments and will not be described again. As used below, the term "module" can be a combination of software and / or hardware that implements a predetermined function. Although the device described in the following embodiments is preferably implemented in software, implementation in hardware, or a combination of software and hardware, is also possible and is contemplated.

[0256] The device for determining an association relationship provided in this embodiment includes the following modules, as shown in FIG. 23:

[0257] The obtaining module 401 is configured to obtain an association state between a first object and a second object.

[0258] The control display module 402 is configured to, if the association state indicates that the first object and the second object have a first association relationship, display an object adding control for the second object.

[0259] The verification request sending module 403 is configured to, in response to a trigger operation of the first object on the object adding control, generate a verification request and send the verification request to the second object.

[0260] The second association relationship determining module 404 is configured to determine a second association relationship between the first object and the second object based on a verification result generated by the second object for the verification request, the second association relationship indicating that the first object has a permission associated with the second object.

[0261] In some optional embodiments, the control display module 402 includes:

[0262] The first display unit is configured to display an information interface of the second object in response to a triggering operation of the first object on the object identification of the second object, and display an object adding control on the information interface.

[0263] In some optional embodiments, the control display module 402 includes:

[0264] The pushing unit is configured to display an information pushing interface associated with the second object, and display the object adding control on the information pushing interface corresponding to the second object.

[0265] In some optional embodiments, the pushing unit includes:

[0266] The first information pushing interface display unit is configured to display the information pushing interface associated with the second object on the media content stream display interface.

[0267] The second information pushing interface display unit is configured to display the information pushing interface associated with the second object on a preset interface associated with the first object.

[0268] In some optional embodiments, the verification request sending module 403 includes:

[0269] The first response unit is configured to display a verification interface in response to a triggering operation of the first object on the object adding control, the verification interface including a verification request sending control.

[0270] The second response unit is configured to generate and send a verification request to the second object in response to a triggering operation on the verification request sending control.

[0271] In some optional embodiments, the verification interface includes a verification information input area, and correspondingly, the second response unit includes:

[0272] The verification information input subunit is configured to obtain verification information in response to an information input operation on the verification information input area.

[0273] The first generation subunit is configured to generate and send a verification request to the second object according to the verification information in response to a triggering operation on the verification request sending control.

[0274] In some optional embodiments, the verification request sending module 403 described above further includes:

[0275] The saving unit is configured to save the verification information, and display the saved verification information on the verification information input area when the first object triggers the object adding control again.

[0276] In some optional embodiments, the verification interface further includes a remark information input area, and the verification request sending module 403 described above further includes:

[0277] The note information input unit is configured to acquire the note information for the second object in response to an information input operation in the note information input area.

[0278] The note display unit is configured to display the second object based on the note information in response to establishment of the second association relationship between the first object and the second object.

[0279] In some optional embodiments, the apparatus further includes:

[0280] The interactive association determination module is configured to determine whether the interactive association between the first object and the second object meets a preset condition and acquire a determination result.

[0281] The control display module is configured to determine, based on the determination result, whether to display an object adding control for the second object or a target control in an information interface of the second object, the target control including a first association control indicating establishment of an association relationship with the second object or a second association control indicating that the first object and the second object have established an association relationship.

[0282] In some optional embodiments, the control display module includes:

[0283] The first control display unit is configured to display, in response to a determination that the interactive association between the first object and the second object meets the preset condition, the object adding control for the second object in the information interface of the second object.

[0284] The second control display unit is configured to display, in response to a determination that the interactive association between the first object and the second object meets the preset condition, the target control in the information interface of the second object.

[0285] In some optional embodiments, the second control display unit includes:

[0286] The association detection subunit is configured to determine whether the first association relationship exists between the first object and the second object.

[0287] The first display subunit is configured to display the second association control in the information interface of the second object if the first association relationship exists between the first object and the second object.

[0288] The first display subunit is configured to display the first association control in the information interface of the second object if the first association relationship does not exist between the first object and the second object.

[0289] In some optional embodiments, the first display subunit is specifically configured to: display the second associated control and the first setting control in the information interface of the second object; in response to the triggering operation of the first object on the first setting control, display the first setting interface, the first setting interface including a preset adding control; and in response to the triggering operation of the first object on the preset adding control, generate the verification request and send the verification request to the second object.

[0290] In some optional embodiments, the second association relationship determination module 404 includes:

[0291] The first determination module is configured to determine that the target second association relationship is generated between the first object and the second object if the verification result indicates that the second object passes the verification request, and the target second association relationship is used to indicate that the first object has the permission to access the content published by the second object.

[0292] The second determination module is configured to determine that the original first association relationship is maintained between the first object and the second object if the verification result indicates that the second object fails the verification request, and the original first association relationship is used to indicate that the first object does not have the permission to access the content published by the second object.

[0293] The further function descriptions of the above modules and units are the same as those of the corresponding embodiments, and will not be repeated here.

[0294] The association relationship determination apparatus in this embodiment is presented in the form of functional units. The units refer to ASIC (Application Specific Integrated Circuit) circuits, processors and memories executing one or more software or fixed programs, and / or other devices that can provide the above functions.

[0295] The association relationship determination apparatus provided in this embodiment, when the first object and the second object have the first association relationship, if the first object wants to build the second association relationship between the first object and the second object, the first object needs to initiate a verification request to the second object. According to the verification result generated by the second object in response to the verification request, it is determined whether the first object can have the permission associated with the second object. Thus, it is realized that whether the first object is added as the target associated object is determined through verification, and the user experience of using the application program is improved.

[0296] This embodiment provides an association relationship determination apparatus, as shown in FIG. 24, which includes:

[0297] The verification request receiving module 501 is configured to receive the verification request initiated by the first object, and display the verification request in the associated object application interface, and the first object and the second object have the first association relationship.

[0298] The verification result generation module 502 is configured to generate a verification result corresponding to the verification request in response to a feedback operation of the second object to the verification request.

[0299] The second association relationship construction module 503 is configured to construct a second association relationship between the first object and the second object based on the verification result, and send the verification result to the first object, so that the first object determines the second association relationship between the first object and the second object based on the verification result.

[0300] In some optional embodiments, the apparatus further includes:

[0301] The reply module is configured to display a reply control in an area where the verification request is located, if the verification request carries the verification information.

[0302] The reply area display module is configured to display an information reply area in response to a triggering operation on the reply control.

[0303] The reply information editing module is configured to generate reply information corresponding to the verification information in response to an information editing operation in the information reply area.

[0304] Further function descriptions of the above-mentioned modules and units are the same as those of the corresponding embodiments, and will not be described here.

[0305] The association relationship determination apparatus in the embodiment is presented in the form of a functional unit. The unit refers to an ASIC (Application Specific Integrated Circuit) circuit, a processor and a memory executing one or more software or fixed programs, and / or other devices that can provide the above functions.

[0306] The association relationship determination apparatus provided in the embodiment can feed back the verification request when the second object receives the verification request of the first object, so as to construct the second association relationship between the first object and the second object in combination with the feedback verification result of the second object. The determination manner of the second association relationship is further strengthened, and the use experience of the user for the application program is improved.

[0307] The disclosure further provides an electronic device with the association relationship determination apparatus shown in FIG. 23 or FIG. 24.

[0308] Referring to FIG. 25, FIG. 25 is a structural schematic diagram of an electronic device according to an optional embodiment of the present disclosure. As shown in FIG. 25, the electronic device includes one or more processors 10, a memory 20, and interfaces for connecting various components, including high-speed interfaces and low-speed interfaces. The various components communicate with each other using different buses, and can be mounted on a common mainboard or in other manners as needed. The processor can process instructions executed within the electronic device, including instructions stored in the memory or graphical information of a GUI stored in the memory for displaying on an external input / output device (such as a display device coupled to the interface). In some optional embodiments, multiple processors and / or multiple buses can be used with multiple memories and multiple memory banks, if necessary. Also, multiple electronic devices can be connected, each providing part of the necessary operations (for example, as a server array, a group of blade servers, or a multi-processor system). In FIG. 25, one processor 10 is taken as an example.

[0309] The processor 10 can be a central processor, a network processor, or a combination thereof. The processor 10 can further include a hardware chip. The hardware chip can be an application specific integrated circuit, a programmable logic device, or a combination thereof. The programmable logic device can be a complex programmable logic device, a field programmable logic device, a general array logic, or any combination thereof.

[0310] The memory 20 stores instructions executable by the at least one processor 10, so that the at least one processor 10 executes the method shown in the above embodiments.

[0311] The memory 20 can include a program storage area and a data storage area. The program storage area can store an operating system and application programs required by at least one function; the data storage area can store data created according to the use of the electronic device, etc. In addition, the memory 20 can include a high-speed random access memory, and can also include a non-transitory memory, such as at least one magnetic disk storage device, a flash memory device, or other non-transitory solid-state memory device. In some optional embodiments, the memory 20 can optionally include a memory remotely disposed relative to the processor 10, which can be connected to the electronic device through a network. Examples of the network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and a combination thereof.

[0312] The memory 20 can include a volatile memory, such as a random access memory; the memory can also include a non-volatile memory, such as a flash memory, a hard disk, or a solid-state disk; and the memory 20 can further include a combination of the above types of memories.

[0313] The electronic device also includes an input device 30 and an output device 40. The processor 10, the memory 20, the input device 30, and the output device 40 can be connected by a bus or other means, and are connected by a bus in FIG. 25 as an example.

[0314] The input device 30 can receive inputted digital or character information, and generate key signal input relating to user settings and function control of the electronic device, such as a touch screen, a keypad, a mouse, a trackpad, a touchpad, a pointing stick, one or more mouse buttons, a trackball, a joystick, etc. The output device 40 can include a display device, an auxiliary lighting device (e.g., an LED), a tactile feedback device (e.g., a vibration motor), etc. The display device includes, but is not limited to, a liquid crystal display, a light emitting diode, a display, and a plasma display. In some alternative embodiments, the display device can be a touch screen.

[0315] The electronic device also includes a communication interface for communication of the electronic device with other devices or communication networks.

[0316] The embodiments of the present disclosure also provide a computer readable storage medium, and the method according to the embodiments of the present disclosure can be implemented in hardware, firmware, or recorded in a storage medium, or be implemented as computer code originally stored in a remote storage medium or non-transitory machine readable storage medium downloaded through a network and stored in a local storage medium, so that the method described herein can be processed by such software on a storage medium using a general purpose computer, a special purpose processor, or programmable or special purpose hardware. The storage medium can be a magnetic disk, an optical disk, a read-only memory, a random access memory, a flash memory, a hard disk, or a solid state disk, etc. Further, the storage medium can also include a combination of the above-mentioned types of memories. It can be understood that the computer, the processor, the microprocessor controller, or the programmable hardware includes a storage component that can store or receive software or computer code, when the software or computer code is accessed and executed by the computer, the processor, or the hardware, the method shown in the above embodiments is implemented.

[0317] Part of the present disclosure can be applied as a computer program product, for example, computer program instructions, when executed by a computer, through the operation of the computer, the method and / or technical solutions according to the present disclosure can be invoked or provided. Those skilled in the art should understand that the form of computer program instructions in computer readable medium includes but is not limited to source file, executable file, installation package file and the like, and accordingly, the way of computer program instructions executed by computer includes but is not limited to: the computer directly executes the instructions, or the computer compiles the instructions and then executes the corresponding compiled program, or the computer reads and executes the instructions, or the computer reads and installs the instructions and then executes the corresponding installed program. Here, the computer readable medium can be any available computer readable storage medium or communication medium accessible to the computer.

[0318] Although the embodiments of the present disclosure are described in conjunction with the drawings, various modifications and changes can be made by those skilled in the art without departing from the spirit and scope of the present disclosure, and such modifications and changes fall within the scope defined by the appended claims.

Claims

1. A method for determining an association relationship, comprising: obtaining an association state between a first object and a second object; in response to the association state indicating that the first object and the second object have a first association relationship, displaying an object adding control for the second object; in response to a triggering operation of the first object on the object adding control, generating a verification request and sending the verification request to the second object; based on a verification result generated by the second object for the verification request, determining a second association relationship between the first object and the second object, the second association relationship indicating that the first object has a permission associated with the second object.

2. The method of claim 1, wherein, The displaying of the object adding control for the second object comprises at least one of the following: in response to a triggering operation of the first object on an object identifier of the second object, displaying an information interface of the second object, and displaying the object adding control on the information interface; displaying an information push interface associated with the second object, and displaying the object adding control on the information push interface corresponding to the second object.

3. The method of claim 2, wherein, The displaying of the information push interface associated with the second object comprises: displaying the information push interface associated with the second object on a media content stream display interface; displaying the information push interface associated with the second object on a preset interface associated with the first object.

4. The method of claim 1 or 2, wherein, The generating of the verification request and the sending of the verification request to the second object in response to the triggering operation of the first object on the object adding control comprises: in response to the triggering operation of the first object on the object adding control, displaying a verification interface, the verification interface comprising a verification request sending control; in response to a triggering operation on the verification request sending control, generating a verification request and sending the verification request to the second object.

5. The method of claim 4, wherein, The verification interface comprises a verification information input area, and the generating of the verification request and the sending of the verification request to the second object in response to the triggering operation on the verification request sending control comprises: in response to an information input operation on the verification information input area, obtaining verification information; in response to a triggering operation on the verification request sending control, generating a verification request according to the verification information and sending the verification request to the second object. 6.The method of claim 5, further comprising: saving the verification information, and when the first object triggers the object adding control again, displaying the saved verification information on the verification information input area.

7. The method of claim 5 or 6, wherein, The verification interface further comprises a remark information input area, and the method further comprises: in response to an information input operation on the remark information input area, obtaining remark information for the second object; in response to the establishment of the second association relationship between the first object and the second object, displaying the second object based on the remark information. 8.The method of any one of claims 1-7, further comprising: determining whether an interactive association between the first object and the second object satisfies a preset condition, and obtaining a determination result. determine, based on the determination result, to display, in an information interface of the second object, an object adding control or a target control for the second object, the target control including a first association control indicating establishment of an association relationship with the second object or a second association control indicating that the first object and the second object have established an association relationship.

9. The method of claim 8, wherein, The determining, based on the determination result, to display, in an information interface of the second object, an object adding control or a target control for the second object includes: in response to determining that the interactive association between the first object and the second object meets a preset condition, displaying, in an information interface of the second object, an object adding control for the second object; in response to determining that the interactive association between the first object and the second object meets a preset condition, displaying, in an information interface of the second object, the target control.

10. The method of claim 9, wherein, The displaying, in an information interface of the second object, the target control includes: determining whether a first association relationship exists between the first object and the second object; in response to a first association relationship existing between the first object and the second object, displaying the second association control in the information interface of the second object; in response to a first association relationship not existing between the first object and the second object, displaying the first association control in the information interface of the second object.

11. The method of claim 10, wherein, The displaying, in an information interface of the second object, the second association control includes: displaying, in an information interface of the second object, the second association control and a first setting control; in response to a triggering operation of the first object on the first setting control, displaying a first setting interface, the first setting interface including a preset adding control; in response to a triggering operation of the first object on the preset adding control, generating the verification request and sending it to the second object.

12. The method of any one of claims 1-11, wherein, The determining, based on a verification result generated by the second object for the verification request, of a second association relationship between the first object and the second object includes: based on the verification result indicating that the second object passed the verification request, determining that a target second association relationship is generated between the first object and the second object, the target second association relationship indicating that the first object has permission to access content published by the second object; based on the verification result indicating that the second object failed the verification request, determining that the first object and the second object maintain an original first association relationship, the original first association relationship indicating that the first object does not have permission to access content published by the second object.

13. A second association relationship determination method, comprising: receiving a verification request initiated by a first object, and displaying the verification request in an association object application interface, the first object and the second object having a first association relationship; in response to a feedback operation of the second object on the verification request, generating a verification result corresponding to the verification request; construct a second association relationship between the first object and the second object based on the verification result, and send the verification result to the first object, so that the first object determines a second association relationship between the first object and the second object based on the verification result.

14. The method of claim 13, further comprising: if the verification request carries verification information, displaying a reply control in an area where the verification request is located; in response to a triggering operation on the reply control, displaying an information reply area; in response to an information editing operation in the information reply area, generating reply information corresponding to the verification information.

15. An association relationship determination apparatus, comprising: an obtaining module configured to obtain an association state between a first object and a second object; a control display module configured to, if the association state indicates that the first object and the second object have a first association relationship, display an object adding control for the second object; a verification request sending module configured to, in response to a triggering operation of the first object on the object adding control, generate a verification request and send it to the second object; a second association relationship determination module configured to determine a second association relationship between the first object and the second object based on a verification result generated by the second object for the verification request, the second association relationship indicating that the first object has a permission associated with the second object.

16. An association relationship determination apparatus, comprising: a verification request receiving module configured to receive a verification request initiated by a first object, and display the verification request in an association object application interface, the first object and the second object having a first association relationship; a verification result generating module configured to, in response to a feedback operation of the second object on the verification request, generate a verification result corresponding to the verification request; a second association relationship constructing module configured to construct a second association relationship between the first object and the second object based on the verification result, and send the verification result to the first object, so that the first object determines a second association relationship between the first object and the second object based on the verification result.

17. An electronic device, comprising: a memory and a processor, which are communicatively connected with each other, wherein the memory stores computer instructions, and the processor executes the computer instructions to perform the association relationship determination method in any one of claims 1 to 12, or perform the association relationship determination method in any one of claims 13 to 14.

18. A computer readable storage medium storing computer instructions, wherein, The computer instructions are used to make a computer execute the association relationship determination method in any one of claims 1 to 12, or execute the association relationship determination method in any one of claims 13 to 14.

19. A computer program product comprising computer instructions, wherein, The computer instructions are used to make a computer execute the association relationship determination method in any one of claims 1 to 12, or execute the association relationship determination method in any one of claims 13 to 14.

Images