Session processing method and device, equipment and storage medium

Abstract

The embodiment of the invention provides a session processing method and device, equipment and a storage medium. The method comprises the following steps: receiving a session request initiated by an own user to any opposite user through a target chat site, and determining management account relationship information between the own user and the opposite user from a session object relationship set of the target chat site; if the management user relation information is a non-null value, a first session room between the own user and the opposite user is obtained, a first session page of the first session room is displayed through a client of the own user, and a session input control in the first session page is in an operable state; if the management account relation information is a null value, a second session room between the own user and the opposite user is obtained, a second session page of the second session room is displayed through a client of the own user, and a session input control in the second session page is in an inoperable state. According to the invention, session management and control of both parties of the session under a management account relationship can be realized, so that safe and effective high-quality session service is provided.

Description

Technical Field

[0001] This application relates to the field of data processing technology, specifically to a session processing method, apparatus, device, and storage medium. Background Technology

[0002] In investment and trading scenarios for various trading products, in order to improve customer retention and activity, a dedicated service advisor, such as an account manager, is usually assigned to each customer to provide timely and effective trading services.

[0003] Typically, clients and service advisors use existing chat tools offline to add each other as friends, enabling timely and effective online communication regarding the transaction process for various products. However, existing chat tools do not support managing the friend relationships between clients and service advisors, allowing other service advisors to add clients as friends at will, thus compromising the security and effectiveness of conversations between the two parties. Summary of the Invention

[0004] This application provides a session processing method, apparatus, device, and storage medium to realize session control between two parties under a manager-client relationship, provide a more secure and efficient high-quality session service for both parties, and ensure the convenience of the session for both parties in any business transaction scenario.

[0005] In a first aspect, embodiments of this application provide a session processing method, the method comprising: Receive a session request initiated by your own user to any other user through the target chat site, and determine the management relationship information between your own user and the other user from the session object relationship set of the target chat site; If the user relationship information is not empty, obtain the first conversation room between the user and the other user, and display the first conversation page of the first conversation room through the user's client. The conversation input controls in the first conversation page are in an operable state. If the user relationship information is empty, obtain the second conversation room between the user and the other user, and display the second conversation page of the second conversation room through the user's client. The conversation input controls on the second conversation page are in an inoperable state.

[0006] Secondly, embodiments of this application provide a session processing apparatus, the apparatus comprising: The user management relationship determination module is used to receive a session request initiated by a user on the target chat site to any other user, and determine the user management relationship information between the user and the other user from the session object relationship set of the target chat site. The first session module is used to obtain the first session room between the user and the other user if the user relationship information is not empty, and to display the first session page of the first session room through the user's client. The session input controls in the first session page are in an operable state. The second session module is used to obtain the second session room between the user and the other user if the user relationship information is empty, and to display the second session page of the second session room through the user's client. The session input controls on the second session page are in an inoperable state.

[0007] Thirdly, embodiments of this application provide an electronic device, which includes: A processor and a memory, wherein the memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory to perform the session processing method provided in any embodiment of this application.

[0008] Fourthly, embodiments of this application provide a computer-readable storage medium for storing a computer program that causes a computer to perform a session processing method as provided in any embodiment of this application.

[0009] Fifthly, embodiments of this application provide a computer program product, including a computer program / instructions, which, when executed by a processor, implement the session processing method provided in any embodiment of this application.

[0010] The technical solution provided in this application, upon receiving a conversation request initiated by a user from a target chat site to any other user, can determine whether a manager-user relationship exists between the user and the other user from the conversation object relationship set of the target chat site. If so, a first conversation room between the user and the other user is obtained, and a first conversation page of the first conversation room is displayed through the user's client. The conversation input controls on the first conversation page are operable, enabling normal conversation between the two parties. If not, a second conversation room between the user and the other user is obtained, and a second conversation page of the second conversation room is displayed through the user's client. The conversation input controls on the second conversation page are inoperable, prohibiting conversation between the user and the other user. This achieves conversation control under a manager-user relationship, preventing communication and interaction between parties without a manager-user relationship in any business transaction scenario. It ensures reasonable and compliant conversations between the parties in any business transaction scenario, reducing transaction risks and providing a safer and more effective high-quality conversation service, ensuring the convenience of conversations for both parties in any business transaction scenario. Attached Figure Description

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

[0012] Figure 1 A flowchart illustrating a session processing method provided in an embodiment of this application; Figure 2 A flowchart illustrating a method for initiating a session against any other user when the user is a first-type user, as provided in this application embodiment; Figure 3 A flowchart illustrating another method for initiating a session against any other user when the user is a first-type user, as provided in this application embodiment; Figure 4 A flowchart illustrating a method for initiating a session against any other user when the user is a second type of user, as provided in this application embodiment; Figure 5 A flowchart illustrating another method for initiating a session against any other user when the user is a second type of user, as provided in this application embodiment; Figure 6 A schematic block diagram of a session processing device provided in an embodiment of this application; Figure 7 A schematic block diagram of an electronic device provided in an embodiment of this application. Detailed Implementation

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

[0014] It should be noted that the terms "first," "second," etc., in the specification, claims, and accompanying drawings of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of this application described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion; for example, a process, method, system, product, or server that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or devices.

[0015] In this application, the terms "exemplary" or "for example" are used to indicate that something is an example, illustration, or description. Any embodiment or solution described as "exemplary" or "for example" in this application should not be construed as being better or more advantageous than other embodiments or solutions. Specifically, the use of terms such as "exemplary" or "for example" is intended to present the relevant concepts in a specific manner.

[0016] In the description of the embodiments in this application, unless otherwise stated, "multiple" means two or more, that is, at least two. "At least one" means one or more. "Any" means any one or any several.

[0017] It should be noted that all information (including but not limited to user login identity information, various chat messages, and the account management relationship between the chat partners), data (including but not limited to data used for analysis, stored data, and displayed data), and signals involved in this application have been authorized by the user or fully authorized by all parties, and the collection, use, and processing of related data must comply with the relevant laws, regulations, and standards of the relevant countries and regions. For example, the user's identity data when logging into the target chat site, the account management relationship between the chat partners, and chat messages during the chat process involved in this application were all obtained with full authorization.

[0018] Because existing conversation tools can no longer guarantee secure and effective conversations between clients and service advisors (such as account managers) regarding specific transaction processes for various transaction targets, this application will construct an instant messaging (IM) site to provide a more secure and effective high-quality conversation service for both parties.

[0019] Specifically, in investment and trading scenarios for various trading instruments, clients can execute corresponding trading operations on various instruments within any business trading application. Furthermore, by assigning a dedicated service advisor to each client, the advisor can promptly follow up and communicate with the client regarding their trading activities across various instruments, thus providing clients with higher-quality and more convenient trading services. At this point, for each client and service advisor registered within the business trading application, the Customer Relationship Management (CRM) system typically maintains the personal information of each client and service advisor, as well as the account management relationship between the client and the service advisor, in real time. For example, when a client is added to the CRM system, in addition to maintaining the client's personal information, a dedicated service advisor is added to monitor the client's trading activities across various instruments in real time, thereby maintaining an account management relationship between the client and the dedicated service advisor.

