CN111224860B - Method and device for realizing communication session, electronic equipment and readable storage medium - Google Patents

Method and device for realizing communication session, electronic equipment and readable storage medium Download PDF

Info

Publication number
CN111224860B
CN111224860B CN201811426920.4A CN201811426920A CN111224860B CN 111224860 B CN111224860 B CN 111224860B CN 201811426920 A CN201811426920 A CN 201811426920A CN 111224860 B CN111224860 B CN 111224860B
Authority
CN
China
Prior art keywords
organization
interconnection
architecture
framework
client
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
CN201811426920.4A
Other languages
Chinese (zh)
Other versions
CN111224860A (en
Inventor
陈晓波
杨培艺
康师亮
李斌
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Tencent Technology Shenzhen Co Ltd
Original Assignee
Tencent Technology Shenzhen Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Tencent Technology Shenzhen Co Ltd filed Critical Tencent Technology Shenzhen Co Ltd
Priority to CN201811426920.4A priority Critical patent/CN111224860B/en
Publication of CN111224860A publication Critical patent/CN111224860A/en
Application granted granted Critical
Publication of CN111224860B publication Critical patent/CN111224860B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L51/00User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
    • H04L51/04Real-time or near real-time messaging, e.g. instant messaging [IM]

Abstract

The invention discloses a method and a device for realizing a communication session, electronic equipment and a computer readable storage medium, wherein the scheme comprises the following steps: a client where a user is located receives an interconnection organization framework loading instruction; the interconnection organization framework comprises organization members forming interconnection communication relations with the users; pulling and displaying the interconnection organization framework according to the interconnection organization framework loading instruction; receiving a selected instruction for selecting an organization member from the interconnection organization architecture; and executing a communication session with the organization members according to the selected instruction, wherein the organization members comprise members which are not joined in the contact list of the client. According to the technical scheme provided by the invention, the interconnection communication can be realized without adding the other party as a friend in advance, and the communication among different organizations is facilitated.

Description

Method and device for realizing communication session, electronic equipment and readable storage medium
Technical Field
The present invention relates to the field of instant messaging, and in particular, to a method and an apparatus for implementing a communication session, an electronic device, and a computer-readable storage medium.
Background
Communication between enterprises and external enterprises is frequent, and basically all enterprises have appeal for communication with enterprise partners. Instant Messaging (IM) has become an important means for users to communicate over a network and is increasingly deployed and applied in enterprises.
In such communication between an enterprise and an external enterprise, a contact of the external enterprise is added to a friend by the personal identity of the employee of the enterprise through instant messaging software, and then the communication is performed with the other party.
The premise of this communication is that the user account of the external enterprise contact must be known in advance, and then the other party is added as a friend. That is, there must be a process of adding the other party as a friend before communication can take place. For some relatively close partner enterprises, if more people need to communicate, the process of adding friends one by one is tedious and needs to consume more time.
Disclosure of Invention
The invention provides a method for realizing communication session, which aims to solve the problems that in the related art, communication can be carried out only by adding other parties to friends, and when the number of added people is large, the process is complicated and the time is long.
First, the present invention provides a method for implementing a communication session, where the method includes:
a client where a user is located receives an interconnection organization framework loading instruction; the interconnection organization framework comprises organization members forming interconnection communication relations with the users;
pulling and displaying the interconnection organization framework according to the interconnection organization framework loading instruction;
receiving a selected instruction for selecting an organization member from the interconnection organization architecture;
and executing a communication session with the organization members according to the selected instruction, wherein the organization members comprise members which are not joined in the contact list of the client.
Secondly, the present invention provides another method for implementing a communication session, where the method includes:
when a client where an organization member is located loads an added interconnection organization framework, a server receives a node change pulling request initiated by the client; the interconnection organization framework comprises other members which form interconnection communication relations with the organization members;
comparing the version identification carried in the node change pulling request to obtain node change information of the interconnection organization framework under the latest version identification of the server;
and controlling the client to synchronize an interconnection organization framework by returning the node change information to the client, wherein the synchronized interconnection organization framework is used for carrying out interconnection communication between the organization member and other members in the interconnection organization framework.
Third, the present invention provides an apparatus for implementing a communication session, where the apparatus includes:
the instruction receiving module is used for receiving an interconnection organization framework loading instruction through a client where a user is located; the interconnection organization framework comprises organization members forming interconnection communication relations with the users;
the framework display module is used for pulling and displaying the interconnection organization framework according to the interconnection organization framework loading instruction;
the member selection module is used for receiving a selection instruction for selecting an organization member from the interconnection organization framework;
and the session execution module is used for executing the communication session with the organization members according to the selected instruction, wherein the organization members comprise the members which are not added in the contact list of the client.
Fourth, the present invention provides an apparatus for implementing a call session, where the apparatus includes:
the request receiving module is used for receiving a node change pulling request initiated by a client at a server when the client where an organization member is located loads an added interconnection organization framework; the interconnection organization framework comprises other members which form interconnection communication relations with the organization members;
the architecture comparison module is used for comparing version identifiers carried in the node change pulling request to obtain node change information of the interconnection organization architecture under the latest version identifier of the server;
and the framework synchronization module is used for controlling the client to synchronize the interconnection organization framework by returning the node change information to the client, and the synchronized interconnection organization framework is used for carrying out interconnection communication between the organization member and other members in the interconnection organization framework.
Fifth, the present invention provides an electronic device, comprising:
a processor;
a memory for storing processor-executable instructions;
wherein the processor is configured to execute the implementation method of the communication session.
Sixthly, the present invention provides a computer-readable storage medium storing a computer program executable by a processor to perform the method for implementing the communication session.
The technical scheme provided by the embodiment of the invention can have the following beneficial effects:
according to the technical scheme provided by the invention, the client side where the user is located pulls and displays the interconnection organization framework, the interconnection organization framework comprises organization members forming interconnection communication relation with the user, the organization members can comprise members which are not added in a friend list of the user, the user can select one or more organization members from the displayed interconnection organization framework, and the client side can execute communication session between the user and the organization members according to the selected instructions of the organization members. Because the user and the organization members in the interconnection organization structure have interconnection communication relationship, the user can directly communicate with the organization members in the interconnection organization structure without adding the other party as a friend, thereby facilitating the communication among different users, and overcoming the problems that the process is complicated and the error is easy to occur because the other party needs to be added as a friend in advance when the user communicates with the external enterprise staff at present.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the invention, as claimed.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the invention and together with the description, serve to explain the principles of the invention.
FIG. 1 is a schematic illustration of an implementation environment in accordance with the present invention;
FIG. 2 is a block diagram illustrating an apparatus in accordance with an exemplary embodiment;
FIG. 3 is a flow diagram illustrating a method of implementing a communication session in accordance with an exemplary embodiment;
FIG. 4 is a representation of one form of an interconnect fabric architecture in accordance with an exemplary embodiment of the present invention;
FIG. 5 is a schematic diagram of an interface for a mobile client to display an Internet organizational structure;
FIG. 6 is a schematic diagram of an interface for a computer client to display an interconnect fabric architecture;
FIG. 7 is a detailed flowchart of step 330 in the corresponding embodiment of FIG. 3;
FIG. 8 is a detailed flowchart of step 333 in the corresponding embodiment of FIG. 7;
FIG. 9 is a schematic flow chart illustrating client-side creation of an interconnect fabric architecture in accordance with a corresponding embodiment of FIG. 3;
FIG. 10 is a diagram illustrating a create interface in accordance with an exemplary embodiment of the present invention;
FIG. 11 is a schematic view of a management page for member addition by a client;
FIG. 12 is a detailed flowchart of step 950 in a corresponding embodiment of FIG. 9;
FIG. 13 is a schematic diagram illustrating a member addition interface in accordance with an illustrative embodiment of the present invention;
FIG. 14 is a flowchart detailing step 953 of the corresponding embodiment of FIG. 12;
FIG. 15 is a flowchart detailing step 9533 of the corresponding embodiment of FIG. 14;
FIG. 16 is a schematic diagram of a two-dimensional code display interface according to an exemplary embodiment of the invention;
FIG. 17 is a schematic illustration of an interface for removal of an interconnected enterprise by the administrative side;
FIG. 18 is a flowchart showing details of step 953 in the corresponding embodiment of FIG. 12, in accordance with another embodiment;
FIG. 19 is a flowchart illustrating a method of implementation of a communication session in accordance with another exemplary embodiment;
FIG. 20 is a flowchart detailing step 1930 in a corresponding embodiment of FIG. 19;
FIG. 21 is a flowchart illustrating a process for a server to create an interconnect fabric according to the embodiment shown in FIG. 19;
FIG. 22 is a flowchart detailing step 2130 of the corresponding embodiment of FIG. 21;
FIG. 23 is a system framework diagram illustrating a method of implementing a communication session in accordance with an exemplary embodiment of the present invention;
FIG. 24 is a timing diagram of a client-side synchronized interconnection fabric from an interconnection enterprise server within the system framework shown in FIG. 23;
FIG. 25 is a timing diagram illustrating the construction of an interworking organizational structure between an interworking enterprise server and a web page manager in the system framework of FIG. 23;
FIG. 26 is a block diagram illustrating an apparatus for effectuating a communication session in accordance with an exemplary embodiment;
fig. 27 is a block diagram illustrating an apparatus for effectuating a communication session in accordance with another exemplary embodiment.
Detailed Description
Reference will now be made in detail to the exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, like numbers in different drawings represent the same or similar elements unless otherwise indicated. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present invention. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the invention, as detailed in the appended claims.
FIG. 1 is a schematic diagram illustrating an implementation environment to which the present invention relates, according to an exemplary embodiment. The implementation environment of the invention comprises a server 110 and a plurality of user terminals 130; a plurality of user terminals 120 are connected to the server 110 via a wireless network. The user terminal 130 may be a desktop computer, a laptop computer, a tablet computer, a smart phone, or other electronic devices that can be used for the social application, which is not limited herein. The social application may be in the form of an application program or a web page, and for this purpose, the interface presented by the social application to the user may be in the form of a program window or a web page.
Further, the server 110 may be a server or a cluster of multiple servers, or even a cloud computing center consisting of multiple servers.
The method for implementing the communication session provided by the present invention may be executed by the user terminal 130, and may also be understood as being executed by a client executed by the user terminal 130, for example, an instant messaging client. In the method embodiments described below, for ease of description, the method of implementing a communication session may be considered to be performed by a client.
It should be noted that the user to which the client belongs may be an employee of the enterprise. An enterprise may be considered an organization and employees of the enterprise may be considered members of the organization. Organization members that form an interconnected communication relationship with the user may be included in the interconnected organization architecture. The number of organization members is not limited, and the user and the organization members may belong to the same organization or different organizations. Wherein a business or a department may be considered an organization.
In an embodiment, the server 110 may receive information of organization members sent by different clients, and establish an interconnection communication relationship between the organization members to obtain an interconnection organization architecture. A client of a user, who is one of the organization members of the internet organization architecture, may pull and display the internet organization architecture from the server 110. The client executes a communication session between the user and a certain organization member when receiving a selection instruction of the user for selecting the organization member.
It should be explained that members of different enterprises or departments in the interconnection organization structure form interconnection communication relations, so that the organization member selected by the user can communicate with the organization member without being in a friend list of the user, and the user can communicate with the other party without adding the other party as a friend in advance, thereby facilitating the contact among the members of different organizations.
Referring to fig. 2, fig. 2 is a schematic structural diagram of an apparatus according to an embodiment of the present invention. The apparatus 200 may vary significantly depending on configuration or performance, and may include one or more Central Processing Units (CPUs) 222 (e.g., one or more processors) and memory 232, one or more storage media 230 (e.g., one or more mass storage devices) storing applications 242 or data 244. Memory 232 and storage medium 230 may be, among other things, transient or persistent storage. The program stored in the storage medium 230 may include one or more modules (not shown), each of which may include a series of instruction operations in the apparatus 200. Further, the central processor 222 may be configured to communicate with the storage medium 230, in devices200 to execute a series of instruction operations in the storage medium 230. The device 200 may also include one or more power supplies 226, one or more wired or wireless network interfaces 250, one or more input-output interfaces 258, and/or one or more operating systems 241, such as a Windows ServerTM,Mac OS XTM,UnixTM,LinuxTM,FreeBSDTMAnd so on. The steps performed by the client described in the embodiments of fig. 3, 7-9, 12, 14, 15, 18 described below may be based on the device structure shown in fig. 2.
It will be understood by those skilled in the art that all or part of the steps for implementing the following embodiments may be implemented by hardware, or may be implemented by a program instructing relevant hardware, and the program may be stored in a computer-readable storage medium, and the above-mentioned storage medium may be a read-only memory, a magnetic disk or an optical disk, etc.
Fig. 3 is a flow chart illustrating a method of effectuating a communication session in accordance with an exemplary embodiment. The method of implementing the communication session may be performed by a client that may run in the user terminal 130 of the implementation environment shown in fig. 1. As shown in fig. 3, the method for implementing the communication session may include the following steps.
In step 310, the client where the user is located receives an interconnection organization architecture loading instruction; the interconnection organization framework comprises organization members forming interconnection communication relations with the users.
It should be noted that the client may be a social networking application, such as an instant messaging application, a (picture, text, or location) sharing application, and a game application. The interconnection organization framework comprises organization members forming interconnection communication relations, and the number of the organization members is at least 2. The organization members that make up the interconnected communication relationship may belong to the same organization or may belong to different organizations. An organization may be a business, a department, or a group. The user in step 310 belongs to an organization member in the internetworking organization architecture. The interconnection organization architecture also comprises other organization members which form interconnection communication relations with the user.
Fig. 4 is a representation of a type of interconnect fabric architecture in accordance with an exemplary embodiment of the present invention. As shown in fig. 4, the interconnection department a, the interconnection department B, and the interconnection department C may respectively represent an organization, and each organization has a corresponding organization member, for example, the organization members in the interconnection department a include a member a, a member B, and a member C. An organization may be comprised of multiple groups, with multiple members under each group. For example, the department of interconnection B has a group A and a group B, and the group A can be composed of a member D, a member E and a member F. The administrator of each organization can add corresponding members to the respective organization, and the server establishes the interconnection communication among the members of different organizations, so that the members of the organizations in the interconnection organization structure can send messages to each other without any process of adding friends.
In one embodiment, the client receives the interconnect organizational structure load instruction when the user clicks on an interface element specified in the client user interface.
In another embodiment, the client may generate the interconnection fabric loading instruction at a fixed time, so that the client where the user is located may receive the interconnection fabric generated at the fixed time.
In other embodiments, the server may send an interconnection organization architecture load instruction to an organization member in the interconnection organization architecture when the interconnection organization architecture changes, so that a client where the organization member (i.e., a user) is located may receive the interconnection organization architecture load instruction. Wherein the interconnect fabric load instruction may be an interconnect fabric change notification.
In step 330, the interconnect fabric is pulled and displayed according to the interconnect fabric load instruction.
In a specific embodiment, the interconnection organization architecture may be cached locally at the client, so that the client may pull the interconnection organization architecture from the local according to the interconnection organization architecture loading instruction and display the interconnection organization architecture on the user interface.
In other embodiments, the interconnection organization architecture may be stored in the server, and the client may pull the interconnection organization architecture from the server according to the received interconnection organization architecture loading instruction, and further display the interconnection organization architecture on the user interface.
The organization members in the interconnection organization structure can be displayed in a list form, and the members of the same organization can be in the same pull-down menu.
Fig. 5 is an interface schematic diagram of a mobile phone client showing an interconnection organization architecture. As shown in fig. 5, the interconnect fabric architecture includes three organizations 501: "registration test", "red packet testing enterprise", "experience enterprise"; where the organization 501, "red packet testing enterprise" may include multiple departments 502: "campportion", "cheshire 1". The organization 501, an "experience enterprise," may include a plurality of organization members 503, such as 2 organization members 503 as shown in FIG. 5.
FIG. 6 is a schematic diagram of an interface for displaying an interconnection fabric at a computer client. Similar to fig. 5, the root node of the interconnected enterprise a includes three organizations, "entry test", "red packet test enterprise", and "experience enterprise", for example, the root node of the "entry test" includes three members.
In step 350, a selected instruction is received to select an organization member from the interconnect organizational structure.
The user may click on an organization member from the exposed internetworking organization structure, so that the client receives a selected instruction for the user to select the organization member from the internetworking organization structure. The selected instruction can carry a member of the organization selected by the user.
In step 370, a communication session is performed with the organization members, including the members not joined in the client's contact list, according to the selected instructions.
It should be noted that the contact list may also be referred to as a buddy list of the user, and the contacts in the contact list are added to the list by the user by adding the other party as a buddy. Organization members in the interworking organization architecture may not be members in the user's buddy list. According to the invention, the communication session between the user and the organization member can be realized by virtue of the interconnection communication relationship between the user and the organization member in the interconnection organization structure, and the method is not limited to whether the organization member belongs to a member in a user friend list or not.
Specifically, the client may display a chat interface where the user performs a communication session with the organization member according to the organization member indicated by the selected instruction, the user may input a message to be sent in the chat interface, and the client sends the message to the server, and the server forwards the message to the client where the organization member selected by the user is located.
As shown in fig. 6, when the client receives a command that the user clicks the "iosbob" member of the "experience enterprise", the client displays the contact corresponding to the "iosbob" member, and when the client receives a command that the user clicks the "send message" button 601, the client pops up the session interface between the user and the "iosbob" member. Therefore, the user can realize the internet communication with the iosbob without adding the iosbob member as a friend, and the operation is convenient.
In the prior art, in order to perform communication session with employees of enterprise B, employees of enterprise a need to add enterprise B as friends, if the employees of enterprise B need to contact with more employees, the contact way of the other side is obtained, and the process of adding the other side as friends is tedious and is prone to errors. The invention can establish the interconnection communication relationship between all the employees of the two enterprises through the interconnection organization architecture, so that the client of the employee of the enterprise A can communicate with the employee of the enterprise B. Of course, the client of employee a of enterprise a may also have a communication session with employee b of enterprise a.
According to the technical scheme provided by the above exemplary embodiment of the invention, the client where the user is located pulls and displays the interconnection organization architecture, the interconnection organization architecture comprises organization members forming interconnection communication relationship with the user, the organization members can comprise members not added in the user friend list, the user can select one or more organization members from the displayed interconnection organization architecture, and the client can execute the communication session between the user and the organization members according to the selected instruction of the organization members. Because the user and the organization members in the interconnection organization structure have interconnection communication relationship, the user can directly communicate with the organization members in the interconnection organization structure without adding the other party as a friend, thereby facilitating the communication among different users, and overcoming the problems that the process is complicated and the error is easy to occur because the other party needs to be added as a friend in advance when the user communicates with the external enterprise staff at present.
In an exemplary embodiment, as shown in fig. 7, the step 330 specifically includes:
in step 331, according to the interconnection organization architecture loading instruction, the client initiates a node change pull request to the server.
It should be noted that an organization may be considered as an organization node in the interconnect organization architecture, a member may be considered as a member node in the interconnect organization architecture, and a change in organization or member causes a change in organization node and member node. Such as adding/deleting organizations, adding/deleting members may cause changes to nodes in the interconnect organization's architecture.
Wherein, the node change pull request carries the version identification of the local cached interconnection organization architecture of the client. When receiving the interconnection organization framework loading instruction, the client can send a node change pull request to the server. The node change pull request is used for requesting the server to acquire changed node information, namely deleting nodes and adding nodes.
In step 332, receiving node change information returned by the server according to the node change pull request; and the node change information is obtained by comparing the version identification carried in the node change pull request with the interconnection organization structure under the latest version identification of the server by the server.
The node change information refers to node information that is different between the interconnection organization structure stored in the client and the latest interconnection organization structure of the server, that is, all changed node information, including newly added node information (including modified node information) and deleted node information. The server side pulls the version identification carried in the request according to the node change, compares the interconnection organization structure corresponding to the version identification with the interconnection organization structure under the latest version identification of the server side, and can obtain all changed node information, namely node change information.
For example, the server pulls the version number (e.g., 0005) carried in the request according to the node change, and compares the version number with the latest version number (e.g., 0007) of the server, and if the latest version number of the server is greater than the version number carried in the request, it indicates that the interconnect organization architecture stored in the server is updated compared with the local interconnect organization architecture of the client, so that all nodes that change between the interconnect organization architecture corresponding to the version number 0007 and the interconnect organization architecture corresponding to the version number 0005, including information of the changed enterprise, department, or employee, can be obtained through comparison. And the client can receive the node change information returned by the server responding to the node change pull request.
In step 333, according to the returned node change information, the client performs update display of the interconnection organization framework.
In an embodiment, the step 333 specifically includes:
and updating the locally cached interconnection organization architecture of the client according to the node change information.
And locally pulling the updated interconnection organization structure from the client to display.
Specifically, the client updates the local cached interconnection organization architecture according to the added node information and the deleted node information indicated in the node change information, and updates the identification information of the local cached interconnection organization architecture, thereby realizing synchronization between the local cached interconnection organization architecture and the latest interconnection organization architecture of the server. After the synchronization of the interconnection organization architecture is completed, the client can display the cached interconnection organization architecture, so that a user can conveniently select an organization member from the displayed interconnection organization architecture. And then the client side where the user is located can carry out conversation with the organization member selected by the user without adding the operation that the other side is a friend.
In an exemplary embodiment, as shown in fig. 8, the updating, according to the node change information, the locally cached interconnect fabric architecture of the client specifically includes the following steps:
in step 3331, comparing the node change information with the locally cached interconnection organization architecture of the client, and determining a newly added node and a node to be deleted;
the newly added nodes include added nodes and modified nodes, and the nodes can be regarded as organizations or members. The nodes to be deleted are nodes with a reduced number of interconnected organizational structures of the server compared with the locally cached interconnected organizational structures of the client. Specifically, the client may determine which nodes in the local interconnection organization architecture are to-be-deleted nodes and information of newly added nodes by comparing the node change information returned by the server with the local interconnection organization architecture.
For example, the node change information indicates that the node A, B, C disappears, the content of the node C, D changes, and the node E is added, so that the client can determine which nodes in the local cached interconnection organization structure are to be deleted, which nodes are to be modified, and which nodes need to be added according to the node change information. The nodes to be modified and the added nodes are collectively called as new added nodes.
In step 3332, the node to be deleted in the cached interconnection organization structure is marked as a deleted state;
the client may mark the node to be deleted in the locally cached interconnect organization structure as a deleted state according to the node to be deleted in the interconnect organization structure obtained in step 3331. Therefore, when the interconnection organization structure is synchronized, the dirty data needing to be deleted can be prevented from being read again.
In step 3333, the cached interconnect fabric is incrementally updated by requesting the server to pull the details of the newly added node.
The client can send a data acquisition request to the server, wherein the data acquisition request carries information of the newly added node and is used for requesting the server to pull detailed data corresponding to the newly added node. The detail data comprises names, contact ways, departments and the like of organization members corresponding to the nodes. Organization names of organizations corresponding to the nodes, and the like. And the server side returns the detailed data corresponding to the newly added node to the client side according to the information of the newly added node carried in the data acquisition request sent by the client side. And after receiving the detail data returned by the server, the client performs incremental updating on the locally cached interconnection organization architecture of the client. The incremental updating refers to that only the detail data of the added node and the detail data of the modified node are synchronized, and other nodes to be deleted and nodes which are not changed do not synchronize data.
In an exemplary embodiment, as shown in fig. 9, before the step 310, the method for implementing a communication session provided by the present invention may further include the following steps:
in step 910, according to the triggered interconnection organization architecture creating instruction, the client initiates an interconnection organization architecture creating request;
specifically, when a user clicks a creation button in a client creation interface, the client receives an interconnection organization architecture creation instruction triggered by the user, and the client responds to the received interconnection organization architecture creation instruction and sends an interconnection organization architecture creation request to the server. The interconnection organization structure creating request is used for requesting the creation of the interconnection organization structure from the server side. The request for creating an interconnection organization structure can carry the name of the interconnection organization structure input by the user.
Fig. 10 is a schematic diagram of a client creation interface according to an exemplary embodiment of the present invention, where, as shown in fig. 10, a "create" function button 101 in the client creation interface is triggered by a user, and a service receives an internetwork architecture creation request sent by the client, where the internetwork architecture creation request indicates that an internetwork of "red-envelope test enterprises" is created.
In step 930, receiving the architecture identification information returned according to the interconnection organization architecture creating request;
the architecture identification information may be a number, a name, and the like of the interconnection organization architecture. And the server generates framework identification information for creating a new interconnection organization framework according to the interconnection organization framework creating request sent by the client, and returns the framework identification information to the client sending the creating request.
In an embodiment, the server may use, according to the name of the interconnect organization architecture carried in the request for creating the interconnect organization architecture, the name of the interconnect organization architecture as the architecture identification information of the newly created interconnect organization architecture if there is no interconnect organization architecture with the same name. The fabric identification information may be considered a root node of the interconnect fabric. For example, the information of the root node may be "interconnected enterprises of the red packet testing enterprise".
In other embodiments, the server may generate an architecture number for creating a new interconnect organization architecture according to the interconnect organization architecture name carried in the interconnect organization architecture creation request, and use the architecture number as architecture identification information of the interconnect organization architecture, so that the root node of the interconnect organization architecture may be the architecture number.
In step 950, the organization members corresponding to the architecture identification information are added to trigger the server to establish the interconnection communication relationship between the organization members corresponding to the architecture identification information, so as to obtain the interconnection organization architecture.
In one embodiment, the client where the user is located may invite the client where the other user is located, and add an organization member corresponding to the architecture identification information through the client where the other user is located. The client side where other users are located can send the added organization member information to the server side.
In other embodiments, the user may also select an organization member from the contact list, and the client where the user is located adds the organization member selected by the user under the architecture identification information, that is, the architecture identification information corresponds to the organization member selected by the user. The client side can send organization member information corresponding to the framework identification information to the server side.
The server side can establish the interconnection communication relationship between the organization members corresponding to the framework identification information according to the organization member information corresponding to the framework identification information sent by one or more client sides. The interconnection communication relation means that a data transmission channel is arranged between the two. The organization members forming the interconnection communication relationship are interconnection organization frameworks.
Fig. 11 is a schematic diagram of a management page for adding members by a client, and as shown in fig. 11, the management page shows that the root node of the interconnected enterprise a includes three enterprises (i.e., three organizations) of "entry test", "red packet test enterprise", and "experience enterprise", and each enterprise has a corresponding enterprise member, i.e., an organization member. For example, an administrative user of an "experience enterprise" may add organizational members of the enterprise by clicking on the "import department/member" button 111. If necessary, the administrative user can click the "remove" button 112 to delete the individual organization member, which facilitates the maintenance of the interconnection organization architecture.
In an exemplary embodiment, as shown in fig. 12, the step 950 specifically includes:
in step 951, according to the received architecture identification information, the client jumps to a member adding interface containing the architecture identification information;
specifically, the client can jump from the creation interface to the member addition interface according to the framework identification information returned by the server. The member adding interface can display the architecture identification information, namely the root node information. Fig. 13 is a schematic diagram of a member adding interface of a client according to an exemplary embodiment of the present invention, where the client jumps from the creating interface shown in fig. 10 to the member adding interface shown in fig. 13 when receiving the architecture identification information returned by the server.
In step 952, receiving a member adding instruction triggered in the member adding interface;
in one embodiment, the member adding instruction may be an invitation instruction for instructing clients where other users are invited to add the organization member. In other embodiments, the member addition instruction may also be an in-authority member addition instruction for instructing selection of an organization member in the user contact list for addition. And when the user clicks the designated element in the member adding interface, the client receives a member adding instruction triggered by the user.
In one embodiment, as shown in fig. 13, when the "invite enterprise to join" function button 131 in the member adding interface is clicked by a user, the client receives an invitation instruction, and the client sends an interconnection relation invitation request to the server. When a button 132 for selecting the members/departments which need to be interconnected of the enterprise in the member adding interface is clicked by a user, the client receives an instruction for adding the members in the authority, and a contact list can be displayed for the user to add.
In step 953, adding the organization members under the framework identification information according to the member adding instruction, and triggering the server to establish an interconnection communication relationship between the organization members corresponding to the framework identification information, so as to obtain the interconnection organization framework.
In a specific embodiment, when the user clicks the "select members/departments of the enterprise that need to be interconnected" button 132, the client receives a member adding instruction, adds the selected organization members in the user contact list according to the instruction of the member adding instruction, displays the user contact list, and uses the designated contact selected by the user as the organization member corresponding to the architecture identification information.
In a specific embodiment, when the user clicks the "invite enterprise to join" button 131, the client receives the member adding instruction, invites the client where the other user is located to add an organization member according to the instruction of the member adding instruction, and invites the client where the other user is located, so that the client where the other user is located can select a designated contact from the contact list of the client to serve as the organization member corresponding to the architecture identification information.
For example, an enterprise may serve as an organization, and an administrator of each enterprise has a right to add members of the enterprise, so that the client of the administrator a of the enterprise may add employees of the enterprise to corresponding architecture identification information, and may invite the client of the administrator B of the enterprise and the client of the administrator C of the enterprise, and thus, the client of the administrator B of the enterprise and the client of the administrator C of the enterprise may add employees of the enterprise as organization members of the interconnected organization architecture under the architecture identification information.
The client of the administrator of each enterprise can send the information of the organization members added by the client to the server, so that the server can establish an interconnection communication relationship among all the organization members corresponding to the same architecture identification information to obtain an interconnection organization architecture.
In an embodiment, when the member adding instruction is an invitation instruction, as shown in fig. 14, the step 953 may specifically include the following steps:
in step 9531, according to the triggered invitation instruction, the client initiates an interconnection relation invitation request to a server;
specifically, when the user clicks an "invite enterprise to join" button, the client receives an invitation instruction, and the client sends an interconnection relationship invitation request to the server according to the invitation instruction triggered by the user. The request for inviting an interconnection relationship may carry architecture identification information.
In step 9531, receiving participation information returned by the server according to the interconnection relation invitation request for joining the interconnection organization architecture;
specifically, when receiving an interconnection relationship invitation request sent by a client, a server generates participation information for joining an interconnection organization architecture according to architecture identification information carried by the interconnection relationship invitation request. It should be noted that other clients can obtain the architecture identification information by identifying the participation information, and add the organization members corresponding to the architecture identification information, so that the organization members are also added to the interconnection organization architecture. The participation information can be in the form of a two-dimensional code or a link. The server side can return the generated participation information to the client side, so that the client side can receive the participation information returned by the server side.
In step 9533, the organization members corresponding to the architecture identification information are added by forwarding the participation information, and the server is triggered to establish an interconnection communication relationship between the added organization members under the architecture identification information, so as to obtain the interconnection organization architecture.
Specifically, the client where the user is located may forward the participation information to the client where the other user is located, and then the client where the other user is located may obtain the architecture identification information by recognizing the participation information, and then add the organization member corresponding to the architecture identification information in the contact list. The client side where the other users are located can send the added organization member information to the server side, and then the server side can establish the interconnection communication relationship among all organization members corresponding to the framework identification information, so that the interconnection organization framework comprising a plurality of organization members forming the interconnection communication relationship is obtained.
In an embodiment, the participation information is a two-dimensional code, and the two-dimensional code carries the architecture identification information, as shown in fig. 15, adding an organization member corresponding to the architecture identification information by forwarding the participation information includes:
in step 1501, jumping to a display interface of the two-dimensional code according to the received participation information.
The participation information may be in the form of the two-dimensional code 161, and when receiving the participation information, the client jumps to the display interface of the two-dimensional code 161. The display interface of the two-dimensional code 161 can be as shown in fig. 16.
In step 1502, the two-dimensional code is copied in response to a copy instruction triggered in the display interface.
As shown in fig. 16, a "copy invitation link" function button 162 is provided in the display interface of the two-dimensional code 161, and when the user clicks the "copy invitation link" function button 162, the client receives a copy instruction triggered by the user in the display interface, and the client copies the displayed two-dimensional code 161 in response to the copy instruction.
In step 1503, the copied two-dimensional code is forwarded to the management terminals of different organizations, so that the management terminals of different organizations create organization names corresponding to the architecture identification information by recognizing the two-dimensional code and add organization members corresponding to the organization names.
The management terminals of different organizations refer to clients where managers of different organizations are located, such as a client where an enterprise B manager is located and a client where an enterprise C manager is located. Specifically, the client where the user is located may forward the copied two-dimensional code to the client where the enterprise B administrator is located and the client where the enterprise C administrator is located. In an embodiment, the client where the user is located may forward the copied two-dimensional code to management terminals of different organizations by calling other communication software APPs, such as a mailbox.
After receiving the two-dimensional code, the management terminals of different organizations can identify the two-dimensional code to obtain the architecture identification information, create the organization name corresponding to the architecture identification information, and add the organization member corresponding to the organization name from the own contact list. The management end of different organizations can only operate the organization name and the organization member created by the management end, namely, the department and the member of the enterprise are imported and removed.
As shown in fig. 17, the interconnected enterprises of "red packet test enterprise" include: the registration test and the enterprise experience are realized by inviting management terminals of different enterprises through the two-dimensional codes, and adding employees into the interconnection organization structure to form the interconnection organization structure comprising three enterprises. The management side can also receive a trigger instruction of the management user clicking the "remove" button 171, and send a removal instruction for removing the specified enterprise to the service side, so that the service side removes the added specified enterprise.
In an embodiment, when the member addition instruction is an instruction for adding a member in the authority, as shown in fig. 18, the step 953 may further include the following steps:
in step 1801, according to the triggered member in authority addition instruction, an organization name corresponding to the architecture identification information is created.
For example, when the user clicks a "select member/department of the enterprise that needs to be interconnected" button in the member adding interface, the client receives the member adding instruction in the authority, and creates an organization name corresponding to the architecture identification information, where the organization name may be input by the user.
In step 1802, in response to a user trigger, an organization member corresponding to the organization name is added from a contact list.
For example, when the user clicks the "+" button in the user interface, the client may present the contact list in response to a user trigger. And adding an organization member corresponding to the organization name according to the contact selected by the user.
In step 1803, according to the added organization member, sending member information corresponding to the organization name to the server, and triggering the server to establish an interconnection communication relationship between the added organization members under the architecture identification information according to the member information, so as to obtain the interconnection organization architecture.
Specifically, the client may send member information of the added organization member corresponding to the organization name to the server according to the added organization member, and then the server may establish an interconnection communication relationship between the organization members corresponding to each organization name under the architecture identification information according to the member information to obtain an interconnection organization architecture.
Fig. 19 is a flow chart illustrating a method of effectuating a communication session in accordance with an exemplary embodiment. The method of implementing the communication session may be performed by a server, which may run in the server 110 of the implementation environment shown in fig. 1. As shown in fig. 19, the method for implementing the communication session may include the following steps.
In step 1910, when the client where the organization member is located loads the added interconnection organization architecture, the server receives a node change pull request initiated by the client; the interconnection organization framework comprises other members which form interconnection communication relations with the organization members;
the organization member refers to a member under a certain organization in the interconnection organization architecture, and the client where the organization member is located may be the client where the user is located in the above embodiment. And when the client side where the organization member is located can receive the loading instruction, the interconnection organization framework is loaded from the server side. Specifically, the client where the organization member is located sends a node change pull request to the server after receiving the loading instruction, so that the server receives the node change pull request sent by the client where the organization member is located. For details, reference may be made to the above embodiment of the method for implementing the communication session executed by the client.
In step 1930, the version identifier carried in the node change pull request is compared with the version identifier carried in the node change pull request to obtain node change information of the interconnection organization framework under the latest version identifier of the server;
the version identifier refers to a version identifier of the interconnection organization architecture, so that different versions of the interconnection organization architecture can be distinguished conveniently, and the version identifier can be a version number. The latest version identification of the server is a specimen identification added to the interconnection organization framework when the server modifies the framework last time. For example, the most originally generated version number of the interconnect fabric is 0001, the version number after the first update is 0002, the version number after the second update is 0003, and so on. The node change pulling request sent by the client to the server carries the version identification of the interconnection organization architecture stored locally by the client.
The node change information refers to node information which is different between the interconnection organization structure stored in the client and the latest interconnection organization structure of the server. The server pulls the version number (e.g., 0005) carried in the request according to the node change, and compares the version number with the latest version number (e.g., 0007) of the server, and if the latest version number of the server is greater than the version number carried in the request, it indicates that the interconnection organization architecture stored in the server is updated compared with the local interconnection organization architecture of the client, so that all nodes which change between the interconnection organization architecture corresponding to the version number 0007 and the interconnection organization architecture corresponding to the version number 0005, including information of changed enterprises, departments or employees, can be obtained through comparison.
In step 1950, the client is controlled to synchronize an interworking architecture by returning the node change information to the client, and the synchronized interworking architecture is used for interworking communication between the organization member and other members in the interworking architecture.
And the server returns the node change information obtained by comparison to the client initiating the node change pull request, so that the client is prompted to synchronize the interconnection organization framework according to the returned node change information. The synchronous interconnection organization structure means that the client updates the locally stored interconnection organization structure according to the node change information, so that the local interconnection organization structure is consistent with the latest interconnection organization structure of the server.
The interconnection organization framework can contain a plurality of organization information and organization member information under each organization, and the organization member information comprises contact information, departments, enterprises and the like of the organization members. The client side where the organization member is located can display the interconnection organization structure in the form of an address book on a user interface, and the address book can contain contact ways of the members under different organizations. The organization member can communicate with other organization members according to the contact information of other organization members in the address list.
In an exemplary embodiment, as shown in fig. 20, the step 1930 specifically includes:
in step 1931, the version identifier carried in the node change pull request is compared with the latest version identifier of the server, and whether the server updates the version of the interconnect organization architecture is determined;
it should be noted that the version identifier carried in the node change pull request refers to a version identifier of an interconnection organization architecture stored by the client, and the version identifier of the interconnection organization architecture stored by the client is carried in the node change pull request sent by the client to the server. Since the server modifies the interconnection organization architecture according to the configuration of the management ends of different organizations on the organization members, the interconnection organization architecture stored by the client may not be the latest generated by the server.
The latest version identification of the server refers to the version identification of the interconnection organization architecture generated by the server latest. The version identifier and the latest version identifier of the server may be version numbers, and the version number of the server interconnection organization architecture gradually increases with the modification of the interconnection organization architecture. The server compares the version identification of the client-side interconnection organization structure with the latest version identification of the server, and if the version number of the server-side interconnection organization structure is greater than the version number of the client-side interconnection organization structure, the version of the server-side interconnection organization structure can be considered to be updated, and the client side does not obtain synchronization.
In step 1932, when it is determined that the server performs version update, according to the version identifier carried in the node change pull request, comparing the node change between the interconnect organization architecture under the version identifier and the interconnect organization architecture under the latest version identifier of the server, and obtaining the node change information.
When the server is determined to perform version updating, the server compares the interconnection organization structure corresponding to the version identifier carried by the node change pull request with the interconnection organization structure under the latest version identifier of the server to obtain all the nodes which are changed, namely node change information.
In an exemplary embodiment, as shown in fig. 21, before step 1910, the method for implementing a communication session provided by the present invention may further include:
in step 2110, in response to the received interconnect fabric creation request, fabric identification information is returned.
Referring to the embodiment of the method for implementing the communication session executed by the client, the client where the user is located sends an interconnection organization architecture creation request to the server according to an interconnection organization architecture creation instruction triggered by the user. The server side responds to the received interconnection organization architecture creating request, generates architecture identification information and returns the architecture identification information to the client side which initiates the request.
In step 2130, according to the organization members added corresponding to the architecture identification information, establishing an interconnection communication relationship between the organization members corresponding to the architecture identification information, so as to obtain the interconnection organization architecture.
Specifically, when receiving the returned architecture identification information, the client initiating the request for creating the interconnection organization architecture may add an organization member corresponding to the architecture identification information from its own contact list, and the client may also forward the architecture identification information to a management end of another organization, so that the management end of the other organization adds an organization member corresponding to the architecture identification information.
It should be noted that the management terminals of different organizations may add organization members corresponding to the architecture identification information from their own contact lists, and send information of the added organization members to the server, so that the server may establish interconnection communication among the organization members according to the organization members added by the management terminals of different organizations corresponding to the architecture identification information, thereby obtaining an interconnection organization architecture.
In an exemplary embodiment, as shown in fig. 22, the step 2130 specifically includes:
in step 2131, according to the received request for inviting interconnection relationships, generating and returning participation information for joining the interconnection organization architecture; the participation information carries the architecture identification information.
Referring to the above embodiment of the method for implementing a communication session executed by a client, after receiving the architecture identification information, the client may send an invitation request of an internet organization architecture to the server when receiving an invitation instruction triggered by a user. And the server generates participation information carrying the framework identification information according to the received interconnection relation invitation request, and returns the generated participation information to the client initiating the invitation request.
In step 2132, according to the organization name newly created by the management end of the different organization under the framework identification information through the participation information and the organization member added corresponding to the organization name, establishing an interconnection communication relationship among all the organization members under the framework identification information, so as to obtain the interconnection organization framework.
Specifically, the client initiating the invitation request may forward the received participation information to the management terminals of different organizations, and then the management terminals of different organizations may obtain the architecture identification information by recognizing the participation information, create new organization names corresponding to the architecture identification information, and add organization members corresponding to the organization names from the contact list, and the management terminals of different organizations may send the organization names and the corresponding organization member information to the server, so that the server may establish the interconnection communication relationship between all organization members corresponding to the architecture identification information, and obtain the interconnection organization architecture.
Fig. 23 is a system framework diagram illustrating a method for implementing a communication session in accordance with an exemplary embodiment of the present invention. As shown in fig. 23, the system framework includes a back-end 180 and a client 190, and the back-end 180 includes a web page managing end 181, an internet enterprise server 182, and an internet enterprise DB database 183. The internet enterprise server 182 may be the server 110 in the implementation environment shown in fig. 1, and the client 190 and the web page manager 181 may be the user terminal 130 in the implementation environment shown in fig. 1.
Data transmission between the inter-enterprise server 182 and the client 190 is performed through a TCP channel. The interconnected enterprise server 182 may be comprised of one or more servers. Interconnection enterprise DB database 183 may store the generated interconnection organizational structure. The internet enterprise server 182 may generate an internet organization structure according to the configuration of the management user on the internet organization structure through the web page management terminal 181, and store the internet organization structure in the internet enterprise DB database 183.
Client 190 includes, among other things, an inter-enterprise interface layer 191, a logical and storage layer 192, and a network protocol layer 193. The enterprise interface layer 191 is configured to initiate a node change pull request for pulling the interconnect organization architecture to the interconnect enterprise server 182, obtain a list of changed nodes in the interconnect organization architecture, and obtain detail data corresponding to the changed nodes. And informing the upper address book interface 194 to display the interconnection organization structure.
The logic and storage layer 192 is used for storing the interconnection organization architecture in the local DB database of the client 190, caching the current interconnection organization architecture of the client 190 in a memory, and performing incremental synchronization and update of the interconnection organization architecture after the detail data of the changed node is pulled from the interconnection enterprise server 182.
The network protocol layer 193 is configured to send a node change pull request to the inter-enterprise server 182, request the inter-enterprise server 182 to pull node data, and receive an architecture change notification returned by the inter-enterprise server 182.
FIG. 24 is a timing diagram of a client-side synchronous interconnect organizational architecture from an interconnect enterprise server in the system framework shown in FIG. 23, wherein the business services module 1901 may include an interconnect enterprise interface layer 191, a logical and storage layer 192. The business network module 1902 may include a network protocol layer 193. As shown in fig. 24, the client-side synchronization of the interworking organizational architecture from the interworking enterprise server may include the following timing.
Sequence 1: the internet enterprise server 182 sends an architecture change notification to the client 190 according to the configuration of the management user to the internet organization architecture trigger through the web page management terminal 181; the management user may configure the internet organization framework by logging in a management webpage of the webpage management end 181.
And (2) time sequence: the business service module 1901 of the client 190 responds to the architecture change notification, initiates a pull operation of the interconnect organization architecture to the business network module 1902, and sends a node change pull request to the interconnect enterprise server 182 through the business network module 1902.
Sequence 3: the enterprise server 182 obtains node change information of the organization architecture of the internet under the latest version identifier of the enterprise server 182 by comparison according to the version identifier carried in the node change pull request, and obtains a changed node list.
Meanwhile, the business service module 1901 of the client 190 loads the interconnection organization structure stored in the DB database into the cache.
And 4, time sequence: the inter-enterprise server 182 returns the changed node list to the business network module 1902 of the client 190, and the business network module 1902 transmits the changed node list to the business service module 1901.
Sequence 5: the business service module 1901 compares the changed node list with the local interconnection organization structure of the client 190 in the cache.
Time sequence 6: the business service module 1901 of the client 190 requests the inter-enterprise server 182 to pull the node data corresponding to the changed node through the business network module 1902;
and (7) timing sequence: the inter-enterprise server 182 returns node data to the client 190 through the business network module 1902 of the client 190, and controls the business service module 1901 of the client 190 to update the inter-organization structure according to the node data.
Time sequence 8: the client 190 refreshes the display of the contact list interface on the interconnect fabric.
Timing sequence 9: the internet enterprise server 182 sends a framework change notification to the client 190 according to the modification of the internet organization framework trigger by the management user through the web page management terminal 181. The above sequence 2-8 is then repeated.
Fig. 25 is a timing diagram illustrating the construction of the interconnection organization architecture by the interconnection enterprise server and the web page manager in the system framework shown in fig. 23, and as shown in fig. 25, the construction of the interconnection organization architecture may include the following timing sequence.
Sequence 1: the web page management terminal 181 (initiator) sends an internet organization architecture creation request to the internet enterprise server 182 according to the trigger of the management user whose creation function is specified in the creation interface;
and (2) time sequence: the internet enterprise server 182 responds to the creation request and returns the root node information to the web page management terminal 181 (initiator); and the web page management end 181 (initiator) receives the root node information and jumps to the member adding interface.
And 4, time sequence: when the user clicks the "add own employee" button in the member adding interface, the web page management terminal 181 (initiator) can create an organization under the root node information, and add an organization member;
sequence 5: the web page management terminal 181 (initiator) may send the created organization name and the added organization member information to the internet enterprise server 182;
time sequence 6: the interconnection enterprise server 182 establishes interconnection communication relations among all organization members under the root node information;
and (7) timing sequence: when the user clicks an "invite enterprise to join" button in the member adding interface, the web page management terminal 181 (initiator) receives an invitation instruction; it should be added that the sequences of sequences 4 and 7 are not limited.
Time sequence 8: the web page management terminal 181 (initiator) sends an internet relation invitation request to the internet enterprise server 182;
timing sequence 9: the internet enterprise server 182 returns participation information to the web page managing terminal 181 (initiator) in response to the received internet connection invitation request. Wherein the participation information carries root node information;
time sequence 10: the web page management terminal 181 (initiator) forwards the participation information to the web page management terminals 181 (invitees) of other organizations;
sequence 11: the web page management terminal 181 (invited party) can identify the participation information by means of code scanning and the like to obtain root node information;
sequence 12: the web page management terminal 181 (invited party) creates an organization under the root node information, and configures organization members;
timing sequence 13: the web page management terminal 181 (invitee) sends organization created under the root node information and configured organization member information to the internet enterprise server 182;
timing 14: the internet enterprise server 182 establishes an internet communication relationship between the organization members according to the organization members configured by the web page management terminal 181 of different organizations, so as to obtain an internet organization framework.
It should be noted that, in an embodiment, the client 190 may serve as the web page management terminal 181 to send an internet organization architecture creation request to the internet enterprise server 182, so as to construct an internet organization architecture.
The following is an embodiment of the apparatus of the present invention, which may be used to implement an embodiment of a method for implementing a communication session executed by the above-mentioned client of the present invention. For details that are not disclosed in the embodiments of the apparatus of the present invention, refer to the embodiments of the method for implementing a communication session of the present invention.
Fig. 26 is a block diagram illustrating an implementation apparatus of a communication session, which may be used in the user terminal 130 of the implementation environment illustrated in fig. 1, and performs all or part of the steps of the implementation method of the communication session illustrated in any one of fig. 3, 7-9, 12, 14, 15, and 18 according to an exemplary embodiment. As shown in fig. 26, the apparatus includes, but is not limited to: an instruction receiving module 2610, an architecture display module 2630, a member selection module 2650, and a session execution module 2670.
The instruction receiving module 2610 is used for receiving an interconnection organization framework loading instruction through a client where a user is located; the interconnection organization framework comprises organization members forming interconnection communication relations with the users;
a framework display module 2630, configured to pull and display the interconnection organization framework according to the interconnection organization framework loading instruction;
a member selection module 2650 configured to receive a selection instruction for selecting an organization member from the interconnection organization architecture;
a session executing module 2670, configured to execute a communication session with the organization member according to the selected instruction, where the organization member includes a member that is not joined in the contact list of the client.
The implementation process of the functions and actions of each module in the above device is specifically described in the implementation process of the corresponding step in the above implementation method of the communication session, and is not described herein again.
The instruction receiving module 2610 can be, for example, a wired or wireless network interface 250 of one of the physical structures in fig. 2.
The architecture displaying module 2630, the member selecting module 2650 and the session executing module 2670 may also be functional modules for executing corresponding steps in the implementation method of the communication session. It is understood that these modules may be implemented in hardware, software, or a combination of both. When implemented in hardware, these modules may be implemented as one or more hardware modules, such as one or more application specific integrated circuits. When implemented in software, the modules may be implemented as one or more computer programs executing on one or more processors, such as programs stored in memory 232 for execution by central processor 222 of FIG. 2.
In an exemplary embodiment, the architecture display module 2630 includes: the system comprises a request initiating unit, a change information receiving unit and an architecture updating display unit.
The request initiating unit is used for initiating a node change pulling request to the server side by the client side according to the interconnection organization framework loading instruction;
the change information receiving unit is used for receiving the node change information returned by the server according to the node change pull request; the node change information is obtained by comparing the version identification carried in the node change pull request with the interconnection organization structure under the latest version identification of the server by the server;
and the architecture updating display unit is used for updating and displaying the interconnection organization architecture by the client according to the returned node change information.
In another exemplary embodiment, the architecture update display unit includes a cache update unit and a display unit;
the cache updating unit is used for updating the locally cached interconnection organization architecture of the client according to the node change information;
and the display unit is used for locally pulling the updated interconnection organization structure from the client to display.
In one exemplary embodiment, the cache update unit includes a node ratio subunit, a change node tag subunit, and an incremental update subunit.
The node comparison subunit is used for comparing the node change information with the locally cached interconnection organization architecture of the client to determine a newly added node and a node to be deleted;
the change node marking subunit is used for marking the nodes to be deleted in the cached interconnection organization structure as a deleted state;
and the increment updating subunit is used for updating the cached interconnection organization structure in an increment manner by requesting the server to pull the detail data of the newly added node.
In an exemplary embodiment, the apparatus for implementing a communication session further includes: the framework creation device comprises a framework creation initiating module, an information receiving module and a framework trigger establishing module;
the framework creation initiating module is used for initiating an interconnection organization framework creation request by the client according to the triggered interconnection organization framework creation instruction;
the information receiving module is used for receiving the framework identification information returned according to the interconnection organization framework establishing request;
and the framework triggering and establishing module is used for triggering the server to establish the interconnection communication relationship between the organization members corresponding to the framework identification information by adding the organization members corresponding to the framework identification information, so as to obtain the interconnection organization framework.
In another exemplary embodiment, the architecture trigger establishment module comprises an interface jump control unit, an adding instruction receiving unit and a member adding unit;
the interface skip control unit is used for skipping the client to a member adding interface containing the architecture identification information according to the received architecture identification information;
the adding instruction receiving unit is used for receiving a member adding instruction triggered in the member adding interface;
and the member adding unit is used for adding the organization members under the framework identification information according to the member adding instruction, and triggering the server to establish the interconnection communication relationship between the organization members corresponding to the framework identification information to obtain the interconnection organization framework.
In another exemplary embodiment, when the member adding instruction is an invitation instruction, the member adding unit includes: the system comprises an invitation initiating unit, a participation information receiving unit and a forwarding unit;
the invitation initiating unit is used for initiating an interconnection relation invitation request to the server by the client according to the triggered invitation instruction;
a participation information receiving unit, configured to receive participation information returned by the server according to the interconnection relationship invitation request and used for joining the interconnection organization architecture;
and the forwarding unit is used for adding the organization members corresponding to the architecture identification information by forwarding the participation information, and triggering the server to establish the interconnection communication relationship among the added organization members under the architecture identification information to obtain the interconnection organization architecture.
In another exemplary embodiment, the participation information is a two-dimensional code, the two-dimensional code carries the architecture identification information, and the forwarding unit includes: the system comprises a two-dimensional code display subunit, a two-dimensional code replication subunit and a two-dimensional code forwarding subunit;
the two-dimension code display subunit is used for jumping to enter a display interface of the two-dimension code according to the received participation information;
the two-dimensional code replication sub-unit is used for responding to a replication instruction triggered in the display interface and replicating the two-dimensional code;
and the two-dimension code forwarding subunit is used for forwarding the copied two-dimension codes to management ends of different organizations, so that the management ends of the different organizations create organization names corresponding to the architecture identification information by identifying the two-dimension codes and add organization members corresponding to the organization names.
In another exemplary embodiment, when the member adding instruction is an member adding instruction in the authority, the member adding unit includes an organization name creating subunit, a member adding subunit and a relationship initiation establishing subunit;
the organization name creating subunit is used for creating an organization name corresponding to the architecture identification information according to the triggered member adding instruction in the authority;
the component member adding subunit is used for responding to the triggering of the user and adding the organization members corresponding to the organization names from the contact person list;
and the relationship initiation establishing subunit is used for sending member information corresponding to the organization name to the server according to the added organization member, and triggering the server to establish an interconnection communication relationship between the added organization members under the framework identification information according to the member information to obtain the interconnection organization framework.
Fig. 27 is a block diagram illustrating an apparatus for implementing a communication session, which may be used in the service end 110 of the implementation environment shown in fig. 1, according to another exemplary embodiment, and which performs all or part of the steps of the method for implementing a communication session shown in any one of fig. 19-22. As shown in fig. 27, the apparatus includes, but is not limited to: a request receiving module 2710, an architecture alignment module 2730, and an architecture synchronization module 2750;
a request receiving module 2710, configured to receive, by a server, a node change pull request initiated by a client when the client where an organization member is located loads an added interconnection organization architecture; the interconnection organization framework comprises other members which form interconnection communication relations with the organization members;
a framework comparison module 2730, configured to compare the version identifier carried in the node change pull request to obtain node change information of the interconnect organization framework under the latest version identifier of the server;
a framework synchronization module 2750, configured to control the client to synchronize an interconnection organization framework by returning the node change information to the client, where the synchronized interconnection organization framework is used to perform interconnection communication between the organization member and other members in the interconnection organization framework.
The implementation process of the functions and actions of each module in the above device is specifically described in the implementation process of the corresponding step in the above implementation method of the communication session, and is not described herein again.
In an exemplary embodiment, architecture alignment module 2730 includes: a version comparison unit and a node change acquisition unit;
the version comparison unit is used for comparing the version identification carried in the node change pulling request with the latest version identification of the server and determining whether the server carries out version updating of the interconnection organization architecture or not;
and the node change acquiring unit is used for comparing the node change between the interconnection organization structure under the version identification and the interconnection organization structure under the latest version identification of the server according to the version identification carried in the node change pulling request when the version update of the server is determined, so as to obtain the node change information.
In another exemplary embodiment, the implementation apparatus of the communication session further includes an architecture identification returning module and a communication relationship establishing module;
the framework identification returning module is used for responding to the received interconnection organization framework establishing request and returning framework identification information;
and the communication relationship establishing module is used for establishing the interconnection communication relationship between the organization members corresponding to the architecture identification information according to the organization members added corresponding to the architecture identification information to obtain the interconnection organization architecture.
In another exemplary embodiment, the communication relationship establishing module includes: a participation information generating unit and a framework obtaining unit;
a participation information generating unit, configured to generate and return participation information for joining the interconnection organization framework according to the received interconnection relationship invitation request; the participation information carries the architecture identification information;
and the architecture obtaining unit is used for establishing the interconnection communication relationship among all the organization members under the architecture identification information according to the newly established organization names of the participation information under the architecture identification information and the organization members added corresponding to the organization names by the management ends of different organizations, so as to obtain the interconnection organization architecture.
Optionally, the present invention further provides an electronic device, where the electronic device may perform all or part of the steps of the method for implementing the communication session. The electronic device includes:
a processor;
a memory for storing processor-executable instructions;
wherein the processor is configured to execute the implementation method of the communication session described in the above exemplary embodiment.
The specific manner in which the processor of the electronic device performs operations in this embodiment has been described in detail in the embodiment of the implementation method related to the communication session, and will not be elaborated here.
In an exemplary embodiment, a storage medium is also provided that is a computer-readable storage medium, such as may be transitory and non-transitory computer-readable storage media, including instructions. The storage medium stores a computer program executable by a processor of an electronic device to perform the method of implementing the communication session described above.
It will be understood that the invention is not limited to the precise arrangements described above and shown in the drawings and that various modifications and changes may be made without departing from the scope thereof. The scope of the invention is limited only by the appended claims.

Claims (15)

1. A method for implementing a communication session, the method comprising:
a client where a user is located receives an interconnection organization framework loading instruction; the interconnection organization architecture comprises organization members forming interconnection communication relation with the users, the interconnection organization architecture comprises a plurality of organizations, and the organization members and the users belong to the same organization or different organizations;
pulling and displaying the interconnection organization framework according to the interconnection organization framework loading instruction;
receiving a selected instruction for selecting an organization member from the interconnection organization architecture;
executing a communication session with the organization members according to the selected instruction, wherein the organization members comprise members which are not joined in a contact list of the client;
before the client where the user is located receives the interconnection organization architecture loading instruction, the method further comprises the following steps:
according to a triggered interconnection organization architecture creating instruction, the client initiates an interconnection organization architecture creating request, wherein the interconnection organization architecture creating request is used for requesting a server to generate architecture identification information for creating a new interconnection organization architecture, and the architecture identification information is returned to the client which sends the interconnection organization architecture creating request back;
receiving framework identification information returned according to the interconnection organization framework establishing request;
and triggering the server to establish the interconnection communication relationship between the organization members corresponding to the architecture identification information by adding the organization members corresponding to the architecture identification information, so as to obtain the interconnection organization architecture.
2. The method of claim 1, wherein pulling and displaying the interconnect fabric according to the interconnect fabric load instruction comprises:
according to the interconnection organization framework loading instruction, the client side initiates a node change pulling request to the server side;
receiving node change information returned by the server according to the node change pulling request; the node change information is obtained by comparing the version identification carried in the node change pull request with the interconnection organization structure under the latest version identification of the server by the server;
and according to the returned node change information, the client updates and displays the interconnection organization framework.
3. The method according to claim 2, wherein the updating display of the interconnect organization architecture by the client according to the returned node change information comprises:
updating the locally cached interconnection organization architecture of the client according to the node change information;
and locally pulling the updated interconnection organization structure from the client to display.
4. The method of claim 3, wherein the updating the locally cached interconnect fabric of the client according to the node change information comprises:
comparing the node change information with the locally cached interconnection organization architecture of the client to determine a newly added node and a node to be deleted;
marking nodes to be deleted in the cached interconnection organization structure as a deleted state;
and updating the cached interconnection organization structure in an incremental manner by requesting the server to pull the detail data of the newly added node.
5. The method according to claim 1, wherein the obtaining the interconnection organization structure by adding the organization members corresponding to the architecture identification information and triggering the server to establish an interconnection communication relationship between the organization members corresponding to the architecture identification information comprises:
according to the received architecture identification information, the client jumps to a member adding interface containing the architecture identification information;
receiving a member adding instruction triggered in the member adding interface;
and adding the organization members under the framework identification information according to the member adding instruction, and triggering the server to establish the interconnection communication relationship between the organization members corresponding to the framework identification information to obtain the interconnection organization framework.
6. The method according to claim 5, wherein when the member adding instruction is an invitation instruction, adding the organization members under the architecture identification information according to the member adding instruction, and triggering a server to establish an interconnection communication relationship between the organization members corresponding to the architecture identification information to obtain the interconnection organization architecture, includes:
according to the triggered invitation instruction, the client side initiates an interconnection relation invitation request to a server side;
receiving participation information which is returned by the server side according to the interconnection relation invitation request and is used for joining the interconnection organization structure;
and triggering the server to establish an interconnection communication relationship between the added organization members under the architecture identification information by forwarding the participation information and adding the organization members corresponding to the architecture identification information, thereby obtaining the interconnection organization architecture.
7. The method according to claim 6, wherein the participation information is a two-dimensional code, the two-dimensional code carries the architecture identification information, and the step of triggering the server to establish the interconnection communication relationship between the added organization members under the architecture identification information by forwarding the participation information and adding the organization members corresponding to the architecture identification information, so as to obtain the interconnection organization architecture, comprises:
jumping to enter a display interface of the two-dimensional code according to the received participation information;
responding to a copying instruction triggered in the display interface, and copying the two-dimensional code;
and forwarding the copied two-dimension code to management ends of different organizations, so that the management ends of the different organizations create organization names corresponding to the architecture identification information by identifying the two-dimension code and add organization members corresponding to the organization names.
8. The method according to claim 5, wherein when the member adding instruction is a member in authority adding instruction, adding the organization member under the architecture identification information according to the member adding instruction, and triggering a server to establish an interconnection communication relationship between the organization members corresponding to the architecture identification information to obtain the interconnection organization architecture, comprises:
creating an organization name corresponding to the framework identification information according to the triggered member adding instruction in the authority;
adding an organization member corresponding to the organization name from a contact list in response to a user trigger;
and sending member information corresponding to the organization name to the server according to the added organization member, and triggering the server to establish an interconnection communication relationship between the added organization members under the framework identification information according to the member information to obtain the interconnection organization framework.
9. A method for implementing a communication session, the method comprising:
when a client where an organization member is located loads an added interconnection organization framework, a server receives a node change pulling request initiated by the client; the interconnection organization framework comprises other members forming interconnection communication relations with the organization members, the interconnection organization framework comprises a plurality of organizations, and the organization members and the other members belong to the same organization or different organizations;
comparing the version identification carried in the node change pulling request to obtain node change information of the interconnection organization framework under the latest version identification of the server;
controlling the client to synchronize an interconnection organization framework by returning the node change information to the client, wherein the synchronized interconnection organization framework is used for carrying out interconnection communication between the organization member and other members in the interconnection organization framework;
before the server receives a node change pull request initiated by the client when the client where the organization member is located loads the added interconnection organization architecture, the method further includes:
responding to a received interconnection organization architecture creating request, generating architecture identification information for creating a new interconnection organization architecture and returning the architecture identification information;
and establishing an interconnection communication relationship between the organization members corresponding to the architecture identification information according to the organization members added corresponding to the architecture identification information to obtain the interconnection organization architecture.
10. The method according to claim 9, wherein the comparing, with respect to the version identifier carried in the node change pull request, to obtain node change information of the interconnect organization architecture under the latest version identifier of the server includes:
comparing the version identification carried in the node change pulling request with the latest version identification of the server, and determining whether the server carries out version updating of an interconnection organization framework;
and when the server is determined to be updated, comparing the node change between the interconnection organization structure under the version identification and the interconnection organization structure under the latest version identification of the server according to the version identification carried in the node change pulling request to obtain the node change information.
11. The method according to claim 9, wherein the establishing, according to the organization member added corresponding to the architecture identification information, an interconnection communication relationship between the organization members corresponding to the architecture identification information to obtain the interconnection organization architecture comprises:
generating and returning participation information for joining the interconnection organization framework according to the received interconnection relation invitation request; the participation information carries the architecture identification information;
and establishing an interconnection communication relationship among all organization members under the framework identification information according to the newly established organization names of the participation information under the framework identification information and the organization members added corresponding to the organization names by the management terminals of different organizations, so as to obtain the interconnection organization framework.
12. An apparatus for effectuating a communication session, the apparatus comprising:
the instruction receiving module is used for receiving an interconnection organization framework loading instruction through a client where a user is located; the interconnection organization architecture comprises organization members forming interconnection communication relation with the users, the interconnection organization architecture comprises a plurality of organizations, and the organization members and the users belong to the same organization or different organizations;
the framework display module is used for pulling and displaying the interconnection organization framework according to the interconnection organization framework loading instruction;
the member selection module is used for receiving a selection instruction for selecting an organization member from the interconnection organization framework;
the session execution module is used for executing the communication session with the organization members according to the selected instruction, wherein the organization members comprise the members which are not added in the contact list of the client;
the system comprises an architecture creation initiating module, a client and a server, wherein the architecture creation initiating module is used for initiating an interconnection organization architecture creation request by the client according to a triggered interconnection organization architecture creation instruction, the interconnection organization architecture creation request is used for requesting the server to generate architecture identification information for creating a new interconnection organization architecture, and returning the architecture identification information to the client which sends the interconnection organization architecture creation request back;
the information receiving module is used for receiving the framework identification information returned according to the interconnection organization framework establishing request;
and the framework triggering and establishing module is used for triggering the server to establish the interconnection communication relationship between the organization members corresponding to the framework identification information by adding the organization members corresponding to the framework identification information, so as to obtain the interconnection organization framework.
13. An apparatus for implementing a conversation session, the apparatus comprising:
the request receiving module is used for receiving a node change pulling request initiated by a client at a server when the client where an organization member is located loads an added interconnection organization framework; the interconnection organization framework comprises other members forming interconnection communication relations with the organization members, the interconnection organization framework comprises a plurality of organizations, and the organization members and the other members belong to the same organization or different organizations;
the architecture comparison module is used for comparing version identifiers carried in the node change pulling request to obtain node change information of the interconnection organization architecture under the latest version identifier of the server;
the framework synchronization module is used for controlling the client to synchronize an interconnection organization framework by returning the node change information to the client, and the synchronized interconnection organization framework is used for carrying out interconnection communication between the organization member and other members in the interconnection organization framework;
the framework identification returning module is used for responding to the received interconnection organization framework creating request, generating framework identification information for creating a new interconnection organization framework and returning the framework identification information;
and the communication relationship establishing module is used for establishing the interconnection communication relationship between the organization members corresponding to the architecture identification information according to the organization members added corresponding to the architecture identification information to obtain the interconnection organization architecture.
14. An electronic device, characterized in that the electronic device comprises:
a processor;
a memory for storing processor-executable instructions;
wherein the processor is configured to perform a method of implementing a communication session according to any one of claims 1 to 11.
15. A computer-readable storage medium, on which a computer program is stored which, when being executed by a processor, carries out a method of carrying out a communication session according to any one of claims 1 to 11.
CN201811426920.4A 2018-11-27 2018-11-27 Method and device for realizing communication session, electronic equipment and readable storage medium Active CN111224860B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201811426920.4A CN111224860B (en) 2018-11-27 2018-11-27 Method and device for realizing communication session, electronic equipment and readable storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201811426920.4A CN111224860B (en) 2018-11-27 2018-11-27 Method and device for realizing communication session, electronic equipment and readable storage medium

Publications (2)

Publication Number Publication Date
CN111224860A CN111224860A (en) 2020-06-02
CN111224860B true CN111224860B (en) 2021-10-15

Family

ID=70828001

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201811426920.4A Active CN111224860B (en) 2018-11-27 2018-11-27 Method and device for realizing communication session, electronic equipment and readable storage medium

Country Status (1)

Country Link
CN (1) CN111224860B (en)

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112073300B (en) * 2020-08-28 2022-02-25 北京五八信息技术有限公司 Group data synchronization method and device
CN113139786A (en) * 2021-04-12 2021-07-20 天津中新智冠信息技术有限公司 Organizational structure interconnection method and device, electronic equipment and storage medium
CN113965537B (en) * 2021-10-13 2023-03-31 成都华唯科技股份有限公司 Cross-mechanism instant messaging method, server, terminal and readable storage medium

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1487706A (en) * 2003-07-17 2004-04-07 腾讯科技(深圳)有限公司 Method, system and control process for enterprise to communicate timely
CN105099869A (en) * 2014-05-07 2015-11-25 三竹资讯股份有限公司 Message transmission device and method with multiple organization structures
CN105099876A (en) * 2015-06-26 2015-11-25 阿里巴巴集团控股有限公司 Methods and devices for managing data of group users and maintaining instant messaging group
CN107171856A (en) * 2017-06-21 2017-09-15 珠海信达九州科技有限公司 A kind of method that instant communicating system organizational structure quickly updates
CN108418747A (en) * 2018-02-23 2018-08-17 平安科技(深圳)有限公司 Method for sending information, device, equipment based on instant messaging and storage medium

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8082301B2 (en) * 2006-11-10 2011-12-20 Virtual Agility, Inc. System for supporting collaborative activity
US9684937B2 (en) * 2014-01-07 2017-06-20 International Business Machines Corporation Allowing a user to view network contacts of other users when visiting an environment of a different organization
US9356895B2 (en) * 2014-05-07 2016-05-31 Mitake Information Corporation Message transmission system and method for a structure of a plurality of organizations
US20150326511A1 (en) * 2014-05-07 2015-11-12 Mitake Information Corporation Message transmission system and method suitable for individual and organization
CN104539511A (en) * 2014-12-05 2015-04-22 蓝信工场(北京)科技有限公司 Method and system for displaying own group when entering client

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1487706A (en) * 2003-07-17 2004-04-07 腾讯科技(深圳)有限公司 Method, system and control process for enterprise to communicate timely
CN105099869A (en) * 2014-05-07 2015-11-25 三竹资讯股份有限公司 Message transmission device and method with multiple organization structures
CN105099876A (en) * 2015-06-26 2015-11-25 阿里巴巴集团控股有限公司 Methods and devices for managing data of group users and maintaining instant messaging group
CN107171856A (en) * 2017-06-21 2017-09-15 珠海信达九州科技有限公司 A kind of method that instant communicating system organizational structure quickly updates
CN108418747A (en) * 2018-02-23 2018-08-17 平安科技(深圳)有限公司 Method for sending information, device, equipment based on instant messaging and storage medium

Also Published As

Publication number Publication date
CN111224860A (en) 2020-06-02

Similar Documents

Publication Publication Date Title
US9536228B2 (en) Contact management systems
US7454465B2 (en) Real-time collaboration and communication in a peer-to-peer networking infrastructure
CN111224860B (en) Method and device for realizing communication session, electronic equipment and readable storage medium
US20130246525A1 (en) Instant transition from a public conversation thread to a private chat or instant message environment
US9245251B2 (en) Managing electronic sticky notes
CN109923571A (en) Live conference for the channel in team collaboration's tool
US20090248824A1 (en) Theme-based instant messaging communications
JP2017517063A (en) Instant messaging system and method
JP2010533906A (en) Method, system and apparatus for sorting topics within a group
WO2010027577A1 (en) Content sharing and instant messaging
CN112437004B (en) Information processing method, information processing device, electronic equipment and storage medium
US8543654B2 (en) Contextual conversation framework
US11265183B1 (en) Asynchronous meeting management for collaboration solutions
US9621494B2 (en) Generating instant messaging contacts for customer relationship management systems
CN110213156B (en) Cross-center group instant messaging method and system
CN103703767A (en) Video conference realizing method, business management device and video conference system
CN111586672B (en) Network call information processing method and device
CN113761510A (en) User information processing method, device, equipment and medium thereof
US11336701B2 (en) Creation and sharing of contacts groups between communication participants
US20230082425A1 (en) Communication method, related apparatus, device, and storage medium
Dinatha et al. Data exchange service using google drive API
CN110620672B (en) Multi-person session data processing method and device, computer equipment and storage medium
WO2023020092A1 (en) Multi-person collaboration-based resource processing method, apparatus and system
CN112332995B (en) Conference state updating method and device, computer equipment and storage medium
CN114527913B (en) Message display method and device and terminal equipment

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
REG Reference to a national code

Ref country code: HK

Ref legal event code: DE

Ref document number: 40023670

Country of ref document: HK

SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant