An information processing method and apparatus

Abstract

This application discloses an information processing method applied to a client corresponding to a first user. The first user and the second user are both members of a first organization's address book. A second user set is configured such that users in the first user set cannot send conversation messages to users in the second user set. The first user belongs to the first user set, and the second user belongs to the second user set. The client corresponding to the first user can display an associated page for the second user. This associated page includes a first request control used to request a conversation with the second user. In response to an operation triggered by the first request control, a conversation request message is sent to the client corresponding to the second user, indicating that the first user requests a conversation with the second user. This solution can improve the efficiency of conversational communication between the first user and the second user.

Description

Technical Field

[0001] This application relates to the field of computer technology, and in particular to an information processing method and apparatus. Background Technology

[0002] To facilitate collaboration and communication among users, some applications have emerged. These applications may include an organizational address book, which can contain multiple members. Members belonging to the same organizational address book can communicate through the application.

[0003] However, currently, when members of the same organization's address book use this application for conversational communication, there is a problem of low communication efficiency. Therefore, there is an urgent need for a solution to address this issue. Summary of the Invention

[0004] To solve, or at least partially solve, the above-mentioned technical problems, this application provides an information processing method and apparatus.

[0005] In a first aspect, embodiments of this application provide an information processing method applied to a client corresponding to a first user, the method comprising:

[0006] The association page of the second user is displayed. The association page includes a first application control. The first application control is used to apply for a session with the second user. The first user and the second user are both members of the first organization's address book. The second user set is configured such that users in the first user set cannot send session messages to users in the second user set. The first user belongs to the first user set, and the second user belongs to the second user set.

[0007] In response to an operation triggered by the first request control, a session request message is sent to the client corresponding to the second user, the session request message indicating that the first user requests to have a session with the second user.

[0008] Optionally, after sending a session request message to the client corresponding to the second user, the method further includes:

[0009] Change the state of the first application control to an untriggerable state, or cancel the display of the first application control.

[0010] Optionally, the method further includes:

[0011] Display a first prompt message, which indicates the conditions that must be met to trigger the first application control again.

[0012] Optionally, the conditions required to trigger the first application control again include:

[0013] The time interval between the first moment when the first application control is triggered again and the second moment when the first application control is triggered again is greater than or equal to a preset time interval.

[0014] Optionally, if the first user's client sent a session request message to the second user's client before a preset time period, the method further includes the following steps before sending the session request message to the client corresponding to the second user:

[0015] A second prompt message is displayed, which prompts the user to confirm whether to send the session request message again;

[0016] Sending a session request message to the client corresponding to the second user includes:

[0017] In response to the confirmation operation triggered by the second prompt message, a session request message is sent to the client corresponding to the second user.

[0018] Optionally, sending a session request message to the client corresponding to the second user includes:

[0019] The robot assistant sends the session request message to the client corresponding to the second user.

[0020] Optionally, displaying the associated page for the second user includes:

[0021] The system displays an information display page for the second user, which is used to display at least one attribute information of the second user and at least one interactive control for triggering interaction with the second user.

[0022] Optionally, the at least one interactive control includes a first interactive control for initiating a session, and the method further includes:

[0023] In response to a triggering operation on the first interactive control, a third prompt message is displayed, which is used to prompt the first user that they cannot send a session message to the second user.

[0024] Optional,

[0025] The first user is configured to send a session request message to the second user.

[0026] Optionally, displaying the associated page for the second user includes:

[0027] The historical conversation page between the first user and the second user is displayed. A fourth prompt message is displayed in a preset area of ​​the historical conversation page. The fourth prompt message is used to prompt the first user that they cannot have a conversation with the second user, and that the first user can request to have a conversation with the second user.

[0028] The method further includes:

[0029] In response to the second user accepting the session request message, the display of the fourth prompt message is cancelled.

[0030] Secondly, embodiments of this application provide an information processing method applied to a client corresponding to a second user, the method comprising:

[0031] A session request message is displayed, indicating that a first user requests a session with a second user. The first user and the second user are both members of a first organization's address book. The second user set is configured such that users in the first user set cannot send session messages to users in the second user set. The first user belongs to the first user set, and the second user belongs to the second user set.

[0032] In response to the accept operation triggered by the session request message, a first indication message is sent to the server, the first indication message indicating that the second user has accepted the session request of the first user.

[0033] Optionally, the display session request message includes:

[0034] The session request message is displayed on the page corresponding to the robot assistant, wherein the robot assistant sends the session request message to the client corresponding to the second user.

[0035] Optionally, the display session request message may also include:

[0036] The session request message sent by the robot assistant is displayed in the second user's information stream, along with a new message notification.

[0037] Optionally, the method further includes:

[0038] In response to a first operation triggered by a second user on the first user's associated page, a second indication message is sent to the server. The second indication message is used to instruct the second user to trigger a withdrawal operation in response to the acceptance operation.

[0039] Thirdly, embodiments of this application provide an information processing apparatus applied to a client corresponding to a first user, the apparatus comprising:

[0040] The first display unit is used to display the associated page of the second user. The associated page includes a first application control, which is used to apply for a conversation with the second user. The first user and the second user are both members of the first organization's address book. The second user set is configured such that users in the first user set cannot send conversation messages to users in the second user set. The first user belongs to the first user set, and the second user belongs to the second user set.

[0041] The sending unit is configured to send a session request message to the client corresponding to the second user in response to an operation triggered by the first request control. The session request message indicates that the first user requests to have a session with the second user.

[0042] Optionally, the device further includes:

[0043] The processing unit is configured to, after sending a session request message to the client corresponding to the second user, change the state of the first request control to an untriggerable state, or cancel the display of the first request control.

[0044] Optionally, the device further includes:

[0045] The second display unit is used to display the first prompt information, which is used to prompt the conditions that need to be met to trigger the first application control again.

[0046] Optionally, the conditions required to trigger the first application control again include:

[0047] The time interval between the first moment when the first application control is triggered again and the second moment when the first application control is triggered again is greater than or equal to a preset time interval.

