Methods, apparatus, equipment, storage media, and program products for determining association relationships

Abstract

This disclosure relates to the field of Internet technology, and discloses a method, apparatus, device, storage medium, and program product for determining association relationships. The method includes: obtaining 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 control added for the second object; responding to a triggering operation of the first object adding a control to the object, generating a verification request and sending it to the second object; and based on the 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, wherein the second association relationship indicates that the first object has permissions associated with the second object. By implementing the technical solution of this disclosure, the user experience of the application is improved.

Description

Technical Field

[0001] This disclosure relates to the field of Internet technology, specifically to methods, apparatus, equipment, storage media, and program products for determining related relationships. Background Technology

[0002] With the development of internet technology, mobile applications have become increasingly popular. For example, applications allow users to publish content, which can then be accessed by friends within the application. However, the user experience of interacting through applications needs improvement. Summary of the Invention

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

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

[0005] Secondly, this disclosure provides a method for determining an association relationship, comprising: receiving a verification request initiated by a first object and displaying the verification request on an object application interface, wherein the first object and a second object have a first association relationship; responding to the feedback operation of the second object on the verification request and generating a verification result corresponding to 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] Thirdly, this disclosure provides a device for determining a second association relationship, comprising: an acquisition module for acquiring an association state between a first object and a second object; a control display module for displaying an object-added control for the second object if the association state indicates that the first object and the second object have a first association relationship; a verification request sending module for generating a verification request and sending it to the second object in response to a triggering operation of the first object adding a control to the object; and a second association relationship determination module for determining a second association relationship between the first object and the second object based on the verification result generated by the second object in response to the verification request, wherein the second association relationship indicates that the first object has permissions associated with the second object.

[0007] Fourthly, this disclosure provides an apparatus for determining a second association relationship, comprising: a verification request receiving module, configured to receive a verification request initiated by a first object and display the verification request on an object application interface, wherein the first object and the second object have a first association relationship; a verification result generating module, configured to generate a verification result corresponding to the verification request in response to a feedback operation of the second object on the verification request; and a second association relationship constructing module, configured to construct a second association relationship between the first object and the second object based on the verification result and send the verification result to the first object, so that the first object determines the second association relationship between the first object and the second object based on the verification result.

[0008] Fifthly, this disclosure provides an electronic device, including: a memory and a processor, the memory and the processor being communicatively connected to each other, the memory storing computer instructions, and the processor executing the computer instructions to perform the method for determining the association relationship of the first aspect or any corresponding embodiment described above, or to perform the method for determining the association relationship of the second aspect or any corresponding embodiment described above.

[0009] In a sixth aspect, this disclosure provides a computer-readable storage medium storing computer instructions, which are used to cause a computer to perform the method for determining the association relationship of the first aspect or any of its corresponding embodiments, or to perform the method for determining the association relationship of the second aspect or any of its corresponding embodiments.

[0010] In a seventh aspect, this disclosure provides a computer program product, including computer instructions, which are used to cause a computer to execute the method for determining the association relationship of the first aspect or any corresponding embodiment described above, or to execute the method for determining the association relationship of the second aspect or any corresponding embodiment described above.

[0011] The method, apparatus, device, storage medium, and program product for determining association relationships provided in this disclosure obtain the association status between a first object and a second object to determine whether the first object can trigger the addition of the second object based on 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 can determine whether to add the first object as the target associated object based on the verification request, thereby improving the user experience of the application. Attached Figure Description

[0012] To more clearly illustrate the technical solutions in the specific embodiments of this disclosure or the prior art, the drawings used in the description of the specific embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of this disclosure. For those skilled in the art, other drawings can be obtained from these drawings without creative effort.

[0013] Figure 1 This is a flowchart illustrating a method for determining association relationships according to embodiments of this disclosure;

[0014] Figure 2 This is a schematic diagram illustrating the addition of controls to a homepage display object according to an embodiment of this disclosure;

[0015] Figure 3 This is a flowchart illustrating another method for determining an association according to an embodiment of this disclosure;

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

[0017] Figure 5 This is a schematic diagram illustrating the pushing of a second object within waterfall content according to an embodiment of this disclosure;

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

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

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

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

[0022] Figure 10 This is a schematic diagram showing the prompt information according to an embodiment of the present disclosure;

[0023] Figure 11 This is a schematic diagram illustrating the addition of controls to an object displayed on an information interface according to an embodiment of the present disclosure;

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

[0025] Figure 13 This is a schematic diagram illustrating the triggering of other controls according to an embodiment of this disclosure;

[0026] Figure 14 This is a schematic diagram showing that the control added to the object is in a disabled state according to an embodiment of this disclosure;

[0027] Figure 15 This is a flowchart illustrating another method for determining an association relationship according to an embodiment of this disclosure;

[0028] Figure 16 This is a schematic diagram of the target associated object application interface according to an embodiment of this disclosure;

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

[0030] Figure 18 This is a schematic diagram showing the over-limit warning information according to an embodiment of the present disclosure;

[0031] Figure 19 This is a schematic diagram of message types according to embodiments of this disclosure;

[0032] Figure 20 This is a schematic diagram of an application based on an embodiment of this disclosure;

[0033] Figure 21 This is a schematic diagram illustrating the setting notes according to an embodiment of this disclosure;

[0034] Figure 22 This is a schematic diagram customized based on the remarks information of the embodiments of this disclosure;

[0035] Figure 23 This is a structural block diagram of an apparatus for determining association relationships according to embodiments of the present disclosure;

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

[0037] Figure 25 This is a schematic diagram of the hardware structure of an electronic device according to an embodiment of this disclosure. Detailed Implementation

[0038] To make the objectives, technical solutions, and advantages of the embodiments of this disclosure clearer, the technical solutions of the embodiments of this disclosure will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this disclosure, and not all embodiments. Based on the embodiments of this disclosure, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this disclosure.

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

[0040] For example, upon receiving a user's active request, a prompt message is sent to the user to explicitly inform them that the requested operation will require the acquisition and use of the user's personal information. This allows the user to independently choose whether to provide personal information to the software or hardware, such as the electronic device, application, server, or storage medium performing the operations of this disclosed technical solution, based on the prompt message.

[0041] As an optional but non-limiting implementation, in response to a user's active request, sending a prompt message to the user can be done via a pop-up window, where the prompt message can be presented in text format. Furthermore, the pop-up window can also include a selection control allowing the user to choose "agree" or "disagree" to provide personal information to the electronic device.

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

[0043] It is understood 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 related provisions.

[0044] This disclosed technical solution, when determining the association relationship for granting access to each other's published content, requires mutual verification based on existing mutual following or interaction before establishing such an association. This further enhances the user experience of the application.

[0045] According to embodiments of this disclosure, a method for determining association relationships is provided. It should be noted that the steps shown in the flowcharts of the accompanying drawings can be executed in a computer system such as a set of computer-executable instructions. Furthermore, although a logical order is shown in the flowcharts, in some cases, the steps shown or described may be executed in a different order than that shown here.

[0046] This embodiment provides a method for determining association relationships, which can be used in electronic devices such as mobile phones, tablets, and computers. This embodiment uses the electronic device used by the first object as the execution subject. Figure 1 This is a flowchart of a method for determining association relationships according to embodiments of this disclosure, such as... Figure 1 As shown, the process includes the following steps:

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

[0048] The association status is used to characterize whether a first object and a second object have a first association relationship, such as mutual following or mutual followers. For example, mutual following, mutual followers, or one-sided following indicate that a first association relationship exists between the first object and the second object; the absence of the above relationships indicates that a first association relationship does not exist between the first object and the second object.

[0049] An electronic device has an application installed. The first object registers a corresponding account on the application to interact with the second object. The association status between the first and second objects can be obtained by reading the first object's account information.

[0050] Specifically, if the first object only interacts temporarily with the second object, the first object may not establish a first association with the second object, and correspondingly, there is no first association between the first and second objects. If the first object wishes to interact with the second object multiple times, it can request to establish a first association with the second object before interacting with it. Accordingly, the electronic device can associate the first object's account with the second object's account and record this association information in the account information. Therefore, by reading the association information corresponding to the account information, the association status between the first and second objects can be determined.

[0051] Step S102: If the association status indicates that the first object and the second object have a first association relationship, display the object to be added for the second object.

[0052] The object addition control is used to trigger the addition of a second object as the target associated object to a first object. The association status is used to indicate whether a first association exists or not; for example, the identifier for an existing first association is 1, and the identifier for a non-existent first association is 0. By determining the identifier corresponding to the association status, it can be determined whether a first association exists 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 mutually associated. When the first object enters the second object's homepage, the second object's homepage will display an object adding control, such as... Figure 2 As shown.

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

[0055] The verification request is generated when a first object requests to add a second object as a target associated object. This verification request is used by the second object to verify the first object and determine whether to approve the first object's request. Specifically, when the first object clicks the object add control, the application in the electronic device can respond to the first object's click operation, triggering a verification request to add the second object as a target associated object, and sending the verification request to the second object. The second object can then receive and view the verification request through the application.

[0056] Step S104: Based on the verification result generated by the second object in response to the verification request, determine the second association relationship between the first object and the second object. The second association relationship indicates that the first object has the permissions associated with the second object.

[0057] After the second object sees the verification request sent by the first object, it can view the first object's homepage to learn about the first object's information, thereby determining whether to accept the verification request. If the second object accepts the verification request initiated by the first object, a second association is established between the first and second objects. The first and second objects are mutually associated objects and each has the permissions associated with the other. Specifically, these associated permissions include the permission to access the content published by the other. It should be noted that the published content here refers to publicly published content; access is not granted to privately published content.

[0058] At the same time that the second object initiates the verification request through the first object, the verification result generated by the second object in response to 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 that it has established a second association relationship with the second object.

[0059] The method for determining the association relationship provided in this embodiment allows the first object to initiate a verification request to the second object if it wants to establish a second association relationship with the second object when the first object has a first association relationship with the second object. Based on the verification result generated by the second object in response to the verification request, it is determined whether the first object has the permissions associated with the second object. This achieves the requirement that verification is required to determine whether to add the first object as the target associated object, thereby improving the user experience of the application.

[0060] This embodiment provides a method for determining association relationships, which can be used in electronic devices such as mobile phones, tablets, and computers. This embodiment takes the electronic device used by the first object as the execution subject. Figure 3 This is a flowchart of a method for determining association relationships according to embodiments of this disclosure, such as... Figure 3 As shown, the process includes the following steps:

[0061] Step S201: Obtain the association status between the first object and the second object. For detailed explanation, please refer to the relevant descriptions of the corresponding steps in the above embodiments; they will not be repeated here.

[0062] Step S202: If the association status indicates that the first object and the second object have a first association relationship, display the object to be added for the second object.

[0063] Specifically, step S202 above may include:

[0064] In step S2021, in response to the triggering operation of the first object on the object identifier of the second object, the information interface of the second object is displayed, and the object addition control is displayed on the information interface.

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

[0066] In one specific implementation, the first object can click on the location of the second object in a non-reply area to enter the second object's homepage, where an information interface is displayed. This information interface shows the second object's nickname, avatar, number of likes, number of followers, number of fans, the first association between the first and second objects, signature information, and published works. Simultaneously, an object addition control is displayed on the information interface; this control can be placed above published works. A private message control can also be set to allow the first object to send private messages to the second object, such as... Figure 2 As shown.

[0067] By triggering the second object to enter its information interface and displaying the object addition control on the information interface, the experience of the first object in adding the second object is improved.

[0068] Specifically, step S202 above may include:

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

[0070] The information push interface is used to display the second object. It includes an object addition control, allowing the first object to select and add the second object it is interested in. The application in the electronic device can then display the information push interface associated with the second object to the first object based on the first object's interaction data, thus enabling targeted push notifications to the second object.

[0071] By displaying an object addition control on the information push interface corresponding to the second object, the scenario of the first object adding the second object is enriched, which helps to increase the willingness of the first object to add it.

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

[0073] The appearance and layout of the push card are pre-designed, including the position and style of elements such as the title, image, description, and buttons. Attribute information of the second object associated with the first object is retrieved from the application's database and populated into the corresponding positions on the card, ensuring accuracy and completeness. Interactive elements, such as an object addition button, can be added to the card to allow the first object to add objects. After assembling the card, it is pushed to the first object within the application to present the second object's attribute information in a concise and intuitive way.

[0074] In some optional implementations, the step S2022 above, which involves displaying the information push interface associated with the second object, includes:

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

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

[0077] Media content streaming refers to multimedia data, such as audio, video, images, and text, continuously transmitted by an application over a network. Media content streaming allows a first user to simultaneously receive and play the corresponding multimedia content. The preset interface is a pre-defined browsing interface designed to display information push notifications to the first user. When the first user browses media content through the preset interface, the information push notification interface can be displayed within the media content streaming display of the preset interface.

[0078] In some specific implementations, based on the interaction relationship of the first object, an information push interface is displayed in the information stream to recommend a second object associated with it to the first object. This second object can be one or more, such as... Figure 4 As shown.

