Object sharing method and device, object display method and device, electronic equipment and medium

Abstract

The invention provides an object sharing method and device, an object display method and device, electronic equipment and a medium, and relates to the technical field of data processing, in particular to the field of instant messaging. The specific implementation scheme is as follows: in response to detection that a shared party performs a predetermined operation on an interaction window, obtaining window information of the interaction window and an identifier of the shared party; wherein the interaction window is generated based on the target object shared by the sharing party in the active sharing direction; determining a first system where the active sharing party is located and a second system where the shared party is located according to the window information and the identifier of the shared party; obtaining object description of the target object based on the first system; querying whether the shared party has a target object based on the second system to obtain a query result; and outputting the object description and the query result.

Description

Technical Field

[0001] The present disclosure relates to the field of data processing technology, and in particular to the field of instant messaging. More specifically, the present disclosure provides an object sharing method, an object display method, an object sharing device, an object display device, an electronic device, a storage medium, and a computer program product. Background Art

[0002] In work and life, users sometimes send emails, files and other objects to other users. For example, employees of a company send emails to each other, and friends send files to each other. Summary of the invention

[0003] The present disclosure provides an object sharing method, an object display method, an object sharing device, an object display device, an electronic device, a storage medium, and a computer program product.

[0004] According to one aspect of the present disclosure, an object sharing method is provided, comprising: in response to detecting that a shared party performs a predetermined operation on an interactive window, obtaining window information of the interactive window and an identifier of the shared party; wherein the interactive window is generated based on a target object shared by an active sharer to the shared party; determining a first system in which the active sharer is located and a second system in which the shared party is located based on the window information and the identifier of the shared party; obtaining an object description of the target object based on the first system; querying whether the shared party has the target object based on the second system to obtain a query result; and outputting the object description and the query result.

[0005] According to another aspect of the present disclosure, an object display method is provided, including: obtaining an object description of a target object, and a query result characterizing whether a shared party has the target object; determining operation options for use by the shared party based on the query result; and rendering the object description and the operation options; wherein the object description and the query result are obtained based on the above-mentioned object sharing method.

[0006] According to another aspect of the present disclosure, an object sharing device is provided, comprising: a first acquisition module, a system determination module, a second acquisition module, a query module and a first output module. The first acquisition module is used to obtain the window information of the interactive window and the identifier of the shared party in response to detecting that the shared party performs a predetermined operation on the interactive window, wherein the interactive window is generated based on the target object shared by the active sharing direction to the shared party. The system determination module is used to determine the first system where the active sharing party is located and the second system where the shared party is located based on the window information and the identifier of the shared party. The second acquisition module is used to obtain the object description of the target object based on the first system. The query module is used to query whether the shared party has the target object based on the second system to obtain the query result. The first output module is used to output the object description and the query result.

[0007] According to another aspect of the present disclosure, an object display device is provided, comprising: a fifth acquisition module, an option determination module and a rendering module. The fifth acquisition module is used to obtain an object description of a target object and a query result indicating whether the shared party has the target object. The option determination module is used to determine an operation option for the shared party to use based on the query result. The rendering module is used to render the object description and the operation option, wherein the object description and the query result are obtained based on the above-mentioned object sharing device.

[0008] According to another aspect of the present disclosure, an electronic device is provided, comprising: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor so that the at least one processor can execute the method provided by the present disclosure.

[0009] According to another aspect of the present disclosure, a non-transitory computer-readable storage medium storing computer instructions is provided, wherein the computer instructions are used to enable a computer to execute the method provided by the present disclosure.

[0010] According to another aspect of the present disclosure, a computer program product is provided, including a computer program, and when the computer program is executed by a processor, the method provided by the present disclosure is implemented.

[0011] It should be understood that the content described in this section is not intended to identify the key or important features of the embodiments of the present disclosure, nor is it intended to limit the scope of the present disclosure. Other features of the present disclosure will become easily understood through the following description. BRIEF DESCRIPTION OF THE DRAWINGS

[0012] The accompanying drawings are used to better understand the present solution and do not constitute a limitation of the present disclosure.

[0013] Figure 1 is a schematic diagram of an application scenario of an object sharing method, an object display method and a device according to an embodiment of the present disclosure;

[0014] Figure 2 is a schematic flow chart of an object sharing method according to an embodiment of the present disclosure;

[0015] Figure 3 is a schematic diagram of an object sharing method according to an embodiment of the present disclosure;

[0016] Figure 4 is a schematic diagram of an object sharing method according to another embodiment of the present disclosure;

[0017] Figure 5 is a schematic diagram of an object sharing method according to another embodiment of the present disclosure;

[0018] Figure 6 is a schematic diagram of an object sharing method according to another embodiment of the present disclosure;

[0019] Figure 7 A schematic flowchart of an object display method according to an embodiment of the present disclosure;

[0020] Figure 8 is a schematic structural block diagram of an object sharing device according to an embodiment of the present disclosure;

[0021] Fig. 9 is a schematic structural block diagram of an object display device according to an embodiment of the present disclosure; and

[0022] Fig.10 It is a structural block diagram of an electronic device used to implement the object sharing method and / or object display method of the embodiments of the present disclosure. DETAILED DESCRIPTION

[0023] The following is a description of exemplary embodiments of the present disclosure in conjunction with the accompanying drawings, including various details of the embodiments of the present disclosure to facilitate understanding, which should be considered as merely exemplary. Therefore, it should be recognized by those of ordinary skill in the art that various changes and modifications may be made to the embodiments described herein without departing from the scope and spirit of the present disclosure. Similarly, for the sake of clarity and conciseness, descriptions of well-known functions and structures are omitted in the following description.

[0024] In the technical solution of the present disclosure, the collection, storage, use, processing, transmission, provision and disclosure of user personal information involved are in compliance with the provisions of relevant laws and regulations and do not violate public order and good morals.

[0025] In the technical solution of the present disclosure, the user's authorization or consent is obtained before obtaining or collecting the user's personal information.

[0026] In work and life, users sometimes send emails, files and other objects to other users. For example, in enterprises, many business approvals are based on emails. However, with the advent of the information age, everyone's mailbox will have a lot of emails. At the same time, due to problems such as inaccurate search, the approver may not be able to find the emails to be processed, which will affect the normal progress of the business.

[0027] In addition, there are multiple mailbox systems in an enterprise. Since different mail systems are deployed on different servers, there is physical data isolation; or even if two mail systems are deployed on the same server, one mail system does not have the authority to view, modify, and perform other operations on the data of another mail system. Therefore, the data between the various mail systems is generally not interoperable. Therefore, when a user in the first mail system shares an email that he or she has sent or received with a user in the second mail system, since the second mail system lacks detailed information about the email, it is unable to display the specific content of the email to the shared party, such as the body of the email. In other words, sharing emails across systems will cause the shared party to be unable to browse the email details.

