Association relation determination method and device, equipment, storage medium and program product

Abstract

The invention relates to the technical field of Internet, and discloses an association relationship determination method and device, equipment, a storage medium and a program product. The method comprises the following steps: acquiring an association state between a first object and a second object; if the association state indicates that a first association relationship exists between the first object and the second object, displaying an object adding control for the second object; in response to a trigger operation of the first object for the object adding control, generating a verification request and sending the verification request to the second object; and 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. By implementing the technical scheme disclosed by the invention, the use experience of the user on the application program is improved.

Description

Technical Field

[0001] The present disclosure relates to the field of Internet technology, and in particular to a method, device, equipment, storage medium and program product for determining an association relationship. Background Art

[0002] With the development of Internet technology, mobile terminal applications are becoming more and more popular. For example, applications can support users to publish content, and friends in the application can access the content. However, the experience of users interacting through applications needs to be improved. Summary of the invention

[0003] In view of this, the present disclosure provides a method, apparatus, device, storage medium and program product for determining an association relationship.

[0004] In a first aspect, the present disclosure provides a method for determining an association relationship, comprising: obtaining an association status between a first object and a second object; if the association status indicates that a first association relationship exists between the first object and the second object, 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 in response to 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 permissions associated with the second object.

[0005] In a second aspect, the present disclosure provides a method for determining an association relationship, including: receiving a verification request initiated by a first object, and displaying the verification request on an object application interface, wherein a first association relationship exists between the first object and the second object; generating a verification result corresponding to the verification request in response to a feedback operation of the second object on the verification request; constructing a second association relationship between the first object and the second object based on the verification result, 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.

[0006] In a third aspect, the present disclosure provides a device for determining a second association relationship, comprising: an acquisition module for acquiring an association status between a first object and a second object; a control display module for displaying an object addition control for the second object if the association status indicates that a first association relationship exists between the first object and the second object; a verification request sending module for generating a verification request and sending the request to the second object in response to a triggering operation of the first object for adding an object control; and a second association relationship determination module for 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 permissions associated with the second object.

[0007] In a fourth aspect, the present disclosure provides a device for determining a second association relationship, including: a verification request receiving module, used to receive a verification request initiated by a first object, and display the verification request on an object application interface, where a first association relationship exists between the first object and the second object; a verification result generating module, used to generate a verification result corresponding to the verification request in response to a feedback operation of the second object on the verification request; a second association relationship building module, used to build 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.

[0008] 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 to each other, computer instructions being stored in the memory, and the processor executing the computer instructions to thereby execute the method for determining the association relationship of the above-mentioned first aspect or any corresponding embodiment thereof, or execute the method for determining the association relationship of the above-mentioned second aspect or any corresponding embodiment thereof.

[0009] In a sixth aspect, the present disclosure provides a computer-readable storage medium having computer instructions stored thereon, the computer instructions being used to enable a computer to execute the method for determining the association relationship of the above-mentioned first aspect or any corresponding embodiment thereof, or to execute the method for determining the association relationship of the above-mentioned second aspect or any corresponding embodiment thereof.

[0010] In a seventh aspect, the present disclosure provides a computer program product, comprising computer instructions, the computer instructions being used to enable a computer to execute the method for determining the association relationship of the above-mentioned first aspect or any corresponding embodiment thereof, or to execute the method for determining the association relationship of the above-mentioned second aspect or any corresponding embodiment thereof.

[0011] The method, device, equipment, storage medium and program product for determining association relationships provided by the embodiments of the present disclosure obtain the association status between the first object and the second object to determine whether the first object can trigger the addition of the second object according to the association status. If the first object can trigger the addition of the second object, a verification request is further generated so that the second object determines whether to add the first object as a target association object according to the verification request, thereby improving the user experience of the application. BRIEF DESCRIPTION OF THE DRAWINGS

[0012] In order to more clearly illustrate the specific embodiments of the present disclosure or the technical solutions in the prior art, the drawings required for use in the specific embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of the present disclosure. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.

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

[0014] Figure 2 is a schematic diagram of adding a control to a home page display object according to an embodiment of the present disclosure;

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

[0016] Figure 4 is a schematic diagram of pushing a second object in an information stream according to an embodiment of the present disclosure;

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

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

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

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

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

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

[0023] Fig.11 is a schematic diagram of displaying an object adding control on an information interface according to an embodiment of the present disclosure;

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

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

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

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

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

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

[0030] Fig.18 is a schematic diagram of displaying excess prompt information according to an embodiment of the present disclosure;

[0031] Fig.19 is a schematic diagram of message types according to an embodiment of the present disclosure;

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

[0033] Fig.21 is a schematic diagram of setting notes according to an embodiment of the present disclosure;

[0034] Fig. 22 is a schematic diagram of customizing the remark information according to an embodiment of the present disclosure;

[0035] Fig.23 is a structural block diagram of a device for determining an association relationship according to an embodiment of the present disclosure;

[0036] Fig.24 is a structural block diagram of another device for determining an association relationship according to an embodiment of the present disclosure;

[0037] Fig.25 It is a schematic diagram of the hardware structure of the electronic device according to the embodiment of the present disclosure. DETAILED DESCRIPTION

[0038] In order to make the purpose, technical solution and advantages of the embodiments of the present disclosure clearer, the technical solution in the embodiments of the present disclosure will be clearly and completely described below in conjunction with 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 work are within the scope of protection of the present disclosure.

[0039] It is understandable that before using the technical solutions disclosed in the embodiments of the present disclosure, the types, scope of use, usage scenarios, etc. of the personal information involved in the present disclosure should be informed to the user and the user's authorization should be obtained in an appropriate manner in accordance with relevant laws and regulations.

[0040] For example, in response to receiving an active request from a user, a prompt message is sent to the user to clearly prompt the user that the operation requested to be performed will require obtaining and using the user's personal information. Thus, the user can autonomously choose whether to provide personal information to software or hardware such as an electronic device, application, server, or storage medium that performs the operation of the technical solution of the present disclosure according to the prompt message.

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

[0042] It is understandable that the above notification and the process of obtaining user authorization are merely illustrative and do not constitute a limitation on the implementation of the present disclosure. Other methods that meet the relevant laws and regulations may also be applied to the implementation of the present disclosure.

[0043] It is understandable that the data involved in this technical solution (including but not limited to the data itself, the acquisition or use of the data) shall comply with the requirements of relevant laws, regulations and relevant provisions.

[0044] When determining the association relationship with the permission to access the other party's published content, the disclosed technical solution requires both parties to verify each other before establishing the association relationship with the permission to access the other party's published content, based on the mutual attention or interaction, etc. This further improves the user experience of the application.

[0045] According to an embodiment of the present disclosure, an embodiment of 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 set of computer executable instructions, and although a 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.

[0046] In this 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. In this embodiment, the electronic device used by the first object is used as the execution subject. Figure 1 is a flow chart of a method for determining an association relationship according to an embodiment of the present disclosure, such as Figure 1 As shown, the process includes the following steps:

[0047] Step S101: Acquire the association status between the first object and the second object.

[0048] The association state is used to characterize whether there is a first association relationship between the first object and the second object, such as mutual attention, mutual fans, etc. Exemplarily, mutual attention, mutual fans, and unilateral attention indicate that there is a first association relationship between the first object and the second object; the absence of the above relationship indicates that there is no first association relationship between the first object and the second object.

[0049] An application is installed in the electronic device, and the first object registers a corresponding account on the application to interact with the second object. The association status between the first object and the second object can be obtained by reading the account information of the first object.

[0050] Specifically, if the first object only temporarily interacts with the second object, the first object may 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 interact with the second object multiple times, 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 interactively associate the account of the first object with the account of the second object, and record the association information in the account information. Therefore, by reading the association information corresponding to the account information, the association status between the first object and the second object can be determined.

[0051] Step S102: if the association status indicates that a first association relationship exists between the first object and the second object, an object adding control for the second object is displayed.

[0052] The object adding control is a control used to trigger the first object to add the second object as a target associated object. The associated state is used to indicate that the identifier of the existence of the first associated relationship is different from the identifier of the non-existence of the first associated relationship. For example, the identifier of the existence of the first associated relationship is 1, and the identifier of the non-existence of the first associated relationship is 0. By determining the identifier corresponding to the associated state, it can be determined whether there is a first associated relationship between the first object and the second object.

[0053] If the association status 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. When the first object enters the homepage of the second object, an object adding control will be displayed on the homepage of the second object, such as Figure 2 shown.

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

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

[0056] Step S104: 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, wherein the second association relationship indicates that the first object has the authority associated with the second object.

[0057] After the second object has viewed the verification request sent by the first object, it can view the homepage of the first object to understand the information of the first object, thereby determining 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 for each other, and each has the authority associated with the other party. Specifically, the associated authority includes the authority to access the content published by the other party. It should be noted that the published content here refers to publicly published content, and there is no access authority for privately published content.

[0058] When the second object initiates a verification request through the first object, the verification result generated by the second object for the verification request will be sent to the first object through the application, so that the first object can know that the second object has passed the verification request and has a second association relationship with the second object.

[0059] The method for determining an association relationship provided in this embodiment is that when a first association relationship exists between a first object and a second object, if the first object wants to establish a second association relationship between itself and the second object, a verification request is initiated to the second object, and based on a verification result generated by the second object in response to the verification request, it is determined whether the first object can have the authority to be associated with the second object, thereby achieving the goal of determining whether to add the first object as a target association object only through verification, thereby improving the user experience of the application.

[0060] In this 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. In this embodiment, the electronic device used by the first object is used as the execution subject. Figure 3 is a flow chart of a method for determining an association relationship according to an embodiment of the present disclosure, such as Figure 3 As shown, the process includes the following steps:

[0061] Step S201, obtaining the association state between the first object and the second object. For detailed description, please refer to the relevant description of the corresponding steps in the above embodiment, which will not be repeated here.

[0062] Step S202: if the association status indicates that a first association relationship exists between the first object and the second object, an object adding control for the second object is displayed.

[0063] Specifically, the above step S202 may include:

[0064] Step S2021: In response to a triggering 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.

[0065] The information interface is used to display the attribute information of the second object, including the nickname, avatar, published works, and related object data (such as the number of likes, the number of followers, and the number of fans) of the second object.

[0066] In a specific implementation, the first object can click on the location of the second object in the non-reply area to enter the homepage of the second object, so as to display an information interface on the homepage, and the information interface displays the nickname, avatar, number of likes, number of followers, number of fans, the first association relationship between the first object and the second object, signature information, and published works of the second object. At the same time, an object adding control is displayed on the information interface, and the object adding control can be set above the published work. At the same time, a private message control can also be set to support the first object to send a private message to the second object, such as Figure 2 shown.

[0067] 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 to the second object is improved.

[0068] Specifically, the above step S202 may include:

[0069] Step S2022: display the information push interface associated with the second object, and display an object adding control on the information push interface corresponding to the second object.

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

[0071] By displaying an object adding control on the information push interface corresponding to the second object, the scenarios of the first object adding the second object are enriched, which is conducive to improving the first object's willingness to add.

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

[0073] Pre-design the appearance and layout of the push card, including the location and style of elements such as the title, picture, description, and button. Obtain the attribute information of the second object associated with the first object from the database of the application, and fill the acquired attribute information into the corresponding position of the card to ensure the accuracy and completeness of the information. At the same time, interactive elements such as object adding buttons can be added to the card so that the first object can perform object adding operations. After the card is assembled, push the card to the first object in the application so that the attribute information of the second object can be presented to the first object in a concise and intuitive manner through the card.

[0074] In some optional implementations, the information push interface associated with the second object displayed in step S2022 includes:

[0075] Step a1: displaying an information push interface associated with the second object on the media content stream display interface.

[0076] Step a2: displaying an information push interface associated with the second object on a preset interface associated with the first object.

[0077] The media content stream is multimedia data, such as audio, video, image, text, etc., which is continuously transmitted by the application through the 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 pre-set browsing interface for displaying the information push interface to the first object. 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.

[0078] In some specific implementations, according to the interactive relationship of the first object, an information push interface is displayed in the information flow to recommend a second object associated with the first object. The second object may be one or more. Figure 4 shown.

[0079] In some specific implementations, when a user browses a media content stream, an information push interface may be displayed in the displayed media content stream to recommend a second object related to the first object, that is, the information push interface associated with the second object is embedded in the display of the media content stream, such as Figure 5It is also possible to display an information push interface when the media content stream browsing ends, so as to push the second object to the first object, that is, to display the push of the information push interface associated with the second object at the bottom of the media content stream, such as Figure 5 As shown. It is understandable that Figure 5 The waterfall flow interface can display a media content stream, which can include multiple media contents arranged in sequence. Users can browse the media contents in the media content stream by sliding. The waterfall flow interface can simultaneously display media contents posted by multiple users. Comments and other interactive information can be displayed under the screen content of each media content. Different media contents can occupy different lengths in the waterfall flow interface based on the screen ratio and the number of interactive information such as comments.

[0080] In some specific implementations, the preset interface may be a user content display interface, which is used to display social sharing content posted by other objects. The first object may 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 on the user content display interface is empty, an information push interface may be displayed in the user content display interface to push the second object, so that the first object can add the second object, such as Figure 6 shown.

[0081] In some specific implementations, the preset interface may be a second association application interface, which is used to display the verification request sent by other objects to the first object. The first object can switch from other interfaces to the second association application interface to view the verification request it has received. Figure 7 As shown, after the first object enters the second association relationship application interface, an information recommendation interface can be displayed below the verification request display area to push the second object.

[0082] In some specific implementations, the preset interface may be a second association relationship recommendation interface, which is used to display multiple second objects that have 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 it, and select the second object of interest to add the object. Figure 8 As shown, after the first object enters the second association relationship recommendation interface, the second object is pushed and displayed on the second association relationship recommendation interface.

[0083] This embodiment supports pushing the second object in multiple application scenarios, enriches the push methods of the second object, and makes the push methods more diversified, thereby enabling the first object to understand the second object associated with it in multiple scenarios.

[0084] Step S203: In response to the triggering operation of the first object on adding a control to the object, a verification request is generated and sent to the second object.

[0085] Specifically, the above step S203 includes:

[0086] Step S2031: In response to a triggering operation of the first object on an object adding control, a verification interface is displayed, where the verification interface includes a verification request sending control.

[0087] The verification interface is an interface for displaying verification information. A verification request sending control is provided on the verification interface. The verification request sending control may be in the form of a button. Fig. 9 As shown, when the first object triggers the object adding control, a verification interface is pulled up from the current interface, and a verification request sending button is displayed on the verification interface.

[0088] Step S2032: In response to the triggering operation of the verification request sending control, a verification request is generated and sent to the second object.

[0089] When the first object triggers the verification request sending control, the application will respond to the triggering operation of the first object, generate a verification request based on the verification information displayed on the verification interface, and send it to the second object, so that the second object can check the verification request and confirm whether to establish a second association relationship with the first object.

[0090] The method for determining the association relationship provided in this embodiment can pop up a verification interface when the object is triggered to add a component, so that a verification request can be sent to the second object on the verification interface, thereby realizing the construction of the second association relationship through verification, thereby improving the construction experience of the second association relationship.

[0091] In some optional implementations, the verification interface includes a verification information input area, and the verification information input area is used to input verification information. Accordingly, the above step S2032 includes:

[0092] Step b1, obtaining verification information in response to the information input operation in the verification information input area.

[0093] Step b2: in response to the triggering operation of the verification request sending control, generate a verification request according to the verification information and send it to the second object.

[0094] like Fig. 9As shown, the verification interface includes a verification information input area, which supports the first object to input verification information. Specifically, the first object can click the verification information input area to pull an input component (such as a keyboard component), and input verification information into the verification information input area through the input component. After completing the input of the verification information, the first object can trigger the verification request sending control to send the verification information.

[0095] The method for determining the association relationship provided in this embodiment supports editing verification information in the verification interface so that the verification information is sent together with the verification request, which makes it easier for the second object to confirm the identity information of the first object based on the verification information, and is conducive to improving the pass rate of the verification request.

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

[0097] After the first object sends a 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 last saved verification information will be displayed in the pop-up verification interface.

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

[0099] The method for determining the association relationship provided in this embodiment supports the storage of verification information so that it can be directly used when sending a verification request next time, avoiding repeated input of the same verification information, and improving the verification request sending experience of the first object.

[0100] In some optional implementations, the above method further includes: if the verification request is sent successfully, displaying a first prompt message indicating that the verification request is sent successfully.

[0101] After triggering the sending of the verification request, the electronic device can monitor the sending status of the verification request to determine whether the verification request is sent successfully. When it is determined that the verification request is sent successfully, a first prompt message will be displayed in the interface for adding the second object, indicating that the verification request is sent successfully. For example, the first prompt message can be "The request for adding an object has been sent", such as Fig.10 shown.

[0102] The method for determining the association relationship provided in this embodiment supports displaying prompt information when the verification request is sent successfully, so that the first object can determine the sending status of the verification request.

[0103] In some optional implementations, the method further includes: if the number of times the verification request is sent reaches a preset value, displaying a second prompt message waiting for verification.

[0104] The preset value is the maximum number of times the first object is allowed to send a verification request to the same second object. If the first object does not receive the verification result fed back by the second object, the first object can repeatedly send a verification request to the second object and accumulate the number of times the first object sends a verification request. When the number of times the verification request is sent reaches the preset value, the verification request is refused to be sent again, and a second prompt message is displayed on the interface for adding the second object. The second prompt message indicates that the number of times the verification request is sent exceeds the limit. For example, the second prompt message can be "You have added the other party multiple times, please wait patiently for the application", such as Fig.10 shown.

[0105] In a specific example, the first object A can add the second object B multiple times. The cumulative upper limit of adding a single-to-one relationship is 5 times (i.e. sending verification requests 5 times) every six natural months (6 natural months from the date when the second object was first added). Exceeding this number is considered as sending too many times. When the object adding control is triggered again, it will be displayed "You have added the other party multiple times, please wait patiently for the application."

[0106] The method for determining the association relationship provided in this embodiment supports displaying a prompt message when the verification request is sent too many times, so as to remind the first object that the verification request is sent too many times and avoid the user from sending it repeatedly.

[0107] In some optional implementations, the above method further includes: if the verification request fails to be sent, displaying a third prompt message for modifying the verification request.

[0108] In a specific example, if the verification information is not available, the verification request cannot be successfully sent. For example, if the number of characters in the verification information exceeds the limit, the verification request cannot be sent. At this time, a third prompt message can be displayed on the interface for adding the second object to notify the first object to modify the verification information in the verification request through the third message. For example, the third message can be "Verification information is not available, please modify and try again", such as Fig.10 shown.

[0109] In a specific example, if the verification request fails to be sent due to a network problem, a third prompt message will also be displayed on the interface for adding the second object to notify the first object of the failure of the verification request to be sent through the third message. For example, the third message can be "Your network is out of service, please try again", such as Fig.10 shown.

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

[0111] In some optional implementations, the verification interface further includes a remark information input area, and the remark information input area is used to input a remark for the second object. Accordingly, the above method further includes:

[0112] Step c1, in response to an information input operation in the remark information input area, obtaining remark information for the second object.

[0113] Step b2: in response to the establishment of the second association relationship between the first object and the second object, display the second object based on the remark information.

[0114] like Fig. 9 As shown, the verification interface includes a remark information input area, which supports the first object to input its remark information for the second object. Specifically, the first object can click on the remark information input area to pull out an input component (such as a keyboard component), and input remark information into the remark information input area through the input component. After completing the input of the verification information and / or remark information, the first object can trigger the verification request sending control to send the verification information.

[0115] When the second object receives the verification request sent by the first object, the second association relationship between the first object and the second object can be established. At this time, in the target association object list of the first object, the second object will be displayed according to the remark information, so that the first object can quickly retrieve the second object with which it has a target association relationship according to the remark information.

[0116] The method for determining the association relationship provided in this embodiment supports editing the remark information when sending a verification request, so as to display the second object according to the remark information after completing the construction of the second association relationship, so that the first object can quickly retrieve the second object according to the remark information.

[0117] In some optional implementations, the above method further includes: if the remark information is not available, displaying fourth prompt information for modifying the remark information.

[0118] There is a character limit for entering the remark information. If the number of characters in the remark information exceeds the limit, the remark information will be unavailable. If the remark information is unavailable, the verification request will not be sent successfully. At this time, a fourth prompt message can be displayed on the interface for adding the second object to notify the first object to modify the remark information in the verification request through the fourth message. For example, the fourth message can be "Remark information is unavailable, please modify and try again", such as Fig.10 shown.

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

[0120] In some optional implementations, the above method further includes:

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

[0122] Step d2, based on the determination result, determines to display an object addition control or a target control for the second object on the 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 an association relationship has been established between the first object and the second object.

[0123] The preset condition is a pre-set condition for determining that the first object and the second object have an interactive relationship, 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 unilaterally follows the second object; the second object unilaterally follows the first object; there is interactive information between the first object and the second object, etc. The preset condition is not specifically limited here, and those skilled in the art can determine it according to actual needs.