[0079] In some specific implementations, when a user browses a media content stream, an information push interface can be displayed within the shown 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 within the display of the media content stream, such as... Figure 5As shown. An information push interface can also be displayed when the media content stream browsing ends, to push the second object to the first object; that is, the push notification associated with the second object is displayed at the bottom of the media content stream, such as... Figure 5 As shown. It is understandable that... Figure 5 The waterfall layout can display a media content stream, which can include multiple media content items arranged in sequence. Users can browse the media content in the stream by swiping. Multiple user-posted media content items can be displayed simultaneously in the waterfall layout. Comments and other interactive information can be displayed below the screen of each media content item. Different media content items can occupy different lengths in the waterfall layout based on their screen ratio and the amount of comments and other interactive information.

[0080] In some specific implementations, the preset interface can be a user content display interface, used to display social sharing content posted by other objects. A first object can switch from other interfaces to the user content display interface to browse social sharing content. If the social sharing content displayed on the user content display interface is detected to be empty, an information push interface can be displayed on the user content display interface to push information to a second object, enabling the first object to add the second object, such as... Figure 6 As shown.

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

[0082] In some specific implementations, the preset interface can be a second association recommendation interface, which displays multiple second objects that have a first association with the first object. The first object can switch from other interfaces to the second association recommendation interface to view the associated second objects and select the second object of interest to add. Figure 8 As shown, after the first object enters the second association recommendation interface, the second object is pushed and displayed on the second association recommendation interface.

[0083] This embodiment supports multiple ways to push the second object in various application scenarios, enriching the ways to push the second object and making the push methods more diversified, thereby enabling the first object to know about the second object associated with it in various scenarios.

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

[0085] Specifically, step S203 includes:

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

[0087] The verification interface displays verification information and includes a verification request sending control, which can be in the form of a button. Figure 9 As shown, when the first object triggers the object addition control, the verification interface will be pulled up from the current interface, and a verification request send button will be displayed on the verification interface.

[0088] Step S2032: In response to the triggering operation of the control for sending verification requests, 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 first object's triggering operation, 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 receive the verification request and confirm whether to establish a second association with the first object.

[0090] The method for determining the association provided in this embodiment can pop up a verification interface when a component is added to the trigger object, so that a verification request can be sent to the second object through the verification interface, thereby enabling the construction of the second association through verification and improving the experience of constructing the second association.

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

[0092] Step b1: In response to the information input operation in the verification information input area, verification information is obtained.

[0093] Step b2: In response to the triggering operation of the control for sending a verification request, a verification request is generated according to the verification information and sent to the second object.

[0094] like Figure 9As shown, the verification interface includes a verification information input area, which allows a 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 the 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 a verification request sending control to send the verification information.

[0095] The method for determining the association provided in this embodiment supports editing verification information on the verification interface so that the verification information is sent at the same time as the verification request. This makes it easier for the second object to confirm the identity information of the first object based on the verification information, which helps to improve the pass rate of the verification request.

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

[0097] After the first object sends a verification request, the electronic device will save the verification information corresponding to the verification request. When the first object triggers the object addition control again to request the addition of other objects, the previously 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 next verification interface will also be empty, that is, it will be consistent with the verification information when the verification request was triggered last time.

[0099] The method for determining the association provided in this embodiment supports the saving of verification information so that it can be used directly when sending verification requests next time, avoiding the need to repeatedly enter the same verification information and improving the verification request sending experience of the first object.

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

[0101] After a verification request is triggered, the electronic device can monitor its sending status to determine if the request was sent successfully. Upon successful verification, a first notification message will be displayed on the interface for adding a second object, indicating that the verification request was successfully sent. For example, this first notification message could be "Object addition request sent," or similar. Figure 10 As shown.

[0102] The method for determining the association provided in this embodiment supports the display of prompt information when the verification request is successfully sent, 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 verification requests sent reaches a preset value, displaying a second prompt message indicating that verification is pending.

[0104] The preset value is the maximum number of times a first object is allowed to send verification requests to the same second object. If the first object does not receive a verification result from the second object, it can repeatedly send verification requests to the second object, accumulating the number of verification requests sent. When the preset number of verification requests is reached, further verification requests are rejected, and a second prompt message is displayed on the interface for adding the second object, indicating that the limit for the number of verification requests has been exceeded. For example, this second prompt message could be "You have added the other party multiple times, please wait patiently for the application," or similar. Figure 10 As shown.

[0105] In a specific example, object A can add object B multiple times. Within a single relationship, the maximum number of additions per six calendar months (calculated from the date the second object is first added) is 5 (i.e., 5 verification requests). Exceeding this number is considered exceeding the limit. When the object addition control is triggered again, the message "You have already added the other party multiple times. Please wait patiently for the application" will be displayed.

[0106] The method for determining the association provided in this embodiment supports displaying prompt information when too many verification requests are sent, so as to remind the first object that too many verification requests have been sent and avoid the user from sending them repeatedly.

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

[0108] In a specific example, if the verification information is unavailable, the verification request cannot be sent successfully. For instance, exceeding the character limit for the verification information will prevent the request from being sent. In this case, a third 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. For example, this third message could be "Verification information unavailable, please modify and try again," such as... Figure 10 As shown.

[0109] In a specific example, if the verification request fails to send due to network issues, a third message will also be displayed on the interface for adding the second object to notify the first object of the verification request failure. For example, this third message could be "Your network is having problems, please try again," or similar. Figure 10 As shown.

[0110] The method for determining the association provided in this embodiment supports the display of prompt information when the verification request fails to be sent, so that the first object can resend the verification request in a timely manner.

[0111] In some optional implementations, the verification interface further includes a remarks input area for entering remarks about the second object. Accordingly, the above method also includes:

[0112] Step c1: In response to the information input operation in the remarks information input area, obtain the remarks information for the second object.

[0113] Step b2: In response to the establishment of the second association between the first object and the second object, the second object is displayed based on the remarks information.

[0114] like Figure 9 As shown, the verification interface includes a notes input area, which allows a first object to input notes for a second object. Specifically, the first object can click the notes input area to pull an input component (e.g., a keyboard component) and input notes into the notes input area. After completing the input of verification information and / or notes, the first object can trigger a verification request sending control to send the verification information.

[0115] When the second object sends a verification request through the first object, the second association between the first and second objects is established. At this time, the second object will be displayed in the target associated object list of the first object according to the remarks information, so that the first object can quickly retrieve the second object with which it has a target association based on the remarks information.

[0116] The method for determining the association provided in this embodiment supports editing the remarks information when sending the verification request. After the construction of the second association is completed, the second object is displayed according to the remarks information, so that the first object can quickly retrieve the second object based on the remarks information.

[0117] In some optional implementations, the method further includes: if the remarks information is unavailable, displaying a fourth prompt message to modify the remarks information.