[0028] The disclosed embodiment aims to provide an object sharing method. After the active sharing party sends an email to the shared party, an interactive window can be generated based on the target object shared by the active sharing party to the shared party, and then the interactive window can be displayed to the shared party. In response to the shared party performing a predetermined operation on the interactive window, the window information of the interactive window and the identifier of the shared party can be obtained, and then the first system where the active sharing party is located and the second system where the shared party is located can be determined based on the window information and the identifier of the shared party. Next, the object description of the target object can be obtained based on the first system, and the shared party can be queried based on the second system whether it has the target object to obtain the query result. Then the object description and the query result can be output. In this way, even if the data of the first system and the second system are not interoperable, the object description can still be obtained from the first system where the active sharing party is located, and then rendered. Therefore, in the scenario of cross-system email sharing, the shared party can browse the email details normally or further process the email. In addition, the shared party does not need to search for the email in his own mailbox, but can directly browse or further process the email based on the interactive window, thereby improving the processing efficiency and ensuring the normal progress of the business.

[0029] The object sharing method and object display method provided by the embodiments of the present disclosure may be applied to an IM (Instant Message) platform.

[0030] The technical solution provided by the present disclosure will be described in detail below with reference to the accompanying drawings and specific embodiments.

[0031] Figure 1 It is a schematic diagram of an application scenario of an object sharing method, an object display method and an apparatus according to an embodiment of the present disclosure.

[0032] It should be noted that Figure 1 What is shown is merely an example of a system architecture to which the embodiments of the present disclosure can be applied, in order to help those skilled in the art understand the technical content of the present disclosure, but it does not mean that the embodiments of the present disclosure cannot be used in other devices, systems, environments or scenarios.

[0033] like Figure 1 As shown, the system architecture 100 according to this embodiment may include terminal devices 101, 102, 103, a network 104 and a server 105. The network 104 is used to provide a medium for communication links between the terminal devices 101, 102, 103 and the server 105. The network 104 may include various connection types, such as wired and / or wireless communication links, etc.

[0034] Users can use terminal devices 101, 102, 103 to interact with server 105 through network 104 to receive or send messages, etc. Terminal devices 101, 102, 103 can be various electronic devices with display screens and supporting web browsing, including but not limited to smart phones, tablet computers, laptops, desktop computers, etc.

[0035] The server 105 may be a server that provides various services, such as a background management server (only an example) that provides support for websites browsed by users using the terminal devices 101, 102, and 103. The background management server may analyze and process the received data such as user requests, and feed back the processing results to the terminal device.

[0036] For example, if the active sharer shares an email with the shared party through the front-end page of the terminal device 101, the server 105 can generate an interactive window and return the interactive window to the front-end page of the terminal device 101 so that the shared party can view and click the interactive window. In addition, if the shared party clicks the interactive window, the server 105 can also obtain the object details and query results and then return them to the terminal device 101. The terminal device 101 can render through the front-end page so that the shared party can view the object or further process the shared target object.

[0037] It should be noted that the object sharing method provided in the embodiment of the present disclosure can generally be executed by the server 105. Accordingly, the object sharing device provided in the embodiment of the present disclosure can generally be set in the server 105. The object display method provided in the embodiment of the present disclosure can generally be executed by the terminal devices 101, 102, 103. Accordingly, the object display device provided in the embodiment of the present disclosure can generally be set in the terminal devices 101, 102, 103.

[0038] It should be understood that Figure 1 The number of terminal devices, networks and servers in the embodiment is only for illustration. Any number of terminal devices, networks and servers may be provided according to implementation requirements.

[0039] Figure 2 is a schematic flowchart of an object sharing method according to an embodiment of the present disclosure.

[0040] like Figure 2 As shown, the object sharing method 200 may be executed by a backend service, and the backend service may be deployed on a server. The object sharing method 200 may include operations S210 to S250.

[0041] In operation S210, in response to detecting that the recipient party performs a predetermined operation on the interactive window, window information of the interactive window and an identifier of the recipient party are acquired; wherein the interactive window is generated based on a target object shared by the active sharing direction to the recipient party.

[0042] For example, the target object may be an email, a file, a resource, etc., and this embodiment does not limit the target object. Taking the target object as an email as an example, the active sharing party may be the sender or recipient of the email, the shared party may be the recipient of the email, or other users unrelated to the sender or recipient of the email, and the shared party may be a single user or a user group.

[0043] For example, after the active sharer chooses to share an email with a specific recipient through the front-end page, an interactive window can be generated and displayed to the recipient. The recipient can click, circle or perform other predetermined operations on any area or predetermined area in the interactive window through the front-end page. The front-end page can obtain the window information of the interactive window and the identifier of the recipient, and then send it to the back-end service so that the back-end service obtains this information.

[0044] For example, the interactive window carries window information, and the window information may include at least one of the following: the email address of the active sharer, the identifier of the active sharer, the email identifier, the sharing type, the predetermined parameters, etc. The predetermined parameters may represent the system identifier of the active sharer. For example, if the predetermined parameter is "from Server 1", it means that the active sharer is in system 1; if the predetermined parameter is "from Server 2", it means that the active sharer is in system 2.

[0045] In operation S220, the first system where the active sharing party is located and the second system where the shared party is located are determined according to the window information and the identifier of the shared party.

[0046] For example, the active sharing party is a user using the first system, and the shared party is a user using the second system. The first system and the second system can be the same system or different systems. When the first system and the second system are different systems, the first system and the second system can be deployed on different servers, and there is physical data isolation, resulting in data incommunicability between the first system and the second system. Or the first system and the second system are deployed on the same server, but one mail system does not have the authority to view, modify, and perform other operations on the data of the other mail system, so the data between the first system and the second system is incommunicable.

[0047] The first system where the active sharer of the interactive window is located can be queried based on the active sharer's ID, email ID, predetermined parameters and other information in the window information. The second system where the shared party is located can be determined based on the shared party's ID and the corresponding relationship between the ID and the system.

[0048] In operation S230, an object description of the target object is acquired based on the first system.

[0049] For example, the first system may be called to obtain the object description of the target object, or a request may be sent to the first system to obtain the object description of the target object returned by the first system.

[0050] In operation S240, the second system is queried to determine whether the shared party has a target object, and a query result is obtained.

[0051] For example, the second system may be called to obtain the object description of the target object, or a request may be sent to the second system to obtain the query result returned by the second system. During the query process, the target object identifier, the time and type of the target object may be used to query the database of the second system to determine whether the shared party has the target object.

[0052] In operation S250, the object description and the query result are output.

[0053] For example, the object description and query results are output to the front-end page, and then the front-end page is rendered, thereby displaying the object description, query results and other information to the shared party.

[0054] According to the object sharing method provided by the embodiment of the present disclosure, after the active sharing party sends an email to the shared party, an interactive window can be generated based on the target object shared by the active sharing party to the shared party, and then the interactive window can be displayed to the shared party. In response to the shared party performing a predetermined operation on the interactive window, the window information of the interactive window and the identifier of the shared party can be obtained, and then the first system where the active sharing party is located and the second system where the shared party is located can be determined based on the window information and the identifier of the shared party. Next, the object description of the target object can be obtained based on the first system, and the shared party can be queried based on the second system whether it has the target object to obtain the query result. Then the object description and the query result can be output. In this way, even if the data of the first system and the second system are not interoperable, the object description can still be obtained from the first system where the active sharing party is located, and then rendered. Therefore, in the scenario of cross-system email sharing, the shared party can browse the email details normally or further process the email. In addition, the shared party does not need to search for the email in his own mailbox, but can directly browse or further process the email based on the interactive window, thereby improving the processing efficiency and ensuring the normal progress of the business.