[0124] The first association control is used to indicate the establishment of an association relationship between the first object and the second object, and the second association control is used to indicate the existence of an association relationship between the first object and the second object. By detecting the association state between the first object and the second object, it can be determined whether the interactive association between the first object and the second object meets the preset conditions. If it is determined that the interactive association between the first object and the second object meets the preset conditions, an object addition control or a target control for the second object is displayed on the information interface of the second object. Among them, the target control includes a first association control indicating the 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.

[0125] In some optional implementations, the above step d2 includes:

[0126] Step d21, in response to determining that the interactive association between the first object and the second object satisfies a preset condition, displaying an object adding control for the second object on the information interface of the second object.

[0127] Step d22, in response to determining that the interactive association between the first object and the second object meets a preset condition, displaying a target control on the information interface of the second object.

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

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

[0130] In some optional implementations, displaying the target control on the information interface of the second object in the above step d22 may include:

[0131] Step e1, determining whether a first association relationship exists between the first object and the second object.

[0132] Step e2: if there is a first association relationship between the first object and the second object, display a second association control on the information interface of the second object.

[0133] Step e3: if there is no first association relationship between the first object and the second object, display a first association control on the information interface of the second object.

[0134] The first association relationship is used to characterize whether there is a mutual association between the first object and the second object, such as following each other, being fans of each other, etc. If there is a first association relationship between the first object and the second object, it means that there is a mutual association between the first object and the second object, and the second association control (such as "Followed") is displayed on the information interface of the second object. If there is no first association relationship between the first object and the second object, it means that the first object and the second object are not related to each other, and the first association control (such as "Follow") is displayed on the information interface of the second object.

[0135] Specifically, if the first object and the second object do not have a first association relationship, it is possible to detect whether there is an interactive association between the first object and the second object. Specifically, the interactive association may include work interaction, unilateral association, and address book friends when the user fully authorizes the address book, etc. The content of the interactive association is not specifically limited here.

[0136] If there is an interactive association between the first object and the second object, a first association control for the second object is displayed on the information interface of the second object.

[0137] If it is determined that there is no first association relationship between the first object and the second object by determining the identifier corresponding to the association state, the interactive relationship data of the first object can be further obtained. It is determined whether there is an interactive association between the first object and the second object by parsing the interactive relationship data of the first object. If there is an interactive association between the first object and the second object, 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, an object adding control is displayed on the information interface of the second object.

[0138] If there is an interactive association between the first object and the second object, and the second object is the second interactive association object followed by 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. At this time, after the first object triggers the setting control of the information interface, the object adding control can be displayed in the setting interface corresponding to the setting control, such as Fig.12 shown.

[0139] If there is an interactive relationship between the first object and the second object, and the second object is the third interactively associated object that follows the first object, when the first object enters the information interface of the second object, a first associated control (for example, "Follow") is displayed on the information interface of the second object; after the first object triggers the associated control, an object adding control can be displayed on the information interface of the second object.

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

[0141] In some optional embodiments, such as Fig.11 As shown, the above method also includes:

[0142] Step f1: displaying a second associated control and a first setting control on the information interface of the second object.

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

[0144] Step f3: in response to the triggering operation of the first object for adding a preset control, generate a verification request and send it to the second object.

[0145] The first object clicks the first setting control, and accordingly, the application can respond to the first object's click operation 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.

[0146] Then, the first object can click on the preset add control, and accordingly, the application can respond to the first object's click operation on the preset add control, pop up a verification interface from the first device interface, and send a verification request to the second object through the verification interface.

[0147] By integrating the adding control in the first setting control, multiple ways of adding the second object to the first object are provided, so that the first object can select the required adding way according to actual needs.

[0148] In some optional implementations, the above method further includes:

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

[0150] Step e2: In response to a triggering operation of the first object on the first associated control, a first associated relationship between the first object and the second object is established.

[0151] Step e3: If the first association relationship is successfully established, a second association control and a second setting control are displayed.

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

[0153] Step e5: In response to the triggering operation of the first object for the preset adding control, a verification request is generated and sent to the second object.

[0154] Step e6: if the first association relationship fails to be established, a fifth prompt message indicating that the association has failed is generated, and the verification request for adding the object is rejected.

[0155] If there is no interactive association between the first object and the second object, it means that the second object is a stranger to the first object. At this time, when the first object enters the information interface of the second object, a first association control (such as "Follow") is displayed on the information interface of the second object. Fig.13 As shown, by clicking the first association control, a first association relationship is established between the first object and the second object, that is, the first object unilaterally associates with the second object. Fig.13 ) to set relevant attribute information in the pop-up interface, such as canceling the association, setting remarks information, etc.

[0156] When it is determined that the first association relationship between the first object and the second object is successfully established, a second association control and a second setting control are displayed on the second object corresponding information interface, such as Fig.12 shown.

[0157] The first object clicks the second setting control, and accordingly, the application can respond to the click operation of the first object on the second setting control, pop up the second setting interface from the information interface, and display the preset adding control in the second setting interface.

[0158] Then, the first object can click on the preset add control, and accordingly, the application can respond to the first object's click operation on the preset add control, pop up a verification interface from the second device interface, and send a verification request to the second object through the verification interface.

[0159] When it is determined that the first association relationship between the first object and the second object fails to be established, the verification request for adding the object is rejected to the second object, and the display of the fifth prompt information is triggered at the same time, and the fifth prompt information indicates that the association between the first object and the second object fails. At this time, the first object can trigger the second association control again to request the first association relationship with the second object.

[0160] The method for determining an association relationship provided in this embodiment supports first building a first association relationship and then triggering the addition of the second object when there is no interactive association between the first object and the second object, thereby ensuring that the construction of the second association relationship is safer and improving the user experience of building the second association relationship.

[0161] In some optional implementations, the above method further includes:

[0162] Step g1: Determine whether the second object is a private object based on the account attribute information of the second object.

[0163] 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.

[0164] The account attribute information is used to characterize the attributes of the object, and a private account flag is set in the account attribute information. By parsing 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 association object.

[0165] If the first object wants to establish a second association relationship with the second object, the first object needs to apply to the second object to establish the first association relationship. When the second object accepts the association request, the first association relationship between the first object and the second object is established. At this time, if the first object is only unilaterally associated with the second object, the object adding control will still be disabled, such as Fig.14 Only when there is a mutual association relationship between the first object and the second object, the first object can trigger the object adding control to send a verification request for object adding to the second object.

[0166] When other objects add objects to private objects, their object adding controls are disabled, thus ensuring the privacy of private objects.

[0167] 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, wherein the second association relationship indicates that the first object has the authority associated with the second object.

[0168] Specifically, the above step S204 includes:

[0169] Step S2041: if the verification result indicates that the second object passes the verification request, it is determined to generate a target second association relationship between the first object and the second object, where the target second association relationship is used to indicate that the first object has the authority to access the content published by the second object.

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

[0171] Accordingly, when the second object passes the verification request, the application may feed back the verification result generated by the second object for the verification request to the first object. At this time, the first object may determine that a target second association relationship has been generated between it and the second object.

[0172] Step S2042: If the verification result indicates that the second object fails the verification request, it is determined that the original first association relationship between the first object and the second object is maintained, where the original first association relationship is used to indicate that the first object does not have the authority to access the content published by the second object.

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

[0174] Accordingly, when the second object fails the verification request, the application can feedback the verification result generated by the second object for the verification request to the first object, and at this time, the first object can determine that the target second association relationship is not generated between it 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.

[0175] The method for determining the association relationship provided in this embodiment is that the first object determines whether the verification request is passed in combination with the verification result, thereby being able to clarify the second association relationship between the first object and the second object based on whether the verification request is passed, thereby clarifying the authority of the first object with respect to the content published by the second object, and preventing the content published by the second object from being accessed arbitrarily.

[0176] In this 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. In this embodiment, the electronic device used by the second object is used as the execution subject. Fig.15 is a flow chart of a method for determining a second association relationship according to an embodiment of the present disclosure, such as Fig.15 As shown, the process includes the following steps:

[0177] Step S301, receiving a verification request initiated by a first object, and displaying the verification request on an associated object application interface, wherein a first association relationship exists between the first object and the second object.

[0178] As described above, when a first object and a second object have a first association relationship, when the first object triggers an object adding control to add the second object as a target association object, a corresponding verification request will be generated and sent to the second object. Specifically, an application is also installed in the electronic device used by the second object, and the verification request initiated by the first object is received through the application. The second object can check the verification request initiated by the first object on the association object application interface, such as Fig.16 shown.

[0179] Step S302: In response to a feedback operation of the second object on the verification request, a verification result corresponding to the verification request is generated.

[0180] The feedback operation is a verification operation performed by the second object on the verification request initiated by the first object. The feedback operation can be performed by clicking the verification tag corresponding to the verification request. Fig.16 As shown, the second object can click the "Go to Verification" label corresponding to the verification request to verify the first object to generate a verification result for the first object.

[0181] Step S303: 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.

[0182] After the second object completes the verification of the first object, a corresponding second association relationship is established between the first object and the second object according to the verification result. Specifically, if the second object passes the verification request initiated by the first object, the second association relationship between the first object and the second object is established; 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. At the same time, 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 it and the second object according to the verification result.

[0183] The method for determining the association relationship provided in this embodiment enables the second object to provide feedback on the verification request when receiving the verification request from the first object, thereby building 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 method for determining the second association relationship and improving the user experience of the application.

[0184] In some optional implementations, the method further includes: displaying the number of associated object applications on the user content display interface, wherein the number of associated object applications is the sum of the number of newly added verification requests and the number of newly added application messages.

[0185] The user content display interface is used to display dynamic information published by the target associated object, which is an object that has a second association relationship with the second object and has the authority to access the content published by the second object. The number of associated object applications is the number of new information applied to the second object.

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

[0187] In some optional implementations, the number of associated object applications is displayed in the form of bubbles at the top of the user content display interface. Fig.17 As shown, the number of associated object applications is displayed at the top of the user content display interface and is displayed in the form of bubbles to avoid affecting the dynamic information display in the user content display interface.

[0188] In some optional implementations, the above method further includes:

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

[0190] Step A2: Update the number of associated object applications based on the message type.

[0191] The message type indicates the message style of the message received by the second object and the message style of the message sent by the second object. Fig.19 As shown, the message types may include: (1) the second object receives a verification request from the first object, and the verification request carries verification information; (2) the second object receives a verification request from the first object, and the verification request does not carry verification information; (3) the second object receives a verification request from the first object, and the second object has clicked to approve; (4) the second object sends a verification request to other objects; (5) the second object sends a verification request to other objects, and the verification request carries verification information, and the other objects reply to the verification information; (6) the second object sends a verification request to other objects, and the other objects have clicked to approve; (7) the second object receives a verification request from the first object, and the verification request has expired; (8) the second object sends a verification request to other objects, and the verification request has expired.

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

[0193] The method for determining the association relationship provided in this embodiment supports multiple message types and enriches the message styles, so that the verification request can meet various user needs.

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

[0195] The second object can click on the associated object application number on the user content display interface, and accordingly, the application can respond to the second object's click operation on the associated object application number on the user content display interface and switch from the user content display interface to the associated object application interface. Fig.16 As shown, an application information display list is displayed on the associated object application interface, and at least one application information is displayed in the application information display list. When switching from the associated object application interface back to the user content display interface, the associated object application number will disappear from the user content display interface.

[0196] The method for determining the association relationship provided in this embodiment supports hiding the number of applications for associated objects, thereby ensuring the content display effect of the user content display interface.

[0197] In some optional implementations, the method further includes: if the verification request is a new verification request, displaying a new mark at the list position of the new verification request; wherein the new mark disappears the next time the associated object application interface is entered.

[0198] A new mark is displayed on the new verification request, and the new mark is used to indicate that the verification request is newly received by the second object. Fig.16 As shown, the newly added mark can be a small dot and is displayed in front of the newly added verification request. When the second object is cut out from the associated object application interface and enters the associated object application interface again, the newly added mark displayed last time will disappear.

[0199] The method for determining the association relationship provided in this embodiment supports adding a new flag before the new verification request, highlighting the user identifier displayed for the new verification request, so that the second object can filter the new verification request according to the new flag.

[0200] In some optional implementations, each verification request is displayed in the application information display list in chronological order. Specifically, each verification request can be sorted from recent to far in chronological order, for example, the verification request of the first object A is ranked at the xth position, and 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 timestamps of each application information and re-sort according to the updated timestamps.

[0201] The method for determining the association relationship provided in this embodiment displays the application information of each verification request in chronological order, so that the display of the verification requests can be orderly.

[0202] In some optional implementations, the application information display list includes at least one page, and the page is used to display verification requests received in different time intervals.

[0203] Different time intervals are used to represent different time ranges, such as the past three days, three days ago, half a year ago, etc. Fig.16 The application information display list can be divided according to different time intervals to obtain pages corresponding to each time zone, and each page displays the verification requests received in the corresponding time interval.

[0204] The method for determining the association relationship provided in this embodiment supports paging of verification requests according to different time zones, which facilitates the second object to view and manage verification requests within different time intervals, thereby improving the efficiency and readability of information display.

[0205] In some optional implementations, the above method further includes: when the number of newly received verification requests exceeds a preset number, displaying an excess prompt message on the associated object application interface.

[0206] The preset number is a preset number of verification requests used to characterize an excess. The newly added verification requests received by the second object are counted to obtain the number of newly added verification requests. The number of newly added verification requests is compared with the preset number to determine whether the number of newly added verification requests exceeds the preset number. If the number of newly added verification requests exceeds the preset number, an excess prompt message is displayed on the associated object application interface.

[0207] like Fig.18 As shown, the excess prompt information can be displayed in the form of a prompt bar. When the number of newly added verification requests exceeds the preset number, a prompt message "Too many unfamiliar messages received, please add me as a target associated object" is displayed in the prompt bar. If the second object clicks on the excess prompt information, the second object can enter the adding setting interface, and the second object can set the adding condition in the adding setting interface. The subsequent verification requests can be filtered through the adding condition, and the verification requests that do not meet the adding condition can be rejected.

[0208] The method for determining the association relationship provided in this embodiment is that when the number of new verification requests received exceeds the preset number, the second object will see an excess prompt message on the association object application interface, so that the second object can promptly understand the status of the currently received verification requests and take corresponding processing measures.