[0118] There is a character limit to the input of the remarks information. If the number of characters in the remarks exceeds the limit, the remarks will be unavailable. Unavailable remarks will also prevent the verification request from being sent successfully. In this case, a fourth message can be displayed on the interface for adding the second object to notify the first object to modify the remarks in the verification request. For example, this fourth message could be "Remarks are unavailable, please modify and try again," such as... Figure 10 As shown.

[0119] The method for determining the association provided in this embodiment supports the display of prompt information when the remarks information is unavailable, so that the first object can modify the remarks information in a timely manner.

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

[0121] Step d1: Determine whether the interaction between the first object and the second object meets the preset conditions, and obtain the determination result.

[0122] Step d2: Based on the determined result, determine to display an object control or target control for the second object in the information interface of the second object. 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.

[0123] The preset conditions are pre-defined conditions used to determine whether there is an interactive relationship between the first object and the second object. Examples include: the first object and the second object follow each other; the first object and the second object are mutual followers; the first object unilaterally follows the second object; the second object unilaterally follows the first object; and there is interactive information between the first object and the second object. The preset conditions are not specifically limited here, and those skilled in the art can determine them according to actual needs.

[0124] The first association control indicates the establishment of an association between the first object and the second object, while the second association control indicates the existence of an association between the first object and the second object. By detecting the association status 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 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 target control for the second object is displayed on the information interface of the second object. The target control includes either the first association control indicating the establishment of an association with the second object or the second association control indicating that an association has already been established between the first object and the second object.

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

[0126] Step d21: In response to determining that the interaction between the first object and the second object meets the preset conditions, the information interface of the second object displays the object control added for the second object.

[0127] Step d22: In response to determining that the interaction between the first object and the second object meets the preset conditions, the target control is displayed on the information interface of the second object.

[0128] If the interaction between the first object and the second object is determined to meet the preset conditions for mutual association, then when the first object enters the information interface of the second object, the control added to the object for the second object will be displayed in the information interface of the second object.

[0129] If the interaction between the first object and the second object is determined to meet the preset conditions for unilateral association, then when the first object enters the information interface of the second object, the target control for the second object will be displayed in 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 step d22 above may include:

[0131] Step e1: Determine whether there is a first association relationship 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 the 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, the first association control is displayed on the information interface of the second object.

[0134] The first association relationship is used to characterize whether there is a mutual relationship between the first object and the second object, such as mutual following or being mutual fans. If a first association relationship exists between the first object and the second object, it means that there is a mutual relationship between the first object and the second object. In this case, a second association control (such as "Following") 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 there is no mutual relationship between the first object and the second object. In this case, a first association control (such as "Following") is displayed on the information interface of the second object.

[0135] Specifically, if there is no first association between the first object and the second object, it is possible to detect whether there is an interactive association between them. Specifically, this interactive association can include interactive works, one-sided associations, and contact friends in the user's address book with full authorization. The specific content of the interactive association is not limited here.

[0136] If there is an interactive relationship between the first object and the second object, the first associated control for the second object will be displayed on the information interface of the second object.

[0137] If, by determining the identifier corresponding to the association status, it is found that there is no first association relationship between the first object and the second object, then the interaction relationship data of the first object can be further obtained. The interaction relationship data of the first object is parsed to determine whether an interaction association exists between the first object and the second object. If an interaction association exists between the first object and the second object, and the second object is the first interactive association object of the first object, then when the first object enters the information interface of the second object, an object addition control will be displayed in the information interface of the second object.

[0138] If there is an interactive relationship between the first object and the second object, and the second object is a second interactively related object that the first object follows, when the first object enters the information interface of the second object, the second related control (e.g., "Followed") and settings control will be displayed in the information interface of the second object. At this time, after the first object triggers the settings control in the information interface, the object can add controls in the settings interface corresponding to the settings control, such as... Figure 12 As shown.

[0139] If there is an interactive relationship between the first object and the second object, and the second object is a third interactive relationship object that follows the first object, when the first object enters the information interface of the second object, the first associated control (such as "follow") will be displayed in the information interface of the second object. After the first object triggers the associated control, the object can add control in the information interface of the second object.

[0140] The first object can click on the object add control to trigger the process of adding the second object. Specifically, in response to the first object's click on the object add control, the application triggers a verification request to add the second object as the target associated object, and sends the verification request to the second object. The second object can then receive and view the verification request through the application.

[0141] In some alternative implementations, such as Figure 11 As shown, the above method also includes:

[0142] Step f1: The second associated control and the first setting control are displayed in the information interface of the second object.

[0143] Step f2: In response to the first object's trigger operation on the first setting control, the first setting interface is displayed, which includes preset add controls.

[0144] Step f3: In response to the first object's trigger operation for adding a preset control, a verification request is generated and sent to the second object.

[0145] When the first object clicks the first settings control, the application can respond to the first object's click operation on the first settings control, pop up the first settings interface from the information interface, and display the preset added controls in the first settings interface.

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

[0147] By integrating the add control into the first settings control, multiple ways are provided for adding a second object to the first object, making it easy for the first object to choose the desired addition method according to actual needs.

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

[0149] Step e1: If there is no interactive relationship between the first object and the second object, display the first associated control for the second object.

[0150] Step e2: In response to the first object's trigger operation on the first associated control, establish the first association relationship between the first object and the second object.

[0151] Step e3: If the first association is successfully established, display the second association control and the second setting control.

[0152] Step e4: In response to the first object's trigger operation on the second setting control, the second setting interface is displayed, which includes preset add controls.

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

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

[0155] If there is no interactive relationship between the first object and the second object, it means that the second object is an unfamiliar object compared to the first object. In this case, when the first object enters the information interface of the second object, the first associated control (such as "Follow") will be displayed in the information interface of the second object. Figure 13 As shown, clicking the first associated control establishes a first association between the first and second objects, meaning the first object unilaterally associates with the second object. This association can also be established by clicking other controls (such as...). Figure 13 The "..." shown in the image allows you to set relevant attribute information in the pop-up interface, such as unlinking, setting notes, etc.

[0156] When the first association between the first object and the second object is successfully established, the second association control and the second setting control are displayed on the information interface corresponding to the second object, such as... Figure 12 As shown.

[0157] When the first object clicks the second settings control, the application can respond to the first object's click operation on the second settings control, pop up the second settings interface from the information interface, and display the preset added controls in the second settings interface.

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

[0159] When it is determined that the first association between the first object and the second object has failed to be established, the verification request to add the object to the second object is refused, and a fifth prompt message is triggered to indicate that the association between the first object and the second object has failed. At this time, the first object can trigger the second association control again to request the first association with the second object.

[0160] The method for determining the association provided in this embodiment supports building the first association before triggering the addition of the second object when there is no interactive association between the first object and the second object. This ensures that the construction of the second association is safer and improves the user's experience in building the second association.

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