[0055] In some embodiments, the interactive window can be used to display some information of the target object. Taking the target object as an email as an example, the interactive window can be used to display at least one of the following: email subject, email summary, recipient, sender, email content, etc. The email content can be displayed in image form rather than text form. In this way, rich text, pictures, tables and other elements in the email can be displayed, making it convenient for the shared party to intuitively see the specific content of the email, making the information communication more comprehensive and easier for the shared party to understand.

[0056] According to another embodiment of the present disclosure, after the active sharing party triggers a sharing operation for sharing an interactive window, a predetermined parameter may be added to the window information of the interactive window, where the predetermined parameter represents the system identifier of the active sharing party.

[0057] For example, an enterprise uses multiple mailbox systems, and different users are in different mailbox systems. For example, the first user is in the first system, and the second user is in the second system. If the first user triggers a sharing operation, a predetermined parameter "from Server 1" can be added to the window information of the interaction window. If the second user triggers a sharing operation, a predetermined parameter "from Server 2" can be added to the window information of the interaction window. In some embodiments, the predetermined parameters of a specific system (such as the first system used) can adopt default values, and the default value can be empty. In this way, although the window information does not explicitly mark the system as the first system, the default value can still be different from the predetermined parameters of other systems, thereby distinguishing each system.

[0058] According to another embodiment of the present disclosure, the above process of determining the first system in which the active sharing party is located and the second system in which the shared party is located based on the window information and the identifier of the shared party may include the following operations: determining the first system from multiple systems based on predetermined parameters in the window information, and then determining the second system from multiple systems based on the identifier of the shared party.

[0059] For example, a predetermined parameter is read from the window information, such as "from Server 1", and then the first system is determined by the identifier therein. For example, a correspondence between each shared party and the system is pre-established, and then the second system is determined based on the correspondence and the identifier of the shared party.

[0060] This embodiment achieves accurate identification and differentiation of different systems by adding predetermined parameters to the window information, so that the source clarity of the shared content can be maintained in a multi-system environment, thereby accurately identifying the systems where the active sharer and the shared party are located.

[0061] According to another embodiment of the present disclosure, the process of obtaining the object description of the target object based on the first system includes: determining whether the shared party has the authority to view the object description based on the window information and the information in the predetermined database. If the shared party has the authority, the object description of the target object can be obtained based on the first system. If the shared party does not have the authority, the object description of the target object may no longer be obtained, and a prompt message is returned to the front-end page, prompting the shared party that it does not have the authority to view through the front-end page.

[0062] For example, after the shared party receives the shared interactive window, he clicks on the interactive window and jumps to another page. At the same time, the front-end page reads the window information from the window information and requests the back-end service. The back-end service can compare the window information with the information in the predetermined database to see if they are consistent. If they are consistent, it means that the authentication is successful and the shared party has the authority to view the object description. Otherwise, it means that the authentication is not successful and the shared party does not have the authority to view the object description.

[0063] According to another embodiment of the present disclosure, the above process of obtaining the query result by querying whether the shared party has the target object based on the second system may include: determining the basic identifier of the target object based on the window information. Then, based on the basic identifier, querying the candidate object matching the basic identifier based on the second system. Then, judging whether the object information of the candidate object is consistent with the object information in the object description, if they are consistent, it means that the candidate object is the target object, and it can be determined that the shared party has the target object. If they are inconsistent, it can be determined that the shared party does not have the target object.

[0064] For example, the target object has a basic identifier and an object identifier. For example, the target object is an email. The email has a basic identifier Message ID and an object identifier Mail ID. The active sharer User_1 sent an email. The recipient, CC, and BCC of the email are User_2, User_3, and User_4 respectively. There are four emails in total, namely, the email sent by User_1, the email received by the recipient User_2, the email received by the CC User_3, and the email received by the BCC User_4. The basic identifier Message ID of these four emails is the same, but the object identifiers Mail ID of the four emails are different.

[0065] Emails can be queried based on the basic identifier Message ID of the email, and the queried emails are called candidate objects. However, there is a possibility of duplication of basic identifiers. The reason for the duplication is that some users will send two emails through the email sending service. The basic identifier Message ID of these two emails is constructed by the email sending service. There is a small probability that the basic identifier Message ID of two unrelated emails is the same. Therefore, it is also necessary to compare whether the object information of the candidate object is consistent with the object information in the object description (i.e., email details) of the active sharing party. If they are consistent, it is determined that the sharing party has the target object. If they are inconsistent, it can be determined that the shared party does not have the target object. The object information used in the above comparison process may include, for example, the subject of the email, the number of attachments, the sender, the recipient, the email content type (plain text, HTML), time, etc., where the time of the active sharing party is the sending time, and the time of the shared party is the receiving time. Considering that there may be a delay between the sending time and the receiving time, the delay range can be determined according to the actual situation, and the sending time and the receiving time can meet the delay range.

[0066] In some embodiments, considering that there are too many emails in the user's mailbox, a timeout may occur in the process of querying the target email based on the basic identifier. Therefore, a timeout period can be set. If no candidate object is found before the timeout period, the query can be directly interrupted, thereby improving the user experience and reducing the user's waiting time.

[0067] Figure 3 It is a schematic diagram of an object sharing method according to an embodiment of the present disclosure.

[0068] In this embodiment, the object sharing method involves the front-end page Page, the back-end service Service, the system Server A and the system Server B. Figure 3 The solid lines represent actions that need to be performed, and the dotted lines represent actions that do not need to be performed.

[0069] In this embodiment, user User 1 sends an email to user User 2 and then shares a card with user User 2. It can be seen that user User 1 is the active sharer and user User 2 is the shared party. In addition, user User 1 is in system Server A and user User 2 is in system Server B. It can be seen that system Server A is the first system and system Server B is the second system, and the first system and the second system are two different systems.

[0070] In this embodiment, after the active sharer shares the interactive window with the shared party and displays it through the front-end page Page, the shared party performs a predetermined operation by clicking or other means, so that the front-end page Page can collect the window information of the interactive window and the identifier of the shared party, and send a request to the back-end service Service, which carries the window information and the identifier of the shared party who clicked the interactive window.

[0071] The backend service Service obtains the request from the frontend page Page, then extracts the identifier of the shared party from the request, and based on the correspondence between the identifier and the system, determines from multiple systems that the shared party is in system Server B, and diverts the request to system Server B.

[0072] Then, the system Server B queries the predetermined parameter in the window information in the request, and for example extracts the predetermined parameter "from Server A", indicating that the active sharing party is in the system Server A.

[0073] Next, the object description of the target object can be obtained based on system Server A. For example, system Server B sends a request to system Server A, and then system Server A can authenticate the shared party to determine whether the shared party has the authority to view the target object. If the authentication is successful, the object description of the target object sent by the active sharer can be queried in its own database based on the window information. When the target object is an email, the object description can be the subject, body, and other contents in the email. Then system Server A can send the queried information to system Server B.