[0209] In some optional implementations, the above method further includes:

[0210] Step B1, in response to a closing operation on the excess prompt information, closing the excess prompt information.

[0211] Step B2: When the number of times the shutdown operation is triggered reaches a preset number, the excess prompt message is no longer displayed.

[0212] like Fig.18 As shown, the excess prompt information has a corresponding close tag, that is, the excess prompt information allows closing. When the second object clicks the close tag corresponding to the excess prompt information, the application can respond to the closing operation of the second object and close the excess prompt information.

[0213] The preset number of times is the preset number of times to display the closing excess prompt, for example, 3 times. When the second object clicks the close tag, the application can count the number of times the second object triggers the closing operation, and compare the number with the preset number to determine whether the number of times the closing operation is triggered reaches the preset number. If the number of times the closing operation is triggered reaches the preset number, the excess prompt information will no longer be displayed. When the number of new verification requests received again reaches the preset number, the excess prompt information will be triggered and displayed again.

[0214] The method for determining the association relationship provided in this embodiment supports closing the excess prompt information, and will no longer display it when the number of closing times reaches a preset number, thereby achieving flexible closing of the excess prompt information.

[0215] In some optional implementations, the above method further includes:

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

[0217] 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.

[0218] The delete operation is an operation by which the second object deletes the verification request initiated by the first object, and the delete operation can be triggered by long pressing the verification request. Fig.19 As shown, the second object can long press the verification request to trigger the display of a "Delete Notification" button, and click "Delete Notification" to remove the verification request from the application information display list.

[0219] 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 again in the application information display list.

[0220] 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, then when the first object replies again to the reply message of the second object, the verification information corresponding to the deleted verification request of the first object will be displayed again in the application information display list.

[0221] The method for determining the association relationship provided in this embodiment supports deletion of verification requests, so that the second object can delete verification requests that it is not interested in according to actual needs, thereby providing the second object with selectivity of verification requests.

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

[0223] When the second object releases the second association relationship between itself and the first object, the first object will no longer be able to send messages to the second object, and the verification request sent by the first object to the second object will also be removed from the application information display list.

[0224] In the method for determining the association relationship provided in this embodiment, if the second association relationship is cancelled, the corresponding application information will be deleted together, thereby ensuring that the verification requests displayed in the application information display list are meaningful and avoiding the display of meaningless verification requests.

[0225] In some optional implementations, the above method further includes:

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

[0227] Step D2, in response to the triggering operation on the reply control, display the information reply area.

[0228] Step D3, in response to the information editing operation in the information reply area, generating reply information corresponding to the verification information.

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

[0230] 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, an information reply area pops up, and the second object can enter the reply information in the information reply area. Specifically, the second object clicks the information reply area, and an information input component (such as a keyboard input component) pops 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 reply information fails to be sent, a prompt message of failure to send can be generated, such as "Failed to send, please try again". At this time, the second object can resend the reply information to the first object.

[0231] Specifically, the reply scenarios between the first object and the second object include: (1) when the first object adds the second object, the verification request carries verification information, and the second object can reply to the verification information; (2) when the first object adds the second object, the verification request carries verification information, and the second object replies to the verification information, and the first object can reply to the reply of the second object.

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

[0233] The method for determining the association relationship provided in this embodiment supports replying verification information, which facilitates the first object and the second object to communicate through reply information, thereby strengthening the interaction between the first object and the second object, and is conducive to improving the pass rate of verification requests through reply information.

[0234] In some optional implementations, the above method further includes: if the first object is in the blacklist, refusing to receive the reply information sent by the first object.

[0235] If the second object refuses to establish a second association relationship with the first object, and after replying to the verification information to inform the first object of the refusal to be added, the second object is added to the blacklist. Then, when the first object sends a reply message to the second object, the reply message cannot be sent.

[0236] If the second object does not read the reply message after receiving the reply message from the first object and puts the first object into the blacklist, the reply message will be deleted.

[0237] If the second object adds the first object to 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 received historical messages will be displayed as expired.

[0238] The method for determining the association relationship provided in this embodiment refuses to receive messages from the first object if the first object is in the blacklist, thereby preventing the second object from being interfered with by the first object and also protecting the rights and interests and information security of the second object.

[0239] In some optional implementations, the above method further includes:

[0240] Step E1: In response to a note triggering operation on a first object, a note editing area is displayed.

[0241] Step E2: generating note information corresponding to the first object in response to an input operation on the note editing area.

[0242] When the second object passes the verification request of the first object, the second association relationship is established between the first object and the second object, such as Fig. 20 At this time, the second object can make a note of the first object for subsequent search. Fig.21 and Fig. 22 As shown, when the second object triggers a note operation on the first object, a note editing area is displayed, and the second object can enter note information in the note editing area.

[0243] The method for determining the association relationship provided in this embodiment supports the editing of the remark information and realizes the customization of the candidate information.

[0244] In some optional implementations, the method further includes: if there is remark information for the first object, then when a remark operation for the first object is triggered, the remark information is displayed in the remark editing area.

[0245] If the first object exists in the address book of the second object, it indicates that there is remark information for the first object. When the remark operation for the first object is triggered, the name of the first object in the address book can be displayed in the remark editing area as the remark information of the first object.

[0246] 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 verification information, then when the remark operation for the first object is triggered, the remark information in the verification information can be displayed in the remark editing area.

[0247] If there is historical remark information for the first object, when a remark operation for the first object is triggered, the historical remark information is displayed in the remark editing area.

[0248] It should be noted that the remark information supports indexing verification information and address book names, and the index priority of the address book name is higher than the verification information.

[0249] In some optional implementations, if the note editing area is empty, clicking Done or clicking Close the note editing area is equivalent to skipping the note operation.

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

[0251] In some optional implementations, the above method further includes: if generating a verification result for the verification request fails, displaying a retry prompt message.

[0252] If the second object fails to pass the verification request due to network reasons, etc., a corresponding retry prompt message (such as "failed, please try again") can be generated and displayed to remind the second object to pass the verification request again.

[0253] The method for determining the association relationship provided in this embodiment supports the display of retry prompt information when the verification request fails to generate a verification result, so that the second object can understand the verification status of the verification request in a timely manner.

[0254] In the present embodiment, a device for determining an association relationship is also provided, and the device is used to implement the above-mentioned embodiments and preferred implementation modes, and the descriptions that have been made will not be repeated. As used below, the term "module" can implement a combination of software and / or hardware of a predetermined function. Although the device described in the following embodiments is preferably implemented in software, the implementation of hardware, or a combination of software and hardware is also possible and conceived.

[0255] This embodiment provides a device for determining an association relationship, such as Fig.23 As shown, including:

[0256] The acquisition module 401 is used to acquire the association state between the first object and the second object.

[0257] The control display module 402 is configured to display an object adding control for the second object if the association status indicates that the first object has a first association relationship with the second object.

[0258] The verification request sending module 403 is used to generate a verification request and send it to the second object in response to a triggering operation of the first object on adding a control to the object.

[0259] The second association relationship determination module 404 is used to determine a second association relationship between the first object and the second object based on the verification result generated by the second object for the verification request, wherein the second association relationship indicates that the first object has the authority associated with the second object.

