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

Abstract

The present disclosure provides an object sharing method, an object display method, an apparatus, an electronic device, and a medium, relating to the field of data processing technology, particularly to the field of instant messaging. A specific implementation scheme comprises: in response to detecting that a recipient performs a predetermined operation on an interactive window, obtaining window information of the interactive window and an identifier of the recipient; wherein the interactive window is generated based on a target object shared by an active sharer to the recipient; determining a first system in which the active sharer is located and a second system in which the recipient is located based on the window information and the identifier of the recipient; obtaining an object description of the target object based on the first system; querying whether the recipient has the 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, 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 in 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 indicating 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 operation options; wherein the object description and 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 sharer to the shared party. The system determination module is used to determine the first system in which the active sharer 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. The second acquisition module is used to obtain an 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 configured to obtain an object description of a target object and a query result indicating whether a recipient has the target object. The option determination module is configured to determine, based on the query result, operation options for the recipient. The rendering module is configured to render the object description and operation options, wherein the object description and query result are obtained based on the 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 to enable the at least one processor to 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 cause 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, which implements the method provided in the present disclosure when executed by a processor.

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

[0012] The accompanying drawings are provided to facilitate a better understanding of the present invention and do not constitute a limitation of the present disclosure.

[0013] Figure 1 is a schematic diagram of an application scenario of the object sharing method, object display method and 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] Figure 9 is a schematic structural block diagram of an object display device according to an embodiment of the present disclosure; and

[0022] Figure 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 description of exemplary embodiments of the present disclosure is made in conjunction with the accompanying drawings, including various details of the embodiments of the present disclosure to facilitate understanding. These details should be considered as merely exemplary. Therefore, those skilled in the art will recognize 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 solutions disclosed herein, the collection, storage, use, processing, transmission, provision and disclosure of user personal information involved comply with the provisions of relevant laws and regulations and do not violate public order and good morals.

[0025] In the technical solution disclosed herein, 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, within companies, many business approvals are based on email. However, with the advent of the information age, everyone's inbox is overflowing with emails. Inaccurate searches can cause approvers to be unable to find pending emails, hindering the normal progress of business.

[0027] In addition, there are multiple mailbox systems in an enterprise. Because 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 permission to view, modify, or perform other operations on the data of another mail system. Therefore, data between different mail systems is generally not interoperable. Therefore, when a user in the first mail system shares an email that they have sent or received with a user in the second mail system, the second mail system lacks detailed information about the email and is therefore unable to display the specific content of the email to the recipient, such as the email body. In other words, sharing emails across systems will prevent the recipient from viewing the email details.

[0028] The disclosed embodiments provide an object sharing method. After an active sharer sends an email to a recipient, an interactive window can be generated based on the target object shared by the active sharer to the recipient, and then displayed to the recipient. In response to the recipient performing a predetermined operation on the interactive window, window information of the interactive window and the recipient's identifier can be obtained. Based on the window information and the recipient's identifier, the first system where the active sharer is located and the second system where the recipient is located can be determined. Next, an object description of the target object can be obtained based on the first system, and the recipient can be queried based on the second system to determine whether the recipient has the target object, obtaining a query result. The object description and query result can then be output. In this way, even if the data between the first and second systems are not interoperable, the object description can still be obtained from the active sharer's first system and then rendered. Therefore, in cross-system email sharing scenarios, the recipient can normally browse the email details or further process the email. Furthermore, the recipient does not need to search for the email in their own mailbox; instead, they can directly browse or further process the email based on the interactive window, thereby improving processing efficiency and ensuring the normal progress of business.

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

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

[0031] Figure 1 2 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 The examples shown are merely examples of system architectures to which the embodiments of the present disclosure may be applied, to help those skilled in the art understand the technical content of the present disclosure, but do not mean that the embodiments of the present disclosure may not 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 as a medium for providing 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, and 103 to interact with server 105 via network 104 to receive or send messages, etc. Terminal devices 101, 102, and 103 can be various electronic devices with display screens and support web browsing, including but not limited to smartphones, tablet computers, laptop computers, and desktop computers, etc.

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

[0036] For example, if the active sharer shares an email with the recipient via 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 recipient can view and click on the interactive window. In addition, if the recipient clicks on the interactive window, the server 105 can also obtain the object details and query results and return them to the terminal device 101. The terminal device 101 can render the results via the front-end page, allowing the recipient to view the object or further process the shared target object.

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