[0048] Optionally, if the first user's client sent a session request message to the second user's client before a preset time period, the device further includes:

[0049] The third display unit is used to display a second prompt message before sending a session request message to the client corresponding to the second user. The second prompt message is used to prompt the user to confirm whether to send the session request message again.

[0050] The transmitting unit is used for:

[0051] In response to the confirmation operation triggered by the second prompt message, a session request message is sent to the client corresponding to the second user.

[0052] Optionally, the sending unit is used for:

[0053] The robot assistant sends the session request message to the client corresponding to the second user.

[0054] Optionally, the first display unit is used for:

[0055] The system displays an information display page for the second user, which is used to display at least one attribute information of the second user and at least one interactive control for triggering interaction with the second user.

[0056] Optionally, the at least one interactive control includes a first interactive control for initiating a session, and the device further includes:

[0057] The fourth display unit is used to display a third prompt message in response to a trigger operation on the first interactive control. The third prompt message is used to prompt the first user that it cannot send a session message to the second user.

[0058] Optional,

[0059] The first user is configured to send a session request message to the second user.

[0060] Optionally, the first display unit is used for:

[0061] The historical conversation page between the first user and the second user is displayed. A fourth prompt message is displayed in a preset area of ​​the historical conversation page. The fourth prompt message is used to prompt the first user that they cannot have a conversation with the second user, and that the first user can request to have a conversation with the second user.

[0062] The device further includes:

[0063] The cancellation display unit is used to cancel the display of the fourth prompt information in response to the second user accepting the session request message.

[0064] Fourthly, embodiments of this application provide an information processing apparatus applied to a client corresponding to a second user, the apparatus comprising:

[0065] The display unit is used to display a session request message, which indicates that a first user requests a session with a second user. The first user and the second user are both members of a first organization's address book. The second user set is configured such that users in the first user set cannot send session messages to users in the second user set. The first user belongs to the first user set, and the second user belongs to the second user set.

[0066] The first sending unit is configured to send a first indication message to the server in response to an acceptance operation triggered by the session request message. The first indication message is used to indicate that the second user has accepted the session request of the first user.

[0067] Optionally, the display unit is used for:

[0068] The session request message is displayed on the page corresponding to the robot assistant, wherein the robot assistant sends the session request message to the client corresponding to the second user.

[0069] Optionally, the display unit is further configured to:

[0070] The session request message sent by the robot assistant is displayed in the second user's information stream, along with a new message notification.

[0071] Optionally, the device may also include:

[0072] The second sending unit is used to send a second indication message to the server in response to a first operation triggered by the second user on the associated page of the first user. The second indication message is used to indicate that the second user has triggered a withdrawal operation in response to the acceptance operation.

[0073] Fifthly, embodiments of this application provide an apparatus, the apparatus including a processor and a memory;

[0074] The processor is configured to execute instructions stored in the memory to cause the device to perform the method described in any of the first aspects above, or to cause the device to perform the method described in any of the second aspects above.

[0075] In a sixth aspect, embodiments of this application provide a computer-readable storage medium including instructions that instruct a device to perform the method described in any of the first aspects above, or that instruct a device to perform the method described in any of the second aspects above.

[0076] In a seventh aspect, embodiments of this application provide a computer program product that, when run on a computer, causes the computer to perform the method described in any of the first aspects above, or causes the computer to perform the method described in any of the second aspects above.

[0077] Compared with the prior art, the embodiments of this application have the following advantages:

[0078] This application provides an information processing method that can be applied to a client corresponding to a first user. The first user and the second user are both members of a first organization's address book. A second user set is configured such that users in the first user set cannot send conversation messages to users in the second user set. The first user belongs to the first user set, and the second user belongs to the second user set; in other words, the first user cannot send conversation messages to the second user. In this case, the client corresponding to the first user can display an associated page for the second user. This associated page includes a first request control, which is used to request a conversation with the second user. The user can trigger an operation on the first request control. Correspondingly, the client corresponding to the first user can respond to the operation triggered by the first request control by sending a conversation request message to the client corresponding to the second user. The conversation request message indicates that the first user requests a conversation with the second user. Therefore, using this solution, even when the first user cannot send conversation messages to the second user, the first user can trigger a corresponding operation on the associated page of the second user to request to send a conversation message to the second user. Using this solution, the first user can request to send a conversation message to the second user whenever needed. This solution is more efficient and convenient than having administrators change the relevant configurations. Therefore, this solution can improve the efficiency of conversational communication between the first user and the second user.

[0079] This application provides an information processing method that can be applied to a client corresponding to a second user. The first user and the second user are both members of a first organization's address book. The second user set is configured such that users in the first user set cannot send conversation messages to users in the second user set. The first user belongs to the first user set, and the second user belongs to the second user set; in other words, the first user cannot send conversation messages to the second user. In one example, the client corresponding to the second user can display a conversation request message, indicating that the first user requests a conversation with the second user. The second user can trigger an acceptance operation in response to the conversation request message. Correspondingly, the client corresponding to the second user can send a first indication message to the server in response to the acceptance operation triggered by the conversation request message. The first indication message indicates that the second user has accepted the first user's conversation request. After the second user triggers the acceptance operation in response to the conversation request message, the first user can then send conversation messages to the second user. Therefore, using this solution, even when the first user cannot send conversation messages to the second user, if the second user triggers an acceptance operation in response to the aforementioned conversation request message, the first user can then send conversation messages to the second user, enabling the first user to communicate with the second user. This solution is more efficient and convenient than having administrators change the relevant configurations. Therefore, this solution can improve the efficiency of conversational communication between the first user and the second user. Attached Figure Description

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

[0081] Figure 1 A signaling interaction diagram of an information processing method provided in an embodiment of this application;

[0082] Figure 2a A schematic diagram of an information display page for a second user provided in an embodiment of this application;

[0083] Figure 2b A schematic diagram of yet another information display page for a second user provided in an embodiment of this application;

[0084] Figure 2c A schematic diagram of a session page provided in an embodiment of this application;

[0085] Figure 2d A schematic diagram of yet another type of session page provided in an embodiment of this application;

[0086] Figure 3 A flowchart illustrating an information processing method provided in an embodiment of this application;

[0087] Figure 4 A flowchart illustrating another information processing method provided in an embodiment of this application;

[0088] Figure 5 This is a schematic diagram of the structure of an information processing device provided in an embodiment of this application;

[0089] Figure 6 This is a schematic diagram of the structure of another information processing device provided in the embodiments of this application;

[0090] Figure 7 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Detailed Implementation

[0091] To enable those skilled in the art to better understand the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present application, and not all embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative effort are within the scope of protection of the present application.

[0092] The inventors of this application discovered through research that members belonging to the same organization's address book can send conversational messages to each other. For example, if user A and user B are members of the same organization's address book, then user A can send conversational messages to user B, and user B can also send conversational messages to user A.

[0093] However, this approach doesn't provide a good user experience. For example, although users A and B are members of the same organization's address book, they generally don't need to have conversations. Therefore, if user A sends a conversation message to user B, it will cause some interference for user B. Conversely, if user B sends a conversation message to user A, it will cause some interference for user A.

[0094] To avoid the aforementioned problems, administrators can configure members within the same organization's address book accordingly. For example, they can configure members from two departments with no overlap in their work to not initiate conversations with each other, or they can configure individual members to not initiate conversations, such as preventing user A from sending conversation messages to user B. Furthermore, considering that the conversation needs between members within the same organization's address book may change, administrators can adaptively modify the relevant configurations for these members when their conversation needs change. For example, if user A needs to have a conversation with user B, administrators can change user A's configuration to allow user A to send conversation messages to user B.

[0095] However, using administrators to change configurations is inefficient, which in turn prevents users from communicating in a timely manner, resulting in low efficiency in user communication.

[0096] To address the aforementioned problems, this application provides an information processing method and apparatus.

[0097] The various non-limiting embodiments of this application will now be described in detail with reference to the accompanying drawings.

[0098] Exemplary methods

[0099] See Figure 1 This figure is a signaling interaction diagram of an information processing method provided in an embodiment of this application. In this embodiment, the method may include, for example, the following steps: S101-S102.

[0100] S101: The client corresponding to the first user displays the associated page of the second user, which includes a first application control for applying to have a session with the second user.

[0101] In this embodiment, both the first user and the second user are members of the first organization's address book. For members of the first organization's address book, the second user set is configured such that users in the first user set cannot send session messages to users in the second user set. The second user set includes at least one member of the first organization's address book, and the first user set also includes at least one member of the first organization's address book. The first user set and the second user set have no overlap. In one example, the first user belongs to the first user set, and the second user belongs to the second user set. That is, the first user cannot send session messages to the second user.

[0102] In one example, the client corresponding to the first user can obtain first configuration information from the server. The first configuration information indicates that the second user set is configured such that users in the first user set cannot send session messages to users in the second user set. Based on the first configuration information, the client corresponding to the first user can determine that the first user cannot send session messages to the second user, thereby preventing the first user from sending session messages to the second user through the client corresponding to the first user.

[0103] If the first user cannot send a session message to the second user, the client corresponding to the first user can display the associated page of the second user. The associated page displays a first application control for requesting a session with the second user. The first user can trigger the corresponding operation through the first application control to request to send a session message to the second user.

[0104] In one example, the first user can be configured to send a session request message to the second user. Accordingly, the client corresponding to the first user, upon determining that the first user can be configured to send a session request message to the second user, can display the aforementioned first request control on the associated page of the second user. As an example, the client corresponding to the first user can obtain second configuration information from the server. This second configuration information indicates that the first user can be configured to send a session request message to the second user. Accordingly, the client corresponding to the first user can display the first request control on the associated page of the second user based on the second configuration information.

[0105] In this embodiment, the associated page of the second user refers to a page related to the second user. As an example, the associated page of the second user could be the second user's information display page, which may include at least one attribute of the second user, such as the second user's username, avatar, and department. Additionally, the second user's information display page may also include at least one interactive control for interacting with the second user.

[0106] In one example, the at least one interactive control may include a first interactive control for initiating a session. The first control for initiating a session, as mentioned herein, may be a control for triggering the display of an instant messaging session page with a second user, which can be used to send session messages. In this scenario, if the first user cannot send a session message to the second user, and the first user triggers an operation on the first interactive control, for example, by clicking the first interactive control, the client corresponding to the first user can respond to the triggering operation on the first interactive control by displaying a third prompt message. This third prompt message indicates that the first user cannot send a session message to the second user. Thus, based on this third prompt message, the first user can determine that they cannot send a session message to the second user, and accordingly, the first user can perform a next operation, for example, by triggering an operation on the first request control to request to send a session message to the second user.

[0107] In addition to the aforementioned first interactive control, the at least one interactive control may also include other interactive controls. For example, it may include a second interactive control for initiating a video call, or a third interactive control for initiating a voice call, etc., which will not be described in detail here.

[0108] In another example, if the first user has previously had a conversation with the second user, the associated page for the second user could be the historical conversation page between the first and second users, which could include historical conversation messages between the first and second users. In one example, a preset area of ​​the historical conversation page could display a fourth prompt message, which indicates that the first user cannot have a conversation with the second user, but that the first user can request to have a conversation with the second user. In this way, based on this fourth prompt message, the first user can determine that they cannot currently send conversation messages to the second user, but can request to send conversation messages to the second user, thus allowing the first user to perform the next operation, such as triggering an operation on a first request control to request to send conversation messages to the second user.

[0109] This application does not specifically limit the preset area. The preset area can be any area in the history session page. For example, the preset area can be the top area of ​​the history session page.

[0110] In one example, when the second user's associated page is the history session page, the aforementioned first application control can also be displayed in the preset area. In this way, the aforementioned fourth prompt message and the first application control are in the same area, allowing the first user to trigger an operation on the first application control located in the same area as the fourth prompt message after viewing it.