[0260] In some optional implementations, the control display module 402 includes:

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

[0262] In some optional implementations, the control display module 402 includes:

[0263] The push unit is used to display the information push interface associated with the second object and display the object adding control on the information push interface corresponding to the second object.

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

[0265] The first information push interface display unit is used to display the information push interface associated with the second object on the media content stream display interface.

[0266] The second information push interface display unit is used to display the information push interface associated with the second object on the preset interface associated with the first object.

[0267] In some optional implementations, the verification request sending module 403 includes:

[0268] The first response unit is used to display a verification interface in response to a triggering operation of the first object on adding a control to the object, where the verification interface includes a verification request sending control.

[0269] The second response unit is used to generate a verification request and send it to the second object in response to a trigger operation of sending a verification request control.

[0270] In some optional implementations, the verification interface includes a verification information input area, and accordingly, the second response unit includes:

[0271] The verification information input subunit is used to obtain verification information in response to an information input operation in the verification information input area.

[0272] The first generating subunit is used to generate a verification request according to the verification information and send it to the second object in response to a triggering operation of sending a verification request control.

[0273] In some optional implementations, the verification request sending module 403 further includes:

[0274] The saving unit is used to save the verification information, and when the first object triggers the object adding control again, the saved verification information is displayed in the verification information input area.

[0275] In some optional implementations, the verification interface further includes a remark information input area, and the verification request sending module 403 further includes:

[0276] The remark information input unit is used to obtain remark information for the second object in response to an information input operation in the remark information input area.

[0277] The remark display unit is used to display the second object based on the remark information in response to the establishment of the second association relationship between the first object and the second object.

[0278] In some optional embodiments, the above device further includes:

[0279] The interactive association determination module is used to determine whether the interactive association between the first object and the second object meets a preset condition and obtain a determination result.

[0280] A control display module is used to determine, based on the determination result, to display an object addition control or a target control for the second object on the information interface of the second object, wherein the target control includes a first association control indicating establishment of an association relationship with the second object or a second association control indicating that an association relationship has been established between the first object and the second object.

[0281] In some optional implementations, the control display module includes:

[0282] The first control display unit is used to display an object adding control for the second object on the information interface of the second object in response to determining that the interactive association between the first object and the second object meets a preset condition.

[0283] The second control display unit is used to display a target control on the information interface of the second object in response to determining that the interactive association between the first object and the second object meets a preset condition.

[0284] In some optional implementations, the second widget display unit includes:

[0285] The association detection subunit is used to determine whether a first association relationship exists between the first object and the second object.

[0286] The first display subunit is configured to display a second associated control on the information interface of the second object if a first associated relationship exists between the first object and the second object.

[0287] The first display subunit is configured to display a first associated control on the information interface of the second object if there is no first associated relationship between the first object and the second object.

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

[0289] In some optional implementations, the second association relationship determination module 404 includes:

[0290] The first determination module is used to determine to generate a target second association relationship 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 authority to access the content published by the second object.

[0291] The second determination module is used to determine that the original first association relationship between the first object and the second object is maintained 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 authority to access the content published by the second object.

[0292] The further functional description of each of the above modules and units is the same as that of the above corresponding embodiments and will not be repeated here.

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

[0294] The device for determining association relationships provided in this embodiment, when a first association relationship exists between a first object and a second object, if the first object wants to establish a second association relationship between itself and the second object, it must initiate a verification request to the second object, and determine whether the first object can have the authority to be associated with the second object based on the verification result generated by the second object in response to the verification request. This achieves the goal of determining whether to add the first object as a target association object only through verification, thereby improving the user experience of the application.

[0295] This embodiment provides a device for determining an association relationship, such as Fig.24 As shown, including:

[0296] The verification request receiving module 501 is used to receive a verification request initiated by a first object and display the verification request on an associated object application interface. The first object has a first associated relationship with the second object.

[0297] The verification result generating module 502 is used to generate a verification result corresponding to the verification request in response to the feedback operation of the second object on the verification request.

[0298] The second association relationship building module 503 is used to build 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.

[0299] In some optional embodiments, the above device further includes:

[0300] The reply module is used to display a reply control in the area where the verification request is located if the verification request carries verification information.

[0301] The reply area display module is used to display the information reply area in response to the trigger operation on the reply control.

[0302] The reply information editing module is used to generate reply information corresponding to the verification information in response to the information editing operation in the information reply area.

[0303] The further functional description of each of the above modules and units is the same as that of the above corresponding embodiments and will not be repeated here.

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

[0305] The device for determining the association relationship provided in this embodiment enables the second object to provide feedback on the verification request when receiving the verification request from the first object, thereby building 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 method for determining the second association relationship and improving the user experience of the application.

[0306] The present disclosure also provides an electronic device having the above Fig.23 or Fig.24 A device for determining the association relationship shown.

[0307] See also Fig.25 , Fig.25 is a schematic diagram of the structure of an electronic device provided by an optional embodiment of the present disclosure, such as Fig.25 As shown, 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 are connected to each other using different buses for communication, and can be installed on a common mainboard or installed in other ways as needed. The processor can process instructions executed in the electronic device, including instructions stored in or on the memory to display graphical information of the GUI on an external input / output device (such as a display device coupled to the interface). In some optional embodiments, if necessary, multiple processors and / or multiple buses can be used together with multiple memories and multiple memories. Similarly, multiple electronic devices can be connected, and each device provides some necessary operations (for example, as a server array, a group of blade servers, or a multi-processor system). Fig.25 A processor 10 is taken as an example.

[0308] The processor 10 may be a central processing unit, a network processor or a combination thereof. The processor 10 may further include a hardware chip. The hardware chip may be a dedicated integrated circuit, a programmable logic device or a combination thereof. The programmable logic device may be a complex programmable logic device, a field programmable gate array, a general purpose array logic or any combination thereof.

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

[0310] The memory 20 may include a program storage area and a data storage area, wherein the program storage area may store an operating system, an application required for at least one function; the data storage area may store data created according to the use of the electronic device, etc. In addition, the memory 20 may include a high-speed random access memory, and may also include a non-transient memory, such as at least one disk storage device, a flash memory device, or other non-transient solid-state storage device. In some optional embodiments, the memory 20 may optionally include a memory remotely arranged relative to the processor 10, and these remote memories may be connected to the electronic device via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0311] The memory 20 may include a volatile memory, such as a random access memory; the memory may also include a non-volatile memory, such as a flash memory, a hard disk or a solid state drive; the memory 20 may also include a combination of the above types of memory.

[0312] The electronic device further 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 may be connected via a bus or other means. Fig.25 The example of connecting through bus is taken in the following.

[0313] The input device 30 can receive input digital or character information, and generate key signal input related to the user settings and function control of the electronic device, such as a touch screen, a keypad, a mouse, a track pad, a touch pad, an indicator rod, one or more mouse buttons, a trackball, a joystick, etc. The output device 40 may include a display device, an auxiliary lighting device (e.g., an LED) and a tactile feedback device (e.g., a vibration motor), etc. The above-mentioned display device includes but is not limited to a liquid crystal display, a light emitting diode, a display and a plasma display. In some optional embodiments, the display device can be a touch screen.

[0314] The electronic device also includes a communication interface for the electronic device to communicate with other devices or a communication network.

[0315] The embodiments of the present disclosure also provide a computer-readable storage medium. The above-mentioned method according to the embodiments of the present disclosure can be implemented in hardware, firmware, or can be implemented as a computer code that can be recorded in a storage medium, or can be implemented as a computer code that is originally stored in a remote storage medium or a non-temporary machine-readable storage medium and will be stored in a local storage medium and downloaded through a network, so that the method described herein can be stored in such software processing on a storage medium using a general-purpose computer, a dedicated processor, or programmable or dedicated hardware. Among them, the storage medium can be a magnetic disk, an optical disk, a read-only storage memory, a random access memory, a flash memory, a hard disk or a solid-state drive, etc.; further, the storage medium can also include a combination of the above-mentioned types of memory. It can be understood that a computer, a processor, a microprocessor controller, or 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 a computer, a processor, or hardware, the method shown in the above embodiment is implemented.

[0316] A part of the present disclosure may be applied as a computer program product, such as a computer program instruction, which, when executed by a computer, can call or provide the method and / or technical solution according to the present disclosure through the operation of the computer. Those skilled in the art should understand that the existence of computer program instructions in computer-readable media includes, but is not limited to, source files, executable files, installation package files, etc., and accordingly, the way in which computer program instructions are executed by a computer includes, but is not limited to: the computer directly executes the instruction, or the computer compiles the instruction and then executes the corresponding compiled program, or the computer reads and executes the instruction, or the computer reads and installs the instruction 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.

[0317] Although the embodiments of the present disclosure have been described in conjunction with the accompanying drawings, those skilled in the art may make various modifications and variations without departing from the spirit and scope of the present disclosure, and such modifications and variations are all within the scope defined by the appended claims.

Claims

1. A method for determining an association relationship, characterized in that: The method comprises: Obtaining an association state between a first object and a second object; If the association status indicates that the first object has a first association relationship with the second object, displaying an object adding control for the second object; In response to a triggering operation of the first object to add a control to the object, generating a verification request and sending the request to the second object; Based on the 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, wherein the second association relationship indicates that the first object has the permission associated with the second object.

2. The method according to claim 1, characterized in that The displaying of an object adding control for the second object includes at least one of the following: In response to a triggering operation of the first object on the object identifier of the second object, displaying an information interface of the second object and displaying the object adding control on the information interface; The 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.

3. The method according to claim 2, characterized in that The information push interface displaying the second object association includes: Displaying the information push interface associated with the second object on the media content stream display interface; An information push interface associated with the second object is displayed on a preset interface associated with the first object.

4. The method according to claim 1 or 2, characterized in that: The step of generating a verification request in response to a triggering operation of the first object to add a control to the object and sending the verification request to the second object comprises: In response to a triggering operation of the first object adding a control to the object, displaying a verification interface, the verification interface including a verification request sending control; In response to a triggering operation of sending the verification request control, a verification request is generated and sent to the second object.

5. The method according to claim 4, characterized in that The verification interface includes a verification information input area, and the generating of the verification request and sending the verification request to the second object in response to the triggering operation of the verification request sending control includes: In response to an information input operation in the verification information input area, obtaining verification information; In response to a triggering operation of sending the verification request control, a verification request is generated according to the verification information and sent to the second object.

6. The method according to claim 5, characterized in that Also includes: The verification information is saved, and when the first object triggers the object adding control again, the saved verification information is displayed in the verification information input area.

7. The method according to claim 5, characterized in that The verification interface also includes a note information input area, and the method further includes: In response to an information input operation in the remark information input area, acquiring remark information for the second object; In response to the second association relationship between the first object and the second object being established, the second object is displayed based on the remark information.

8. The method according to claim 1, characterized in that Also includes: Determine whether the interactive association between the first object and the second object meets a preset condition, and obtain a determination result; Based on the determination result, determine to display an object addition control or a target control for the second object in the information interface of the second object, and the target control includes a first association control indicating establishment of an association relationship with the second object or a second association control indicating that an association relationship has been established between the first object and the second object.

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

10. The method according to claim 9, characterized in that The displaying the target control on the information interface of the second object includes: Determine whether there is a first association relationship between the first object and the second object; If there is a first association relationship between the first object and the second object, displaying the second association control on the information interface of the second object; If there is no first association relationship between the first object and the second object, the first association control is displayed on the information interface of the second object.

11. The method according to claim 10, characterized in that The displaying the second associated control on the information interface of the second object includes: Displaying the second associated control and the first setting control on the information interface of the second object; In response to a triggering operation of the first object on the first setting control, displaying a first setting interface, wherein the first setting interface includes a preset adding control; In response to the triggering operation of the first object on the preset adding control, the verification request is generated and sent to the second object.

12. The method according to claim 1, characterized in that 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 includes: If the verification result indicates that the second object passes the verification request, determining to generate a target second association relationship between the first object and the second object, the target second association relationship being used to indicate that the first object has the authority to access the content published by the second object; If the verification result indicates that the second object fails the verification request, it is determined that the original first association relationship is maintained between the first object and the second object, and the original first association relationship is used to indicate that the first object does not have the authority to access the content published by the second object.

13. A method for determining a second association relationship, characterized in that: The method comprises: Receiving a verification request initiated by a first object, and displaying the verification request on an associated object application interface, wherein the first object has a first associated relationship with a second object; In response to a feedback operation of the second object on the verification request, generating a verification result corresponding to the verification request; A second association relationship between the first object and the second object is established 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.

14. The method according to claim 13, characterized in that Also includes: If the verification request carries verification information, displaying a reply control in the area where the verification request is located; In response to a trigger operation on the reply control, displaying an information reply area; In response to the information editing operation in the information reply area, reply information corresponding to the verification information is generated.

15. A device for determining an association relationship, characterized in that: The device comprises: An acquisition module, used to acquire the association state between the first object and the 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 has a first association relationship with the second object; A verification request sending module, configured to generate a verification request and send the verification request to a second object in response to a triggering operation of adding a control to the object by the first object; The second association relationship determination module is used 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, wherein the second association relationship indicates that the first object has permissions associated with the second object.

16. A device for determining an association relationship, characterized in that: The device comprises: A verification request receiving module, configured to receive a verification request initiated by a first object, and display the verification request on an associated object application interface, wherein the first object has a first associated relationship with a second object; 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; The second association relationship building module is used to build 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.

17. An electronic device, characterized in that: include: A memory and a processor, wherein the memory and the processor are communicatively connected to each other, the memory stores computer instructions, and the processor executes the method for determining the association relationship described in any one of claims 1 to 12, or executes the method for determining the association relationship described in any one of claims 13 to 14 by executing the computer instructions.

18. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer instructions, and the computer instructions are used to enable a computer to execute the method for determining an association relationship described in any one of claims 1 to 12, or to execute the method for determining an association relationship described in any one of claims 13 to 14.

19. A computer program product, characterized in that The method comprises computer instructions, wherein the computer instructions are used to cause a computer to execute the method for determining an association relationship according to any one of claims 1 to 12, or the method for determining an association relationship according to any one of claims 13 to 14.

Images