[0038] It should be understood that Figure 1 The number of terminal devices, networks and servers in the embodiment is merely illustrative. Any number of terminal devices, networks and servers may be provided as required.

[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, which 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 can be an email, a file, a resource, etc. This embodiment does not limit the target object. Taking the target object as an email as an example, the active sharer can be the sender or recipient of the email, and the shared party can be the recipient of the email or other users unrelated to the sender or recipient of the email. The shared party can 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 use the front-end page to perform predetermined operations such as clicking, circling, or other methods on any area or a predetermined area in the interactive window. 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, allowing the back-end service to obtain 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 sharer is a user using the first system, and the recipient is a user using the second system. The first and second systems can be the same system or different systems. When the first and second systems are different systems, they can be deployed on different servers, physically isolating their data and preventing data from being communicated between them. Alternatively, the first and second systems can be deployed on the same server, but one email system does not have permission to view or modify the data of the other email system, resulting in data being incommunicable between them.

[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, pre-set 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 correspondence 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 can be called to obtain the object description of the target object, or a request can be sent to the second system to obtain the query results returned by the second system. During the query process, the target object's identifier, target object time, type, and other information can be used to query the second system's database to determine whether the target object exists.

[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 embodiments of the present disclosure, after the active sharer sends an email to the sharee, an interaction window can be generated based on the target object shared by the active sharer to the sharee, and then displayed to the sharee. In response to the sharee performing a predetermined operation on the interaction window, the window information of the interaction window and the sharee's identifier can be obtained. Then, based on the window information and the sharee's identifier, the first system where the active sharer is located and the second system where the sharee is located can be determined. Next, the object description of the target object can be obtained based on the first system, and the sharee can be queried based on the second system to determine whether the sharee has the target object, obtaining the query results. The object description and query results can then be output. In this way, even if the data of the first and second systems are not interoperable, the object description can still be obtained from the active sharer's first system and then rendered. Therefore, in the cross-system email sharing scenario, the sharee can normally browse the email details or further process the email. In addition, the sharee can browse or further process the email directly based on the interaction window without having to search for the email in their own mailbox, thereby improving processing efficiency and ensuring the normal progress of 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. This can display rich text, pictures, tables and other elements in the email, making it convenient for the shared party to intuitively see the specific content of the email, making the information conveyed 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 the 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 email systems, with different users in different email systems. For example, if 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 for a specific system (e.g., the first system used) can use a default value. 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-mentioned 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 the first system is determined based on the identifier therein. For example, a correspondence between each shared party and the system is pre-established, and 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 of the active sharer and the shared party.

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

[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 passed and the shared party has the permission to view the object description. Otherwise, it means that the authentication fails and the shared party does not have the permission to view the object description.

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

[0064] For example, a target object has a base ID and an object ID. For example, an email has a base ID (Message ID) and an object ID (Mail ID). User_1, the active sharer, sends an email. The recipient, CC, and BCC recipients are User_2, User_3, and User_4, respectively. This creates a total of four emails: the email sent by User_1, the email received by recipient User_2, the email received by CC user User_3, and the email received by BCC user User_4. These four emails share the same base ID (Message ID), but different object IDs (Mail IDs).

[0065] Emails can be queried based on their basic Message IDs. The resulting emails are called candidate objects. However, there's a possibility of duplicate basic IDs. This is because some users may send two emails through the email service. The basic Message IDs of these two emails are constructed by the email service, and there's a small chance that two unrelated emails will have the same basic Message ID. Therefore, it's necessary to compare the candidate object's object information with the object information in the object description (i.e., email details) of the active sharer. If they are consistent, the sharer is determined to have the target object. If they are inconsistent, the recipient is determined to not have the target object. The object information used in this comparison process may include, for example, the email subject, number of attachments, sender, recipient, email content type (plain text, HTML), and time. The active sharer's time is the sending time, while the recipient's time is the receiving time. Considering the potential delay between the sending and receiving times, a delay range can be determined based on actual conditions, as long as the sending and receiving times meet this delay range.

[0066] In some embodiments, considering that there are too many emails in the user's mailbox, a timeout may occur during the query of 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 line indicates the operation that needs to be performed, and the dotted line indicates the operation that does not need to be performed.

[0069] In this example, User 1 sends an email to User 2 and then shares a card with User 2. This shows that User 1 is the active sharer, while User 2 is the recipient. Furthermore, User 1 is on Server A, while User 2 is on Server B. This shows that Server A is the primary system, while Server B is the secondary system, and that the primary and secondary systems are distinct.

[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 receives 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. System Server A then authenticates the recipient to determine whether they have permission to view the target object. If authentication succeeds, it can query its own database for the object description of the target object sent by the active sharer based on the window information. If the target object is an email, the object description can include the email's subject, body, and other content. System Server A then sends the retrieved information to System Server B.

[0074] Next, the system Server B can 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 based on the basic identifier of the target object to obtain the query result.

[0075] Next, the target object's object description and query results can be output. For example, system Server B encapsulates the object description and query results and sends the encapsulated data to the front-end page. The front-end page then renders the email content, displaying it to the recipient.

[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 as an example, after sharing, an interactive window can be displayed to the shared party. The shared party clicks the interactive window to display the email details to the shared party. Furthermore, the shared party can also perform operations such as replying and forwarding.

[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 shared 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 line indicates the operation that needs to be performed, and the dotted line indicates the operation that does not need to be performed.

[0080] In this example, User 3 sends an email to User 4 and then shares a card with User 4. This shows that User 3 is the active sharer, while User 4 is the recipient. Furthermore, User 3 is on Server B, while User 4 is on Server A. This shows that Server B is the first system, while Server A is the second system, and that the first and second systems are distinct.

[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 the interactive window, and the front-end page Page sends a request to the back-end service Service.

[0082] The backend service Service receives the request from the frontend page Page, determines that the shared party is on system Server A, and diverts the request to system Server A. System Server A then checks the window information in the request and finds the predetermined parameter is "from Server B", indicating that the active sharer is on 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, which then authenticates the shared party. If the authentication is successful, system server B queries the object description of the target object. System server B then sends the retrieved information to system server A.

[0084] Next, the system Server A can query whether the shared party has the target object and obtain the query result.

[0085] Next, the target object's object description and query results can be output. For example, system Server A encapsulates the object description and query results and sends the encapsulated data to the front-end page. The front-end page then renders the email content, displaying it to the recipient.

[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 line indicates the operation that needs to be performed, and the dotted line indicates the operation that does 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 on system Server A, and diverts the request to system Server A. Then, the predetermined parameter in the window information in the system Server A query request is "from Server A". Next, the shared party can be authenticated based on the system Server A. If the authentication is passed, the object description and query results of the target object can be determined based on the system Server A. The system Server A then 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 it, thereby displaying 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 line indicates the operation that needs to be performed, and the dotted line indicates the operation that does 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 predetermined parameter in the window information in the system Server B query request is "from Server B". Next, the shared party can be authenticated based on system Server B. If the authentication is passed, the object description and query results of the target object can be 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 may directly return the object description to the frontend, or the backend service may indirectly return the object description to the frontend. In addition, the backend service may request the second system to determine the query results, and then the second system may directly return the query results to the frontend, or the backend service may indirectly return the query results to the frontend.

[0095] It should be noted that in some of the above-mentioned embodiments, the object description and query results are packaged and returned to the front-end page together. In other embodiments, the object description can be returned to the front-end page first, and while the front-end page is rendering the object description, a request is sent to the second system to query whether the shared party has the target object, and then the query results are returned to the front-end page. This can reduce the waiting time for the shared party to view the object details, but this method can easily result in the option buttons for executing predetermined actions such as forwarding and replying not being displayed during 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, the enterprise has two mailbox systems: the first system, which was introduced first, and the second system, which was introduced later. Users 1 and 2 are on the first system, while users 3 and 4 are on the second system. When users 1 and 2 share emails, a predetermined parameter "from Server 1" is added to the window information, or the predetermined parameter "fromServer" is set to a default value, which can be left blank. When users 3 and 4 share emails, a predetermined parameter "from Server 2" is added to the window information.

[0098] For example, let's say User 1 is the active sharer and User 2 is the recipient. After User 1 shares with User 2, User 2 clicks the interactive window. Based on User 2's ID, User 2 is determined to be in the first system. Therefore, a request is made to the first system through offload processing. Upon receiving the request, System 1 checks the predefined parameters. In this case, the predefined parameters are "from Server 1," and the email details are retrieved from System 1. Then, based on the basic ID, System 1 queries the recipient's mailbox to determine whether the email exists, generating the query result.

[0099] For example, let's say the active sharer is User 1, and the recipient is User 3. After User 1 shares with User 3, User 3 clicks the interactive window. User 3's identifier determines that User 3 is in the second system, so the request is diverted and a request is made to the second system. Upon receiving the request, the second system checks the predefined parameters, which are "from Server 1." It then requests the first system. For example, the first system can perform the following operations: Determine whether the predefined parameters are "from Server 1." If not, request the second system. If so, obtain the email details from the first system and return them to the second system. The second system then uses the basic identifier to query the recipient's mailbox to determine whether the email exists, thereby obtaining the query result.

[0100] For example, let's say the active sharer is User 3, and the recipient is User 1. After User 3 shares with User 1, User 1 clicks the interactive window and, based on User 1's identifier, determines that User 1 is in the first system. Therefore, the request is diverted and a request is made to the first system. Upon receiving the request, the first system checks the predefined parameters, which are "from Server 2." The request is then forwarded to the second system. For example, the second system can perform the following operations: Determine whether the predefined parameters are "from Server 2." If not, request the first system. If so, obtain the email details from the second system and return them to the first system. The first system then queries the recipient's mailbox based on the basic identifier to determine whether the email exists, thereby obtaining the query result.

[0101] For example, let's say User 3 is the active sharer and User 4 is the recipient. After User 3 shares with User 4, User 4 clicks the interactive window. Based on User 4's ID, User 4 is identified as being in the second system. Therefore, a request is made to the second system through offload processing. Upon receiving the request, the second system checks the predefined parameters. In this case, the predefined parameters are "from Server 2," and therefore obtains the email details from the second system. Then, based on the basic ID, the second system queries the recipient's mailbox to determine whether the email exists, generating the query result.

[0102] It should be noted that in this embodiment, the active sharer must first share an interactive window with the recipient. The recipient then clicks on the interactive window before subsequent operations such as determining the object description and query results are performed. This embodiment describes the sharing process of the active sharer, which is primarily achieved through interaction between the active sharer and the front-end page.

[0103] In one example, the active sharer can choose to share with an individual. For example, the active sharer clicks the share option on the front-end page, which displays a list of the active sharer's recent contacts. After the active sharer selects the corresponding shareee, the front-end obtains the shareee's email address or identifier, marks the sharing type as user, and obtains the identifier of the target object to be shared. The active sharer can then click the confirm option, and the front-end page can send a request to the back-end service, carrying at least one of the shareee's email address and identifier, as well as the sharing type and identifier 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 is presented with their recently connected groups. After selecting a group, the active sharer obtains the group number as the shared recipient's identifier, marks the sharing type as group, and obtains the identifier of the target object to be shared. The active sharer then clicks the confirm option, and the front-end page sends a request to the back-end service, carrying the shared recipient's identifier, 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 simultaneously. Each group and individual is a separate recipient. In addition, in actual applications, after the active sharer completes the sharing, the dialog box can automatically jump to the recipient or group, rather than remaining on the current page, making it easier for the active sharer to continue with other operations.

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

[0107] It should be noted that in this embodiment, the active sharer must first share an interactive window with the shared party. This embodiment describes the process of generating the interactive window. This interactive window generation process may include pre-processing, recording information in a predetermined database, assembly, calling, and prompting. This interactive window generation process is primarily implemented by the backend, which may include backend services, reservation generation services, etc.

[0108] In one example, the process of generating an interactive window may include preprocessing. For example, after the active sharer clicks the share option on the front-end page or triggers the sharing operation through 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 sharee from the request. Next, the back-end service can determine whether the identifier of the sharee belongs to a predetermined group, for example, by searching for the identifier of the sharee in the identifier set of the predetermined group. The predetermined group can be other groups such as corporate users or users who have activated the sharing function. This embodiment does not limit the predetermined group. If the identifier of the sharee belongs to the predetermined group, subsequent operations can be triggered to generate an interactive window. For example, the window attributes associated with the sharee can be determined, and then the interactive window can be generated based on the window attributes. If the identifier of the sharee does not belong to the predetermined group, the identifier of the sharee can be added to the sharing failure set. The sharing failure set can then be returned to the front-end to prompt the active sharer that the sharing operation for these sharee has failed.

[0109] It should be noted that the preprocessing process provided in this embodiment ensures that only users in the predetermined group can generate an interaction window by preprocessing the identifier of the shared party, thereby improving the accuracy of the sharing operation and effectively avoiding resource waste and incorrect sharing. At the same time, by recording the situation where the shared party identifier does not belong to the predetermined group in the sharing failure set and providing timely feedback 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, this solution also has good scalability, facilitating the development of 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 recording information in a predetermined database. For example, after the active sharer clicks on the sharing option on the front-end page or triggers the sharing operation through 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 responding 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 shared party), 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, it can be subsequently used in a variety of ways. For example, the predetermined database can be queried for information based on actual needs. In another example, the data in the predetermined database can be used to authenticate the recipient, including, for example, determining whether the recipient has permission 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 above describes the process of recording information in a predetermined database. It is understandable that in some embodiments, this process may 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 based on the different sharing types (individual or group). In addition, the backend service can also set different style values ​​based on the style parameters of the target object. 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 database table primary key ID, etc.

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

[0117] This embodiment implements a personalized interactive window assembly and generation process, enhancing the customization and user experience of information sharing. By extracting key email information and setting different style values, the rendering of the interactive window on the front-end page is ensured to be consistent with the content characteristics, enhancing the visual effect and information readability. Furthermore, by generating a specific interactive window for each recipient, the needs of different users are met and the accuracy of sharing is improved.

[0118] In one example, the interaction window generation process may include a prompt process. For example, if the backend service receives an interaction window from a predetermined generation service, the backend service may add the identifier of the sharee to the sharing success set. If the backend service does not receive an interaction window from a predetermined generation service, the backend service may add the identifier of the sharee 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 sharer of the sharing result of the interaction window based on the status of the sharing success set and the sharing failure set. For example, if the sharing failure set is empty, the active sharer is prompted that all sharing is successful. If the sharing success set is empty, the active sharer is prompted that all sharing has failed. If both the sharing success set and the sharing failure set are not empty, the active sharer is prompted with the successful and failed sharees respectively based on 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 target object is available to the sharee are obtained. For example, the object description and the query result may be obtained by the object sharing method described above.

[0122] In operation S720 , an operation option for the shared party is determined based on 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 permissions 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, who then shares the email with the first and second users. The second user and the second user click on the interactive window to display the email details. Since the first user has the shared email, the first user can reply to, forward, and perform other operations based on the email without having to return to their 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 to, forward, or 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 configured 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, and obtain a query result.

[0133] The first output module 850 is used to output object descriptions 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, a system determination module includes: a first system determination submodule and a second system determination submodule. The first system determination submodule is configured to determine a first system from multiple systems based on predetermined parameters in the window information. The predetermined parameters are added to the window information in response to an active sharer triggering a sharing operation for sharing an interactive window, and the predetermined parameters represent the system identifier of the active sharer. The second system determination submodule is configured to determine a second system from multiple systems based on the identifier of the shareee.

[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 configured to determine whether the shared party has permission to view the object description based on the window information and information in a predetermined database. The acquisition submodule is configured to acquire 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, information in a predetermined database is determined by the following modules: a third acquisition module and a storage module. The third acquisition module is configured to acquire information related to the sharing operation in response to detecting that an active sharer has triggered a sharing operation for sharing an interactive window. The storage module is configured 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 based on 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 the 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 the 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, the system further includes: a fourth acquisition module, a trigger module, and a third addition module. The fourth acquisition module is configured to acquire the identifier of the shareeee based on a sharing operation triggered by the active sharer. The trigger module is configured to trigger an operation of determining window attributes associated with the shareeee in response to detecting that the identifier of the shareeee belongs to a predetermined group. The third addition module is configured to add the identifier of the shareeee to a sharing failure set in response to detecting that the identifier of the shareeee 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] Figure 9 4 is a schematic structural block diagram of an object display device according to an embodiment of the present disclosure.

[0142] like Figure 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 based on the query results.

[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, including at least one processor; and a memory communicatively connected to the at least one processor; 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 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] Figure 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 assistants, 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 Figure 10 As shown, 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. RAM 1003 may also store various programs and data required for the operation of device 1000. Computing unit 1001, ROM 1002, and RAM 1003 are connected to each other via a bus 1004. An input / output (I / O) interface 105 is also connected to bus 1004.

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

[0153] Computing unit 1001 can be any general-purpose and / or specialized processing component with processing and computing capabilities. Some examples of computing unit 1001 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various specialized artificial intelligence (AI) computing chips, various computing units running machine learning model algorithms, a digital signal processor (DSP), and any suitable processor, controller, microcontroller, etc. 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 can be implemented as a computer software program tangibly embodied in a machine-readable medium, such as storage unit 1008. In some embodiments, part or all of the computer program can be loaded and / or installed onto device 1000 via ROM 1002 and / or communication unit 1009. When the computer program is loaded into RAM 1003 and executed by computing unit 1001, one or more steps of the object sharing method and the object display method described above can be performed. 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 embodiments of the systems and techniques described above 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), system-on-a-chip systems (SOCs), complex programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof. These various embodiments can include being implemented in one or more computer programs that are executable and / or interpreted on a programmable system that includes 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 can be written in any combination of one or more programming languages. These program codes can be provided to a processor or controller of a general-purpose computer, a special-purpose computer, or other programmable data processing device so that when the program code is executed by the processor or controller, the functions / operations specified in the flow chart and / or block diagram are implemented. The program code can be executed entirely on the machine, partially on the machine, as a stand-alone software package, partially on the machine and partially on a remote machine, 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, apparatus, or device. 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, apparatus, or device, or any suitable combination of the foregoing. More specific examples of machine-readable storage media may include an electrical connection based on one or more wires, 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), optical fibers, 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 can 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 can 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] Computer systems may include clients and servers. A client and server are generally remote from each other and typically interact through a communication network. The client and server relationship arises through computer programs running on the respective computers and having a client-server relationship to each other.

[0160] It should be understood that the various forms of the processes shown above can be used to reorder, add, or delete steps. For example, the steps described in this disclosure can be performed in parallel, sequentially, or in a different order, as long as the desired results of the technical solutions disclosed in this disclosure can be achieved. This is not limited herein.

[0161] The above specific embodiments do not constitute a limitation on the scope of protection of this disclosure. Those skilled in the art will appreciate that various modifications, combinations, sub-combinations, and substitutions may be made based on design requirements and other factors. Any modifications, equivalent substitutions, and improvements made within the spirit and principles of this disclosure shall be included within the scope of protection of this disclosure.

Claims

1. A method for sharing an object, comprising: In response to detecting that the recipient party performs a predetermined operation on the interactive window, obtaining window information of the interactive window and an identifier of the recipient party; wherein the interactive window is generated based on a target object shared by the active sharer to the recipient party; Determining, based on the window information and the identifier of the shared party, a first system in which the active sharing party is located and a second system in which the shared party is located, comprising: determining the first system from a plurality of systems based on 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 the system identifier of the active sharing party; and determining the second system from the plurality of systems based on the identifier of the shared party; 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, and obtaining the query result includes: Determining a basic identifier of the target object based on the window information; According to the basic identifier, querying the second system for candidate objects that match the basic identifier; 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 acquiring the object description of the target object based on the first system includes: determining, based on the window information and information in a predetermined database, whether the shared party has permission to view the object description; and In response to detecting that the shared party has the permission, an object description of the target object is obtained based on the first system.

4. The method according to claim 3, 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.

5. 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, determining a window attribute associated with the shared party according to a sharing operation triggered by the active sharing party; calling a predetermined generation service according to the window attributes 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 to prompt the active sharing party with the sharing result of the interactive window.

6. The method according to claim 5, further comprising: Obtaining the identifier of the shared party according to the sharing operation triggered by the active sharing party; In response to detecting that the identifier of the shared party belongs to a predetermined group, triggering an operation of determining window attributes 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.

7. 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.

8. A method for displaying an object, comprising: Obtaining an object description of the target object and a query result indicating whether the shared party has the target object; Determining, based on 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 7.

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

10. An object sharing device, comprising: A first acquisition module is configured 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 sharer to the shared party; a system determination module, configured 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 A first output module, configured to output the object description and the query result; Wherein, the system determination module includes: a first system determination submodule, configured to determine the first system from a plurality of systems based on 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 an identifier of the system in which the active sharing party is located; and The second system determining submodule is configured to determine the second system from the multiple systems according to the identifier of the shared party.

11. The device according to claim 10, wherein The query module includes: A basic identification submodule, configured 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 determining 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 determining 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.

12. The device according to claim 10, wherein The second acquisition module includes: a permission determination submodule, configured to determine whether the shared party has permission to view the object description based on the window information and information in a predetermined database; and The acquisition submodule is configured 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.

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

14. The device according to claim 10, wherein The number of the shared party is at least one, and the apparatus 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 configured to output the sharing success set and the sharing failure set, so as to prompt the active sharing party with the sharing result of the interactive window.

15. The apparatus according to claim 14, 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 window attributes 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.

16. The device according to claim 10, 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.

17. An object display device comprising: a fifth acquisition module, configured 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, configured to determine, based on the query result, an operation option for the shared party to use; as well as A rendering module, configured to render the object description and the operation options; The object description and the query result are obtained based on the device described in any one of claims 10 to 16.

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

19. 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 9.

20. 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 9.

21. 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 9.

Images