[0111] S102: In response to the operation triggered by the first request control, the client corresponding to the first user sends a session request message to the client corresponding to the second user. The session request message indicates that the first user requests to have a session with the second user.

[0112] The first user can trigger an operation on the first application control in the aforementioned associated page; for example, the first user can click on the first application control. Correspondingly, the client corresponding to the first user can send a session request message to the client corresponding to the second user in response to the operation triggered by the first application control. This session request message instructs the first user to request a session with the second user. Specifically, the first user's request to establish a session with the second user can be expressed as the first user requesting to send a session message to the second user.

[0113] This application does not specifically limit the message format and message content of the session request message. In one example, the session request message may include the user identifier of the first user.

[0114] In another example, the client corresponding to the first user can display an information input interface in response to an operation triggered by the first request control. The first user can enter content in the information input interface, for example, a reason for requesting a session with the second user. Furthermore, the first user can trigger a confirmation operation based on the content entered in the information input interface, and the client corresponding to the first user can retrieve the content entered in the information input interface in response to the confirmation operation. In this case, the communication request message may include the content entered by the first user in the information input interface.

[0115] In one example, the client corresponding to the first user can directly send the session request message to the client of the second user.

[0116] In yet another example, the client corresponding to the first user can send the session request message to the client corresponding to the second user through the server.

[0117] In yet another example, the client corresponding to the first user can send the session request message to the client corresponding to the second user via a robot assistant. In one example, the robot assistant can be understood as a special user that can send at least one type of notification message to all members in the first organization's address book, wherein the at least one type of notification message includes a session request message.

[0118] As described above, in this embodiment, when the first user cannot send a session message to the second user, the first user can trigger a corresponding operation on the second user's associated page to request to send a session message to the second user. This solution is more efficient and convenient than having administrators change related configurations; therefore, it can improve the efficiency of session communication between the first and second users.

[0119] In one example, to avoid interfering with the second user by having the client corresponding to the first user frequently send session request messages to the client corresponding to the second user, the client corresponding to the first user can change the state of the first request control to an untriggerable state or cancel the display of the first request control after sending the session request message to the client corresponding to the second user. This prevents the user from continuing to trigger operations on the first request control, thus preventing the client corresponding to the first user from continuing to send the session request messages to the client corresponding to the second user.

[0120] In one example, changing the state of the first application control to an untriggerable state can be understood as the client corresponding to the first user no longer responding to the triggering operation of the first application control after the first user triggers an operation on the first application control.

[0121] In one example, to fulfill the need for a first user to send a session message to a second user, if the session request message sent by the client corresponding to the first user to the client corresponding to the second user is not accepted by the second user, the first user can be allowed to trigger the first request control again, thereby enabling the client corresponding to the first user to send the session request message to the client corresponding to the second user again. In this scenario, in one example, besides changing the state of the first request control to an untriggerable state or canceling its display, the client corresponding to the first user can also display a first prompt message. For example, the first prompt message can be displayed in the display area corresponding to the first request control on the associated page, indicating the conditions that must be met to trigger the first request control again. In this way, the first user can determine when to trigger the first request control again based on the first prompt message, thereby requesting to send a session message to the second user again.

[0122] This application embodiment does not specifically limit the conditions that need to be met for the first application control to be triggered again. The conditions that the first application control needs to meet can be determined according to the actual situation.

[0123] In one example, the condition for re-triggering the first request control can be a time interval between the first moment the first request control is triggered again and the second moment the first request control is triggered again, which is greater than or equal to a preset time interval. This embodiment does not specifically limit the preset time interval; it can be determined based on actual circumstances, for example, the preset time interval could be 12 hours. This approach ensures that the client corresponding to the second user will not frequently receive session request messages from the client of the first user within the preset time interval, thereby reducing interference to the second user.

[0124] In another example, the condition for triggering the first request control again could be that the session request message is read by the second user. In other words, the first user cannot trigger the first request control again if the second user has not yet read the aforementioned session request message. This approach avoids the second user reading multiple session request messages sent by the client corresponding to the first user while reading unread messages, thus reducing interference for the second user.

[0125] As mentioned earlier, the client corresponding to the first user sending session request messages multiple times to the client corresponding to the second user can cause some interference to the second user. Therefore, if the client corresponding to the first user has sent a session request message to the client corresponding to the second user before a preset time period, the client corresponding to the first user can display a second prompt message before executing S102. The second prompt message is used to prompt the user to confirm whether to send the session request message again. For example, the client corresponding to the first user can display the second prompt message in the form of a pop-up window. If the first user triggers a confirmation operation in response to the second prompt message, the client corresponding to the first user can execute S102. Conversely, if the first user triggers a cancellation operation in response to the second prompt message, the client corresponding to the first user can choose not to execute S102. This approach can effectively reduce the interference to the second user.

[0126] In one example, when the client corresponding to the first user displays the second prompt message, it can also display a confirmation control and a cancellation control corresponding to the second prompt message. The first user can trigger a confirmation operation for the second prompt message through the confirmation control. For example, the first user can click the confirmation control to trigger a confirmation operation for the second prompt message. Similarly, the first user can trigger a cancellation operation for the second prompt message through the cancellation control. For example, the first user can click the cancellation control to trigger a cancellation operation for the second prompt message.

[0127] S103: The client corresponding to the second user displays the session request message.

[0128] After receiving the session request message sent by the client corresponding to the first user, the client corresponding to the second user can display the session request message.

[0129] In one example, the client corresponding to the second user can display the session request message on the page corresponding to the organization's address book.

[0130] In another example, if the client corresponding to the first user sends the session request message to the client corresponding to the second user through the robot assistant, the client corresponding to the second user can display the session request message on the page corresponding to the robot assistant. In this way, the second user can view the session request message through the page corresponding to the robot assistant. In one example, the page corresponding to the robot assistant could be the session page corresponding to the robot assistant.

[0131] In one example, the second user's information stream may include messages sent by multiple other users, and these messages may include the session request message sent by the robot assistant. In this case, in a specific implementation, S103 may display the session request message sent by the robot assistant in the second user's information stream. Displaying the session request message in the second user's information stream can be achieved by displaying the session identifier with the robot assistant in the second user's session list. Additionally, the client corresponding to the second user can also display a new message notification, thereby alerting the second user to the receipt of a new message so that the second user can quickly view the session request message.

[0132] In this embodiment of the application, when the client corresponding to the second user displays the session request message, it may display, for example, the identifier of the first user and the content entered by the first user in the aforementioned information input interface.

[0133] S104: The client corresponding to the second user responds to the acceptance operation triggered by the session request message by sending a first indication message to the server. The first indication message is used to indicate that the second user has accepted the session request of the first user.

[0134] In one implementation, after viewing the session request message, the second user can trigger an acceptance operation for the session request message. In a specific example, when displaying the session request message, the client corresponding to the second user can also display an acceptance control corresponding to the session request message. The second user can trigger a confirmation operation for the session request message through the acceptance control. For example, the second user can click the acceptance control to trigger an acceptance operation for the session request message. After the second user triggers an acceptance operation for the session request message, the client corresponding to the second user responds to the acceptance operation triggered for the session request message by sending first indication information to the server. The first indication information is used to indicate that the second user has accepted the session request from the first user. Correspondingly, the server can send the first indication information to the client corresponding to the first user to indicate that the second user has accepted the session request from the first user. The client corresponding to the first user can determine, based on the first indication information, that the first user can send a session message to the second user.

[0135] In one example, if the second user accepts the first user's session request, the first user can trigger an operation on the first interactive control on the second user's information display page, thereby sending a session message to the second user.

[0136] In another example, if the second user accepts the first user's session request, the first user can send a session message to the second user from the history session page with the second user.

[0137] In one example, if the associated page of the second user is the historical conversation page between the first user and the second user, then after the second user accepts the conversation request from the first user, the client corresponding to the first user can cancel the display of the fourth prompt information displayed in the historical conversation page. In this way, after determining that the historical conversation page does not include the fourth prompt information, the first user can determine that he / she can send a conversation message to the second user.

[0138] In another implementation, after viewing the session request message, the second user can trigger a rejection operation for the session request message. In a specific example, when displaying the session request message, the client corresponding to the second user can also display a rejection control corresponding to the session request message. The second user can trigger a rejection operation for the session request message through the rejection control. For example, the second user can click the rejection control to trigger a rejection operation for the session request message. After the second user triggers a rejection operation for the session request message, the client corresponding to the second user responds to the rejection operation triggered for the session request message by sending a third indication message to the server. The third indication message is used to indicate that the second user has rejected the first user's session request. Correspondingly, the server can send a third indication message to the client corresponding to the first user to indicate that the second user has rejected the first user's session request. The client corresponding to the first user can determine, based on the third indication message, that the first user still cannot send a session message to the second user. In this case, the first user can re-trigger the first request control to request to send a session message to the second user.

[0139] In another implementation, after the second user views the session request message, they can ignore the session request message (neither triggering an accept operation nor a reject operation). In this case, the first user can request to send a session message to the second user again by triggering the first request control again.

[0140] As described above, this solution allows a first user to request to send a session message to a second user whenever needed, and the second user can then decide whether to accept the first user's request. Compared to administrators modifying configurations, this solution is more efficient and convenient, thus improving the efficiency of conversational communication between the first and second users.

[0141] In one example, after the second user triggers an accept operation in response to the communication request message, they can also trigger a first operation on the first user's associated page. This first operation could be a reversal of the accept operation. For example, after the session between the first and second users ends, the second user can trigger the first operation on the first user's associated page. In one example, the second user can trigger the first operation through a relevant control on the first user's associated page; the control that triggers the first operation will not be described in detail here.

[0142] For information on the associated pages for the first user, please refer to the previous section describing the associated pages for the second user; this description will not be repeated here.

[0143] Correspondingly, the client corresponding to the second user can respond to the first operation by sending a second indication message to the server. This second indication message indicates that the second user has triggered a withdrawal operation in response to the accept operation. In one example, the server can send the second indication message to the client corresponding to the first user, and the client can determine, based on this second indication message, that the first user cannot continue sending session messages to the second user.

[0144] The information processing method provided by the embodiments of this application has been described above. Next, with specific examples, the information processing method provided by the embodiments of this application will be described in detail.

[0145] See Figure 2a This figure is a schematic diagram of an information display page for a second user provided in an embodiment of this application. Figure 2a As shown, the information display page 200 includes a conversation message control 201, a voice call control 202, and a video call control 203. The information display page also includes a first application control 204. Additionally, the information display page includes at least one attribute of a second user. Figure 2a The image 205 and username 206 are shown in the image. Figure 2a In this context, the username of the second user is represented by "***".

[0146] In one example, if the first user triggers an operation on the session message control 201, the client corresponding to the first user can display a third prompt message, which is used to prompt the first user that the first user cannot send a session message to the second user.

[0147] The first user can trigger a corresponding operation through the first request control 204, thereby sending a session request message to the client corresponding to the second user. After sending the session request message to the client corresponding to the second user, the information display page 200 is updated. Figure 2b As shown, the first application control 204 is changed to an untriggerable state, and the display area corresponding to the first application control 204 displays the first prompt message "Application has been sent, please try again in 12 hours".

[0148] After the second user triggers an accept operation in response to the session request message, the first user can trigger an operation on the session message control 201 to send a session message to the second user.

[0149] See Figure 2c This figure is a schematic diagram of a session page provided in an embodiment of this application. Figure 2c The shown conversation page is the historical conversation page 300 between the first user and the second user. The top of this historical conversation page 300 displays the second user's avatar 301 and username "XXX". In this historical conversation page 300, 302 represents the first user's avatar. This historical conversation page 300 includes the historical conversation messages between the first user and the second user. Figure 2c The symbols are represented by "***". Additionally, the top area 310 of the conversation window on the history conversation page 300 displays a fourth prompt message, "Unable to send conversation messages to the other party, you can request a conversation," and a first request control 311. Furthermore, 320 on the history conversation page is the conversation message input area.