[0162] Step g1: Based on the account attribute information of the second object, determine whether the second object is a private object.

[0163] In 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, then the object addition control is disabled.

[0164] Account attribute information is used to characterize the attributes of an object, and a private account flag is set within the account attribute information. By parsing the account attribute information of a 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, then the first object cannot add the second object as a target associated object.

[0165] If a first object wants to establish a second association with a second object, the first object needs to request the establishment of the first association from the second object. The first association is established when the second object approves the association request. At this point, if the first object only unilaterally associates with the second object, the control added to the object will still be disabled, such as... Figure 14 As shown. Only when there is a mutual relationship between the first object and the second object can the first object send a verification request for object addition to the second object by triggering the object addition control.

[0166] When other objects add objects to a private object, the object addition control is disabled, ensuring the privacy of the private object.

[0167] Step S204: Based on the verification result generated by the second object in response to the verification request, determine the second association relationship between the first object and the second object. The second association relationship indicates that the first object has the permissions associated with the second object.

[0168] Specifically, step S204 includes:

[0169] Step S2041: If the verification result indicates that the second object passes the verification request, then a target second association relationship is determined to be generated between the first object and the second object. The target second association relationship is used to indicate that the first object has the permission to access the content published by the second object.

[0170] If the second object receives a verification request sent by the first object, a second target association is generated between the first and second objects, giving the first object permission to access the content published by the second object, and the second object will also have permission to access the content published by the first object.

[0171] Accordingly, when the second object passes the verification request, the application can send the verification result generated by the second object in response to the verification request back to the first object. At this point, the first object can determine that a target second association relationship has been formed between it and the second object.

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

[0173] If the second object fails to pass 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 permission to access the content published by the second object, and the second object also does not have permission to access the content published by the first object.

[0174] Accordingly, if the second object fails the verification request, the application can send the verification result generated by the second object in response to the verification request back to the first object. At this point, the first object can determine that no target second association has been established between it and the second object. If the first object still wishes to access the content published by the second object, it can send the verification request to the second object again.

[0175] The method for determining the association relationship provided in this embodiment involves the first object determining whether the verification request passes based on the verification result. This allows for the clarification of the second association relationship between the first object and the second object based on whether the verification request passes or fails, thereby clarifying the first object's permissions for the content published by the second object and preventing the content published by the second object from being accessed arbitrarily.

[0176] This embodiment provides a method for determining association relationships, which can be used on electronic devices such as mobile phones, tablets, and computers. This embodiment takes the electronic device used by the second object as the execution subject. Figure 15 This is a flowchart of a method for determining a second association relationship according to an embodiment of this disclosure, such as... Figure 15 As shown, the process includes the following steps:

[0177] Step S301: Receive the verification request initiated by the first object and display the verification request on the associated object application interface. The first object and the second object have a first association relationship.

[0178] As described above, when the first object and the second object have a first association relationship, when the first object triggers the addition of a control to add the second object as the target associated object, it will generate a corresponding verification request and send the verification request to the second object. Specifically, an application is also installed on the electronic device used by the second object. This application receives the verification request initiated by the first object, and the second object can then view the verification request initiated by the first object in the associated object application interface. Figure 16 As shown.

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

[0180] The feedback operation is the verification operation performed by the second object in response to the verification request initiated by the first object. This feedback operation can be executed by clicking the verification tag corresponding to the verification request. For example... Figure 16 As shown, the second object can click the "Go to Verification" tab corresponding to the verification request to verify the first object and generate a verification result for the first object.

[0181] Step S303: Based on the verification result, a second association relationship between the first object and the second object is constructed, and the verification result is sent to the first object so that the first object can determine 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 is established between the first and second objects based on the verification result. Specifically, if the second object passes the verification request initiated by the first object, a second association is established between the first and second objects; if the second object fails the verification request initiated by the first object, the original first association between the first and second objects is maintained. Simultaneously, the second object sends the verification result to the first object through the application, enabling the first object to determine its second association with the second object based on the verification result.

[0183] The method for determining the association provided in this embodiment allows the second object to respond to the verification request received by the first object, thereby constructing a second association between the first and second objects based on the verification result provided by the second object. This further strengthens the method for determining the second association and improves 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 new verification requests and the number of new 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 with the second object and has permission to access the content published by the second object. The associated object request count is the number of new information requests made to the second object.

[0186] Specifically, the number of related object applications is displayed in the user content display interface, allowing the second object to intuitively understand the number of application messages it has received. This number of related object applications is the sum of the number of new verification requests and the number of new application messages. The number of new verification requests refers to the number of new verification requests received by the second object, and the number of new application messages refers to the number of messages sent by newly applying friends.

[0187] In some optional implementations, the number of associated object applications is displayed as a bubble at the top of the user content display interface. For example... Figure 17 As shown, the number of related object applications is displayed at the top of the user content display interface in the form of bubbles to avoid affecting the display of dynamic information in the user content display interface.

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

[0189] Step A1: Obtain the message type corresponding to the second object.

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