[0074] Next, the system Server B may query whether the shared party has the target object to obtain the query result. For example, the system Server B queries whether the shared party has the target object through the basic identifier of the target object to obtain the query result.

[0075] Next, the object description and query results of the target object can be output. For example, system Server B encapsulates the object description and query results, and then sends the encapsulated data to the front-end page Page. The front-end page Page then renders the email content to the shared party.

[0076] By adopting the technical solution provided in this embodiment, the active sharing party can send the target object to the shared party. Taking the target object as an email, an interactive window can be displayed to the shared party after sharing. The shared party clicks the interactive window to display the email details to the shared party. Furthermore, the shared party can also reply and forward.

[0077] In addition, there is a sequence for introducing mailbox systems in an enterprise, for example, the first system is introduced first and the second system is introduced later. Since the shared emails have been persisted to the user client, they cannot be modified. This embodiment can also realize cross-system sharing and viewing without changing the original sharing data of the original system.

[0078] Figure 4 is a schematic diagram of an object sharing method according to another embodiment of the present disclosure.

[0079] In this embodiment, the object sharing method involves the front-end page Page, the back-end service Service, the system Server A and the system Server B. Figure 4 The solid lines represent actions that need to be performed, and the dotted lines represent actions that do not need to be performed.

[0080] In this embodiment, user User 3 sends an email to user User 4 and then shares a card with user User 4. It can be seen that user User 3 is the active sharer and user User 4 is the shared party. In addition, user User 3 is in system Server B and user User 4 is in system Server A. It can be seen that system Server B is the first system and system Server A is the second system, and the first system and the second system are two different systems.

[0081] In this embodiment, after the active sharer shares the interactive window with the shared party and displays it through the front-end page Page, the shared party clicks on the interactive window, and the front-end page Page sends a request to the back-end service Service.

[0082] The backend service Service obtains the request from the frontend page Page, then determines that the shared party is in system Server A, and diverts the request to system Server A. Then system Server A queries the window information in the request for a predetermined parameter "from Server B", indicating that the active sharer is in system Server B.

[0083] Next, the object description of the target object can be obtained based on system Server B. For example, system Server A sends a request to system Server B, and then system Server B authenticates the shared party. If the authentication is successful, system Server B queries the object description of the target object. Then system Server B can send the queried information to system Server A.

[0084] Next, based on the system Server A, it is possible to query whether the shared party has the target object and obtain the query result.

[0085] Next, the object description and query results of the target object can be output. For example, system Server A encapsulates the object description and query results, and then sends the encapsulated data to the front-end page Page. The front-end page Page then renders the email content to the shared party.

[0086] Figure 5 is a schematic diagram of an object sharing method according to another embodiment of the present disclosure.

[0087] In this embodiment, the object sharing method involves the front-end page Page, the back-end service Service, the system Server A and the system Server B. Figure 5 The solid lines represent actions that need to be performed, and the dotted lines represent actions that do not need to be performed.

[0088] In this embodiment, user User 5 sends an email to user User 6 and then shares a card with user User 6. In addition, user User 5 and user User 6 are both in system Server A. It can be seen that in this embodiment, the first system and the second system are the same system, and the same system is system Server A.

[0089] In this embodiment, the shared party clicks on the interactive window through the front-end page Page, and the front-end page Page sends a request to the back-end service Service. The back-end service Service obtains the request from the front-end page Page, then determines that the shared party is in the system Server A, and diverts the request to the system Server A. Then the system Server A queries the window information in the request for the predetermined parameter "from Server A". Next, the shared party can be authenticated based on the system Server A. If the authentication is successful, the object description and query results of the target object are determined based on the system Server A. Then the system Server A encapsulates the object description and query results, and then sends the encapsulated data to the front-end page Page. The front-end page Page is then rendered to display the email content to the shared party.

[0090] Figure 6 is a schematic diagram of an object sharing method according to another embodiment of the present disclosure.

[0091] In this embodiment, the object sharing method involves the front-end page Page, the back-end service Service, the system Server A and the system Server B. Figure 6 The solid lines represent actions that need to be performed, and the dotted lines represent actions that do not need to be performed.

[0092] In this embodiment, user User 7 sends an email to user User 8 and then shares a card with user User 8. In addition, user User 7 and user User 8 are both in system Server B. It can be seen that in this embodiment, the first system and the second system are the same system, and the same system is system Server B.

[0093] In this embodiment, the shared party clicks on the interactive window through the front-end page Page, and the front-end page Page sends a request to the back-end service Service. The back-end service Service obtains the request from the front-end page Page, then determines that the shared party is on system Server B, and diverts the request to system Server B. Then the system Server B queries the window information in the request for the predetermined parameter "from Server B". Next, the shared party can be authenticated based on system Server B. If the authentication is successful, the object description and query results of the target object are determined based on system Server B. Then system Server B encapsulates the object description and query results, and then sends the encapsulated data to the front-end page Page. The front-end page Page is then rendered to display the email content to the shared party.

[0094] It should be noted that, in some of the above embodiments, the first system and the second system may interact with each other, and the interaction process may include sending requests, transmitting object descriptions, etc. In other embodiments, the first system and the second system may not interact with each other. For example, the backend service may request the first system to determine the object description, and then the first system directly returns the object description to the front end, or the backend service indirectly returns the object description to the front end. In addition, the backend service may request the second system to determine the query result, and then the second system directly returns the query result to the front end, or the backend service indirectly returns the query result to the front end.

[0095] It should be noted that in some of the above embodiments, the object description and the query result are returned to the front-end page together after being packaged. In other embodiments, the object description may be returned to the front-end page first, and while the object description is rendered on the front-end page, a request is sent to the second system to query whether the shared party has the target object, and then the query result is returned to the front-end page. This can reduce the waiting time for the shared party to view the object details, but this method is likely to cause the option buttons for executing predetermined operations such as forwarding and replying to not be displayed in the initial rendering stage.

[0096] Next, the process of obtaining email details and query results from the first system and the second system is described in detail.

[0097] In this embodiment, there are two mailbox systems in the enterprise, namely the first system introduced first and the second system introduced later, wherein user 1 and user 2 are on the first system, and user 3 and user 4 are on the second system. When user 1 and user 2 share mails, a predetermined parameter "from Server 1" will be added to the window information, or the value of the predetermined parameter "fromServer" will be set to the default value, which can be empty. When user 3 and user 4 share mails, a predetermined parameter "from Server 2" will be added to the window information.

[0098] For example, the active sharer is user 1, and the share recipient is user 2. After user 1 shares with user 2, user 2 clicks on the interactive window, and through the user 2 identifier, it is determined that user 2 is in the first system, so the first system is processed through diversion and requested. After receiving the request, the first system checks the predetermined parameters, which are "from Server 1". Therefore, the email details are obtained through the first system, and then the first system queries whether the email is in the mailbox of the share recipient based on the basic identifier, thereby obtaining the query result.