[0150] The first user can trigger a corresponding operation through the first request control 311, thereby sending a session request message to the client corresponding to the second user. After sending the session request message to the client corresponding to the second user, the historical session page 300 is updated. Figure 2d As shown, the fourth prompt message and the first application control are no longer displayed, and the history session page displays the prompt message "Application accepted, you can send a session message now". Accordingly, the first user can send a session message to the second user on this history session page 300.

[0151] It should be noted that, Figures 2a to 2d This is shown for ease of understanding of the solution and does not constitute a limitation on the embodiments of this application. Figures 2a to 2d The page shown may also include other content, which will not be described in detail here.

[0152] Next, we will introduce the information processing methods executed by the client corresponding to the first user and the client corresponding to the second user.

[0153] See Figure 3 The figure is a flowchart illustrating an information processing method provided in an embodiment of this application. Figure 3The information processing method described herein can be applied to the client corresponding to the first user, and the method may include, for example, the following steps S201-S202.

[0154] S201: Display the association page of the second user, which includes a first application control. The first application control is used to apply for a session with the second user. The first user and the second user are both members of the first organization's address book. The second user set is configured such that users in the first user set cannot send session messages to users in the second user set. The first user belongs to the first user set, and the second user belongs to the second user set.

[0155] S202: In response to the operation triggered by the first request control, a session request message is sent to the client corresponding to the second user, the session request message indicating that the first user requests to have a session with the second user.

[0156] For the specific implementation details of S201-S202, please refer to the relevant descriptions of S101-S102 above; they will not be repeated here. Additionally, for other operations performed by the client corresponding to the first user, please refer to the descriptions of the method steps performed by the client corresponding to the first user above; they will not be repeated here.

[0157] Therefore, even when the first user cannot send conversation messages to the second user, the first user can trigger a corresponding operation on the second user's associated page to request to send conversation messages to the second user. Using this solution, the first user can request to send conversation messages to the second user whenever needed. This solution is more efficient and convenient than having administrators change relevant configurations, thus improving the efficiency of conversational communication between the first and second users.

[0158] See Figure 4 The figure is a flowchart illustrating another information processing method provided in an embodiment of this application. Figure 4 The information processing method described herein can be applied to the client corresponding to the second user, and the method may include, for example, the following steps S301-S302.

[0159] S301: Display a session request message, which indicates that a first user requests a session with a second user. The first user and the second user are both members of a first organization's address book. The second user set is configured such that users in the first user set cannot send session messages to users in the second user set. The first user belongs to the first user set, and the second user belongs to the second user set.

[0160] S302: In response to the accept operation triggered by the session request message, send a first indication message to the server, the first indication message being used to indicate that the second user has accepted the session request of the first user.

[0161] For the specific implementation details of S301-S302, please refer to the relevant descriptions of S103-S104 above; they will not be repeated here. Additionally, for other operations performed by the client corresponding to the second user, please refer to the descriptions of the method steps performed by the client corresponding to the second user above; they will not be repeated here.

[0162] Therefore, using this solution, even if the first user cannot send a session message to the second user, if the second user triggers an accept operation on the aforementioned session request message, the first user can then send a session message to the second user, enabling the first user to communicate with the second user. This solution is more efficient and convenient than requiring administrators to change relevant configurations; therefore, it can improve the efficiency of session communication between the first and second users.

[0163] Exemplary device

[0164] Based on the methods provided in the above embodiments, this application also provides a corresponding device, which will be described below with reference to the accompanying drawings.

[0165] See Figure 5 This figure is a schematic diagram of the structure of an information processing device provided in an embodiment of this application. Figure 5 The information processing device 500 shown can be applied to the client corresponding to the first user. The device 500 includes: a first display unit 501 and a sending unit 502.

[0166] The first display unit 501 is used to display the associated page of the second user. The associated page includes a first application control, which is used to apply for a conversation with the second user. The first user and the second user are both members of the first organization's address book. The second user set is configured such that users in the first user set cannot send conversation messages to users in the second user set. The first user belongs to the first user set, and the second user belongs to the second user set.

[0167] The sending unit 502 is configured to send a session request message to the client corresponding to the second user in response to an operation triggered by the first request control. The session request message indicates that the first user requests to have a session with the second user.

[0168] Optionally, the device further includes:

[0169] The processing unit is configured to, after sending a session request message to the client corresponding to the second user, change the state of the first request control to an untriggerable state, or cancel the display of the first request control.

[0170] Optionally, the device further includes:

[0171] The second display unit is used to display the first prompt information, which is used to prompt the conditions that need to be met to trigger the first application control again.

[0172] Optionally, the conditions required to trigger the first application control again include:

[0173] The time interval between the first moment when the first application control is triggered again and the second moment when the first application control is triggered again is greater than or equal to a preset time interval.

[0174] Optionally, if the first user's client sent a session request message to the second user's client before a preset time period, the device further includes:

[0175] The third display unit is used to display a second prompt message before sending a session request message to the client corresponding to the second user. The second prompt message is used to prompt the user to confirm whether to send the session request message again.

[0176] The transmitting unit 502 is used for:

[0177] In response to the confirmation operation triggered by the second prompt message, a session request message is sent to the client corresponding to the second user.

[0178] Optionally, the transmitting unit 502 is used for:

[0179] The robot assistant sends the session request message to the client corresponding to the second user.

[0180] Optionally, the first display unit 501 is used for:

[0181] The system displays an information display page for the second user, which is used to display at least one attribute information of the second user and at least one interactive control for triggering interaction with the second user.

[0182] Optionally, the at least one interactive control includes a first interactive control for initiating a session, and the device further includes:

[0183] The fourth display unit is used to display a third prompt message in response to a trigger operation on the first interactive control. The third prompt message is used to prompt the first user that it cannot send a session message to the second user.

[0184] Optional,

[0185] The first user is configured to send a session request message to the second user.