[0191] The message type indicates the message style of the messages received by the second object and the message style of the messages sent by the second object. Specifically, such as... Figure 19 As shown, 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 "accept"; (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 "accept"; (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), (6), then the number of related object requests will be updated.

[0193] The method for determining associations provided in this embodiment supports multiple message types and enriches message styles, thereby enabling verification requests to meet a variety of user needs.

[0194] In some optional implementations, the method further includes: in response to a click operation by the second object on the number of applications for the associated object, displaying an associated object application interface, and the number of applications for the associated object disappearing 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 in the user content display interface. Correspondingly, the application can respond to the second object's click operation on the associated object application number in the user content display interface by switching from the user content display interface to the associated object application interface. For example Figure 16 As shown, the associated object application interface displays a list of application information, which shows at least one application. When switching back from the associated object application interface to the user content display interface, the associated object application count will disappear from the user content display interface.

[0196] The method for determining association relationships 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, then displaying a new flag at the position of the new verification request in the list; wherein the new flag disappears the next time the associated object application interface is accessed.

[0198] A new flag is displayed on newly added verification requests to indicate that the verification request was newly received by the second object. For example... Figure 16 As shown, the new icon can be a small dot and is displayed before the new verification request. When the second object switches out of the associated object application interface and re-enters the associated object application interface, the previously displayed new icon will disappear.

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

[0200] In some optional implementations, the verification requests are displayed in the application information display list in chronological order. Specifically, the verification requests can be sorted from most recent to oldest, for example, the verification request for the first object A is ranked xth. When a response from the first object A is added, or when a new verification request is received, the application information display list will update the timestamps of each application and reorder them according to the updated timestamps.

[0201] The method for determining the association provided in this embodiment displays the application information of each verification request in an orderly manner by sorting the information by time.

[0202] In some alternative implementations, the application information display list includes at least one page for displaying verification requests received in different time intervals.

[0203] Different time intervals are used to represent different time ranges, such as the last three days, three days ago, and six months ago, etc. Figure 16 As shown, the application information display list can be divided according to different time intervals, resulting in pagination for each time zone. Each pagination displays the verification requests received for the corresponding time interval.

[0204] The method for determining the association provided in this embodiment supports pagination of verification requests based on different time zones, which makes it easier for the second object to view and manage verification requests in different time intervals, thereby improving the efficiency and readability of information display.

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

[0206] The preset quantity is a pre-defined limit for representing an excessive number of verification requests. The number of new verification requests received by the second object is counted. This number is then compared to the preset quantity to determine if it exceeds the limit. If the number of new verification requests exceeds the preset quantity, an over-limit warning message is displayed on the associated object application interface.

[0207] like Figure 18 As shown, the excessive message can be displayed as a notification bar. When the number of new verification requests exceeds the preset limit, the notification bar will display the message "Too many unfamiliar messages received. You can set me as the target associated object." If the second object clicks on the excessive message, it can enter the addition settings interface. The second object can set the addition conditions in the addition settings interface, which can filter subsequent verification requests and reject verification requests that do not meet the conditions.

[0208] The method for determining the association provided in this embodiment allows the second object to see an over-limit prompt message on the association object application interface when the number of newly received verification requests exceeds a preset number. This enables the second object to understand the status of the currently received verification requests and take corresponding measures.

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

[0210] Step B1: In response to the operation to disable the over-limit warning message, disable the over-limit warning message.

[0211] Step B2: When the number of times the shutdown operation is triggered reaches the preset number, the over-limit prompt message will no longer be displayed.

[0212] like Figure 18 As shown, the over-limit warning message has a corresponding close label, meaning that the over-limit warning message can be closed. When the second object clicks the close label corresponding to the over-limit warning message, the application can respond to the second object's close operation and close the over-limit warning message.

[0213] The preset number of times is a pre-defined number of times the over-limit warning will be displayed, for example, 3 times. When the second object clicks the close tab, the application can count the number of times the second object triggers the close operation and compare this number with the preset number to determine if the number of times the close operation has been triggered has reached the preset number. If the number of times the close operation has been triggered has reached the preset number, the over-limit warning message will no longer be displayed. The over-limit warning message will only be triggered and displayed again when the number of new verification requests received reaches the preset number.

[0214] The method for determining the association provided in this embodiment supports turning off the over-limit notification information, and stops displaying it when the number of times it is turned off reaches a preset number, thereby realizing the flexible turning off of the over-limit notification information.

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

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

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

[0218] The deletion operation is performed by the second object in response to the verification request initiated by the first object. This deletion operation can be triggered by long-pressing the verification request. Figure 19 As shown, the second object can long-press the verification request to trigger the display of the "Delete Notification" button, and clicking "Delete Notification" will remove the verification request from the application information display list.

[0219] If the first object sends a verification request to the second object again after the first object is deleted, the verification request of the deleted first object will be displayed again in the application information display list.

[0220] In some optional implementations, if the second object responds to the verification information carried in the verification request initiated by the first object, and deletes the verification request after responding, then when the first object responds to the second object's response message again, the verification information corresponding to the deleted first object's verification request will be displayed again in the application information display list.

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

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

[0223] Once the second object terminates its second association with 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] The method for determining the association provided in this embodiment ensures that if the second association is terminated, the corresponding application information will be deleted as well, thereby ensuring that all 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, display a response control in the area where the verification request is located.

[0227] Step D2: In response to the triggered action on the reply control, display the message reply area.

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

[0229] When the second object receives a verification request that carries verification information, the second object can respond with that verification information. For example... Figure 16 As shown, if the verification request carries verification information, a response control is displayed in the area where the verification request is located.

[0230] The second object can click the reply control to respond to the verification message. When the second object clicks the reply control, a message reply area pops up, where the second object can enter a reply message. Specifically, clicking the message reply area brings up a message input component (such as a keyboard input component), allowing the second object to edit the message reply area, generate the corresponding reply message, and send it to the first object. If sending the reply message fails, a failure message can be generated, such as "Sending failed, please try again." At this point, the second object can resend the reply message to the first object.

[0231] Specifically, the response 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 respond to the verification information; (2) when the first object adds the second object, the verification request carries verification information, and the second object responds to the verification information, and the first object can respond to the response of the second object.

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

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

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

[0235] If the second object refuses to establish a second association with the first object, and after replying to the verification message to inform the first object of its refusal, it adds the first object to its blacklist, then the first object will be unable to send a reply message to the second object.

[0236] If the second object, after receiving the reply from the first object, does not read the reply and instead adds the first object to its blacklist, then the reply will be deleted.

[0237] If the second object blacklists the first object after viewing the first object's reply, the second object will no longer receive any messages from the first object, and previously received messages will be displayed as expired.

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

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

[0240] Step E1: In response to the note trigger operation for the first object, the note editing area is displayed.

[0241] Step E2: In response to input operations in the note editing area, generate note information corresponding to the first object.

[0242] When the second object passes the verification request of the first object, the second association relationship is established between the first and second objects, such as... Figure 20 As shown. At this point, the second object can add comments to the first object for later retrieval. For example... Figure 21 and Figure 22 As shown, when the second object triggers a note operation on the first object, it displays a note editing area where the second object can enter note information.

[0243] The method for determining the association provided in this embodiment supports editing of remarks information and enables customization of alternative information.

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

[0245] If the first object exists in the address book of the second object, it indicates that the first object has a note. When the note operation for the first object is triggered, the name of the first object in the address book can be displayed in the note editing area, and this name can be used as the note information for the first object.

[0246] If the first object does not exist in the second object's address book, but the first object's notes exist in the verification information, then when the note operation for the first object is triggered, the notes in the verification information can be displayed in the note editing area.

[0247] If there are historical notes for the first object, then when a note operation is triggered for the first object, the historical notes will be displayed in the note editing area.

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

[0249] In some optional implementations, if the notes editing area is empty, clicking "Done" or "Close Notes Editing Area" is equivalent to skipping the notes operation.

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

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

[0252] If the verification request fails due to network issues or other reasons when the second object attempts to pass the verification request, a corresponding retry message (such as "Failed, please try again") can be generated and displayed to remind the second object to try to pass the verification request again.

[0253] The method for determining the association 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] This embodiment also provides a device for determining association relationships, which is used to implement the above embodiments and preferred embodiments; details already described will not be repeated. As used below, the term "module" can be a combination of software and / or hardware that implements a predetermined function. Although the device described in the following embodiments is preferably implemented in software, hardware implementation, or a combination of software and hardware, is also possible and contemplated.