[0099] For example, the active sharer is user 1, and the shared party is user 3. After user 1 shares with user 3, user 3 clicks on the interactive window, and determines that user 3 is in the second system through the identifier of user 3, so it is processed through diversion and requests the second system. After receiving the request, the second system checks the predetermined parameter, which is "from Server 1" at this time, and then requests the first system. The first system can perform the following operations: determine whether the predetermined parameter is "from Server 1", if not, request the second system; if so, obtain the email details from the first system, and then return the email details to the second system. Then the second system queries whether the email is in the mailbox of the shared party based on the basic identifier, and obtains the query result.

[0100] For example, the active sharer is user 3, and the shared party is user 1. After user 3 shares with user 1, user 1 clicks on the interactive window and determines that user 1 is in the first system through the identifier of user 1, so it processes the request through diversion and requests the first system. After receiving the request, the first system checks the predetermined parameter, which is "from Server 2" at this time, and then requests the second system. The second system can, for example, perform the following operations: determine whether the predetermined parameter is "from Server 2", if not, request the first system; if so, obtain the email details from the second system, and then return the email details to the first system. Then the first system queries whether the email is in the mailbox of the shared party based on the basic identifier, and obtains the query result.

[0101] For example, the active sharer is user 3, and the shared party is user 4. After user 3 shares with user 4, user 4 clicks the interactive window, and through the user 4's identifier, it is determined that user 4 is in the second system, so the second system is processed and requested through diversion. After receiving the request, the second system checks the predetermined parameters. At this time, the predetermined parameters are "from Server 2", so the email details are obtained through the second system, and then the second system queries whether there is the email in the mailbox of the shared party based on the basic identifier, thereby obtaining the query result.

[0102] It should be noted that in this embodiment, the active sharer needs to first share an interactive window with the shared party, and then the shared party clicks the interactive window before performing subsequent operations such as determining the object description and determining the query results. This embodiment describes the sharing process of the active sharer, which is mainly achieved through the interaction between the active sharer and the front-end page.

[0103] In one example, the active sharer can choose to share to an individual. For example, the active sharer clicks the share option on the front-end page, and the front-end page displays the active sharer's recent contact list. After the active sharer selects the corresponding sharee, the email address or ID of the sharee is obtained through the front-end, and the sharing type is marked as user, and the ID of the target object to be shared is obtained. Then the active sharer can click the OK option, and the front-end page can send a request to the back-end service, and the request carries at least one of the email address and ID of the sharee, as well as the sharing type and the ID of the target object.

[0104] In one example, the active sharer can choose to share to a group. For example, when the active sharer clicks the share option on the front-end page, the active sharer's recently contacted groups are displayed. After the active sharer selects the corresponding group, the group number is obtained as the identifier of the shared party, and the sharing type is marked as group. The identifier of the target object to be shared is also obtained. Then the active sharer can click the confirm option, and the front-end page can send a request to the back-end service, and the request carries the identifier of the shared party, the sharing type, and the identifier of the target object.

[0105] It should be noted that during the sharing process, the active sharer can select multiple groups or individuals, and individuals and groups can be selected at the same time, and each group and individual is a separate sharee. In addition, in actual applications, after the active sharer completes the sharing, the dialog box of the sharee or group can be automatically jumped to, instead of staying on the current page, so that the active sharer can continue to perform other operations.

[0106] The above describes the sharing process of the active sharer.

[0107] It should be noted that in this embodiment, the active sharing party needs to first share an interactive window with the shared party, and this embodiment describes the process of generating the interactive window. The process of generating the interactive window may include preprocessing, recording information in a predetermined database, assembly process, calling process, prompting process, etc. The process of generating the interactive window is mainly implemented by the backend, which may include backend services, predetermined generation services, etc.

[0108] In one example, the process of generating an interactive window may include preprocessing. For example, after the active sharing party clicks the sharing option on the front-end page or triggers the sharing operation by other means, the front-end page sends a request to the back-end service, and the back-end service can obtain the request and extract the identifier of the shared party from the request. Next, the back-end service can determine whether the identifier of the shared party belongs to a predetermined group, for example, to find out whether the identifier of the shared party exists in the identifier set of the predetermined group. The predetermined group can be other groups obtained for enterprise users and users who enable the sharing function. This embodiment does not limit the predetermined group. If the identifier of the shared party belongs to the predetermined group, subsequent operations can be triggered to generate an interactive window, for example, the window attributes associated with the shared party can be determined, and then the interactive window can be generated according to the window attributes. If the identifier of the shared party does not belong to the predetermined group, the identifier of the shared party can be added to the sharing failure set. The sharing failure set can be returned to the front end later, thereby prompting the active sharing party that the sharing operation failed for those shared parties.

[0109] It should be noted that the preprocessing process provided in this embodiment ensures that only users in the predetermined group can generate an interactive window by preprocessing the shared party's identifier, thereby improving the accuracy of the sharing operation and effectively avoiding resource waste and erroneous sharing. At the same time, by recording the situation where the shared party's identifier does not belong to the predetermined group in the sharing failure set and promptly feeding back to the front end, the active sharer can understand the result of the sharing operation, thereby improving the transparency and success rate of the sharing process and optimizing the user's sharing experience. In addition, the solution also has good scalability, which is convenient for formulating personalized sharing strategies for different groups.

[0110] The preprocessing process is described above. It can be understood that in some embodiments, the preprocessing process can be omitted.

[0111] In one example, the generation process of the interactive window may include record information in a predetermined database. For example, after the active sharer clicks the share option on the front-end page or triggers the sharing operation by other means, the front-end page sends a request to the back-end service. The back-end service may respond to receiving the request or to the completion of the above-mentioned preprocessing process, and then determine the information related to the sharing operation based on the request. The information related to the sharing operation may include, for example, the email address of the active sharer, the email ID of the sharing, the sharing type, the information of the person or group being shared (the ID of the person being shared), the sharing time, etc., wherein the time when the back-end service receives the front-end request can be used as the sharing time, the identity of the active sharer can be determined based on the source of the request, and then the email address of the active sharer can be determined based on the identity. The information related to the sharing operation can then be stored in a predetermined database.

[0112] It should be noted that after using the predetermined database to record this information, there may be a variety of subsequent applications, for example, the information may be queried in the predetermined database according to actual needs. For another example, the shared party may be authenticated based on the data in the predetermined database, and the authentication may include, for example, determining whether the shared party has the authority to view the target object.

[0113] The record information in the predetermined database of this embodiment can provide a basis for subsequent data analysis and application, facilitate tracking and management of sharing behavior, and can also authenticate the shared party based on the data in the database to ensure the security of the rights of the shared content.

[0114] The process of recording information in a predetermined database is described above. It can be understood that in some embodiments, this process can be omitted.

[0115] In another example, the interactive window generation process may include an assembly process. For example, taking the target object as an email, the backend service can extract information such as the email subject, sender, and recipient, and encapsulate it into a structure. In addition, the backend service can also set different recipient IDs according to different sharing types (person or group). In addition, the backend service can also set different style values ​​according to the style parameters of the target object. The style parameters include, for example, whether the sender is external, the email priority, whether the email contains attachments, etc. The style value is used to make the front-end page render different styles for the interactive window. In addition, the backend service can also set a link, which can include information such as the email address of the active sharer, the email ID, the sharing type, and can also include the primary key ID of the database table, etc.

[0116] In another example, the interactive window generation process may include a calling process. For example, the number of shared parties is at least one, and the following operations may be performed for each of the at least one shared party: according to the sharing operation triggered by the active sharing party, the window attributes associated with the shared party are determined, and then according to the window attributes, the predetermined generation service is called to generate an interactive window associated with the shared party. For example, taking the target object as an email, the backend service assembles a corresponding data for each shared party (person or group), and then calls the predetermined generation service based on the assembled information, and obtains the interactive window from the predetermined generation service. Then, the backend service can return the interactive window to the front-end page for the shared party to view and perform predetermined operations on the interactive window.

[0117] This embodiment implements a personalized interactive window assembly and generation process, improving the customization of information sharing and user experience. By extracting key email information and setting different style values, it ensures that the rendering effect of the interactive window on the front-end page conforms to the content characteristics, enhancing the visual effect and information readability. At the same time, by generating a specific interactive window for each shared party, the needs of different users are met and the accuracy of sharing is improved.

[0118] In one example, the interactive window generation process may include a prompting process. For example, if the backend service receives an interactive window from a predetermined generation service, the backend service may add the identifier of the shared party to the sharing success set. If the backend service does not receive an interactive window from a predetermined generation service, the backend service may add the identifier of the shared party to the sharing failure set. The sharing success set and the sharing failure set may then be output to the front-end page so that the front-end page prompts the active sharing party of the sharing result of the interactive window according to the status of the sharing success set and the sharing failure set. For example, if the sharing failure set is empty, the active sharing party is prompted that all sharing is successful. If the sharing success set is empty, the active sharing party is prompted that all sharing has failed. If both the sharing success set and the sharing failure set are not empty, the active sharing party is prompted with the successful and failed shared parties according to the sharing success set and the sharing failure set.

[0119] Figure 7 A schematic flowchart of an object display method according to an embodiment of the present disclosure.

[0120] like Figure 7 As shown, the object display method 700 may be executed by a front end, and the object display method 700 may include operations S710 to S730.

[0121] In operation S710, an object description of a target object and a query result indicating whether the shared party has the target object are obtained. For example, the object description and the query result may be obtained by the above-mentioned object sharing method.

[0122] In operation S720, an operation option for the shared party is determined according to the query result.

[0123] For example, the target object includes an email, and the operation options include at least one of forwarding, replying, deleting, and moving.

[0124] For example, some operation options are related to the operation authority of the shared party. If the query result indicates that the shared party has the target object, these operation options can be determined as operation options for the shared party. If the query result indicates that the shared party does not have the target object, these operation options can be restricted as operation options for the shared party.

[0125] In operation S730, an object description and operation options are rendered.

[0126] In this embodiment, taking the target object as an email, the active sharer sends an email to the first user, and then shares the email with the first user and the second user. After the second user clicks the interactive window, the email details can be displayed. Since the first user has the shared email, the first user can reply, forward, and perform other operations based on the email without having to return to his own mailbox to find the email. Since the second user does not have the shared email, the second user can view the email details, but cannot reply, forward, and perform other operations.

[0127] Figure 8 is a schematic structural block diagram of an object sharing device according to an embodiment of the present disclosure.

[0128] like Figure 8 As shown, the object sharing device 800 may include a first acquisition module 810 , a system determination module 820 , a second acquisition module 830 , a query module 840 and a first output module 850 .

[0129] The first acquisition module 810 is used to acquire window information of the interactive window and an identifier of the shared party in response to detecting that the shared party performs a predetermined operation on the interactive window, wherein the interactive window is generated based on a target object shared by the active sharing direction to the shared party.

[0130] The system determination module 820 is used to determine the first system where the active sharing party is located and the second system where the shared party is located according to the window information and the identifier of the shared party.

[0131] The second acquisition module 830 is used to acquire an object description of the target object based on the first system.

[0132] The query module 840 is used to query whether the shared party has a target object based on the second system to obtain a query result.

[0133] The first output module 850 is used to output object description and query results.

[0134] According to another embodiment of the present disclosure, the query module includes: a basic identification submodule, a query submodule, a first determination submodule and a second determination submodule. The basic identification submodule is used to determine the basic identification of the target object based on the window information. The query submodule is used to query the candidate objects that match the basic identification based on the second system according to the basic identification. The first determination submodule is used to determine that the shared party has the target object in response to detecting that the object information of the candidate object is consistent with the object information in the object description. The second determination submodule is used to determine that the shared party does not have the target object in response to detecting that the object information of the candidate object is inconsistent with the object information in the object description.

[0135] According to another embodiment of the present disclosure, the system determination module includes: a first system determination submodule and a second system determination submodule. The first system determination submodule is used to determine the first system from multiple systems according to a predetermined parameter in the window information. The predetermined parameter is added to the window information in response to the active sharing party triggering a sharing operation for sharing an interactive window, and the predetermined parameter represents the system identifier of the active sharing party. The second system determination submodule is used to determine the second system from multiple systems according to the identifier of the shared party.

[0136] According to another embodiment of the present disclosure, the second acquisition module includes: a permission determination submodule and an acquisition submodule. The permission determination submodule is used to determine whether the shared party has permission to view the object description based on the window information and the information in the predetermined database. The acquisition submodule is used to obtain the object description of the target object based on the first system in response to detecting that the shared party has permission.

[0137] According to another embodiment of the present disclosure, the information in the predetermined database is determined by the following modules: a third acquisition module and a storage module. The third acquisition module is used to obtain information related to the sharing operation in response to detecting that the active sharing party triggers a sharing operation for sharing the interactive window. The storage module is used to store the information related to the sharing operation in the predetermined database.

[0138] According to another embodiment of the present disclosure, the number of shared parties is at least one, and the device further includes: a window attribute determination module, a generation module, a first adding module, a second adding module, and a second output module. The window attribute determination module is used to determine the window attributes associated with the shared party for each of the at least one shared party according to the sharing operation triggered by the active sharing party. The generation module is used to call a predetermined generation service according to the window attributes to generate an interactive window associated with the shared party. The first adding module is used to add the identifier of the shared party to the sharing success set in response to receiving an interactive window from the predetermined generation service. The second adding module is used to add the identifier of the shared party to the sharing failure set in response to not receiving an interactive window from the predetermined generation service. The second output module is used to output the sharing success set and the sharing failure set so as to prompt the active sharing party of the sharing result of the interactive window.

[0139] According to another embodiment of the present disclosure, it also includes: a fourth acquisition module, a trigger module and a third adding module. The fourth acquisition module is used to obtain the identifier of the shared party according to the sharing operation triggered by the active sharing party. The trigger module is used to trigger the operation of determining the window attributes associated with the shared party in response to detecting that the identifier of the shared party belongs to a predetermined group. The third adding module is used to add the identifier of the shared party to the sharing failure set in response to detecting that the identifier of the shared party does not belong to the predetermined group.

[0140] According to another embodiment of the present disclosure, the target object includes an email, and the interactive window is used to display at least one of the following: email subject, email summary, recipient, sender, and email content in image form.