[0020] In this context, the account management relationship between the two parties in a session can refer to a formal binding relationship in any business transaction platform where one party (e.g., a client) is specifically designated to be followed up by the other party (e.g., a dedicated service advisor). This means that each service advisor in the session can communicate in a timely manner with the clients they are responsible for regarding the transaction status of various transaction targets.

[0021] Therefore, in order to ensure a secure and effective conversation between the customer and the service advisor (such as an account manager), this application will make the IM site and the CRM system share the same backend service and database when building the IM site, so as to realize the data connection between the IM site and the CRM system. This will enable the IM site to accurately query relevant data from the CRM system when performing conversation interactions, such as the account management relationship between the two parties, so as to manage the conversation between the two parties.

[0022] Furthermore, since the conversational functions implemented by the clients and service advisors (e.g., account managers) on both sides of the conversation differ for various transaction targets, the IM site constructed in this application can include an IM client site built for clients and an IM advisor site built for service advisors (e.g., account managers) to ensure normal chat between the two parties. In this case, different conversational functions can be configured in the IM client site and the IM advisor site according to the different conversational needs of clients and service advisors (e.g., account managers) for various transaction targets.

[0023] Furthermore, the IM customer site and IM consultant site in the IM site constructed in this application both embed existing mature conversation frameworks, such as the conversation framework based on TUIKit, to quickly build an application with basic conversation functions, and modify it to adapt to the business conversation functions of the customer and service consultant (such as account manager) on various transaction targets in the conversation, thereby obtaining the IM customer site and IM consultant site in this application.

[0024] Understandably, based on the aforementioned conversation framework, the IM client site and IM consultant site can implement basic conversation functions such as user login, message list display, historical message search, and sending / receiving / recalling messages. Furthermore, the backend service configured for the IM client site and IM consultant site can utilize Kafuka consumption queues to achieve capabilities such as persistent recording of historical conversation messages between the two parties and automatic message replies. Therefore, the IM client site and IM consultant site can implement almost all the conversation functions found in existing conversation tools, such as sending and displaying various types of messages, message bubble style design, message sending status display, group chat, message pinning, and so on.

[0025] Furthermore, the specific business functions performed by the clients and service advisors (such as account managers) on various transaction targets differ between the two parties in the conversation. For example, clients typically log into a business transaction application developed for specific transaction scenarios of various transaction targets to perform actual transaction operations. Service advisors, on the other hand, usually use existing internal conversation tools to conduct internal communication and exchange among themselves regarding the specific details of various transaction targets.

[0026] Therefore, to ensure the convenience of chatting for both parties in any business transaction scenario, the IM customer site built for customers and the IM advisor site built for service advisors will be deployed in different applications that customers and service advisors frequently use for various transaction targets, so that when both parties perform relevant business operations in the relevant applications, they can quickly and conveniently enter the corresponding IM site for conversation interaction without having to frequently exit the application.

[0027] It should be noted that, in investment and trading scenarios involving various trading targets, clients can execute corresponding trading operations on various trading targets within multiple business trading applications developed in multiple regions. Service advisors can also communicate internally using various chat tools in multiple regions. However, the different applications used by clients and service advisors in different regions will have certain business and service differences. Therefore, to ensure efficient and accurate communication between the two parties, this application can design a multi-market (i.e., regional) multi-business deployment solution for the existing IM site, using a configurable approach to make the IM site compatible with the business and service differences under different markets and businesses.

[0028] Therefore, in any deployment environment where an IM site is deployed within any application in any marketplace, when either user enters the IM site, the connection typically passes through a web gateway. This web gateway determines the current configuration information of the IM site after deployment and generates a corresponding configuration tag. Thus, during session interactions within the IM site, this configuration tag can be used to distribute session messages to the corresponding deployment group. This deployment group can include the devices and servers of the specific application used in the specific marketplace where the IM site is deployed. Then, based on the interface mapping relationships pre-configured for different deployment environments at the access layer, session messages from the IM site in different deployment environments can be distributed to the backend services of different business parties, achieving session message isolation for the IM site across multiple deployment environments.

[0029] The following explains the various technical features involved in the embodiments of this application. Wherein: The target chat site refers to the IM site constructed in this application, used to support communication between clients and service advisors (such as account managers) regarding the specific transaction details of various investment targets. The target chat site may include an IM client site built for clients and an IM advisor site built for service advisors (such as account managers).

[0030] "Our own user" refers to the current user who initiates a conversational interaction with any other user by logging into the target chat site. This can be either the customer or the service advisor (e.g., account manager) in the conversation.

[0031] The other party refers to another specific conversation partner that a user points to when initiating a conversation interaction by logging into the target chat site. This can be the other party in a conversation between a customer and a service advisor (such as an account manager).

[0032] The first type of user refers to customers who perform relevant trading operations on various trading targets in investment and trading scenarios.

[0033] The second type of user refers to the service advisors assigned to each client in various investment and trading scenarios for different trading targets. They are responsible for following up on the specific trading situation of each client for various trading targets and sharing information about various trading targets in a timely manner to help clients understand the products of the trading targets and place orders quickly.

[0034] The first type of application client refers to any business trading platform client that supports clients in performing actual trading operations on various trading targets in investment and trading scenarios. In other words, it is a financial trading platform client that supports the first type of users in realizing target trading. By deploying the IM client site built for clients on the first type of application client, clients can quickly and conveniently enter the IM client site for conversational interaction without having to log out of the first type of application client to perform business trading operations on relevant trading targets.

[0035] The second type of application client refers to any existing conversational tool that supports service advisors in internal communication regarding the specific circumstances of various transaction targets. In other words, it's an instant messaging application client that allows second-type users to engage in conversations with other users. Deploying the IM advisor site built for service advisors on the second type of application client allows service advisors to quickly and conveniently access the IM advisor site and interact with their assigned clients without logging out of the second type of application client while engaging in internal chat with other service advisors.

[0036] Next, this application can provide a detailed explanation of the specific session processing procedures between the client and service consultant within the established IM site.

[0037] Figure 1 This is a flowchart illustrating a session processing method provided in an embodiment of this application. This method can be executed by the session processing device provided in this application. The session processing device can be implemented using any software and / or hardware method. Exemplarily, the session processing device can be applied to any electronic device, including but not limited to tablet computers, mobile phones (such as foldable phones, large-screen phones, etc.), wearable devices, in-vehicle devices, laptop computers, ultra-mobile personal computers (UMPCs), netbooks, personal digital assistants (PDAs), smart TVs, smart screens, high-definition TVs, 4K TVs, smart speakers, smart projectors, and other computing devices. This disclosure does not impose any limitations on the specific type of electronic device.

[0038] Specifically, such as Figure 1 As shown, the method may include the following steps: S110: Receive a session request initiated by one's own user to any other user through the target chat site, and determine the management relationship information between one's own user and the other user from the session object relationship set of the target chat site.

[0039] In this context, the "own user," as the current user who initiates a conversation with any other user by logging into the target chat site, can be either one of the two parties in the conversation, consisting of a customer and a service consultant. The target chat site can be an IM site specifically built for communication between customers and service consultants.

