Methods, electronic devices, and storage media for establishing sessions

By introducing a user approval mechanism with designated roles into instant messaging applications, the problem of excessive disturbance to session recipients has been solved, enabling efficient approval of session requests and the establishment of temporary sessions, thus improving the user experience.

CN116980368BActive Publication Date: 2026-11-17TENCENT TECHNOLOGY (SHENZHEN) CO LTD
View PDF 1 Cites 0 Cited by

Patent Information

Application Number
CN202210066815.4
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2022-01-20
Publication Date
2026-11-17
Estimated Expiration
2042-01-20

AI Technical Summary

Technical Problem

In instant messaging applications, users are easily disturbed by the constant stream of conversation messages sent anytime, anywhere, especially for users who have short processing times, such as business or organizational leaders.

Method used

By approving session requests through the client of a user associated with the session recipient and having a designated role, a temporary session is established between the session request initiator and the session recipient, reducing the approval burden and excessive disturbance to the session recipient.

Benefits of technology

This effectively avoids excessive disturbance to the session recipient, reduces the approval pressure of session requests, and improves the efficiency of session requests and user experience.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN116980368B_ABST
    Figure CN116980368B_ABST
Patent Text Reader

Abstract

This application relates to the field of instant messaging technology and discloses a method, electronic device, and storage medium for establishing a session. Applied to a first client where the session requester resides, the method includes: responding to a triggered session request operation by sending a session request, the session request being used to request the establishment of a temporary session between the first client and a second client; the second client refers to the client where the session recipient resides; displaying an approval message, generated after the session request has been approved by a third client, the third client referring to the client of a user associated with the session recipient and having a specified role; the approval message indicating that a temporary session has been established between the first client and the second client; this solution can effectively solve the problem of users being excessively disturbed by session messages in related technologies.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This application relates to the field of instant messaging technology, and more specifically, to a method for establishing a session, an electronic device, and a storage medium. Background Technology

[0002] In instant messaging applications, users can send and receive conversation messages anytime, anywhere, which brings convenience to communication but also presents some problems. For users who have limited time to process conversation messages, the constant influx of messages from other users can easily lead to excessive interruptions. Summary of the Invention

[0003] In view of the above problems, embodiments of this application propose a method for establishing a session, an electronic device, and a storage medium to improve the above problems.

[0004] According to one aspect of the embodiments of this application, a method for establishing a session is provided, applied to a first client where the session requester is located, comprising: in response to a triggered session request operation, sending a session request, the session request being used to request the establishment of a temporary session between the first client and a second client; the second client being the client where the session recipient is located; displaying an approval prompt message, the approval prompt message being generated after a third client approves the session request, the third client being the client where a user associated with the session recipient and having a specified role is located; the approval prompt message being used to indicate that a temporary session between the first client and the second client has been established.

[0005] According to one aspect of the embodiments of this application, a method for establishing a session is provided, applied to a third client, wherein the third client refers to the client of a user associated with a session recipient and having a specified role; the method includes: displaying session request information; the session request is used to request the establishment of a temporary session between a first client and a second client; the first client refers to the client of the session requester, and the second client refers to the client of the session recipient; in response to an approval operation triggered by the session request, sending an approval instruction to a server; after receiving the approval instruction, the server establishes a temporary session between the first client and the second client, and sends an approval prompt message to the first client; the approval prompt message is used to indicate that a temporary session between the first client and the second client has been established.

[0006] According to one aspect of the embodiments of this application, a method for establishing a session is provided, comprising: receiving a session request sent by a first client, the session request being used to request the establishment of a temporary session between the first client and a second client; the first client being the client where the session requester is located; the second client being the client where the session recipient is located; forwarding the session request to a third client, the third client being the client where a user associated with the session recipient and having a specified role is located; receiving an approval instruction returned by the third client after approving the session request; in response to the approval instruction, establishing a temporary session between the first client and the second client; sending an approval prompt message to the first client; the approval prompt message being used to indicate that a temporary session between the first client and the second client has been established.

[0007] According to one aspect of the embodiments of this application, an apparatus for establishing a session is provided, applied to a first client where the session requester is located, comprising: a session request sending module, configured to send a session request in response to a triggered session request operation, the session request being used to request the establishment of a temporary session between the first client and a second client; the second client being the client where the session receiver is located; and a prompt information display module, configured to display an approval prompt information, the approval prompt information being generated after a third client approves the session request, the third client being the client where a user associated with the session receiver and having a specified role is located; the approval prompt information being used to indicate that a temporary session has been established between the first client and the second client.

[0008] According to one aspect of the embodiments of this application, an apparatus for establishing a session is provided, applied to a third client, wherein the third client refers to the client of a user associated with a session recipient and having a specified role; the apparatus includes: an information display module for displaying session request information; the session request is used to request the establishment of a temporary session between a first client and a second client; the first client refers to the client of the session requester, and the second client refers to the client of the session recipient; an approval instruction sending module for sending an approval instruction to a server in response to an approval operation triggered by the session request; after receiving the approval instruction, the server establishes a temporary session between the first client and the second client, and sends an approval prompt message to the first client; the approval prompt message is used to indicate that a temporary session between the first client and the second client has been established.

[0009] According to one aspect of the embodiments of this application, an apparatus for establishing a session is provided, comprising: a session request receiving module, configured to receive a session request sent by a first client, the session request being used to request the establishment of a temporary session between the first client and a second client; the first client refers to the client where the session requester is located; the second client refers to the client where the session receiver is located; a forwarding module, configured to forward the session request to a third client, the third client referring to the client where a user associated with the session receiver and having a designated role is located; an approval instruction receiving module, configured to receive an approval instruction returned by the third client after approving the session request; a temporary session establishment module, configured to establish a temporary session between the first client and the second client in response to the approval instruction; and a pass notification message sending module, configured to send a pass notification message to the first client; the pass notification message indicating that a temporary session between the first client and the second client has been established.

[0010] According to one aspect of the embodiments of this application, an electronic device is provided, including: a processor; and a memory storing computer-readable instructions, which, when executed by the processor, implement the method for establishing a session as described above.

[0011] According to one aspect of the embodiments of this application, a computer-readable storage medium is provided that stores computer-readable instructions thereon, which, when executed by a processor, implement the method for establishing a session as described above.

[0012] According to one aspect of the embodiments of this application, a computer program product is provided, including computer instructions that, when executed by a processor, implement the method for establishing a session as described above.

[0013] In this application's solution, if a session with the recipient is required, a session request needs to be initiated for the recipient. After the session request is approved, a temporary session is established between the request initiator and the recipient. This solves the problem in related technologies where users can send session messages to the recipient at any time, causing excessive disruption to the recipient. Furthermore, in this application's solution, the session request is forwarded to a third-party client associated with the recipient and possessing a designated role for approval. This reduces the burden on the recipient, who would otherwise have to spend considerable time approving session requests. Therefore, this solution not only avoids excessive disruption to the recipient but also prevents additional burden on the recipient's session request approval process. Attached Figure Description

[0014] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application. It is obvious that the drawings described below are merely some embodiments of this application, and those skilled in the art can obtain other drawings based on these drawings without any inventive effort.

[0015] Figure 1 This is a schematic diagram of a conversation system according to an embodiment of this application.

[0016] Figure 2 This is a timing diagram illustrating a method for establishing a session according to an embodiment of this application.

[0017] Figure 3A This is a schematic diagram of a chat management page according to an embodiment of this application.

[0018] Figure 3B This is a schematic diagram of an agent settings page according to an embodiment of this application.

[0019] Figure 4 This is a flowchart illustrating a method for establishing a session according to another embodiment of this application.

[0020] Figure 5 This is a schematic diagram of the user interface of a first client according to an embodiment of this application.

[0021] Figure 6 This is a flowchart illustrating a method for establishing a session according to another embodiment of this application.

[0022] Figure 7 This is a schematic diagram of a user interface on a third client according to an embodiment of this application.

[0023] Figure 8 This is a schematic diagram of the user interface of a second client according to an embodiment of this application.

[0024] Figure 9 This diagram illustrates permission configuration using a role-based access control model.

[0025] Figure 10 This is a flowchart illustrating a method for establishing a session according to an embodiment of this application.

[0026] Figure 11 This is a schematic diagram illustrating the handling process of the agent according to an embodiment of this application.

[0027] Figure 12 A comparative diagram is shown between the communication mechanisms in related technologies and the communication mechanism using the solution of this application.

[0028] Figure 13 This is a block diagram illustrating an apparatus for establishing a session according to an embodiment of this application.

[0029] Figure 14 This is a block diagram of an apparatus for establishing a session according to another embodiment of this application.

[0030] Figure 15 This is a block diagram of an apparatus for establishing a session according to another embodiment of this application.

[0031] Figure 16 A schematic diagram of the structure of a computer system suitable for implementing the electronic device of the present application is shown. Detailed Implementation

[0032] Exemplary embodiments will now be described more fully with reference to the accompanying drawings. However, these exemplary embodiments can be implemented in many forms and should not be construed as limited to the examples set forth herein; rather, these embodiments are provided to make this application more comprehensive and complete, and to fully convey the concept of the exemplary embodiments to those skilled in the art.

[0033] Furthermore, the described features, structures, or characteristics can be combined in any suitable manner in one or more embodiments. Numerous specific details are provided in the following description to give a thorough understanding of embodiments of this application. However, those skilled in the art will recognize that the technical solutions of this application can be practiced without one or more of the specific details, or other methods, components, apparatuses, steps, etc., can be employed. In other instances, well-known methods, apparatuses, implementations, or operations are not shown or described in detail to avoid obscuring various aspects of this application.

[0034] The block diagrams shown in the accompanying drawings are merely functional entities and do not necessarily correspond to physically independent entities. That is, these functional entities can be implemented in software, in one or more hardware modules or integrated circuits, or in different network and / or processor devices and / or microcontroller devices.

[0035] The flowcharts shown in the accompanying drawings are merely illustrative and do not necessarily include all content and operations / steps, nor do they necessarily have to be performed in the described order. For example, some operations / steps can be broken down, while others can be combined or partially combined; therefore, the actual execution order may change depending on the specific circumstances.

[0036] It should be noted that "multiple" in this article refers to two or more. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, or B alone. The character " / " generally indicates that the preceding and following related objects have an "or" relationship.

[0037] Instant Messaging (IM) is a communication method that uses a peer-to-peer (P2P) protocol on a computer network platform to enable users to exchange text, audio, and video messages instantly.

[0038] Figure 1 This is a schematic diagram of a session system according to an embodiment of this application. In the scheme of this application, a session request involves at least three parties: the session request initiator, the session receiver, and the user associated with the session receiver and having a designated role. In this application, for ease of distinction, the terminal where the session request initiator is located is referred to as the first terminal 111, the terminal where the session receiver is located is referred to as the second terminal 112, and the terminal where the user associated with the session receiver and having a designated role is located is referred to as the third terminal 113.

[0039] like Figure 1 As shown, the session system includes a first terminal 111, a second terminal 112, a third terminal 113, and a server 120, wherein the first terminal 111, the second terminal 112, and the third terminal 113 are communicatively connected to the server 120. This session system can be used to implement the session establishment method provided in this application.

[0040] The terminals (first terminal 111, second terminal 112, and third terminal 113) can be smartphones, tablets, laptops, desktop computers, in-vehicle terminals, smart TVs, or other electronic devices capable of interacting with users. Applications can run on the terminals; these applications can be instant messaging applications (such as enterprise instant messaging applications) or other applications integrated with instant messaging functionality.

[0041] Because an application needs to be running on the terminal to send instant session messages with other users' terminals based on that application, for ease of distinction, the client logged in using the user ID of the session request initiator is referred to as the first client, the client logged in using the user ID of the session recipient is referred to as the second client, and the client logged in using the user ID corresponding to the user associated with the session recipient and having a specified role is referred to as the third client. It can be understood that the terminal where the first client is located is the first terminal 111, the terminal where the second client is located is the second terminal 112, and the terminal where the third client is located is the third client 113.

[0042] In some embodiments, the user associated with the session receiver and having a specified role can be one or more. In the case of multiple users, the third terminal 113 also corresponds to multiple users.

[0043] The server 120 is used to provide services to instant messaging applications or other applications that integrate instant messaging functions running in the terminals (first terminal 111, second terminal 112 and third terminal 113), such as login service, message forwarding service, user identity management service, etc.

[0044] The server 120 can be a standalone physical server, a server cluster or distributed system composed of multiple physical servers, or a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, CDN (Content Delivery Network), and big data and artificial intelligence platforms.

[0045] The method described in this application will be explained from the server side first.

[0046] Figure 2 This is a timing diagram illustrating a method for establishing a session according to an embodiment of this application. In this application, in a single session request, the client where the session requester is located is referred to as the first client, the client where the session receiver is located is referred to as the second client, and the client where the user associated with the session receiver and having a designated role is located is referred to as the third client. Figure 2 The illustrated embodiments can be applied to the server side, such as... Figure 2 As shown, the method includes: Step 210: Receive a session request sent by the first client. The session request is used to request the establishment of a temporary session between the first client and the second client. The first client refers to the client where the session requester is located. The second client refers to the client where the session receiver is located.

[0047] Step 220: Forward the session request to a third client, which is the client of the user associated with the session recipient and who has a specified role.

[0048] In some embodiments, before step 220, the method further includes: obtaining role configuration information corresponding to the second client; obtaining a specified user identifier of a user with a specified role from the role configuration information; and using the specified user identifier to determine the third client.

[0049] Specifically, the server can obtain the role configuration information corresponding to the second user identifier carried in the session request, that is, the role configuration information corresponding to the second client. This role configuration information may include the user identifier of the user associated with the session recipient and having a specified role, that is, the specified user identifier.

[0050] In some embodiments, users who need to apply for a session beforehand can be pre-configured with associated users and assigned specific roles. For ease of description, the user who needs to apply for a session beforehand is referred to as the first designated user, and the client containing the first designated user is referred to as the second client.

[0051] In some embodiments, a user's status as requiring prior application for a session (i.e., the first designated user) can be determined based on their role. For example, if a user's role includes a target role, then that user is determined to be the first designated user; conversely, if a user's role does not include a target role, then that user is determined not to be the first designated user. The target role can be set according to actual needs. For example, in enterprise instant messaging applications, the target role could be a department head, company head, etc., without specific limitations here. The target role can be one or more, without specific limitations here. A corresponding user identifier with a designated role is pre-set for the first designated user, i.e., the designated user identifier mentioned above. The client where the user indicated by the designated user identifier is located is the third client. In a specific embodiment, the user indicated by the designated user identifier could be the first designated user's secretary, assistant, etc.

[0052] For example, if User A is an employee, User B is a department head, and User C is User B's secretary, then User B can be designated as the first specified user based on their role (i.e., their position), and User C can be designated as a user associated with User B and having a specified role. Based on this, when User A needs to send a session message to User B, User A's client is the first client, User B's client is the second client, and User C's client is the third client. User A's client (the first client) first sends a session request for User B. This request is forwarded by the server to User C's client (the third client), where User C approves the request. If the server determines that User C has approved the request, a temporary session is established between User A's client (the first client) and User B's client (the second client), and an approval message is sent to User A's client, which displays the approval message. Based on this approval message, User A can send a session message to User B's client, and the server, based on the established temporary session, forwards the message to User B's client. In some embodiments, it can be automatically determined whether a user is a user who needs to apply before a session can be initiated (i.e., the first designated user) based on the user's job level. Specifically, a job level threshold can be set; if a user's job level is not lower than the threshold, then the user is determined to be the first designated user. Correspondingly, the user's secretary is identified as a user associated with the first designated user and having a designated role; that is, the client containing the first designated user's secretary is identified as the third client.

[0053] In some embodiments, whether user D2 is the first designated user requiring prior application to initiate a session can also be determined based on the job level of the user initiating the session request (assuming user D1) and the user receiving the session (assuming user D2). Specifically, assuming user D1's job level is K1 and user D2's job level is K2, if job level K2 is not lower than the job level threshold and T is not lower than the difference threshold, where T = K2 - K1, and the difference threshold is a positive integer, then user D2 can be determined as the first designated user when the client where user D1 is located needs to send a session message to the client where user D2 is located; conversely, if job level K2 is lower than the job level threshold and / or T is lower than the difference threshold, then user D2 is not the first designated user relative to user D1. It can be seen that in this embodiment, whether a user is a designated user is dynamically changing relative to the session initiator. That is, if user D2 is the first designated user relative to user D1, user D2 may not be the first designated user relative to user D3, depending on the job levels of user D2 and user D3.

[0054] In some embodiments, the user acting as the administrator can specify the user for the first designated user on the administrator client, thereby adding a specified role to the specified user, making the specified user a user associated with the first designated user and having the specified role; and correspondingly, the user identifier of the specified user (i.e., the specified user identifier below) is associated with the user identifier of the first designated user and added to the role configuration information of the first designated user.

[0055] In some embodiments, whether a user is the first designated user can also be determined based on whether a user with an associated role has been assigned to the user. For example, if a user B with a designated role has been assigned to user A, then user A can be determined to be the first designated user. Conversely, if no user B with a designated role has been assigned to user A, then user A is not the first designated user. In this case, regardless of user A's job level, when a user (let's say user D1) wants to send a session message to user A, if user A is determined not to be the first designated user, then user D1 can directly initiate a session with user A; otherwise, if user A is determined to be the first designated user, then user D1 can only initiate a session with user A after the session request is approved.

[0056] In some embodiments, if it is determined that the session recipient is not the first designated user, then a session can be initiated directly with the session recipient without first requesting a session.

[0057] Step 230: Receive the approval instruction returned by the third client after approving the session application.

[0058] In this application, users with designated roles have the authority to approve session requests. Moreover, by associating users with designated roles with another user (such as the first designated user mentioned above), session requests for the first designated user are approved by the user associated with the first designated user and with the designated role, thus achieving session request routing.

[0059] Step 240: In response to the approval instruction, establish a temporary session between the first client and the second client.

[0060] Specifically, establishing a temporary session between the first client and the second client is equivalent to granting the first client temporary session permission to communicate with the second client.

[0061] In some embodiments, if the permission to send session messages to a first designated user is limited and the permission of the first designated user to send session messages to other clients is also limited (i.e., if a temporary session is not established between the first client and the second client, the first client cannot receive session messages sent by the second client, and the second client also cannot receive session messages sent by the first client), then the temporary session permission opened by the server in response to the approval instruction can be a bidirectional session permission between the first client and the second client.

[0062] In other embodiments, if only the permission to send session messages to the first designated user is limited, but the permission of the first designated user to send session messages to other users' clients is not limited (in other words, if the server does not establish a temporary session between the first client and the second client, the session message sent by the second client to the first client can be forwarded by the server to the first client, but the session message sent by the first client to the second client will not be forwarded by the server to the second client), then the temporary session permission granted by the server in response to the approval instruction can be a one-way session permission for the first client to send session messages to the second client.

[0063] Step 250: Send a notification message to the first client; the notification message indicates that a temporary session has been established between the first client and the second client.

[0064] Understandably, the established temporary sessions have a validity period. During the validity period of the established temporary session, session messages sent by the first client to the second client can be forwarded by the server to the second client; furthermore, session messages sent by the second client to the first client can also be forwarded by the server to the first client.

[0065] Conversely, if the validity period of the temporary session has expired, even if the server receives the session message sent by the first client to the second client, it will not forward the session message to the second client; furthermore, the server can also return a sending failure message to the first client.