[0141] Fig. 9 It is a schematic structural block diagram of an object display device according to an embodiment of the present disclosure.

[0142] like Fig. 9 As shown, the object display device 900 may include a fifth acquisition module 910 , an option determination module 920 and a rendering module 930 .

[0143] The fifth acquisition module 910 is used to acquire an object description of the target object and a query result indicating whether the shared party has the target object, wherein the object description and the query result are obtained based on the above-mentioned object sharing device.

[0144] The option determination module 920 is used to determine the operation options for the shared party to use according to the query result.

[0145] The rendering module 930 is used to render object descriptions and operation options.

[0146] According to another embodiment of the present disclosure, the target object includes an email, and the operation options include at least one of forwarding, replying, deleting, and moving.

[0147] According to an embodiment of the present disclosure, the present disclosure also provides an electronic device, comprising at least one processor; and a memory communicatively connected to the at least one processor; the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor so that the at least one processor can execute at least one of the above-mentioned object sharing method and object display method.

[0148] According to an embodiment of the present disclosure, the present disclosure further provides a non-transitory computer-readable storage medium storing computer instructions, wherein the computer instructions are used to enable a computer to execute at least one of the above-mentioned object sharing method and object display method.

[0149] According to an embodiment of the present disclosure, the present disclosure further provides a computer program product, including a computer program, which implements at least one of the above-mentioned object sharing method and object display method when executed by a processor.

[0150] Fig.101 is a block diagram of an electronic device for implementing the object sharing method and / or object display method of an embodiment of the present disclosure. The electronic device is intended to represent various forms of digital computers, such as laptop computers, desktop computers, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The electronic device may also represent various forms of mobile devices, such as personal digital processing, cellular phones, smart phones, wearable devices, and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely examples and are not intended to limit the implementation of the present disclosure described and / or claimed herein.

[0151] like Fig.10 As shown, the device 1000 includes a computing unit 1001, which can perform various appropriate actions and processes according to a computer program stored in a read-only memory (ROM) 1002 or a computer program loaded from a storage unit 1008 into a random access memory (RAM) 1003. In the RAM 1003, various programs and data required for the operation of the device 1000 can also be stored. The computing unit 1001, the ROM 1002, and the RAM 1003 are connected to each other via a bus 1004. An input / output (I / O) interface 105 is also connected to the bus 1004.

[0152] A number of components in the device 1000 are connected to the I / O interface 1005, including: an input unit 1006, such as a keyboard, a mouse, etc.; an output unit 1007, such as various types of displays, speakers, etc.; a storage unit 1008, such as a disk, an optical disk, etc.; and a communication unit 1009, such as a network card, a modem, a wireless communication transceiver, etc. The communication unit 1009 allows the device 1000 to exchange information / data with other devices through a computer network such as the Internet and / or various telecommunication networks.

[0153] The computing unit 1001 may be a variety of general and / or special processing components with processing and computing capabilities. Some examples of the computing unit 1001 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various dedicated artificial intelligence (AI) computing chips, various computing units running machine learning model algorithms, digital signal processors (DSPs), and any appropriate processors, controllers, microcontrollers, etc. The computing unit 1001 performs the various methods and processes described above, such as at least one of the object sharing method and the object display method. For example, in some embodiments, at least one of the object sharing method and the object display method may be implemented as a computer software program, which is tangibly included in a machine-readable medium, such as a storage unit 1008. In some embodiments, part or all of the computer program may be loaded and / or installed on the device 1000 via the ROM 1002 and / or the communication unit 1009. When the computer program is loaded into the RAM 1003 and executed by the computing unit 1001, one or more steps in the object sharing method and the object display method described above may be executed. Alternatively, in other embodiments, the computing unit 1001 may be configured to execute at least one of the object sharing method and the object display method in any other appropriate manner (eg, by means of firmware).

[0154] Various implementations of the systems and techniques described above herein can be implemented in digital electronic circuit systems, integrated circuit systems, field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), application specific standard products (ASSPs), systems on chips (SOCs), complex programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof. These various implementations can include: being implemented in one or more computer programs that can be executed and / or interpreted on a programmable system including at least one programmable processor, which can be a special purpose or general purpose programmable processor that can receive data and instructions from a storage system, at least one input device, and at least one output device, and transmit data and instructions to the storage system, the at least one input device, and the at least one output device.

[0155] The program code for implementing the method of the present disclosure may be written in any combination of one or more programming languages. These program codes may be provided to a processor or controller of a general-purpose computer, a special-purpose computer, or other programmable data processing device, so that the program code, when executed by the processor or controller, enables the functions / operations specified in the flow chart and / or block diagram to be implemented. The program code may be executed entirely on the machine, partially on the machine, partially on the machine and partially on a remote machine as a stand-alone software package, or entirely on a remote machine or server.

[0156] In the context of the present disclosure, a machine-readable medium may be a tangible medium that may contain or store a program for use by or in conjunction with an instruction execution system, device, or equipment. A machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, device, or device, or any suitable combination of the foregoing. A more specific example of a machine-readable storage medium may include an electrical connection based on one or more lines, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

[0157] To provide interaction with a user, the systems and techniques described herein can be implemented on a computer having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to the user; and a keyboard and pointing device (e.g., a mouse or trackball) through which the user can provide input to the computer. Other types of devices can also be used to provide interaction with the user; for example, the feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user can be received in any form (including acoustic input, voice input, or tactile input).

[0158] The systems and techniques described herein may be implemented in a computing system that includes back-end components (e.g., as a data server), or a computing system that includes middleware components (e.g., an application server), or a computing system that includes front-end components (e.g., a user computer with a graphical user interface or a web browser through which a user can interact with implementations of the systems and techniques described herein), or a computing system that includes any combination of such back-end components, middleware components, or front-end components. The components of the system may be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include: a local area network (LAN), a wide area network (WAN), and the Internet.

[0159] A computer system may include clients and servers. Clients and servers are generally remote from each other and usually interact through a communication network. The relationship of client and server is generated by computer programs running on respective computers and having a client-server relationship to each other.

[0160] It should be understood that the various forms of processes shown above can be used to reorder, add or delete steps. For example, the steps recorded in this disclosure can be executed in parallel, sequentially or in different orders, as long as the desired results of the technical solutions disclosed in this disclosure can be achieved, and this document does not limit this.

[0161] The above specific implementations do not constitute a limitation on the protection scope of the present disclosure. It should be understood by those skilled in the art that various modifications, combinations, sub-combinations and substitutions can be made according to design requirements and other factors. Any modification, equivalent substitution and improvement made within the spirit and principle of the present disclosure shall be included in the protection scope of the present disclosure.

Claims

1. An object sharing method, comprising: In response to detecting that the shared party performs a predetermined operation on the interactive window, obtaining window information of the interactive window and an identifier of the shared party; wherein the interactive window is generated based on a target object shared by the active sharing party to the shared party; Determine, according to the window information and the identifier of the shared party, the first system where the active sharing party is located and the second system where the shared party is located; acquiring an object description of the target object based on the first system; querying whether the shared party has the target object based on the second system, and obtaining a query result; and The object description and the query result are output.