[0186] Optionally, the first display unit 501 is used for:

[0187] The historical conversation page between the first user and the second user is displayed. A fourth prompt message is displayed in a preset area of ​​the historical conversation page. The fourth prompt message is used to prompt the first user that they cannot have a conversation with the second user, and that the first user can request to have a conversation with the second user.

[0188] The device further includes:

[0189] The cancellation display unit is used to cancel the display of the fourth prompt information in response to the second user accepting the session request message.

[0190] Since the device 500 is the device corresponding to the method executed by the client corresponding to the first user provided in the above method embodiments, the specific implementation of each unit of the device 500 is based on the same concept as the above method embodiments. Therefore, the specific implementation of each unit of the device 500 can be referred to the relevant descriptions in the above method embodiments, and will not be repeated here.

[0191] See Figure 6 This figure is a schematic diagram of the structure of another information processing device provided in an embodiment of this application. Figure 6 The information processing device 600 shown can be applied to the client corresponding to the second user. The device 600 includes: a display unit 601 and a first sending unit 602.

[0192] Display unit 601 is used to display a session request message, which indicates that a first user requests a session with a second user. The first user and the second user are both members of a first organization's address book. The second user set is configured such that users in the first user set cannot send session messages to users in the second user set. The first user belongs to the first user set, and the second user belongs to the second user set.

[0193] The first sending unit 602 is configured to send a first indication message to the server in response to an acceptance operation triggered by the session request message. The first indication message is used to indicate that the second user has accepted the session request of the first user.

[0194] Optionally, the display unit 601 is used for:

[0195] The session request message is displayed on the page corresponding to the robot assistant, wherein the robot assistant sends the session request message to the client corresponding to the second user.

[0196] Optionally, the display unit 601 is further configured to:

[0197] The session request message sent by the robot assistant is displayed in the second user's information stream, along with a new message notification.

[0198] Optionally, the device may also include:

[0199] The second sending unit is used to send a second indication message to the server in response to a first operation triggered by the second user on the associated page of the first user. The second indication message is used to indicate that the second user has triggered a withdrawal operation in response to the acceptance operation.

[0200] Since the device 600 is the device corresponding to the method executed by the client corresponding to the second user provided in the above method embodiments, the specific implementation of each unit of the device 600 is based on the same concept as in the above method embodiments. Therefore, the specific implementation of each unit of the device 600 can be referred to the relevant description in the above method embodiments, and will not be repeated here.

[0201] This application also provides an apparatus, which includes a processor and a memory;

[0202] The processor is used to execute instructions stored in the memory so that the device performs the information processing method described in any of the above method embodiments.

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

[0204] like Figure 7 As shown, the electronic device 700 may include a processing unit (e.g., a central processing unit, a graphics processor, etc.) 701, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 702 or a program loaded from a storage device 708 into a random access memory (RAM) 703. The RAM 703 also stores various programs and data required for the operation of the electronic device 700. The processing unit 701, ROM 702, and RAM 703 are interconnected via a bus 704. An input / output (I / O) interface 705 is also connected to the bus 704.

[0205] Typically, the following devices can be connected to I / O interface 705: input devices 706 including, for example, touchscreens, touchpads, keyboards, mice, cameras, microphones, accelerometers, gyroscopes, etc.; output devices 707 including, for example, liquid crystal displays (LCDs), speakers, vibrators, etc.; storage devices 708 including, for example, magnetic tapes, hard disks, etc.; and communication devices 709. Communication device 709 allows electronic device 700 to communicate wirelessly or wiredly with other devices to exchange data. Although Figure 7 An electronic device 700 with various devices is shown; however, it should be understood that it is not required to implement or possess all of the devices shown. More or fewer devices may be implemented or possessed alternatively.

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

[0207] The electronic device provided in this application embodiment belongs to the same inventive concept as the method provided in the above embodiments. Technical details not described in detail in this embodiment can be found in the above embodiments, and this embodiment has the same beneficial effects as the above embodiments.

[0208] This application provides a computer-readable medium having a computer program stored thereon, wherein the program, when executed by a processor, implements the method described in any of the above embodiments.

[0209] It should be noted that the computer-readable medium described above in this application can be a computer-readable signal medium or a computer-readable storage medium, or any combination of the two. A computer-readable storage medium can be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of a computer-readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer disk, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination thereof. In this application, a computer-readable storage medium can be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system, apparatus, or device. In this application, a computer-readable signal medium can include a data signal propagated in baseband or as part of a carrier wave, carrying computer-readable program code. Such propagated data signals can take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. A computer-readable signal medium can be any computer-readable medium other than a computer-readable storage medium, which can send, propagate, or transmit a program for use by or in connection with an instruction execution system, apparatus, or device. The program code contained on the computer-readable medium can be transmitted using any suitable medium, including but not limited to: wires, optical fibers, RF (radio frequency), etc., or any suitable combination thereof.

[0210] In some implementations, clients and servers can communicate using any currently known or future-developed network protocol such as HTTP (Hypertext Transfer Protocol) and can interconnect with digital data communication (e.g., communication networks) of any form or medium. Examples of communication networks include local area networks (“LANs”), wide area networks (“WANs”), the Internet (e.g., the Internet of Things), and peer-to-peer networks (e.g., ad hoc peer-to-peer networks), as well as any currently known or future-developed networks.

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

[0212] The aforementioned computer-readable medium carries one or more programs, which, when executed by the electronic device, cause the electronic device to perform the aforementioned method.

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

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

[0215] The units described in the embodiments of this application can be implemented in software or in hardware. The name of the unit / module does not necessarily limit the unit itself; for example, a voice data acquisition module can also be described as a "data acquisition module".

[0216] The functions described above in this document can be performed at least in part by one or more hardware logic components. For example, exemplary types of hardware logic components that can be used, without limitation, include: field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), application-specific standard products (ASSPs), system-on-a-chip (SoCs), complex programmable logic devices (CPLDs), and so on.

[0217] In the context of this application, a machine-readable medium can be a tangible medium that may contain or store a program for use by or in conjunction with an instruction execution system, apparatus, or device. A machine-readable medium can be a machine-readable signal medium or a machine-readable storage medium. Machine-readable media can be, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination of the foregoing. More specific examples of machine-readable storage media include electrical connections based on one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fibers, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing.

[0218] Other embodiments of this application will readily occur to those skilled in the art upon consideration of the specification and practice of the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of this application that follow the general principles of this application and include common knowledge or customary techniques in the art not disclosed herein. The specification and examples are to be considered exemplary only, and the true scope and spirit of this application are indicated by the following claims.

[0219] It should be understood that this application is not limited to the precise structure described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope. The scope of this application is limited only by the appended claims.

[0220] The above description is only a preferred embodiment of this application and is not intended to limit this application. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the protection scope of this application.

Claims

1. An information processing method characterized by comprising: The method applied to a client corresponding to a first user comprises: displaying a second user's association page, the association page comprising a first application control for applying for a session with the second user, the first user and the second user belonging to members in a first organization address book of an application program, the first user set and the second user set belonging to a subset of the first organization address book, the second user set being configured such that a user in the first user set cannot send a session message to a user in the second user set, the first user belonging to the first user set, the second user belonging to the second user set, the first user being configured to be able to send a session application message to the second user, the second user association page comprising an information display page of the second user or a historical session page of the first user and the second user; in response to an operation triggered for the first application control, sending a session application message to a client corresponding to the second user, the session application message indicating that the first user requests a session with the second user.

2. The method of claim 1, wherein, After sending the session application message to the client corresponding to the second user, the method further comprises: changing a state of the first application control to an untriggerable state or canceling display of the first application control.

3. The method of claim 2, wherein, The method further comprises: displaying first prompt information for prompting conditions required for retriggering the first application control.

4. The method of claim 3, wherein, The conditions required for retriggering the first application control comprise: a time interval between a first time of retriggering the first application control and a second time of currently triggering the first application control being greater than or equal to a preset time interval.

5. The method of claim 1, wherein, If the client of the first user has sent a session application message to the client of the second user before a preset time period, before sending the session application message to the client corresponding to the second user, the method further comprises: displaying second prompt information for prompting a user to confirm whether to send a session application message again; The method of sending the session application message to the client corresponding to the second user comprises: in response to a confirmation operation triggered for the second prompt information, sending the session application message to the client corresponding to the second user.

6. The method of claim 1, wherein, The method of sending the session application message to the client corresponding to the second user comprises: sending the session application message to the client corresponding to the second user through a robot assistant.

7. The method of claim 1, wherein, The information display page of the second user is used to display at least one attribute information of the second user and at least one interaction control for triggering interaction with the second user.

8. The method of claim 7, wherein, The at least one interaction control comprises a first interaction control for initiating a session, and the method further comprises: in response to a trigger operation for the first interaction control, displaying third prompt information for prompting that the first user cannot send a session message to the second user.

9. The method of claim 1, wherein, The preset area of the historical session page displays fourth prompt information, the fourth prompt information is used for prompting that the first user cannot have a session with the second user, and the first user can apply for having a session with the second user; The method further includes: In response to the session application message being accepted by the second user, the fourth prompt information is stopped from being displayed.

10. An information processing method characterized by comprising: The method applied to a client corresponding to a second user includes: displaying a session application message, the session application message indicating that a first user requests to have a session with the second user, the first user and the second user both belonging to members in a first organization address book of an application program, a first user set and a second user set both belonging to a subset of the first organization address book, the second user set being configured such that a user in the first user set cannot send a session message to a user in the second user set, the first user belonging to the first user set, the second user belonging to the second user set, and the first user being configured to be able to send a session application message to the second user; In response to an acceptance operation triggered for the session application message, sending first indication information to a server, the first indication information being used to indicate that the second user has accepted the session application of the first user.

11. The method of claim 10, wherein, The session application message is displayed in a page corresponding to a robot assistant, and the session application message is sent to a client corresponding to the second user through the robot assistant. The session application message is also displayed in a message stream of the second user, and a new message reminder is displayed.

12. The method of claim 11, wherein, The method further includes: In response to a first operation triggered by the second user in an association page of the first user, sending second indication information to a server, the second indication information being used to indicate that the second user has triggered a withdrawal operation for the acceptance operation.

13. The method of claim 10, wherein, The apparatus applied to a client corresponding to a first user includes: A first display unit is configured to display an association page of a second user, the association page including a first application control, the first application control being used to apply for having a session with the second user, the first user and the second user both belonging to members in a first organization address book of an application program, a first user set and a second user set both belonging to a subset of the first organization address book, the second user set being configured such that a user in the first user set cannot send a session message to a user in the second user set, the first user belonging to the first user set, the second user belonging to the second user set, and the first user being configured to be able to send a session application message to the second user, the association page of the second user including an information display page of the second user or a historical session page of the first user and the second user; 14. An information processing apparatus comprising: A sending unit is configured to send a session application message to a client corresponding to the second user in response to an operation triggered for the first application control, the session application message indicating that the first user requests to have a session with the second user. ​ ​ 15. An information processing apparatus, comprising: The device applied to a client corresponding to a second user comprises: a display unit configured to display a session application message, the session application message indicating that a first user requests to have a session with the second user, the first user and the second user being members of a first organization address book of an application program, a first user set and a second user set being a subset of the first organization address book, the second user set being configured such that a user in the first user set is unable to send a session message to a user in the second user set, the first user belonging to the first user set, the second user belonging to the second user set, and the first user being configured to be able to send a session application message to the second user; a first sending unit configured to send first indication information to a server in response to an acceptance operation triggered for the session application message, the first indication information being used to indicate that the second user accepts the session application of the first user.

16. An apparatus, comprising: The device comprises a processor and a memory; The processor is configured to execute instructions stored in the memory, so that the device performs the method of any one of claims 1-13.

17. A computer-readable storage medium, characterized in that, The instructions instruct the device to perform the method of any one of claims 1-13.

Images