[0066] Of course, if the first client needs to send a session message to the second client again after the expiration of the temporary session, it needs to request a session again so that the server can re-establish the temporary session between the first client and the second client.

[0067] In this application's solution, if a session with the recipient is required, a session request needs to be initiated for the recipient. After the session request is approved, a temporary session is established between the request initiator and the recipient. This solves the problem in related technologies where users can send session messages to the recipient at any time, causing excessive disruption to the recipient. Furthermore, in this application's solution, the session request is forwarded to a third-party client associated with the recipient and possessing a designated role for approval. This reduces the burden on the recipient, who would otherwise have to spend considerable time approving session requests. Therefore, this solution not only avoids excessive disruption to the recipient but also prevents additional burden on the recipient's session request approval process.

[0068] The solution proposed in this application can be applied to users who have short processing time for session messages, such as users who are heads of enterprises, institutions, or organizations, or users who are department heads. When such users who have short processing time for session messages are the recipients of session requests in this application, the method proposed in this application establishes a temporary session only after the session request has been approved. Since the session approval is performed by a user associated with the session recipient and with a designated role, the user who is the recipient of the session can be avoided from being excessively disturbed.

[0069] In some embodiments, a first control button for session requests can be set in the client. In this case, if a user with a specified role is associated with the first designated user, and the client of the first designated user has the first control button enabled, then if a user (let's say user A) needs to initiate a session with the first designated user, since the client of the first designated user (which is now the second client) has the first control button enabled, it is determined that a session request needs to be initiated first. After establishing a temporary session with the second client, the first client of user A can then initiate a session with the second client. Conversely, even if a user with a specified role is associated with the first designated user, but the client of the first designated user has the first control button disabled, then user A does not need to initiate a session request to initiate a session with the second client. That is, in this case, the session message sent by the client of user A to the client of the first designated user will be forwarded by the server to the client of the first designated user. In this embodiment, since a first control button is set in the client, the first designated user can enable or disable the first control button according to actual needs, thereby determining whether to enable or disable a session request. In this situation, the first designated user can flexibly decide whether to open the first control button based on their own workload. For example, when the workload is heavy, the first control button can be opened, and a temporary session will be established only after the session request is submitted and approved by the associated third client. When the workload is light, the first control button can be closed, so that a session can be initiated with the first designated user without submitting a session request.

[0070] In some embodiments, a second control button can be set on the client side to indicate whether a user with a specified role associated with the first specified user should handle the session messages on behalf of the first specified user. In this case, if the first specified user enables the second control button on the client, after a temporary session is established on the server, the session messages sent from the first client to the second client are also simultaneously sent to the third client. In this case, either the second client or the user associated with the third client can handle the session messages. Of course, in this case, if the third client handles the session messages between the second client and the first client, the session messages sent by the third client to the first client on behalf of the second client are also forwarded to the first client by the server. In this case, since the session messages sent from the first client to the second client are sent to both the third and second clients, even if the session messages are not handled by the first specified user, the first specified user can still know the content of the session between the third client and the first client based on the received session messages, thereby supervising the user of the third client and preventing the user of the third client from abusing the permissions of the first specified user.

[0071] Conversely, if the first designated user closes the second control button on the client, after a temporary session is established on the server, the session messages sent by the first client to the first client will be forwarded by the server to the first client instead of to the third client. Thus, the first designated user will handle the session messages between the first client and the second client on the second client.

[0072] In this embodiment, since a second control button is provided to control whether the session messages are handled by a user with a specified role associated with the first specified user, the first specified user can flexibly choose to handle the session messages with the first client himself or choose to have the session messages with the first client handled by a user with a specified role associated with the first specified user.

[0073] In some embodiments, after step 210, the method further includes: forwarding the session request to a second client; and receiving an approval instruction returned by the second client after approving the session request. In this embodiment, the session request sent by the first client is forwarded not only to the third client but also to the second client. Therefore, the session recipient can also approve the session request on the second client, which can further ensure that the session request is approved in a timely manner.

[0074] In some embodiments, after forwarding the session request to the second client, the method further includes: if an approval rejection instruction is received from a third client after rejecting the session request, or if an approval rejection instruction is received from the second client after rejecting the session request, sending a rejection notification message to the first client. Thus, the session request initiator can be aware that the session request has been rejected based on the rejection notification message received by the first client.

[0075] In some embodiments, after step 240, the method further includes: if a session message is received from the first client to the second client during the validity period of the temporary session, forwarding the session message to the second client.

[0076] In some embodiments, before step 240, the method further includes: during the period when a temporary session between the first client and the second client has not been established, or after the validity period of the temporary session has expired, if a session message sent by the first client to the second client is received, the session message is not forwarded to the second client, and a sending failure prompt message is returned to the first client.

[0077] In this embodiment, the first client can only have a session with the second client within the validity period of the established temporary session, thereby effectively ensuring that the session receiver is not excessively disturbed.

[0078] In some embodiments, session permissions for each user can be pre-configured to identify users who require a session request to initiate a session. Furthermore, for users who require a session request, users associated with that user and holding specific roles can also be defined.

[0079] Figure 3A This is a schematic diagram of a chat management page according to an embodiment of this application, as shown below. Figure 3A As shown, the chat management page 310 includes multiple setting options, such as maximum file size that can be sent, maximum number of group members, message reading status, department groups, chat requests, setting up agents, and custom chat emoticons. Of course, in other embodiments, the setting options in the chat management page 310 may include... Figure 3A The options for more or fewer settings are shown. Figure 3A This is merely an example and should not be considered as a limitation on the scope of this application.

[0080] The "Chat Request" option 311 in the chat management page 310 is used to specify users who need to make a session request before they can have a session. User identifiers can be added to the "Chat Request" option 311. For example, "Li Si" added in 3A indicates that the user is a user who needs to make a session request before they can have a session.

[0081] The "Set Agent" option 312 in the chat management page 310 is used to set an agent role for a user who needs to apply for a session. The agent role is the specified role in this application. After setting it in the "Set Agent" option, the "Agent" role is configured for the user added in the "Set Agent" option 312.

[0082] When the user triggers the "Add" control 313 under the "Set Agent" option 312, they can enter... Figure 3B The agent settings page 320 shown allows users to add users specified under the "Chat Request" option 311, giving these added users the "agent" role. For example... Figure 3B On the agent settings page 320 shown, users are added as agents for the user "Li Si".

[0083] The agent settings page 320 has an "Add Agent" control 321 and a "Delete" control 322. By triggering the "Add Agent" control 321, a user can be added as an agent for a selected user, so that the added user is associated with the specified role of agent. By triggering the "Delete" control 322, an added user as an agent can be deleted.

[0084] In specific embodiments, the number of users added as agents for a single user can be one or more, without specific limitations. For example, in Figure 3B In the game, users named "Shao XX" and "Zhang XX" can both act as agents for "Li Si".

[0085] After completion Figure 3A and Figure 3B After the settings are shown, the user ID specified under the "Chat Request" option 311 will be associated with the user ID added under the "Set Agent" option 312 to obtain the role configuration information corresponding to the user ID specified under the "Chat Request" option 311. This role configuration information will then be sent to the server for storage.

[0086] In a specific embodiment, the action can be performed by the client where the user acting as the administrator is located. Figure 3A and Figure 3B As shown, you can specify users who need to request a session to have a session, and add agents for users who need to request a session to have a session.

[0087] The following description of the method of this application is from the perspective of the client where the session request is initiated (i.e., the first client).

[0088] Figure 4 This is a flowchart illustrating a method for establishing a session according to another embodiment of this application. Figure 4 The illustrated embodiment applies to the first client where the session requester resides. For example... Figure 4 As shown, the method includes: Step 410: In response to the triggered session request operation, a session request is sent. The session request is used to request the establishment of a temporary session between the first client and the second client; the second client refers to the client where the session receiver is located.

[0089] The session request indicates the user identifier of the session recipient. When a user needs to initiate a session with a certain user (who then acts as the session recipient), if the session recipient is a user who requires a session request to conduct a session (such as the user with the target role mentioned above), then a session request operation is triggered for that session recipient, thereby sending a session request. In this application, for ease of distinction, the user who requires a session request before conducting a session is referred to as the first designated user.

[0090] In some embodiments, to help users identify which users are the first designated users, the first designated users can be marked in the client interface, or a session request prompt can be displayed in the session interface with the first designated user. This session request prompt indicates that a session request must be made before a session can be established with the first designated user. Marking the first designated user can be achieved by adding a specific marker to the user identifier of the first designated user (e.g., user avatar, user nickname, etc.).

[0091] In some embodiments, a first control for triggering a session request operation may be displayed in the session interface with the session recipient, so that if an operation triggered by the first control is detected, it is determined that a session request operation has been detected.

[0092] In some embodiments, if it is determined that the session recipient who needs to initiate a session is not a user who needs to apply for a session before initiating a session, the session information can be sent directly to the session recipient, and the server will forward the session information to the client where the session recipient is located.

[0093] In some embodiments, before step 410, the method further includes: displaying a session request window, the session request window being used to input session request information; in this embodiment, step 410 includes: in response to a session request operation triggered in the session request window, sending a session request based on the session request information.

[0094] The session request window is used to enter session request information. This information can be information that facilitates the approval of the session request, such as the reason or matter for requesting the session, etc., without specific limitations. The display format of this session request window is not limited; it can be displayed as a pop-up window or in a designated area of ​​a page.

[0095] In some embodiments, the session request window may include a first control for triggering a session request operation. If a triggering operation (e.g., click, touch, swipe, etc.) is detected on the first control, it is determined that a session request operation has been detected.

[0096] If a user enters session request information in the session request window, the session request will carry the session request information in addition to the user identifier of the session recipient.

[0097] In some embodiments, before displaying the session request window, the method further includes: displaying session request prompt information in the session interface with the session recipient, the session request prompt information including a session request entry; in this embodiment, displaying the session request window includes: displaying the session request window in response to an operation triggered by the session request entry.

[0098] The session request prompt message indicates that a session request must be made before a session can be initiated with the session recipient. Since the session request prompt message includes a session request entry point, the user can trigger this entry point to display the session request window in the user interface of the first client.

[0099] The entry point for a chat request can be a link to the chat request window or a control that triggers entry into the chat request window. In a specific embodiment, a portion of the text in the chat request prompt can be used as the chat request entry point. Thus, by triggering the text used as the chat request entry point, one can enter the chat request window. For example, if the chat request prompt is "You do not have permission to send chat messages to the other party, request to chat," then the text "Request to chat" can be used as the chat request entry point.

[0100] In some embodiments, displaying a session request prompt message in the session interface with the session recipient includes: in response to receiving a sending failure prompt message, displaying a session request prompt message in the session interface with the session recipient, wherein the sending failure prompt message is sent by the server to the first client after receiving a session message sent by the first client to the second client and determining that no temporary session has been established between the first client and the second client.

[0101] If the server receives a session message from the first client to the second client without establishing a temporary session between them, it will not forward the message to the second client. Instead, it will return a sending failure message to the first client. The first client will then respond with a session message sending failure notification. Furthermore, upon receiving the sending failure message, the first client can determine that it needs to initiate a session request with the current session recipient. Therefore, it will display a session request notification in the session interface with the session recipient, prompting the user to initiate a session request with that recipient first.

[0102] Step 420: Display the approval message. The approval message is generated after the session request is approved by the third client. The third client refers to the client of the user associated with the session recipient and who has a specified role. The approval message is used to indicate that a temporary session has been established between the first client and the second client.

[0103] After the first client sends a session request, the session request will be received by the server, which will then forward the session request to the third client, where the user will approve the session request.

[0104] After the server forwards the session request to the third client, if the third client detects a triggered approval operation, it sends an approval command to the server. The server can then establish a temporary session between the first and second clients based on this approval command and send an approval notification to the first client. Thus, based on the approval notification displayed in the first client, the user can know that a temporary session with the second client has been established.

[0105] In some embodiments, the prompt message may be displayed in the session interface between the first client and the session recipient. Of course, in other embodiments, it may also be displayed on a designated page of the first client, and no specific limitation is made here.

[0106] After the server establishes a temporary session between the first client and the second client, during the validity period of the temporary session, the session messages sent by the first client to the second client can be forwarded by the server to the second client.

[0107] In some embodiments, the session request is also sent to a second client, and after the second client approves the session request, an approval message is generated. In other words, in this case, the server can send an approval message to the first client after receiving an approval instruction from the second client or from the third client.

[0108] In some embodiments, after receiving a session request from a first client, the server can simultaneously send the session request to a second client and a third client. In other embodiments, after receiving a session request from the first client, the server can first send the session request to the third client. If no approval instruction (e.g., approval or rejection instruction) is received from the third client within a first set time period, the session request is forwarded to the second client. This ensures that session requests can be approved in a timely manner.

[0109] In some embodiments, after step 410, the method further includes: displaying a rejection message, which is generated after a third client or a second client approves and rejects the session request.

[0110] If a session request is forwarded to a third client, and the server receives an approval rejection instruction from the third client for that session request, then the server will not establish a temporary session between the first client and the second client, and will send a rejection message to the first client so that the rejection message can be displayed in the first client.

[0111] Similarly, if a session request is forwarded to the second client and the third client, and the server receives an approval rejection instruction from the third client or the second client for the session request, then a temporary session between the first client and the second client will not be established, and a rejection message will be sent to the first client to be displayed in the first client.

[0112] In some embodiments, the rejection message may be displayed in the session interface with the session recipient. Of course, the rejection message may also be displayed in other interfaces of the first client, and no specific limitation is made here.

[0113] Figure 5 5A in the diagram is a schematic diagram of a session interface according to an embodiment of the present application. In this embodiment, it is assumed that the session initiator is user A, the session receiver is user B, and the user associated with the session receiver B and having a designated role is user A.

[0114] like Figure 5 As shown in Figure 5A, a sending failure message 511 is displayed in the conversation interface 510 with user B (i.e., Figure 5 The exclamation mark next to the conversation message sent to User B (shown in section 5A) and the conversation request prompt message 512 are displayed. The content of the conversation request prompt message 512 is "You do not have permission to send chat messages to the other party. Request a chat." The "Request a chat" in the conversation request prompt message 512 is the conversation request entry point 513. When the user clicks on the conversation request entry point 513, the following is displayed: Figure 5 The interface diagram shown in Figure 5B.

[0115] like Figure 5 As shown in Figure 5B, in the session request interface 510 with User B, a session request window 520 is displayed as a pop-up window. This window includes an information editing area 521, which displays the session request information entered by the user. Furthermore, the session request window 520 includes a "Cancel" control 522 and a "Send" control 523. If the user clicks the "Send" control 523, they can send a session request based on the entered information; conversely, if the user clicks the "Cancel" control 522, they can cancel sending the session request.

[0116] After a session request is sent to a third client, if the user approves the session request on the third client, the server can send an approval message to the first client. Then, the approval message "530" can be displayed in the session interface between the first client and user B. Figure 5 As shown in 5C, the message 530 reads: "The other party has accepted your request and automatically added you to their contact list. You can start chatting now. View details."

[0117] Furthermore, since the first client automatically adds user B to the favorites list, if user A needs to have another conversation with user B later, user A can trigger user B's identification information (such as user B's avatar, nickname, etc.) from the favorites list to enter the conversation interface with user B.

[0118] Furthermore, the prompt message 530 includes an entry point 531 for viewing approval details. In this embodiment, the entry point 531 for viewing approval details can be the "View Details" text in the prompt message 530. When the user triggers this entry point 531, they can access... Figure 5 The approval details page 540 shown in 5D.

[0119] like Figure 5 As shown in Figure 5D, the approval details page 540 includes a first display area 541, a second display area 542, and a third display area 543. The first display area 541 displays the user information of the session request initiator, such as the username "A" and avatar, as well as the organization information, i.e., "Company / Department / Bureau". The second display area 542 displays the session request information, such as... Figure 5 In section 5D, the message "Because of matter XX, communication with Party B is required, please approve" appears. The third display area, 543, is used to display the approval process for the session request. Figure 5In the 5D section, the user name of the user who initiated the session request and the time when the session request was initiated are shown, as well as the user name of the user who approved the session request, the approval time, approval comments, and approval actions are shown. Among them, the approval comments refer to the opinions entered by the user who approved the session request during the approval process (such as the reasons for rejecting the session request or the reasons for approving the session request). The approval actions refer to the actions of approving or rejecting the session request.

[0120] If a user rejects a session request on a third client, the server can send a rejection message to the first client based on the rejection instruction sent by the third client. The rejection message can then be displayed on the first client.

[0121] Figure 5 5E is a schematic diagram illustrating the display of a rejection prompt message according to an embodiment of this application, such as... Figure 5 As shown in Figure 5E, a rejection message 550 is displayed in the conversation interface with User B. The content of the rejection message 550 is "The other party has rejected your application. View details." Furthermore, the rejection message 550 includes an entry point 531 for viewing approval details, which can be the "View Details" option in the rejection message 550. Triggering this entry point 531 leads to the approval details page 540. The content of the approval details page 540 is as follows... Figure 5 As shown in 5D, it can be understood that the approval action displayed on the approval details page 540, which is accessed through the approval details viewing entry 531 in the rejection prompt message 550, is approval rejection.

[0122] Understandably, if the session request is also forwarded to the second client, the username of the party requesting the approval session displayed on the approval details page 540 may also be the username of the user logged in on the second client.

[0123] The method of this application will now be described from the perspective of the third client.

[0124] Figure 6 This is a flowchart illustrating a method for establishing a session according to another embodiment of this application. Figure 6 The illustrated embodiment applies to a third client, which refers to the client of a user associated with the session recipient and possessing a designated role; such as Figure 6 As shown, the method includes: Step 610: Display the session request information; the session request is used to request the establishment of a temporary session between the first client and the second client; the first client refers to the client where the session requester is located, and the second client refers to the client where the session receiver is located.

[0125] When the third client receives a session request, it displays information related to that session request. This information can be a summary of the session request or detailed information about the session request. The session request information may include the user identifier of the requester (e.g., username (nickname)) and the time the session request was initiated (or the time the third client received the session request). In some embodiments, if the session request was sent by the first client based on user-inputted session request information, the session request information may also include the user-inputted session request information.

[0126] Step 620: In response to the approval operation triggered by the session request, an approval instruction is sent to the server; after receiving the approval instruction, the server establishes a temporary session between the first client and the second client, and sends an approval prompt message to the first client; the approval prompt message is used to indicate that a temporary session between the first client and the second client has been established.

[0127] In some embodiments, the user interface of the client may include a second control for triggering an approval operation, so that if a triggering operation (e.g., click, touch, swipe, etc.) is detected for the second control, it is determined that an approval operation has been detected.

[0128] Based on the temporary session established by the server between the first client and the second client, the first client and the second client can have a conversation during the validity period of the temporary session.

[0129] In some embodiments, before step 610, the method further includes: if a session request is received, displaying a reminder message for the session request; in this embodiment, step 610 includes: in response to a request viewing operation triggered by the reminder message, displaying information about the session request.

[0130] The notification message for a session request is used to indicate that a session request has been received. In some embodiments, the notification message for a session request may be a red dot notification, or other notification messages indicating that a session request has been received; no specific limitation is made here.

[0131] In some embodiments, the reminder message for the session request may be displayed on the client's message page or in the session interface with the session request initiator. Of course, the reminder message for the session request may also be displayed on other pages. No specific limitation is made here, nor is the display format of the reminder message limited.

[0132] The request to view the request triggered by the reminder message can be any action such as clicking, touching, or swiping on the display area of ​​the reminder message; no specific restrictions are imposed here.

[0133] In some embodiments, the session application information is displayed on the session application viewing page, which includes an approval entry point; in this embodiment, before sending an approval instruction to the server in response to an approval approval operation triggered on the session application, the method further includes: displaying an approval page for the session application in response to an operation triggered on the approval entry point; in this embodiment, step 620 includes: sending an approval approval instruction to the server in response to an approval approval operation triggered on the approval page.

[0134] The session request page can display information about multiple session requests received by the client, including information about session requests that have been processed and those that have not been processed.

[0135] The approval entry point can be a link to the approval page or a control set on the session application page for users to access the approval page; no specific restrictions are imposed here.

[0136] In some embodiments, the approval page may also display the event attributes of a session request, wherein the event attributes include pending and completed. If the event attribute of a session request is pending, it indicates that the session request has not yet been approved; conversely, if the event attribute of a session request is completed, it indicates that the session request has already been approved.

[0137] As described above, for a session request sent by the first client, the server can forward the session request to at least two third clients associated with the session recipient, or forward the session request to a second client and at least one third client. Based on this, for any session request, as long as one client (either the second client or a third client) approves the session request, the item attributes of the session request will change accordingly. Therefore, to ensure that the item attributes displayed for the same session request are consistent across multiple clients, after receiving the approval instruction for the session request for the first time, the server sends approval information for the session request to each client that received the session request. This allows each client to update the item attributes of the session request and the current process node of the session request based on the approval information. The approval information for the session request may include the approval instruction received by the server (e.g., approval approval instruction or approval rejection instruction), the user information of the user approving the session request, and the approval time, etc., which are not specifically limited here.

[0138] In this embodiment, after the server receives the approval instruction for the session request for the first time, it sends the approval information for the session request to each client that received the session request. This avoids the situation where two clients (such as two third clients, or one third client and one second client) approve the session request, thus preventing the session request from being subject to secondary approval.

[0139] In some embodiments, after step 610, the method further includes: in response to an approval rejection operation triggered by a session request, sending an approval rejection instruction to the server; and upon receiving the approval rejection instruction, the server sending a rejection notification message to the first client. The rejection notification message indicates that the session request has been rejected.

[0140] In some embodiments, after step 610, the method further includes: forwarding the session request to a fourth client in response to a request forwarding operation triggered by the session request; the fourth client is the client where the selected user identifier is located.

[0141] Generally, a session request is initiated by the requester for a specific matter. However, the requester may misjudge the matter and mistakenly believe that it is to be handled by the recipient when it is not. In such cases, the user of the third-party client can determine whether to forward the session request based on the session request information carried in the request. This ensures that the matter corresponding to the requester is processed promptly and efficiently, avoiding excessive processing time due to incorrect session request transmission.

[0142] In this application, the person who can actually handle the matters indicated by the session request information is referred to as the handler. When it is determined that the session request needs to be forwarded to the actual handler, the user can select a user identifier in the client's display interface. The user indicated by the selected user identifier is the handler, and the corresponding client where the selected user identifier is located is the fourth client. It is understood that the user logged into the fourth client is a different user from the user logged into the second client.

[0143] In some embodiments, when the solution of this application is applied to an enterprise instant messaging application, when it is necessary to forward a session request, an enterprise address book is provided in the client. The enterprise address book includes the user identifiers of all employees in the enterprise, thereby facilitating the selection of the user identifier of the person in charge in the enterprise address book. Then, the session request is forwarded to the client where the person in charge is located (i.e., the fourth client).

[0144] When a session request is forwarded to a fourth client, the fourth client can display the corresponding information about the session request, such as the user identifier of the session request initiator (e.g., user name, nickname, organization information, etc.) and the session request information that initiated the session request.

[0145] In some embodiments, since the session request is forwarded to a fourth client, which is not the second client that the session requester actually requested to receive the session, the client can be set to not have the authority to approve the session requests received through forwarding. The user can then initiate a session with the user who initiated the session request (i.e., the user of the first client) based on the session requests received through forwarding.

[0146] In some embodiments, after forwarding a session request to a fourth client, the third client can send forwarding information to the server. This forwarding information can indicate that the session request has been forwarded and includes the user identifier corresponding to the fourth client. Based on this, the server can send a forwarding notification to the first client, indicating that the session request has been forwarded to the fourth client. The user of the first client can then know from this forwarding notification that the matter to be resolved is actually handled by the user corresponding to the fourth client, and consequently, the user of the first client can proactively initiate a session with the user of the fourth client.

[0147] In some embodiments, when the user of the first client wants to initiate a session with the user of the fourth client based on the forwarding prompt information, the process can be similar to that described above for requesting a session with the second client. That is, if it is determined that the user of the fourth client is not a user who needs to request a session to initiate a session, the first client can directly send a session message to the fourth client, and the server will forward the session message to the fourth client accordingly; conversely, if it is determined that the user of the fourth client is a user who needs to request a session to initiate a session, a session request needs to be initiated for the fourth client first. The processing flow for the session request is similar to that described above and will not be repeated here.

[0148] Figure 7 This is an interface diagram in a third client according to an embodiment of this application. It is worth noting that in this embodiment, the session request is referred to as a chat request. Figure 7 7A in the diagram is an interface diagram of a message viewing page according to an embodiment of this application, such as... Figure 7 As shown in 7A, the message viewing page 710 is used to display reminder messages, which can be reminders of received conversation messages or reminders of received chat requests.

[0149] like Figure 7As shown in 7A, if a chat request is received, a red dot notification will be displayed in the chat request prompt item 711 on the message viewing page 710. This red dot notification can be regarded as a reminder message for the chat request.

[0150] When a user triggers an action (such as clicking or touching), chat request prompt item 711 will appear, allowing access to... Figure 7 The chat request viewing page 720 shown in section 7B displays information about each received chat request. Figure 7 In section 7B, only one chat request is displayed on the chat request viewing page 720. It is understandable that if the client receives multiple chat requests, the information of multiple chat requests can be displayed on the same chat request viewing page 720.

[0151] The chat application viewing page 720 includes a "To-Do" control 723 and a "Completed" control 724. When a user triggers the "To-Do" control 723, uncompleted chat applications are filtered out, and the chat application viewing page 720 displays information about uncompleted chat applications while disabling information about completed chat applications. Similarly, if a user triggers the "Completed" control 724, completed chat applications are filtered out, and the chat application viewing page 720 displays information about completed chat applications while disabling information about uncompleted chat applications.

[0152] The chat request viewing page 720 also includes a chat request viewing area 721, where chat request information can be displayed, such as... Figure 7 The information displayed in the chat request viewing area 721 in 7B includes the username of the chat request initiator (i.e., A) and the username of the conversation recipient (i.e., B), as well as the chat request information entered by A when initiating the chat request (i.e.: I need to communicate with B because of XX matter, please approve).

[0153] Furthermore, the chat application viewing area 721 also includes an approval entry point 722, which is a link to the approval page. Users who trigger this entry point 722 can access... Figure 7 The approval page 730 for chat requests is shown in 7C.

[0154] like Figure 7As shown in Figure 7C, the approval page 730 displays detailed information about the chat application, such as the avatar of the person who initiated the application, the user's nickname (or username), the user's organization information (Company / Department / Organization), the time the application was initiated, and the application details. The approval page 730 also includes an approval comments editing area 732, which displays the user's input comments on the chat application.

[0155] The approval page 730 also includes a "reject" control 733 and an "agree" control 734. If the "agree" control 734 is triggered, it is determined that an approval operation for the chat application has been detected; if the "reject" control 733 is triggered, it is determined that an approval rejection operation for the chat application has been detected.

[0156] The approval page 730 also includes a matter attribute display area 735, which displays the matter attributes of the chat application. These attributes include "pending" and "completed". If the approval entry 722 for a pending chat application is triggered on the chat application viewing page 720, the matter attribute displayed on the approval page 730 for that chat application will be "pending". Similarly, if the approval entry 722 for a completed chat application is triggered, the matter attribute displayed on the approval page 730 for that chat application will be "completed".

[0157] The approval page 730 also includes an entry point 731 for viewing the approval process, which is the area containing the text "View Approval Process". If a user clicks on the entry point 731, they can access the approval process. Figure 7 The interface shown in Figure 7D. Figure 7 The interface diagram shown in 7D includes an approval process viewing area 740. This area 740 can display the process nodes that the chat application has already passed and the current process node. Figure 7 As shown in 7D, the current process node is "Approval Stage: Agent Approval".

[0158] Furthermore, in Figure 7 The 7D interface also allows for the approval of chat requests. The 7D interface includes a "reject" control 733 and an "agree" control 734, which users can trigger to approve the chat request.

[0159] Furthermore, if the user is Figure 7In the approval page 730 shown in 7C, approval comments are entered, and approval controls ("Reject" control 733 and "Agree" control 734) are triggered. If the approval process viewing entry 731 is triggered again, the content of the approval process viewing area 740 on this page will be updated accordingly. Specifically, as shown in 7C... Figure 7 As shown in Figure 7E, the approval process viewing area 740 displays the approval action "Agree" triggered by user A and the approval opinion "Reason is reasonable, can be approved" entered by user A.

[0160] In some embodiments, the server can also forward the session request initiated by the first client to the second and third clients, so that the session recipient can also approve the session request on the second client. In this case, the second client can also approve the session request in the same way as the third client. The specific approval process and the interface diagram for the session request on the second client are as follows. Figure 7 They are basically similar, so I won't go into details here.

[0161] In some embodiments, the second client may also forward the session request received from the first client. The specific forwarding process is similar to that of the third client, and will not be described in detail here.

[0162] Figure 8 This is a schematic diagram of the interface of a second client according to an embodiment of this application. For example... Figure 8 As shown in Figure 8A, if a session request is sent to the client where the session recipient is located (i.e., the second client), the approval process displayed in the approval process viewing area 740 corresponds to the "session recipient"; similarly, when the user of the second client approves the session request, the session recipient (i.e., B) corresponding to the indicated approving user is displayed in the approval process viewing area 740.

[0163] The method of this application will be explained below with reference to a specific application scenario.

[0164] The method described in this application can be applied to enterprise instant messaging applications. In these applications, administrators can configure roles and permissions for personnel within the enterprise, and associate these roles with the corresponding permissions. Furthermore, administrators can designate a first-level user within the enterprise who requires a session request to initiate a conversation, and assign associated users to each of these first-level users. These associated users will have designated roles, such as the "agent" role mentioned above. However, the designated role can have other names, which are not specifically limited here. The permissions corresponding to these designated roles must at least include the permission to approve (or approve and forward) session requests for the associated users.

[0165] In specific implementations, roles and permissions can be set according to the RBAC (Role-Based Access Control) model. In the RBAC model, permissions are associated with roles, and users acquire the permissions of the appropriate roles by becoming members of those roles. Within an organization, roles are created to accomplish various tasks, and users are assigned corresponding roles based on their responsibilities and qualifications. Roles can be granted new permissions based on new needs and system consolidation, and permissions can be revoked from a role as needed. Relationships between roles can be established to encompass a broader range of objective circumstances.

[0166] Figure 9 This diagram illustrates permission configuration using a role-based access control model. Figure 9 As shown, roles can be set based on job positions and organizations, and menu permissions, operation permissions, list field permissions, and permission groups can be assigned to each role. Permission groups serve as the carriers of data permissions. Since organizations have their own organizational permissions, a user's permissions are jointly determined by the permissions of the user's role in their corresponding job position and the organizational permissions of the user's organization.

[0167] In the RBAC model, roles are the fundamental basis for permissions. Functional permissions and data permissions are both attached to roles. This role-based authorization structure enables fine-grained control over functional and data permissions, allowing for unified maintenance of roles and permissions and facilitating flexible addition, deletion, modification, and querying of roles. Administrators can define two types of roles: Leader and Agent.

[0168] Menu permissions, operation permissions, and list field permissions are reflected through interface elements in the logged-in client. Therefore, you can set function permission control interface elements to reflect the menu permissions, operation permissions, and list field permissions of different roles.

[0169] Functional permissions mainly control various interface elements, including menus, pages, fields and buttons on pages, tabs, fields in lists, and other related interface elements. It can provide fine-grained control over the permissions of leaders and agents for interface elements such as chat application permissions and agency capabilities.

[0170] Permission groups serve as the carriers of data permissions. Based on master data, they define the permissions of different users for different master data by using master data as the condition for filtering data permissions, thereby enabling the filtering of various business data.

[0171] A job position is a combination of roles; a single job position can contain multiple roles, allowing a single job position to have multiple roles, thereby expanding the authority of a particular job position. For example, the role of "leader" can be assigned to personnel in multiple positions, and these personnel can also have the roles of leader / agent.

[0172] When a user has permissions for multiple roles, there is no need to switch roles. Instead, the role permissions are stacked, displaying the permissions of all roles under that user's position.

[0173] Furthermore, in the RBAC model, key roles can be mutually exclusive, achieving separation of the three roles: system administrator, security administrator, and security auditor. This ensures that the three key administrator roles are mutually exclusive, thereby improving the security of the entire enterprise instant messaging system.

[0174] Based on the above role definition, further associate users are set for the leader role, so that the associated users have the role of agents, and then process the session requests of the associated leader users.

[0175] Figure 10 This is a flowchart illustrating a method for establishing a session according to an embodiment of this application. Figure 10 In this embodiment, it is assumed that the session request initiator is A, the session recipient is B, and the agent set for B is A (A is the user associated with B and has a designated role (agent)).

[0176] like Figure 10 As shown, the process includes: Step 1001, sending a session message to B; if it is determined that A and B do not need to apply for a session, then proceed to step 1009; otherwise, if it is determined that A and B need to apply for a session, then proceed to step 1002 and receive a message sending failure prompt; Step 1003, initiating a session application.

[0177] If it is determined that B has an agent, the session request can be sent to A, or it can be sent to both A and B. If it is determined that B does not have an agent, the session request can be sent to B. After the session request is sent to A and / or B, A or B will approve the session request according to the following steps 1004-1006. Step 1004: Received the session request; Step 1005: Should it be forwarded to the handler? If it should be forwarded to the handler, the process will jump to the handler's processing flow; if it should not be forwarded to the handler, proceed to step 1006: Approved the session request? If the session request is approved, A will proceed to step 1007: Received an approval message; furthermore, A can view the session request approval process based on the approval message. Then A will proceed to step 1008: Send a session message to B again; correspondingly, B will proceed to step 1009: Receive the session message sent by A.

[0178] If the session request is not approved (i.e., the session request is rejected), then A will proceed to step 1010 and receive a rejection message; similarly, A can also view the session request approval process based on this rejection message. Afterwards, A can re-initiate the session request.

[0179] Figure 11 This is a schematic diagram illustrating the handling process of the agent according to an embodiment of this application. Figure 11 The processes of steps 1001-1005 are not described in detail here. Figure 11 As shown, after determining that the session request needs to be forwarded to the handler, the client where the handler is located executes the following steps 1101-1104: Step 1101: Receive a card message; this card message indicates that the forwarded session request has been received. Step 1102: Send a session message to A; Step 1103: Determine if the handler needs to apply for a session with A; if it is determined that the handler does not need to apply for a session with A, then execute step 1104: Send a session message to A; correspondingly, A will receive the session message sent by the handler. If it is determined that the handler needs to apply for a session with A, then execute the session application process, where the session application process is described in [link to relevant documentation]. Figure 10 The processes of steps 1003-1007 and step 1010 are not described in detail here.

[0180] In instant messaging applications using related technologies, session requests only occur between the requester and the recipient. The process can be either peer-to-peer: request initiation → request approval → session initiation, or peer-to-peer: request initiation → request rejection → session rejection. However, in this application's solution, administrators can assign specific roles (e.g., agents) to certain users. Users with these roles can handle chat requests on behalf of their associated users (e.g., leaders), thereby reducing the burden of processing session requests on the leader's side and improving the efficiency of conversations with the leader.

[0181] Figure 12 A comparative diagram is shown between the communication mechanism in related technologies and the communication mechanism using the solution of this application. In related technologies, in enterprise instant messaging applications of enterprises or other organizations, session requests can only be initiated hierarchically, for example... Figure 12 The communication mechanism on the left side of the screen requires a multi-level communication channel. If a frontline employee needs to communicate with a company manager, they must first submit a request to a group of managers. After the group approves the request, the request is submitted to the secretary, who then submits it to the company manager. Only after the company manager approves the request can the frontline employee communicate with the company manager through their own client. Because this process requires multiple levels of approval, and the next level's request is only initiated after the previous level approves it, the approval process is lengthy, resulting in low communication efficiency.

[0182] If the solution proposed in this application is adopted, an agent can be set up for users with target roles (such as company leaders, department leaders, etc., which will be referred to as the first designated user for ease of description). Session requests for the first designated user can be sent directly to the client where the agent of the first designated user is located. The client where the agent is located approves the session request. After the session request is approved, the client of the session request initiator can directly conduct a temporary session with the client where the first designated user is located. Thus, there is no need to go through the session request step by step. Moreover, for the first designated user with limited time, there is no need to spend a lot of time on session request approval, which greatly reduces the pressure on the first designated user to make session requests, shortens the session request time, and improves session efficiency.

[0183] The solution proposed in this application, while supporting sessions for a first designated user based on a request, can send session requests to a user associated with the first designated user and with a specified role to assist in processing session requests for the first designated user. On the one hand, this avoids the problem of the first designated user being overwhelmed by the indiscriminate sending of messages, and on the other hand, by having a user associated with the first designated user and with a specified role assist in processing session requests for the first designated user, it avoids the first designated user having to spend a lot of time approving session requests due to the need to request first and then have a session. Thus, it improves the efficiency of session request approval and ensures the efficiency of sessions with the first designated user.

[0184] Furthermore, the solution in this application allows users with designated roles to forward session requests to the relevant handlers for processing when they determine that the matters requested in the session request are unrelated to the first designated user. The handlers can then handle the corresponding matters without the first designated user's involvement, and the efficiency of the matter processing can be guaranteed.

[0185] The following describes an apparatus embodiment of this application, which can be used to perform the methods described in the above embodiments of this application. For details not disclosed in the apparatus embodiments of this application, please refer to the method embodiments described in the above embodiments of this application.

[0186] Figure 13This is a block diagram of an apparatus for establishing a session according to an embodiment of this application. The apparatus is applied to a first client where the session requester is located, and includes: a session request sending module 1310, used to send a session request in response to a triggered session request operation, the session request being used to request the establishment of a temporary session between the first client and a second client; the second client refers to the client where the session receiver is located; and a prompt information display module 1320, used to display an approval prompt information, generated after the session request has been approved by a third client, the third client referring to the client where the user associated with the session receiver and having a specified role is located; the prompt information is used to indicate that a temporary session has been established between the first client and the second client.

[0187] In some embodiments, based on Figure 13 The apparatus for establishing a session shown further includes a session request window display module for displaying a session request window for inputting session request information. In this embodiment, the session request sending module 1310 is further configured to send a session request based on the session request information in response to a session request operation triggered in the session request window.

[0188] In some embodiments, based on Figure 13 The apparatus for establishing a session shown further includes: a session request prompt information display module, used to display session request prompt information in the session interface with the session recipient, the session request prompt information including a session request entry; in this embodiment, the session request window display module is further configured to: display a session request window in response to an operation triggered by the session request entry.

[0189] In some embodiments, the session request prompt information display module is further configured to: in response to receiving a sending failure prompt information, display the session request prompt information in the session interface with the session recipient. The sending failure prompt information is sent by the server to the first client after receiving a session message sent by the first client to the second client and determining that no temporary session has been established between the first client and the second client.

[0190] In some embodiments, the session request is also sent to a second client, and upon acceptance of the session request by the second client, an acceptance message is generated.

[0191] In some embodiments, based on Figure 13 The apparatus for establishing a session shown further includes a rejection message display module for displaying rejection messages, which are generated after a third client or a second client approves and rejects the session request.

[0192] Figure 14This is a block diagram of an apparatus for establishing a session according to another embodiment of this application. Figure 14 The apparatus shown is applied to a third client, which refers to the client of a user associated with the session recipient and possessing a designated role; such as Figure 14 As shown, the device includes: an information display module 1410 for displaying session request information; the session request is used to request the establishment of a temporary session between a first client and a second client; the first client refers to the client where the session requester is located, and the second client refers to the client where the session receiver is located; an approval instruction sending module 1420 for sending an approval instruction to the server in response to the approval operation triggered by the session request; after receiving the approval instruction, the server establishes a temporary session between the first client and the second client and sends an approval prompt message to the first client; the approval prompt message is used to indicate that a temporary session between the first client and the second client has been established.

[0193] In some embodiments, based on Figure 14 The apparatus for establishing a session shown further includes: a reminder information display module, used to display a reminder information for the session request if a session request is received; in this embodiment, the information display module 1410 is further configured to display information about the session request in response to a request viewing operation triggered by the reminder information.

[0194] In some embodiments, session request information is displayed on the session request viewing page, which includes an approval entry point; in this embodiment, based on Figure 14 The apparatus for establishing a session shown further includes: an approval page display module, used to display an approval page for the session application in response to an operation triggered by the approval entry; in this embodiment, the approval approval instruction sending module 1420 is further configured to send an approval approval instruction to the server in response to an approval approval operation triggered on the approval page.

[0195] In some embodiments, based on Figure 14 The apparatus for establishing a session shown further includes a forwarding module for forwarding the session request to a fourth client in response to a request forwarding operation triggered by the session request; the fourth client is the client where the selected user identifier is located.

[0196] In some embodiments, based on Figure 14 The apparatus for establishing a session shown further includes: an approval rejection instruction sending module, used to send an approval rejection instruction to the server in response to an approval rejection operation triggered by a session application, and the server sending a rejection prompt message to the first client after receiving the approval rejection instruction.

[0197] Figure 15This is a block diagram illustrating an apparatus for establishing a session according to another embodiment of this application. This apparatus can be applied to a server, such as... Figure 15 As shown, the device includes: a session request receiving module 1510, used to receive a session request sent by a first client, the session request being used to request the establishment of a temporary session between the first client and a second client; the first client refers to the client where the session requester is located; the second client refers to the client where the session receiver is located; a forwarding module 1520, used to forward the session request to a third client, the third client referring to the client where the user associated with the session receiver and having a specified role is located; an approval instruction receiving module 1530, used to receive an approval instruction returned by the third client after approving the session request; a temporary session establishment module 1540, used to establish a temporary session between the first client and the second client in response to the approval instruction; and a notification message sending module 1550, used to send an approval notification message to the first client; the notification message is used to indicate that a temporary session between the first client and the second client has been established.

[0198] In some embodiments, based on Figure 15 The apparatus for establishing a session shown further includes: a role configuration information acquisition module for acquiring role configuration information corresponding to the second client; a specified user identifier acquisition module for acquiring a specified user identifier of a user with a specified role from the role configuration information; and the specified user identifier is used to determine the third client.

[0199] In some embodiments, based on Figure 15 The apparatus for establishing a session shown further includes a session message forwarding module, which, during the validity period of the temporary session, forwards the session message to the second client if a session message sent by the first client to the second client is received.

[0200] In some embodiments, based on Figure 15 The apparatus for establishing a session shown further includes a failure message sending module, which, if a session message sent by the first client to the second client is received during the period when a temporary session between the first client and the second client has not been established, or after the validity period of the temporary session has expired, does not forward the session message to the second client, but returns a failure message to the first client.

[0201] In some embodiments, based on Figure 15 The apparatus for establishing a session shown further includes: a second session request forwarding module for forwarding a session request to a second client; and a second approval instruction receiving module for receiving an approval instruction returned by the second client after approving the session request.

[0202] In some embodiments, based on Figure 15 The apparatus for establishing a session shown further includes a rejection notification message sending module, used to send a rejection notification message to the first client if it receives an approval rejection instruction returned by a third client after approving and rejecting a session application, or receives an approval rejection instruction returned by a second client after approving and rejecting a session application.

[0203] Figure 16 A schematic diagram of a computer system suitable for implementing the embodiments of this application is shown. It should be noted that... Figure 16 The computer system 1600 of 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 16 As shown, the computer system 1600 includes a Central Processing Unit (CPU) 1601, which can perform various appropriate actions and processes, such as executing the methods described in the above embodiments, based on programs stored in Read-Only Memory (ROM) 1602 or programs loaded from storage portion 1608 into Random Access Memory (RAM) 1603. The RAM 1603 also stores various programs and data required for system operation. The CPU 1601, ROM 1602, and RAM 1603 are interconnected via a bus 1604. An Input / Output (I / O) interface 1605 is also connected to the bus 1604.

[0205] The following components are connected to I / O interface 1605: an input section 1606 including a keyboard, mouse, etc.; an output section 1607 including a cathode ray tube (CRT), liquid crystal display (LCD), etc., and speakers, etc.; a storage section 1608 including a hard disk, etc.; and a communication section 1609 including a network interface card such as a LAN (Local Area Network) card, modem, etc. The communication section 1609 performs communication processing via a network such as the Internet. A drive 1610 is also connected to I / O interface 1605 as needed. Removable media 1611, such as a disk, optical disk, magneto-optical disk, semiconductor memory, etc., are installed on drive 1610 as needed so that computer programs read from them can be installed into storage section 1608 as needed.

[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 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 section 1609, and / or installed from removable medium 1611. When the computer program is executed by central processing unit (CPU) 1601, it performs various functions defined in the system of this application.

[0207] It should be noted that the computer-readable medium shown in the embodiments of 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), flash memory, optical fiber, portable compact disc 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 transmitted data signals can take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. The computer-readable signal medium can also 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 wireless, wired, etc., or any suitable combination thereof.

[0208] 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. Each block in a flowchart or block diagram may represent a module, segment, or portion of code, which contains 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 a block diagram or flowchart, and combinations of blocks in a block diagram or flowchart, 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.

[0209] The units described in the embodiments of this application can be implemented in software or hardware, and the described units can also be located in a processor. The names of these units do not necessarily limit the specific unit itself.

[0210] In another aspect, this application also provides a computer-readable storage medium, which may be included in the electronic device described in the above embodiments; or it may exist independently and not assembled into the electronic device. The aforementioned computer-readable storage medium carries computer-readable instructions that, when executed by a processor, implement the methods in any of the above embodiments.

[0211] According to one aspect of this application, an electronic device is also provided, comprising: a processor; and a memory storing computer-readable instructions that, when executed by the processor, implement the methods of any of the above embodiments.

[0212] According to one aspect of the embodiments of this application, a computer program product or computer program is provided, the computer program product or computer program including computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, causing the computer device to perform the methods of any of the above embodiments.

[0213] It should be noted that although several modules or units for the device used to perform actions have been mentioned in the detailed description above, this division is not mandatory. In fact, according to the embodiments of this application, the features and functions of two or more modules or units described above can be embodied in one module or unit. Conversely, the features and functions of one module or unit described above can be further divided and embodied by multiple modules or units.

[0214] Through the above description of the embodiments, those skilled in the art will readily understand that the exemplary embodiments described herein can be implemented by software or by combining software with necessary hardware. Therefore, the technical solutions according to the embodiments of this application can be embodied in the form of a software product, which can be stored in a non-volatile storage medium (such as a CD-ROM, USB flash drive, external hard drive, etc.) or on a network, including several instructions to cause a computing device (such as a personal computer, server, touch terminal, or network device, etc.) to execute the method according to the embodiments of this application.

[0215] Other embodiments of this application will readily occur to those skilled in the art upon consideration of the specification and practice of the embodiments 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.

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

Claims

1. A method of establishing a session, characterized by, Applied to the first client where the session requester is located, including: The session request window is displayed; the session request window is used to input session request information. In response to a session request operation triggered in the session request window, a session request is sent based on the input session request information. The session request is used to request the establishment of a temporary session between a first client and a second client; the second client refers to the client where the session recipient is located; the session request information includes the reason for requesting the session. The message indicating approval is generated after a third client approves the session request. The third client refers to the client of a user associated with the session recipient and possessing a designated role. The message indicates that a temporary session has been established between the first client and the second client. This temporary session has a validity period. During this period, session messages sent from the first client to the second client are forwarded by the server to the second client, and session messages sent from the second client to the first client are forwarded by the server to the first client. If no temporary session is established between the first client and the second client, session messages sent from the second client to the first client are forwarded by the server to the first client, but session messages sent from the first client to the second client are not forwarded by the server to the second client. The first client, the second client, and the third client are clients of an enterprise instant messaging application; the user corresponding to the second client has a higher job level in the enterprise than the user corresponding to the first client.

2. The method of claim 1, wherein, Before displaying the session request window, the method further includes: A session request prompt message is displayed in the session interface with the session recipient, and the session request prompt message includes a session request entry point; The session request window includes: In response to an operation triggered by the session request entry, the session request window is displayed.

3. The method of claim 2, wherein, The step of displaying a session request prompt in the session interface with the session recipient includes: In response to receiving a sending failure message, a session request message is displayed in the session interface with the session recipient. The sending failure message is sent by the server to the first client after receiving the session message sent by the first client to the second client and determining that no temporary session has been established between the first client and the second client.

4. The method of claim 1, wherein, The session request is also sent to the second client, and after the second client approves the session request, the approval message is generated.

5. The method of claim 4, wherein, After responding to a session request operation triggered by the session request window and sending a session request based on the input session request information, the method further includes: The rejection message is displayed after the third client or the second client approves and rejects the session request.

6. A method of establishing a session, characterized by, This applies to a third client, which is the client of a user associated with the session recipient and having a specified role. The method includes: The session request information is displayed; the session request is used to request the establishment of a temporary session between the first client and the second client; the first client refers to the client where the session requester is located, and the second client refers to the client where the session receiver is located; the first client, the second client, and the third client are clients of an enterprise instant messaging application; the user corresponding to the second client has a higher job level in the enterprise than the user corresponding to the first client; In response to the approval operation triggered by the session request, an approval instruction is sent to the server; after receiving the approval instruction, the server establishes a temporary session between the first client and the second client, and sends an approval prompt message to the first client; the approval prompt message is used to indicate that a temporary session between the first client and the second client has been established. The temporary session has a validity period. During the validity period of the temporary session, the session messages sent by the first client to the second client will be forwarded by the server to the second client, and the session messages sent by the second client to the first client will be forwarded by the server to the first client. If no temporary session is established between the first client and the second client, the session messages sent by the second client to the first client will be forwarded by the server to the first client, but the session messages sent by the first client to the second client will not be forwarded by the server to the second client. The session request is initiated by the first client, which initiates the session request according to the following process: displaying a session request window; the session request window is used to input session request information; in response to a session request operation triggered in the session request window, the first client sends a session request based on the input session request information, the session request information including the reason for requesting a session.

7. The method of claim 6, wherein, Before displaying the session request information, the method further includes: If the session request is received, a notification message for the session request will be displayed; The information displayed in the session request includes: In response to the request to view the notification message, the session request information is displayed.

8. The method according to claim 7, characterized in that, The session request information is displayed on the session request viewing page, which includes an approval entry point; Before sending an approval instruction to the server in response to the approval operation triggered by the session request, the method further includes: In response to an operation triggered by the approval entry point, an approval page for the session application is displayed; The step of sending an approval instruction to the server in response to the approval operation triggered by the session request includes: In response to the approval action triggered on the approval page, an approval instruction is sent to the server.

9. The method according to claim 6, characterized in that, After displaying the session request information, the method further includes: In response to the request forwarding operation triggered by the session request, the session request is forwarded to the fourth client; the fourth client is the client where the selected user identifier is located.

10. The method according to claim 6, characterized in that, After displaying the session request information, the method further includes: In response to the approval rejection operation triggered by the session request, an approval rejection instruction is sent to the server. After receiving the approval rejection instruction, the server sends a rejection prompt message to the first client.

11. A method for establishing a session, characterized in that, Applied to the server side, including: The system receives a session request sent by a first client, which requests the establishment of a temporary session between the first client and a second client; the first client refers to the client where the session requester is located; the second client refers to the client where the session receiver is located. The session request is forwarded to a third client, which is the client of a user associated with the session recipient and having a specified role; the first client, the second client, and the third client are clients of an enterprise instant messaging application; the user corresponding to the second client has a higher job level in the enterprise than the user corresponding to the first client; Receive the approval instruction returned by the third client after approving the session request; In response to the approval instruction, a temporary session is established between the first client and the second client; A pass notification message is sent to the first client; the pass notification message indicates that a temporary session has been established between the first client and the second client; the temporary session has a validity period, during which session messages sent by the first client to the second client will be forwarded by the server to the second client, and session messages sent by the second client to the first client will be forwarded by the server to the first client; if no temporary session is established between the first client and the second client, session messages sent by the second client to the first client will be forwarded by the server to the first client, but session messages sent by the first client to the second client will not be forwarded by the server to the second client; The first client initiates the session request according to the following process: displaying a session request window; the session request window is used to input session request information; in response to the session request operation triggered in the session request window, a session request is sent according to the input session request information, the session request information including the reason for requesting a session.

12. The method according to claim 11, characterized in that, Before forwarding the session request to the third client, the method further includes: Obtain the role configuration information corresponding to the second client; Obtain the designated user identifier of the user with the designated role from the role configuration information; the designated user identifier is used to identify the third client.

13. The method according to claim 11, characterized in that, The method further includes: During the period when a temporary session between the first client and the second client is not established, or after the validity period of the temporary session has expired, if a session message is received from the first client to the second client, the session message is not forwarded to the second client, and a sending failure message is returned to the first client.

14. The method according to claim 11, characterized in that, Before establishing a temporary session between the first client and the second client in response to the approval instruction, the method further includes: The session request is forwarded to the second client; Receive the approval instruction returned by the second client after approving the session application.

15. The method according to claim 14, characterized in that, After forwarding the session request to the second client, the method further includes: If the system receives an approval rejection instruction from the third client after rejecting the session request, or receives an approval rejection instruction from the second client after rejecting the session request, it sends a rejection notification message to the first client.

16. An apparatus for establishing a session, characterized in that, Applied to the first client where the session requester is located, including: A session request window display module is used to display a session request window; the session request window is used to input session request information. The session request sending module is used to respond to a session request operation triggered in the session request window, and send a session request based on the input session request information. The session request is used to request the establishment of a temporary session between a first client and a second client; the second client refers to the client where the session recipient is located; the session request information includes the reason for requesting the session. The notification display module displays an approval notification, which is generated after the session application is approved by a third client. The third client refers to the client of a user associated with the session recipient and possessing a designated role. The approval notification indicates that a temporary session has been established between the first client and the second client. This temporary session has a validity period. During this period, session messages sent by the first client to the second client are forwarded by the server to the second client, and session messages sent by the second client to the first client are forwarded by the server to the first client. If no temporary session is established between the first client and the second client, session messages sent by the second client to the first client are forwarded by the server to the first client, but session messages sent by the first client to the second client are not forwarded by the server to the second client. The first client, the second client, and the third client are clients of an enterprise instant messaging application; the user corresponding to the second client has a higher job level in the enterprise than the user corresponding to the first client.

17. An apparatus for establishing a session, characterized in that, Applied to a third client, wherein the third client refers to the client of a user associated with the session recipient and having a specified role; the apparatus includes: The information display module is used to display session request information; the session request is used to request the establishment of a temporary session between a first client and a second client; the first client refers to the client where the session requester is located, and the second client refers to the client where the session receiver is located; the first client, the second client, and the third client are clients of an enterprise instant messaging application; the user corresponding to the second client has a higher job level in the enterprise than the user corresponding to the first client; The approval instruction sending module is used to send an approval instruction to the server in response to the approval operation triggered by the session application; after receiving the approval instruction, the server establishes a temporary session between the first client and the second client, and sends an approval prompt message to the first client; the approval prompt message is used to indicate that a temporary session between the first client and the second client has been established. The temporary session has a validity period. During the validity period of the temporary session, the session messages sent by the first client to the second client will be forwarded by the server to the second client, and the session messages sent by the second client to the first client will be forwarded by the server to the first client. If no temporary session is established between the first client and the second client, the session messages sent by the second client to the first client will be forwarded by the server to the first client, but the session messages sent by the first client to the second client will not be forwarded by the server to the second client. The session request is initiated by the first client, which initiates the session request according to the following process: displaying a session request window; the session request window is used to input session request information; in response to a session request operation triggered in the session request window, a session request is sent according to the input session request information; the session request information includes the reason for requesting a session.

18. An apparatus for establishing a session, characterized in that, Applied to the server side, the device includes: The session request receiving module is used to receive a session request sent by a first client, which is used to request the establishment of a temporary session between the first client and a second client; the first client refers to the client where the session requester is located; the second client refers to the client where the session receiver is located. The forwarding module is used to forward the session request to a third client, which is the client of a user associated with the session recipient and having a specified role; the first client, the second client, and the third client are clients of an enterprise instant messaging application; the user corresponding to the second client has a higher job level in the enterprise than the user corresponding to the first client; The approval instruction receiving module is used to receive the approval instruction returned by the third client after approving the session application; A temporary session establishment module is used to establish a temporary session between the first client and the second client in response to the approval instruction; The notification message sending module is used to send a notification message to the first client. The notification message indicates that a temporary session has been established between the first client and the second client. The temporary session has a validity period. During the validity period of the temporary session, session messages sent by the first client to the second client will be forwarded by the server to the second client, and session messages sent by the second client to the first client will be forwarded by the server to the first client. If no temporary session is established between the first client and the second client, session messages sent by the second client to the first client will be forwarded by the server to the first client, but session messages sent by the first client to the second client will not be forwarded by the server to the second client. The first client initiates the session request according to the following process: displaying a session request window; the session request window is used to input session request information; in response to the session request operation triggered in the session request window, a session request is sent according to the input session request information, the session request information including the reason for requesting a session.

19. An electronic device, characterized in that, include: processor; A memory storing computer-readable instructions that, when executed by the processor, implement the method as described in any one of claims 1-15.

20. A computer-readable storage medium having stored thereon computer-readable instructions that, when executed by a processor, implement the method as described in any one of claims 1-15.

21. A computer program product comprising computer instructions, characterized in that, When the computer instructions are executed by the processor, they implement the method of any one of claims 1-15.

Citation Information

Patent Citations

  • Real-time third-party authorization of communication sessions

    US20200280539A1