2. The method according to claim 1, wherein: The querying of whether the shared party has the target object based on the second system to obtain the query result includes: Based on the window information, determining a basic identifier of the target object; According to the basic identifier, querying the candidate object matching the basic identifier based on the second system; In response to detecting that the object information of the candidate object is consistent with the object information in the object description, determining that the shared party has the target object; and In response to detecting that the object information of the candidate object is inconsistent with the object information in the object description, it is determined that the shared party does not have the target object.

3. The method according to claim 1, wherein: The determining, according to the window information and the identifier of the shared party, the first system where the active sharing party is located and the second system where the shared party is located comprises: Determining the first system from a plurality of systems according to a predetermined parameter in the window information; wherein the predetermined parameter is added to the window information in response to the active sharing party triggering a sharing operation for sharing the interactive window, and the predetermined parameter represents a system identifier of the active sharing party; and The second system is determined from the multiple systems according to the identifier of the shared party.

4. The method according to claim 1, wherein: The acquiring the object description of the target object based on the first system includes: Determining whether the shared party has permission to view the object description according to the window information and information in a predetermined database; and In response to detecting that the shared party has the authority, an object description of the target object is obtained based on the first system.

5. The method according to claim 4, wherein: The information in the predetermined database is determined by: In response to detecting that the active sharing party triggers a sharing operation for sharing the interactive window, acquiring information related to the sharing operation; as well as The information related to the sharing operation is stored in the predetermined database.

6. The method according to claim 1, wherein: The number of the shared parties is at least one, and the method further includes: For each of the at least one shared party, according to the sharing operation triggered by the active sharing party, determining a window attribute associated with the shared party; According to the window attribute, calling a predetermined generation service to generate the interaction window associated with the shared party; In response to receiving the interaction window from the predetermined generation service, adding the identifier of the shared party to a sharing success set; In response to not receiving the interaction window from the predetermined generation service, adding the identifier of the shared party to a sharing failure set; The sharing success set and the sharing failure set are outputted so as to prompt the active sharing party with the sharing result of the interactive window.

7. The method according to claim 6, further comprising: According to the sharing operation triggered by the active sharing party, obtaining the identifier of the shared party; In response to detecting that the identifier of the shared party belongs to a predetermined group, triggering an operation of determining a window attribute associated with the shared party; as well as In response to detecting that the identifier of the shared party does not belong to a predetermined group, the identifier of the shared party is added to the sharing failure set.

8. The method according to claim 1, wherein: The target object includes an email, and the interactive window is used to display at least one of the following: email subject, email summary, recipient, sender, and email content in image form.

9. An object display method, comprising: Obtaining an object description of a target object and a query result indicating whether the shared party has the target object; Determining, according to the query result, an operation option for the shared party to use; as well as Rendering the object description and the operation options; The object description and the query result are obtained based on the method described in any one of claims 1 to 8.

10. The method according to claim 9, wherein: The target object includes an email, and the operation options include at least one of forwarding, replying, deleting, and moving.

11. An object sharing device, comprising: A first acquisition module is used to acquire window information of the interactive window and an identifier of the shared party in response to detecting that the shared party performs a predetermined operation on the interactive window; wherein the interactive window is generated based on a target object shared by the active sharing party to the shared party; A system determination module, used to determine the first system where the active sharing party is located and the second system where the shared party is located according to the window information and the identifier of the shared party; A second acquisition module, configured to acquire an object description of the target object based on the first system; A query module, configured to query whether the shared party has the target object based on the second system, and obtain a query result; and The first output module is used to output the object description and the query result.

12. The device according to claim 11, wherein The query module includes: A basic identification submodule, used to determine a basic identification of the target object based on the window information; A query submodule, configured to query, based on the basic identifier and based on the second system, candidate objects that match the basic identifier; A first determination submodule, configured to determine that the shared party has the target object in response to detecting that the object information of the candidate object is consistent with the object information in the object description; and The second determination submodule is configured to determine that the shared party does not have the target object in response to detecting that the object information of the candidate object is inconsistent with the object information in the object description.

13. The device according to claim 11, wherein: The system determination module comprises: a first system determination submodule, configured to determine the first system from a plurality of systems according to a predetermined parameter in the window information; wherein the predetermined parameter is added to the window information in response to the active sharing party triggering a sharing operation for sharing the interactive window, and the predetermined parameter represents a system identifier of the active sharing party; and The second system determining submodule is used to determine the second system from the multiple systems according to the identifier of the shared party.

14. The device according to claim 11, wherein: The second acquisition module includes: a permission determination submodule, for determining whether the shared party has permission to view the object description according to the window information and information in a predetermined database; and The acquisition submodule is used to acquire the object description of the target object based on the first system in response to detecting that the shared party has the permission.

15. The device according to claim 14, wherein: The information in the predetermined database is determined by the following modules: A third acquisition module, configured to acquire information related to the sharing operation in response to detecting that the active sharing party triggers a sharing operation for sharing the interactive window; as well as The storage module is used to store the information related to the sharing operation in the predetermined database.

16. The device according to claim 11, wherein The number of the shared party is at least one, and the device further includes: a window attribute determination module, configured to determine, for each of the at least one shared party, a window attribute associated with the shared party according to a sharing operation triggered by the active sharing party; A generating module, configured to call a predetermined generating service according to the window attributes to generate the interactive window associated with the shared party; A first adding module, configured to add the identifier of the shared party to a sharing success set in response to receiving the interaction window from the predetermined generation service; a second adding module, configured to add the identifier of the shared party to a sharing failure set in response to not receiving the interaction window from the predetermined generation service; The second output module is used to output the sharing success set and the sharing failure set so as to prompt the active sharing party of the sharing result of the interactive window.

17. The apparatus according to claim 16, further comprising: A fourth acquisition module, configured to acquire the identifier of the shared party according to the sharing operation triggered by the active sharing party; a triggering module, configured to trigger an operation of determining a window attribute associated with the shared party in response to detecting that the identification of the shared party belongs to a predetermined group; as well as The third adding module is configured to add the identifier of the shared party to the sharing failure set in response to detecting that the identifier of the shared party does not belong to a predetermined group.

18. The device according to claim 11, wherein The target object includes an email, and the interactive window is used to display at least one of the following: email subject, email summary, recipient, sender, and email content in image form.

19. An object display device, comprising: A fifth acquisition module, used to acquire an object description of a target object and a query result indicating whether the shared party has the target object; An option determination module, used to determine an operation option for the shared party to use according to the query result; as well as A rendering module, used for rendering the object description and the operation options; Wherein, the object description and the query result are obtained based on the device described in any one of claims 11 to 18.

20. The device according to claim 19, wherein The target object includes an email, and the operation options include at least one of forwarding, replying, deleting, and moving.

21. An electronic device comprising: at least one processor; as well as a memory communicatively connected to the at least one processor; wherein, The memory stores instructions that can be executed by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to perform the method according to any one of claims 1 to 10.

22. A non-transitory computer-readable storage medium storing computer instructions, wherein: The computer instructions are used to cause the computer to execute the method according to any one of claims 1 to 10.

23. A computer program product comprising a computer program which, when executed by a processor, implements the method according to any one of claims 1 to 10.

Images