[0255] This embodiment provides a device for determining association relationships, such as... Figure 23 As shown, it includes:

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

[0257] The control display module 402 is used to display the control added to the object for the second object if the association status indicates that the first object and the second object have a first association relationship.

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

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

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

[0261] The first display unit is used to respond to the triggering operation of the first object on the object identifier of the second object, display the information interface of the second object, and display the object addition control on the information interface.

[0262] In some alternative 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 to display the object addition control on the information push interface corresponding to the second object.

[0264] In some optional implementations, the push 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 a preset interface associated with the first object.

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

[0268] The first response unit is used to respond to the triggering operation of the first object adding a control to the object and display the verification interface, which 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 the triggering operation of the verification request sending control.

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

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

[0272] The first generation subunit is used to respond to the triggering operation of the control for sending a verification request, generate a verification request according to the verification information, and send it to the second object.

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

[0274] The save unit is used to save the verification information. When the first object triggers the object to add controls again, the saved verification information is displayed in the verification information input area.

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

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

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

[0278] In some alternative embodiments, the above-described apparatus further includes:

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

[0280] The control display module is used to determine, based on the determined result, to display a control or target control for the second object on the information interface of the second object. 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.

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

[0282] The first control display unit is used to display the added control for the second object in the information interface of the second object in response to the determination that the interaction relationship between the first object and the second object meets the preset conditions.

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

[0284] In some optional implementations, the second control 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 used to display a second associated control on the information interface of the second object if a first association relationship exists between the first object and the second object.

[0287] The first display subunit is used to display the first 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.

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

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

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

[0291] The second determining module is used to determine that if the verification result indicates that the second object has failed the verification request, the original first association relationship between the first object and the second object will be maintained. The original first association relationship is used to indicate that the first object does not have permission to access the content published by the second object.

[0292] Further functional descriptions of the above modules and units are the same as those in the corresponding embodiments described above, and will not be repeated here.

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

[0294] The device for determining the association relationship provided in this embodiment allows the first object to initiate a verification request to the second object if it wants to establish a second association relationship with the second object when the first object has a first association relationship with the second object. Based on the verification result generated by the second object in response to the verification request, it determines whether the first object has the permissions associated with the second object. This achieves the requirement that verification is required to determine whether to add the first object as the target associated object, thereby improving the user experience of the application.

[0295] This embodiment provides a device for determining association relationships, such as... Figure 24 As shown, it includes:

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

[0297] The verification result generation module 502 is used to generate the 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 construction module 503 is used to construct a second association 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 can determine the second association between the first object and the second object based on the verification result.

[0299] In some alternative embodiments, the above-described apparatus 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 of the reply control.

[0302] The reply message editing module is used to generate reply messages corresponding to the verification messages in response to message editing operations in the message reply area.

[0303] Further functional descriptions of the above modules and units are the same as those in the corresponding embodiments described above, and will not be repeated here.

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

[0305] The device for determining the association provided in this embodiment enables the second object to provide feedback on the verification request when it receives the verification request from the first object. By combining the verification result provided by the second object, a second association between the first object and the second object is constructed, which further strengthens the method of determining the second association and improves the user experience of the application.

[0306] This disclosure also provides an electronic device having the above-described features. Figure 23 or Figure 24 The apparatus for determining the relationship shown.

[0307] Please see Figure 25 , Figure 25 This is a schematic diagram of the structure of an electronic device provided in an optional embodiment of this disclosure, such as... Figure 25 As shown, the electronic device includes one or more processors 10, memory 20, and interfaces for connecting the components, including high-speed interfaces and low-speed interfaces. The components communicate with each other via different buses and can be mounted on a common motherboard or otherwise as required. The processors can process instructions executed within the electronic device, including instructions stored in or on memory to display graphical information of a GUI on external input / output devices (such as display devices coupled to the interfaces). In some alternative implementations, multiple processors and / or multiple buses can be used with multiple memories and multiple memory modules, if desired. Similarly, multiple electronic devices can be connected, each providing some of the necessary operations (e.g., as a server array, a group of blade servers, or a multiprocessor system). Figure 25 Take a processor 10 as an example.

[0308] Processor 10 may be a central processing unit, a network processor, or a combination thereof. Processor 10 may further include a hardware chip. The hardware chip may be an application-specific integrated circuit (ASIC), a programmable logic device (PLD), or a combination thereof. The programmable logic device may be a complex programmable logic device (CAMP), a field-programmable gate array (FPGA), a general-purpose array logic (GDA), or any combination thereof.

[0309] The memory 20 stores instructions executable by at least one processor 10 to cause the at least one processor 10 to perform the method shown in the above embodiments.

[0310] The memory 20 may include a program storage area and a data storage area. The program storage area may store the operating system and applications required for at least one function; the data storage area may store data created based on the use of the electronic device. Furthermore, the memory 20 may include high-speed random access memory and may also include non-transitory memory, such as at least one disk storage device, flash memory device, or other non-transitory solid-state storage device. In some alternative embodiments, the memory 20 may optionally include memory remotely located relative to the processor 10, and these remote memories may be connected to the electronic device via a network. Examples of such networks include, but are not limited to, the Internet, intranets, local area networks, mobile communication networks, and combinations thereof.

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

[0312] The electronic device also includes an input device 30 and an output device 40. The processor 10, memory 20, input device 30, and output device 40 can be connected via a bus or other means. Figure 25 Taking the example of a connection between China and Israel via a bus.

[0313] Input device 30 can receive input numerical or character information, and generate key signal inputs related to user settings and function control of the electronic device, such as a touch screen, keypad, mouse, trackpad, touchpad, joystick, one or more mouse buttons, trackball, joystick, etc. Output device 40 may include display devices, auxiliary lighting devices (e.g., LEDs), and haptic feedback devices (e.g., vibration motors). The aforementioned display devices include, but are not limited to, liquid crystal displays, light-emitting diodes, displays, and plasma displays. In some alternative embodiments, the display device may be a touch screen.

[0314] The electronic device also includes a communication interface for communicating with other devices or communication networks.

[0315] This disclosure also provides a computer-readable storage medium in which the methods described in this disclosure can be implemented in hardware or firmware, or implemented as recordable on a storage medium, or implemented as computer code originally stored on a remote storage medium or a non-transitory machine-readable storage medium and subsequently stored on a local storage medium after being downloaded over a network. Thus, the methods described herein can be processed by software stored on a storage medium using a general-purpose computer, a dedicated processor, or programmable or dedicated hardware. The storage medium may be a magnetic disk, optical disk, read-only memory, random access memory, flash memory, hard disk, or solid-state drive, etc.; further, the storage medium may also include combinations of the above types of memory. It is understood that computers, processors, microprocessor controllers, or programmable hardware include storage components capable of storing or receiving software or computer code that, when accessed and executed by the computer, processor, or hardware, implements the methods shown in the above embodiments.

[0316] A portion of this disclosure can be applied to computer program products, such as computer program instructions, which, when executed by a computer, can invoke or provide methods and / or technical solutions according to this disclosure through the operation of the computer. Those skilled in the art will understand that the forms in which computer program instructions exist in a computer-readable medium include, but are not limited to, source files, executable files, and installation package files. Accordingly, the ways in which computer program instructions are executed by a computer include, but are not limited to: the computer directly executing the instructions; the computer compiling the instructions and then executing the corresponding compiled program; the computer reading and executing the instructions; or the computer reading and installing the instructions and then executing the corresponding installed program. Here, the computer-readable medium can be any available computer-readable storage medium or communication medium accessible to a computer.

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

Claims

1. A method for determining an association relationship, characterized in that, The method includes: Get the association state between the first object and the second object; If the association status indicates that the first object and the second object have a first association relationship, a control is added to the object for the second object. The first association relationship indicates that the first object and the second object are associated with each other. The first association relationship is configured to be established based on a first request operation between the objects. In response to the second request operation of the first object to add a control to the object, a verification request is generated and sent to the second object; Based on the verification result generated by the second object in response to the verification request, a second association relationship between the first object and the second object is determined. The second association relationship indicates that the first object has permissions associated with the second object, including the permission to access content published by the other party.

2. The method according to claim 1, characterized in that, The display of adding controls to the object of the second object includes at least one of the following: In response to a trigger operation by the first object targeting the object identifier of the second object, an information interface for the second object is displayed, and an object addition control is displayed on the information interface; Display the information push interface associated with the second object, and display the object addition control 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 includes: The information push interface associated with the second object is displayed on the media content stream display interface; The information push interface associated with the second object is displayed on the 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 and sending it to the second object in response to the second object's second request operation of adding a control to the object includes: In response to the second request operation of the first object to add a control to the object, a verification interface is displayed, the verification interface including a verification request sending control; In response to the triggering operation of the control for sending the verification request, 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. The step of generating a verification request and sending it to the second object in response to a trigger operation of the control for sending the verification request includes: In response to an information input operation in the verification information input area, verification information is obtained; In response to the triggering operation of the control for sending the verification request, 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 add 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 remarks input area, and the method further includes: In response to an information input operation in the remarks information input area, remarks information for the second object is obtained; In response to the establishment of a second association between the first object and the second object, the second object is displayed based on the remarks information.

8. The method according to claim 1, characterized in that, Also includes: Determine whether the interaction between the first object and the second object meets preset conditions, and obtain the determination result; Based on the determination result, it is determined that an object-added control or a target control for the second object will be displayed on the information interface of the second object. 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.

9. The method according to claim 8, characterized in that, Based on the determination result, determining to display an object control or target control added to the second object in the information interface of the second object includes: In response to determining that the interaction between the first object and the second object meets the preset conditions, the control for adding objects to the second object is displayed on the information interface of the second object; In response to determining that the interaction association between the first object and the second object meets the preset conditions, the target control is displayed on the information interface of the second object.

10. The method according to claim 9, characterized in that, Displaying the target control on the information interface of the second object includes: Determine whether a first association relationship exists between the first object and the second object; If a first association exists between the first object and the second object, the second association control 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, 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 step of displaying the second associated control on the information interface of the second object includes: The second associated control and the first setting control are displayed in the information interface of the second object; In response to the first object's trigger operation on the first setting control, a first setting interface is displayed, the first setting interface including a preset add control; In response to the first object's trigger operation on the preset added control, the verification request is generated and sent to the second object.

12. The method according to claim 1, characterized in that, Based on the verification result generated by the second object in response to the verification request, a second association relationship between the first object and the second object is determined, including: If the verification result indicates that the second object passes the verification request, then it is determined that a target second association relationship is generated between the first object and the second object, and the target second association relationship is used to indicate that the first object has the permission to access the content published by the second object; If the verification result indicates that the second object failed the verification request, then it is determined that the original first association relationship is maintained between the first object and the second object. The original first association relationship is used to indicate that the first object does not have permission to access the content published by the second object.

13. A method for determining a second association relationship, characterized in that, The method includes: The system receives a verification request initiated by the first object in performing a second application operation and displays the verification request on the associated object application interface. The first object and the second object have a first association relationship, which indicates that the first object and the second object are associated with each other. The first association relationship is configured to be established based on the first application operation between the objects. In response to the feedback operation of the second object on the verification request, a verification result corresponding to the verification request is generated; Based on the verification result, a second association relationship is constructed between the first object and the second object, 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; the second association relationship indicates that the first object has permissions associated with the second object, and the associated permissions include the permission to access the content published by the other party.

14. The method according to claim 13, characterized in that, Also includes: If the verification request carries verification information, a response control is displayed in the area where the verification request is located. In response to a trigger operation on the reply control, a message reply area is displayed; 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 includes: The acquisition module is used to obtain the association status between the first object and the second object; The control display module is used to display an object added to the second object if the association status indicates that the first object and the second object have a first association relationship. The first association relationship indicates that the first object and the second object are associated with each other. The first association relationship is configured to be established based on a first application operation between the objects. The verification request sending module is used to generate a verification request and send it to the second object in response to the second application operation of the first object to add a control to the object; The second association determination module is used to determine a second association between the first object and the second object based on the verification result generated by the second object in response to the verification request. The second association indicates that the first object has permissions associated with the second object, and the associated permissions include the permission to access content published by the other party.

16. A device for determining an association relationship, characterized in that, The device includes: The verification request receiving module is used to receive a verification request initiated by the first object when performing a second application operation, and to display the verification request on the associated object application interface. The first object and the second object have a first association relationship, which indicates that the first object and the second object are associated with each other. The first association relationship is configured to be established based on the first application operation between the objects. The verification result generation module 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. The second association construction module is used to construct a second association 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 between the first object and the second object based on the verification result; the second association indicates that the first object has permissions associated with the second object, and the associated permissions include the permission to access the content published by the other party.

17. An electronic device, characterized in that, include: A memory and a processor are communicatively connected, the memory storing computer instructions, and the processor executing the computer instructions to perform the method for determining the association relationship according to any one of claims 1 to 12, or the method for determining the association relationship according to any one of claims 13 to 14.

18. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer instructions for causing a computer to perform the method for determining the association relationship according to any one of claims 1 to 12, or the method for determining the association relationship according to any one of claims 13 to 14.

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

Images