[0040] Therefore, when a user logs into the target chat site on their client, the target chat site analyzes the user's identity information to find multiple users with whom the user has historical conversation records or management relationships from the two parties in the conversation, which consists of customers and service consultants. The information of each user is then presented to the user through their client to support the user in initiating a corresponding conversation request to any of the users.

[0041] The account management relationship information is used to indicate the relationship between the two parties in a session (i.e., one's own user and the other's user). For example, the account management relationship between the two parties in a session can refer to a formal binding relationship explicitly designated within any business transaction platform, where one party (e.g., a customer) is followed up by the other party (e.g., a dedicated service advisor). This indicates that each service advisor in the session sends transaction card information to the customers they are responsible for following up on, or session information regarding the transaction status of various transaction targets. Specifically, the account management relationship information can be set to a preset identifier value to indicate the existence of an account management relationship, and can be set to an empty value to indicate the absence of an account management relationship.

[0042] Furthermore, the account management relationship between the two parties in the session can include various different types of account management relationships. In different types of account management relationships, the service advisor can send transaction card information for recommending different types of transaction instruments (such as stocks, options, funds, etc.) to each client they are responsible for following up with. Correspondingly, different values ​​can be set for the preset identifier to indicate different account management relationships between the two parties in the session.

[0043] Furthermore, for each registered customer and service advisor within a financial trading platform client, the CRM system typically maintains the personal information of each customer and service advisor, as well as the account management relationship between the customer and the service advisor, in real time. For example, when a customer is added to the CRM system, in addition to maintaining the customer's personal information, a dedicated service advisor is added to monitor the customer's trading activities across various trading instruments in real time, thus maintaining an account management relationship between the customer and the dedicated service advisor. Moreover, the target chat site (i.e., IM site) in this application shares the same backend services and database with the CRM system to ensure data connectivity between the IM site and the CRM system.

[0044] Therefore, to ensure timely and effective conversations between the client and service consultant on the target chat site, after the client logs in, the system continuously monitors whether the client has selected any other user to initiate a conversation. This checks whether a conversation is needed between the client and the other user. Upon detecting that the client has selected any other user to initiate a conversation, a conversation request is generated and reported to the server. The server then provides a timely and effective response to the conversation between the client and the other user.

[0045] Therefore, upon receiving a session request initiated by its own user to any other user through the target chat site, this application, in order to ensure a secure and effective session between the two parties, utilizes the data connectivity between the target chat site and the CRM system to obtain all the account management relationships maintained in the CRM system, which serve as the session object relationship set in this application. Furthermore, by analyzing the two parties involved in each account management relationship recorded in the session object relationship set, the application obtains the account management relationship information between its own user and the other user in the selected session, thereby determining whether an account management relationship exists between its own user and the other user in the selected session.

[0046] In some embodiments, in order to ensure accurate analysis of the management relationship between the two parties in a session, this application can determine the management relationship between its own user and the other party's user through the following steps: calling a pre-built user relationship service through the target chat site to query the management relationship information between its own user and the other party's user from the configured session object relationship set.

[0047] In other words, when the target chat site (i.e., IM site) and the CRM system share the same backend services and database, a user relationship service will be set up for the CRM system at the microservice layer. Through this user relationship service, all account relationships between customers and service advisors maintained in the CRM system will be fully managed.

[0048] Therefore, when this application receives a session request initiated by its own user to any other user through the target chat site, it can directly call the pre-built user relationship service from the backend service through the target chat site to initiate a corresponding user relationship query request to the specific database used to store all the management relationships between customers and service consultants maintained in the CRM system. In this way, it can quickly obtain the management relationship information between its own user and the other user of the selected session from the session object relationship set represented by all the management relationships between customers and service consultants, so as to determine whether there is a corresponding management relationship between its own user and the other user.

[0049] Furthermore, since the specific business functions performed by the clients and service advisors (e.g., account managers) on various transaction targets differ between the two parties in the conversation, this application will deploy the IM client site built for clients and the IM advisor site built for service advisors within different applications frequently used by clients and service advisors for various transaction targets, respectively, to ensure the convenience of conversation between the two parties in any business transaction scenario. This will allow them to quickly and conveniently access the corresponding IM site for conversational interaction without frequently exiting the relevant application when performing relevant business operations within that application.

[0050] For example, an IM customer site built for customers can be deployed on any financial trading platform client that supports customers in performing relevant trading operations on various trading instruments, while an IM advisor site built for service advisors can be deployed on any internal conversation tool that supports service advisors in exchanging internal information on the specific details of various trading instruments.

[0051] Therefore, when a user initiates a conversation request from a target chat site to any other user, the user first logs into the relevant application deployed on the target chat site. Within this application, the user performs corresponding operations on various transaction items. For example, a customer logs into any business transaction application to make a purchase on a specific transaction item, or a service advisor logs into an internal conversation tool to communicate with other service advisors about the details of various transaction items. Then, after logging into the relevant application deployed on the target chat site, the application continuously monitors whether the user has triggered the target chat site's entry point to determine whether logging into the target chat site is necessary to perform various conversational interactions between the two parties.

[0052] In this application, to ensure the convenience of conversations between the two parties in any business transaction scenario, upon detecting a triggering operation performed by a user on a site entry point set within an application deployed on the target chat site, a login request initiated by the user through the application deployed on the target chat site is generated and reported to the server. Then, upon receiving the login request from the user through the application deployed on the target chat site, the server can, based on the login information of the application deployed on the target chat site, perform a login-free operation for the user on the target chat site.

[0053] Specifically, upon receiving a login request from an application deployed on the target chat site, it indicates that the user needs to log in to the target chat site to interact with the other user. To ensure accurate interaction between the two parties through the target chat site, this application first obtains the specific login information entered by the user when logging in within the application deployed on the target chat site, using this as the application login information. Then, using the user's identity information from this application login information, automatic authentication is performed on the target chat site. This allows the user to log in directly and successfully without needing to re-enter login information, thus improving the efficiency of conversations between the user and other users through the target chat site.

[0054] S120, if the user relationship information is not empty, obtain the first session room between the user and the other user, and display the first session page of the first session room through the user's client. The session input controls in the first session page are in an operable state.

[0055] If the account management relationship information between the user and the other user is not empty, it indicates that one of the users is being followed up by the other, and both can perform normal conversation functions. Therefore, to ensure accurate conversation between the user and the other user, this application can obtain the personal information of both users, as well as their historical conversation information, and other conversation-related information to construct a conversation room that supports conversational interaction between the two users, serving as the first conversation room in this application. Furthermore, to achieve a successful conversation between the user and the other user, this application will set up a conversation page for conversational interaction within this first conversation room, serving as the first conversation page in this application. The conversation input controls on this first conversation page will be operable, allowing both parties to trigger these controls to perform corresponding actual conversational interactions, thereby achieving normal conversation between the two parties.

[0056] Therefore, for the first conversation room, this application can obtain various page data of the first conversation page of the first conversation room and send it to the client of its own user. The client of its own user can then display the first conversation page of the first conversation room, allowing the user to input corresponding conversation messages to the other user through the operable conversation input controls on the first conversation page, and successfully send the conversation messages to the other user. Furthermore, after receiving a conversation message reply from the other user, the application also sends the reply to the client of its own user, thus displaying the reply on the first conversation page of the first conversation room through the client of its own user, thereby achieving normal conversational interaction between the two parties.

[0057] In some embodiments, for applications deployed on the target chat site, the server typically configures corresponding push services to implement various message pushes for these applications. When a user and another user perform related conversational interactions through the first conversation page of the first conversation room, the server usually pushes the conversational messages entered by one party to the other. Therefore, to minimize the construction cost of the target chat site, this application can complete the specific conversational interactions when a user and another user perform related conversational interactions through the first conversation page of the first conversation room in the following way: obtain any conversational message entered by the user through the conversational input control in the first conversation page, and push the conversational message to the other user by reusing the client push service deployed on the target chat site.

[0058] Specifically, after the client displays the first session page of the first session room, the client can allow the client to input corresponding session messages by triggering the session input controls in the operable state of the first session page, and then send them to the other user. Thus, the server can continuously receive any session message input by the client through triggering the session input controls in the operable state of the first session page. Furthermore, for any session message input by the client, this application can directly call the message push service configured in the relevant application deployed on the target chat site as the client message push service in this application. This client message push service supports online / offline message push. Therefore, by reusing this client message push service, the session message can be successfully pushed to the other user without needing to configure an additional message push service for the target chat site, greatly reducing the construction cost of the target chat site.

[0059] S130, if the user relationship information is empty, obtain the second conversation room between the user and the other user, and display the second conversation page of the second conversation room through the user's client. The conversation input controls on the second conversation page are in an inoperable state.

[0060] If the account management relationship information between the user and the other user is empty, it indicates that one of the users does not require the other to follow up, meaning there is no need for conversational interaction regarding various transaction targets. Therefore, to achieve accurate conversation control between the two parties, this application can obtain the personal information of both users, as well as their historical conversation information, and other conversation-related information to construct a conversation room for both users that only supports browsing historical conversations and does not allow direct interaction. This serves as the second conversation room in this application. Furthermore, to achieve conversation control between the user and the other user, this application will set up a conversation page within the second conversation room for both users to browse historical conversations but not to interact directly. This serves as the second conversation page in this application, and the conversation input controls on this second conversation page will be inoperable, preventing the two parties from performing actual conversational interaction by triggering the input controls, thereby achieving conversation control between the two parties.

[0061] As can be seen from the above, for the target chat site constructed in this application, normal conversational interaction between two parties with a manager-user relationship can be supported, while conversational interaction between two parties without a manager-user relationship is prohibited, thereby achieving accurate conversational control between the two parties under the manager-user relationship.

[0062] The technical solution provided in this application, upon receiving a conversation request initiated by a user from a target chat site to any other user, can determine whether a manager-user relationship exists between the user and the other user from the conversation object relationship set of the target chat site. If so, a first conversation room between the user and the other user is obtained, and a first conversation page of the first conversation room is displayed through the user's client. The conversation input controls on the first conversation page are operable, enabling normal conversation between the two parties. If not, a second conversation room between the user and the other user is obtained, and a second conversation page of the second conversation room is displayed through the user's client. The conversation input controls on the second conversation page are inoperable, prohibiting conversation between the user and the other user. This achieves conversation control under a manager-user relationship, preventing communication and interaction between parties without a manager-user relationship in any business transaction scenario. It ensures reasonable and compliant conversations between the parties in any business transaction scenario, reducing transaction risks and providing a safer and more effective high-quality conversation service, ensuring the convenience of conversations for both parties in any business transaction scenario.

[0063] As an optional implementation scheme in this application, considering that the customer and service advisors (e.g., account managers) on both sides of the conversation implement different conversation functions for various transaction targets, and that the specific business functions performed by the customer and service advisors (e.g., account managers) on both sides of the conversation are also different for various transaction targets, the specific conversation initiation process executed by one side of the conversation when initiating a conversation request to the other side with conversation needs through the target chat site during the specific business execution process is also different.

[0064] For example, clients in a conversation can log into a business transaction application developed for specific transaction scenarios of various transaction targets to perform actual transaction operations. During the transaction execution process, they can log into an IM client site built for them, enabling them to interact with their dedicated service advisors. Service advisors, on the other hand, can use existing internal conversation tools to conduct internal communication and exchange among themselves regarding the specific details of various transaction targets. During internal chat, they can log into an IM advisor site built for them, enabling them to interact with the clients they are responsible for following up with.

[0065] Therefore, the target chat site, which is built for different types of users in the conversation, can set up different conversation initiation processes for different types of users according to their conversation needs for the other user. This allows different types of users to perform different conversation initiation operations through the target chat site to send corresponding chat requests to the other user.

[0066] In this application, the user can be either one of the two parties in a conversation, consisting of a customer and a service advisor (e.g., an account manager), and the other party can be the other user in the conversation. Next, this application will provide a detailed explanation of the specific conversation initiation process when the user initiates a conversation request to either the other party through the target chat site, taking into account both the first type of user (i.e., a customer) and the second type of user (i.e., a service advisor).

[0067] In scenario one, when the user is a type 1 user (i.e., a customer), the user's client can include a type 1 application client, and the target chat site can be an IM client site built for customers. In this case, the target chat site can be deployed within the aforementioned type 1 application client. Moreover, the type 1 application client can be a financial trading platform client that supports type 1 users in conducting transactions, such as any business trading application that supports customers in performing actual trading operations on various trading targets in investment and trading scenarios.

[0068] Specifically, to improve customer retention and activity levels in any Category 1 application client, Category 1 users are typically assigned a dedicated service advisor to provide timely and effective transaction services. Therefore, within the Category 1 application client supporting Category 1 users' transactions, a private service entry point can be set up to centralize the unique service functions configured for Category 1 users within the application client into a single private service page. This allows Category 1 users to quickly and conveniently execute various unique service functions within the private service page. This private service page can also provide Category 1 users with a convenient chat function that allows them to easily log in to the target chat site and interact with their assigned dedicated service advisor.

[0069] Furthermore, within the first-type application client that supports the first type of users in completing the target transaction, a corresponding client message push service is typically configured to push various notification messages within the first-type application client. Therefore, the first-type application client has a corresponding session list to display a message bar formed by various historical session messages between the first-type application client and other users, including but not limited to the message bar formed by any service advisor sending corresponding session messages to the first-type user through the target chat site.

[0070] Therefore, when the user is a type 1 user, the private service page and conversation list set up within the type 1 application client can both support the user to initiate corresponding chat requests to the other user indicated by the service advisor.

[0071] Figure 2 A flowchart illustrating a method for initiating a session with any other user when the user is a first-type user, as provided in this application embodiment, is shown. This method may specifically include the following steps: S210, receives an access request for a private service page sent by a first-type application client.

[0072] For the first-type application client that supports the first-type users in realizing target transactions, this application can set up a private service entry in the user center page of the first-type application client to centralize various unique service functions configured for the first-type users within the first-type application client into a single private service page. These unique service functions include a conversational function provided between the customer and the service advisor through the deployment of a target chat site.

[0073] Therefore, after a user logs into the first type of application client, the first type of application client will continuously monitor whether the user has triggered an operation on the private service entry point set in the user center page of the first type of application to determine whether the user needs to execute any unique service function within the first type of application client. Thus, when the first type of application client detects a user's trigger operation on the private service entry point, it indicates that the user has a need for a specific service function provided by the first type of application client within the private service page. The first type of application client then generates an access request for the private service page and sends it to the server. The server can then receive the access request for the private service page from the first type of application client, allowing the server to know that the user has a need for a specific service function provided by the first type of application client within the private service page, so that the server can subsequently display the accurate private service page through the user's client (i.e., the first type of application client).

[0074] S220: Based on this access request, obtain the exclusive management data of your own user.

[0075] Among them, the exclusive account manager of the first type of user is a specific service consultant who has an account manager relationship with the first type of user and can act as the other party user who has a need for conversational interaction on the target chat site.

[0076] In this application, the conversation function provided between the customer and the service advisor by deploying a target chat site within the first type of application client can be considered as one of the unique service functions configured within the first type of application client. The exclusive account management data may include account management user identification information. Upon receiving an access request from the first type of application client for the private service page, this application can, based on the identification information of the user currently logged in within the first type of application client, retrieve the corresponding account management user identification information from the conversation object relationship set connected to the backend data, thus obtaining the exclusive account management data. Based on the exclusive account management data, it can be determined whether the user has an exclusive account management user, so that, subsequently, based on whether the user has an exclusive account management user, different customer service conversation entry points can be provided to the user on the private service page to enable conversational interaction between the user and different types of customer service representatives.

[0077] S230, if the exclusive account data is not empty, send the page data of the private service page to the first type of application client based on the exclusive account data. The private service page includes the first session entry point of the other party user in the target chat site corresponding to the exclusive account data. The first session entry point is used to receive the trigger operation of the own user on the first session entry point to send a session request.

[0078] If the user's dedicated account data is not empty, it indicates that the user has a dedicated account. In this case, this application can utilize this dedicated account data and other relevant service data of unique service functions to merge and obtain the complete page data related to the aforementioned private service page. Then, the server can send the page data of the aforementioned private service page to the first type of application client (i.e., the user's client) to instruct the first type of application client to display the private service page to the user.

[0079] In the first type of application client, when displaying the private service page, it parses the exclusive administrator data to identify the corresponding user (i.e., the user's own exclusive administrator). Within the private service page, it creates a conversation card for this user. This conversation card displays the exclusive administrator's name, avatar, and other identity information, as well as a permanent conversation entry point allowing the user to interact with the exclusive administrator within the target chat site. This serves as the primary conversation entry point for the exclusive administrator within the target chat site. Furthermore, this primary conversation entry point can be used to receive triggering actions from the user to send conversation requests. That is, upon detecting a triggering action from the user to the primary conversation entry point, it indicates a conversation need between the user and the exclusive administrator. This triggers a conversation request initiated by the user through the target chat site to the user identified by the exclusive administrator, which is then sent to the server. The server then provides a timely and effective response to the conversation between the user and the exclusive administrator.

[0080] S240, if the exclusive account data is empty, send the page data of the private service page to the first type of application client based on the backup user data. The private service page includes the customer complaint entry point for the backup user.

[0081] If the dedicated account data for a user is empty, it means that the user does not have a dedicated account. In this case, this application can first assign a fallback user data set to the user. This fallback user data includes the identity information of the dedicated customer service user, who is used to handle various customer service issues for the user. Therefore, the server, for the user's dedicated customer service user, first obtains the identity information of the dedicated customer service user as the fallback user data in this application. Then, it uses the fallback user data and other relevant service data from unique service functions to merge and obtain the complete page data related to the aforementioned private service page. Finally, the server can send the page data of the aforementioned private service page to the first type of application client (i.e., the user's client) to instruct the first type of application client to display the private service page to the user.

[0082] The first type of application client, when displaying the private service page, will analyze the backup user data to determine the exclusive customer complaint user assigned to its own user, and create a customer complaint card for the exclusive customer complaint user within the private service page. The customer complaint card can display the exclusive customer complaint user's name, avatar and other identity information, as well as a customer complaint entry point that allows the own user to consult with the exclusive customer complaint user. This allows the user to subsequently communicate with the exclusive customer complaint user about various transaction targets by triggering the customer complaint entry point.

[0083] Figure 3 The flowchart below illustrates another method for initiating a session with any third-party user when the user is a first-type user, as provided in this application embodiment. This method may specifically include the following steps: S310 receives an access request for the session list sent by a first-type application client.

[0084] For the first type of application client that supports the first type of users to realize target transactions, in order to realize the various notification message push within the first type of application client, a corresponding session list will be set up. Whether it is the application notification push message of the user within the first type of application client, or the various historical session messages sent by the other user to the user through the target chat site as indicated by the service advisor, they will all be displayed in the session list in a corresponding message bar.

[0085] In this application, to achieve rapid and convenient response to the session list within the first type of application client, a message notification entry can be set up within the first type of application client to support quick navigation to the aforementioned session list. Therefore, when the first type of application client detects a trigger operation performed by its own user on the message notification entry set within it, this application can generate an access request for the session list from the first type of application client and send it to the server. The server can then receive the access request for the session list from the first type of application client, allowing the server to know that its own user has a browsing request for various pushed messages within the first type of application client, so that the corresponding session list can be displayed subsequently through the user's client (i.e., the first type of application client).

[0086] S320, based on the historical session messages between the user and any other user, a first target session list is sent to the first type of application client. The first target session list includes a second session entry point for the historical session room between the user and any other user. The second session entry point is used to receive the user's trigger operation for the second session entry point to send a session request.

[0087] When the server receives an access request from a first-type application client for the conversation list, it can determine that its user has a need to browse various pushed messages within the first-type application client. Therefore, the server can query the various historical conversation messages between its user and other users through the target chat site, create corresponding historical conversation rooms for each user with whom it has historical conversation messages, and generate corresponding message bars for each historical conversation room. This generates a corresponding first target conversation list, which is then sent to the first-type application client. The first-type application client then presents this first target conversation list to the user, allowing the user to view the corresponding historical conversation messages by clicking on any message bar within the first target conversation list.

[0088] Specifically, the first target session list can include message bars corresponding to historical session rooms between the user and any other user, serving as a second session entry point for these historical session rooms. This second session entry point can then be used to receive trigger operations from the user to send session requests. In other words, when the first type of application client detects that the user has executed a trigger operation on the message bar corresponding to a historical session room between the user and any other user in the first target session list, it indicates that the user and the other user have a need for session interaction. This triggers a session request initiated by the user through the target chat site to the other user, which is then sent to the server. The server then provides a timely and effective response to the session between the user and the other user.

[0089] Scenario Two: When the user is a Type II user (i.e., a service advisor), the user's client can include a Type II application client, and the target chat site can be an IM advisor site built for service advisors. In this case, the target chat site can be deployed within the aforementioned Type II application client. Furthermore, the Type II application client can be an instant messaging application client that supports Type II users in communicating with other users. For example, this Type II application client can be any existing conversation tool used by various service advisors for internal communication regarding various transaction targets.

[0090] Specifically, since a service advisor may be responsible for following up on the specific transactions of multiple clients for various trading instruments, this indicates that a service advisor will have conversational interaction needs with multiple clients within the target chat site. Therefore, a management chat entry point will be set up within the second type of application client for the target chat site, allowing second-type users to directly trigger this management chat entry point within the second type of application client to quickly and conveniently jump to and log in to the target chat site from the second type of application client, supporting conversational interaction between the second-type users and the various clients they are responsible for following up with.

[0091] Figure 4 A flowchart illustrating a method for initiating a session against any other user when the user is a second-type user, as provided in this application embodiment, is shown. This method may specifically include the following steps: S410 receives an access request from a second-type application client for a list of conversations within a target chat site.

[0092] For the second type of application client that supports the second type of user to conduct conversations with other users, the second type of user can quickly and conveniently jump directly from the second type of application client to the target chat site by directly triggering the chat entry of the administrator, so as to support the second type of user to conduct conversational interaction with the various clients they are responsible for following up with.

[0093] Understandably, within the target chat site built for the second type of users, it's possible to support conversational interaction between the user and the respective customer representatives they are responsible for following up with. Therefore, to achieve this conversational interaction within the target chat site, corresponding conversation lists and user lists can be set up. Specifically, the various historical conversation messages between the second type of user and each of the first type of users represented by their respective customer representatives can be displayed in corresponding message bars within the aforementioned conversation list. Furthermore, the first type of users represented by the various customer representatives followed up by the second type of user can be collectively displayed in the aforementioned user list page.

[0094] In this application, after a second-type user (represented by the user in question) logs in to the target chat site via a second-type application client, the user can choose to enter either the aforementioned session list or the aforementioned user list. Therefore, when the second-type application client detects a user's selection operation on the session list within the target chat site, it can generate an access request for the session list and send it to the server. The server can then receive this access request, allowing it to know that the user has a need to browse historical session messages between the user and other users on the target chat site deployed through the second-type application client. This enables the server to subsequently display the session list corresponding to the historical session messages between the user and the other users through the user's client (i.e., the second-type application client).

[0095] S420, based on the historical session messages between the user and any other user, a second target session list is sent to the second type of application client. The second target session list includes a third session entry point for the historical session rooms between the user and any other user. The third session entry point is used to receive the user's trigger operation for the third session entry point to send a session request.

[0096] When the server receives an access request from a second-type application client for the conversation list within the target chat site, it can determine that its user has a need to browse the various historical conversation messages between the user and other users on the target chat site deployed through the second-type application client. Therefore, the server can query the various historical conversation messages between the user and other users on the target chat site, create corresponding historical conversation rooms for each user with whom there are existing historical conversations, and generate corresponding message bars for each historical conversation room. This generates a corresponding second target conversation list, which is then sent to the second-type application client. The second-type application client then presents this second target conversation list to the user, allowing the user to view the corresponding historical conversation messages by clicking on any message bar within the second target conversation list.

[0097] Specifically, the second target session list can include message bars corresponding to historical session rooms between the user and any other user, serving as a third session entry point for these historical session rooms. This third session entry point can then be used to receive trigger actions from the user to send session requests. In other words, when the second type of application client detects that the user has executed a trigger action on the message bar corresponding to a historical session room between the user and any other user in the second target session list, this trigger action, acting as a third session entry point for the historical session room between the user and any other user in the second target session list, indicates a need for session interaction between the user and the other user. This triggers a session request initiated by the user through the target chat site to the other user, which is then sent to the server. The server then provides a timely and effective response to the session between the user and the other user.

[0098] Figure 5 The flowchart below illustrates another method for initiating a session with any third-party user when the user is a second-type user, as provided in this application embodiment. This method may specifically include the following steps: S510 receives access requests from second-type application clients for a list of users within a target chat site.

[0099] In this application, after a second-type user (represented by the user) logs in to the target chat site via a second-type application client, the second-type user can choose to enter either the aforementioned session list or the aforementioned user list. Therefore, when the second-type application client detects that the user has performed a selection operation on the user list within the target chat site, it can generate an access request for the user list within the target chat site and send it to the server. The server can then receive this access request, allowing it to know that the user has a viewing request for each first-type user represented by each client being followed by the user. This allows the server to subsequently display the user list formed by each first-type user represented by each client being followed by the user through the user's client (i.e., the second-type application client).

[0100] S520, based on the managed user data of each of the user's own users, a target user list is sent to the second type of application client. The target user list includes the user details entry of the other party user corresponding to each managed user data. The user details entry is used to receive the user's own user's trigger operation for the user details entry to enter the user details page. The user details page of each other party user includes the fourth session entry of the historical session room between the user and the other party user. The fourth session entry is used to receive the user's own user's trigger operation for the fourth session entry to send a session request.

[0101] When the server receives an access request from a second-type application client for a user list within the target chat site, it can determine that its own users have a viewing request for each first-type user represented by each client that its own users are responsible for following up with. Specifically, the managed users of its own users can be each first-type user represented by each client that its own users are responsible for following up with.

[0102] Therefore, this application can use the identity information of the user who logged in this time in the second type of application client to find the user identity information of each first type of user represented by each customer who is the second type of user and is responsible for following up in the session object relationship set of the backend data connection, and use it as the data of each managed user of the user.

[0103] Then, based on the first-type user identifier in each managed user's data, each managed user is grouped together to generate a corresponding target user list. Specifically, the user details entry point for each managed user in this target user list can be the user identifier card representing the first-type user in the managed user's data. This card can be used to receive trigger actions from the user's own user regarding the user details entry point to enter the user details page. That is, this application can send the above-mentioned target user list to a second-type application client, so that the second-type application client can present the above-mentioned target user list to its own user, allowing the user to enter the user details page of the first-type user from the target chat site's target user list by clicking on the user details entry point represented by the user identifier card of any first-type user in the target user list.

[0104] Therefore, to enable conversational interaction between the user and each user in the target user list, this application can set a fourth conversation entry point within the user details page of each user in the target user list, representing the historical conversation room between the user and that user. This fourth conversation entry point is used to receive trigger operations from the user targeting the fourth conversation entry point to send a conversation request. In other words, when the second type of application client presents the aforementioned target user list to the user, the second type of application client can detect in real time whether the user has executed a trigger operation targeting the user details entry point represented by the user identifier card of any first type of user in the target user list, to determine whether the user has a need to view the user details information of that first type of user.

[0105] Therefore, when the second type of application client detects a trigger operation by its own user targeting the user details entry represented by the user identifier card of any first type of user in the target user list, it can support the second type of application client to enter the user details page of that first type of user from the target user list of the target chat site. To this end, in order to facilitate convenient conversations between the own user and that first type of user, a conversation initiation entry can be set within the user details page of that first type of user for the historical conversation rooms between the own user and that first type of user. This serves as the fourth conversation entry in this application, and the fourth conversation entry can be used to receive the trigger operation by the own user targeting the fourth conversation entry to send a conversation request. That is, when the second type of application client detects that its own user has executed a trigger operation targeting the fourth conversation entry set in the user details page of any other user, it indicates that the own user and that other user have a need for conversational interaction. This generates a conversation request initiated by the own user to that other user through the target chat site and sends it to the server, which then provides a timely and effective response to the conversation between the own user and the other user.

[0106] The technical solution provided in this application, under two different scenarios where the user is a first-type user and a second-type user, detects in real time, through different methods, the conversation requests initiated by the user to any other user through the target chat site. This ensures the accuracy of conversation initiation within the target chat site, provides a more secure and efficient high-quality conversation service for both parties, and allows the user to quickly and conveniently enter the target chat site from their current application without frequently exiting their current application in any business transaction scenario. This ensures the convenience of chatting for both parties in any business transaction scenario.

[0107] Figure 6 This is a schematic block diagram of a session processing device provided in an embodiment of this application. Figure 6 As shown, the device 600 may include: The user management relationship determination module 610 is used to receive a session request initiated by a user to any other user through a target chat site, and determine the user management relationship information between the user and the other user from the session object relationship set of the target chat site. The first session module 620 is used to obtain the first session room between the user and the other user if the user relationship information is not empty, and to display the first session page of the first session room through the user's client. The session input controls in the first session page are in an operable state. The second conversation module 630 is used to obtain the second conversation room between the user and the other user if the user relationship information is empty, and to display the second conversation page of the second conversation room through the user's client. The conversation input controls in the second conversation page are in an inoperable state.

[0108] In some possible implementations, the user relationship determination module 610 can be specifically used for: The target chat site invokes a pre-built user relationship service to query the management relationship information between the user and the other user from the configured session object relationship set.

[0109] In some possible implementations, the self-user includes a first type of user among the two parties in the session, and the self-user's client includes a first type of application client, which is a financial trading platform client that supports the first type of user in realizing target transactions.

[0110] In some implementations, the session processing apparatus 600 may further include a first session initiation detection module. This first session initiation detection module can be used to: Receive access requests for the private service page sent by the first type of application client; Based on the access request, obtain the exclusive account management data of the user; If the exclusive user data is not empty, the page data of the private service page is sent to the first type of application client based on the exclusive user data. The private service page includes the first session entry point of the other party user in the target chat site corresponding to the exclusive user data. The first session entry point is used to receive the trigger operation of the user on the first session entry point to send a session request.

[0111] In some implementations, the first session initiation detection module can also be used for: If the exclusive account data is empty, the page data of the private service page is sent to the first type of application client based on the backup user data. The private service page includes the customer complaint entry point for the exclusive customer complaint user.

[0112] In some implementations, the first session initiation detection module can also be used for: Receive access requests for the session list sent by the first type of application client; Based on the historical session messages between the user and any other user, a first target session list is sent to the first type of application client. The first target session list includes a second session entry point for the historical session room between the user and any other user. The second session entry point is used to receive the user's trigger operation for the second session entry point to send a session request.

[0113] In some implementations, the "own user" includes a second type of user among the two parties in the session, and the client of the "own user" includes a second type of application client, which is an instant messaging application client that supports the second type of user in conducting sessions with other users.

[0114] In some implementations, the session processing apparatus 600 may further include a second session initiation detection module. This second session initiation detection module can be used to: Receive an access request from a second type of application client for the session list within the target chat site; Based on the historical session messages between the user and any other user, a second target session list is sent to the second type of application client. The second target session list includes a third session entry point for the historical session rooms between the user and any other user. The third session entry point is used to receive the user's trigger operation for the third session entry point to send a session request.

[0115] In some implementations, the second session initiation detection module can also be used for: Receive an access request from a second type of application client for the user list within the target chat site; Based on the managed user data of each of the self-users, a target user list is sent to the first type of application client. The target user list includes the user details entry of the other party user corresponding to each managed user data. The user details entry is used to receive the self-user's trigger operation for the user details entry to enter the user details page. The user details page of each other party user includes a fourth session entry of the historical session room between the self-user and the other party user. The fourth session entry is used to receive the self-user's trigger operation for the fourth session entry to send a session request.

[0116] In some implementations, the session processing apparatus 600 may further include a session message push module. This session message push module can be used for: The system acquires any conversation message entered by the user through the conversation input control on the first conversation page, and pushes the conversation message to the user by reusing the client message push service deployed on the target chat site.

[0117] In some implementations, the session processing apparatus 600 may further include a session login module. This session login module can be used for: Based on the application login information deployed on the target chat site, perform the login-free operation for the user on the target chat site.

[0118] In this embodiment, upon receiving a conversation request initiated by a user from a target chat site to any other user, the system can determine whether a manager-user relationship exists between the user and the other user based on the conversation object relationship set of the target chat site. If so, a first conversation room between the user and the other user is obtained, and a first conversation page of the first conversation room is displayed through the user's client. The conversation input controls on the first conversation page are operable, enabling normal conversation between the two users. If not, a second conversation room between the user and the other user is obtained, and a second conversation page of the second conversation room is displayed through the user's client. The conversation input controls on the second conversation page are inoperable, prohibiting conversation between the user and the other user. This achieves conversation control under a manager-user relationship, preventing communication and interaction between users without a manager-user relationship in any business transaction scenario. This ensures reasonable and compliant conversations between the two users in any business transaction scenario, reducing transaction risks and providing a safer and more effective high-quality conversation service, ensuring the convenience of conversations for both parties in any business transaction scenario.

[0119] It should be understood that the above-described apparatus embodiments and the method embodiments provided in this application can correspond to each other, and similar descriptions can be referred to the method embodiments. To avoid repetition, further details are omitted here. Specifically, Figure 6 The apparatus 600 shown can execute any of the method embodiments provided in this application, and the foregoing and other operations and / or functions of each module in the apparatus 600 are respectively for implementing the corresponding processes in the various methods provided in the embodiments of this application. For the sake of brevity, they will not be described in detail here.

[0120] The apparatus 600 of this application embodiment has been described above from the perspective of functional modules in conjunction with the accompanying drawings. It should be understood that this functional module can be implemented in hardware, in software instructions, or in a combination of hardware and software modules. Specifically, the steps of the method embodiments applied to the server in this application embodiment can be completed by integrated logic circuits in the processor hardware and / or by software instructions. The steps of the method applied in this application embodiment can be directly manifested as execution by a hardware decoding processor, or by a combination of hardware and software modules in the decoding processor. Optionally, the software module can be located in a mature storage medium in the art, such as random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, etc. This storage medium is located in memory, and the processor reads information from the memory and, in conjunction with its hardware, completes the steps in the above method embodiments.

[0121] Figure 7 A schematic block diagram of an electronic device provided in an embodiment of this application.

[0122] like Figure 7 As shown, the electronic device 700 may include: The system includes a memory 710 and a processor 720. The memory 710 stores computer programs and transfers the program code to the processor 720. In other words, the processor 720 can retrieve and run the computer program from the memory 710 to implement the methods described in the embodiments of this application.

[0123] For example, the processor 720 can be used to execute the above-described method embodiments according to instructions in the computer program.

[0124] In some embodiments of this application, the processor 720 may include, but is not limited to: General-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc.

[0125] In some embodiments of this application, the memory 710 includes, but is not limited to: Volatile memory and / or non-volatile memory. Non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. Volatile memory can be random access memory (RAM), used as an external cache. By way of example, but not limitation, many forms of RAM are available, such as Static RAM (SRAM), Dynamic RAM (DRAM), Synchronous DRAM (SDRAM), Double Data Rate SDRAM (DDR SDRAM), Enhanced SDRAM (ESDRAM), Synchronous Link DRAM (SLDRAM), and Direct Rambus RAM (DR RAM).

[0126] In some embodiments of this application, the computer program may be divided into one or more modules, which are stored in the memory 710 and executed by the processor 720 to perform the method provided in this application. The one or more modules may be a series of computer program instruction segments capable of performing a specific function, which describe the execution process of the computer program in the electronic device.

[0127] like Figure 7 As shown, the electronic device may also include: Transceiver 730, which can be connected to processor 720 or memory 710.

[0128] The processor 720 can control the transceiver 730 to communicate with other devices; specifically, it can send information or data to other devices or receive information or data sent by other devices. The transceiver 730 may include a transmitter and a receiver. The transceiver 730 may further include antennas, and the number of antennas may be one or more.

[0129] It should be understood that the various components in the electronic device are connected through a bus system, which includes a data bus, a power bus, a control bus, and a status signal bus.

[0130] This application also provides a computer storage medium storing a computer program thereon, which, when executed by a computer, enables the computer to perform the methods of the above-described method embodiments. Alternatively, this application also provides a computer program product containing instructions that, when executed by a computer, cause the computer to perform the methods of the above-described method embodiments.

[0131] When implemented using software, it can be implemented entirely or partially as a computer program product. This computer program product includes one or more computer instructions. When these computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium accessible to a computer or a data storage device such as a server or data center that integrates one or more available media. The available medium can be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., digital video disc (DVD)), or a semiconductor medium (e.g., solid-state disk (SSD)).

[0132] Those skilled in the art will recognize that the modules and algorithm steps of the various examples described in conjunction with the embodiments claimed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0133] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of modules is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple modules or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or modules may be electrical, mechanical, or other forms.

[0134] The modules described as separate components may or may not be physically separate. The components shown as modules may or may not be physical modules; that is, they may be located in one place or distributed across multiple network units. Some or all of the modules can be selected to achieve the purpose of this embodiment according to actual needs. For example, the functional modules in the various embodiments of this application may be integrated into one processing module, or each module may exist physically separately, or two or more modules may be integrated into one module.

[0135] The above are merely specific embodiments of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the technical scope disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A session processing method, characterized in that, include: Receive a session request initiated by your own user to any other user through the target chat site, and determine the management relationship information between your own user and the other user from the session object relationship set of the target chat site; If the user relationship information is not empty, obtain the first conversation room between the user and the other user, and display the first conversation page of the first conversation room through the user's client. The conversation input controls in the first conversation page are in an operable state. If the user relationship information is empty, obtain the second conversation room between the user and the other user, and display the second conversation page of the second conversation room through the user's client. The conversation input controls on the second conversation page are in an inoperable state.

2. The method according to claim 1, characterized in that, Determining the user management relationship information between the user and the other user from the session object relationship set of the target chat site includes: The target chat site invokes a pre-built user relationship service to query the management relationship information between the user and the other user from the configured session object relationship set.

3. The method according to claim 1, characterized in that, The self-users include the first type of users in both parties of the session, and the clients of the self-users include the first type of application clients, which are financial trading platform clients that support the first type of users to realize target transactions.

4. The method according to claim 3, characterized in that, Before receiving a session request initiated by one's own user to any other user through the target chat site, it also includes: Receive access requests for the private service page sent by the first type of application client; Based on the access request, obtain the exclusive account management data of the user; If the exclusive user data is not empty, the page data of the private service page is sent to the first type of application client based on the exclusive user data. The private service page includes the first session entry point of the other party user in the target chat site corresponding to the exclusive user data. The first session entry point is used to receive the trigger operation of the user on the first session entry point to send a session request.

5. The method according to claim 4, characterized in that, The method further includes: If the exclusive account data is empty, the page data of the private service page is sent to the first type of application client based on the backup user data. The private service page includes the customer complaint entry point for the backup user.

6. The method according to claim 3, characterized in that, Before receiving a session request initiated by one's own user to any other user through the target chat site, it also includes: Receive access requests for the session list sent by the first type of application client; Based on the historical session messages between the user and any other user, a first target session list is sent to the first type of application client. The first target session list includes a second session entry point for the historical session room between the user and any other user. The second session entry point is used to receive the user's trigger operation for the second session entry point to send a session request.

7. The method according to claim 1, characterized in that, The "own user" includes a second type of user among the two parties in the session, and the client of the "own user" includes a second type of application client, which is an instant messaging application client that supports the second type of user to conduct sessions with other users.

8. The method according to claim 7, characterized in that, Before receiving a session request initiated by one's own user to any other user through the target chat site, it also includes: Receive an access request from a second type of application client for the session list within the target chat site; Based on the historical session messages between the user and any other user, a second target session list is sent to the second type of application client. The second target session list includes a third session entry point for the historical session rooms between the user and any other user. The third session entry point is used to receive the user's trigger operation for the third session entry point to send a session request.

9. The method according to claim 7, characterized in that, Before receiving a session request initiated by one's own user to any other user through the target chat site, it also includes: Receive an access request from a second type of application client for the user list within the target chat site; Based on the managed user data of each of the self-users, a target user list is sent to the second type of application client. The target user list includes the user details entry of the other party user corresponding to each managed user data. The user details entry is used to receive the self-user's trigger operation for the user details entry to enter the user details page. The user details page of each other party user includes a fourth session entry of the historical session room between the self-user and the other party user. The fourth session entry is used to receive the self-user's trigger operation for the fourth session entry to send a session request.

10. The method according to claim 1, characterized in that, The method further includes: The system acquires any conversation message entered by the user through the conversation input control on the first conversation page, and pushes the conversation message to the user by reusing the client message push service deployed on the target chat site.

11. The method according to claim 1, characterized in that, The method further includes: Based on the application login information deployed on the target chat site, perform the login-free operation for the user on the target chat site.

12. A session processing apparatus, characterized in that, include: The user management relationship determination module is used to receive a session request initiated by a user on the target chat site to any other user, and determine the user management relationship information between the user and the other user from the session object relationship set of the target chat site. The first session module is used to obtain the first session room between the user and the other user if the user relationship information is not empty, and to display the first session page of the first session room through the user's client. The session input controls in the first session page are in an operable state. The second session module is used to obtain the second session room between the user and the other user if the user relationship information is empty, and to display the second session page of the second session room through the user's client. The session input controls on the second session page are in an inoperable state.

13. An electronic device, characterized in that, include: A processor and a memory, the memory being used to store a computer program, the processor being used to invoke and run the computer program stored in the memory to perform the session processing method according to any one of claims 1-11.

14. A computer-readable storage medium, characterized in that, Used to store a computer program that causes a computer to perform the session processing method as described in any one of claims 1-11.

Images